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
(Security warning: the links below were found via search and I have not attempted to verify their trustworthiness.)
As far as I can find (though I might be mistaken), pybikes does not currently include any dockless systems, though there are several that have APIs (12). Is this a deliberate choice, or a general lack of much development since such systems became common?
If it is a choice not to, I suggest documenting that, closing requests to add them (#303#304), and linking to somewhere that does (Multicycles? did this industry effort ever get anywhere?).
If they are to be included, there is the question of how to represent them: #238 has a patch that treats each available bike as a 'station' with 1 bike and 1 space, which is probably the best option for compatibility with existing user code.
It could be useful to also have a field that marks a system as dockless, and/or specifies the boundary within which dockless returns are permitted, so e.g. a routing app can know that returning at your actual destination is an option.
The text was updated successfully, but these errors were encountered:
(Security warning: the links below were found via search and I have not attempted to verify their trustworthiness.)
As far as I can find (though I might be mistaken), pybikes does not currently include any dockless systems, though there are several that have APIs (1 2). Is this a deliberate choice, or a general lack of much development since such systems became common?
If it is a choice not to, I suggest documenting that, closing requests to add them (#303 #304), and linking to somewhere that does (Multicycles? did this industry effort ever get anywhere?).
If they are to be included, there is the question of how to represent them:
#238 has a patch that treats each available bike as a 'station' with 1 bike and 1 space, which is probably the best option for compatibility with existing user code.
It could be useful to also have a field that marks a system as dockless, and/or specifies the boundary within which dockless returns are permitted, so e.g. a routing app can know that returning at your actual destination is an option.
The text was updated successfully, but these errors were encountered: