Opened 12 years ago

Closed 9 years ago

#1327 closed defect (invalid)

Rendering non-existent data

Reported by: chriscf Owned by: jburgess777@…
Priority: major Milestone:
Component: mapnik Version:
Keywords: Cc: Nakor


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?

Change History (6)

comment:1 Changed 12 years ago by osm@…

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.

comment:2 Changed 12 years ago by steve8@…

Resolution: fixed
Status: newclosed

Someone has tidied up the data now

comment:3 Changed 10 years ago by Dwi Secundus

Resolution: fixed
Status: closedreopened

This is not fixed. Mapnik renders the South Pole at (0,0):

comment:4 Changed 10 years ago by Ldp

Owner: changed from steve8@… to jburgess777@…
Status: reopenednew

Can we filter for this in osm2pgsql?

comment:5 Changed 10 years ago by Nakor

Cc: Nakor added

comment:6 Changed 9 years ago by Ldp

Resolution: invalid
Status: newclosed

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.

We should find out soon whether the code works.

Note: See TracTickets for help on using tickets.