[OSM-talk] List of changes from API only gives target tile of moved node
Andre Hinrichs
andre.hinrichs at gmx.de
Sun Dec 20 18:58:07 GMT 2009
Am Sonntag, den 20.12.2009, 19:12 +0100 schrieb Frederik Ramm:
> Hi,
>
> Andre Hinrichs wrote:
> > See list of changes for the here:
> > http://www.openstreetmap.org/api/0.6/changes?start=2009-12-18T17:12:00Z&end=2009-12-18T17:13:00&zoom=12
> >
> > So currently both mapnik and t at h have a ghost way:
>
> What you describe may be right, but the reasoning is not; the Mapnik map
> does not use the API to find out what has changed, but instead relies on
> the diffs generated by Osmosis.
Then why does Mapnik show the same behaviour than T at H? If Mapnik would
take the diffs of Osmosis than it would have recognised that the tile
has changed, wouldn't it?
> > Is API 0.6 meant to list both tiles (means, this is a bug) or is this
> > possibly worth a feature request for API 0.7?
>
> Frankly, I think the "changes" call you're describing could well be
> removed altogether for 0.7 as it is very limited in the first place and
> does not seem to offer any advantages over running Osmosis and
> retrieving the changesets.
I'm pretty sure, that at least T at H uses it currently. But if there is an
easy (fast) way to get the changed tiles out of the diffs than it could
possibly be adapted.
Does creating the changes via osmosis have less limitations than the API
way? If yes, which?
Anyway, if not many services use it (except T at H) it would not create a
high load on the server, so why drop it?
Andre
More information about the talk
mailing list