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
How do I mark up GTFS feeds not stored one .zip archive?
Serving the individual .csv/.txt files via HTTP has great benefits, including following web semantics & efficiency (caching, downloading only necessary files).
I currently run vbb-gtfs.jannisr.de as a "special treatment" for my need to work with Berlin data, but I'd like to a) follow best practices to make the "endpoint" as reusable as possible, and b) make it as portable as possible by using semantic markup such as DMFR/DACT-AP/DataPackage.
The text was updated successfully, but these errors were encountered:
derhuerst
changed the title
unzipped GTFS feeds
how to specify unzipped GTFS feeds?
Jan 10, 2020
derhuerst
added a commit
to derhuerst/vbb-gtfs.jannisr.de
that referenced
this issue
Jan 11, 2020
DMFR does not absolutely require that URLs be ZIP files. You may do so if you wish.
However, the transitland-lib tooling can currently only handle URLs that reference ZIP files. Since transitland-lib is used to power the Transitland Atlas repo of DMFR files, this means that Transitland Atlas can only have URLs that point to ZIPs. (Related to transitland/transitland-atlas#357)
How do I mark up GTFS feeds not stored one
.zip
archive?Serving the individual
.csv
/.txt
files via HTTP has great benefits, including following web semantics & efficiency (caching, downloading only necessary files).I currently run
vbb-gtfs.jannisr.de
as a "special treatment" for my need to work with Berlin data, but I'd like to a) follow best practices to make the "endpoint" as reusable as possible, and b) make it as portable as possible by using semantic markup such as DMFR/DACT-AP/DataPackage.The text was updated successfully, but these errors were encountered: