search

MobilityData / gbfs

Documentation for the General Bikeshare Feed Specification, a standardized data feed for shared mobility system availability. Maintained by MobilityData
https://gbfs.org
Other
774 stars 282 forks source link

Restful API for filtering and pagination #617

Open edwinvandenbelt opened 3 months ago

edwinvandenbelt commented 3 months ago

What is the issue and why is it an issue?

We want to get availability in the (near) future, to reserve bikes/shared cars. The problem is that the dataset returned would be too large for systems with many vehicles.

Please describe some potential solutions you have considered (even if they aren’t related to GBFS).

The restful endpoint should have filters to limit the result (like geographical boundary, vehicle type, etc).

Is your potential solution a breaking change?

mobilitydataio commented 1 month ago

This discussion has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

testower commented 1 month ago

I have the same comment here, there is already an issue where forecasting is discussed as a new optional file, which I think would probably be a better fit. #612

richfab commented 1 month ago

I believe that this issue (https://github.com/MobilityData/gbfs/issues/617) is specific to the problem that the hypothetical dataset would be too large.

In the interest of keeping the GitHub issues for current problems rather than future problems: @edwinvandenbelt and community, do you have real life examples where the size of a GBFS file is an issue? If so, could you please share the datasets URLs?

testower commented 1 month ago

I think this should be considered in a broader context yes. Turning GBFS into a server / API specification has more implications. For example, would #630 alleviate some of that concern?