openmobilityfoundation / openmobilityfoundation/mobility-data-specification
Create a "Provider Manifest" endpoint for operating dates/down time dates/service suspension
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 746
- Forks
- 252
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 2
Description
Edit by @schnuerle - turning this issue into a 'Provider Manifest' issue which includes what you'd like to see here, similar to system_information in GBFS and complimentary to agency's Policy Requirements. Original issue title was: "Provide the operating date ranges within the Provider API so that we know when to query data"
Is your feature request related to a problem? Please describe.
We are struggling to know the collection of date ranges when a provider has been operating in the city.
It makes it difficult to query efficiently the Provider API. It makes it difficult for the city to have a good visibility on this key information.
Describe the solution you'd like
I wonder whether this info could be provided within the Provider API as part of an info endpoint. The operating zone could also be provided by the operator this way, as well as the data availability. Operators may indeed have no data historically for certain periods they were operating due to technical issues.
Is this a breaking change
No, it's not a breaking change. It's additive
Impacted Spec
provider
Describe alternatives you've considered
Asking directly the city or the provider. Trial & guess day by day in the provider API ingestion.
Additional context
NA
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provider section of the specification and compare the requested manifest with GBFS's system_information reference. Define the agreed endpoint scope for operating dates, downtime or service suspension, operating zone, and data availability, then document the final fields and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100