Scenario-generation using survey persons is now possible. Also working for multiple ids'.
regionType as an attribute in SurveyPersons should be reconsidered. Instead of streaming the SurveyDataContainer for persons from matching regionTypes we could create multiple containers when creating scenarios where the ids' aren't of the sam regionType.
Instead of DatabaseReader.readPopulationFromDatabase() we could access the population data in a Task since the method is not mandatory for the generation of a scenario. To do this the DatabaseTask needs access to the scenario and the configuration though.
Scenario-generation using survey persons is now possible. Also working for multiple ids'.
regionType as an attribute in SurveyPersons should be reconsidered. Instead of streaming the SurveyDataContainer for persons from matching regionTypes we could create multiple containers when creating scenarios where the ids' aren't of the sam regionType.
Instead of DatabaseReader.readPopulationFromDatabase() we could access the population data in a Task since the method is not mandatory for the generation of a scenario. To do this the DatabaseTask needs access to the scenario and the configuration though.