Change OSM column names formatting #733
Merged
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
…el. Column names are escaped Add a test to check if the osm tag table exists before running the script to build the corresponding layers : line, polygon...
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 PR changes the OSM column names formatting to keep the original OSM case.
e.g : "BUILDING:LEVEL" replaced by ""building:level""
So we can for example reuse some SQL queries provided by the OSM tool ecosystem as geovelo :
https://gitlab.com/geovelo-public/requetes_amenagements_cyclables/-/blob/master/Bandes_cyclables-1xD.sql
This PR fixes also a bug on BDTopo workflow when the user set multiple location codes.