Introduce 'other' rank for address rank 0 objects #808
Conversation
This file contains 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
In order to get an address, a feature needs to have a named rank. Mixing rank 0 objects with other address ranks seems wrong, so give it its own named rank instead. This slightly changes the output of these features. They now get type=other instead of type=locality.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the issue that non-addressable features wouldn't be assigned any address items.
In order to get an address, a feature needs to have a named rank. Mixing rank 0 objects with other address ranks seems wrong, so give it its own named rank instead. This slightly changes the output of these features. They now get
type=otherinstead oftype=locality.