libremap / libremap-api Goto Github PK

The data from openwifimap should (at least once) be imported to libremap.

I understand that it makes no sence for an map-applikation to render nodes with no location data (lat, lon).
But the libremap-api is not a map applikation. It provides only an API for a collection of wifi nodes.
In the future I want to create simple statistic applikations that show e.g. the count of all online and offline nodes of a specific community. Also graphs like the ffmap-d3 are a nice example what could be done using the libremap-api as backend. For this tasks the position of nodes is not needed at all.

We should change the API in future versions to allow nodes with no position but instead change the map-specific views to simply ignore such nodes.

Old

lat: (required, number) latitude in degrees, range [-90,90], EPSG:3857.
lon: (required, number) longitude in degrees, range [-180,180], EPSG:3857.
elev: (optional, number) elevation in meters above mean sea level.

New

location: { (optional, object)
    lat: (required, number) latitude in degrees, range [-90,90], EPSG:3857.
    lon: (required, number) longitude in degrees, range [-180,180], EPSG:3857.
    elev: (optional, number) elevation in meters above mean sea level.
}

Is this something for version 2.0? What do you thing guys?

Just skimmed the api documentation [1] and I think you should puralize? the endpoint name for router to api/routers. If there are or will be other endpoints you should also rename them.

A maybe good resource for arguments:

http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

Maybe it's also worth to think about the routers_by_location resource? Just brain storming:

• api/bboxes/1/2/3/4 (-1)
• api/routers?bbox=1,2,3,4 (+1)
• api/routers?clustered=true
• api/routers?clustered=true&stripped=true

I understand that this is a very subjective topic but there are some conventions that most people try to follow and maybe we should try to do so too.

Thanks for your ongoing hard work on the topic! Nice work!!!

Best Regards
Philipp

[1] https://github.com/libremap/libremap-api/blob/master/doc-api.md

add field with status information ["online", "offline", "unknown"]

A maintenance script should be run regularly or as a daemon that

• initiates a CouchDB database cleanup + compaction.
• deletes routers from the database that haven't been updated for a while.

In future, such a script could also listen on the database's changes feed and create documents for statistics...

add field with number of currently connected clients

it would be nice to have a object containing system information like the following:

• number of processes
• memory usage
• OS type and version
• wireless chip revision
• cpu type
• loadaverage

it can come very useful to find way of contacting someone who acts as a admin(s) for particular node. maybe something in lines:

"admins": [
  {
    "name": "Bob",
    "email": "[email protected]"
  }, {
    "name": "Alice",
    "jabber": "[email protected]",
    "irc": "irc://freenode.net/alice"
  }
]

Hi,

I'm embarrassed to say that I got stuck on the first line of the installation instructions

CouchDB server 1.3 (or newer) with the GeoCouch plugin.

Is there a simple way to install CouchDB with the GeoCouch plugin on Ubuntu? I've successfully compiled CouchDB 1.6 from scratch but attempts to pull the latest GeoCouch repo and compile generates errors and fixing one only seems to reveal others. Am I doing something wrong? Should I be using an earlier version of CouchDB?

• orientation of antenas
• modes master / client / adhoc
• ESSID / BSSID
• channels

I work lately a lot with Linked Data and JSON-LD and would like to create JSON-LD context for schema used by routers.

similar as in http://map.ninux.org

• how to represent it in schema?
• how to prevent cluttering with inactive 'planned' nodes?

Set up couchdb+geocouch and test API on travis-ci

Currently, there's no way to determine to which local alias is associated with a link. Thus, I suggest to add a mandatory alias_local field into each link object, e.g.

"links": [
    {
      "alias": "52:23:61:a7:a1:56",
      "alias_local": "ca:ff:ee:51:34:21",
      "type": "batman-adv",
      "quality": 0.78
    },
    ...
]