As discussed at the 2017 TRB Annual Meeting

General Travel Network Specification

The inordinate amount of time required to develop the network by MPO’s needs to be resolved.

Currently there are too many different solutions, inelegant solutions, non transferrable solutions to the same problem.

What are the steps to take to create a generalized standard?

Convene stakeholders to identify requirements

Data model that has capability of storing current, past, and future conditions [including variants on the future] and good capabilities for switching between scenarios. Should have versioning abilities at very least, which can evolve to scenarios.

Must be sharing-oriented. Could greatly augment ability to visualize results.

What resolution will it support: micro vs macro? Dynamic? What schema? node-link? intersection geometry? signalization?

Identify Existing Solutions


Jellyfish project: Queensland university attempted a master network for Australia

Examine where the time-consuming steps are in the current work flows.

Standardize Network Vocabulary

Decide on:

  • Vocabulary: standard naming conventions

Focus on static assignment as first pass.

Leverage existing popular standards when possible [ e.g. GTFS, OSM ]

Need some sort of “WOW” factor for phase I that this lacks.

Standardize Network Schema

Decide on:

  • directed or reversible links
  • Schema: Minimum set of fields
  • set of 3-5 data formats that Zephyr can support APIs for and create data validators to check network topology

Reference research on existing formats and solutions.

Develop network management strategy

Develop capabilities for:

  • Diff-able networks
  • Scenario development
  • Version control/flow standards
  • Projects/master metworks

Who should be involved ?

Involvement should include vendors, consultants, and owners

Make sure there is a variety of players to ensure different ways of thinking

Relative priority

We believe this could be a quick win.