-
Notifications
You must be signed in to change notification settings - Fork 3
2025 04 01
Justyna Goworowska edited this page Apr 14, 2025
·
19 revisions
Tuesday April 1, 2025 @ 4:00pm on Microsoft Teams
- Welcome
- Housekeeping
- Context
- Meeting Objectives
- NC-BPAID Status Updates
- Co-chair elections and voting process
- Guiding principles vote
- Open floor for announcements
- Subgroup updates
- Data Practices – Josh Roll and Jonah Chiarenza leading
- Outreach – Krista Nordback and Ellwood Hanrahan leading
- Special update from Specification Development Subgroup – Jeff Maki, Paul Moser and Ryan Westrom leading
- Report out on focus group sessions
- Update on first specifications draft and process ahead
- Field testing and specification review update
- Meeting Objectives:
- Discuss upcoming Co-chair elections and voting process
- Invite the Collaboration to vote on Guiding Principles
- Provide subgroup updates and take a deep dive into specification development activities
- Introduce field testing guidelines
- NC-BPAID Updates:
- GitHub is back online. The content has been cleaned up and changes made based on Executive Orders.
- Staff Update – Reid Passmore has joined as a new Active Transportation Fellow. He has a PhD from Georgia Tech in transportation engineering.
- Full collaboration will now meet every other month. The next meeting will be May 29th.
- Join a subgroup – Meeting times:
- Outreach Subgroup - First Thursday of each month, 4-5p ET
- Specification Development Subgroup - Every other Wednesday, 4-5p ET (next meeting April 2)
- Data Practices Subgroup - First Thursday of each month, 3-4p ET
- Open Floor Announcements:
- Sarah Abel had a comment regarding ITS America MAP Standards. There are similar discussions in both groups, so coordination and participation in both groups are encouraged. David Jackson noted that MAP is in a holding pattern and no meetings are scheduled at this moment.
- Co-Chair Elections and Voting Process:
- The co-chair elections vote is open from April 1st to April 15th, 11:59PT.
- There is one voting member from each organization and it is an asynchronous vote.
- The Guiding Principles vote is open April 1st to April 15th, 11:59PT and is an asynchronous vote.
- Please view the meeting slides for more details (link at the top of this page).
- Subgroup Updates:
- Data Practices:
- The subgroup is currently curating a series of presentations from different data users regarding the way they characterize their uses and how they apply to real world problems. The presentations showcase how they are using their existing standards, and how the standards work, and how they don’t work.
- The presentations given so far are from Washington State DOT, Utah DOT, Delaware DOT, Oregon DOT.
- Next month the subgroup is hosting industry presentations from Ecopia, Citian.
- Outreach Subgroup:
- The subgroup is working on a strategic communication outline. The group wants to make sure we are getting to all the groups we want to include.
- Next month they will be thinking about a new name for the specification.
- Specifications Subgroup:
- The process to get to the first draft of the specifications:
-
- Identifying use cases (mainly asset management and routing).
-
- Solicit expert opinion (two focus groups on bike and ped infrastructure).
-
- Identifying existing specifications (memo from Mobility Data on similar specs).
-
- The subgroup is in the process of drafting the first version of the specifications, which will be completed in April.
- The next steps will be to get feedback and to test with real world data pipeline. Then to complete the second version of the specifications.
- The subgroup has three task forces: Intersections (how to model), Governance (metadata, governance of specs), and Element Hierarchy (how to represent shared elements).
- The input from the task forces is put into a draft of the data specifications.
- The process to get to the first draft of the specifications:
- Data Practices:
- Field testing and specification review update:
- Field testing is taking existing data and fitting it into our draft specifications.
- Who can be a field tester? Anyone with data or a data collection plan.
- Currently we have 11 different organizations who are interested in being field testers, and possibly more.
- Please share your recommendations for field testers.
- The timeline for field testing is April -June 2025.
- The review of the results will be completed before the second draft of the specifications in August.
- Who can be a reviewer? Anyone.
- Please view the meeting slides for more details (link at the top of this page).