home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: rec.railroad
- Path: sparky!uunet!digex.com!terryfry
- From: terryfry@access.digex.com (Terry Fry)
- Subject: Re: Amtrak List of Trains by # (LOOONG) (fwd)
- Message-ID: <BxuBsq.167@access.digex.com>
- Sender: usenet@access.digex.com
- Nntp-Posting-Host: access.digex.com
- Organization: Express Access Online Communications, Greenbelt, Maryland USA
- References: <Pine.3.05.9211151945.A26182-e100000@uafhp.uark.edu> <TML.92Nov16103137@hemuli.tik.vtt.fi>
- Date: Tue, 17 Nov 1992 03:17:13 GMT
- Lines: 26
-
- In article <TML.92Nov16103137@hemuli.tik.vtt.fi> tml@tik.vtt.fi (Tor Lillqvist) writes:
- >In article <Pine.3.05.9211151945.A26182-e100000@uafhp.uark.edu> plaws@uafhp.uark.edu (Peter Laws) writes:
- > 1) Taken from _Amtrak System Train Timetables_, valid through 4/3/93.
- >
- > 1 Sunset Ltd. NOL LAX 136 Comb w/21 SAS
- > ^^^ ^^^
- >
- >Why does Amtrak use what I assume are *airport* designators for
- >stations? Isn't that both stupid, as trains are supposed to compete
- >with airplanes, and misleading, as many cities have several airports,
- >none of which presumably are as conveniently located as the railway
- >station(s)?
-
- You have a valid question, but the answer makes sense (err, sorta).
-
- It has to do with Travel agency Automations systems, Amtrak, and the huge
- reservation computer systems that were under development at the time
- Amtrak started. Both were going though a major overhaul, it was decided
- to reduce confusion for Travel Agencies (which book though a res system
- that "connects" to Amtraks computers. (For SABRE its **AMK)
- Utilizing a single set of codes reduced confusion & obviously made
- programmers much happier.
-
-
- It hasn't become the standard that was envisioned, but for people who
- travel its become a defacto-standard.
-