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

Features should be taggable as underground, at level, or elevated #133

Open
BrunoSalerno opened this issue May 22, 2018 · 2 comments
Open

Comments

@BrunoSalerno
Copy link
Member

And this should be represented in the map

@Kalepom
Copy link
Contributor

Kalepom commented Sep 22, 2018

When imported from OSM, this info is set with the tunnel tag

@BrunoSalerno
Copy link
Member Author

BrunoSalerno commented Mar 31, 2019

This could be a little bit more complex: Tracks could be at level ...-2, -1, 0, 1, 2... If level == 0, it means that it is at ground level; if it is = 1, it is elevated. If it is < 0, it's underground. This value should be used to set the rendering order of the lines (with an order bystatements in the feature_collection query).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants