-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend Metrics API to accommodate street segment-level metrics / aggregates #556
Comments
this is a great idea. seems like a good use case for the SharedStreets reference system, but i'm curious to hear from folks who have experience working with it. |
Good question for the Curb WG |
See notes from the WG call this week.
|
@schnuerle is this still under consideration for next release? It sounds like it might be blocked by the Curb WG making a decision about a linear referencing system? |
@quicklywilliam It can be discussed especially if people have a good proposal for it. But it may change based on Curb efforts which can bring some clarity to a good technical solution. |
@schnuerle we are interested in putting something together. Our thought is that it could be agnostic to the LRS – we'd focus on the aggregation method/format, and leave it open to be used with OSM, CurbLR, Coord etc. |
Closing unless people chime in to say this is still needed, and have an idea on how it could be executed. |
Is your feature request related to a problem? Please describe.
The Metrics API proposed in #485/#486/#487 offers a mechanism for exchange calculated / aggregated metrics within MDS. It supports metrics reporting across various dimensions, such as vehicle_type, MDS Geography, or provider. In its current form, MDS Geographies are not well suited for identifying individual street segments in a form that could be related to a linear referencing system. For some metrics (vehicle volume, average speed, parked vehicle density, etc.) street-segment level data could be extraordinarily useful.
This proposal is a placeholder for a conversation to extend Metrics to allow for aggregated metrics reporting at the street segment level, perhaps by creating an appropriate Dimension within the Metrics API.
The text was updated successfully, but these errors were encountered: