Skip to content
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

Underground building parts sprouting like mushrooms at the Paris Opera #1304

Open
nvkelso opened this issue Jul 5, 2017 · 10 comments
Open

Comments

@nvkelso
Copy link
Member

nvkelso commented Jul 5, 2017

  • What did you see? Lots of random building boxes near Opera metro station in Paris.
  • What did you expect to see? Building boxes that are underground should generally be marked as such so the style can hide them. Looks like these are marked indoor=*, so maybe they shouldn't show up in the buildings layer at all?

See also:

screen shot 2017-07-05 at 10 08 54

screen shot 2017-07-05 at 10 20 11

@zerebubuth
Copy link
Member

One way of dealing with this is to parse the level tag (including the M;N syntax - perhaps take the max?) and assign location: underground when level < 0. That would allow existing processing to work on these features.

It's worth noting that the building:parts and highway=footways both have level tags, and looks worth doing the location: underground processing to both so that they can both be hidden. Otherwise, the footpaths look quite confusing and aren't useful for an above-ground traveller at all.

@nvkelso
Copy link
Member Author

nvkelso commented Jul 5, 2017

location: underground and layer: [-1, -2, -3, -4, -5] (not level) are probably conflated a bit in Mapzen house styles:

Right now we block rendering any underground building, but if we see it's level is negative we don't extrude it. That'll need to be re-evaluated.

(I favor marking any negative layer and any negative level as location: underground).

@nvkelso nvkelso added this to the v1.6.0 milestone Jul 5, 2017
@matkoniecz
Copy link
Contributor

Note that negative layer tag does not mean that object is underground.

(see http://wiki.openstreetmap.org/wiki/Key:layer - Things to avoid - Using negative values to describe something to be underground. Use location=underground for this purpose.)

@nvkelso
Copy link
Member Author

nvkelso commented Jul 18, 2017

@matkoniecz Thanks for the tip! There's quite a bit of funky data here so we need to balance preventing egregious rendering errors with showing original data.

@nvkelso nvkelso modified the milestones: v1.6.0, v1.7.0 Sep 25, 2018
@nvkelso
Copy link
Member Author

nvkelso commented Feb 13, 2019

Still a problem:

image

@nvkelso
Copy link
Member Author

nvkelso commented Feb 13, 2019

I think really this is a tagging issue upstream, closing.

@nvkelso nvkelso closed this as completed Feb 13, 2019
@zerebubuth
Copy link
Member

Looks like a lot of those underground buildings could have location=underground and we'd handle them better. Alternatively, perhaps we could be more robust to this sort of thing by inferring location=underground from the level tag being negative?

@nvkelso
Copy link
Member Author

nvkelso commented Feb 14, 2019

See #1304 (comment) – negative levels don't neccesarily mean underground. So instead of being clever suggest the data is cleaned up.

@zerebubuth
Copy link
Member

If I may be pedantic for a second; the wiki says that negative levels don't mean underground. However, that might have been the intent of the person who mapped those.

You are right, and we should "fix" the data to make it more consistent in its use of location=underground. If we find that this is a widespread problem outside Place de l'Opéra, then it might imply that, whatever the wiki says, in practice people are using negative levels to indicate underground-ness.

@nvkelso
Copy link
Member Author

nvkelso commented Feb 15, 2019

There's been enough discussion here to warrant reopening the issue (to be acted on at some later date)...

@nvkelso nvkelso reopened this Feb 15, 2019
@nvkelso nvkelso modified the milestones: v1.9.0, v2.0.0, v1.10.0 Feb 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants