Code Officiel Géographique 2019 #4
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
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.
Nous étions à jour des communes 2019 depuis mi-janvier, mais le nouveau Code Officiel Géographique 2019 apporte beaucoup de changements.
Cette PR permet donc de se baser sur le COG 2019 plutôt que sur le COG 2018 avec Table de passage 2019.
Elle apporte un fichier historique des communes, et un fichier des communes différent.
Les communes périmées ne sont plus présentes dans le fichier des communes.
À l'inverse, plusieurs entrées avec le même code peuvent coexister lorsqu'une commune nouvelle a sa commune chef-lieu qui est déléguée.