Dyno-Demand

A GTFS-based data transit network data standard suitable for dynamic transit modeling.

version: 0.1.2 updated: 15 August 2016
created: 17 June 2015
authors:

• Bhargava Sana (San Francisco County Transportation Authority)
• Lisa Zorn (LMZ LLC)
• Elizabeth Sall (UrbanLabs LLC)

NOTE: This is a draft specification and still under development. If you have comments or suggestions please file them in the issue tracker. If you have explicit changes please fork the git repo and submit a pull request.

Changelog

• 0.1.2: renames p-trip_id and p-tour_id to use underscores rather than hyphens
• 0.1.1: adds mandatory person trip id: p-trip_id to the trip_list and optional tour id: p-tour_id
• 0.1.0: initial commit; Technical Memo Documentation

Known Issues

• Trips currently do not relate to tours or trip chains. Since this is not currently a capability in the dynamic transit model Fast-Trips for which this format was designed, this is not deemed an immediate issue that needs resolution.

Specification

A Dyno-Demand dataset consists of required and optional data files that together describe the demand for transportation.

A Dyno-Demand dataset MUST include the following files:

Filename	Description
trip_list.txt	Trip attributes

A Dyno-Demand dataset MAY include the following files:

Filename	Description
person.txt	Person attributes
household.txt	Household attributes