openmobilityfoundation / openmobilityfoundation/mobility-data-specification

Adopt additional parking facilities information

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

Nobody has claimed this yet.

Agency Policy 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.

Yes. As more mobility providers add infrastructure in the ROW, the City of Minneapolis has been having challenges understanding where parking facilities are located and what their different features are.

We'd like mobility operators to regularly report where their parking facilities are so we can know where they are, what features/amenties they have and to be able to direct riders to those locations and create optional or required parking zones. The City would also share its parking infrastructure as well.

Additionally, as we add more and different parking facilities; racks, docks, hangars, etc. with various features; power, security, etc. we need to better track what capabilities and capacities these new facilities have for residents & users.

Describe the solution you'd like

We would like to add data fields and new variables that can capture the different data necessary to map and understand their locations and different features.

Is this a breaking change
  • I'm not sure
Impacted Spec

For which spec is this feature being requested?

  • agency
  • provider
Describe alternatives you've considered

Receiving regular reports or maps from individual providers.

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

The issue identifies the agency and provider specs as impacted entry points but names no files or tests. Start by reviewing those specs and their existing facility-related data. Done would require an agreed set of fields and variables for parking-facility locations, features, capabilities, and capacities.

Written by the indexing model from the issue text.

Assessment

Domain
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.