-
Notifications
You must be signed in to change notification settings - Fork 24
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
Germany sources and zenodo #27
Comments
Thanks for highlighting these issues. Upon verification of the links, it seems like they have indeed all been overwritten with 2023's data. For Lower Saxony they did replace the attribute KULTURCODE with NC_FESTG, you can find the mapping file under [Verzeichnis Nutzungscodes - Download (XLSX, 0,26 MB)] (https://www.sla.niedersachsen.de/download/193947/Verzeichnis_Nutzungscodes.xlsx)https://www.sla.niedersachsen.de/andi/downloads/dokumente-und-formulare-169962.html). As for Brandenburg, we hope to release the mapped files this year on zenodo. |
Edit: Oh, I just realized, that this is in progress #23 I should probably wait until it is done, as you indicated, that you are currently re-structuring the entire project. |
Nordrhein-Westfalen is also publishing historical dataset, which currently contains years 2019, 2020, 2021, and 2022 🥳 |
Brandenburg is now live on zenodo along with the new mapping files :) |
Hi, thanks for doing this, your repo is amazing!
Couple of questions with regard to Germany.
Lower saxony, the "Data Source: LEA-Portal" link does not lead to 2021 data, but that website contains 2023 data (and 2022, hidden), albeit without the KULTURCODE attributes. These collections have an attribute NC_FESTG, which from a superficial analysis looks to be the same as CODE attribute in 2021 dataset.
North Rhine Westphalia, the data.europa link does not lead to 2021 data, but rather to 2023. Do they overwrite that file 🤔
Brandenburg, data link also leads to 2023 data, seems to be overwritten? Also, any reason what Branderburg is not on zenodo?
Thanks!
The text was updated successfully, but these errors were encountered: