SUMO
Simulation of Urban MObility

- Home
- Download
- Documentation
- Wiki
- Trac
- Blog
- Contact
- SF-Project

# Networks/Further Outputs

NETCONVERT, NETGENERATE, and NETEDIT allow to generate additional output files besides writing a SUMO network file. They will be presented in the following.

# Writing/Exporting Networks

If no other output option is given, NETCONVERT and NETGENERATE will write the result of network import/generation as a SUMO network file into "net.net.xml". Otherwise the specified output will be generated.

Currently, the applications allow to write networks in the following formats:

- SUMO road networks
- plain XML definitions, as described in Networks/Building Networks from own XML-descriptions
- MATsim networks

## SUMO Road Networks

This is the default output format, see above. The name of the file to write the network into can be given using the option --output-file <FILE>. --sumo-output <FILE> and --output <FILE> are synonymes.

## Plain XML Output

Parsed node and edge definitions may be saved into a XML-files which have the same formats as the ones used for importing XML-networks (as described in Node Descriptions and Edge Descriptions). This shall ease processing of networks read from other formats than XML. The option --plain-output <FILE> forces NETCONVERT and NETGENERATE to generate a file named "<FILE>.nod.xml" which contains the previously imported nodes, a file named "<FILE>.edg.xml" which contains the previously imported edges, and a file named "<FILE>.con.xml" which contains the previously imported connections. The edge file will contain the list of previously read edges and each edge will have the information about the edge's id, the allowed velocity, the number of lanes, and the from/to - nodes stored. Geometry information is stored only if the imported edge has a shape, meaning that it is not only a straight connection between the from/to-nodes. The lane spread type and the basic edge type are only saved if differing from defaults ("right" and "normal", respectively). Additionally, if one of the lanes prohibits/allows vehicle classes, this information is saved, too (see also "Defining allowed Vehicle Types").

## MATsim Road Networks

To write the imported/generated network as a MATsim file, use the option --matsim-output <FILE>. The extension for MATsim networks is usually ".xml".

Please note that the capacity is computed by multiplying an edge's lane number with the capacity norm:

    MAXIMUM_FLOW = LANE_NUMBER * CAPACITY_NORM

The value of CAPACITY_NORM is controlled via the option --capacity-norm <FLOAT> (default: 1800).

## openDRIVE Road Networks

To write the imported/generated network as a openDRIVE file, use the option --opendrive-output <FILE>. The extension for openDRIVE networks is usually ".xodr".

Some notes:

- The feature is currently under implementation
- road - the normal ones
  - the type is always set to "town" for the complete street
  - link
    - The road is always connected to the nodes it is outgoing (predecessor) / incoming (successor) from/to
  - planView
    - the geometry is given as lines only
  - no road widenings are modeled - if the number of lanes changes, the road changes
  - elevationProfile and lateralProfile do not contain relevant information
  - the roads are always unidirectional, this means only the center lane and the right lanes are given
  - objects and signals do not contain relevant information

# Further Outputs

## Information about Geometry Removal

The option --map-output <FILE> (or -M <FILE> for short) generates a file which contains the information about which edges have been joined (see chapter "Removing Geometry Nodes").

The format is a little bit strange and should be reworked in the next time. At the begin of each line of the generated file, you will find the id of an edge from the generated network. Then, divided by tabs, you will find the list of edge ids together with the corresponding edges' lengths, the edge consists of. The id is divided from the length by a ':'. This means if that an edge that was joined from the edges 'edge1', 'edge2', 'edge3', each having the length 10, 20, and 30m, respectively, it would appear in the file encoded as following:

    edge1<TAB>edge1:10<TAB>edge2:20<TAB>edge3:30

If the edge was not build by joining other edges, the list of edge ids/length will have only one value, of course:

    edge<TAB>edge:100

This page was last modified on 25 September 2012, at 09:49.