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
I think it would be a good idea not to render parking lot areas amenity=parking within surrounding forest areas landuse=forest with the typical forest pattern onto it.
A parking lot area (like highway - ways) is usually never covered with (dense) trees like the surrounding forest. Maybe with some single trees between the parking lanes - but these single trees are not part of a forest.
Please render parking areas above the forest area. Right now we would have to cut out each parking lot of the forest's Multipolygon, which in my opinion is unnecessary and not logical.
This is intentional. We render landuse=forest as meaning here trees grow - just like natural=wood. If a polygon tagged amenity=parking overlaps landuse=forest that is intentionally rendered with tree symbols indicating that this is a parking within the forest and the parking does not interrupt the tree cover. See also #1754 (comment).
There indeed exist parkings in dense forest (e.g. https://www.openstreetmap.org/way/146414430). Of course, you can freely drive a car in such a forest, but the tree tops create a continuous canopy. It should be OK to render that with the tree pattern on top of the parking lot.
If there are no trees in the parking lot, it should be cut out of the forest using an inner member of a multipolygon.
I think it would be a good idea not to render parking lot areas
amenity=parking
within surrounding forest areaslanduse=forest
with the typical forest pattern onto it.A parking lot area (like highway - ways) is usually never covered with (dense) trees like the surrounding forest. Maybe with some single trees between the parking lanes - but these single trees are not part of a forest.
Please render parking areas above the forest area. Right now we would have to cut out each parking lot of the forest's Multipolygon, which in my opinion is unnecessary and not logical.
An example is the following parking lot:
https://www.openstreetmap.org/#map=19/47.93165/14.12401
The text was updated successfully, but these errors were encountered: