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: 2longbow[at]gmx.de [Submitted to the original trac issue database at 10.04am, Thursday, 26th February 2009]
The mapfeatures page on OSM wiki gives additional key/value sets for landuse forest, e.g.
wood=mixed etc. It appears that when additional values are added to landuse forest, the green area fails to render on the Mapnik stylesheet. I noticed something similar to happen on landuse=residential. When the additional value name=Waldgirmes (to name the residential area) is set, the grey residential area fails to render. After removing the additional values (wood, name) the areas render fine.
Thank you for looking into it.
Longbow4u
The text was updated successfully, but these errors were encountered:
Author: 2longbow[at]gmx.de [Added to the original trac issue at 10.54pm, Friday, 27th February 2009]
The Forest area north of Alten-Buseck and north of the motorway. Another user had added k=wood v=mixed. The area did not render. Then I removed this value set, now the landuse=forest area is properly rendered.
Permalink follows:
Reporter: 2longbow[at]gmx.de
[Submitted to the original trac issue database at 10.04am, Thursday, 26th February 2009]
The mapfeatures page on OSM wiki gives additional key/value sets for landuse forest, e.g.
wood=mixed etc. It appears that when additional values are added to landuse forest, the green area fails to render on the Mapnik stylesheet. I noticed something similar to happen on landuse=residential. When the additional value name=Waldgirmes (to name the residential area) is set, the grey residential area fails to render. After removing the additional values (wood, name) the areas render fine.
Thank you for looking into it.
Longbow4u
The text was updated successfully, but these errors were encountered: