stop-amenity proposal

[Jonathan Wilson]

Based on my own observations of public transport stops/stations in various
cities over many years, I would like to propose the following items as
being valid for stop amenities (as an addition to what is mentioned on the
proposal page:

Under "Vending Machine", I propose:
Drink Vending Machine
Newspaper Vending Machine (would be used for anything that offers
newspapers, magazines or similar be it free or paid)
Smart Card Recharge Machine (i.e. machine that can be used to recharge
transit smart cards/stored value cards, my local transit system has
different machines for recharge and for sales of normal tickets)
Drinking Fountain (i.e. any place to get free drinking water)

I also propose an entry for Toilet, then under that I propose
Male Toilet
Female Toilet
Disabled Toilet
Parents Room
Separate entries are necessary as not all stations will have e.g. disabled
toilets

An entry for luggage lockers may also be worth adding

I also think it would be usefull to have an entry to indicate that a
stop/station has a staffed information or ticket kiosk (that may sell
transit smart cards, recharge such cards, sell tickets, provide
timetable/route information, issue concession passes etc)

Not being a feed publisher, I have no idea exactly which items feed
publishers would want to include in an "amenities" list, this is just a
proposal based on the sorts of things I as a transit user (and a
user/developer of software that displays transit information) would want to
know about a stop or station (especially one that I may not have visited
before)

[Joe Hughes]

For reference, here are two previous discussion threads about stop
amenities:

http://groups.google.com/group/gtfs-changes/browse_thread/thread/5910790204c0d5b2/
and
http://groups.google.com/group/gtfs-changes/browse_thread/thread/923d9658d2f1f321/

Joe

[Mike Gilligan]

When I first proposed adding stop features in 2007, I just slapped up
a page (http://sites.google.com/site/gtfschanges/proposals/stop-
amenity) which represented most of the public features tracked by
TriMet. TriMet's GTFS (http://developer.trimet.org/schedule/gtfs.zip)
has included stop_features.txt since then and there are a few
consumers using the data including the Sendero Group's (http://
www.senderogroup.com) accessible GPS products.

I was hoping the page would grow, in a thoughtful way, to include
additional features beyond our agency. Though I like Jonathan's
suggestions, I would caution growing the proposal without publishers
willing to supply the new features.

-Mike
TriMet

[tompw]

General point: regardless of the length of the list, I'm worried that
there will always be features that agencies provide (and wish to
communicate to passengers) but won't be on the list. The only way
roudn this is to have a list which includes a lot of very high-level/
items that run the risk of being to vague to be useful.

Regards,

Tom

On Aug 31, 9:43 am, Mike Gilligan <mgilli...@gmail.com> wrote:
> When I first proposed adding stop features in 2007, I just slapped up
> a page (http://sites.google.com/site/gtfschanges/proposals/stop-
> amenity) which represented most of the public features tracked by
> TriMet. TriMet's GTFS (http://developer.trimet.org/schedule/gtfs.zip)
> has included stop_features.txt since then and there are a few

> consumers using the data including the Sendero Group's (http://www.senderogroup.com) accessible GPS products.

> > before)- Hide quoted text -
>
> - Show quoted text -