GMNS v0.90

[ianberg-volpe]

This pull request proposes changes to the specification based on comments received on the structure of the signal tables, several outstanding issues, and ongoing refinements.

Major changes

Restructuring of Signal tables

• Replaced node_id fields with controller_id and added a controller_id table. (Signal phase concurrency (ring diagram): variability #26)
• Reformatted old signal_phase table into new signal_phase_mvmt table:
  • Added signal_phase_mvmt_id and signal_phase_id.
• Reformatted old signal_phase_concurrency table into new signal_phase table:
  • Added position and signal_phase_num. (Signal phase concurrency (ring diagram): completeness #25)
• Smaller changes:
  • Added time_day field to signal_timing_plan table.
  • Renamed phase_num to signal_phase_num
  • Added signal_phase_id to signal_timing_phase table.

Inheritance: Made fields consistent between parent and child relationships (#19, #33)

The inheritance relationships between tables were more clearly defined. See this figure for more detail. Changes to implement this include:

• Adding a toll field to link table.
• Adding the following fields to the segment table: grade, lanes, toll, jurisdiction, and row_width.
• Cleaning up primary keys: they are now all in the format table_name_id
  • Renamed link_lane_tod table to lane_tod.
  • The segment_lane primary key is now segment_lane_id
  • Segment_lane_tod primary key is now segment_lane_tod_id.
  • The lane_tod primary key is now lane_tod_id and references lane_id instead of link_id.

Clarified role of notes fields (#37)

The notes is an optional ad hoc field that is used in many of our examples, but it should not be included in the base specification.

New Time of Day Examples

Two new examples (I-93 and CT Ave have been added that demonstrate the use of different TOD tables.

Minor changes

• In movement table, separated ib_lane into start_ib_lane and end_ib_lane (same for outbound). (Movement ib_lane #20)
• Removed link_id field from the segment_lane table as it was redundant.
  Several cleanup edits and clarifications to documentation were also made, including:
• Adding a FAQ and General GMNS Concepts section to the main readme. (Use OSM standards for location type #10, If a location is "on" a node, do we have to create a location entry? #12, Link shape, lateral offset, and node geometry #27)
• Organizing the wiki and removing outdated information.
• Changed all enumerated values to lowercase (standardize uppercase vs lowercase for enums #35)

Examples and conversions

Examples and conversion tools have been updated to reflect updates to the specification. Additionally, one new conversion script was added, from GMNS to Network Wrangler.