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.
Author: Ldp [Added to the original trac issue at 11.46am, Friday, 28th August 2009]
Yes, that one is still active (or actually, in osm2pgsql's source). I was actually counting on it picking about the same spot as the polygon centroid mapnik is supposed to take, dropping one of them due to a collision.
I wonder which P comes from which source. If the out of center one is mapnik's, why would it choose such an awkward spot for such a simple polygon?
Author: jburgess777[at]googlemail.com [Added to the original trac issue at 12.03pm, Friday, 28th August 2009]
The two nodes on the right have been moved several times. If they were aligned with the road to right then the second P would be in about the centre of this area. I don't believe the diff update process does anything to delete the generated P nodes when parking areas are updated.
There are currently two generated P nodes in the DB:
Reporter: wiso
[Submitted to the original trac issue database at 1.43pm, Thursday, 27th August 2009]
Look here:
http://www.openstreetmap.org/?lat=45.356127&lon=9.65366&zoom=18&layers=B000FTF
there is a parking with 2 "P". I try to regenerate the tiles locally with R17299 and I don't get the double "P"
The text was updated successfully, but these errors were encountered: