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
As first suggested by @pstraforelli in main data issue, Vanouver's Mobi system now provides open trip data. These can not, however, currently be incorporated because there are no associated data on station locations. The only information provided is in the form of a system map, itself calling an external google maps script with embedded --- and non-accessible --- data. As for Ciudad Mexico, such data can not be incorporated in this package without associated georeferences for station locations.
A further issue with the Vancouver data is the non-standard format. Rather than precise start and end times, these are rounded to nearest hour, and a total trip duration in seconds is given. This ought not prevent incorporation, and could be circumvented either by:
Generating simulated start and end times, with differences precisely reflecting stated journey times; or
Modifying basic data output to include additional raw data column for journey durations.
... will address that if and when information on station locations might become available. I'll close this issue straight away, but please @pstraforelli if you could help determine whether station coordinates might be openly available in any form, then i'll be happy to re-open and pursue incorporation of these data. Thanks for the input!
The text was updated successfully, but these errors were encountered:
As first suggested by @pstraforelli in main data issue, Vanouver's Mobi system now provides open trip data. These can not, however, currently be incorporated because there are no associated data on station locations. The only information provided is in the form of a system map, itself calling an external google maps script with embedded --- and non-accessible --- data. As for Ciudad Mexico, such data can not be incorporated in this package without associated georeferences for station locations.
A further issue with the Vancouver data is the non-standard format. Rather than precise start and end times, these are rounded to nearest hour, and a total trip duration in seconds is given. This ought not prevent incorporation, and could be circumvented either by:
... will address that if and when information on station locations might become available. I'll close this issue straight away, but please @pstraforelli if you could help determine whether station coordinates might be openly available in any form, then i'll be happy to re-open and pursue incorporation of these data. Thanks for the input!
The text was updated successfully, but these errors were encountered: