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: BrunoC [Submitted to the original trac issue database at 12.29am, Friday, 14th January 2011]
Mapnik renders areas tagged with protected_area=* with 'solid' color. When the area is over the sea or natural=* area the rendered map is not very good. A solution is to use some a very ligh transparency and a more marked limit like boundary=national_park
Author: steve8[at]mdx.ac.uk [Added to the original trac issue at 6.21pm, Tuesday, 18th January 2011]
Done in latest revision, but please check your boundaries. In first example it doesn't seem to recognise the large boundary, and the small island ones are duplicated. In second example there seems to be a join
Author: cmuelle8 [Added to the original trac issue at 3.07am, Tuesday, 27th August 2013]
This has not been closed for good, protected_area should differentiate according to protect_class and not be hard wired to national_park for all classes/cases.
The reason this has been closed originally seem to be changesets [25056] and [25057] - but these do not affect osm slippy map, just http://www.hikebikemap.de, or more genereally nor-screenspec and nor-hikingmap based renderers.
See also #3102 and the newer #4249 for dups of this bug.
Reporter: BrunoC
[Submitted to the original trac issue database at 12.29am, Friday, 14th January 2011]
Mapnik renders areas tagged with protected_area=* with 'solid' color. When the area is over the sea or natural=* area the rendered map is not very good. A solution is to use some a very ligh transparency and a more marked limit like boundary=national_park
Link this to http://trac.openstreetmap.org/ticket/3102
Some examples :
http://osm.org/go/erB2742
http://osm.org/go/eqtY2vY
The text was updated successfully, but these errors were encountered: