Skip to content

2025 07 31

Jump to bottom
Reid Passmore edited this page Aug 7, 2025 · 13 revisions

When

Thursday July 31, 2025 @ 3:00pm on Microsoft Teams

Slides

Agenda

Please join us for the next meeting of the National Collaboration on Bicycle, Pedestrian and Accessibility Infrastructure Data (NC-BPAID)! We’ll be presenting another look into the draft specification to see how bicycle infrastructure is represented, and we want your ideas and feedback.

Also, reminder that the draft specification document is up for review and comment on the GitHub: https://github.com/dotbts/BPA/tree/main#see-the-draft-specification

Hope to see you there!

Agenda:

  • Welcome
    • Housekeeping
    • Context
    • Meeting Objectives
  • NC-BPAID Status Updates
    • GATIS Explorer
  • New subgroup leads
  • Open floor for announcements
  • Subgroup updates
    • Specification Development – Jeff Maki, Paul Moser, Ryan Westrom
    • Data Practices – Jonah Chiarenza, Bahar Dadashova, Josh Roll
    • Outreach – Ellwood Hanrahan and Ximon Zhu
  • Specification Discussion: GATIS Bicycle features - Reid Passmore and Paul Moser

Notes

Outreach Subgroup Update

  • Welcome Ximon Zhu as the new subgroup co-lead!

Data Specification Development Subgroup Update

  • Feedback on draft one is still coming in
  • Draft two document will be created shortly
  • Next meeting is August 6 at 4pm Eastern

Data Practices Subgroup Update

  • Welcome Bahar Dadashova as the new subgroup co-lead!

Announcements

  • NCHRP 08-177 “Digitizing Bicycle and Pedestrian Treatments for Promoting Active Transportation Safety” is starting up work again. The project team is working on a practitioner survey on bike/ped infrastructure data practices. If you are at a state DOT or MPO and are interested in taking the survey to share your practices, please reach out to Cyrus Chimento ASAP: cyruschimento@AltaGo.com
  • First Meeting of the new independent Bicycle and Pedestrian Data Committee is on Tuesday, August 19, 2025 at 2PM Eastern (11AM Pacific). This will be an excellent opportunity for you to give input on group direction and become more involved with the new independent bike and pedestrian data committee. A link to this exciting and interactive one-hour meeting is below. We hope you can join us! Teams Meeting Link In addition, now is an excellent time to help us chart a new path into the future to support bicycle and pedestrian data outside of TRB. To give us input on our new name and direction, please fill out our survey before August 4 (extended to August 12!).
  • OS-CONNECT the WA state OpenSidewalks Consistent Networked dataset has a new data viewer with commenting capacity! https://osconnect-viewer.tdei.us/

GATIS Bicycle features Presentation - Reid Passmore and Paul Moser (see slides for more info)

Discussion that followed the presentation:
  • How are BRT/bus lanes and access for bikes (including floating bus stops) represented in the spec?
    • This is currently not in the specification, but it’s a conversation that needs to take place. Floating bus stops can be represented as traffic islands.
  • What’s the connection of GATIS to OSM attributes and where should smaller agencies pull information about roads?
    • We don’t specify where the attributes should come from, so they can be pulled from anywhere. We want to be agnostic, and mindful of OSM licensing. The recommendation is to give folks an opportunity to pull in OSM attributes, at least for roadway.
  • Is there a defined threshold where the infrastructure deviates from the right of way (ROW) where it needs to be represented as a separate edge? Is it 50 feet or some other distance?
    • We would like folks to make that decision for themselves rather than impose one. But we’re looking for feedback on that topic. This is also something we may capture in the tier model; start requiring separate infrastructure at tier 2 and above, for example.
  • What about representing advisory bike lanes and sharrows?
    • Specification is currently not capturing that.
  • Consider the MUTCD bike section when listing our bike facility types, not just AASHTO, NACTO and NBN.
  • What constitutes a buffer? Are planters buffers?
  • "bikeway_type" is the flexible field, where you can have some variety, like separated bike lane or cycle track, but when you are looking at the type of separation field, this is a bit less flexible and needs to be more specific, whether flex posts or jersey barriers are used.
  • There was some confusion on the difference between "separation_elements" and "separation_permeable_car". Do these overlap? Would you use one or the other?
    • "separation_permeable_car" is a little more subjective, and it’s still an experimental field. We would use both fields. Permeability is probably not a great word here, soft/hard separation is a better dichotomy, maybe fixed and non-fixed.
  • We have a date on when the bike facilities were added (date built), but we should add a date on when the facility closed. This would be useful for safety studies across time.
  • Non-permanent features: Temporary traffic control, pilot lane, or even damaged infrastructure like flex posts. Also, temporal facilities that switch between peak and off-peak usage.
    • Specification is not currently representing it, only includes seasonal closures. Should add temporal changes.

Clone this wiki locally