Skip to content

Latest commit

 

History

History
168 lines (123 loc) · 9.91 KB

README.md

File metadata and controls

168 lines (123 loc) · 9.91 KB

GMNS-AMS Traffic Network Modeling

Introduction

GMNS: The General Modeling Network Specification (GMNS) defines a common human and machine-readable format for sharing routable road network files. It is designed to be used in multi-modal static and dynamic transportation planning and operations models.

AMS: The objective of the AMS data hub is to define a prototype of operations and associated requirements that will allow for the effective integration of analysis modeling and simulation tools across various domains and scales. Easily exchange information and data at both the input and output levels.

The ASU Trans + AI Lab devotes to developing a better AMS data hub framework and a set of integrated open-source transportation tools. The objective of the repository is to aggregate the developed software as a systematic modeling flow and demonstrate its sequential steps, so call “7-steps modeling”. However, the modeling flow is not limited to seven steps. The advanced software under development are CGLite and Data2VDF for the traffic demand and supply calibration. The repository will continue to be updated. Meanwhile, the team also collaborates with other development teams to improve integration and modeling accuracy.

The continuous flow of GMNS-AMS modeling:

Step Description Software Input Files Output Files
0 OSM data download Open Street Map(OSM) - - Map.osm
1 Convert OSM data to GMNS OSM2GMNS Map.osm Node.csv, Link.csv, poi.csv
2 Convert GTFS data to GMNS GTFS2GMNS Open transit data GTFS Node.csv, Link.csv, poi.csv
3 Expand macroscopic network data to micro, meso net2cell Node.csv, Link.csv Meso and micro networks in node.csv and link.csv
4 Zone-to-zone travel demand grid2demand Node.csv, Link.csv, Poi.csv, Poi_trip_rate.csv Demand.csv, Zone.csv, Accessibility.csv, Input_agent.csv
5 Traffic signal for timing Data2timing (In development), Sigma-X Node.csv, Link.csv, Movement.csv Timing.csv
6 Capacity estimation and VDF calibration Data2vdf link_performance.csv vdf_table.csv link.csv
7 AMS simulation A/B Street, Path2GMNS DTALite Demand.csv, Node.csv, Link.csv, Input_agent.csv Agent.csv, Link_performance.csv
8 OD Matrix estimation Data2demand link_performance.csv Agent.csv Demand.csv,
9 Visualization QGIS, [NeXTA]https://github.com/asu-trans-ai-lab/NeXTA4GMNS) Node.csv, Link.csv, Movement.csv, Zone.csv, Demand.csv - -

Step 0: Download Map File

Open Street Map (OSM) provides a free editable map of the world, which accords with the ASU team's objective of developing open-source tools for traffic network modeling. The open street website allows adjusting and directly downloading the OSM data file. The data file is the basic input for the GMNS-AMS modeling flow.

The interface of OSM:

Step 1: OSM2GMNS

Converting OSM data to GMNS (General Modeling Network Specification) format is the first step of 7-steps modeling demonstration. The unified specification is cardinal for the effective integration of analysis in the GMNS-AMS modeling. The GMNS data is stored and represented in CSV file as the modeling input and output.

The outputs of OSM2GMNS (nodes, links and poi):

Step 2: GTFS2GMNS

The public transit agencies publish the open public transit data in GTFS (General Transit Feed Specification) format. Like OSM2GMNS, the step aims to convert the GTFS data for further application in the AMS data hub. The required files of GTFS2GMNS are stop.txt, route.txt, trip.txt, stop_times.txt in the GTFS data package.

Step 3: net2cell

The net2cell is an open-source tool for expanding GMNS macro-network to mesoscopic and microscopic resolution. It aims to unify transportation modeling data in the same format for the more effective integration of analysis modeling and simulation across resolutions.

The analysis tools of different resolution networks are as follows:

  • Micro: These models are generally simulation-based and effective in replicating individual driver behavior, complex geometric configurations, and advanced features of traffic control devices.

  • Macro: These include sketch-planning tools, regional/statewide TDMs, macroscopic simulation models, regional air quality models, freight models, etc.

  • Meso: These include most DTA models and mesoscopic simulation models

The difference between macro and meso networks:

Mesco Marco

Step 4: Grid2demand

Grid2demand is a quick trip generation and distribution tool based on the trip generation and trip distribution methods of the standard 4-step travel model in transportation planning applications.

The four separate steps are described below.

  • Trip Generation: Estimate how many trips entering or leaving a traffic-analysis-zone (TAZ)

  • Trip Distribution: Estimate how many trips from each TAZ end in all TAZs through gravity model

  • Mode Choice: Estimate which travel-method is used (e.g., vehicle, transit, walk)

  • Traffic Assignment: Distribute vehicles/traffic flow to different paths during travel

The grid2demand is the succeeding step of OSM2GMNS, which generates zone-to-zone travel demand based on alphanumeric grid zones. Users can obtain the demand file within a few lines of python code

The visualization of zone-to-zone demand volume over the University of Washington:

Step 5: Signal2timing

Quick Estimation Method (QEM)based implementation, GMNS based traffic signal API for multi-resolution modeling. This tool aims to automate the process of optimizing movement-based, phase-based signal control strategy and provide the interfaces for AMS modeling.

The software package is still in development. The output is movement.csv and can be used in Sigma-X: an Excel-based Quick Estimation Method.

Step 6: Capacity estimation and VDF calibration

Calibrate hourly capacities for each facility type and area type and calibrate period capacity for each assignment periods (e.g. AM, PM, etc.). Calibrate coefficients in the volume delay function (e.g., the “alpha” and “beta” in the BPR function)

Step 7: AMS Simulation

A mesoscopic DTA engine called DTALite can be run directly within NeXTA. DTALite is a mesoscopic simulation-assignment framework that uses a computationally simple but theoretically rigorous traffic queuing model in its simulation engine. The DTALite can be executed after obtaining the demand file from grid2demand.

The ASU Trans+AI Lab collaborates with the development team of A/B Street closely for adapting the proposed AMS data hub framework and improve the software efficiency.

A/B Street:

Step 8: OD Matrix estimation (Data2Demand)

Derive the OD matrix from the observations of link counts or speed, as well as the candidate paths generated AMS simulation (i.e., path4gmns) using the customized computational graph developed using Tensorflow.

Step 9: Data Visualization.

Visualization is an increasingly important element of transportation analysis and is an integral part of any AMS data hub. The common visualization tools used in the 7 steps are QGIS and NeXTA.