dyno-demand
Demand format
A standard for describing transportation demand in dynamic network models
Demand format suitable for dynamic network models
2 stars
4 watching
5 forks
last commit: over 7 years ago
Linked from 1 awesome list
Related projects:
| Repository | Description | Stars |
|---|---|---|
| osplanning-data-standards/dyno-path | Data standards for transit and passenger path data used in assignment output processing | 2 |
| osplanning-data-standards/gtfs-plus | Defines a data standard for dynamic transit modeling using GTFS-based data | 21 |
 zephyr-data-specs/gmns | Defines a common format for sharing routable road network files used in transportation planning and operations models. | 115 |
 apiaryio/mson | A Markdown syntax for describing data structures in JSON and related formats. | 902 |
| osplanning-data-standards/gtfs-stat | A data standard extension to the GTFS transit network protocol for storing performance metrics and statistics. | 4 |
 ndjson/ndjson-spec | Defines a standard for transporting JSON data in stream protocols | 688 |
 adulau/pdns-qof | Defines a common output format for passive DNS queries | 36 |
 google/transit | A standardized format for distributing transit system data to software applications | 625 |
 mobilitydata/gtfs-flex | A proposed specification for adding demand-responsive transportation services to public transit data formats | 119 |
 ontola/hextuples | A data serialization format designed for performance in the browser | 31 |
 mario-campos/dyndnsd | A dynamic DNS daemon written in C for the OpenBSD operating system. | 21 |
 openmobilityfoundation/mobility-data-specification | Enables standardized communication and data-sharing between cities and mobility providers. | 692 |
 gsoh/ved | A large-scale dataset capturing vehicle energy consumption and usage patterns in real-world driving scenarios. | 94 |
 osplanning/omx | Provides a structured format for storing and retrieving 2D matrix data with associated metadata. | 50 |
 odot-pts/gtfs-ride | Defines an open standard for storing and sharing fixed-route transit ridership data. | 49 |