publiclab / mapknitter

Upload your own aerial images, position (rubbersheet) them in a web interface over existing map data, and share via web or composite and export for print.
http://mapknitter.org
GNU General Public License v3.0
267 stars 208 forks source link

create API to retrieve maps for a given user #175

Open btbonval opened 9 years ago

btbonval commented 9 years ago

There is/was an RSS feed for maps, but it was causing problems when publiclab.org tried to download the RSS feed.

At any rate, processing an RSS feed is likely suboptimal compared to a RESTful API.

For example: GET https://mapknitter.org/user/41231/maps.json (returns all the user's maps in a JSON list) GET https://mapknitter.org/user/41231/maps.csv (returns all the user's maps as a single row, comma separated)

This interface could be expanded to include metadata or whatever with json dicts and one csv row per map (with columns containing URL, name, other metadata).

When publiclab.org needs to get a user's maps, it knows the user id, and can very easily fetch a json or csv from MapKnitter.org which should parse super fast.

This is also sort of industry standard for machines talking to other machines, whereas RSS is mostly meant for RSS reader applications exclusively.

jywarren commented 9 years ago

Yay also this could be accessed very natively from plots2 using activeresource, which is sorta like an ORM for Rest APIs in rails.

I'm sure bryan will have a more accurate way to describe it. On May 4, 2015 12:09 PM, "Bryan Bonvallet" notifications@github.com wrote:

There is/was an RSS feed for maps, but it was causing problems when publiclab.org tried to download the RSS feed.

At any rate, processing an RSS feed is likely suboptimal compared to a RESTful API.

For example: GET https://mapknitter.org/user/41231/maps.json (returns all the user's maps in a JSON list) GET https://mapknitter.org/user/41231/maps.csv (returns all the user's maps as a single row, comma separated)

This interface could be expanded to include metadata or whatever with json dicts and one csv row per map (with columns containing URL, name, other metadata).

When publiclab.org needs to get a user's maps, it knows the user id, and can very easily fetch a json or csv from MapKnitter.org which should parse super fast.

This is also sort of industry standard for machines talking to other machines, whereas RSS is mostly meant for RSS reader applications exclusively.

— Reply to this email directly or view it on GitHub https://github.com/publiclab/mapknitter/issues/175.