-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building z-order broken? #1130
Comments
very similar to #688. |
Yes, it's duplicate. It's something that definitely needs to be looked at, but it's hard to get layering right in all circumstances. |
NP, sadly wasn't able to find the other issue. Please mark as dupe :) |
+1 Besides the inherent difficulties of the "3D" aspect rendered in 2D, I think people should be more aware of the great effort it already requires to make any sort of "logically" feeling rendering when it comes to layering different thematic layers of data. There is no good or bad, or correct or wrong, when we consider the translation of concrete objects in the real world, to a digital rendered map. _Everything_ is interpretation / choice by the style developer. Looking at this particular example, personally, I also see good reasons to keep rendering railway station buildings below tracks:
If the "roofed-over" aspect of some tracks needs to be visible, I think it would be better if Carto started support for rendering of the "building=roof" tag (for open sided roofs, like on many railway stations), or change the way it is currently rendered (I am not sure if it is, it doesn't seem so?). The images below, from my ArcGIS renderer, show some of the nice rendering that can be achieved by open hatches on this tag, in combination with railway stations: |
2014-11-14 10:24 GMT+01:00 Matthias Meißer notifications@github.com:
agree for the footway. The subway is inconsistent as it is not rendered IMHO (and usually) a dashed line is used to denote a feature that is behind |
I render all railway tunnels, including subway, as two thin parallel dashed lines on top of everything else. This corresponds with your view. I don't render underground buildings at all. I think they clutter up the map to much, and make the map really unreadable in some places. I filter them out by a query like this: (osm_level NOT LIKE ('%-%') OR osm_level IN (Null,'')) AND (osm_layer NOT LIKE ('%-%') OR osm_layer IN (Null,'')) AND osm_location NOT IN ('underground','underwater') The "osm_" prefix for the field names is something specific for the OpenStreetMap Editor for ArcGIS that I use in my ArcGIS renderer. Compare these two images for the difference, notice how the aboveground layout of the Rotterdam railway station is more clear without the underground facilities: |
2014-11-17 19:26 GMT+01:00 mboeringa notifications@github.com:
this way you'll also miss all overground buildings which happen to have |
BTW: If anybody says our tagging is incosistant and needs to be fixed (instead of the map style) I will do it with layer=* or level=* tags. |
2014-11-20 11:35 GMT+01:00 Matthias Meißer notifications@github.com:
no, the thing is more that there isn't a "right" or "wrong" and therefor no |
I wil consider this issue after the building colour change is rolled out. No need to change the tagging now I think. |
You're absolutely right regarding the "layer" key issue, and the significance and meaning of this key regarding z-position. However, there is a quite common (mal)practice of using the "layer" key instead of "level" or "location" to register the underground position, or maybe more correctly said the fact that some building (often underground), is below others, by setting layer at -1. Often, no level or location is additionally set (the malpractice, if I may use this word at all, is of course not so much setting layer=-1 on a building, but forgetting to set level or location where appropriate...). E.g., here in the Netherlands, it seems most subway stations only have "layer=-1" to signify their underground presence... no other keys to help out here. This seems more common unfortunately, also in other countries. E.g. see here, near Rotterdam Centraal station: While potentially erroneous, assuming buildings with layer=-1 are below ground, is the only way to get a decent rendering if you want to exclude subsurface structures. It wont be right in all cases, but more often than not it will. Considering probably 95-98% of all buildings on earth are currently not mapped in OSM, that is a risk I am willing to take... Anyway, my ArcGIS renderer will be customizable, so people can "fix" this to their liking once it is released. |
The main problem is that it encourages bad tagging. |
Using layer=-1 on a building is, by itself, not bad tagging, although most Wiki pages recommend using level to signify the position of a floor of a building relative to "ground floor". The main problem is not using location or level where appropriate. And using the layer tag on buildings is somehow suggested in specific cases in this other GitHub issue (see remarks by @dieterdreist and @Morphan): Problem with level is of course, what do you do with entirely underground buildings, that do not "start" at ground level? What level to tag on an underground building with just elevator access? Probably -1, but anyway... I guess the more generic "location=underground" may be more suitable to filter out underground structures... if it were tagged~! Anyway, personally, I think there are more pressing issues to worry about in the rendering arena... I also honestly don't think this will lead to massive bad tagging... most people at least attempt to do the right thing. |
2014-11-23 18:24 GMT+01:00 mboeringa notifications@github.com:
it is your own interpretation that "layer=-1" is used in these cases to |
Agree 100% with all you write, but I would just rephrase "it is your interpretation" into "it is your way of rendering / styling the data". I am fully aware this is an undesirable "shortcut", but it is one that will work in most cases, as most buildings having layer=-1 do seem to be underground. People are just unlikely to tag a building with -1 when it is in fact aboveground, simply because it "doesn't feel right". But I am the first to admit that additional tagging, preferably using the "location=underground" tag is highly desirable. Although the "level" key is less ambiguous than the "layer" key, it still is somewhat ambiguous as to whether something is aboveground or below. The "location" key, using actual tagging phrases with "underground"/"overground", seems to be most concise... But I am well aware there is a plethora of real world cases out there, with buildings having partly covered or artificial basements, that may make tagging what is "underground" actually not that straightforward as it may seem. Just look at something like the Van Gogh museum in Amsterdam: https://www.google.nl/maps/@52.3580451,4.8812186,286a,20y,90h/data=!3m1!1e3 The right modern half-"egg" shaped part, has a basement with an outside open air "floor" (that is the left part in the above image link), one level below what is generally considered "ground level"... |
2014-11-24 22:25 GMT+01:00 mboeringa notifications@github.com:
I also agree 100% with your text ;-) Seen from the (main) street you have the impression to see a modern temple |
Hi there,
I guess we've got a bug when we have buildings that contain other ways:
http://www.openstreetmap.org/#map=18/54.07835/12.13105&layers=N
As you see, the rails are above the buildings, even if they are in a tunnel and subways. Also the footways seem to be above the buildings while they are just within. IMHO the vizualisation was different / correctsome time ago :-/
The text was updated successfully, but these errors were encountered: