openmobilityfoundation / openmobilityfoundation/mobility-data-specification

Add fields to describe vehicle locks

Open
#706 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Agency Provider
Dominant language
No language data
Stars
746
Forks
252
Avg merge
3d 16h
Merged PRs (30d)
2

Description

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

Cities often include policies on locks and locking vehicles so they want to be able to track if vehicles have a lock (or not) and when that lock is in use (or not) as part of the data their getting via MDS.

Describe the solution you'd like

Add a new field for lock that would be used in the same way as vehicle_type or propulsion_type. Not sure if this could be a yes/no field or if there are lock types that would be useful to capture.

Add a new field for lock_status that would be used in the same way as battery_pct. This could probably be expressed as a simple on/off or 0/1.

Is this a breaking change
  • No, not breaking
Impacted Spec

For which spec is this feature being requested?

  • agency
  • provider
Describe alternatives you've considered

Currently there's no way to get this data.

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the agency and provider portions of the MDS specification, comparing the existing vehicle_type, propulsion_type, and battery_pct fields. Resolve whether lock and lock_status need defined types or values, then specify both fields without a breaking change; done means the requested vehicle-lock data is unambiguously represented in both impacted specs.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.