|
http://www.openstreetmap.org/relation/7184233 The fountain was not visible as it was covered by the highway=pedestrian. I created a multipolygon relation so that the fountain would be outside of the pedestrian area. But then it's shown as a hole, showing the road below it. Is it a bug of the mapping engine or is it the wrong way to map it?
|
|
Don't create a hole if there isn't any. If the fountain is not visible then this is a rendering issue. This is no reason for changing the data (see tagging for the renderer)! The first priority is always to keep the data correct. Creating an artificial hole will have a negative impact on routing. Rendering issues can be reported at the openstreetmap-carto GitHub repo after making sure that 1) the data is correct and 2) the tiles you are seeing are up to data and not coming from your browser cache. Thank you for the answer. Yes, I know about that wiki page. I'm wondering however if the fountain should be kept inside the highway=pedestrian as we don't usually walk in it. So I don't actually see it as a hole and the previous state could be considered as "tagging for the renderer" if it's just to avoid the visual hole. Elements - even buildings - are hidden by highway=pedestrian, but it may or may not be intended. Should an element override the highway=pedestrian container?
(24 Apr '17, 14:47)
The RedBurn
I think areas tagged with only amenity=fountain don't get a fill, they still just render with the fountain icon? Therefore if you create a fountain as an inner multipolygon of another area, it just cuts a hole in that area's rendering.
(24 Apr '17, 15:24)
neuhausr
2
This is a good question. I guess this depends on the size of the fountain. It if is a really large one (i.e. diameter > 20 m which seems to be true in your case) then it can be mapped as an own area. However I'm unsure if it is a good idea to exclude it from the pedestrian area. I wouldn't remove it from a leisure=park area however a pedestrian area might be different due to routing. Maybe this comes down to the question if routing engines capable of performing area routing are able to avoid this obstacle? Looks like I can't give a good advice here.
(24 Apr '17, 15:30)
scai ♦
1
These areas have just a line on the edge, like (http://www.openstreetmap.org/#map=19/50.64490/5.57321). After the edit of mmahmud, I'm thinking that the highway=pedestrian shouldn't be opaque, which would explain why the fountain looked like a hole.
(24 Apr '17, 19:35)
The RedBurn
|
|
It appears like this to me ... seems ok with fountain seen, although with the highway number and one-way arrows... not perfect, but passable for me.
I've added a screenshot. Did you look at that part of the map earlier and have still an old version in your cache? Or maybe is it that the map wasn't updated yet at all zoom levels. Anyway, your screenshot is how it was before creating the multipolygon.
(24 Apr '17, 14:06)
The RedBurn
Yes, I just refreshed again and it still the same....interesting that we see it quite differently. Same on Firefox, Safari and Cliqz for me. Old image could be fed from my service provider I suppose?
(24 Apr '17, 14:16)
nevw
1
I guess the cache depends of the server you get the map from, and yours is still behind, probably because the edit didn't come from the same server.
(24 Apr '17, 14:20)
The RedBurn
|
|
Hi, I think this is rendering correctly as it is showing the tunnel below with dotted lines and fountain in the middle with the pedestrian road around it. I used Layer = 1 on both the pedestrian road and fountain. But another thing, there is already a residential road drawn, is it necessary to draw the pedestrian one additionally or is it a separate road?
1
It's a plaza (https://wiki.openstreetmap.org/wiki/Tag:highway=pedestrian#Plazas), so the whole area can be walked on except where the fountain is. So I think that the right way to map it is to use a polygon with area=yes. But your edit made me understand that the highway=pedestrian shouldn't be opaque, the road below it should be visible and that may explain why the fountain looked like a hole.
(24 Apr '17, 19:16)
The RedBurn
Remember, the data is related to, but separate from, the rendering. It is most important to make sure the data is tagged correctly. If you don't like the rendering of the data, you can take that up with the renderer (in this case OSM Carto https://github.com/gravitystorm/openstreetmap-carto). Really, the same rendering issues exist with the park and footways to the west and the underground road.
(24 Apr '17, 19:51)
neuhausr
|
