Article View: dc.driving
Article #21328Re: Travel Updates on the Radio
From: John Boteler
Date: Wed, 01 Jun 1994 02:30
Date: Wed, 01 Jun 1994 02:30
46 lines
2667 bytes
2667 bytes
thonhazz@clark.net (Jonathan Hazzard) writes: > Metro Traffic does at least a reasonable job, reporting all dispatched >emergencies and most of the major tie-ups, but in my opinion, WTOP has by >far the best coverage. During rush hour, they typically have two aircraft >and four reporters around the city watching traffic. It seems that their >information is more timely and more thorough. And what's more, the I have listened to the communications between Bob Marburg and his minions to get an inside peek at how he does things. (I don't think much of Marburg's reports or style, you will find.) He routinely gives these kids tongue-lashings for reporting on things which "everybody knows about anyway", meaning that the listener should know that the Beltway is slow at River Road everyday, therefore WTOP reports on it will be rote and valueless. This does nothing for the driver who is not intimately familiar with traffic patterns around here. This is Marburg's philosophy on most of the reports. If it is a typical problem area, it gets little treatment; what mention the area does receive is based on conjecture and is likely not accurate. Example: after spending enough time in a 5MPH backup on the Inner Loop past River Road and I270, I exited at Old Georgetown Road to go cross-country. Meanwhile, Marburg robotically reported that "the Inner Loop in Montgomery County is moving without incident". This while my scanner told me about the "incident" at the Mormon Temple responsible for the non-moving traffic. I glean what information I can from as many sources as possible to piece it together myself. There is Metro Traffic Control, Shadow Traffic (MTC's new competitors), WTOP, Walt Starling, and perhaps others. -- rec.nude: your exit to good living along the Information Toll Road. finger bote@access.digex.net for PGP key and an operator will help you. Por via del empedrado de informacion.
Technical Details
Message-ID:
<bote.770437257@access3>Path:
arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!rtp.vnet.net!news1.digex.net!access3!boteReferences:
<2rtu3i$909@search01.news.aol.com> <1994May26.110627.27952@srg.srg.af.mil> <2s2i0g$1t9@linus.mitre.org> <2s7l5b$ejf@clarknet.clark.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1011e5,f09bc74d06e51f27 X-Google-Attributes: gid1011e5,public X-Google-ArrivalTime: 1994-06-01 10:48:10 PST Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!rtp.vnet.net!news1.digex.net!access3!bote From: bote@access.digex.net (John Boteler) Newsgroups: dc.driving Subject: Re: Travel Updates on the Radio Date: 31 May 1994 22:30:49 -0400 Organization: Express Access Public Access UNIX, Greenbelt, Maryland USA Lines: 46 Message-ID: <bote.770437257@access3> References: <2rtu3i$909@search01.news.aol.com> <1994May26.110627.27952@srg.srg.af.mil> <2s2i0g$1t9@linus.mitre.org> <2s7l5b$ejf@clarknet.clark.net> NNTP-Posting-Host: access3.digex.net