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.
Reporter: schuetzm[at]gmx.net [Submitted to the original trac issue database at 11.14pm, Friday, 27th June 2008]
When a wayMarker is rendered on a node connected to more than one way, the wayMarker is always rendered perpendicular to the first way. This can lead to unintended results, when a gate on a highway= is placed directly at the border of a landuse area (e.g. cemetery or allotments).
The attached patch adds two (optional) attributes k= and v= to the wayMarker instruction in ORP. When these are set, the renderer uses the first way matching the specified key or (key,value) pair.
The text was updated successfully, but these errors were encountered:
Reporter: schuetzm[at]gmx.net
[Submitted to the original trac issue database at 11.14pm, Friday, 27th June 2008]
When a wayMarker is rendered on a node connected to more than one way, the wayMarker is always rendered perpendicular to the first way. This can lead to unintended results, when a gate on a highway= is placed directly at the border of a landuse area (e.g. cemetery or allotments).
Example: http://www.openstreetmap.org/?lat=48.9533&lon=9.58121&zoom=17&layers=0B0FTF
The attached patch adds two (optional) attributes k= and v= to the wayMarker instruction in ORP. When these are set, the renderer uses the first way matching the specified key or (key,value) pair.
The text was updated successfully, but these errors were encountered: