Opened 11 years ago

Closed 9 years ago

#1018 closed defect (worksforme)

Strangly rendered bridges at lowzoom

Reported by: Astrofreak85 Owned by: osm@…
Priority: major Milestone:
Component: osmarender Version:
Keywords: Cc: osm@…

Description

You can see the problem here for example: http://www.informationfreeway.org/?lat=51.17003021111493&lon=13.837901379145942 or here: http://www.informationfreeway.org/?lat=51.13685367802098&lon=13.684049903374985

Is this render bug, or is there something tagged wrong? In mapnik it seems to be OK.

Attachments (1)

osm_bug.png (80.6 KB) - added by Astrofreak85 11 years ago.
bugous bridges are marked with a red arrow

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by Astrofreak85

Attachment: osm_bug.png added

bugous bridges are marked with a red arrow

comment:1 Changed 11 years ago by Dirk Stoecker

Isn't that a topic for maplint?

comment:2 Changed 11 years ago by Astrofreak85

I think I have an idea why this happens:

A bridge is at a higer layer than the rest of the way, and it semms to me, that a bridge has a small black line at the end, and becaus of it's at another layer, also the thin black lin is rendered.

When ther is a bridge over an other street, the bridge has a fixed lenght, so when you zoom out, the street (wich is crossed by the bridge) get wider, after so zoomsteps the street is wider then the bridge above is long.

I don't now, how the guys on mapnik get rid of this, but there it doesn't seem to be like in osmarender.

comment:3 Changed 10 years ago by osm@…

Cc: osm@… added

I guess we have to move the start/end of way tagged as bridge=yes along the way going over the bridge until the nodes are outside the (exaggeratedly wide) way passing under the bridge. Not easy to get right in all instances.

comment:4 Changed 9 years ago by Jochen Topf

Owner: changed from Jochen Topf to osm@…

comment:5 Changed 9 years ago by spaetz

Resolution: worksforme
Status: newclosed

The bridges in the example above look all fine to me now. Thanks for reporting this and do reopen if this issue is not fixed yet.

Note: See TracTickets for help on using tickets.