tobsesHub

Hi everybody, I have created a first proposal now. Please feel free to give me feedback. ## specification `forecasts.json` This file would describe multiple forecasts. Every forecast has a probability...

@sven4all Thanks, that's a good point. Do you know any kind of standard where something like this would fit better.

Okay, good points. I'm not sure at the moment. There are probably several sources that could provide such forecast data. The operator, because he has the data, but maybe also...

Interested people, please note that we are currently discussing another [topic](https://github.com/MobilityData/gbfs/issues/616), in which we may also be able to consider this topic.

One question. Why is there no endpoint like `all_vehicles.json`, which would include general information like equipment and pricing plan id, of course no coordinates? So it could be something like...

@richfab I like that soulution. Yes, we could probably add an optional `probability` field to unify this problem and the https://github.com/MobilityData/gbfs/issues/612 issue.