Transit Website Generation #2
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
gtfs.zone/hatchery#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We need to fix transit websites. No more https://westbusservice.com/ or http://www.columbiacountyny.com/columbia-county-public-transit.html
Lets be real, though, no big operator needs this. So for the small operators, what do they need?
Some Questions
Lets pretend I'm an operator. I have an existing website. It sucks. I want to build a new one. Maybe I can control some DNS records, maybe I can write a 302 page. I think I would prefer someone else reliable be hosting it, but I must be able to edit it.
Idea
More Questions
Sooo...
We could just host one of each theme and you could point it at your GTFS feed and it would display it. I'll think more about this later.
There's lots of other examples of public transit websites in the UK. I know more about rail sites (which do not generally use GTFS).
The best example I've worked with is Bus Times: https://bustimes.org/ This is one I use regularly and it takes GTFS RT feeds from the bus Open Data service: https://www.bus-data.dft.gov.uk/ There are many others though!
For rail we don't currently have the same requirements on TOCs to provide GTFS RT data. It's something I could probably implement in our systems. The market leaders in this space are:
Agreed on what you say about having good templates, however. I'm not aware of a public repository that hosts such templates which could 'easily' be incorporated by small-medium transit providers. This seems like something which is worth exploring!
@rhorridge These aggregators are cool and provide a nice one stop shop for a variety of networks. However, agencies will likely always continue to maintain their own independent websites. It would be nice to have a minimum quality for them.
This is something I've tested out previously that generates timetables usable for agencies: https://gtfstohtml.com/ Expanding that so that it can output a Zola or Jekyll formatted static site (which could then be further themed) would be cool.
Yes, having a straightforward template is very useful! There's a big need for a standard reference implementation for displaying this information.
Agree that agencies will always need to maintain their own. This has its share of issues e.g. in the UK every train operator maintains their own website for buying tickets, and there isn't a lot of standardisation between them. For buses the fare structure is usually much simpler so there is less inherent complexity that has to be built-in, making a standardised tool more useful.