search

InnoZ / MAS

analysis and (potentially) development of a multi-agent simultation for carsharing
Apache License 2.0
0 stars 0 forks source link

BBSR data doesn't cover all of Germany #63

Closed wese-da closed 7 years ago

wese-da commented 7 years ago

This problem occurred before (e.g. during the Ril-Project with DB S&S): Some German districts like "Mecklenburgische Seenplatte" aren't contained in the BBSR region type data. Perspectively this should be fixed by anyone who feels responsible...

bsmoehring commented 7 years ago

I'm not sure if we're talking about the population data i uploaded. The BBSR forecast uses old districts boundaries from before the 'Kreisgebietsreform Mecklenburg-Vorpommern' in 2011. 'Mecklenburgische Seenplatte' formerly existed as -Neubrandenburg, -Landkreis Müritz, -Landkreis Mecklenburg-Strelitz; -Landkreis Demmin Shall I try to merge them?

00Bock commented 7 years ago

what is a clever way of doing so?

bsmoehring commented 7 years ago

-check if all new districts are aggregates of the old boundaries. if a former district was split into two new districts this might require further bbsr information.

-summarize the old district's population by agegroup and insert the new ones. i will chek if I can do this with a 'simple' sql statement

-delete the old ones if we don't need them, so that the aggregates (e.g. population of germany in 2020) are still valid

wese-da commented 7 years ago

@bsmoehring This issue actually wasn't about your population data, rather about the region type data provided by the BBSR see here.

But you have a point... The population data should be affected too

EDIT: There are newer versions of the region types tables on the BBSR website, so the first point should be fixed easily by just overwriting the bbsr.regiontypes table in geodata.

00Bock commented 7 years ago

let's deal with it when we have the first automated model generation process...