criticalmaps / criticalmaps-api Goto Github PK

Is there any documentation for the API and their responses. I'm currently looking at the code for the client but it would be nice to have a document that contains all the information.

Especially for existing conventions that are used in the mobile clients like the update intervals for locations

Last discussed implementation was:

• a new optional Boolean field in the requests device object called observerMode
• value should be saved alongside the location on the backend (defaults to false)
• responses to clients should only include locations where observerMode == false

It would be really cool if you could provide more geolocation information like accuracy and the timestamp of the data. The accuracy value would be useful to filter through the geolocation data and throw out all those "somewhere here in a 15 mile radius" users to build a nice timelapse or heatmap.

moved over from criticalmaps/criticalmaps-web#1

The JSON response from the API does not return the correct content type:

$ curl -s -D - http://api.criticalmaps.net/twitter/get.php

HTTP/1.1 200 OK
Date: Sun, 04 Oct 2015 22:27:23 GMT
Server: Apache
X-Powered-By: PHP/5.4.44
Transfer-Encoding: chunked
Content-Type: text/html

It should be Content-Type: application/json;charset=utf-8 instead.

👋 I believe it would be useful to cluster the locations in order to quickly find out what points belong to what criticalmass. This would then enable other functionaly: like estimating the direction of each critical mass.

The API could just have another field per record with a cluster number.

Depending on the method the clusters could be computed on the fly or on a regular basis in the background.

I would be happy to work on something. Depending on the algorithm there could either be a pure JS algorithm or there is another local http service giving the cluster estimates.

Questions:

• do you think this is useful?
• would you accept a pull request?
• are there open datasets of past critical masses?

As far as I can tell after my first time of using the app there is no way to see the currently running CM identified so that could be a potential blocker for this proposal. But it would be nice to give feedback about the current mass.

Feedback Ideas:

• Speed (too fast / too slow?)
• Route (like / dislike)

This could become a part of the chat or be implemented in a new view. An alternative would be to just give feedback after the ride has ended.