Difference between revisions of "Tutorials/PT from OpenStreetMap"

From Sumo
Jump to: navigation, search
(Created page with "This tutorial shows you how to build a public transit (PT) simulation scenario from scratch using an OpenStreetMap file as the only input. If you are new to OpenStreetMap...")
 
Line 1: Line 1:
 
This tutorial shows you how to build a public transit (PT) simulation scenario from scratch using an  [[OpenStreetMap file]] as the only input. If you are new to OpenStreetMap in conjunction with SUMO you will also find the [[Tutorials/Import_from_OpenStreetMap | OSM]] tutorial helpful.
 
This tutorial shows you how to build a public transit (PT) simulation scenario from scratch using an  [[OpenStreetMap file]] as the only input. If you are new to OpenStreetMap in conjunction with SUMO you will also find the [[Tutorials/Import_from_OpenStreetMap | OSM]] tutorial helpful.
  
The creation of PT simulation consists of three steps:
+
The creation of PT simulation consists of two steps:
 
# Initial network and public transit information extraction
 
# Initial network and public transit information extraction
# Finding feasible stop-to-stop travel times
+
# Finding feasible stop-to-stop travel times and creating PT schedules
# Creating the PT schedule
+
 
  
 
== Initial network and public transit information extraction ==
 
== Initial network and public transit information extraction ==
Line 16: Line 16:
 
* ''--ptstop-output additional.xml'' points to the to-be-generated [[Simulation/Public_Transport | PT stop file]]
 
* ''--ptstop-output additional.xml'' points to the to-be-generated [[Simulation/Public_Transport | PT stop file]]
 
* ''--ptline-output ptlines.xml'' points to an intermediate file defining the PT lines.
 
* ''--ptline-output ptlines.xml'' points to an intermediate file defining the PT lines.
 +
 +
== Finding feasible stop-to-stop travel times and creating PT schedules ==
 +
The second step is to run a python script that performs the following:
 +
# To determine feasible stop-to-stop travel times, a simulation run is performed with one PT vehicle for each PT line.
 +
# The PT schedule (regular interval timetable) for all lines is created from the stop-to-stop travel time information.
 +
The stop-to-stop travel times are determined on an empty network. It will be straightforward to extend the script so the stop-to-stop travel times a determined for an existing transport model. This, however, is beyond the scope of this tutorial. The steps are performed by invoking the ''ptlines2flows.py'' script as follows
 +
  ptlines2flows.py -n net.net.xml -s additional.xml -l ptlines.xml -f flows.rou.xml -p 600
 +
, where
 +
* ''-n net.net.xml'' points to the SUMO network previously created with netconvert
 +
* ''-s additional.xml'' points to the PT stop file created with netconvert
 +
* ''-l ptlines.xml'' points to the PT lines definition file created with netconvert
 +
* "-f flows.rou.xml'' points to the to-be-generated [[Definition_of_Vehicles,_Vehicle_Types,_and_Routes | route]] files for the PT vehicles
 +
* "-p 600" is the period for the regular interval time table

Revision as of 15:39, 24 July 2017

This tutorial shows you how to build a public transit (PT) simulation scenario from scratch using an OpenStreetMap file as the only input. If you are new to OpenStreetMap in conjunction with SUMO you will also find the OSM tutorial helpful.

The creation of PT simulation consists of two steps:

  1. Initial network and public transit information extraction
  2. Finding feasible stop-to-stop travel times and creating PT schedules


Initial network and public transit information extraction

In the first step PT stops and line information will be extracted. The step is performed by invoking netconvert as follows

 netconvert --osm-files osm.xml -o net.net.xml --osm.stop-output.length 20 --ptstop-output additional.xml --ptline-output ptlines.xml

, where

  • --osm-files osm.xml points to the OpenStreetMap file
  • -o net.net.xml points to the to-be-generated SUMO network file
  • --osm.stop-output.length 20 defines the length of the PT stop platforms in meter
  • --ptstop-output additional.xml points to the to-be-generated PT stop file
  • --ptline-output ptlines.xml points to an intermediate file defining the PT lines.

Finding feasible stop-to-stop travel times and creating PT schedules

The second step is to run a python script that performs the following:

  1. To determine feasible stop-to-stop travel times, a simulation run is performed with one PT vehicle for each PT line.
  2. The PT schedule (regular interval timetable) for all lines is created from the stop-to-stop travel time information.

The stop-to-stop travel times are determined on an empty network. It will be straightforward to extend the script so the stop-to-stop travel times a determined for an existing transport model. This, however, is beyond the scope of this tutorial. The steps are performed by invoking the ptlines2flows.py script as follows

 ptlines2flows.py -n net.net.xml -s additional.xml -l ptlines.xml -f flows.rou.xml -p 600

, where

  • -n net.net.xml points to the SUMO network previously created with netconvert
  • -s additional.xml points to the PT stop file created with netconvert
  • -l ptlines.xml points to the PT lines definition file created with netconvert
  • "-f flows.rou.xml points to the to-be-generated route files for the PT vehicles
  • "-p 600" is the period for the regular interval time table