Skip to content
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

Closed
jfh01 opened this issue Jul 17, 2020 · 7 comments
Closed
Labels
Metrics Related to the Metrics API and related topics
Milestone

Comments

@jfh01
Copy link
Contributor

jfh01 commented Jul 17, 2020

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.

@marie-x marie-x added this to the Future milestone Aug 20, 2020
@schnuerle schnuerle added the Metrics Related to the Metrics API and related topics label Aug 28, 2020
@johnclary
Copy link
Contributor

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.

@marie-x
Copy link
Collaborator

marie-x commented Sep 17, 2020

Good question for the Curb WG

@schnuerle
Copy link
Member

See notes from the WG call this week.

  • Sharada - streets segments identified with shared streets ID?
  • Burden on providers?
  • DC can do this if the GPS accuracy is good enough
  • 2 things - disaggregated data with street segments and /trips, and in Metrics to aggregate to street segments (useful for providers offering to cities, not how it is now).
  • Shared streets only ID used? City IDs. Question of analytic tools cities are using.
  • Combine multiple provider data into Metrics
  • Instead of geographies, talk in segments
  • Use case - MPO wanting to make use of this for members
  • OSM, Coord, CurbLR street segment systems, cities have their own segment ids in Open data.
  • Curb WG will decide how to define linear space, could be used here, needs to be consistent with rest of MDS

@quicklywilliam
Copy link
Contributor

@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?

@schnuerle
Copy link
Member

@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.

@quicklywilliam
Copy link
Contributor

@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.

@schnuerle
Copy link
Member

Closing unless people chime in to say this is still needed, and have an idea on how it could be executed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metrics Related to the Metrics API and related topics
Projects
None yet
Development

No branches or pull requests

5 participants