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: IknowJoseph [Added to the original trac issue at 4.46pm, Friday, 21st December 2012]
The originally reported area was fixed by some heavy editing, but that seems like an unsustainable approach to the whole area. Also affected, for example:
Author: Ldp [Added to the original trac issue at 10.04pm, Thursday, 16th May 2013]
Somehow, at some point, adding/modifying these ways in the osm.org rendering db must have gone wrong. Editing these ways causes them to be reprocessed, so they then show up.
There is not much that can be done about this from a stylesheet perspective and only the server admins could force a reimport of the affected ways.
Reporter: IknowJoseph
[Submitted to the original trac issue database at 8.58am, Tuesday, 18th December 2012]
(Added this to Component Website as I'm not sure it's a Mapnik issue - other Mapnik renderers seem to be ok, it's just osm.org that fails)
The tile renderer at osm.org is failing to render some highway ways. Compare osm data with the rendering at:
http://www.openstreetmap.org/?lat=51.02554&lon=-3.6502&zoom=17&layers=M
Note that MapQuest is showing the junction as the data represents it:
http://www.openstreetmap.org/?lat=51.02554&lon=-3.6502&zoom=17&layers=M
I have edited features within the affected area - new ones are showing in rendered tiles, but existing ways are troublesome:
http://c.tile.openstreetmap.org/16/32103/21932.png
Sample affected ways (there are further ways south of this location that show the same symptoms) : 149335654 135724736 149333479 135724729
The text was updated successfully, but these errors were encountered: