Which event types and states should be tracked for vehicles?

[schnuerle]

The Events API currently has an event_type field, modeled after MDS, with a few options in it the draft for what fields need to be returned for which states in the curb events object:

• comms_lost: communications with the event source were lost
• comms_restored: communications with the event source were restored
• decommissioned: event source was decommissioned
• park_start: a vehicle stopped, parked, or double parked
• park_end: a parked vehicle leaving a parked or stopped state and resuming movement
• scheduled_report: event source reported status status at a scheduled interval
• enter_area: vehicle enters the relevant geographic area
• exit_area: vehicle exits the relevant geographic area

Which other events need to be added?

In MDS we have vehicle_states as well that use events to transition between. Do we need to add these as well, and if so what states?

How do we structure events and states? What can you measure with these? What do you want to measure with these?

[schnuerle]

Per the discussions, it seems the working group is leaning toward:

1. This list of states, as above
2. No state event changes to describe what happens between states (at least for v1.0)