https://github.com/osplanning-data-standards/dyno-demand

Demand format suitable for dynamic network models
https://github.com/osplanning-data-standards/dyno-demand

Last synced: about 2 months ago
JSON representation

Demand format suitable for dynamic network models

• Host: GitHub
• URL: https://github.com/osplanning-data-standards/dyno-demand
• Owner: osplanning-data-standards
• License: apache-2.0
• Created: 2015-10-22T19:30:44.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2018-07-02T17:46:49.000Z (almost 6 years ago)
• Last Synced: 2024-02-08T02:35:42.152Z (5 months ago)
• Size: 13.7 KB
• Stars: 2
• Watchers: 4
• Forks: 4
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-transit - Dyno-Demand - A GTFS-based travel demand data format focusing on individual passenger *demand* suitable for dynamic network modeling developed by San Francisco County Transportation Authority, LMZ LLC, and UrbanLabs LLC. (Uncategorized / Uncategorized)
• awesome-transit - Dyno-Demand - A GTFS-based travel demand data format focusing on individual passenger *demand* suitable for dynamic network modeling developed by San Francisco County Transportation Authority, LMZ LLC, and UrbanLabs LLC. (Uncategorized / Uncategorized)

README

        

## Dyno-Demand

A travel demand data standard suitable for dynamic network 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)  

[issues]: https://github.com/osplanning-data-standards/dyno-demand/issues

[repo]: https://github.com/osplanning-data-standards/dyno-demand

NOTE: This is a draft specification and still under development. If you have comments

or suggestions please file them in the [issue tracker][issues]. If you have

explicit changes please fork the [git repo][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](http://fast-trips.mtc.ca.gov/library/)  

# 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`](/files/trip_list.md)	| Trip attributes													

A Dyno-Demand dataset MAY include the following files:

Filename 								| Description										

----------								| -------------		

[`person.txt`](/files/person.md)		| Person attributes

[`household.txt`](/files/household.md)	| Household attributes