Skip to content

Policy-Driven Trip Events #480

@quicklywilliam

Description

@quicklywilliam

Is your feature request related to a problem? Please describe.

Cities want to be able to perform Policy compliance monitoring (both real-time and historical) for vehicles in motion. Currently, it is not possible to meet this need without requiring precise trip location data.

Describe the solution you'd like

The idea is that vehicles would emit events whenever they enter or leave a geography defined in the Policy endpoint. Then, instead of sharing the exact vehicle location, these events would simply give the UUID for the geography. This would be accomplished via the following changes:

Rename events for entering and leaving municipal areas so they apply to all Policy geographies.

  • enter_municipal_areaenter_geography
  • leave_municipal_arealeave_geography

Add the geography information to the event.

  • Add a new event_geography field containing the geography UUID to Provider. This field is required if event_location is not present.
  • Add a new event_geography field containing the geography UUID to Agency. This field is required if telemetry is not present.

Remove requirement for precise location data for vehicles during trips.

  • Make event_location in Provider optional in the case of vehicle_state:in_use events
  • Make telemetry in agency optional in the case of vehicle_state:in_use events

Is this a breaking change

  • Yes, breaking

Impacted Spec

For which spec is this feature being requested?

  • agency
  • provider

Describe alternatives you've considered

None at this time.

Additional context

Note that this proposal assumes/builds on the already proposed changes that unify and simplify Policy and Agency events:
#271

This issue is also related to a proposal to unify the way municipal boundaries and Policy geometries are expressed:
#474

Metadata

Metadata

Assignees

No one assigned

    Labels

    AgencySpecific to the Agency APIPolicySpecific to the Policy APIProviderSpecific to the Provider APIprivacyImplications around privacy for the attention of the OMF Privacy Committee

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions