[OSM-dev] API 0.6: Changeset Access

Shaun McDonald shaun at shaunmcdonald.me.uk
Wed Jan 28 11:38:15 GMT 2009


You can just look at the object history, which will also include the  
changeset ids of each version of the node/way/relation.

Shaun

On 28 Jan 2009, at 11:20, David Earl wrote:

> It would be useful to know which changeset(s) a particular object
> appears in backwards through time. If you want to revert soemthing a
> particular object is likely to be the starting point I'd have  
> thought. I
> agree with your general thoughts though.
>
> David
>
> On 28/01/2009 11:09, Frederik Ramm wrote:
>> Hi,
>>
>>    to make good use of the new changeset stuff for analysing and
>> possibly also reverting changes, third parties will probably want to
>> know which changesets exist.
>>
>> We have not planned to include an API call that says "give me all
>> changesets that intersect this bbox" or so, and neither do we have
>> something where you can access a list of changesets based on other
>> criteria ("all changesets of the last hour" or so).
>>
>> Will the planet dump and/or diffs be extended so that they contain  
>> all
>> changesets too, or what should be the preferred mode of operation  
>> for a
>> third-party application that wants to track changesets? The only  
>> way I
>> can currently think of would be looking at diffs to find out which
>> changeset IDs were active and then download them individually. Have I
>> overlooked something?
>>
>> Should we perhaps add a changeset query call that lets you find
>> changesets? Or shift the burden onto the interested parties by simply
>> giving them changeset "dumps" and "diffs"?
>>
>> Bye
>> Frederik
>>
>> _______________________________________________
>> dev mailing list
>> dev at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/dev
>>
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev





More information about the dev mailing list