-
Notifications
You must be signed in to change notification settings - Fork 299
Closed
Description
Have you read our FAQ? It’s possible your question can be answered there!
If you are new to the specification, please introduce yourself (name and organization/link to GBFS). It’s helpful to know who we're chatting with!
Hi,
My name is Arash Mansouri and I'm an engineering manager at Lyft.
What is the issue and why is it an issue?
I'm opening this issue as we are seeking guidance on how one would go about informing consumers of a GBFS feed about the fact that a particular market is no longer active. We would expect this information to fit into the system_alerts.json
file as it is supposed to be used for temporary shut-downs, but wanted to seek guidance on whether that is appropriate.
Questions:
- Can that file be used for permanent shut-downs, perhaps with the
end
field undertimes
being omitted? - Do you have any other recommendations for how one would notify consumers of this, without shutting the feed down all together which might lead to something breaking on the consumer's side?
- Would it be possible to perhaps add a field to that file distinguishing a temporary shutdown from a permanent one?
Please describe some potential solutions you have considered (even if they aren’t related to GBFS).
We have considered using the system_alerts.json
as described above.
Is your potential solution a breaking change?
- Yes
- [ ✔️ ] No
- Unsure
Metadata
Metadata
Assignees
Labels
No labels