You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We at Populus have been working to convert GBFS feeds to trip logs. One of the biggest issues is that when a bike disappears from the feed, we can't tell whether the bike is in use (on a trip) or if it's undergoing maintenance, being charged, etc. Also it's hard to differentiate short trips from connectivity issues / GPS noise (i.e. did a bike move 200 meters in 3 minutes, or was that just a gust of wind).
I wonder if it would help to leave a bike which is in use in the GBFS feed with an in_use flag. This would help address the above, and we also could know how many bikes are out there at any given time, which you can't know now. In theory, operators could continue to include some location information for the trip even when the vehicle is in use, and we could very roughly track the trip route for infrastructure planning purposes.
Some context here is that we are working with the cities to help them know how their bike and scooter share systems are working holistically. I understand from the responses to #47 that this is not the purpose of GBFS exactly, but it seems to me that GBFS could evolve to support this and keep from forcing my group and others from having to overhaul the standard entirely like MDS. Any thoughts on this use case, which I think will be increasingly common in the future. Is it better to just have the operators use MDS and report their own trips? I know that some cities would rather use GBFS because they don't trust the operators to report their trips perfectly.
The text was updated successfully, but these errors were encountered:
Hey @fscottfoti - a couple of your Populus colleagues were at the GBFS developers workshop held before the NABSA 2019 conference (workshop agenda and notes), where one hot topic of discussion was the roles of GBFS and MDS. While GBFS' purpose is not to support research or enforcement, we recognize that stakeholders may be using GBFS datasets to support those functions. Still, to avoid spec scope creep, we are suggesting that MDS is where this belongs. The hope is that cities will be able to use GBFS datasets as supplemental data, and in the future, GBFS validators will make this easier. The intention is also for the GBFS and MDS stakeholder communities to work closely together in the future to make sure these kinds of cross-spec requests don't get lost. I'm going to give this a few days and then go ahead and close out this issue.
This is tangentially related to #47.
We at Populus have been working to convert GBFS feeds to trip logs. One of the biggest issues is that when a bike disappears from the feed, we can't tell whether the bike is in use (on a trip) or if it's undergoing maintenance, being charged, etc. Also it's hard to differentiate short trips from connectivity issues / GPS noise (i.e. did a bike move 200 meters in 3 minutes, or was that just a gust of wind).
I wonder if it would help to leave a bike which is in use in the GBFS feed with an in_use flag. This would help address the above, and we also could know how many bikes are out there at any given time, which you can't know now. In theory, operators could continue to include some location information for the trip even when the vehicle is in use, and we could very roughly track the trip route for infrastructure planning purposes.
Some context here is that we are working with the cities to help them know how their bike and scooter share systems are working holistically. I understand from the responses to #47 that this is not the purpose of GBFS exactly, but it seems to me that GBFS could evolve to support this and keep from forcing my group and others from having to overhaul the standard entirely like MDS. Any thoughts on this use case, which I think will be increasingly common in the future. Is it better to just have the operators use MDS and report their own trips? I know that some cities would rather use GBFS because they don't trust the operators to report their trips perfectly.
The text was updated successfully, but these errors were encountered: