faq 109055091

In the Matsim Evacuation extension 0.9.0, how to use predifined shapefiles for the evacuation area and the evacuation demand?

by dieynaba on 2017-04-21 08:21:46

---

I would to use the Matsim evacuation extension to simulate an evacuation in a region threatened with dam break flood. I already have one shape file containing the information on the size and the distribution of the population at risk in the building polygons, and one shape file corresponding to the area of the evacuation area. I would like to use them instead of producing them with the help of the scenario manager, that would only give an approximated solution.

Does anybody know how could I do it? 

---

Comments: 3

---

Re: In the Matsim Evacuation extension 0.9.0, how to use predifined shapefiles for the evacuation area and the evacuation demand?

by Gregor Lämmel on 2017-04-21 08:43:35

Dear Dieynaba,

The use of custom shape files is not directly supported, however with some manual adjustments you can do it.

Proceed as follows.

1. Open the tool and define an evacuation scenario for the approximately location you intent to evacuate
   1. Define configuration and save config file
   2. Define approximately evacuation and save evacuation area file
   3. Define approximately population and save population file
   4. exit tool
2. Thus far the tool has created two shape files (population.shp and area.shp) those files have to be replaced by you custom shape files
   1. Inspect population.shp (area.shp) and make sure that your custom files follow the same convention (attributes etc.) and also make sure that your custom shape files are in the same coordinate system (probably WGS84) as the files created by the tool (transform if needed).
   2. Replace population.shp and area.shp (and obviously all the other files like population.dbf ...) with you custom files
3. Open the evacuation tool again
   1. Load the existing config instead of creating a new one
   2. Skip evacuation area definition
   3. Skip population definition
   4. Create scenario
   5. Run scenario

Good luck 

Gregor

---

Re: In the Matsim Evacuation extension 0.9.0, how to use predifined shapefiles for the evacuation area and the evacuation demand?

by dieynaba on 2017-04-21 13:49:55

Dear Mr. Lämmel,

Thank you very much for your answer.

I have applied your instructions, however it doesn't work. I have adapted the attribute as well as the coordinate system for the 2 shape files. But when I save them, they do not generate any .fix file that appears in the test shape files. Should the .fix file should be also adapted to my predifined shape file? Could my problem come from this? If yes, how could I generate this .fix file using qgis?

---

Re: In the Matsim Evacuation extension 0.9.0, how to use predifined shapefiles for the evacuation area and the evacuation demand?

by dieynaba on 2017-04-21 15:57:49

I have checked my custom shape files and their feature types are corresponding to the one generated by the evacuation scenario.

After defining the scenario configuration I get the following errors :

2017-04-21 17:06:26,433  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:06:26,856  INFO Logger:? dataFileCache open start
2017-04-21 17:06:27,122  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:06:27,376  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:06:27,380  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:06:27,395  WARN OsmNetworkReader:188 No hierarchy layer specified. Will convert every highway specified by setHighwayDefaults.

...

2017-04-21 17:06:29,029  WARN LinkImpl:140 [permlanes=0.5 of link id 10110 may cause problems]
2017-04-21 17:06:29,029  WARN LinkImpl:142  Future occurences of this logging statement are suppressed.

...
2017-04-21 17:15:37,210  WARN ShapeFileReader:151 Unsafe method! store.dispose() is not called from within this method
2017-04-21 17:15:37,669  INFO ShapeFileReader:97 features to read #1
2017-04-21 17:15:37,678  INFO Counter:61 features read #1
2017-04-21 17:15:37,699  INFO Counter:67 features read #1
2017-04-21 17:15:37,700  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:15:41,485  WARN ShapeFileReader:151 Unsafe method! store.dispose() is not called from within this method
2017-04-21 17:15:41,494  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:15:41,495  WARN ShapeFileReader:151 Unsafe method! store.dispose() is not called from within this method

...
2017-04-21 17:15:41,601  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).


Then, when I have checked the evacuation area, as well as the evacuation demand tabs the shape files are correctly implemented according to the vizualiser, except that the density indicated in the population column is set to 100 for each building polygon, whereas it was defined differently in the predefined shapefile.  

Once I run the scenario conversion to Matsim, I get the following error messages :

2017-04-21 17:25:16,855  WARN ShapeFileReader:151 Unsafe method! store.dispose() is not called from within this method
2017-04-21 17:25:16,864  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).
2017-04-21 17:25:16,864  WARN MGC:174 Assuming that coordinates are in longitude first notation, i.e. (longitude, latitude).

...
2017-04-21 17:25:16,903  WARN OsmNetworkReader:188 No hierarchy layer specified. Will convert every highway specified by setHighwayDefaults.

...
2017-04-21 17:25:18,345  WARN ShapeFileReader:151 Unsafe method! store.dispose() is not called from within this method

...
2017-04-21 17:27:14,885  WARN LinkImpl:149 [length=0.0 of link id dummy3321 may cause problems]
2017-04-21 17:27:14,885  WARN LinkImpl:151  Future occurences of this logging statement are suppressed.
2017-04-21 17:27:14,888  WARN LinkImpl:108 [from=to=[id=en2][coord=[x=425376.41478337353][y=5129758.21356319]] [type=null][nof_inlinks=1][nof_outlinks=3321] link is a loop]
2017-04-21 17:27:14,889  WARN LinkImpl:110  Future occurences of this logging statement are suppressed.
2017-04-21 17:27:14,891  WARN NodeImpl:87 [id=en2][coord=[x=425376.41478337353][y=5129758.21356319]] [type=null][nof_inlinks=1][nof_outlinks=3322][inlink_id=dummy3321 is now in- and out-link]
2017-04-21 17:27:14,891  WARN NodeImpl:88  This message given only once.

...
2017-04-21 17:27:14,944  WARN ShapeFileReader:151 Unsafe method! store.dispose() is not called from within this method

...
WARN ControlerConfigGroup:326 setting overwriting behavior to overwriteExistingFiles
2017-04-21 17:27:15,168  WARN ControlerConfigGroup:327 this is not recommended, as it might result in a directory containing output from several model runs
2017-04-21 17:27:15,168  WARN ControlerConfigGroup:328 prefer the options deleteDirectoryIfExists or failIfDirectoryExists

...
2017-04-21 17:27:15,171  WARN PlanCalcScoreConfigGroup$ReflectiveDelegate:1252 Setting pathSizeLogitBeta different from zero is experimental.  KN, Sep'08


By finally running the simulation I get the following messages :

2017-04-21 17:33:59,391  WARN ModeStatsControlerListener:185 about to add the following series:
2017-04-21 17:33:59,391  WARN ModeStatsControlerListener:187 0 -- 0.0
2017-04-21 17:33:59,391  WARN ModeStatsControlerListener:187 1 -- 0.0
2017-04-21 17:33:59,393  WARN ModeStatsControlerListener:187 2 -- 0.0
2017-04-21 17:33:59,394  WARN ModeStatsControlerListener:187 3 -- 0.0
2017-04-21 17:33:59,394  WARN ModeStatsControlerListener:187 4 -- 0.0
2017-04-21 17:33:59,394  WARN ModeStatsControlerListener:185 about to add the following series:
2017-04-21 17:33:59,395  WARN ModeStatsControlerListener:187 0 -- 0.0
2017-04-21 17:33:59,395  WARN ModeStatsControlerListener:187 1 -- 0.0
2017-04-21 17:33:59,396  WARN ModeStatsControlerListener:187 2 -- 0.0
2017-04-21 17:33:59,396  WARN ModeStatsControlerListener:187 3 -- 0.0
2017-04-21 17:33:59,396  WARN ModeStatsControlerListener:187 4 -- 0.0
2017-04-21 17:33:59,397  WARN ModeStatsControlerListener:185 about to add the following series:
2017-04-21 17:33:59,397  WARN ModeStatsControlerListener:187 0 -- 0.0
2017-04-21 17:33:59,397  WARN ModeStatsControlerListener:187 1 -- 0.0
2017-04-21 17:33:59,398  WARN ModeStatsControlerListener:187 2 -- 0.0
2017-04-21 17:33:59,398  WARN ModeStatsControlerListener:187 3 -- 0.0
2017-04-21 17:33:59,398  WARN ModeStatsControlerListener:187 4 -- 0.0

...


And in the analysis tab, there is no evacuation curve appearing.