generated on 2019-08-26 00:07:10.060274 from the wiki page for Tools/District for SUMO git

Transform districts into polygons for visualization in SUMO-GUI. Using the options --hue, --saturation, --brightness the colors can be controlled. Each of these options supports values from [0, 1] as well as the special value random.

<SUMO_HOME>/tools/ myDistricts.rou.xml
Only districts using the attribute edges are currently supported

Parsing a number of networks and taz (district) files with shapes this script writes a taz file with all the edges which are inside the relevant taz. The taz files must be in the format generated by POLYCONVERT.

 <SUMO_HOME>/tools/ -n -t myDistrictPolygons.add.xml

Call option --help for additional details.

Filter a taz (district) file using a network file and a vehicle class so that only edges which allow the given vehicle class are included in the taz definitions.

 <SUMO_HOME>/tools/district/ -n -t myDistricts.add.xml -o filteredDistricts.add.xml --vclass passenger

Call option --help for additional details.

Finds edges that are opposites of each other and puts them in a common district (TAZ). This can be used to improve routing in conjunction with trip attributes fromTaz and toTaz.


Call option --help for additional details.

Example usage

When applied to a typical OSM network, and edge and the edge with the negated id describe opposite direction edges of the same road. The generated bidi-taz would look like this:

 <taz id="-123" edges="-123 123"/>
 <taz id="123" edges="-123 123"/>

The <trip> definitions that would typically use attributes from and to instead use the attributes fromTaz and toTaz:

 <trip id="someTrip" from="123" to="456" depart="0"/>
 <trip id="someTripWithBidiTaz fromTaz="123" toTaz="456"/>

The second definition would allow departure from either edge 123' or -123 due to the way the taz 123 is definied. This can prevent unwanted turn-arounds and the beginning and end of generated trips and thus simplifies trips created from mapping of geo-coordinates.