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 changes via osmosis have less limitations than the API > way? If yes, which? You can generate a list of changes for any interval (provided you have the matching .osc files available of course), and for any zoom level. > 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 itself with tile numbers of a spherical Mercator projection. Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
