[OSM-dev] OSM API Improvements work

[Ian Dees]

Tom, all of these things already exist as part of other tools.

JSON formatting and filtering for API endpoints exist as part of jxapi (
https://github.com/iandees/xapi-servlet).

TagInfo has an API that's fairly well done. What did you have in mind to
improve it?

On Thu, Oct 11, 2012 at 2:26 PM, Tom MacWright <tom at macwright.org> wrote:

> Hey dev,
>
> Just posted the first few issues of the work that I can deem 'stuff that
> we're doing as part of the Knight iniative'. They consist of API-related
> tasks, some of which have had prior art but haven't been tested/completed
> enough to ship. I'd like to get them done and shipped to make some
> substantive improvement in the API.
>
> The first three are:
>
> * JSON formatting for API calls and GeoJSON for some of them. Basically
> just making things friendly for Javascript and other JSON-era languages.
> * Filtering the API endpoints, so that POI editors don't have to sift
> through road data, and so on.
> * A TagInfo-like API for 'commonly used tags'
>
> ( see on
> https://github.com/openstreetmap/openstreetmap-website/issues?direction=desc&sort=created&state=open)
>
> There are a few more tasks to come - stuff like the possibility of an
> Oauth 2 client flow, a complete user API for stuff like user photos &
> stats. Some of the tasks might not be necessary, some might be in need of
> technical reframing (what should be done in cgimap instead?): if you've got
> (constructive) input, please give it!
>
> Tom
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20121011/6e46fe37/attachment.html>