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

returns an empty file #27

Open
dimacv opened this issue Jul 11, 2024 · 3 comments
Open

returns an empty file #27

dimacv opened this issue Jul 11, 2024 · 3 comments

Comments

@dimacv
Copy link

dimacv commented Jul 11, 2024

Previously, on version 3.2.0, I extracted the data I needed with the config -

"agencies": [
{
"agency_key": "feed_name_stops",
"path": "feed_name.zip",
"exclude": [
"stop_times",
"trips",
"shapes",
"transfers",
"pathways",
"calendar",
"calendar_dates"
]
}
],
"bufferSizeMeters": 400,
"coordinatePrecision": 5,
"outputType": "agency",
"outputFormat": "stops",
"zipOutput": false
}

However, starting from version 3.3.0 and higher, this config returns an empty file.

Please explain why this is so?

@brendannee
Copy link
Member

Thanks for reporting this issue. Can you share with me the GTFS file you are using with this config?

And also the output from running the command?

@dimacv
Copy link
Author

dimacv commented Jul 12, 2024

Yes, sure.
For example, to reproduce this behavior you can take the file from your examples -
http://cccta.org/GTFS/google_transit.zip

From version 3.3.0 onwards the resulting .json file will be like this -
{"type":"FeatureCollection","features":[]}

However, previously, up to and including version 3.2.0, the resulting .json file contained normal data.

@brendannee
Copy link
Member

I figured out the issue - in the config you shared, in the exclude array it is excluding shapes, trips and stop_times - this excludes importing some of the data that GTFS-to-geojson needs to create the GeoJSON.

I published an updated version just how that handles excluding calendar.txt - grab that latest version and update the exclude array in the config and it should work as expected.

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

2 participants