Thank you all for attending this meeting and having a very lively and robust discussion on the needs for Delivery data and digital policy in MDS from multiple cities, vendors, and operators.
Here are the slides, recording, notes, action items, links, etc:
Action Items:
- Discussion area, leave your needs and data requirements
- Are Incidents enough to track "unsafe and illegal operations by delivery drivers - i.e. speeding, illegal turn, double-parking, etc." - may need more incident types, like CDS Enforcements and Violations
- Clarify that shifts are made up of journeys, journeys made up of trips. Trips could have multiple orders, orders could have multiple packages.
- Might need an array of package/orders details (delivery type, order_id, costs)
- Shift_id allows chaining of journeys. Is this the right name (some term bigger than a journey for freight solution), or is there another additional field needed?
- Digital policy - how does MDS Policy support density? Eg cap on number of vehicles in an area. New policy type needed?
- Statistical areas - Change to array from string? Is there only one area per event?
- If you want a statistical area for an end, but lat/lon for a start, how do you account for privacy? What change in spec could support this?
Please leave your thoughts and needs for Delivery in the discussion area, since we want to wrap this up in 2 months for CDS 2.1 release.