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.
Just noticed that secondary bridges are being rendered on z15-z13 a lot bigger than primary bridges that are nearby, which shouldn't be the case.
So, I went into the osm.xml file to see if I could spot where the problem was and I 'think' I found it.
The problem (I think) lies in the "<Style name="bridges_fill">" section. Now, I don't fully know all that much on how the style sheet works, so, I will not go suggesting exactly what to fix because for all I know, what I suggest could make it worse.
But this secondary bridge is rendered bigger than the twinned SR 592 right above it which should be wider since there are two ways there that are combined when rendered at z15-z13. So, any rendering fix would be appreciated for this.
The text was updated successfully, but these errors were encountered:
Reporter: rickmastfan67
[Submitted to the original trac issue database at 9.35pm, Friday, 17th June 2011]
http://www.openstreetmap.org/?lat=36.107&lon=-115.1832&zoom=14&layers=M
Just noticed that secondary bridges are being rendered on z15-z13 a lot bigger than primary bridges that are nearby, which shouldn't be the case.
So, I went into the osm.xml file to see if I could spot where the problem was and I 'think' I found it.
The problem (I think) lies in the "<Style name="bridges_fill">" section. Now, I don't fully know all that much on how the style sheet works, so, I will not go suggesting exactly what to fix because for all I know, what I suggest could make it worse.
But this secondary bridge is rendered bigger than the twinned SR 592 right above it which should be wider since there are two ways there that are combined when rendered at z15-z13. So, any rendering fix would be appreciated for this.
The text was updated successfully, but these errors were encountered: