Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure CSV data can be parsed if headers are not consistent #11

Open
romanofski opened this issue Nov 4, 2016 · 0 comments
Open

Comments

@romanofski
Copy link
Owner

Some of the data we find out there does not include headers and data for optional fields (e.g. the Brisbane CSV data misses https://developers.google.com/transit/gtfs/reference/stop_times-file shape_dist_traveled from the reference). Investigate if we can import the data if the dataset provides these optional fields, although no functionality is using it right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant