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

Re-create and validate post-merger muncipial spatial data #4

Open
mhermans opened this issue Oct 8, 2020 · 1 comment
Open

Re-create and validate post-merger muncipial spatial data #4

mhermans opened this issue Oct 8, 2020 · 1 comment
Assignees

Comments

@mhermans
Copy link

mhermans commented Oct 8, 2020

From:

"15 Vlaamse gemeenten hebben formeel hun intentie kenbaar gemaakt om op 1 januari 2019 te fuseren. Statbel heeft aan deze nieuwe gemeenten nieuwe NIS-codes toegekend vanaf 01/01/2019."

This is also reflected in new NIS-codes (valid/used from 2019-01-01) and NUTS-codes: "De nieuwe NUTS-codes zullen worden gebruikt om vanaf 2021 officiële statistieken op EU-niveau te produceren (de NUTS-codes kunnen slechts om de drie jaar officieel worden aangepast). De nieuwe NUTS-codes zullen echter worden opgenomen in de attributententabel van de statistische sectoren"

Muncipial and higher-level spatial files will need to be re-generated, and checked if all NIS, NUTS, etc. codes are valid. Need to double-check the mapping with sector-identifiers (issue #5 ), but atm. I don't think there will be an obstacle (aggregation step of sectors gives proper number of muncipalities, 581).

Open question is how this package should deal with historical spatial data.

@mhermans mhermans self-assigned this Oct 8, 2020
@jwijffels
Copy link
Contributor

maybe create a function be_spatial(type = "municipality", clean_names = TRUE, format = "sf") which then pulls either the data from the inst folder as sf or sp objects or downloads them if they are not in the inst folder and applies your cleaning of names.

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