Comments (8)
We get lots of support requests for exactly this topic in the OpenTripPlanner chat room.
I would welcome the spec being more clear on this.
from transit.
I think a simple one liner at this section would be sufficient:
All files must be placed at the root level of the zip file. Zip files with no entries at the root level are invalid.
from transit.
I upvote this - many GTFS producers incorrectly assume that simply having a zipped file is sufficient, and will often enclose them using software that malforms the enclosure.
from transit.
Mecatran: +1
Not forbidding this also raise the interesting question of what to do with multiple data inside multiple folders, or split in several folders. Forcing files to be at the root would be more convenient. The spec should at least strongly advise to do that.
from transit.
I would be even a bit more explicit maybe?
All files must be placed at the root level of the zip file. A zip file with data files contained in a subfolder is considered invalid.
(just an idea)
from transit.
In #379 I propose a PR (unsure what the recommended process is, at least this helped me figure out what a good place to state this would be).
from transit.
I have opened the votes officially, please ensure your vote is listed in #379 (comment) ! (@leonardehrenfried @evantrillium @laurentg in particular, since you had already "voted" here). Thanks!
from transit.
Thanks everyone for the feedback :-)
from transit.
Related Issues (20)
- Static file version information is missing in the real-time data feed HOT 10
- preferred citation? HOT 1
- Improve definition of Fare Products
- Draft proposal : GTFS-TripModifications HOT 5
- Add rider_category_id to fare_products.txt
- Add maximum waiting time to transfers.txt HOT 2
- Documentation: inconsistencies between gtfs-realtime.proto
- GTFS-Fares v2: Improvement of filling with stops of a certain area HOT 3
- Move Dataset Publishing and General Practices from Best Practices to the spec HOT 10
- Add recommended presence: reconciling confusion between best practices and spec HOT 10
- TripDescriptor.start_date matching between GTFS-RT + GTFS-static HOT 2
- GTFS-Flex: Service Discovery HOT 11
- Add rule_priority field to fare_leg_rules.txt HOT 7
- Add fare_media_type=1 to fare_media.txt HOT 8
- GTFS-Fares v2: Add networks.txt & route_networks.txt HOT 13
- GeoJSON in GTFS? (Or the future of GTFS serialisation) HOT 20
- Phone number international format in GTFS HOT 2
- stop_times.shapes_dist_traveled shouldn't be defined if the trip doesn't have shapes associated HOT 7
- GTFS changes - voting agents HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from transit.