zephyr-data-specs/GMNS

Integration with A/B Street?

dabreegster opened this issue · 1 comments

Hi,

I stumbled across this repository looking for open data about traffic signal timing. I think the GMNS spec is the first specification I've found. I'm working on a traffic simulation tool called A/B Street. Part of this work has been surveying traffic signals around Seattle and representing the phases in a format referencing OpenStreetMap objects. This example file corresponds to the attached screenshot. The format is defined here, and this doc has more context on the format. A/B Street includes a UI for easily reconfiguring signals; this video demos this (but note the UI has been improved a bit since then).

I'm not totally sure what the goals of GMNS are, but I'm very interested in open data standards for traffic signals, and I have lots of existing code for editing, visualizing, and simulating signal timing. If there's any collaboration that makes sense, let me know!

Thanks,
-Dustin

Screenshot from 2020-07-04 16-16-48

Dustin, thank you for sharing your work, and for the interest in GMNS. GMNS is trying for a unified data specification that works across multiple network resolutions (i.e., from the statewide planning model to a detailed corridor analysis). The signals part of GMNS is the least mature, so we would be very interested in comments. I'll be taking a closer look at what you have done. Meanwhile, I'd suggest looking at following parts of GMNS:

  1. go to the updates branch (we have done some recent work with signals, not yet moved to the master branch)
  2. Look at the movements files (turning movements) and signal_phase_mvmt (ties signal phases to turning movements)
    Thanks. - Scott