search

osm-spline / xappy.js

Xappy.JS
Other
37 stars 4 forks source link

Implment json standard #73

Closed slomo closed 13 years ago

slomo commented 13 years ago

This directly relates to #72. The task is to implment a common standard

andreasnuesslein commented 13 years ago

decided to implement our own.

basically it does this: {"version":0.6,"generator":"xappy.js", "xapi":{"uri":"XXX","planetDate":"XXX","copyright":"XXX","instance":"XXX"},

"elements": [{"id":1,"lat":9.427,"lon":51.415,"version":1,"uid":291857,"user":"sladda","changesetId":123456,"timestamp":"2011-05-26T16:47:48.000Z","tags":[],"type":"node"}, {"type":"way", ....}, {"type":"relation",...} ]}

someone who likes wiki-editing should write this to the osm-wiki now ;)

booo commented 13 years ago

Could you please write a bit of documentation for the github wiki? I can edit the osm-wiki afterwards. There should be an example for every typ of object.

andreasnuesslein commented 13 years ago

Query: which timestamp format should we use?! i'd prefer unix timestamp as it is easy to "read".

andreasnuesslein commented 13 years ago

"changeset" or "changesetId" - who made the move to changesetID? in the Xapi-documentation it's 'changeset' and it would be stupid to modify all the js-objects on their way to the json-output.

i move for a renaming of changesetid to changeset

andreasnuesslein commented 13 years ago

https://github.com/slomo/osm-spline-xapi/wiki/JSON-Output < tadaaa...

booo commented 13 years ago

Sounds like an argument. I think it's changesetId at the moment because the database column is changeset_id and it fits better to what the attribute real is. It's a reference to something not the actual changeset. But we don't care about changesets so feel free to rename the attribute.

Thx for the documentation!

booo commented 13 years ago

Dario would you like to announce and discuss the json format on the osm-dev mailinglist? dev@openstreetmap.org is the place to be ;)

dalino commented 13 years ago

ok

andreasnuesslein commented 13 years ago

this issue will be closed in favor of #85