New gtfs url for westfalen-lippe #54
Conversation
|
There should be a permanent URL for the GTFS feed. Changing URLs every so often is not how GTFS is supposed to work. The URL, of course, can be a redirect to another URL that points to a specific dated GTFS file. @od-ms can you make that happen? I'm holding off on updating for now, if this can become a more sustainable change. |
|
@stefanw juliuste did something similar already, but he is only hosting the germany-wide gtfs file. Could you use that file instead for mapnificent? Or maybe is that file too large for mapnificent? (currently 266MB) https://github.com/juliuste/opendata-oepnv Alternatively, the easiest way for me would be to commit the "westfalen-lippe" gtfs feed file into a github repository, and then link to that file directly. And then update the file from time to time. I could do that. Should I do that? |
|
I think one way to do this with CKAN is to have a dataset or resource on a dataset dedicated to the latest GTFS file and then update that resource. The filename of the resource can change and reflect the creation date, the resource download URL without the filename like this still works and can be stable: I don't think the data needs to be committed anywhere. I just want a stable URL. That URL can just point at the latest resource file on opendata-oepnv.de (no need to copy the data). |
|
@stefanw Yes I see. So what we need is a hosting space where we can put a durable and reliable redirect link. |
it seems the old file was taken down by opendata-oepnv