[OSM-talk] List of changes from API only gives target tile of moved node

2009-12-20 Thread Andre Hinrichs
Hi List! I've fixed a misplaced node in a way and was waiting for the rendered tiles to be updated. I was expecting that both tiles are beeing updated the one where the node was and the one where the node was moved to. But unfortunately, only the tile the node was moved to was updated. Moved node

Re: [OSM-talk] List of changes from API only gives target tile of moved node

2009-12-20 Thread 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...@h have a ghost way: What you describe may be right, but the reasoning is not; the Mapnik m

Re: [OSM-talk] List of changes from API only gives target tile of moved node

2009-12-20 Thread Andre Hinrichs
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...@h have a ghost

Re: [OSM-talk] List of changes from API only gives target tile of moved node

2009-12-20 Thread Frederik Ramm
Hi, Andre Hinrichs wrote: > Then why does Mapnik show the same behaviour than t...@h? The osc file doesn't list the old position of the node. You could find out by querying your local database for the old position but this is deemed too much cost for too little gain. > Does creating the chang

Re: [OSM-talk] List of changes from API only gives target tile of moved node

2009-12-20 Thread Matt Amos
On Sun, Dec 20, 2009 at 8:17 PM, Frederik Ramm wrote: > Andre Hinrichs wrote: >> Anyway, if not many services use it (except t...@h) it would not create a >> high load on the server, so why drop it? > > I think it is certainly an "odd one out" among the API calls; no other > API call concerns itse