[OSM-dev] 0.6 API clarifications and corrections

Martijn van Oosterhout kleptog at gmail.com
Thu May 15 08:10:42 BST 2008

On Thu, May 15, 2008 at 7:28 AM, bvh <bvh-osm at irule.be> wrote:
> On Thu, May 15, 2008 at 08:30:08AM +0200, Martijn van Oosterhout wrote:
>> So, we specced out what you would need for a changeset download,
>> invented old_version and new_version and then used old_version
>> everywhere we needed it. If we do it your way then we would get
>> old_version and version for the changeset download, right?
> Well, see my earlier mail on the subject. I don't think we should
> be sending full object definitions as a response to diff uploads.

I'm not talking abot diff upload responses, I'm talking about
changeset downloads. Say I note that object 123 was modified in
changeset 456 six weeks ago. And I go to the API and say: show me
everything done in changeset 456. You're right, the response to an
upload doesn't need it.

> Well the changeset_id is certainly bogus when you save it to disk no?
> What would you put in it? Scenario : I am somewhere in the woods with
> JOSM/merkaartor on a laptop charting new territory without internet.
> Now I want to save my work to a file so I can later upload it.
> What would we save in the changeset_id?

Leave it out, obviously. Say I do a map call for an area, currently
you get for example the user_id, soon you will get the changeset ID.
So in JOSM if you see a way changed, you will be able to ask "which
other things were changed at the same time?".

This information should be saved if I save the data to disk and load
it up later. It isn't necessary for uploading though. If you download
an area in general every object will have a different changeset id so
you can't stick it in the header...

Have a nice day,
Martijn van Oosterhout <kleptog at gmail.com> http://svana.org/kleptog/

More information about the dev mailing list