Skip to content

Web conference notes, 2020.09.24 (Joint Working Group Provider Services)

Michael Schnuerle edited this page Sep 29, 2020 · 12 revisions

Web Conference, 2020.09.23

Joint Working Group - Provider Services

  • Every other week call at 9am PT / 12pm ET / 6pm CET

Conference Call Info

Meeting ID: 627 957 16 - https://zoom.us/j/627957166

One tap mobile: +19294362866,,627957166# US

Dial by phone: +1 929 436 2866 (US) (Find your local number)

Attendees

Add your own name, link, and organization during call

Agenda

  1. MDS 1.0.0 Released
  2. New chairs of steering committee
  3. Metrics #485 for 1.1.0
    • Special Groups aggregated metrics #569
    • Review Metrics Methodology document which includes MDC Glossary definitions

Minutes

Notes and or transcript of the call with presentation, document, GitHub links and calls to action.

Metrics - Aggregate Groups

  • Alex's needs:
    • Understanding utilization is valuable
    • Having defined approach streamlines across the board
    • added thoughts to the issue
  • Sharada's needs:
    • Been difficult to track data collection across providers
    • Trying to validate where low income demand is
    • added thoughts to the issue
  • Technical perspective
    • Sharada brought up geographies
      • Michael resurfaced the idea to redact data if count is too small (possibly if less than 5 or 10? See census)
      • Idea: Providers make recommendation on right level of granularity
      • Has been flagged for the privacy committee, but could also reach out to other privacy entities for guidance like EFF
      • Bill brought up a question about time range for the geographies
      • Michael mentioned that this ties to geography API which is underway
      • Performance was brought back up - need to ask providers what they think about implementing arbitrary geometries
      • Sean said that time range should be defined by cities, likely 1 hour is minimum
      • Metrics #486 has certain query interval enumerated values (though not defined yet) to create some guard rails
    • Sean mentioned that special groups is really just a filter or dimension and that that there might be other trip metrics needed
      • Michael mentioned that the proposal describes it, and that the implementation method in the PR is still up for debate.
      • The goal is to keep the first iteration of it pretty simple to solve one or two high value use cases for cities and providers.
    • Reviewed the attached Metrics document
      • Noted that even though averages could be calculated by the minute as in the MDC doc, they roll up to the hour for the MDS Metrics
    • Start/End Location
      • Can you just pick one, or do cities need both? What are the use cases and what is useful for policies and planning.
      • Sharada mentioned that both are useful
      • Stadium Scenario
        • For special group aggregation, this would help us understand number of low income individuals going to destination
      • Sean mentioned that having both OD (with anonymization) would still be useful
      • consensus is that having start and end location as a variable option is needed.
    • Calculation methodologies/thresholds
      • Michael mentioned that metrics should be tied together
      • Sean asked how frequently metrics should be run
    • Metrics may become a feature branch for community to see all together and give feedback on (like we are doing with Geography).

Please leave more feedback on the Github issues and PR for this.

Clone this wiki locally