How to represent reversible lanes in GMNS?

Define two lane records on the lanes table for opposite directions, with allowed_uses set to None for non-peak times, and use time-of-day tables to modify usage, as explained in the TOD examples section of the README.

GMNS vs MATSim network format: which is better for traffic simulation?

GMNS is a vendor-agnostic specification for data exchange, while MATSim has its own optimized format for simulation; GMNS is ideal for interoperability, but MATSim may offer better performance within its ecosystem without conversion overhead.

How to validate a GMNS dataset for compliance?

Use the provided Python and R tools for basic validation, and cross-reference the specification reference to ensure required fields and inheritance rules are met, though comprehensive validation suites are still evolving.

Can GMNS handle detailed bicycle lane data?

Yes, use the bike_facility field on links for basic info, or represent bike lanes explicitly in the lanes table or as separate links for paths, as detailed in the bicycle facilities FAQ.

What's the best way to store geometry in GMNS for large networks?

For efficiency, store shapepoints in a separate geometry table keyed by geometry_id instead of WKT in the link table, especially for complex networks, as noted in the geometry flexibility section.

How to integrate pedestrian sidewalks in GMNS?

Use the ped_facility field on links for simple representation, or create separate undirected links for detailed sidewalks and crosswalks, as demonstrated in the Cambridge example.

GMNS

Jupyter Notebookv0.97

A common human and machine-readable format for sharing routable, multi-modal road network data for transportation modeling.

Visit Website

What is GMNS?

GMNS (General Modeling Network Specification) is an open data specification that defines a common format for sharing routable road network files used in transportation planning and operations models. It solves the problem of incompatible network data formats across different modeling tools by providing a standardized, machine-readable structure that supports multi-modal and multi-resolution analysis. The specification describes network elements like nodes, links, lanes, and movements, along with their attributes and relationships.

Target Audience

Transportation planners, modelers, researchers, and software developers working on static or dynamic traffic simulation, network assignment, and multi-modal transportation analysis who need to exchange road network data between different tools and models.

Value Proposition

Developers and organizations choose GMNS because it is a vendor-neutral, extensible standard that promotes interoperability without locking users into specific software. Its flexibility allows detailed representation for dynamic microsimulation while remaining simple enough for macroscopic models, and it integrates with existing standards like GTFS for transit data.

Overview

General Modeling Network Specification

Use Cases

Best For

Related Projects

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

GitHub

132 stars17 forks0 contributors

Creating interoperable road network datasets for transportation research
Sharing network data between different traffic simulation software (e.g., MATSim, TRANSIMS)
Building multi-modal transportation models that include vehicles, pedestrians, and bicycles
Developing tools for converting between proprietary network formats and an open standard
Representing time-of-day variations like reversible lanes or dynamic tolls in network data
Integrating detailed intersection operations (lanes, movements, signals) into network models

Not Ideal For

Real-time traffic monitoring applications that require live data streams and dynamic updates
Simple web mapping projects that only need basic road geometries for visualization without modeling
Proprietary software environments with fixed internal formats and no need for external data exchange
Projects exclusively focused on transit data that can rely solely on GTFS without road network integration

Pros & Cons

Pros

Vendor-Neutral Interoperability

GMNS is implementation-agnostic, stored as JSON-described files like CSV or databases, enabling data sharing across different transportation modeling tools without software lock-in, as emphasized in the philosophy.

Multi-Resolution Flexibility

Supports from macro static models with just nodes and links to detailed micro simulations with optional lanes, movements, and time-of-day tables, allowing tailored detail levels per the specification table.

Extensible Modular Design

Only nodes and links are required; user-defined fields and extensions like segments and TOD files can be added, providing adaptability without enforcing a rigid universal model.

GTFS Integration

Links to GTFS for transit data via the gtfs_stop_id field, leveraging an established standard instead of reinventing the wheel, as recommended in the transit approach section.

Cons

Complex Inheritance Model

Attributes are inherited from parent to child elements (e.g., links to segments), which can lead to confusion and errors if not meticulously managed, as acknowledged in the inheritance relationships.

Lack of Enforced Standards

Fields like node_type have no standardized values, relying on external references like OpenStreetMap, potentially causing interoperability issues if users adopt different conventions.

Redundant Lane Representations

The lanes field on links may not match the lanes table entries, creating ambiguity, especially for static vs. dynamic models, as highlighted in the 'Difference between Lane Field and Lanes Table' section.

Limited Tooling Maturity

While basic Python and R tools are provided for conversion and validation, the ecosystem for robust integration with major modeling software is still under development, requiring custom implementation efforts.

Frequently Asked Questions

Home

Transit

GBFS

Documentation for the General Bikeshare Feed Specification, a standardized data feed for shared mobility system availability. Maintained by MobilityData

Stars899

Forks306

Last commit3 days ago

MDS

A data specification to enable right-of-way regulation, digital policy, geofencing, and two-way communication between mobility companies and public agencies worldwide for any regulated, shared vehicle.

Stars738

Forks249

Last commit3 days ago

OpenStreetMap Route Editor

A tool for efficiently editing Route Relations in OpenStreetMap - OSM

Stars0

Forks0

Last commit

TCRP G-16 Development of Transactional Data Specifications for Demand-Responsive Transportation (In progress)

The objective of this research is to develop technical specifications for transactional data for entities involved in the provision of demand-responsive transportation. Expected completion date is late 2018

Stars0

Forks0

Last commit

#transportation-planning

#transportation-modeling

Urban & Regional Planning332