You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: chriscf [Submitted to the original trac issue database at 2.03pm, Wednesday, 12th November 2008]
Something seems to be rendered at (0,0). The API denies that there is any current data near this location. This has been here for several weeks now - perhaps some data is being cached here?
The text was updated successfully, but these errors were encountered:
Author: osm[at]randomjunk.co.uk [Added to the original trac issue at 10.42am, Thursday, 13th November 2008]
It's because the data isn't actually there -- it's somewhere else.
When things go wrong it's not unusual for the projection code etc to
end up sticking stuff at 0,0. The API doesn't return it though.
For example, the station is node 32009797, located at -90 latitude...
the south pole.
There's also a BP petrol station at the north pole, a helpful
place=continent for Antartica, a helpful place for the North Pole, and
a number of parking nodes inserted by osm2pgsql from parking areas
that it obviously doesn't like.
So it's partially some bad data, and partially some odd behaviour on
the part of osm2pgsql/postgis/mapnik.
Author: Ldp [Added to the original trac issue at 9.27pm, Sunday, 27th March 2011]
Some code has been added to osmg2pgsql two months ago to attempt to deal with this problem. It's not a mapnik problem as such, but rather something that happens during the import of the planet into the rendering db.
Reporter: chriscf
[Submitted to the original trac issue database at 2.03pm, Wednesday, 12th November 2008]
Something seems to be rendered at (0,0). The API denies that there is any current data near this location. This has been here for several weeks now - perhaps some data is being cached here?
The text was updated successfully, but these errors were encountered: