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: edloach [Submitted to the original trac issue database at 9.57pm, Sunday, 8th February 2009]
I finally got around yesterday to converting Walton pier into a pier, rather than it being defined as coastline. Checking the Osmarender layer this morning, and then some of the stylesheets, it seems T@H only renders man_made=pier as a line rather than an area. Map Features suggests it can be either.
Walton pier can be seen here: http://www.openstreetmap.org/?lat=51.84574&lon=1.27513&zoom=17&layers=0B00FTF
The text was updated successfully, but these errors were encountered:
Author: osm[at]deelkar.net [Added to the original trac issue at 10.41am, Monday, 9th February 2009]
have you tried setting area=yes? otherwise it's a Hard Problem for osmarender to distinguish between lines and areas, since osmarender tries to auto-close areas if not closed, which would lead to misrenderings on linear, but angled piers.
However I have no idea wether or not area=yes is already supported for man_made=pier, which it should
Reporter: edloach
[Submitted to the original trac issue database at 9.57pm, Sunday, 8th February 2009]
I finally got around yesterday to converting Walton pier into a pier, rather than it being defined as coastline. Checking the Osmarender layer this morning, and then some of the stylesheets, it seems T@H only renders man_made=pier as a line rather than an area. Map Features suggests it can be either.
Walton pier can be seen here:
http://www.openstreetmap.org/?lat=51.84574&lon=1.27513&zoom=17&layers=0B00FTF
The text was updated successfully, but these errors were encountered: