Don't use elevation data directly for ways with cutting=*, location=underground or indoor=yes tags in the default mapper#6093
Merged
Conversation
3 tasks
Member
|
Does this solve your specific indoor mall problem? |
Member
Author
I think it fixes the original problem but not all problems. This is before: This is after: |
leonardehrenfried
approved these changes
Sep 27, 2024
flaktack
approved these changes
Oct 3, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Copies over the rules from Norway mapper for disabling the elevation usage for the for the following tag value combinations to the default mapper as well:
Issue
Related to #6092
Unit tests
Added some
Documentation
Not needed
Changelog
From title