After a little more thinking about this, it seems like it might be
good to generalize this to cover general information about fares, not
just online ticket-buying pages. This way, it would effectively be a
version of Kevin O'Malley's fare_url proposal from April:
http://groups.google.com/group/gtfs-changes/browse_thread/thread/8633aa6cc371aa3f
The field name and description would then be something more like this:
--------------------------------
agency_fare_url (optional):
The agency_fare_url specifies the URL of a web page that allows a
rider to learn more about that agency's fare structure, and/or
purchase tickets or other fare instruments online.
The value must be a fully qualified URL that includes http://
or https://, and any special characters in the URL must be correctly
escaped. Seehttp://
www.w3.org/Addressing/URL/4_URI_Recommentations.html
for a description of how to create fully qualified URL values.
--------------------------------
I take it that this modified version would be more broadly useful.
Your thoughts?
Joe
On Sep 9, 9:59 pm, Joe Hughes <
joe.hughes.c...@gmail.com> wrote:
> Summary:
> Add a way to specify the URL of a page where the rider can purchase
> fare instruments online.
>
> Motivation:
> An increasing number of agencies and operators have a way to purchase
> tickets and passes online, and it would be useful to riders if GTFS-
> based applications knew which page to link to.
>
> Proposal:
> The following field would be added to agency.txt:
> --------------------------------
> agency_ticket_url (optional):
> The agency_ticket_url specifies the URL of a web page that allows a
> rider to purchase tickets or other fare instruments for that agency
> online. The value must be a fully qualified URL that includes http://
> or https://, and any special characters in the URL must be correctly
> escaped. Seehttp://
www.w3.org/Addressing/URL/4_URI_Recommentations.html