3011 36 B362
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
36 PENNSYLVANIA AVE" routeTag="
36" stopTitle="
Naylor Rd Se + Southern Ave Se" stopTag="
2862"> - (http://forums.dctransit.info/#) <direction title="
East to Naylor Rd Station"> <prediction seconds="
928" minutes="
15" epochTime="
1282947586061" isDeparture="
false" dirTag="
36_36v1_1" vehicle="
3011" block="
B362" />
4086 71 N701
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
71 GA AVE-7TH STREET" routeTag="
71" stopTitle="
Georgia Ave + Eastern Ave" stopTag="
16123"> - (http://forums.dctransit.info/#) <direction title="
South to Buzzard Point"> <prediction seconds="
119" minutes="
1" epochTime="
1283344515547" isDeparture="
false" dirTag="
71_71_1" vehicle="
4086" block="
N701" />
Quote from: 79MetroExtraMD on September 01, 2010, 08:37:02 AM
4086 71 N701
- (http://forums.dctransit.info/#) <predictions agencyTitle="WMATA Washington" routeTitle="71 GA AVE-7TH STREET" routeTag="71" stopTitle="Georgia Ave + Eastern Ave" stopTag="16123"> - (http://forums.dctransit.info/#) <direction title="South to Buzzard Point"> <prediction seconds="119" minutes="1" epochTime="1283344515547" isDeparture="false" dirTag="71_71_1" vehicle="4086" block="N701" />
Nextbus was actually up this morning? I noticed that it was down from around 6:30-8:00 on both versions of the Metro website.
I noticed that too. The radio system was down this morning.
APPROXIMATE COORDINATE LOCATIONS
[example: Location: (lowest latitude location) to (highest latitude location) | (lowest longitude location) to (highest longitude location)]
^do know that when I say "lowest" or "highest", it's an approximation and is therefore may not always be true
Annex Division: 38.871 to 38.873 | -76.932 to -76.933
Bladensburg Division: 38.920 to 38.924 | -76.968 to -76.971
Ballston Station: 38.880 to 38.882 | -77.110 to -77.112
Carmen E Turner Facility: 38.940 to 38.941 | -76.877 to -76.878
Four Mile Run Division: 38.841 to 38.844 | -77.053 to -77.054
Landover Division: 38.935 to 38.937 | -76.873 to -76.875
Montgomery Division: 39.045 to 39.047 | -77.107 to -77.109
Northern Division: 38.946 to 38.948 | -77.031 to -77.032
Royal Division: 38.810 to 38.811 | -77.042 to -77.043
West Ox Division: 38.847 to 38.849 | -77.378 to -77.379
Western Division: 38.957 to 38.958 | -77.085
_________________________________________________________________________
[original post]
Found the split between the 6500s in which Montgomery and West Ox get...
Highest Montgomery:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6566" routeTag="K6" dirTag="K6_K6_1" lat="39.046783" lon="-77.108093" secsSinceReport="89" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
Lowest West Ox:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6567" routeTag="null" dirTag="null" lat="38.849281" lon="-77.378746" secsSinceReport="5391" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
___________________________________________________________
6569 on the 1A:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6569" routeTag="1A" dirTag="1A_1A_0" lat="38.849281" lon="-77.378502" secsSinceReport="265" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
6578 seems to be at Western. TBH, if West Ox got only 10 for now, they need more 6500s, there's barely any 6390s/6400s compared to other bus divisions.
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6578" routeTag="null" dirTag="null" lat="38.957958" lon="-77.085373" secsSinceReport="374" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6589 seems to be the highest overall so far
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6589" routeTag="null" dirTag="null" lat="38.941132" lon="-76.878281" secsSinceReport="79009" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Actually, 6592 is the highest.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6592" routeTag="null" dirTag="null" lat="38.941101" lon="-76.878456" secsSinceReport="4389" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I'm very curious as to how many were ordered. Are there going to be any 6600s by year's end ? We'll have to wait and see.
Quote from: OrionFlyer on September 08, 2010, 01:09:25 PM
Actually, 6592 is the highest.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6592" routeTag="null" dirTag="null" lat="38.941101" lon="-76.878456" secsSinceReport="4389" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I'm very curious as to how many were ordered. Are there going to be any 6600s by year's end ? We'll have to wait and see.
I swear, I checked this morning and 6592-6594 didn't show any info, but now it seems like 6593 and 6594 are here now. Which means that 6594 is the highest. At the rate these buses are coming in, I wouldn't be surprised if we saw some 6600s by next week.
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6594" routeTag="null" dirTag="null" lat="38.941158" lon="-76.878242" secsSinceReport="1209" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6589 M4 WM46
- <predictions agencyTitle="WMATA Washington" routeTitle="M4 NEBRASKA AVENUE" routeTag="M4" stopTitle="Nebraska Ave + Reno Rd" stopTag="8613">
- <direction title="South to Tenleytown Station">
<prediction seconds="169" minutes="2" epochTime="1284119740225" isDeparture="false" dirTag="M4_M4c_1" vehicle="6589" block="WM46" />
6584 32 W307
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
32 PENNSYLVANIA AVE" routeTag="
32" stopTitle="
Wisconsin Ave Nw + Woodley Rd Nw" stopTag="
7648"> - (http://forums.dctransit.info/#) <direction title="
West to Friendship Heights Station">
<prediction seconds="
5462" minutes="
91" epochTime="
1284125185642" isDeparture="
false" dirTag="
32_32_0" vehicle="
6584" block="
W307" />
6588 36 W303
6579 36 W305
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
36 PENNSYLVANIA AVE" routeTag="
36" stopTitle="
Wisconsin Ave Nw + Woodley Rd Nw" stopTag="
7648"> - (http://forums.dctransit.info/#) <direction title="
West to Friendship Heights Station"> <prediction seconds="
2951" minutes="
49" epochTime="
1284122674632" isDeparture="
false" dirTag="
36_36_0" vehicle="
6588" block="
W303" /> <prediction seconds="
3875" minutes="
64" epochTime="
1284123598751" isDeparture="
false" dirTag="
36_36_0" vehicle="
6575" block="
W305" />
6578 E2 WE22
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
E2 MIL RD-CROSSTOWN" routeTag="
E2" stopTitle="
Friendship Hts Sta + Bus Bay J" stopTag="
308944"> - (http://forums.dctransit.info/#) <direction title="
West to Friendship Heights Station">
<prediction seconds="
4307" minutes="
71" epochTime="
1284124198343" isDeparture="
false" dirTag="
E2_E2_0" vehicle="
6578" block="
WE22" />
9303 F4
- <predictions agencyTitle="WMATA Washington" routeTitle="F4 NEW CARROLLTON - SILSPG" routeTag="F4" stopTitle="Pg Plaza Station + Bus Bay F" stopTag="14983">
- <direction title="East to New Carrollton Station">
<prediction seconds="34" minutes="0" epochTime="1284156946933" isDeparture="false" dirTag="F4_F4_0" vehicle="9303" block="LF73" />
Looks like 4304 and 4305 may be Northern buses now...
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4304" routeTag="null" dirTag="null" lat="38.947922" lon="-77.032242" secsSinceReport="9255" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4305" routeTag="null" dirTag="null" lat="38.947399" lon="-77.031265" secsSinceReport="1516" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
plus I know it's Friday night (early Saturday morning), and buses usually run later tonight, but according to nextbus, every route (even the 30s, Q4, 70, S line) is out of service. glitch or service change?
I was on NextBus earlier that night, and they said that it would be down from 1 to 1:30; why, I don't remember.
On a side note, how are you guys getting this kind of information? I remember reading in an earlier thread that it has something to do with getting the data in XML format, so how's it done?
yeah looks like 4305 is back at Northern. I hope the others don't follow...
Quote<vehicle id="4305" routeTag="70" dirTag="70_70cv3_1" lat="38.965" lon="-77.027802" secsSinceReport="44" predictable="true" heading="182" speedKmHr="0.0"/>
6168 on the 34
Quote<vehicle id="6168" routeTag="34" dirTag="34_34_1" lat="38.889431" lon="-77.021919" secsSinceReport="37" predictable="true" heading="360" speedKmHr="46.656"/>
3910 42 W427
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
42 MOUNT PLEASANT" routeTag="
42" stopTitle="
I St Nw + 17th St Nw" stopTag="
5946"> - (http://forums.dctransit.info/#) <direction title="
North to Mt Pleasant Via Adams Morgan"> <prediction seconds="
1598" minutes="
26" epochTime="
1284611894419" isDeparture="
false" dirTag="
42_42_1" vehicle="
3910" block="
W427" />
4048 on the Y9!!!Quote<vehicle id="4048" routeTag="Y9" dirTag="Y9_Y9_0" lat="39.084789" lon="-77.0781329" secsSinceReport="284" predictable="true" heading="330" speedKmHr="33.768"/>
4249 on the H11
Quote<vehicle id="4249" routeTag="H11" dirTag="H11_H11_1" lat="38.936951" lon="-76.874992" secsSinceReport="17" predictable="true" heading="218" speedKmHr="0.0"/>
First of the 6600s is here...
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6607" routeTag="null" dirTag="null" lat="38.940994" lon="-76.877968" secsSinceReport="34955" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
What happened to 2386??? I searched it up and got this:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<Error shouldRetry="false">
No data available for vehicle=2386
</Error>
</body>
In other news, 2626 and 2627 have moved to FMR, 4355 remains at Royal, Royal now has 2141-2143. Bladensburg now has 2191 and 2192; 2193-2195 are at CET, possibly in the process of transferring garages.
6600-6607 so far are Western buses
6603 36 W303
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
36 PENNSYLVANIA AVE" routeTag="
36" stopTitle="
M St Nw + Wisconson Ave Nw" stopTag="
6209"> - (http://forums.dctransit.info/#) <direction title="
East to Naylor Rd Station"> <prediction seconds="
356" minutes="
5" epochTime="
1286285975064" isDeparture="
false" dirTag="
36_36_1" vehicle="
6603" block="
W303" />
6607 42 W414
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
42 MOUNT PLEASANT" routeTag="
42" stopTitle="
9th St Nw + G St Nw" stopTag="
5745"> - (http://forums.dctransit.info/#) <direction title="
North to Mt Pleasant Via Adams Morgan"> <prediction seconds="
286" minutes="
4" epochTime="
1286286060000" isDeparture="
true" dirTag="
42_42_1" vehicle="
6607" block="
W414" />
Quote from: NewFlyer9736BCT on October 05, 2010, 12:34:46 AM
What happened to 2386??? I searched it up and got this:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<Error shouldRetry="false">
No data available for vehicle=2386
</Error>
</body>
In other news, 2626 and 2627 have moved to FMR, 4355 remains at Royal, Royal now has 2141-2143. Bladensburg now has 2191 and 2192; 2193-2195 are at CET, possibly in the process of transferring garages.
2386?? that must be the bus that was torched at cet
Quote from: Southern Avenue Annex on October 05, 2010, 06:10:27 PM
Quote from: NewFlyer9736BCT on October 05, 2010, 12:34:46 AM
What happened to 2386??? I searched it up and got this:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<Error shouldRetry="false">
No data available for vehicle=2386
</Error>
</body>
In other news, 2626 and 2627 have moved to FMR, 4355 remains at Royal, Royal now has 2141-2143. Bladensburg now has 2191 and 2192; 2193-2195 are at CET, possibly in the process of transferring garages.
2386?? that must be the bus that was torched at cet
was it in the new paint? that sucks man...
Quote from: NewFlyer9736BCT on October 05, 2010, 11:14:30 PM
Quote from: Southern Avenue Annex on October 05, 2010, 06:10:27 PM
Quote from: NewFlyer9736BCT on October 05, 2010, 12:34:46 AM
What happened to 2386??? I searched it up and got this:
Quote<body copyright="All data copyright WMATA Washington 2010.">
<Error shouldRetry="false">
No data available for vehicle=2386
</Error>
</body>
In other news, 2626 and 2627 have moved to FMR, 4355 remains at Royal, Royal now has 2141-2143. Bladensburg now has 2191 and 2192; 2193-2195 are at CET, possibly in the process of transferring garages.
2386?? that must be the bus that was torched at cet
was it in the new paint? that sucks man...
Yeah but it wasn't 2386 i just saw it recently I don't know what the C40LF is at CET but we are 1 short now
5205 L2 WL16. I kid you not
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
L2 CONNECTICUT AVE" routeTag="
L2" stopTitle="
Connecticut Ave + Chesapeake St" stopTag="
8483"> - (http://forums.dctransit.info/#) <direction title="
North to Chevy Chase Circle"> <prediction seconds="
327" minutes="
5" epochTime="
1286672599017" isDeparture="
false" dirTag="
L2_L2_0" vehicle="
5205" block="
WL16" />
2636 on the 10B
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2636" routeTag="10B" dirTag="10B_10B_0" lat="38.814137" lon="-77.052895" secsSinceReport="65" predictable="true" heading="360" speedKmHr="37.008"/>
<lastTime time="1286769781956"/>
</body>
2422 on the H6 at this time...never saw a 40' bus on that line
Quote<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2422" routeTag="H6" dirTag="H6_H6_0" lat="38.925785" lon="-76.983704" secsSinceReport="1" predictable="true" heading="75" speedKmHr="35.388"/>
<lastTime time="1286770566522"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2422" routeTag="H6" dirTag="H6_H6_0" lat="38.925785" lon="-76.983704" secsSinceReport="1" predictable="true" heading="75" speedKmHr="35.388"/>
<lastTime time="1286770566522"/>
</body>
Quick question, how is this done? There are many times when I'm waiting for a bus and I would like to know what type of bus is coming, thanks!
5205 64 W651
- (http://www.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=1000910&r=64#) <predictions agencyTitle="
WMATA Washington" routeTitle="
64 FT TOTT-PETWORTH" routeTag="
64" stopTitle="
10th St (West Curb) + Pennsylvania" stopTag="
5334">
- (http://www.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=1000910&r=64#) <direction title="
South to Federal Triangle">
<prediction seconds="
439" minutes="
7" epochTime="
1287435437962" isDeparture="
false" dirTag="
64_64_1" vehicle="
5205" block="
W651" />
Huh. Didn't know Western could handle artics. According to Nextbus, 5205 is there right now.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="5205" routeTag="null" dirTag="null" lat="38.958538" lon="-77.0855179" secsSinceReport="10919" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: VIPERZ6 on October 15, 2010, 08:55:27 PM
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2422" routeTag="H6" dirTag="H6_H6_0" lat="38.925785" lon="-76.983704" secsSinceReport="1" predictable="true" heading="75" speedKmHr="35.388"/>
<lastTime time="1286770566522"/>
</body>
Quick question, how is this done? There are many times when I'm waiting for a bus and I would like to know what type of bus is coming, thanks!
You're wasting your breath. I've asked the same thing... no response...
Quote from: RideOn5905 on October 19, 2010, 02:15:42 PM
Quote from: VIPERZ6 on October 15, 2010, 08:55:27 PM
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2422" routeTag="H6" dirTag="H6_H6_0" lat="38.925785" lon="-76.983704" secsSinceReport="1" predictable="true" heading="75" speedKmHr="35.388"/>
<lastTime time="1286770566522"/>
</body>
Quick question, how is this done? There are many times when I'm waiting for a bus and I would like to know what type of bus is coming, thanks!
You're wasting your breath. I've asked the same thing... no response...
here ya go
http://forums.dctransit.info/index.php?topic=1718.0
An Orion V on the S9
<vehicle id="4266" routeTag="S9" dirTag="S9_S9_1" lat="38.97831" lon="-77.0327" secsSinceReport="38" predictable="true" heading="210" speedKmHr="49.86"/>
4278 W13
<vehicle id="4278" routeTag="W13" dirTag="W13_W13_0" lat="38.887505" lon="-77.017723" secsSinceReport="90" predictable="true" heading="106" speedKmHr="0.0"/>
6173 moved to Annex
<vehicle id="6173" routeTag="null" dirTag="null" lat="38.861874" lon="-76.995773" secsSinceReport="88" predictable="false" heading="-4" speedKmHr="0.0"/>
All Royal Blocks on the W19
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4405" routeTag="W19" dirTag="W19_W19c_1" lat="38.832478" lon="-76.986885" secsSinceReport="182" predictable="true" heading="224" speedKmHr="1.584"/>
<vehicle id="4404" routeTag="W19" dirTag="W19_W19c_1" lat="38.801678" lon="-77.0489039" secsSinceReport="36" predictable="true" heading="180" speedKmHr="17.676"/>
<vehicle id="4406" routeTag="W19" dirTag="W19_W19v4_0" lat="38.598839" lon="-77.170212" secsSinceReport="42" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="4399" routeTag="W19" dirTag="W19_W19c_1" lat="38.813061" lon="-77.0497819" secsSinceReport="85" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="4412" routeTag="W19" dirTag="W19_W19_1" lat="38.799477" lon="-77.0490109" secsSinceReport="121" predictable="true" heading="218" speedKmHr="0.0"/>
<lastTime time="1287607548460"/>
</body>
apparently 4278 is at Annex
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4278" routeTag="null" dirTag="null" lat="38.872051" lon="-76.932709" secsSinceReport="13291" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
as well as 4245-4248 that have all recently moved there
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4245" routeTag="34" dirTag="null" lat="38.872269" lon="-76.932632" secsSinceReport="12810" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4246" routeTag="34" dirTag="34_34_1" lat="38.884975" lon="-76.996582" secsSinceReport="350" predictable="true" heading="285" speedKmHr="41.832"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4247" routeTag="null" dirTag="null" lat="38.8723529" lon="-76.933403" secsSinceReport="9950" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4248" routeTag="null" dirTag="null" lat="38.872406" lon="-76.933472" secsSinceReport="14751" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Landover now has 4251, 4252, 4255, and 4256, Annex still has 4257-4259 (coords for 4252 show that it's apparently deadheading to Landover, but I have seen this bus on a Landover route recently)
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4251" routeTag="null" dirTag="null" lat="38.937389" lon="-76.873871" secsSinceReport="12616298" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4252" routeTag="null" dirTag="null" lat="38.916656" lon="-76.922241" secsSinceReport="131" predictable="false" heading="90" speedKmHr="67.572"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4255" routeTag="null" dirTag="null" lat="38.936924" lon="-76.874573" secsSinceReport="5290" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4256" routeTag="P12" dirTag="P12_P12_0" lat="38.8198549" lon="-76.989616" secsSinceReport="49" predictable="true" heading="75" speedKmHr="35.388"/>
</body>
6174 and 6175 are now Annex
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6174" routeTag="null" dirTag="null" lat="38.872601" lon="-76.932846" secsSinceReport="2901" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6175" routeTag="null" dirTag="null" lat="38.8723529" lon="-76.93309" secsSinceReport="1030" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2629 and 2632 are now at FMR (Bladensburg remains with 2630, 2631, 2633, 2634, 2635, and 2637)
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2629" routeTag="null" dirTag="null" lat="38.8443029" lon="-77.054016" secsSinceReport="46008" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2632" routeTag="null" dirTag="null" lat="38.84235" lon="-77.053665" secsSinceReport="11282" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2200-2205 are now at Bladensburg
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2200" routeTag="null" dirTag="null" lat="38.923752" lon="-76.96991" secsSinceReport="20875" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2201" routeTag="null" dirTag="null" lat="38.923035" lon="-76.969315" secsSinceReport="2714" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2202" routeTag="null" dirTag="null" lat="38.922047" lon="-76.969208" secsSinceReport="200" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2203" routeTag="null" dirTag="null" lat="38.922264" lon="-76.9687579" secsSinceReport="3952" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2204" routeTag="null" dirTag="null" lat="38.922348" lon="-76.968895" secsSinceReport="210" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2205" routeTag="null" dirTag="null" lat="38.922348" lon="-76.968933" secsSinceReport="120" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
5205 on the 42 right now
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="5205" routeTag="42" dirTag="42_42_0" lat="38.959003" lon="-77.086426" secsSinceReport="53" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
4293-4297 are back at Northern. apparently it shows that 4295 is still at Annex, but that's most likely bound to change soon.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4293" routeTag="S2" dirTag="null" lat="38.994316" lon="-77.0287479" secsSinceReport="500776" predictable="true" heading="90" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4294" routeTag="null" dirTag="null" lat="38.946274" lon="-77.03228" secsSinceReport="23277" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4295" routeTag="null" dirTag="null" lat="38.8732029" lon="-76.933197" secsSinceReport="32887" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4296" routeTag="null" dirTag="null" lat="38.948086" lon="-77.031998" secsSinceReport="12537" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4297" routeTag="52" dirTag="null" lat="38.96434" lon="-77.03347" secsSinceReport="25074" predictable="true" heading="180" speedKmHr="41.832"/>
</body>
1:35 AM, 6440 on the 36
<vehicle id="6440" routeTag="36" dirTag="36_36_1" lat="38.9152259" lon="-77.067558" secsSinceReport="64" predictable="true" heading="150" speedKmHr="37.008"/>
4278 must've been on borrow it's back at Northern
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4278" routeTag="S1" dirTag="S1_S1_1" lat="38.915997" lon="-77.0365829" secsSinceReport="48" predictable="true" heading="165" speedKmHr="33.768"/>
</body>
Why are artics at Western? Isn't it too small for those buses?
4295 at Western apparently. the other 4290s are all back at Northern.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4295" routeTag="36" dirTag="null" lat="38.958374" lon="-77.085861" secsSinceReport="5969" predictable="true" heading="314" speedKmHr="0.0"/>
</body>
Quote from: OrionFlyer on October 21, 2010, 11:00:09 AM
Why are artics at Western? Isn't it too small for those buses?
that's what we all thought, but apparently we're wrong
Quote from: OrionFlyer on October 21, 2010, 11:00:09 AM
Why are artics at Western? Isn't it too small for those buses?
There's only one there for the time being. 5205. It mainly goes out just on rush hour runs on the 30s and one time was on the 64.
I'm 6000 miles away from Western right now instead of my usual 1 mile, but even so, I'm very skeptical of a report that 5205 is actually at Western, the depot doesn't have any maintenance bays that can support an artic. If I remember when I get up in the morning (6 hours ahead of the US), I'll try and see where this bus is spending the night.
5205 on the 42 doesn't neccesarily == 5205 is at Western.
Quote from: aznboy4305 on October 21, 2010, 07:00:22 PM
5205 on the 42 doesn't neccesarily == 5205 is at Western.
its been on the 30s, 64, 42, and L2, sounds like Western to me
Quote from: aznboy4305 on October 21, 2010, 07:00:22 PM
5205 on the 42 doesn't neccesarily == 5205 is at Western.
It's there. According these NextBus coordinates, it's currently at the Wisconsin Ave side of the division.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="5205" routeTag="null" dirTag="null" lat="38.95829" lon="-77.085236" secsSinceReport="4975" predictable="false" heading="360" speedKmHr="3.204"/>
</body>
When I check it earlier today, it was at the Jennifer St/44th St side. But why is it at Western, is what I want to know. Maybe for some kind of test.
Quote from: OrionFlyer on October 21, 2010, 09:33:28 PM
Quote from: aznboy4305 on October 21, 2010, 07:00:22 PM
5205 on the 42 doesn't neccesarily == 5205 is at Western.
It's there. According these NextBus coordinates, it's currently at the Wisconsin Ave side of the division.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="5205" routeTag="null" dirTag="null" lat="38.95829" lon="-77.085236" secsSinceReport="4975" predictable="false" heading="360" speedKmHr="3.204"/>
</body>
When I check it earlier today, it was at the Jennifer St/44th St side. But why is it at Western, is what I want to know. Maybe for some kind of test.
I'm getting the same thing (it is 4:30 AM right now in DC). Very strange...
Now:
<predictions agencyTitle="WMATA Washington" routeTitle="N2 MASS AVENUE" routeTag="N2" stopTitle="Connecticut Ave Nw + L St Nw" stopTag="6150">
?
<direction title="East to Farragut Square">
<prediction seconds="46" minutes="0" epochTime="1287750299110" isDeparture="false" dirTag="N2_N2_1" vehicle="2083" block="MN06"/>
<prediction seconds="1758" minutes="29" epochTime="1287752011322" isDeparture="false" dirTag="N2_N2_1" vehicle="
5205" block="WE31"/>
<prediction seconds="2924" minutes="48" epochTime="1287753176880" isDeparture="false" dirTag="N2_N2_1" vehicle="6557" block="MN09"/>
<prediction seconds="4044" minutes="67" epochTime="1287754297100" isDeparture="false" dirTag="N2_N2_1" vehicle="4311" block="MN05"/>
</direction>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="
5205" routeTag="N2" dirTag="N2_N2_1" lat="38.9549639" lon="-77.082893" secsSinceReport="122" predictable="true" heading="162" speedKmHr="0.0"/>
</body>
Quote from: 79MetroExtraMD on October 21, 2010, 05:01:27 PM
Quote from: OrionFlyer on October 21, 2010, 11:00:09 AM
Why are artics at Western? Isn't it too small for those buses?
There's only one there for the time being. 5205. It mainly goes out just on rush hour runs on the 30s and one time was on the 64.
Your source please? Until I see picture proof of this I will not believe it. My thinking is that the tracking system was taken off 5205 and was put on another bus and the bus number was not changed in the system when installed. This happened ALL the time at Ride On with fareboxes. Old buses retired, fareboxes were pulled out and put into new buses that were being delivered with the old unit number showing it was still operating. Now I will try and verify if 5205 is REALLY at Western Division :-)
2632 on the 4A
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2632" routeTag="4A" dirTag="4A_4A_0" lat="38.880383" lon="-77.084114" secsSinceReport="25" predictable="true" heading="165" speedKmHr="62.748"/>
</body>
Quote from: rideonrulez on October 22, 2010, 08:44:57 AM
Quote from: 79MetroExtraMD on October 21, 2010, 05:01:27 PM
Quote from: OrionFlyer on October 21, 2010, 11:00:09 AM
Why are artics at Western? Isn't it too small for those buses?
There's only one there for the time being. 5205. It mainly goes out just on rush hour runs on the 30s and one time was on the 64.
Your source please? Until I see picture proof of this I will not believe it. My thinking is that the tracking system was taken off 5205 and was put on another bus and the bus number was not changed in the system when installed. This happened ALL the time at Ride On with fareboxes. Old buses retired, fareboxes were pulled out and put into new buses that were being delivered with the old unit number showing it was still operating. Now I will try and verify if 5205 is REALLY at Western Division :-)
5452's system hasn't worked at all. It still shows it as being at CET although I've seen it running on the 71 and logged in.
Quote from: rideonrulez on October 22, 2010, 08:44:57 AM
Quote from: 79MetroExtraMD on October 21, 2010, 05:01:27 PM
Quote from: OrionFlyer on October 21, 2010, 11:00:09 AM
Why are artics at Western? Isn't it too small for those buses?
There's only one there for the time being. 5205. It mainly goes out just on rush hour runs on the 30s and one time was on the 64.
Your source please? Until I see picture proof of this I will not believe it. My thinking is that the tracking system was taken off 5205 and was put on another bus and the bus number was not changed in the system when installed. This happened ALL the time at Ride On with fareboxes. Old buses retired, fareboxes were pulled out and put into new buses that were being delivered with the old unit number showing it was still operating. Now I will try and verify if 5205 is REALLY at Western Division :-)
Now, this makes perfect sense to me. Not saying 5205 can't be at Western, but I'd be really suprised if it is there.
Quote from: 79MetroExtraMD on October 22, 2010, 06:13:37 PM
Quote from: rideonrulez on October 22, 2010, 08:44:57 AM
Quote from: 79MetroExtraMD on October 21, 2010, 05:01:27 PM
Quote from: OrionFlyer on October 21, 2010, 11:00:09 AM
Why are artics at Western? Isn't it too small for those buses?
There's only one there for the time being. 5205. It mainly goes out just on rush hour runs on the 30s and one time was on the 64.
Your source please? Until I see picture proof of this I will not believe it. My thinking is that the tracking system was taken off 5205 and was put on another bus and the bus number was not changed in the system when installed. This happened ALL the time at Ride On with fareboxes. Old buses retired, fareboxes were pulled out and put into new buses that were being delivered with the old unit number showing it was still operating. Now I will try and verify if 5205 is REALLY at Western Division :-)
5452's system hasn't worked at all. It still shows it as being at CET although I've seen it running on the 71 and logged in.
yes, plus several other buses like 4039 and 4040 have this problem too. although let's see...apparently 6583 and 6608 aren't showing up on Nextbus, so it may be a possibility that one of those has 5205's GPS. speaking of Ride On buses retiring, is it finally over with everything between 5550-5579? I haven't seen them in a while, and as much as I hated them before, I'm missing them.
6608 is not in service yet. Actually it is not even on WMATA property. This one is actually at a contractor lot at the intersection of Route 50 and I-495/95. They always have a good assortment of buses there. I have seen buses from Ride On, WMATA, THE BUS, Fairfax Connector, Howard Transit and MDMTA Commuter.
Quote from: WES on October 25, 2010, 09:38:31 AM
6608 is not in service yet. Actually it is not even on WMATA property. This one is actually at a contractor lot at the intersection of Route 50 and I-495/95. They always have a good assortment of buses there. I have seen buses from Ride On, WMATA, THE BUS, Fairfax Connector, Howard Transit and MDMTA Commuter.
Given the location, could CET have run out of room?
Quote from: Scrabbleship on October 25, 2010, 09:53:09 AM
Quote from: WES on October 25, 2010, 09:38:31 AM
6608 is not in service yet. Actually it is not even on WMATA property. This one is actually at a contractor lot at the intersection of Route 50 and I-495/95. They always have a good assortment of buses there. I have seen buses from Ride On, WMATA, THE BUS, Fairfax Connector, Howard Transit and MDMTA Commuter.
Given the location, could CET have run out of room?
I doubt it. I remember when the Orion VIIs and C40LFR were cming in it was pretty crowded at CET. However, with the LFA's, they seem to have arrived at such a pace that CET was never quite full. I also see that vendor's lot that WES mentioned. My guess is that it's simply as good location as it is pretty industrial over there. I usually look in when driving past on I-495 and there's always buses in there from the various agencies in the area.
If you're driving on I-495 inner loop (south) you can see the lot just ofter passing over route 50.
6324 is currently at Annex.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6324" routeTag="W4" dirTag="null" lat="38.871941" lon="-76.933159" secsSinceReport="26456" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4357 and 4359 are now at Montgomery.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4357" routeTag="K6" dirTag="K6_K6_0" lat="38.970802" lon="-76.998611" secsSinceReport="94" predictable="true" heading="15" speedKmHr="30.564"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4359" routeTag="C2" dirTag="C2_C2_1" lat="38.998001" lon="-76.918182" secsSinceReport="270" predictable="true" heading="75" speedKmHr="70.776"/>
</body>
2631 and 2633 are now at FMR
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2631" routeTag="1A" dirTag="null" lat="38.84301" lon="-77.053802" secsSinceReport="15232" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="2633" routeTag="7W" dirTag="7W_7W_0" lat="38.830334" lon="-77.113899" secsSinceReport="240" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
and 6324 is back at Landover
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6324" routeTag="F4" dirTag="F4_F4_0" lat="38.9690439" lon="-76.973412" secsSinceReport="10" predictable="true" heading="105" speedKmHr="0.0"/>
</body>
well it looks like 6100s are now a thing of the past for Landover. 6176 and 6177 are now at Annex. 6178 still shows that it's at Landover, but the seconds since last report is high so chances are that it's at Annex as well. (and I thought the V5 was Bladensburg only, guess Annex does some runs?)
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6176" routeTag="null" dirTag="null" lat="38.873013" lon="-76.932388" secsSinceReport="4372" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6177" routeTag="V5" dirTag="null" lat="38.872242" lon="-76.932953" secsSinceReport="890" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: NewFlyer9736BCT on October 29, 2010, 08:50:21 AM
well it looks like 6100s are now a thing of the past for Landover. 6176 and 6177 are now at Annex. 6178 still shows that it's at Landover, but the seconds since last report is high so chances are that it's at Annex as well. (and I thought the V5 was Bladensburg only, guess Annex does some runs?)
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6176" routeTag="null" dirTag="null" lat="38.873013" lon="-76.932388" secsSinceReport="4372" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6177" routeTag="V5" dirTag="null" lat="38.872242" lon="-76.932953" secsSinceReport="890" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
The V5 in the morning is split 6 blocks 3 for Bladensburg and 3 for Annex, but in the afternoon its all Bladensburg blocks
4317 on the F4
<vehicle id="4317" routeTag="F4" dirTag="F4_F4_1" lat="38.963158" lon="-76.938972" secsSinceReport="85" predictable="true" heading="270" speedKmHr="104.58"/>
4242 on the H1 this morning
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4242" routeTag="H1" dirTag="H1_H1_0" lat="38.926254" lon="-77.013908" secsSinceReport="153" predictable="true" heading="270" speedKmHr="40.212"/>
</body>
6533 and 6313 both on the C2 this evening.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6533" routeTag="C2" dirTag="C2_C2_0" lat="39.037106" lon="-77.039284" secsSinceReport="137" predictable="true" heading="306" speedKmHr="0.0"/>
<vehicle id="6313" routeTag="C2" dirTag="C2_C2_1" lat="38.995663" lon="-76.886856" secsSinceReport="18" predictable="true" heading="52" speedKmHr="0.0"/>
</body>
6533 is on another Montgomery route; this time, it's the C8.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6533" routeTag="C8" dirTag="C8_C8v2_0" lat="38.987717" lon="-76.956642" secsSinceReport="12" predictable="true" heading="150" speedKmHr="59.544"/>
</body>
You know, this is the third day in a row I've seen 6533 at Montgomery: Monday I reported it on the C2, yesterday I saw it on the J2 but didn't report it, and today... this.
2155 is at Bladensburg
<vehicle id="2155" routeTag="V7" dirTag="V7_V7_0" lat="38.879337" lon="-77.021713" secsSinceReport="35" predictable="true" heading="270" speedKmHr="11.232"/>
6180 is at Northern.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6180" routeTag="null" dirTag="null" lat="38.94817" lon="-77.03228" secsSinceReport="50" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Looks like some of Bladensburg's 30' Orion VII's are on routes they usually aren't today.
3004 on the G8.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="3004" routeTag="G8" dirTag="G8_G8v2_0" lat="38.933071" lon="-76.975052" secsSinceReport="70" predictable="true" heading="90" speedKmHr="0.0"/>
3012 on the 36.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="3012" routeTag="36" dirTag="36_36v1_1" lat="38.895866" lon="-77.033714" secsSinceReport="12" predictable="true" heading="183" speedKmHr="0.0"/>
3014 on the X3
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="3014" routeTag="X3" dirTag="X3_X3_0" lat="38.942368" lon="-77.07666" secsSinceReport="82" predictable="true" heading="150" speedKmHr="25.74"/>
I mean it's going to sound funny when I say this, but every morning when I went to work there would always be a 30 foot Orion VII on the G8 and from what I see, it gets packed. Why is there always a 30 foot bus on the G8 during rush, I don't know. The same thing for the 30s. I have even seen an Orion II on the 30s, which if you think getting a 30 foot bus on the 30s was weird, try getting an Orion II on the 30s...........during rush hour.
I think everything in Bladensburg that's shorter than 60 feet is fair game for the 30s, especially during rush hour.
Quote from: WES on December 03, 2010, 08:55:34 PM
I mean it's going to sound funny when I say this, but every morning when I went to work there would always be a 30 foot Orion VII on the G8 and from what I see, it gets packed. Why is there always a 30 foot bus on the G8 during rush, I don't know. The same thing for the 30s. I have even seen an Orion II on the 30s, which if you think getting a 30 foot bus on the 30s was weird, try getting an Orion II on the 30s...........during rush hour.
This doesn't seem endemic to Bladensburg. When I briefly lived along the 3's in northwest Arlington, there always would be one oddball 30' Orion VII in rush that would be crush loaded leaving Rosslyn. Haven't there also been odd cases where Landover has sent a 3900 on the F4?
Quote from: Scrabbleship on December 03, 2010, 10:38:57 PM
Haven't there also been odd cases where Landover has sent a 3900 on the F4?
I've never seen one, but in the late 90s I rode baby Flxs 5168 and 5169 on the F4 during the PM rush hour.
Quote from: Scrabbleship on December 03, 2010, 10:38:57 PM
Quote from: WES on December 03, 2010, 08:55:34 PM
I mean it's going to sound funny when I say this, but every morning when I went to work there would always be a 30 foot Orion VII on the G8 and from what I see, it gets packed. Why is there always a 30 foot bus on the G8 during rush, I don't know. The same thing for the 30s. I have even seen an Orion II on the 30s, which if you think getting a 30 foot bus on the 30s was weird, try getting an Orion II on the 30s...........during rush hour.
This doesn't seem endemic to Bladensburg. When I briefly lived along the 3's in northwest Arlington, there always would be one oddball 30' Orion VII in rush that would be crush loaded leaving Rosslyn. Haven't there also been odd cases where Landover has sent a 3900 on the F4?
I heard of it happening once in a while. There has been more sightings of the old Orion V B30 dedicated buses on the F4 than 30 footers.
What is it with random buses appearing in different divisions? First we had 6533 hanging out at Montgomery, then we've got 6180 regularly appearing on the 90s, and now this:
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6467" routeTag="10A" dirTag="null" lat="38.968769" lon="-77.036339" secsSinceReport="70" predictable="false" heading="360" speedKmHr="41.832"/>
</body>
Quote from: WES on December 04, 2010, 10:36:23 AM
Quote from: Scrabbleship on December 03, 2010, 10:38:57 PM
Quote from: WES on December 03, 2010, 08:55:34 PM
I mean it's going to sound funny when I say this, but every morning when I went to work there would always be a 30 foot Orion VII on the G8 and from what I see, it gets packed. Why is there always a 30 foot bus on the G8 during rush, I don't know. The same thing for the 30s. I have even seen an Orion II on the 30s, which if you think getting a 30 foot bus on the 30s was weird, try getting an Orion II on the 30s...........during rush hour.
This doesn't seem endemic to Bladensburg. When I briefly lived along the 3's in northwest Arlington, there always would be one oddball 30' Orion VII in rush that would be crush loaded leaving Rosslyn. Haven't there also been odd cases where Landover has sent a 3900 on the F4?
I heard of it happening once in a while. There has been more sightings of the old Orion V B30 dedicated buses on the F4 than 30 footers.
Right after the Orion V's began to be taken off of the B30, they ended up dominating the F4 (and F6). The long length of those routes makes softs seats and such a benefit, kinda like how Montgomery's D40LFR suburbans end up on a lot of long routes (K6, C8, weekday L8) outside of rush hours.
After slumming on the 90 yesterday and this morning, 6180 found its way home today.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6180" routeTag="M6" dirTag="M6_M6_0" lat="38.880573" lon="-76.985313" secsSinceReport="154" predictable="true" heading="258" speedKmHr="0.0"/>
</body>
6406 on the 38B this afternoon.
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="6406" routeTag="38B" dirTag="38B_38B_1" lat="38.881592" lon="-77.111801" secsSinceReport="34" predictable="true" heading="345" speedKmHr="22.5"/>
</body>
ugh...the 4250s can never seem to find a permanent home. let's see, 4256 is back at West Ox, 4257 is now on the 2A, which means it's back at West Ox as well, and 4258 and 4259 are at Montgomery. And that leaves Bladensburg with only 4242, 4254, and 4255 (besides 4200-4209)
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4256" routeTag="null" dirTag="null" lat="38.849445" lon="-77.378433" secsSinceReport="3101" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4257" routeTag="2A" dirTag="2A_2A_0" lat="38.881676" lon="-77.171753" secsSinceReport="47" predictable="true" heading="210" speedKmHr="43.452"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4258" routeTag="null" dirTag="null" lat="39.047199" lon="-77.108017" secsSinceReport="11116" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2010.">
<vehicle id="4259" routeTag="null" dirTag="null" lat="39.046181" lon="-77.107147" secsSinceReport="12582" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
it appears that 3019 and 3020 are FMR buses now
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3019" routeTag="10E" dirTag="10E_10E_1" lat="38.846088" lon="-77.065392" secsSinceReport="79" predictable="true" heading="163" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3020" routeTag="null" dirTag="null" lat="38.842075" lon="-77.0539469" secsSinceReport="2812" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
...and 2052-2057 are now West Ox buses (2056 shows that it's at CET)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2052" routeTag="18H" dirTag="18H_18H_0" lat="38.770439" lon="-77.227509" secsSinceReport="121" predictable="true" heading="270" speedKmHr="28.943999999999996"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2053" routeTag="18S" dirTag="18S_18S_0" lat="38.766724" lon="-77.170181" secsSinceReport="35" predictable="true" heading="75" speedKmHr="14.471999999999998"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2054" routeTag="18P" dirTag="null" lat="38.848511" lon="-77.378883" secsSinceReport="3183" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2055" routeTag="17F" dirTag="17F_17F_1" lat="38.810558" lon="-77.251312" secsSinceReport="349" predictable="true" heading="90" speedKmHr="4.824"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2057" routeTag="17F" dirTag="17F_17F_1" lat="38.867184" lon="-77.056709" secsSinceReport="93" predictable="true" heading="110" speedKmHr="0.0"/>
</body>
however, 2064 seems to have escaped West Ox and gone to Western
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2064" routeTag="32" dirTag="32_32c_0" lat="38.861244" lon="-76.96907" secsSinceReport="39" predictable="true" heading="330" speedKmHr="3.204"/>
</body>
2464 X2 BX29
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
X2 Benning RD-H" routeTag="
X2" stopTitle="
H St Nw + 7th St Nw" stopTag="
5801"> - (http://forums.dctransit.info/#) <direction title="
East to Minnesota Ave Station"> <prediction epochTime="
1294674261858" seconds="
532" minutes="
8" isDeparture="
false" dirTag="
X2_X2_0" vehicle="
2464" block="
BX29" />
Not dead yet
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
32 Penns Ave" routeTag="
32" stopTitle="
Wisconsin Ave Nw + Woodley Rd Nw" stopTag="
7648"> - (http://forums.dctransit.info/#) <direction title="
West to McLean Gardens"> <prediction epochTime="
1294700422070" seconds="
283" minutes="
4" isDeparture="
false" dirTag="
32_32cv2_0" vehicle="
9357" block="
B362" />
Well, this is... odd...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4343" routeTag="79" dirTag="79_79_0" lat="38.984554" lon="-77.026718" secsSinceReport="25" predictable="true" heading="165" speedKmHr="22.5"/>
</body>
According to Nextbus, the following Orion VIIs are at Bladensburg (most likely for rehab/repaint?)
2504, 2506, 2536, 2539, 2543, 2546, 2556, 2560, 2561, 2562, 2571, 2577, 2580, 2584, 2588, 2598, 2608, 2610, 2630, and 2679
as for the 30-foot ones, 3001-3018 are at Bladensburg for revenue service, so there's no telling when they will be in rehab, and 3019-3035 are all at FMR.
edit 3/25/2012 (for notes): funny how 3018 turned out that it was getting rehabbed right at the time 3019 and 3020 moved to FMR, and moved to FMR right after the rehab. also 2679 has not been rehabbed at the time, instead it was repowered with the C Gas engine
Quote from: 79MetroExtraMD on January 10, 2011, 05:56:57 PM
Not dead yet
- (http://forums.dctransit.info/#) <predictions agencyTitle="WMATA Washington" routeTitle="32 Penns Ave" routeTag="32" stopTitle="Wisconsin Ave Nw + Woodley Rd Nw" stopTag="7648"> - (http://forums.dctransit.info/#) <direction title="West to McLean Gardens"> <prediction epochTime="1294700422070" seconds="283" minutes="4" isDeparture="false" dirTag="32_32cv2_0" vehicle="9357" block="B362" />
:) (Face gushing with elation) You mean there's a flicker of hope I could actually land a Metro B when I come up in April?
2210 at Montgomery and 2147 at Western, most likely temporary though, but who knows.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2210" routeTag="L2" dirTag="null" lat="39.046234" lon="-77.107002" secsSinceReport="145" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2147" routeTag="32" dirTag="null" lat="38.957989" lon="-77.085373" secsSinceReport="12485" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
once again, 4256 and 4257 have moved, this time to Royal.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4256" routeTag="null" dirTag="null" lat="38.811054" lon="-77.042816" secsSinceReport="467" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4257" routeTag="null" dirTag="null" lat="38.811661" lon="-77.042885" secsSinceReport="8638" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4242 on the 64
<vehicle id="4242" routeTag="64" dirTag="64_64_0" lat="38.892181" lon="-77.027939" secsSinceReport="63" predictable="true" heading="337" speedKmHr="1.584"/>
This one needs some explaining:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6148" routeTag="P12" dirTag="P12_P12_1" lat="38.8273889" lon="-76.977783" secsSinceReport="5" predictable="true" heading="300" speedKmHr="51.48"/>
</body>
Quote from: RideOn5905 on January 30, 2011, 12:57:58 PM
This one needs some explaining:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6148" routeTag="P12" dirTag="P12_P12_1" lat="38.8273889" lon="-76.977783" secsSinceReport="5" predictable="true" heading="300" speedKmHr="51.48"/>
</body>
well, you see, 6148 apparently is back at Landover...for now
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6148" routeTag="null" dirTag="null" lat="38.937553" lon="-76.874992" secsSinceReport="226" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
talk about blast from the past
Not anymore, it isn't. Oh, well.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6148" routeTag="A8" dirTag="A8_A8_0" lat="38.859619" lon="-76.995041" secsSinceReport="227" predictable="true" heading="195" speedKmHr="37.008"/>
</body>
And it seems that 4260 has joined 4258-59 at Montgomery.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4260" routeTag="C2" dirTag="null" lat="38.905464" lon="-77.021889" secsSinceReport="0" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
2801 on the X3, all signs set to "Not in Service".
Apparently, 2165 is a Montgomery bus:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2165" routeTag="C4" dirTag="C4_C4_1" lat="39.053825" lon="-77.093002" secsSinceReport="84" predictable="true" heading="90" speedKmHr="41.832"/>
</body>
4244, 4246, and 4247 at Northern for now
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4244" routeTag="null" dirTag="null" lat="38.947262" lon="-77.031441" secsSinceReport="107" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4246" routeTag="92" dirTag="92_92_1" lat="38.858685" lon="-76.968475" secsSinceReport="55" predictable="true" heading="210" speedKmHr="32.184"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4247" routeTag="null" dirTag="null" lat="38.948223" lon="-77.031967" secsSinceReport="109" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
and 2165 back at Bburg
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2165" routeTag="null" dirTag="null" lat="38.922073" lon="-76.968964" secsSinceReport="15438" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2151 on the R1:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2151" routeTag="R1" dirTag="R1_R1_0" lat="39.002289" lon="-76.972153" secsSinceReport="65" predictable="true" heading="360" speedKmHr="19.296"/>
</body>
EDIT: And 4247 is back at Annex.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4247" routeTag="A6" dirTag="A6_A6_0" lat="38.827003" lon="-76.994026" secsSinceReport="4" predictable="true" heading="252" speedKmHr="1.584"/>
</body>
What is this I don't even...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="1208" routeTag="X9" dirTag="X9_X9_1" lat="38.894379" lon="-76.912056" secsSinceReport="98" predictable="true" heading="286" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on February 16, 2011, 05:20:13 PM
What is this I don't even...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="1208" routeTag="X9" dirTag="X9_X9_1" lat="38.894379" lon="-76.912056" secsSinceReport="98" predictable="true" heading="286" speedKmHr="0.0"/>
</body>
when I head out tomorrow, I will see what this so-called 1208 really is. something tells me that it's a C40LF (preferrably a John Deere one :)) with a non-working GPS unit that recently got replaced with this one but for some reason it's being identified as 1208. who knows...
Quote from: NewFlyer9736BCT on February 17, 2011, 10:59:19 AM
Quote from: RideOn5905 on February 16, 2011, 05:20:13 PM
What is this I don't even...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="1208" routeTag="X9" dirTag="X9_X9_1" lat="38.894379" lon="-76.912056" secsSinceReport="98" predictable="true" heading="286" speedKmHr="0.0"/>
</body>
when I head out tomorrow, I will see what this so-called 1208 really is. something tells me that it's a C40LF (preferrably a John Deere one :)) with a non-working GPS unit that recently got replaced with this one but for some reason it's being identified as 1208. who knows...
You may be right. Whatever it is, it's on the X9 again...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="1208" routeTag="X9" dirTag="X9_X9_0" lat="38.900154" lon="-77.013412" secsSinceReport="205" predictable="true" heading="60" speedKmHr="14.471999999999998"/>
</body>
4343 on the 79
- <predictions agencyTitle="WMATA Washington" routeTitle="79 Georgia Ave" routeTag="79" stopTitle="Silver Spring Station + Bus Bay I" stopTag="16714">
- <direction title="South to Archives">
<prediction epochTime="1298069700000" seconds="227" minutes="3" isDeparture="true" dirTag="79_79_0" vehicle="4343" block="B777" />
...not dead yet?!?!?!?!?
<vehicle id="9742" routeTag="H8" dirTag="H8_H8_1" lat="38.940689" lon="-77.001022" secsSinceReport="21" predictable="true" heading="75" speedKmHr="40.212"/>
I'm starting to think there are some buses with GPS units from other buses that haven't been renumbered. Also, there are other phantom bus numbers showing up. I also wonder if these number show up on their fixed end CAD/AVL at BOCC.
Quote from: 79MetroExtraMD on February 21, 2011, 07:41:17 PM
I'm starting to think there are some buses with GPS units from other buses that haven't been renumbered.
Well... That possibility (which seems quite possible to me) has been suggested way back when folks were posting about Ikaurus #5205 being assigned to Western.
I went to Mt Pleasant shortly after seeing "9742" on nextbus. Apparently, it was none other than 3766. I waited there until I saw the same bus twice, first it was 3770, then 3766, then 6476, then 3770 again. Looking at the H8 at this very moment on nextbus, you see all those buses that I mentioned, but instead of 3766, it says 9742.
well so much for that, but man how wild that would have been if she was kept for revenue service
It's due time for a better AVL system that is much more reliable than the current one. There was an RFP out for a better integrated system but it's gone now and no idea whether it was cancelled or what. What I've noticed is that these special schedules don't seem to reflect too well on the public side in trying to track a bus since it'll probably load up another route that isn't on the current schedule day or won't track it at all.
5402 was on the D8???????????
<vehicle id="5402" routeTag="D8" dirTag="null" lat="38.922981" lon="-76.968826" secsSinceReport="35" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on February 25, 2011, 03:52:47 PM
5402 was on the D8???????????
<vehicle id="5402" routeTag="D8" dirTag="null" lat="38.922981" lon="-76.968826" secsSinceReport="35" predictable="false" heading="-4" speedKmHr="0.0"/>
That could be true. There was one on the 80 couple months back.
2170 K6
<vehicle id="2170" routeTag="K6" dirTag="K6_K6_1" lat="39.025417" lon="-76.980408" secsSinceReport="61" predictable="true" heading="135" speedKmHr="49.86"/>
3006 H4
<vehicle id="3006" routeTag="H4" dirTag="H4_H4_1" tripTag="2729499" lat="38.929939" lon="-77.011559" secsSinceReport="9" predictable="true" heading="135" speedKmHr="14.471999999999998"/>
2125 90
<vehicle id="2125" routeTag="90" dirTag="90_90_1" tripTag="2719005" lat="38.916958" lon="-77.028847" secsSinceReport="74" predictable="true" heading="75" speedKmHr="30.564"/>
2071 on the 23C.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2071" routeTag="23C" dirTag="23C_23Cc_0" lat="38.838306" lon="-77.084778" secsSinceReport="259" predictable="true" heading="165" speedKmHr="43.452"/>
</body>
4300 R2
<vehicle id="4300" routeTag="R2" dirTag="R2_R2_0" tripTag="2746022" lat="38.972977" lon="-76.979256" secsSinceReport="71" predictable="true" heading="7" speedKmHr="1.584"/>
6188 on the 92.
<vehicle id="6188" routeTag="92" dirTag="null" lat="38.872959" lon="-76.932808" secsSinceReport="24" predictable="false" heading="360" speedKmHr="3.204"/>
GPS unit replacement? or there's really an artic on the H8. I'll go with the first one...
<vehicle id="5207" routeTag="H8" dirTag="H8_H8_0" tripTag="2750633" lat="38.922237" lon="-76.992699" secsSinceReport="3" predictable="true" heading="73" speedKmHr="1.584"/>
Quote from: NewFlyer9736BCT on April 10, 2011, 09:24:36 PM
GPS unit replacement? or there's really an artic on the H8. I'll go with the first one...
<vehicle id="5207" routeTag="H8" dirTag="H8_H8_0" tripTag="2750633" lat="38.922237" lon="-76.992699" secsSinceReport="3" predictable="true" heading="73" speedKmHr="1.584"/>
It's as likely as the time when some had 5205 being at Western. I'd bet the rent that it was never there.
6132 H8
gotta love that H8, always find something interesting on it on nextbus
<vehicle id="6132" routeTag="H8" dirTag="H8_H8_1" lat="38.931339" lon="-77.038338" secsSinceReport="113" predictable="true" heading="218" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on April 29, 2011, 07:19:00 AM
6132 H8
gotta love that H8, always find something interesting on it on nextbus
<vehicle id="6132" routeTag="H8" dirTag="H8_H8_1" lat="38.931339" lon="-77.038338" secsSinceReport="113" predictable="true" heading="218" speedKmHr="0.0"/>
Oh yeah. That's that Annex block that does the P17 then the H8, then the S41. It's block PP45.
Looks like I've found another GPS glitch:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9821" routeTag="92" dirTag="92_92_1" tripTag="2719224" lat="38.876396" lon="-76.994797" secsSinceReport="84" predictable="true" heading="90" speedKmHr="17.676"/>
</body>
Quote from: RideOn5905 on April 30, 2011, 08:53:04 PM
Looks like I've found another GPS glitch:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9821" routeTag="92" dirTag="92_92_1" tripTag="2719224" lat="38.876396" lon="-76.994797" secsSinceReport="84" predictable="true" heading="90" speedKmHr="17.676"/>
</body>
weird...last time I checked 9821 (like a couple weeks ago), it said the bus no longer existed.
Quote from: NewFlyer9736BCT on April 30, 2011, 11:04:12 PM
Quote from: RideOn5905 on April 30, 2011, 08:53:04 PM
Looks like I've found another GPS glitch:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9821" routeTag="92" dirTag="92_92_1" tripTag="2719224" lat="38.876396" lon="-76.994797" secsSinceReport="84" predictable="true" heading="90" speedKmHr="17.676"/>
</body>
weird...last time I checked 9821 (like a couple weeks ago), it said the bus no longer existed.
Metro is using other Orbital modules from retired buses for ones that fail or just don't work properly (which seems to be on some of the newer buses). They just haven't renumbered them to the current vehicle. Plus, that's probably why alot of the LFAs have the older radio displays than some with newer screens. Also, there is supposed to be an upgrade of the components in the next fiscal year so hopefully things will get better.
7003 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7003" routeTag="null" dirTag="null" lat="38.922844" lon="-76.971237" secsSinceReport="11061" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7005 is at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7005" routeTag="null" dirTag="null" lat="38.936096" lon="-76.8747099" secsSinceReport="136" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I saw 7005 At new carrolton around 10, testing.
6363 on the J9.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6363" routeTag="J9" dirTag="J9_J9_0" tripTag="2741594" lat="38.999237" lon="-77.097939" secsSinceReport="93" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
2089 on the 79. (Ironically, it was listed beneath 2809.)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2089" routeTag="79" dirTag="79_79_1" tripTag="2713424" lat="38.892731" lon="-77.02388" secsSinceReport="43" predictable="true" heading="0" speedKmHr="0.0"/>
</body>
EDIT: And "9821" on the 96.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9821" routeTag="96" dirTag="96_96v1_1" tripTag="2726466" lat="38.923283" lon="-77.057411" secsSinceReport="131" predictable="true" heading="298" speedKmHr="0.0"/>
</body>
And wouldn't you now it, we now have another one...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9828" routeTag="G2" dirTag="G2_G2_1" tripTag="2749345" lat="38.909752" lon="-77.015198" secsSinceReport="123" predictable="true" heading="360" speedKmHr="20.916"/>
</body>
possibility that these 9800s are some of the new 7000s? i'm starting to think so
i'm just gonna leave this here...
<vehicle id="2461" routeTag="110" dirTag="null" lat="38.941238" lon="-76.877724" secsSinceReport="82520" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on May 13, 2011, 12:51:03 PM
i'm just gonna leave this here...
<vehicle id="2461" routeTag="110" dirTag="null" lat="38.941238" lon="-76.877724" secsSinceReport="82520" predictable="false" heading="-4" speedKmHr="0.0"/>
I think that's the Bladensburg test route they have in the system to see if everything works. I think the list goes from 110 to 118 IIRC.
4085 on the L8??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4085" routeTag="L8" dirTag="L8_L8_0" tripTag="2728763" lat="38.963047" lon="-77.082748" secsSinceReport="100" predictable="true" heading="40" speedKmHr="0.0"/>
</body>
5207 on H8 <body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5207" routeTag="H8" dirTag="H8_H8_0" tripTag="2750487" lat="38.919983" lon="-76.996162" secsSinceReport="13" predictable="true" heading="205" speedKmHr="0.0"/>
</body>
I've noticed something recently through nextbus: 4250 seems to ALWAYS be on the T18, 2025 is ALWAYS on the F14, and the lower 2300s (2300-2311 or so) seem to ALWAYS be on the G8. just saying...
oh, and 4085 seems to be on the Q4 right now
<vehicle id="4085" routeTag="Q4" dirTag="Q4_Q4_1" tripTag="2716974" lat="39.040268" lon="-77.0561139" secsSinceReport="14" predictable="true" heading="120" speedKmHr="17.676"/>
and what is this, I don't even...
<vehicle id="2574" routeTag="110" dirTag="110_PATBL_0" lat="38.922127" lon="-76.971207" secsSinceReport="1919" predictable="true" heading="218" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on May 19, 2011, 11:23:07 AM
I've noticed something recently through nextbus: 4250 seems to ALWAYS be on the T18, 2025 is ALWAYS on the F14, and the lower 2300s (2300-2311 or so) seem to ALWAYS be on the G8. just saying...
oh, and 4085 seems to be on the Q4 right now
<vehicle id="4085" routeTag="Q4" dirTag="Q4_Q4_1" tripTag="2716974" lat="39.040268" lon="-77.0561139" secsSinceReport="14" predictable="true" heading="120" speedKmHr="17.676"/>
and what is this, I don't even...
<vehicle id="2574" routeTag="110" dirTag="110_PATBL_0" lat="38.922127" lon="-76.971207" secsSinceReport="1919" predictable="true" heading="218" speedKmHr="0.0"/>
I've also noticed that 4374 always seems to be on the B29.
4245 on the X2.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4245" routeTag="X2" dirTag="X2_X2_0" tripTag="2721274" lat="38.900127" lon="-77.035957" secsSinceReport="140" predictable="true" heading="90" speedKmHr="4.824"/>
</body>
According to Nextbus, the following FMR Orion VIIs are at Bladensburg (possibly for rehab):
2516 2523 2529
2530 2538 2554
2566 2574* 2575
2576 2581 2593
2604 2605 2620
2637 2642 3019
*This bus was on the "110" test route, so it could be almost done.
Also, 2463 is apparently near Martin State Airport:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2463" routeTag="null" dirTag="null" lat="39.329155" lon="-76.427338" secsSinceReport="1298143" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Well, look what the cat dragged in!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3901" routeTag="A12" dirTag="A12_A12_1" tripTag="2749881" lat="38.917149" lon="-76.881569" secsSinceReport="94" predictable="true" heading="45" speedKmHr="38.592"/>
</body>
Quote from: RideOn5905 on May 24, 2011, 12:46:52 PM
According to Nextbus, the following FMR Orion VIIs are at Bladensburg (possibly for rehab):
2516 2523 2529
2530 2538 2554
2566 2574* 2575
2576 2581 2593
2604 2605 2620
2637 2642 3019
*This bus was on the "110" test route, so it could be almost done.
Also, 2463 is apparently near Martin State Airport:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2463" routeTag="null" dirTag="null" lat="39.329155" lon="-76.427338" secsSinceReport="1298143" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Well, look what the cat dragged in!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3901" routeTag="A12" dirTag="A12_A12_1" tripTag="2749881" lat="38.917149" lon="-76.881569" secsSinceReport="94" predictable="true" heading="45" speedKmHr="38.592"/>
</body>
you remind me of me, lol
btw 3019 is back at FMR, and you forgot 2559, 2588, and 3031
_____________________________
as for the Neo tics...5309 is (of course) still being shown at Bladensburg,
but looks like another rehab is on the way, 5316!<vehicle id="5316" routeTag="70" dirTag="null" lat="38.920971" lon="-76.970505" secsSinceReport="4070532" predictable="false" heading="-4" speedKmHr="0.0"/>5302, 5312, and 5321 are not being shown due to too much time without having a GPS update, 5320 is getting there too (I think the time out is around 32 million seconds)
EDIT - apparently 5316 was not rehabbed...
2574 is back at Four Mile Run; possibly freshly rehabbed.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2574" routeTag="null" dirTag="null" lat="38.841827" lon="-77.053841" secsSinceReport="14358" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: ...and 2559 has taken its place at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2559" routeTag="null" dirTag="null" lat="38.922871" lon="-76.970924" secsSinceReport="393616" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
DOUBLE EDIT: ...and I completely forgot to report 2538; it, too, has returned to Four Mile Run.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2538" routeTag="4B" dirTag="null" lat="38.842899" lon="-77.053879" secsSinceReport="151" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2566 and 2576 have also returned to FMR. 2550 and 2580 (both already rehabbed) are back at Bladensburg, possibly for some repairs.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2566" routeTag="25B" dirTag="null" lat="38.843174" lon="-77.054123" secsSinceReport="6694" predictable="false" heading="-4" speedKmHr="0.0"/></body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2576" routeTag="23A" dirTag="23A_23A_1" tripTag="2736885" lat="38.925621" lon="-77.225166" secsSinceReport="2" predictable="true" heading="135" speedKmHr="28.943999999999996"/></body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2550" routeTag="7A" dirTag="null" lat="38.920918" lon="-76.970329" secsSinceReport="199607" predictable="false" heading="-4" speedKmHr="0.0"/></body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2580" routeTag="null" dirTag="null" lat="38.922047" lon="-76.971207" secsSinceReport="19483" predictable="false" heading="-4" speedKmHr="0.0"/></body>
Judging by their seconds count, I'd say 3004 and 3013 are being rehabbed as well.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3004" routeTag="U4" dirTag="null" lat="38.923309" lon="-76.970299" secsSinceReport="908223" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3013" routeTag="null" dirTag="null" lat="38.9214399" lon="-76.970192" secsSinceReport="281194" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
2653 now at Bladensburg
<vehicle id="2653" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970398" secsSinceReport="802591" predictable="false" heading="-4" speedKmHr="0.0"/>
looks like the 2700s are finally starting their rehab as well. so far we have 2712, 2714, and 2717 at Bladensburg.
<vehicle id="2712" routeTag="5A" dirTag="null" lat="38.922897" lon="-76.971031" secsSinceReport="179696" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2714" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970467" secsSinceReport="172655" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2717" routeTag="null" dirTag="null" lat="38.9231989" lon="-76.970436" secsSinceReport="77" predictable="false" heading="-4" speedKmHr="0.0"/>
that said, here's the current list of FMR Orion VIIs at Bladensburg for (possible) rehab
2516, 2523, 2529, 2530, 2554, 2559, 2575, 2581, 2588, 2593, 2604, 2605, 2620, 2637, 2642, 2653, 2712, 2714, 2717, 3031
I saw 2714 yesterday on the 5A in Rosslyn.
4289 on the 36.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4289" routeTag="36" dirTag="36_36_0" tripTag="2751214" lat="38.873039" lon="-76.9694899" secsSinceReport="17" predictable="true" heading="285" speedKmHr="8.028"/>
</body>
EDIT: And 4273 on the 64.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4273" routeTag="64" dirTag="64_64_1" tripTag="2731007" lat="38.954906" lon="-77.00946" secsSinceReport="93" predictable="true" heading="285" speedKmHr="11.232"/>
</body>
2030 23C
<vehicle id="2030" routeTag="23C" dirTag="23C_23Cc_0" tripTag="2736831" lat="38.852798" lon="-77.090279" secsSinceReport="90" predictable="true" heading="45" speedKmHr="35.388"/>
2038 on the 92.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2038" routeTag="92" dirTag="92_92_1" tripTag="2718997" lat="38.87458" lon="-76.991539" secsSinceReport="154" predictable="true" heading="179" speedKmHr="0.0"/>
</body>
EDIT: And... 3769 on the S4??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3769" routeTag="S4" dirTag="S4_S4_1" tripTag="2713836" lat="38.961231" lon="-77.036484" secsSinceReport="9" predictable="true" heading="165" speedKmHr="27.324"/>
</body>
DOUBLE EDIT: Another one?!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3768" routeTag="S2" dirTag="S2_S2cv3_0" lat="38.892731" lon="-77.026016" secsSinceReport="239" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
5316 back at Northern already?! I wonder if it was rehabbed, be on the lookout for this one
<vehicle id="5316" routeTag="null" dirTag="null" lat="38.947235" lon="-77.031441" secsSinceReport="15478" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on June 07, 2011, 02:19:30 PM
2653 now at Bladensburg
<vehicle id="2653" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970398" secsSinceReport="802591" predictable="false" heading="-4" speedKmHr="0.0"/>
looks like the 2700s are finally starting their rehab as well. so far we have 2712, 2714, and 2717 at Bladensburg.
<vehicle id="2712" routeTag="5A" dirTag="null" lat="38.922897" lon="-76.971031" secsSinceReport="179696" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2714" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970467" secsSinceReport="172655" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2717" routeTag="null" dirTag="null" lat="38.9231989" lon="-76.970436" secsSinceReport="77" predictable="false" heading="-4" speedKmHr="0.0"/>
that said, here's the current list of FMR Orion VIIs at Bladensburg for (possible) rehab
2516, 2523, 2529, 2530, 2554, 2559, 2575, 2581, 2588, 2593, 2604, 2605, 2620, 2637, 2642, 2653, 2712, 2714, 2717, 3031
how do you tell if the bus is at what division?
Quote from: DCAreaTransitFan on June 11, 2011, 06:59:08 PM
Quote from: NewFlyer9736BCT on June 07, 2011, 02:19:30 PM
2653 now at Bladensburg
<vehicle id="2653" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970398" secsSinceReport="802591" predictable="false" heading="-4" speedKmHr="0.0"/>
looks like the 2700s are finally starting their rehab as well. so far we have 2712, 2714, and 2717 at Bladensburg.
<vehicle id="2712" routeTag="5A" dirTag="null" lat="38.922897" lon="-76.971031" secsSinceReport="179696" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2714" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970467" secsSinceReport="172655" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2717" routeTag="null" dirTag="null" lat="38.9231989" lon="-76.970436" secsSinceReport="77" predictable="false" heading="-4" speedKmHr="0.0"/>
that said, here's the current list of FMR Orion VIIs at Bladensburg for (possible) rehab
2516, 2523, 2529, 2530, 2554, 2559, 2575, 2581, 2588, 2593, 2604, 2605, 2620, 2637, 2642, 2653, 2712, 2714, 2717, 3031
how do you tell if the bus is at what division?
Coordinates for each division are on the first page.
In other news, 2182 on the K6.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2182" routeTag="K6" dirTag="K6_K6_0" tripTag="2748379" lat="38.982296" lon="-76.988495" secsSinceReport="93" predictable="true" heading="360" speedKmHr="43.452"/>
</body>
EDIT: Same route, different day. This time, it's 4285.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4285" routeTag="K6" dirTag="K6_K6_1" tripTag="2748529" lat="39.015518" lon="-76.977928" secsSinceReport="110" predictable="true" heading="180" speedKmHr="1.584"/>
</body>
2554 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2554" routeTag="null" dirTag="null" lat="38.842789" lon="-77.052368" secsSinceReport="2285" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And 2592 has moved to Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2592" routeTag="null" dirTag="null" lat="38.922844" lon="-76.971138" secsSinceReport="35095" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2460's GPS finally updated, just 2462 to go...
<vehicle id="2460" routeTag="null" dirTag="null" lat="38.922951" lon="-76.971275" secsSinceReport="2219" predictable="false" heading="-4" speedKmHr="0.0"/>
2461 showing that it's at Bburg recently, sign of things to come? hope so...
<vehicle id="2461" routeTag="null" dirTag="null" lat="38.922924" lon="-76.971313" secsSinceReport="5724" predictable="false" heading="-4" speedKmHr="0.0"/>
and check out the coords of 2464, it's at Cummins Power Systems in Hanover, MD.
<vehicle id="2464" routeTag="null" dirTag="null" lat="39.156731" lon="-76.663521" secsSinceReport="12691" predictable="false" heading="-4" speedKmHr="0.0"/>
9835 on the Z6??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9835" routeTag="Z6" dirTag="Z6_Z6_1" lat="39.0451089" lon="-76.981216" secsSinceReport="43" predictable="true" heading="120" speedKmHr="32.184"/>
</body>
Quote from: RideOn5905 on June 14, 2011, 02:34:54 PM
9835 on the Z6??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9835" routeTag="Z6" dirTag="Z6_Z6_1" lat="39.0451089" lon="-76.981216" secsSinceReport="43" predictable="true" heading="120" speedKmHr="32.184"/>
</body>
Looks like another GPS unit got recycled. A few buses have really faulty GPS units and theyre taking ones from the Flxs and putting them on the buses, but aren't updating the fleet numbers.
Nothing out of the ordinary, but pay close attention to the speed:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2018" routeTag="B25" dirTag="B25_B25_0" lat="38.951084" lon="-76.742165" secsSinceReport="127" predictable="true" heading="150" speedKmHr="299.304"/>
</body>
Quote from: RideOn5905 on June 17, 2011, 12:57:30 PM
Nothing out of the ordinary, but pay close attention to the speed:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2018" routeTag="B25" dirTag="B25_B25_0" lat="38.951084" lon="-76.742165" secsSinceReport="127" predictable="true" heading="150" speedKmHr="299.304"/>
</body>
Lol. 185 mph. Must have been one really quick trip to Bowie.
I agree that WMATA's Orion VI's are fast buses and they'd certainly have the opportunity to run full speed on Landover's B routes. However, I'm thinking that GPS unit may be a wee bit faulty as the speed listed equates to roughly 185 MPH:-).
2580 and 2588 back at FMR. 2580 (as well as 2550) were already rehabbed but were sent to Bladensburg again for some reason, but now 2580 is back. 2588 has been at Bladensburg for apparently the longest time out of the other 2500s, the GPS time since last report was over 20 million seconds before finally updating around a couple of weeks ago. anyways they are both back at FMR.
<vehicle id="2580" routeTag="null" dirTag="null" lat="38.84301" lon="-77.053802" secsSinceReport="13409" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2588" routeTag="null" dirTag="null" lat="38.842873" lon="-77.053879" secsSinceReport="13297" predictable="false" heading="-4" speedKmHr="0.0"/>
3028 now at Bladensburg
<vehicle id="3028" routeTag="null" dirTag="null" lat="38.9231989" lon="-76.970467" secsSinceReport="274" predictable="false" heading="-4" speedKmHr="0.0"/>
3002 on the H8.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3002" routeTag="H8" dirTag="H8_H8_0" lat="38.921661" lon="-76.993637" secsSinceReport="9" predictable="true" heading="349" speedKmHr="0.0"/>
</body>
2589 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2589" routeTag="23C" dirTag="null" lat="38.923172" lon="-76.970505" secsSinceReport="22330" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2617 and 2707 also at Bladensburg
<vehicle id="2617" routeTag="null" dirTag="null" lat="38.9231989" lon="-76.970436" secsSinceReport="282003" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2707" routeTag="5A" dirTag="null" lat="38.923172" lon="-76.970398" secsSinceReport="23283" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: DCAreaTransitFan on June 11, 2011, 06:59:08 PM
Quote from: NewFlyer9736BCT on June 07, 2011, 02:19:30 PM
2653 now at Bladensburg
<vehicle id="2653" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970398" secsSinceReport="802591" predictable="false" heading="-4" speedKmHr="0.0"/>
looks like the 2700s are finally starting their rehab as well. so far we have 2712, 2714, and 2717 at Bladensburg.
<vehicle id="2712" routeTag="5A" dirTag="null" lat="38.922897" lon="-76.971031" secsSinceReport="179696" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2714" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970467" secsSinceReport="172655" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2717" routeTag="null" dirTag="null" lat="38.9231989" lon="-76.970436" secsSinceReport="77" predictable="false" heading="-4" speedKmHr="0.0"/>
that said, here's the current list of FMR Orion VIIs at Bladensburg for (possible) rehab
2516, 2523, 2529, 2530, 2554, 2559, 2575, 2581, 2588, 2593, 2604, 2605, 2620, 2637, 2642, 2653, 2712, 2714, 2717, 3031
how do you tell if the bus is at what division?
it's not really in the first page, I forgot where I posted the coords, but what you could do is just plug in the coords on Google Maps or something and that will pin point you to its exact location
in this case I could tell you that Bladensburg's coordinates range from 38.920-38.924 latitude and -76.968 to -76.971 longitude
2575 back at FMR
<vehicle id="2575" routeTag="null" dirTag="null" lat="38.8431209" lon="-77.052826" secsSinceReport="13829" predictable="false" heading="-4" speedKmHr="0.0"/>
EDIT: I checked 2637 this morning and it was still at Bladensburg, now it's apparently at Crystal City...
<vehicle id="2637" routeTag="null" dirTag="null" lat="38.859264" lon="-77.0511779" secsSinceReport="36" predictable="false" heading="-4" speedKmHr="0.0"/>
I pray to God that they kept the JD on this one
EDIT 2: look what 2464 is on...
<vehicle id="2464" routeTag="H6" dirTag="H6_H6_0" lat="38.927406" lon="-76.985909" secsSinceReport="172" predictable="true" heading="345" speedKmHr="51.48"/>
EDIT 3: 2637 finally back at FMR
<vehicle id="2637" routeTag="null" dirTag="null" lat="38.844467" lon="-77.053734" secsSinceReport="8" predictable="false" heading="-4" speedKmHr="0.0"/>
2701 has also moved to Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2701" routeTag="25B" dirTag="null" lat="38.924026" lon="-76.970123" secsSinceReport="79" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: So has 2517.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2517" routeTag="29G" dirTag="null" lat="38.92342" lon="-76.970505" secsSinceReport="12266" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3021 at Landover........
<vehicle id="3021" routeTag="9A" dirTag="null" lat="38.937775" lon="-76.874046" secsSinceReport="1071" predictable="false" heading="-4" speedKmHr="0.0"/>
2550 and 2605 have both returned to FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2550" routeTag="9A" dirTag="9A_9A_1" lat="38.802914" lon="-77.0475079" secsSinceReport="130" predictable="true" heading="180" speedKmHr="17.676"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2605" routeTag="null" dirTag="null" lat="38.842873" lon="-77.052406" secsSinceReport="9646" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
guess who's FINALLY back from rehab as well
<vehicle id="5309" routeTag="null" dirTag="null" lat="38.94685" lon="-77.031471" secsSinceReport="467" predictable="false" heading="-4" speedKmHr="0.0"/>
btw this morning I checked 2550, 2605, and 5309 and 2550 was back at FMR, but the other 2 were still at Bladensburg, looks like 2605 and 5309 just got back today
Quote from: 79MetroExtraMD on June 14, 2011, 07:01:18 PM
Quote from: RideOn5905 on June 14, 2011, 02:34:54 PM
9835 on the Z6??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9835" routeTag="Z6" dirTag="Z6_Z6_1" lat="39.0451089" lon="-76.981216" secsSinceReport="43" predictable="true" heading="120" speedKmHr="32.184"/>
</body>
So it's a Flx, and its speed was 32. how much Km/H? ;)
look who's back at FMR so soon, I doubt it was rehabbed after all
<vehicle id="2592" routeTag="null" dirTag="null" lat="38.843063" lon="-77.053177" secsSinceReport="852" predictable="false" heading="-4" speedKmHr="0.0"/>
As of 10:57AM today
<vehicle id="7020" routeTag="null" dirTag="null" lat="38.919624" lon="-76.969841" secsSinceReport="1" predictable="false" heading="315" speedKmHr="30.564"/></body>
Heading to Bladensburg
Quote from: Flxible_Metro_8700 on June 24, 2011, 10:58:00 AM
As of 10:57AM today
<vehicle id="7020" routeTag="null" dirTag="null" lat="38.919624" lon="-76.969841" secsSinceReport="1" predictable="false" heading="315" speedKmHr="30.564"/></body>
Heading to Bladensburg
I did spot one at Bladensburg near the shops while on the train.
According to this, 2636 is at Johnson Truck Center in Landover, MD.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2636" routeTag="null" dirTag="null" lat="38.942696" lon="-76.858192" secsSinceReport="755109" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2529 back from rehab.
<vehicle id="2529" routeTag="28A" dirTag="28A_28A_1" lat="38.855961" lon="-77.139763" secsSinceReport="89" predictable="true" heading="120" speedKmHr="27.324"/>
2631 takes its place at Bladensburg
<vehicle id="2631" routeTag="8Z" dirTag="null" lat="38.922951" lon="-76.970963" secsSinceReport="9757" predictable="false" heading="-4" speedKmHr="0.0"/>
and why are FMR buses on the P6 on a Sunday?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2711" routeTag="P6" dirTag="P6_P6_0" lat="38.8831599" lon="-77.002319" secsSinceReport="37" predictable="true" heading="78" speedKmHr="0.0"/>
<vehicle id="2715" routeTag="P6" dirTag="P6_P6_0" lat="38.916241" lon="-77.000603" secsSinceReport="148" predictable="true" heading="180" speedKmHr="32.184"/>
<vehicle id="2672" routeTag="P6" dirTag="P6_P6_1" lat="38.8945999" lon="-77.021889" secsSinceReport="16" predictable="true" heading="293" speedKmHr="0.0"/>
<lastTime time="1309120912672"/></body>
Quote from: NewFlyer9736BCT on June 26, 2011, 04:17:46 PM
2529 back from rehab.
<vehicle id="2529" routeTag="28A" dirTag="28A_28A_1" lat="38.855961" lon="-77.139763" secsSinceReport="89" predictable="true" heading="120" speedKmHr="27.324"/>
2631 takes its place at Bladensburg
<vehicle id="2631" routeTag="8Z" dirTag="null" lat="38.922951" lon="-76.970963" secsSinceReport="9757" predictable="false" heading="-4" speedKmHr="0.0"/>
and why are FMR buses on the P6 on a Sunday?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2711" routeTag="P6" dirTag="P6_P6_0" lat="38.8831599" lon="-77.002319" secsSinceReport="37" predictable="true" heading="78" speedKmHr="0.0"/>
<vehicle id="2715" routeTag="P6" dirTag="P6_P6_0" lat="38.916241" lon="-77.000603" secsSinceReport="148" predictable="true" heading="180" speedKmHr="32.184"/>
<vehicle id="2672" routeTag="P6" dirTag="P6_P6_1" lat="38.8945999" lon="-77.021889" secsSinceReport="16" predictable="true" heading="293" speedKmHr="0.0"/>
<lastTime time="1309120912672"/></body>
Apparently FMR does the P6 on Sundays now.
http://test.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=schedule&a=wmata&r=P6
So West Ox has a block on the 38B after all, "AS60".
http://test.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=schedule&a=wmata&r=38B
4291 on the 79.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4291" routeTag="79" dirTag="79_79_1" lat="38.896358" lon="-77.021957" secsSinceReport="52" predictable="true" heading="345" speedKmHr="32.184"/>
</body>
2162 is at Western.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2162" routeTag="42" dirTag="null" lat="38.958454" lon="-77.085793" secsSinceReport="14" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Okay, I have no clue what's going on here:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3026" routeTag="3T" dirTag="null" lat="38.903179" lon="-76.844505" secsSinceReport="841" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3034" routeTag="3T" dirTag="null" lat="38.627907" lon="-76.909149" secsSinceReport="9" predictable="false" heading="210" speedKmHr="56.304"/>
</body>
3026 is at The Boulevard at the Capital Centre, and 3034 is at... the MVA in Waldorf??
6028, 6030, and 6039 are also in that place where 2636 is. also, 6007, 6012, 6019, and 6024 are way out of date on the secs since last report.
<vehicle id="6028" routeTag="null" dirTag="null" lat="38.942177" lon="-76.857559" secsSinceReport="146273" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6030" routeTag="null" dirTag="null" lat="38.942314" lon="-76.858818" secsSinceReport="13296" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6039" routeTag="null" dirTag="null" lat="38.942093" lon="-76.8586119" secsSinceReport="73338" predictable="false" heading="-4" speedKmHr="0.0"/>
6026 at Western
<vehicle id="6026" routeTag="N4" dirTag="null" lat="38.95829" lon="-77.0851969" secsSinceReport="3932" predictable="false" heading="-4" speedKmHr="0.0"/>
And it looks like 3026 and 3034 were only out of the way for the day; both buses have returned to Virginia.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3026" routeTag="9A" dirTag="null" lat="38.866879" lon="-77.054016" secsSinceReport="1739" predictable="true" heading="15" speedKmHr="24.12"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3034" routeTag="null" dirTag="null" lat="38.843971" lon="-77.053528" secsSinceReport="10864" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2596 is at Bladensburg, and 2651 is at the same place in Landover as 2636, 6028, 6030, and 6039.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2596" routeTag="null" dirTag="null" lat="38.922871" lon="-76.971169" secsSinceReport="863" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2651" routeTag="null" dirTag="null" lat="38.942505" lon="-76.85833" secsSinceReport="174823" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
With that in mind, the list of Orion VIIs at Bladensburg for rehab are as follows:
2516, 2517, 2523, 2530, 2559, 2581, 2589, 2593, 2596, 2604, 2617, 2620, 2631, 2642, 2653 (has anyone else noticed that the difference between all four of these buses is eleven?), 2701, 2707, 2712, 2714, 2717, 3028, 3031, and possibly 3004 as well, judging by its last seconds count (almost 3 million). Also, 2516, 2530, and 2620's GPS's were all updated very recently, so they could be getting out real soon.
EDIT: And 6026 has returned to Montgomery.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6026" routeTag="null" dirTag="null" lat="39.046814" lon="-77.108337" secsSinceReport="78" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2100 on the 1B
<vehicle id="2100" routeTag="1B" dirTag="1B_1B_1" lat="38.865917" lon="-77.202766" secsSinceReport="82" predictable="true" heading="60" speedKmHr="0.0"/>
2101 on the 2B
<vehicle id="2101" routeTag="2B" dirTag="2B_2B_0" lat="38.877083" lon="-77.194397" secsSinceReport="98" predictable="true" heading="240" speedKmHr="28.943999999999996"/>
3019 is at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3019" routeTag="9A" dirTag="null" lat="38.937225" lon="-76.873734" secsSinceReport="88" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Royal 4300s moving to West Ox apparently
<vehicle id="4358" routeTag="null" dirTag="null" lat="38.849361" lon="-77.37822" secsSinceReport="56576" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4360" routeTag="2T" dirTag="2T_2T_0" lat="38.932606" lon="-77.231674" secsSinceReport="31" predictable="true" heading="353" speedKmHr="0.0"/>
<vehicle id="4361" routeTag="null" dirTag="null" lat="38.849308" lon="-77.378326" secsSinceReport="2967" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4362" routeTag="1A" dirTag="1A_1A_0" lat="38.869576" lon="-77.175957" secsSinceReport="145" predictable="true" heading="255" speedKmHr="41.832"/>
<vehicle id="4365" routeTag="1A" dirTag="1A_1A_1" lat="38.866879" lon="-77.262337" secsSinceReport="63" predictable="true" heading="135" speedKmHr="11.232"/>
<vehicle id="4366" routeTag="1C" dirTag="1C_1C_1" lat="38.858685" lon="-77.305878" secsSinceReport="159" predictable="true" heading="60" speedKmHr="61.128"/>
and 4260 at Royal
<vehicle id="4260" routeTag="null" dirTag="null" lat="38.8112179" lon="-77.04306" secsSinceReport="17421" predictable="false" heading="-4" speedKmHr="0.0"/>
2336 finally updated after over 20 million seconds, but at the same place???
<vehicle id="2336" routeTag="null" dirTag="null" lat="38.917702" lon="-76.928017" secsSinceReport="20857" predictable="false" heading="105" speedKmHr="90.108"/>
2042 on the 96.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2042" routeTag="96" dirTag="96_96_1" lat="38.917011" lon="-77.030113" secsSinceReport="5" predictable="true" heading="255" speedKmHr="16.092"/>
</body>
3031 back at FMR
<vehicle id="3031" routeTag="3B" dirTag="3B_3B_0" lat="38.896221" lon="-77.071548" secsSinceReport="116" predictable="true" heading="180" speedKmHr="11.232"/>
I'm surprised 2516, 2523, 2581, and 2593 are still at Bladensburg, they've been there for a long time now
Would be believable if there werent two buses with the same block logged in.
- <predictions agencyTitle="WMATA Washington" routeTitle="D8 HOSPITAL CENTER" routeTag="D8" stopTitle="Rhode Island Ave Sta + Bus Bay C" stopTag="7070">
- <direction title="South to Union Station">
<prediction epochTime="1309803501729" seconds="2134" minutes="35" isDeparture="false" affectedByLayover="true" dirTag="D8_D8_0" vehicle="2350" block="B880" tripTag="3563084" />
<prediction epochTime="1309803501729" seconds="2134" minutes="35" isDeparture="false" affectedByLayover="true" dirTag="D8_D8_0" vehicle="
7003" block="
B880"
2463 back at Bladensburg
<vehicle id="2463" routeTag="null" dirTag="null" lat="38.922844" lon="-76.9711" secsSinceReport="1104" predictable="false" heading="-4" speedKmHr="0.0"/>
2462 is all that's left to have its GPS updated and showing that it's at Bladensburg. 2460 and 2461 still haven't shown that it's been on any routes yet, hopefully that will be very soon
I have a lot to report since the site went down two days ago:
4294 on the 42 and 4263 on the R2 (both of these were from Tuesday, so I can't bring them back up)
4305 is at Montgomery:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4305" routeTag="null" dirTag="null" lat="39.046261" lon="-77.1073229" secsSinceReport="4114" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2461 IS BACK IN SERVICE!!!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2461" routeTag="80" dirTag="80_80_0" lat="38.933403" lon="-76.994026" secsSinceReport="42" predictable="true" heading="347" speedKmHr="0.0"/>
</body>
Nextbus has no data on 6137.
2620, 2636, and 2651 have all returned to FMR:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2620" routeTag="null" dirTag="null" lat="38.843834" lon="-77.053314" secsSinceReport="5211" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2636" routeTag="null" dirTag="null" lat="38.843533" lon="-77.054047" secsSinceReport="1198" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2651" routeTag="null" dirTag="null" lat="38.842266" lon="-77.053703" secsSinceReport="39" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2625 is now at that place in Landover:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2625" routeTag="null" dirTag="null" lat="38.94223" lon="-76.858467" secsSinceReport="532645" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
6152 is in Clarksburg, in the middle of a forest off Clarksburg Road, a little over a mile north of where the 75 goes:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6152" routeTag="null" dirTag="null" lat="39.2627979" lon="-77.280533" secsSinceReport="502949" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
a few 4200s moving to Royal
<vehicle id="4233" routeTag="null" dirTag="null" lat="38.810917" lon="-77.042923" secsSinceReport="52104" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4234" routeTag="null" dirTag="null" lat="38.810558" lon="-77.042709" secsSinceReport="363" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4238" routeTag="null" dirTag="null" lat="38.810806" lon="-77.043861" secsSinceReport="4791" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4239" routeTag="null" dirTag="null" lat="38.810505" lon="-77.0430219" secsSinceReport="17354" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4240" routeTag="10A" dirTag="10A_10A_1" lat="38.805252" lon="-77.047119" secsSinceReport="0" predictable="true" heading="180" speedKmHr="11.232"/>
<vehicle id="4241" routeTag="null" dirTag="null" lat="38.810589" lon="-77.043266" secsSinceReport="15033" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4260" routeTag="null" dirTag="null" lat="38.810478" lon="-77.043304" secsSinceReport="19943" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: RideOn5905 on July 07, 2011, 11:20:11 AM
2461 IS BACK IN SERVICE!!!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2461" routeTag="80" dirTag="80_80_0" lat="38.933403" lon="-76.994026" secsSinceReport="42" predictable="true" heading="347" speedKmHr="0.0"/>
</body>
I have a picture of that bus in service on the G8 in the July Photos thread
2805 is at Northern.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2805" routeTag="null" dirTag="null" lat="38.948059" lon="-77.0327" secsSinceReport="27" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2657 at Bladensburg
<vehicle id="2657" routeTag="null" dirTag="null" lat="38.923336" lon="-76.970543" secsSinceReport="577448" predictable="false" heading="-4" speedKmHr="0.0"/>
...and 2530 has returned home to FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2530" routeTag="null" dirTag="null" lat="38.842709" lon="-77.052475" secsSinceReport="5918" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
the 7000s are finally in service!
<vehicle id="7003" routeTag="W4" dirTag="W4_W4v1_0" lat="38.843697" lon="-76.9978409" secsSinceReport="29" predictable="true" heading="165" speedKmHr="24.12"/>
<vehicle id="7005" routeTag="B2" dirTag="B2_B2c_0" lat="38.862232" lon="-76.996231" secsSinceReport="391" predictable="true" heading="119" speedKmHr="0.0"/>
<vehicle id="7007" routeTag="H2" dirTag="H2_H2_0" lat="38.927628" lon="-77.029549" secsSinceReport="7" predictable="true" heading="266" speedKmHr="0.0"/>
<vehicle id="7008" routeTag="B2" dirTag="B2_B2v1_1" lat="38.866879" lon="-76.984047" secsSinceReport="28" predictable="true" heading="236" speedKmHr="0.0"/>
7008 G8 BG58
<predictions agencyTitle="WMATA Washington" routeTitle="G8 RHODE ISLAND AVE" routeTag="G8" stopTitle="Brookland Station + Bus Bay H" stopTag="13577">
<direction title="East to Avondale">
<prediction epochTime="1310587506468" seconds="70" minutes="1" isDeparture="false" dirTag="G8_G8_0" vehicle="2405" block="BG56" tripTag="3543371"/>
<prediction epochTime="1310587560000" seconds="123" minutes="2" isDeparture="true" affectedByLayover="true" dirTag="G8_G8v2_0" vehicle="7008" block="BG58"/>
welcome home, 2516!
<vehicle id="2516" routeTag="null" dirTag="null" lat="38.843174" lon="-77.053772" secsSinceReport="24" predictable="false" heading="-4" speedKmHr="0.0"/>
3013 at the Waldorf MVA for some reason
<vehicle id="3013" routeTag="U4" dirTag="null" lat="38.615253" lon="-76.907578" secsSinceReport="151" predictable="false" heading="-4" speedKmHr="0.0"/>
4242 on the S2
<vehicle id="4242" routeTag="S2" dirTag="S2_S2_1" lat="38.935108" lon="-77.036552" secsSinceReport="74" predictable="true" heading="181" speedKmHr="0.0"/>
2228 is at Annex.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2228" routeTag="36" dirTag="null" lat="38.872463" lon="-76.932877" secsSinceReport="388" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4247 is at Friendship Heights; I saw it terminating a 36.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4247" routeTag="null" dirTag="null" lat="38.961674" lon="-77.084923" secsSinceReport="339" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2625 is back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2625" routeTag="null" dirTag="null" lat="38.843369" lon="-77.054085" secsSinceReport="166006" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
5302 finally back online. rehabbed? who knows...
<vehicle id="5302" routeTag="70" dirTag="70_70cv3_1" lat="38.968521" lon="-77.027412" secsSinceReport="110" predictable="true" heading="184" speedKmHr="0.0"/>
6137, 2462, 5312, and 5321 remain with no GPS data (2086 getting very close)
2548 at Bladensburg
<vehicle id="2548" routeTag="23A" dirTag="null" lat="38.922981" lon="-76.970924" secsSinceReport="360" predictable="false" heading="-4" speedKmHr="0.0"/>
7002, 7004, 7014, 7015, and 7018 now online
<vehicle id="7002" routeTag="null" dirTag="null" lat="38.941132" lon="-76.877998" secsSinceReport="7078" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7004" routeTag="null" dirTag="null" lat="38.941132" lon="-76.878212" secsSinceReport="18672" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7014" routeTag="null" dirTag="null" lat="38.94091" lon="-76.877998" secsSinceReport="25" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7015" routeTag="null" dirTag="null" lat="38.941101" lon="-76.878281" secsSinceReport="211" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7018" routeTag="null" dirTag="null" lat="38.940746" lon="-76.878143" secsSinceReport="2661" predictable="false" heading="-4" speedKmHr="0.0"/>
Check out what the 90 has now:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4242" routeTag="90" dirTag="90_90_1" lat="38.904995" lon="-76.995461" secsSinceReport="149" predictable="true" heading="105" speedKmHr="40.212"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4271" routeTag="90" dirTag="90_90_1" lat="38.921055" lon="-77.042152" secsSinceReport="20" predictable="true" heading="165" speedKmHr="127.11600000000001"/>
</body>
EDIT: And 4-and-a-half hours later, 2410 on the G12.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2410" routeTag="G12" dirTag="G12_G12_1" lat="39.00119" lon="-76.875343" secsSinceReport="10" predictable="true" heading="224" speedKmHr="0.0"/>
</body>
2523 and 2604 finally back at FMR
<vehicle id="2523" routeTag="null" dirTag="null" lat="38.842762" lon="-77.052582" secsSinceReport="29757" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2604" routeTag="null" dirTag="null" lat="38.841305" lon="-77.054222" secsSinceReport="9034" predictable="false" heading="-4" speedKmHr="0.0"/>
judging by the "secsSinceReport", 3001 might be in rehab now, but I can't guarantee it
<vehicle id="3001" routeTag="null" dirTag="null" lat="38.923172" lon="-76.970505" secsSinceReport="1930256" predictable="false" heading="-4" speedKmHr="0.0"/>
2678 is at that truck place in Landover:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2678" routeTag="null" dirTag="null" lat="38.942009" lon="-76.858437" secsSinceReport="155294" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
4276 on the X2.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4276" routeTag="X2" dirTag="X2_X2_0" lat="38.900181" lon="-77.035957" secsSinceReport="56" predictable="true" heading="78" speedKmHr="0.0"/>
</body>
4227 on the 23A.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4227" routeTag="23A" dirTag="23A_23A_1" lat="38.915802" lon="-77.218513" secsSinceReport="61" predictable="true" heading="210" speedKmHr="11.232"/>
</body>
6201 on the D14. I really hope Montgomery's remaining 6200s don't get stolen by Annex...
<vehicle id="6201" routeTag="D14" dirTag="D14_D14_1" lat="38.844082" lon="-76.931862" secsSinceReport="268" predictable="true" heading="218" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on July 22, 2011, 04:28:50 PM
6201 on the D14. I really hope Montgomery's remaining 6200s don't get stolen by Annex...
<vehicle id="6201" routeTag="D14" dirTag="D14_D14_1" lat="38.844082" lon="-76.931862" secsSinceReport="268" predictable="true" heading="218" speedKmHr="0.0"/>
You and me both.
Fortunately, 6200, 6202, 6203 and 6204 are all doing Montgomery routes right now (Q2, Y9, J2, and C4, in that order), and 6205-6211 are still at Montgomery. Hopefully, 6201 was only a temporary move.
This is weird... literally NONE of Montgomery or Landover's DE42LFAs are in service at the moment; the only buses in service are Orions and DE40LF(R)s, and in Montgomery's case, D40LFRs as well (all on the C8, no less). Northern's and Western's are still in service today, but why not these two?
EDIT: And speaking of random buses being at Annex:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2557" routeTag="null" dirTag="null" lat="38.872738" lon="-76.9337539" secsSinceReport="2219" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2559 has come home to FMR!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2559" routeTag="null" dirTag="null" lat="38.842926" lon="-77.052757" secsSinceReport="8593" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: ...and 2623 has taken its place at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2623" routeTag="16L" dirTag="null" lat="38.922813" lon="-76.969666" secsSinceReport="21623" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: 2591, despite having already been rehabbed, is also at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2591" routeTag="null" dirTag="null" lat="38.921741" lon="-76.971207" secsSinceReport="126327" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
hmm...2581, 2593, and 2642 have been at Bladensburg way longer than 2559, and even those 3 aren't back yet (2593 timeout at 6 million seconds, so it could be back)
2100 on the 22A.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2100" routeTag="22A" dirTag="22A_22A_0" lat="38.836548" lon="-77.084679" secsSinceReport="33" predictable="true" heading="360" speedKmHr="32.184"/>
</body>
EDIT: Well, that was fast:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7014" routeTag="P6" dirTag="P6_P6_1" lat="38.8861009" lon="-77.016251" secsSinceReport="142" predictable="true" heading="270" speedKmHr="37.008"/>
</body>
2581 has finally made it home! Took it long enough...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2581" routeTag="null" dirTag="null" lat="38.842709" lon="-77.052261" secsSinceReport="6456" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7046 at Montgomery Division <body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7046" routeTag="null" dirTag="null" lat="39.046867" lon="-77.109177" secsSinceReport="89822" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7031 in service on the D6 BD07
<predictions agencyTitle="WMATA Washington" routeTitle="D6 SIBLEY-STAD ARM" routeTag="D6" stopTitle="Stadium Armory Station + Bus Bay E" stopTag="13611">
<direction title="West to Sibley Hospital">
<prediction epochTime="1311948600000" seconds="1563" minutes="26" isDeparture="true" affectedByLayover="true" dirTag="D6_D6_0" vehicle="2394" block="BD02" tripTag="3569373"/>
<prediction epochTime="1311949860000" seconds="2823" minutes="47" isDeparture="true" affectedByLayover="true" dirTag="D6_D6_0" vehicle="
7031" block="
BD07"
and 7046 makes its debut on the L8
<predictions agencyTitle="WMATA Washington" routeTitle="L8 CONN AVE-MD" routeTag="L8" stopTitle="Friendship Hgts Sta + Bus Bay K" stopTag="15409">
<direction title="North to Aspen Hill">
<prediction epochTime="1311951600000" seconds="4376" minutes="72" isDeparture="true" affectedByLayover="true" dirTag="L8_L8_0" vehicle="
7046" block="
ML45" tripTag="3559956"/>
</direction>
</predictions>
7041 on the L2
<predictions agencyTitle="WMATA Washington" routeTitle="L2 CONNECTICUT AVE" routeTag="L2" stopTitle="Chevy Chase Term Rdwy + Connecticut" stopTag="9187">
<direction title="South to McPherson Square">
<prediction epochTime="1311948000000" seconds="501" minutes="8" isDeparture="true" affectedByLayover="true" dirTag="L2_L2_1" vehicle="
7041" block="
ML06" tripTag="3559609"/>
7041 on the L4 (Block ML06) and 7046 on the L8 (Block ML45) are in service for Montgomery Division.
5312's GPS is finally back up and running.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5312" routeTag="S2" dirTag="S2_S2_1" lat="38.988071" lon="-77.031197" secsSinceReport="14" predictable="true" heading="135" speedKmHr="16.092"/>
</body>
Quote from: RideOn5905 on July 29, 2011, 02:41:24 PM
5312's GPS is finally back up and running.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5312" routeTag="S2" dirTag="S2_S2_1" lat="38.988071" lon="-77.031197" secsSinceReport="14" predictable="true" heading="135" speedKmHr="16.092"/>
</body>
I noticed that too...last week I saw that bus deadheading up 16th Street (this was before the GPS was working again), it's not rehabbed.
2642 finally back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2642" routeTag="null" dirTag="null" lat="38.84301" lon="-77.052582" secsSinceReport="12329" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on August 02, 2011, 03:30:31 PM
2642 finally back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2642" routeTag="null" dirTag="null" lat="38.84301" lon="-77.052582" secsSinceReport="12329" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
finally...i checked it this morning and it was still at Bburg
anyways 2086 will be going offline any second now...it's past the 32 million mark
<vehicle id="2086" routeTag="null" dirTag="null" lat="39.045135" lon="-77.1079479" secsSinceReport="32006059" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on August 02, 2011, 07:52:50 PM
Quote from: RideOn5905 on August 02, 2011, 03:30:31 PM
2642 finally back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2642" routeTag="null" dirTag="null" lat="38.84301" lon="-77.052582" secsSinceReport="12329" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
finally...i checked it this morning and it was still at Bburg
anyways 2086 will be going offline any second now...it's past the 32 million mark
<vehicle id="2086" routeTag="null" dirTag="null" lat="39.045135" lon="-77.1079479" secsSinceReport="32006059" predictable="false" heading="-4" speedKmHr="0.0"/>
i dont get the secsSinceReport="32006059"
2712 at the DC DMV inspection station. you know what this means? this bus should be back at FMR sometime this week. I just hope it hasn't been de-powered to Cummins...
<vehicle id="2712" routeTag="null" dirTag="null" lat="38.878265" lon="-77.010895" secsSinceReport="247" predictable="false" heading="-4" speedKmHr="0.0"/>
also, since the return of 2642, nothing has taken its place at Bladensburg as of yet (checked all unrehabbed buses from 2501-2730, 3020-3034, and 5302-5321), I guess it's a matter of patience
3004 on the H6; keep your eyes peeled for this one.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3004" routeTag="H6" dirTag="H6_H6_0" lat="38.922348" lon="-76.960739" secsSinceReport="89" predictable="true" heading="300" speedKmHr="65.952"/>
</body>
3017 is at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3017" routeTag="U4" dirTag="null" lat="38.937584" lon="-76.873764" secsSinceReport="36936" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2163 is at Royal.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2163" routeTag="P6" dirTag="null" lat="38.811001" lon="-77.042671" secsSinceReport="0" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on August 03, 2011, 05:51:50 PM
3004 on the H6; keep your eyes peeled for this one.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3004" routeTag="H6" dirTag="H6_H6_0" lat="38.922348" lon="-76.960739" secsSinceReport="89" predictable="true" heading="300" speedKmHr="65.952"/>
</body>
are you sure this one is rehabbed? I remember a while ago you saw this bus and 3013 with a high secsSinceReport and thought it was being rehabbed (3013 did turn out to be rehabbed, never seen 3004 yet, although this morning it showed that it was on the U4)
Quote from: NewFlyer9736BCT on August 04, 2011, 11:53:59 AM
Quote from: RideOn5905 on August 03, 2011, 05:51:50 PM
3004 on the H6; keep your eyes peeled for this one.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3004" routeTag="H6" dirTag="H6_H6_0" lat="38.922348" lon="-76.960739" secsSinceReport="89" predictable="true" heading="300" speedKmHr="65.952"/>
</body>
are you sure this one is rehabbed? I remember a while ago you saw this bus and 3013 with a high secsSinceReport and thought it was being rehabbed (3013 did turn out to be rehabbed, never seen 3004 yet, although this morning it showed that it was on the U4)
I am 95% sure that it is rehabbed. I don't know why else it would be out of service for so long.
Also, 2183 is at Royal; I'm thinking the Xcelsiors are causing a few 2100s to move.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2183" routeTag="G8" dirTag="null" lat="38.810696" lon="-77.042503" secsSinceReport="116" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Three more 2100s have moved:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2165" routeTag="18E" dirTag="18E_18E_0" lat="38.869438" lon="-77.052338" secsSinceReport="245" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2168" routeTag="P1" dirTag="null" lat="38.811138" lon="-77.042503" secsSinceReport="41" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2186" routeTag="V7" dirTag="null" lat="38.810532" lon="-77.042572" secsSinceReport="40995" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2179 now at Royal
<vehicle id="2179" routeTag="36" dirTag="null" lat="38.810341" lon="-77.043373" secsSinceReport="94" predictable="false" heading="-4" speedKmHr="0.0"/>
as of 8 this morning, still nothing new on the FMR side
Well, at least something new has arrived at Bladensburg...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6538" routeTag="null" dirTag="null" lat="38.920918" lon="-76.970467" secsSinceReport="168693" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
look who's back online!
<vehicle id="6040" routeTag="null" dirTag="null" lat="38.922596" lon="-76.971413" secsSinceReport="292036" predictable="false" heading="-4" speedKmHr="0.0"/>
...and is no longer online :(
<Error shouldRetry="false">
No data available for vehicle=2086
</Error>
What is it with random New Flyers and Bladensburg nowadays?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6212" routeTag="B27" dirTag="null" lat="38.921661" lon="-76.971169" secsSinceReport="139" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6493" routeTag="null" dirTag="null" lat="38.922127" lon="-76.971558" secsSinceReport="458363" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6509" routeTag="null" dirTag="null" lat="38.922047" lon="-76.971207" secsSinceReport="106436" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6523" routeTag="null" dirTag="null" lat="38.920864" lon="-76.969978" secsSinceReport="359308" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on August 09, 2011, 02:46:11 PM
What is it with random New Flyers and Bladensburg nowadays?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6212" routeTag="B27" dirTag="null" lat="38.921661" lon="-76.971169" secsSinceReport="139" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6493" routeTag="null" dirTag="null" lat="38.922127" lon="-76.971558" secsSinceReport="458363" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6509" routeTag="null" dirTag="null" lat="38.922047" lon="-76.971207" secsSinceReport="106436" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6523" routeTag="null" dirTag="null" lat="38.920864" lon="-76.969978" secsSinceReport="359308" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Heavy Repair Shop at Bladensburg
From what I heard from Chris Fancher, 6493 was involved in an accident. Also, I forgot to mention this, but 2010 is also at Bladensburg, it's been there since a couple of months ago, it's still there now apparently.
<vehicle id="2010" routeTag="null" dirTag="null" lat="38.922924" lon="-76.971413" secsSinceReport="2383392" predictable="false" heading="-4" speedKmHr="0.0"/>
2460 has returned to service!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2460" routeTag="B2" dirTag="B2_B2_1" lat="38.899906" lon="-76.985558" secsSinceReport="26" predictable="true" heading="170" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on August 10, 2011, 01:05:40 PM
2460 has returned to service!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2460" routeTag="B2" dirTag="B2_B2_1" lat="38.899906" lon="-76.985558" secsSinceReport="26" predictable="true" heading="170" speedKmHr="0.0"/>
</body>
awesome!!! now it's just 2462 and 2463 left
2558 is now at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2558" routeTag="null" dirTag="null" lat="38.923367" lon="-76.970467" secsSinceReport="11947" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4042 on the R2??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4042" routeTag="R2" dirTag="R2_R2_1" lat="39.039772" lon="-76.947968" secsSinceReport="37" predictable="true" heading="172" speedKmHr="0.0"/>
</body>
2712 back at FMR, I'm assuming this one is blue
<vehicle id="2712" routeTag="null" dirTag="null" lat="38.842957" lon="-77.052895" secsSinceReport="797" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: RideOn5905 on August 12, 2011, 11:10:33 AM
4042 on the R2??
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4042" routeTag="R2" dirTag="R2_R2_1" lat="39.039772" lon="-76.947968" secsSinceReport="37" predictable="true" heading="172" speedKmHr="0.0"/>
</body>
could there be an off chance that "4042" is 2462? or maybe one of the 7000s...let's hope for the best
I'm guessing it's probably the latter. And as for 2712, it probably is blue, what with it being an airport bus and whatnot...
EDIT: And 2624 has arrived at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2624" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970505" secsSinceReport="2604" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2630 finally updated again, this time it's at Crystal City (at least it was nearly 24 hours ago)
<vehicle id="2630" routeTag="null" dirTag="null" lat="38.857254" lon="-77.053032" secsSinceReport="69617" predictable="false" heading="-4" speedKmHr="0.0"/>
It's probably one of those GPS's that updates once every couple of months, if that's the case, this bus needs a new one. I last heard (from Delonta I think) that 2630 was sitting in the back of Bladensburg (about a month ago), so there's a chance that this one may be rehabbed. Until then, it remains a mystery.
edit - 2224 at Bladensburg, 2164 on the 52, 2166 on the 70
<vehicle id="2224" routeTag="62" dirTag="null" lat="38.923061" lon="-76.969528" secsSinceReport="11264" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2164" routeTag="52" dirTag="52_52_1" lat="38.903812" lon="-77.032036" secsSinceReport="22" predictable="true" heading="172" speedKmHr="0.0"/>
<vehicle id="2166" routeTag="70" dirTag="70_70_0" lat="38.917149" lon="-77.021919" secsSinceReport="39" predictable="true" heading="360" speedKmHr="22.5"/>
Quote from: NewFlyer9736BCT on August 14, 2011, 12:37:35 PM
2630 finally updated again, this time it's at Crystal City (at least it was nearly 24 hours ago)
<vehicle id="2630" routeTag="null" dirTag="null" lat="38.857254" lon="-77.053032" secsSinceReport="69617" predictable="false" heading="-4" speedKmHr="0.0"/>
It's probably one of those GPS's that updates once every couple of months, if that's the case, this bus needs a new one. I last heard (from Delonta I think) that 2630 was sitting in the back of Bladensburg (about a month ago), so there's a chance that this one may be rehabbed. Until then, it remains a mystery.
edit - 2224 at Bladensburg, 2164 on the 52, 2166 on the 70
<vehicle id="2224" routeTag="62" dirTag="null" lat="38.923061" lon="-76.969528" secsSinceReport="11264" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2164" routeTag="52" dirTag="52_52_1" lat="38.903812" lon="-77.032036" secsSinceReport="22" predictable="true" heading="172" speedKmHr="0.0"/>
<vehicle id="2166" routeTag="70" dirTag="70_70_0" lat="38.917149" lon="-77.021919" secsSinceReport="39" predictable="true" heading="360" speedKmHr="22.5"/>
Actually, I never posted this, but up until now, its GPS showed that it was at Ballston. And I also remember that there was a hit-and-run at Ballston involving a Metrobus a few months back. So its time spent at Bladensburg may have been for repairs, although it
is possible that they also rehabbed it during repairs.
Quote from: RideOn5905 on August 14, 2011, 06:01:46 PM
Quote from: NewFlyer9736BCT on August 14, 2011, 12:37:35 PM
2630 finally updated again, this time it's at Crystal City (at least it was nearly 24 hours ago)
<vehicle id="2630" routeTag="null" dirTag="null" lat="38.857254" lon="-77.053032" secsSinceReport="69617" predictable="false" heading="-4" speedKmHr="0.0"/>
It's probably one of those GPS's that updates once every couple of months, if that's the case, this bus needs a new one. I last heard (from Delonta I think) that 2630 was sitting in the back of Bladensburg (about a month ago), so there's a chance that this one may be rehabbed. Until then, it remains a mystery.
edit - 2224 at Bladensburg, 2164 on the 52, 2166 on the 70
<vehicle id="2224" routeTag="62" dirTag="null" lat="38.923061" lon="-76.969528" secsSinceReport="11264" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2164" routeTag="52" dirTag="52_52_1" lat="38.903812" lon="-77.032036" secsSinceReport="22" predictable="true" heading="172" speedKmHr="0.0"/>
<vehicle id="2166" routeTag="70" dirTag="70_70_0" lat="38.917149" lon="-77.021919" secsSinceReport="39" predictable="true" heading="360" speedKmHr="22.5"/>
Actually, I never posted this, but up until now, its GPS showed that it was at Ballston. And I also remember that there was a hit-and-run at Ballston involving a Metrobus a few months back. So its time spent at Bladensburg may have been for repairs, although it is possible that they also rehabbed it during repairs.
yeah I saw that it was at Ballston all that time (supposedly), although since the update, the GPS still shows that it's in that same spot at Crystal City.
BTW idk if you saw the rehab thread, but 3004 is, in fact, rehabbed.
Landover's D40LFRs seem to be heading to Bladensburg one by one; first it was 6212, then 6213, and now, 6215 is there.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6215" routeTag="B30" dirTag="null" lat="38.922264" lon="-76.971588" secsSinceReport="6057" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Minor repairs?... Paint job?... IDK...
3028 back at FMR
<vehicle id="3028" routeTag="null" dirTag="null" lat="38.844219" lon="-77.054085" secsSinceReport="37795" predictable="false" heading="-4" speedKmHr="0.0"/>
2720 at Bladensburg
<vehicle id="2720" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970367" secsSinceReport="13007" predictable="false" heading="-4" speedKmHr="0.0"/>
and it's.........BACK at Bladensburg?
<vehicle id="3028" routeTag="null" dirTag="null" lat="38.922733" lon="-76.971413" secsSinceReport="192" predictable="false" heading="-4" speedKmHr="0.0"/>
2593's GPS finally updated... and it's still not out of rehab yet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2593" routeTag="null" dirTag="null" lat="38.921909" lon="-76.971237" secsSinceReport="11037" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
ok, 3028 is back at FMR again
<vehicle id="3028" routeTag="null" dirTag="null" lat="38.842957" lon="-77.054047" secsSinceReport="46" predictable="false" heading="-4" speedKmHr="0.0"/>
I hope this one is rehab 1514, the reason is because 1514 is exactly half of 3028. last time this happened (as far as I know) was with 2228, which is rehab 1114.
last report of 3924 at Briggs Chaney Park and Ride
<vehicle id="3924" routeTag="null" dirTag="null" lat="39.077667" lon="-76.942436" secsSinceReport="1491" predictable="false" heading="-4" speedKmHr="0.0"/>
looks 7016 thing is jammed <Error shouldRetry="false">No data available for vehicle=7016</Error> and here in service http://www.youtube.com/watch?v=mPx5wzXH0r8&feature=feedu
2589 back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2589" routeTag="null" dirTag="null" lat="38.842762" lon="-77.052299" secsSinceReport="8494" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3025 at Bladensburg
<vehicle id="3025" routeTag="null" dirTag="null" lat="38.922813" lon="-76.971207" secsSinceReport="83875" predictable="false" heading="-4" speedKmHr="0.0"/>
and 3924 is still at Briggs Chaney P&R...
<vehicle id="3924" routeTag="null" dirTag="null" lat="39.077805" lon="-76.942398" secsSinceReport="996" predictable="false" heading="-4" speedKmHr="0.0"/>
Judging from its seconds count, 3016 could be getting rehabbed.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3016" routeTag="null" dirTag="null" lat="38.9230919" lon="-76.968857" secsSinceReport="1568711" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Same thing for 3015 and 3017, although I'm less certain about these two:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3015" routeTag="null" dirTag="null" lat="38.922813" lon="-76.968964" secsSinceReport="423565" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3017" routeTag="null" dirTag="null" lat="38.923061" lon="-76.969032" secsSinceReport="305251" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on August 21, 2011, 04:52:30 PM
Judging from its seconds count, 3016 could be getting rehabbed.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3016" routeTag="null" dirTag="null" lat="38.9230919" lon="-76.968857" secsSinceReport="1568711" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Same thing for 3015 and 3017, although I'm less certain about these two:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3015" routeTag="null" dirTag="null" lat="38.922813" lon="-76.968964" secsSinceReport="423565" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3017" routeTag="null" dirTag="null" lat="38.923061" lon="-76.969032" secsSinceReport="305251" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
yeah, I think 3001 is getting rehabbed too, the seconds count was at around 4 mil before resetting a couple of days ago, though it's still inactive apparently. I've also been keeping an eye on 3016, not sure about 3015 or 17 though
2617 at the DC DMV right now, should be back at FMR within a week or so
<vehicle id="2617" routeTag="null" dirTag="null" lat="38.877659" lon="-77.011559" secsSinceReport="164" predictable="false" heading="-4" speedKmHr="0.0"/>
Well, hello there...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4061" routeTag="G8" dirTag="G8_G8v2_0" lat="38.932907" lon="-76.983109" secsSinceReport="105" predictable="true" heading="75" speedKmHr="3.204"/>
</body>
EDIT: And now we've got 2630 at Bladensburg...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2630" routeTag="null" dirTag="null" lat="38.922676" lon="-76.971031" secsSinceReport="23136" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on August 26, 2011, 05:43:47 PMEDIT: And now we've got 2630 at Bladensburg...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2630" routeTag="null" dirTag="null" lat="38.922676" lon="-76.971031" secsSinceReport="23136" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
ah you beat me to it. that bus is a real mystery...
so it looks like we have a cutoff between Bladensburg's and Montgomery's Xcelsiors. 7038 and 7039
<vehicle id="7038" routeTag="null" dirTag="null" lat="38.921852" lon="-76.969139" secsSinceReport="50860" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7039" routeTag="Z8" dirTag="null" lat="39.045906" lon="-77.1079479" secsSinceReport="12342" predictable="false" heading="-4" speedKmHr="0.0"/>
and 7064 is the highest numbered one online so far
<vehicle id="7064" routeTag="null" dirTag="null" lat="38.941185" lon="-76.878067" secsSinceReport="79119" predictable="false" heading="-4" speedKmHr="0.0"/>
2617 and 2714 have both returned to FMR (After seeing 2712, I'm assuming 2714 is red as well).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2617" routeTag="null" dirTag="null" lat="38.842129" lon="-77.053627" secsSinceReport="50813" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2714" routeTag="null" dirTag="null" lat="38.841743" lon="-77.053665" secsSinceReport="54887" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And now 2621 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2621" routeTag="null" dirTag="null" lat="38.923172" lon="-76.970329" secsSinceReport="3811" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: As is 2669.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2669" routeTag="22A" dirTag="null" lat="38.923309" lon="-76.970467" secsSinceReport="13778" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
TRIPLE EDIT: Meanwhile, 2010 is back at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2010" routeTag="null" dirTag="null" lat="38.937336" lon="-76.875343" secsSinceReport="65719" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 3924 is at... Montgomery???
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3924" routeTag="null" dirTag="null" lat="39.046455" lon="-77.107178" secsSinceReport="77949" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And now 3950 is at Montgomery...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3950" routeTag="null" dirTag="null" lat="39.046097" lon="-77.108513" secsSinceReport="35065" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And it looks like 2082 is about to go the way of 2086...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2082" routeTag="null" dirTag="null" lat="39.023136" lon="-77.01709" secsSinceReport="28709138" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And apparently, 5224 got online not too long ago...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5224" routeTag="null" dirTag="null" lat="38.941101" lon="-76.878387" secsSinceReport="893023" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3924 at Briggs Chaney P&R again...
<vehicle id="3924" routeTag="null" dirTag="null" lat="39.077667" lon="-76.9424669" secsSinceReport="148" predictable="false" heading="-4" speedKmHr="0.0"/>
3950 back at Northern
<vehicle id="3950" routeTag="null" dirTag="null" lat="38.947319" lon="-77.031471" secsSinceReport="1431" predictable="false" heading="-4" speedKmHr="0.0"/>
and 4058, the bus that was apparently burnt to a toast a couple of years ago, is still online
<vehicle id="4058" routeTag="null" dirTag="null" lat="38.940689" lon="-76.878242" secsSinceReport="402491" predictable="false" heading="-4" speedKmHr="0.0"/>
4095 has made it past the 33 million mark, more than 32 million that 2086 did
<vehicle id="4095" routeTag="null" dirTag="null" lat="39.046371" lon="-77.108513" secsSinceReport="33150633" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on August 30, 2011, 12:19:35 AM
and 4058, the bus that was apparently burnt to a toast a couple of years ago, is still online
<vehicle id="4058" routeTag="null" dirTag="null" lat="38.940689" lon="-76.878242" secsSinceReport="402491" predictable="false" heading="-4" speedKmHr="0.0"/>
If I had to guess, I'd say 4058's GPS was put on a different bus; most likely an Xcelsior.
EDIT: 2728 at Johnson Truck Center in Landover:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2728" routeTag="null" dirTag="null" lat="38.94212" lon="-76.858292" secsSinceReport="11812" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
as a reply to Wes' post in the Sept Observations Thread, Montgomery did, in fact, give some LFAs to Landover
so far it's 6535-6539
<vehicle id="6535" routeTag="V12" dirTag="V12_V12_1" lat="38.861572" lon="-76.911636" secsSinceReport="115" predictable="true" heading="315" speedKmHr="49.86"/>
<vehicle id="6536" routeTag="V14" dirTag="V14_V14_0" lat="38.862839" lon="-76.894447" secsSinceReport="31" predictable="true" heading="195" speedKmHr="33.768"/>
<vehicle id="6537" routeTag="J12" dirTag="J12_J12_1" lat="38.829891" lon="-76.86673" secsSinceReport="302" predictable="true" heading="270" speedKmHr="78.84"/>
<vehicle id="6538" routeTag="C28" dirTag="C28_C28_0" lat="38.948059" lon="-76.73674" secsSinceReport="133" predictable="true" heading="30" speedKmHr="9.648"/>
<vehicle id="6539" routeTag="F14" dirTag="F14_F14_0" lat="38.9396739" lon="-76.86113" secsSinceReport="216" predictable="true" heading="315" speedKmHr="41.832"/>
and 6533 was last shown on I-70 near Frederick
<vehicle id="6533" routeTag="F4" dirTag="null" lat="39.428513" lon="-77.488823" secsSinceReport="1762833" predictable="false" heading="345" speedKmHr="80.46"/>
4288 on the R2.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4288" routeTag="R2" dirTag="R2_R2_0" lat="38.952213" lon="-77.001549" secsSinceReport="114" predictable="true" heading="98" speedKmHr="0.0"/>
</body>
EDIT: And 2728 is already back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2728" routeTag="null" dirTag="null" lat="38.841389" lon="-77.054016" secsSinceReport="2770" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: NewFlyer9736BCT on September 01, 2011, 06:38:05 PM
as a reply to Wes' post in the Sept Observations Thread, Montgomery did, in fact, give some LFAs to Landover
so far it's 6535-6539
<vehicle id="6535" routeTag="V12" dirTag="V12_V12_1" lat="38.861572" lon="-76.911636" secsSinceReport="115" predictable="true" heading="315" speedKmHr="49.86"/>
<vehicle id="6536" routeTag="V14" dirTag="V14_V14_0" lat="38.862839" lon="-76.894447" secsSinceReport="31" predictable="true" heading="195" speedKmHr="33.768"/>
<vehicle id="6537" routeTag="J12" dirTag="J12_J12_1" lat="38.829891" lon="-76.86673" secsSinceReport="302" predictable="true" heading="270" speedKmHr="78.84"/>
<vehicle id="6538" routeTag="C28" dirTag="C28_C28_0" lat="38.948059" lon="-76.73674" secsSinceReport="133" predictable="true" heading="30" speedKmHr="9.648"/>
<vehicle id="6539" routeTag="F14" dirTag="F14_F14_0" lat="38.9396739" lon="-76.86113" secsSinceReport="216" predictable="true" heading="315" speedKmHr="41.832"/>
and 6533 was last shown on I-70 near Frederick
<vehicle id="6533" routeTag="F4" dirTag="null" lat="39.428513" lon="-77.488823" secsSinceReport="1762833" predictable="false" heading="345" speedKmHr="80.46"/>
I think the thing is messed up. I checked it again and everything there was the same.
2205-2209 are at Montgomery
<vehicle id="2205" routeTag="null" dirTag="null" lat="39.046043" lon="-77.107285" secsSinceReport="78" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2206" routeTag="null" dirTag="null" lat="39.046455" lon="-77.108437" secsSinceReport="57728" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2207" routeTag="null" dirTag="null" lat="39.046207" lon="-77.107285" secsSinceReport="1147" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2208" routeTag="null" dirTag="null" lat="39.046234" lon="-77.107178" secsSinceReport="2057" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2209" routeTag="null" dirTag="null" lat="39.046757" lon="-77.108437" secsSinceReport="2244" predictable="false" heading="-4" speedKmHr="0.0"/>
POST UPDATE:
2587 now at Bladensburg
<vehicle id="2587" routeTag="null" dirTag="null" lat="38.920891" lon="-76.970367" secsSinceReport="40478" predictable="false" heading="-4" speedKmHr="0.0"/>
alright I found out which buses have the GPS's of 4042 and 4061:
4042 = 7016 (seen on H4)
4061 = 7032 (seen on D6)
...even though 7032's GPS is already online, showing that it's sitting at CET
2506 is at Bladensburg, even though it's already rehabbed.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2506" routeTag="null" dirTag="null" lat="38.922047" lon="-76.971275" secsSinceReport="102995" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And now 2717 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2717" routeTag="null" dirTag="null" lat="38.84301" lon="-77.053314" secsSinceReport="3867" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: ...and replacing it at Bladensburg is 2719.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2719" routeTag="5A" dirTag="null" lat="38.923367" lon="-76.970467" secsSinceReport="14806" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I'll save you the trouble of triple editing...
2653 finally back at FMR, I wonder what's holding up 2593 now
<vehicle id="2653" routeTag="null" dirTag="null" lat="38.842735" lon="-77.052338" secsSinceReport="10142" predictable="false" heading="-4" speedKmHr="0.0"/>
EDIT: and 3027 at Bladensburg
<vehicle id="3027" routeTag="null" dirTag="null" lat="38.923447" lon="-76.970543" secsSinceReport="18988" predictable="false" heading="-4" speedKmHr="0.0"/>
4271 on the 42.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4271" routeTag="42" dirTag="42_42_1" lat="38.89867" lon="-77.023949" secsSinceReport="10" predictable="true" heading="180" speedKmHr="19.296"/>
</body>
3001 at the DC DMV; it should be back in service real soon.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3001" routeTag="null" dirTag="null" lat="38.877441" lon="-77.010757" secsSinceReport="83" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4209 at West Ox
<vehicle id="4209" routeTag="null" dirTag="null" lat="38.848591" lon="-77.378395" secsSinceReport="74" predictable="false" heading="-4" speedKmHr="0.0"/>
2707 back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2707" routeTag="null" dirTag="null" lat="38.842571" lon="-77.052757" secsSinceReport="243" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 2547 takes its place at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2547" routeTag="25B" dirTag="null" lat="38.923229" lon="-76.970398" secsSinceReport="8631" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
More 6500s are fleeing to Landover; so far, it's 6540-6544.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6540" routeTag="null" dirTag="null" lat="38.937553" lon="-76.8748169" secsSinceReport="746" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6541" routeTag="null" dirTag="null" lat="38.937336" lon="-76.874535" secsSinceReport="246" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6542" routeTag="F4" dirTag="F4_F4_0" lat="38.996735" lon="-77.027557" secsSinceReport="120" predictable="true" heading="23" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6543" routeTag="null" dirTag="null" lat="38.965248" lon="-76.90432" secsSinceReport="20" predictable="false" heading="195" speedKmHr="82.044"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6544" routeTag="P12" dirTag="P12_P12v2_0" lat="38.942753" lon="-76.857491" secsSinceReport="1" predictable="true" heading="135" speedKmHr="19.296"/>
</body>
EDIT: And 6024 is at Bladensburg. Or at least, NEAR Bladensburg (I don't know if its coordinates are exactly within Bladensburg's boundaries).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6024" routeTag="null" dirTag="null" lat="38.9257009" lon="-76.971519" secsSinceReport="90276" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: 2336 is back offline already? I don't think it had even hit the 10 million mark yet!
<body copyright="All data copyright WMATA Washington 2011.">
<Error shouldRetry="false"> No data available for vehicle=2336 </Error>
</body>
2711 and 3021 at Bladensburg
<vehicle id="2711" routeTag="null" dirTag="null" lat="38.92342" lon="-76.970505" secsSinceReport="1383" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3021" routeTag="3T" dirTag="null" lat="38.923336" lon="-76.970436" secsSinceReport="1235" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: RideOn5905 on September 09, 2011, 02:33:47 PM
EDIT: And 6024 is at Bladensburg. Or at least, NEAR Bladensburg (I don't know if its coordinates are exactly within Bladensburg's boundaries).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6024" routeTag="null" dirTag="null" lat="38.9257009" lon="-76.971519" secsSinceReport="90276" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: 2336 is back offline already? I don't think it had even hit the 10 million mark yet!
<body copyright="All data copyright WMATA Washington 2011.">
<Error shouldRetry="false"> No data available for vehicle=2336 </Error>
</body>
6024 - the coords show that it's at Franklin Street NE, a couple blocks north of the division
2336 - yeah I saw that too, I guess they manually shut off the GPS, or I don't know, I wonder what will become of that bus in the end
2596 back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2596" routeTag="null" dirTag="null" lat="38.843037" lon="-77.052933" secsSinceReport="9801" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: On that note, here's the list of Orion VIIs that are being rehabbed:
2517, 2547, 2548, 2558, 2587, 2593 (Which, might I add, has been at B-burg since MAY; what's taking it so long?!), 2621, 2623, 2624, 2630, 2631, 2657, 2669, 2701, 2711, 2719, 2720, 3001 (should be back in service within a few days), 3016 (I'm sure of it), 3021, 3025, and 3027.
I think 6538 and 6539 are new to Landover too.
Quote from: Super G on September 10, 2011, 10:18:10 PM
I think 6538 and 6539 are new to Landover too.
Yeah, 6535-6544 have all moved to Landover from Montgomery.
In other news, 7065 is now online, I think it's the highest-numbered Xcelsior so far.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7065" routeTag="null" dirTag="null" lat="38.940773" lon="-76.878174" secsSinceReport="286572" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
and now 6024 is actually IN Bladensburg division right now. first hybrid rehab?
<vehicle id="6024" routeTag="null" dirTag="null" lat="38.923119" lon="-76.971275" secsSinceReport="5589" predictable="false" heading="-4" speedKmHr="0.0"/>
EDIT - 3022 at Bladensburg as well
<vehicle id="3022" routeTag="null" dirTag="null" lat="38.923309" lon="-76.970467" secsSinceReport="16190" predictable="false" heading="-4" speedKmHr="0.0"/>
7006 on the X9
- <predictions agencyTitle="WMATA Washington" routeTitle="X9 BENNING RD-H ST EXP" routeTag="X9" stopTitle="Benning Rd Ne + 19th St Ne" stopTag="5758">
- <direction title="East to Capitol Heights Station">
<prediction epochTime="1315857863590" seconds="997" minutes="16" isDeparture="false" dirTag="X9_X9_0" vehicle="2825" block="BX91" tripTag="3862366" />
<prediction epochTime="1315858928580" seconds="2062" minutes="34" isDeparture="false" affectedByLayover="true" dirTag="X9_X9_0" vehicle="
7006" block="BX93" tripTag="3862367" />
7026 on the X9
<predictions agencyTitle="
WMATA Washington" routeTitle="
X9 BENNING RD-H ST EXP" routeTag="
X9" stopTitle="
Benning Rd Ne + 19th St Ne" stopTag="
5758">
- (http://www.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=1001088#) <direction title="
East to Capitol Heights Station"> <prediction epochTime="
1315943563562" seconds="
1111" minutes="
18" isDeparture="
false" dirTag="
X9_X9_0" vehicle="
2821" block="
BX90" tripTag="
3862365" /> <prediction epochTime="
1315947128580" seconds="
4676" minutes="
77" isDeparture="
false" affectedByLayover="
true" dirTag="
X9_X9_0" vehicle="
7026" block="
BX92" tripTag="
3862369" />
6567 on the F4. Since when was West Ox involved in this?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6567" routeTag="F4" dirTag="F4_F4_0" lat="38.958866" lon="-76.920387" secsSinceReport="10" predictable="true" heading="94" speedKmHr="0.0"/>
</body>
EDIT: And now 6303 at West Ox...?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6303" routeTag="J12" dirTag="null" lat="38.848675" lon="-77.378357" secsSinceReport="37" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: 6201 on Columbia Pike (US 29) near White Oak. Could it be...?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6201" routeTag="null" dirTag="null" lat="39.054512" lon="-76.973724" secsSinceReport="21" predictable="false" heading="45" speedKmHr="8.028"/>
</body>
(I'm putting this in a separate post, so as to avoid having to triple edit.)
6198 on the Z11 and 6199 on the K6! I think Annex is indeed giving some D40LFRs back to Montgomery! For the time being, at least.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6198" routeTag="Z11" dirTag="Z11_Z11_1" lat="38.994728" lon="-77.0287479" secsSinceReport="349" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6199" routeTag="K6" dirTag="K6_K6v1_1" lat="39.054649" lon="-77.080017" secsSinceReport="108" predictable="true" heading="120" speedKmHr="57.924"/>
</body>
I know 6199s coordinates aren't where the K6 goes, but I'm just happy they're back.
7065 is at Southern Avenue "All data copyright WMATA Washington 2011.">
<vehicle id="7065" routeTag="null" dirTag="null" lat="38.872601" lon="-76.933441" secsSinceReport="49379" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2724 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2724" routeTag="null" dirTag="null" lat="38.922981" lon="-76.971169" secsSinceReport="31518" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2517's GPS timeout is over 7 million seconds now, so it may be back at FMR already, but with a broken GPS, much like what happened with 2672 when it got out. Then again, the same thing was said about 2593, and it's STILL at Bladensburg, so... I don't know.
2593 at the DC DMV. In a few days, it should finally be back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2593" routeTag="null" dirTag="null" lat="38.878017" lon="-77.011627" secsSinceReport="190" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 7061, 7062, and 7064 are also at Annex alongside 7065.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7061" routeTag="null" dirTag="null" lat="38.872406" lon="-76.933472" secsSinceReport="2519" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7062" routeTag="null" dirTag="null" lat="38.872601" lon="-76.933441" secsSinceReport="2474" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7064" routeTag="null" dirTag="null" lat="38.872986" lon="-76.932007" secsSinceReport="118" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7033 on the C8, and 7035 on the C4.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7033" routeTag="C8" dirTag="C8_C8v2_0" lat="39.0661739" lon="-77.026573" secsSinceReport="126" predictable="true" heading="90" speedKmHr="78.84"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7035" routeTag="C4" dirTag="C4_C4_0" lat="39.038948" lon="-77.049393" secsSinceReport="42" predictable="true" heading="256" speedKmHr="0.0"/>
</body>
heh, 7061 was at Montgomery not too long ago, that's a fast change
2724's GPS was timed out around 4 million seconds before finally updating (I think it was shown at Dulles Airport), I somehow had a feeling it would end up at Bburg
anyways, 2707 is back at Bladensburg, if it was red, then I hope it's back to be painted blue, who knows
<vehicle id="2707" routeTag="null" dirTag="null" lat="38.920891" lon="-76.969978" secsSinceReport="25792" predictable="false" heading="-4" speedKmHr="0.0"/>
6201 has also made its way back to Montgomery
<vehicle id="6201" routeTag="J2" dirTag="J2_J2_0" lat="38.98502" lon="-77.097031" secsSinceReport="443" predictable="true" heading="255" speedKmHr="11.232"/>
I saw 4340, 5301, and 5306 all in person at Bladensburg Division today. However, Nextbus says otherwise
<vehicle id="4340" routeTag="null" dirTag="null" lat="39.066666" lon="-77.019119" secsSinceReport="9202172" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="5301" routeTag="null" dirTag="null" lat="38.948059" lon="-77.032242" secsSinceReport="6815955" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="5306" routeTag="null" dirTag="null" lat="38.946438" lon="-77.031685" secsSinceReport="903529" predictable="false" heading="-4" speedKmHr="0.0"/>
6012 is at Bladensburg, and I have a feeling that 6007 might also be there soon (seconds count is past 17 million).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6012" routeTag="null" dirTag="null" lat="38.923145" lon="-76.9711" secsSinceReport="206442" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Oh, and I forgot to mention this, but 6512 is there, too.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6512" routeTag="null" dirTag="null" lat="38.9211079" lon="-76.970436" secsSinceReport="464988" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 6530's GPS doesn't seem to be working; I remember seeing it on both of the Red Line shuttles from last month, but it's GPS says otherwise.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6530" routeTag="null" dirTag="null" lat="38.937168" lon="-76.8748169" secsSinceReport="4029434" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6024 is back at Montgomery, if it was at Bladensburg for that short amount of time, most likely it was for repairs or something.
<vehicle id="6024" routeTag="null" dirTag="null" lat="39.046783" lon="-77.109772" secsSinceReport="1609" predictable="false" heading="-4" speedKmHr="0.0"/>
And now, 6016 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6016" routeTag="null" dirTag="null" lat="38.922211" lon="-76.971558" secsSinceReport="25501" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7092 on the X9.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7092" routeTag="X9" dirTag="X9_X9_0" lat="38.899769" lon="-77.023216" secsSinceReport="9" predictable="true" heading="91" speedKmHr="1.584"/>
</body>
2513 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2513" routeTag="null" dirTag="null" lat="38.923367" lon="-76.970467" secsSinceReport="463" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: So is 2638.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2638" routeTag="7A" dirTag="null" lat="38.923172" lon="-76.970505" secsSinceReport="3849" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And after spending FOUR MONTHS at Bladensburg, 2593 has FINALLY returned to Four Mile Run!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2593" routeTag="null" dirTag="null" lat="38.842735" lon="-77.054123" secsSinceReport="87" predictable="false" heading="270" speedKmHr="28.943999999999996"/>
</body>
And after spending less time there than 2593, 2517 has also returned to Four Mile Run.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2517" routeTag="null" dirTag="null" lat="38.844357" lon="-77.054016" secsSinceReport="25" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Oh, my God... (sadly, it's most likely an Xcelsior)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9322" routeTag="L2" dirTag="L2_L2_0" lat="38.907799" lon="-77.044807" secsSinceReport="98" predictable="true" heading="15" speedKmHr="17.676"/>
</body>
7031 and 7032 (aka 4061) are now at Montgomery
<vehicle id="7031" routeTag="null" dirTag="null" lat="39.046619" lon="-77.108093" secsSinceReport="6912" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4061" routeTag="null" dirTag="null" lat="39.046398" lon="-77.108093" secsSinceReport="1169" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: RideOn5905 on September 23, 2011, 03:51:33 PM
Oh, my God... (sadly, it's most likely an Xcelsior)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9322" routeTag="L2" dirTag="L2_L2_0" lat="38.907799" lon="-77.044807" secsSinceReport="98" predictable="true" heading="15" speedKmHr="17.676"/>
</body>
Or maybe its an Orion. I got shocked the other week when "4042" came down on the C8 and was really 4343.
6197 on the Y9. Sweet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6197" routeTag="Y9" dirTag="Y9_Y9_1" lat="39.061443" lon="-77.052612" secsSinceReport="54" predictable="true" heading="90" speedKmHr="11.232"/>
</body>
I tried to see if any more D40LFRs had gone to Montgomery, but for whatever reason, NextBus has no data on 6194, 6196, 6198, 6199, or 6200 (6195 was at Archives). My guess is that work is being done to their GPS's.
Quote from: 79MetroExtraMD on September 25, 2011, 08:51:35 AM
Quote from: RideOn5905 on September 23, 2011, 03:51:33 PM
Oh, my God... (sadly, it's most likely an Xcelsior)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9322" routeTag="L2" dirTag="L2_L2_0" lat="38.907799" lon="-77.044807" secsSinceReport="98" predictable="true" heading="15" speedKmHr="17.676"/>
</body>
Or maybe its an Orion. I got shocked the other week when "4042" came down on the C8 and was really 4343.
I thought 4042 was 7016...you sure it wasn't 4085? I haven't figured out what that one is yet.
Quote from: RideOn5905 on September 25, 2011, 10:26:46 AM
6197 on the Y9. Sweet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6197" routeTag="Y9" dirTag="Y9_Y9_1" lat="39.061443" lon="-77.052612" secsSinceReport="54" predictable="true" heading="90" speedKmHr="11.232"/>
</body>
I tried to see if any more D40LFRs had gone to Montgomery, but for whatever reason, NextBus has no data on 6194, 6196, 6198, 6199, or 6200 (6195 was at Archives). My guess is that work is being done to their GPS's.
noice, more D40LFRs for Montgomery.
apparently Nextbus may be down or something, almost ALL buses show no data
Quote from: NewFlyer9736BCT on September 25, 2011, 11:32:46 AM
Quote from: 79MetroExtraMD on September 25, 2011, 08:51:35 AM
Quote from: RideOn5905 on September 23, 2011, 03:51:33 PM
Oh, my God... (sadly, it's most likely an Xcelsior)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="9322" routeTag="L2" dirTag="L2_L2_0" lat="38.907799" lon="-77.044807" secsSinceReport="98" predictable="true" heading="15" speedKmHr="17.676"/>
</body>
Or maybe its an Orion. I got shocked the other week when "4042" came down on the C8 and was really 4343.
I thought 4042 was 7016...you sure it wasn't 4085? I haven't figured out what that one is yet.
Quote from: RideOn5905 on September 25, 2011, 10:26:46 AM
6197 on the Y9. Sweet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6197" routeTag="Y9" dirTag="Y9_Y9_1" lat="39.061443" lon="-77.052612" secsSinceReport="54" predictable="true" heading="90" speedKmHr="11.232"/>
</body>
I tried to see if any more D40LFRs had gone to Montgomery, but for whatever reason, NextBus has no data on 6194, 6196, 6198, 6199, or 6200 (6195 was at Archives). My guess is that work is being done to their GPS's.
noice, more D40LFRs for Montgomery.
apparently Nextbus may be down or something, almost ALL buses show no data
4343 is showing at Montgomery, while 4085 is offline. To tell you the truth, when it comes to the latter, your guess is as good as mine. And as for NextBus, this may have something to do with the new 74 route; I'm not sure, though. Also, 6194 updated; it's still at Annex. All that's left is 6196.
I was on K Street near Conn. Ave on Friday (09/23) and caught this... sort of at the last minute so I was happy to even get the picture at all. The 3Y "LEE HEIGHTS" destination was already reprogrammed to read "HARRISON ST & LEE HIGHWAY" for the Sept 2011 service changes.
Quote from: Transport on September 26, 2011, 02:34:18 PM
I was on K Street near Conn. Ave on Friday (09/23) and caught this... sort of at the last minute so I was happy to even get the picture at all. The 3Y "LEE HEIGHTS" destination was already reprogrammed to read "HARRISON ST & LEE HIGHWAY" for the Sept 2011 service changes.
The WMATA announcement of the changes on their website said that would happen...
2506 and 2630 are both back at FMR. (I'm not sure if the latter is rehabbed)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2506" routeTag="null" dirTag="null" lat="38.843311" lon="-77.054298" secsSinceReport="14321" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2630" routeTag="null" dirTag="null" lat="38.84433" lon="-77.054016" secsSinceReport="281" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And 2726 is at Johnson Truck Center in Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2726" routeTag="null" dirTag="null" lat="38.942726" lon="-76.858192" secsSinceReport="18039" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2667 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2667" routeTag="null" dirTag="null" lat="38.923119" lon="-76.970398" secsSinceReport="105" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And now 6177 is there as well; most likely for some repairs.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6177" routeTag="null" dirTag="null" lat="38.922375" lon="-76.970924" secsSinceReport="28510" predictable="false" heading="345" speedKmHr="6.408"/>
</body>
6545 on the F6, 6547 on the F1, and 6548 on the F14.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6545" routeTag="F6" dirTag="F6_F6_1" lat="38.965137" lon="-76.95549" secsSinceReport="36" predictable="true" heading="345" speedKmHr="6.408"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6547" routeTag="F1" dirTag="F1_F1_1" lat="38.93541" lon="-76.963753" secsSinceReport="224" predictable="true" heading="315" speedKmHr="24.12"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6548" routeTag="F14" dirTag="F14_F14_1" lat="38.888744" lon="-76.908379" secsSinceReport="345" predictable="true" heading="105" speedKmHr="53.1"/>
</body>
2657 at Davidsonville Park & Ride.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2657" routeTag="null" dirTag="null" lat="38.959309" lon="-76.651337" secsSinceReport="543" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 6546 is also at Landover. (6549 has no data)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6546" routeTag="T18" dirTag="null" lat="38.937389" lon="-76.874779" secsSinceReport="511" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
It's a changing of the 2700s; 2701 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2701" routeTag="null" dirTag="null" lat="38.843063" lon="-77.053383" secsSinceReport="6683" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2715 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2715" routeTag="5A" dirTag="null" lat="38.923229" lon="-76.970436" secsSinceReport="1837" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And in other news, 3950 is at Annex.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3950" routeTag="W6" dirTag="null" lat="38.87315" lon="-76.932915" secsSinceReport="25813" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6120 on the 79 B777
- <predictions agencyTitle="WMATA Washington" routeTitle="79 GEORGIA AVE RAPID" routeTag="79" stopTitle="Georgia Ave + Missouri Ave" stopTag="8878">
- <direction title="North to Silver Spring Station">
<prediction epochTime="1317417993748" seconds="143" minutes="2" isDeparture="false" dirTag="79_79_1" vehicle="2805" block="B774" tripTag="3756661" />
<prediction epochTime="1317418123664" seconds="273" minutes="4" isDeparture="false" dirTag="79_79_1" vehicle="
6120" block="
B777" tripTag="3756662" />
Quote from: 79MetroExtraMD on September 30, 2011, 05:24:34 PM
6120 on the 79 B777
- <predictions agencyTitle="WMATA Washington" routeTitle="79 GEORGIA AVE RAPID" routeTag="79" stopTitle="Georgia Ave + Missouri Ave" stopTag="8878">
- <direction title="North to Silver Spring Station">
<prediction epochTime="1317417993748" seconds="143" minutes="2" isDeparture="false" dirTag="79_79_1" vehicle="2805" block="B774" tripTag="3756661" />
<prediction epochTime="1317418123664" seconds="273" minutes="4" isDeparture="false" dirTag="79_79_1" vehicle="6120" block="B777" tripTag="3756662" />
now that weird i wonder what going on?
Quote from: DCAreaTransitFan on September 30, 2011, 07:36:52 PM
Quote from: 79MetroExtraMD on September 30, 2011, 05:24:34 PM
6120 on the 79 B777
- <predictions agencyTitle="WMATA Washington" routeTitle="79 GEORGIA AVE RAPID" routeTag="79" stopTitle="Georgia Ave + Missouri Ave" stopTag="8878">
- <direction title="North to Silver Spring Station">
<prediction epochTime="1317417993748" seconds="143" minutes="2" isDeparture="false" dirTag="79_79_1" vehicle="2805" block="B774" tripTag="3756661" />
<prediction epochTime="1317418123664" seconds="273" minutes="4" isDeparture="false" dirTag="79_79_1" vehicle="6120" block="B777" tripTag="3756662" />
now that weird i wonder what going on?
Strategic possibly.
2707 back at FMR; hopefully for good this time.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2707" routeTag="null" dirTag="null" lat="38.842899" lon="-77.053879" secsSinceReport="11543" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6016 back at Montgomery
<vehicle id="6016" routeTag="J2" dirTag="null" lat="39.046921" lon="-77.107597" secsSinceReport="60391" predictable="false" heading="-4" speedKmHr="0.0"/>
6007 finally updated
<vehicle id="6007" routeTag="null" dirTag="null" lat="38.936317" lon="-76.874573" secsSinceReport="1003" predictable="false" heading="-4" speedKmHr="0.0"/>
2720 is in this...place near Bladensburg Division (I know it's been at Bburg getting rehabbed, might be done soon?)
<vehicle id="2720" routeTag="null" dirTag="null" lat="38.919266" lon="-76.967461" secsSinceReport="12107" predictable="false" heading="-4" speedKmHr="0.0"/>
no info showing for:
2503, 2513*, 2547*, 2548*, 2613, 2621*, 2638*, 2652, 2669*, 2679, 2719*, 2726, 2728, 3005, 3021*, 3022*, 3027*
* these buses were last shown at Bladensburg (3005 obviously is a Bladensburg bus)
oh and 2630 is rehabbed after all, I have a picture to upload later, plus it's rehab # 1525
check out where 3025 is...
<vehicle id="3025" routeTag="null" dirTag="null" lat="38.8971019" lon="-77.541214" secsSinceReport="76689" predictable="false" heading="270" speedKmHr="83.664"/>
it's somewhere west of Chantilly, what's there? no idea, but if it's in Virginia, it may be finished with rehab, but who knows
6124, what are you doing on the 36 on a Sunday evening?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6124" routeTag="36" dirTag="36_36_1" lat="38.961262" lon="-77.0860749" secsSinceReport="40" predictable="true" heading="150" speedKmHr="30.564"/>
</body>
4032 on the 2B (obvious GPS substitute is obvious).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4032" routeTag="2B" dirTag="2B_2B_1" lat="38.88525" lon="-77.117577" secsSinceReport="89" predictable="true" heading="87" speedKmHr="0.0"/>
</body>
2623 is at the D.C. DMV inspection station; should be back in service within a week.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2623" routeTag="null" dirTag="null" lat="38.877743" lon="-77.011597" secsSinceReport="57" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Now 2501 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2501" routeTag="null" dirTag="null" lat="38.923256" lon="-76.970398" secsSinceReport="2344" predictable="false" heading="150" speedKmHr="3.204"/>
</body>
2657 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2657" routeTag="null" dirTag="null" lat="38.84444" lon="-77.053978" secsSinceReport="12673" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Something just occurred to me... I have a theory as to what "4085" really is.
A few GPS's from the Flxible Metro E's have shown up online, such as 4042, 4058, and, of course, 4085. Most of them appeared at around the same time that the Xcelsiors have entered service. As George pointed out in an earlier post, 4042 is really 7016, and 4061 is really 7032. However, I first noted 4085's appearance in May, before the Xcelsiors had entered revenue service. I also remember an accident on University Blvd. involving two Metrobuses around this time last year. The buses involved were 6027 and 2082; the latter had rear-ended the former. Shortly afterwards, 6027 had returned to service. 2082, however, has not. My memory is a bit photographic, but I think the damage 2082 had sustained was certainly fixable. For the record, the last location NextBus had of 2082 before it went offline was at the site of the crash. Roughly seven months after the crash, 4085 showed up on NextBus.
Long story short: I believe "4085" is really 2082. I could be wrong on this, but this is just my two cents on the matter.
2551 on the 5A. That's odd, seeing a bus on the 5A that doesn't start with the number 27...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2551" routeTag="5A" dirTag="5A_5A_1" lat="38.8972399" lon="-77.068222" secsSinceReport="66" predictable="true" heading="330" speedKmHr="69.192"/>
</body>
ugh, I almost figured out what 4032 was today, but that ended up not happening. Plus, without that luggage rack, that 5A bus must have been a crush load with those luggages in the way
Oh, I almost forgot: 6151 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6151" routeTag="null" dirTag="null" lat="38.9218789" lon="-76.971062" secsSinceReport="190262" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7098 G8 BG58
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
G8 RHODE ISLAND AVE" routeTag="
G8" stopTitle="
Brookland Station + Bus Bay H" stopTag="
13577"> - (http://forums.dctransit.info/#) <direction title="
East to Avondale">
<prediction epochTime="
1318023360000" seconds="
1744" minutes="
29" isDeparture="
true" affectedByLayover="
true" dirTag="
G8_G8v2_0" vehicle="
7098" block="
BG58" tripTag="
3755473" />
6136 is at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6136" routeTag="null" dirTag="null" lat="38.936565" lon="-76.874672" secsSinceReport="27639" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: I almost forgot: We have another non-airport bus on the 5A.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2665" routeTag="5A" dirTag="5A_5A_0" lat="38.953587" lon="-77.447342" secsSinceReport="149" predictable="true" heading="102" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on October 08, 2011, 12:31:57 PM
EDIT: I almost forgot: We have another non-airport bus on the 5A.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2665" routeTag="5A" dirTag="5A_5A_0" lat="38.953587" lon="-77.447342" secsSinceReport="149" predictable="true" heading="102" speedKmHr="0.0"/>
</body>
That's the kind of bus that SHOULD be on the 5A, except with suburban seating and overhead luggage racks
I was referring to the paint scheme and green signs
Quote from: NewFlyer9736BCT on October 08, 2011, 03:40:21 PM
Quote from: RideOn5905 on October 08, 2011, 12:31:57 PM
EDIT: I almost forgot: We have another non-airport bus on the 5A.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2665" routeTag="5A" dirTag="5A_5A_0" lat="38.953587" lon="-77.447342" secsSinceReport="149" predictable="true" heading="102" speedKmHr="0.0"/>
</body>
That's the kind of bus that SHOULD be on the 5A, except with suburban seating and overhead luggage racks
I was referring to the paint scheme and green signs
Yeah. It's a real shame they went with the local scheme for the 2700s. Those things were practically tailor-made for the express scheme. I don't mind them keeping the regular signs, though.
2462 and 5321 are finally back online!
<vehicle id="2462" routeTag="null" dirTag="null" lat="38.922897" lon="-76.971344" secsSinceReport="3167" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="5321" routeTag="null" dirTag="null" lat="38.947319" lon="-77.031616" secsSinceReport="18166" predictable="false" heading="-4" speedKmHr="0.0"/>
looks like 2582 may be spending the night at West Ox
<vehicle id="2582" routeTag="null" dirTag="null" lat="38.848701" lon="-77.3785709" secsSinceReport="1918" predictable="false" heading="-4" speedKmHr="0.0"/>
2025 is, once again, at West Ox (2024 may be as well, but there's no info showing for that bus)
<vehicle id="2025" routeTag="null" dirTag="null" lat="38.849556" lon="-77.377731" secsSinceReport="1298" predictable="false" heading="-4" speedKmHr="0.0"/>
6567 at Landover
<vehicle id="6567" routeTag="null" dirTag="null" lat="38.936867" lon="-76.873871" secsSinceReport="2584" predictable="false" heading="-4" speedKmHr="0.0"/>
3032 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3032" routeTag="23A" dirTag="null" lat="38.923393" lon="-76.970467" secsSinceReport="130" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: NewFlyer9736BCT on October 11, 2011, 01:02:21 PM
2462 and 5321 are finally back online!
<vehicle id="2462" routeTag="null" dirTag="null" lat="38.922897" lon="-76.971344" secsSinceReport="3167" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="5321" routeTag="null" dirTag="null" lat="38.947319" lon="-77.031616" secsSinceReport="18166" predictable="false" heading="-4" speedKmHr="0.0"/>
I don't know if you've seen the October Observations thread, but rideonrulez says that 5321 is rehabbed.
On another note, we've got another Orion VII being held up at Bladensburg; this time, it's 2631, which has been there since June, I believe.
Quote from: RideOn5905 on October 12, 2011, 10:50:00 AM
I don't know if you've seen the October Observations thread, but rideonrulez says that 5321 is rehabbed.
awesome! i wonder what's become of 5306 and 5320. I last saw 5306 at Bladensburg about a month ago, and 5320 had a 25+ million second time out before every bus's GPS was reset, and now 5303's GPS shows no data.
also, 2623 and 2724 are back at FMR (I do believe 2631 was at Bladensburg first, oh well)
<vehicle id="2623" routeTag="null" dirTag="null" lat="38.842487" lon="-77.052231" secsSinceReport="5457" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2724" routeTag="null" dirTag="null" lat="38.8429829" lon="-77.053001" secsSinceReport="375" predictable="false" heading="-4" speedKmHr="0.0"/>
I just checked, it seems you first spotted 2631 at Blade in late June. Hopefully, it'll be back before too long (although I have a feeling it'll be in a couple of weeks, making it a four-month stay like 2593).
Oh, and speaking of Bladensburg, 2634 is now there.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2634" routeTag="null" dirTag="null" lat="38.923916" lon="-76.970016" secsSinceReport="6401" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Check this out:
QuotePosted 10/4/2011
Effective immediately until further notice:
Z8 - Fairland Line
Due to area construction, Metro's standard buses will not operate on Castle Blvd, north of Briggs Chaney Road.
Castle Blvd, including the bus turn-around at its north end, will be served by a small shuttle, connecting passengers from Briggs Chaney Park-and-Ride Lot.
All passengers wanting service to Castle Blvd should use the small shuttle from Briggs Chaney Park-and-Ride Lot.
The remainder of the Z8 route will continue to be served by Metro's standard buses.
I'd bet that's what 3924 is there for.
Quote from: RideOn5905 on October 12, 2011, 02:33:35 PM
Oh, and speaking of Bladensburg, 2634 is now there.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2634" routeTag="null" dirTag="null" lat="38.923916" lon="-76.970016" secsSinceReport="6401" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
well that sucks, I really loved the JD on that bus, at least I have an audio recording of it
Quote from: RideOn5905 on October 12, 2011, 02:33:35 PM
QuotePosted 10/4/2011
Effective immediately until further notice:
Z8 - Fairland Line
Due to area construction, Metro's standard buses will not operate on Castle Blvd, north of Briggs Chaney Road.
Castle Blvd, including the bus turn-around at its north end, will be served by a small shuttle, connecting passengers from Briggs Chaney Park-and-Ride Lot.
All passengers wanting service to Castle Blvd should use the small shuttle from Briggs Chaney Park-and-Ride Lot.
The remainder of the Z8 route will continue to be served by Metro's standard buses.
I'd bet that's what 3924 is there for.
hmm...that may be, although 3924 has been hanging around there for well over a month
also, I saw 5321 today, it's rehabbed. it had an "out of service" paper on the dashboard, just like the one I saw on 5306. Guess this means 5306 will be getting rehabbed as well?
7016 and 7032 both have working GPS's now.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7016" routeTag="D8" dirTag="D8_D8_1" lat="38.925373" lon="-76.996162" secsSinceReport="126" predictable="true" heading="360" speedKmHr="6.408"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7032" routeTag="T2" dirTag="T2_T2_0" lat="39.022392" lon="-77.207352" secsSinceReport="13" predictable="true" heading="15" speedKmHr="74.016"/>
</body>
EDIT: And now 2545 is at Bladensburg; repair work, most likely.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2545" routeTag="null" dirTag="null" lat="38.923008" lon="-76.970749" secsSinceReport="5232" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6177 and 2548 are back at their respective homes.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6177" routeTag="null" dirTag="null" lat="38.87249" lon="-76.932915" secsSinceReport="40" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2548" routeTag="null" dirTag="null" lat="38.842899" lon="-77.053284" secsSinceReport="10774" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2709 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2709" routeTag="null" dirTag="null" lat="38.923145" lon="-76.970398" secsSinceReport="2808" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6573-6576 are now at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6573" routeTag="1A" dirTag="null" lat="38.936127" lon="-76.87513" secsSinceReport="2763" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6574" routeTag="null" dirTag="null" lat="38.9372789" lon="-76.874397" secsSinceReport="48159" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6575" routeTag="F4" dirTag="F4_F4_0" lat="38.960629" lon="-76.911919" secsSinceReport="183" predictable="true" heading="60" speedKmHr="9.648"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6576" routeTag="1A" dirTag="1A_1A_0" lat="38.936043" lon="-76.875061" secsSinceReport="7856" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
And 6305, 6306, 6308, and 6309 have moved to West Ox (6307 has no data).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6305" routeTag="null" dirTag="null" lat="38.848812" lon="-77.378258" secsSinceReport="122610" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6306" routeTag="null" dirTag="null" lat="38.848785" lon="-77.378357" secsSinceReport="121790" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6308" routeTag="null" dirTag="null" lat="38.848427" lon="-77.374619" secsSinceReport="114508" predictable="false" heading="315" speedKmHr="24.12"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6309" routeTag="null" dirTag="null" lat="38.848785" lon="-77.37822" secsSinceReport="114111" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And on top of that, 2558 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2558" routeTag="null" dirTag="null" lat="38.842709" lon="-77.05146" secsSinceReport="558" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: ...with 2723 replacing it at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2723" routeTag="5A" dirTag="null" lat="38.922512" lon="-76.970123" secsSinceReport="662" predictable="false" heading="315" speedKmHr="3.204"/>
</body>
6549 now shows data, it's at Landover
<vehicle id="6549" routeTag="C29" dirTag="C29_C29c_1" lat="38.886322" lon="-76.8964079" secsSinceReport="13" predictable="true" heading="165" speedKmHr="24.12"/>
also, 4085 could also be 2076, there's no data showing for that bus
now 2024 is at West Ox
<vehicle id="2024" routeTag="null" dirTag="null" lat="38.848236" lon="-77.378853" secsSinceReport="110" predictable="false" heading="-4" speedKmHr="0.0"/>
and 3003 at Landover
<vehicle id="3003" routeTag="U4" dirTag="null" lat="38.937832" lon="-76.8739779" secsSinceReport="2713" predictable="false" heading="-4" speedKmHr="0.0"/>
2199-2204 are at Montgomery.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2199" routeTag="null" dirTag="null" lat="39.046646" lon="-77.107986" secsSinceReport="6668" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2200" routeTag="C8" dirTag="C8_C8v2_0" lat="39.040211" lon="-76.990837" secsSinceReport="4" predictable="true" heading="150" speedKmHr="53.1"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2201" routeTag="T2" dirTag="T2_T2_1" lat="38.984058" lon="-77.138474" secsSinceReport="1" predictable="true" heading="131" speedKmHr="1.584"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2202" routeTag="null" dirTag="null" lat="39.029297" lon="-77.104279" secsSinceReport="143" predictable="false" heading="330" speedKmHr="54.684"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2203" routeTag="T2" dirTag="null" lat="39.046539" lon="-77.107597" secsSinceReport="321" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2204" routeTag="W4" dirTag="null" lat="39.046539" lon="-77.108513" secsSinceReport="14801" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And so are 6194-6196. Awesome.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6194" routeTag="null" dirTag="null" lat="39.046593" lon="-77.108192" secsSinceReport="52596" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6195" routeTag="Z2" dirTag="null" lat="39.148563" lon="-77.012016" secsSinceReport="20767" predictable="true" heading="150" speedKmHr="35.388"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6196" routeTag="Z6" dirTag="Z6_Z6_0" lat="38.994701" lon="-77.027061" secsSinceReport="77" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
EDIT: Now it's a changing of the rehabs; 2545 is back at Four Mile Run...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2545" routeTag="null" dirTag="null" lat="38.842075" lon="-77.053665" secsSinceReport="11020" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
...and 2610 is at Bladensburg (probably for a check-up).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2610" routeTag="null" dirTag="null" lat="38.921989" lon="-76.971344" secsSinceReport="10099" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And I forgot to mention this, but 5415 has no data.
sweet! I just hope they don't disable this last batch of Orion V knight riders like they did with the lower and mid 2100s
yeah a lot of buses still have been left without data after the GPS reset took place. 2008 is one of them as well.
6367-6370 are at Northern.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6367" routeTag="S2" dirTag="null" lat="38.947289" lon="-77.032387" secsSinceReport="974" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6368" routeTag="96" dirTag="96_96_1" lat="38.888439" lon="-76.986923" secsSinceReport="67" predictable="true" heading="285" speedKmHr="33.768"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6369" routeTag="90" dirTag="null" lat="38.946411" lon="-77.031685" secsSinceReport="25477" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6370" routeTag="90" dirTag="90_90_0" lat="38.862782" lon="-76.995705" secsSinceReport="246" predictable="true" heading="300" speedKmHr="32.184"/>
</body>
And 7067 has arrived at Annex.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7067" routeTag="null" dirTag="null" lat="38.872517" lon="-76.932564" secsSinceReport="1647" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And 2631 is finally back at FMR. It's about time...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2631" routeTag="null" dirTag="null" lat="38.844139" lon="-77.054123" secsSinceReport="991" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2652 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2652" routeTag="16G" dirTag="null" lat="38.923145" lon="-76.970398" secsSinceReport="19" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
7070 and 7074 are at Annex.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7070" routeTag="NH1" dirTag="NH1_NH1_1" lat="38.799534" lon="-77.000603" secsSinceReport="315" predictable="true" heading="300" speedKmHr="32.184"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7074" routeTag="null" dirTag="null" lat="38.872379" lon="-76.932564" secsSinceReport="1308" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2643 on the 5A... for whatever reason...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2643" routeTag="5A" dirTag="5A_5Av1_0" lat="38.953644" lon="-77.446747" secsSinceReport="29" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
2720 back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2720" routeTag="null" dirTag="null" lat="38.842926" lon="-77.053207" secsSinceReport="151" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6391 is at Northern.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6391" routeTag="K6" dirTag="null" lat="38.946548" lon="-77.031647" secsSinceReport="54" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6575 on the K6.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6575" routeTag="K6" dirTag="K6_K6_1" lat="39.004902" lon="-76.982056" secsSinceReport="15" predictable="true" heading="180" speedKmHr="20.916"/>
</body>
2665 at Bladensburg, I wonder what they'll do with this one
<vehicle id="2665" routeTag="null" dirTag="null" lat="38.923943" lon="-76.970222" secsSinceReport="40554" predictable="false" heading="-4" speedKmHr="0.0"/>
6391 is back at Montgomery
<vehicle id="6391" routeTag="null" dirTag="null" lat="39.046482" lon="-77.108437" secsSinceReport="2034" predictable="false" heading="-4" speedKmHr="0.0"/>
More Xcelsiors are arriving at Annex; some of them are finally appearing on local routes.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7068" routeTag="P19" dirTag="P19_P19_0" lat="38.8730959" lon="-76.9695969" secsSinceReport="141" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7075" routeTag="D12" dirTag="D12_D12v2_1" lat="38.840755" lon="-76.9759289" secsSinceReport="128" predictable="true" heading="47" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7076" routeTag="D14" dirTag="D14_D14_1" lat="38.841606" lon="-76.914543" secsSinceReport="88" predictable="true" heading="75" speedKmHr="27.324"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7077" routeTag="P17" dirTag="P17_P17_0" lat="38.900238" lon="-77.03389" secsSinceReport="48" predictable="true" heading="86" speedKmHr="0.0"/>
</body>
And the highest Local one, 7079, is at CET.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7079" routeTag="null" dirTag="null" lat="38.941376" lon="-76.878105" secsSinceReport="4851" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6191-6193 are at Montgomery.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6191" routeTag="null" dirTag="null" lat="39.0470309" lon="-77.1079479" secsSinceReport="12" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6192" routeTag="A8" dirTag="null" lat="39.046429" lon="-77.108337" secsSinceReport="17915" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6193" routeTag="Y9" dirTag="Y9_Y9_0" lat="39.040901" lon="-77.110046" secsSinceReport="123" predictable="true" heading="150" speedKmHr="61.128"/>
</body>
EDIT: So is 6189.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6189" routeTag="Q6" dirTag="Q6_Q6_1" lat="39.117706" lon="-77.16584" secsSinceReport="17" predictable="true" heading="90" speedKmHr="33.768"/>
</body>
Seven more Xcelsiors have arrived at Annex: 7071, 7073, 7078, 7079, 7084, 7085, and 7086.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7071" routeTag="null" dirTag="null" lat="38.872131" lon="-76.932671" secsSinceReport="13624" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7073" routeTag="M6" dirTag="M6_M6_0" lat="38.880573" lon="-76.985344" secsSinceReport="126" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7078" routeTag="C12" dirTag="C12_C12_0" lat="38.847492" lon="-76.951363" secsSinceReport="41" predictable="true" heading="60" speedKmHr="32.184"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7079" routeTag="P17" dirTag="P17_P17_0" lat="38.899441" lon="-77.039528" secsSinceReport="26" predictable="true" heading="360" speedKmHr="17.676"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7084" routeTag="C8" dirTag="C8_C8v2_0" lat="38.873066" lon="-76.932632" secsSinceReport="16743" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7085" routeTag="null" dirTag="null" lat="38.872189" lon="-76.932739" secsSinceReport="13430" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7086" routeTag="34" dirTag="34_34_1" lat="38.8876149" lon="-77.021606" secsSinceReport="1" predictable="true" heading="270" speedKmHr="16.092"/>
</body>
And George, it looks like you were right about 4085:
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4085" routeTag="null" dirTag="null" lat="39.045986" lon="-77.107285" secsSinceReport="758760" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2076" routeTag="null" dirTag="null" lat="39.0453" lon="-77.107918" secsSinceReport="110697" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And I forgot to mention this, but 6327 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6327" routeTag="null" dirTag="null" lat="38.922016" lon="-76.971031" secsSinceReport="2098306" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
2624 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2624" routeTag="null" dirTag="null" lat="38.844414" lon="-77.054016" secsSinceReport="9539" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2656 takes its place at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2656" routeTag="null" dirTag="null" lat="38.923393" lon="-76.970467" secsSinceReport="24364" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2517 is also at Bladensburg (probably not for long, though).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2517" routeTag="16H" dirTag="null" lat="38.920807" lon="-76.970016" secsSinceReport="765975" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6190 at Montgomery.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6190" routeTag="M6" dirTag="null" lat="39.046677" lon="-77.1086119" secsSinceReport="13773" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2446 is showing no data.
please tell me it's coming to revenue service soon
<vehicle id="2463" routeTag="B99" dirTag="B99_B99_1" lat="38.922512" lon="-76.969315" secsSinceReport="993" predictable="true" heading="213" speedKmHr="0.0"/>
2726 is back online, now showing it's at that truck place in Landover
<vehicle id="2726" routeTag="null" dirTag="null" lat="38.942009" lon="-76.858261" secsSinceReport="22022" predictable="false" heading="-4" speedKmHr="0.0"/>
and no data showing for 2667, 2671, 2715, 6002, 6006, 6048, and 6137
Here's a list of Xcelsiors that are not online yet, in order of division:
Bladensburg: 7001 (how ironic), 7023, 7027, 7029
Montgomery: 7034, 7040, 7044, 7050, 7051, 7059
Annex: 7063, 7066, 7069, 7080-83, 7087-90
And in response to the October obs. thread, 5309 is back at Northern.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5309" routeTag="null" dirTag="null" lat="38.946381" lon="-77.03228" secsSinceReport="2639" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2503 is at... an unnamed warehouse, or lot, or whatever, in Elkridge, MD.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2503" routeTag="null" dirTag="null" lat="39.182003" lon="-76.763023" secsSinceReport="18962" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2719 back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2719" routeTag="null" dirTag="null" lat="38.844055" lon="-77.053421" secsSinceReport="27" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2549 replaces it at Bladensburg (must've happened this afternoon; I saw it on the Red Line shuttle this morning).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2549" routeTag="null" dirTag="null" lat="38.922596" lon="-76.969559" secsSinceReport="23157" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And finally, 2463 is BACK IN SERVICE! Four down, one to go!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2463" routeTag="H4" dirTag="H4_H4_1" lat="38.928646" lon="-77.027657" secsSinceReport="36" predictable="true" heading="83" speedKmHr="0.0"/>
</body>
EDIT: 2549 back at Four Mile Run. I guess it was just a layover, or whatever...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2549" routeTag="null" dirTag="null" lat="38.8416629" lon="-77.053841" secsSinceReport="1909" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
i'm so glad 2463 is back, can't wait to see it sometime next week
also, 2549 might have been at Bladensburg for refueling
looks like 2639 will be replacing 2719 at Bladensburg instead
<vehicle id="2639" routeTag="16G" dirTag="null" lat="38.923336" lon="-76.970467" secsSinceReport="34080" predictable="false" heading="-4" speedKmHr="0.0"/>
2621 last shown around the 14th Street bridge, on the way home to FMR perhaps?
<vehicle id="2621" routeTag="null" dirTag="null" lat="38.881374" lon="-77.029968" secsSinceReport="42291" predictable="false" heading="225" speedKmHr="74.016"/>
3924 at Western? This bus just can't seem to sit still, can it?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3924" routeTag="null" dirTag="null" lat="38.9583439" lon="-77.085167" secsSinceReport="62565" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
looks like I was right then, 2621 was going home to FMR, now it's there
<vehicle id="2621" routeTag="null" dirTag="null" lat="38.843201" lon="-77.054298" secsSinceReport="14047" predictable="false" heading="-4" speedKmHr="0.0"/>
now with 2638 and 2639 in rehab, the lowest Pike Ride bus will be 2640 (saw this one in service earlier today)
6347 and 6348 are at West Ox.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6347" routeTag="1B" dirTag="1B_1B_0" lat="38.881344" lon="-77.111557" secsSinceReport="16" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6348" routeTag="15M" dirTag="15M_15M_1" lat="38.859566" lon="-77.359566" secsSinceReport="642" predictable="true" heading="75" speedKmHr="78.84"/>
</body>
3016 back in service, i assume it's rehabbed because of how long it's been out of service
<vehicle id="3016" routeTag="D4" dirTag="D4_D4_1" lat="38.901363" lon="-77.030113" secsSinceReport="351" predictable="true" heading="270" speedKmHr="0.0"/>
EDIT - and 2503 is back at FMR
<vehicle id="2503" routeTag="null" dirTag="null" lat="38.844578" lon="-77.0539469" secsSinceReport="7767" predictable="false" heading="-4" speedKmHr="0.0"/>
judging by the seconds count, 3012 might be in the process of rehab
<vehicle id="3012" routeTag="null" dirTag="null" lat="38.923061" lon="-76.969109" secsSinceReport="382271" predictable="false" heading="-4" speedKmHr="0.0"/>
6137's GPS finally updated; it's at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6137" routeTag="null" dirTag="null" lat="38.9223209" lon="-76.971313" secsSinceReport="284274" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Speaking of which, 6012 is still there after almost two months, and 6151 is also still there, with a timeout of over 3 million seconds. And now, 6013 is there as well.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6013" routeTag="null" dirTag="null" lat="38.922153" lon="-76.971413" secsSinceReport="289674" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
Could the diesels and hybrids possibly be starting rehab?
2566 on the 5A.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2566" routeTag="5A" dirTag="5A_5A_1" lat="38.951633" lon="-77.383858" secsSinceReport="1" predictable="true" heading="330" speedKmHr="22.5"/>
</body>
I didn't report it, but yesterday, I saw 2530, with no route designation, at Herndon-Monroe, then at Dulles a few moments later. Without those luggage racks, this is just asking for trouble.
EDIT: And a REX bus on a non-REX route?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2679" routeTag="23A" dirTag="23A_23A_1" lat="38.8421019" lon="-77.086845" secsSinceReport="39" predictable="true" heading="150" speedKmHr="19.296"/>
</body>
6190 BACK at Annex? I don't like where this is going
<vehicle id="6190" routeTag="null" dirTag="null" lat="38.872406" lon="-76.933128" secsSinceReport="113054" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on November 13, 2011, 09:43:45 AM
6190 BACK at Annex? I don't like where this is going
<vehicle id="6190" routeTag="null" dirTag="null" lat="38.872406" lon="-76.933128" secsSinceReport="113054" predictable="false" heading="-4" speedKmHr="0.0"/>
If it's any consolation, I don't think it was at Montgomery for very long. In fact, I don't think it had operated any routes before it went back to Annex. And on a related note, 6158 is also at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6158" routeTag="null" dirTag="null" lat="38.920971" lon="-76.970222" secsSinceReport="249656" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Here's the status of all the Xcelsiors I brought up in a previous post:
At CET: 7001, 7050, 7063, 7066, 7080, 7083, 7087, 7089
In service: 7023, 7027, 7051, 7081, 7082, 7088
Still not online yet: 7029, 7034, 7040, 7044, 7059, 7069, 7090
2703 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2703" routeTag="null" dirTag="null" lat="38.922348" lon="-76.971558" secsSinceReport="5044" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Is it just me or does it seem like they've been rehabbing a lot of 26-2700s recently? Guess they want to get the repowers over with ASAP...
Good news, everyone! 6190 is back at Montgomery! Again!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6190" routeTag="Z2" dirTag="Z2_Z2vS_0" lat="39.052231" lon="-77.075851" secsSinceReport="70" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
And it brought friends!
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6186" routeTag="Z8" dirTag="Z8_Z8v9_1" lat="39.077339" lon="-76.942436" secsSinceReport="20" predictable="true" heading="248" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6187" routeTag="L8" dirTag="L8_L8_0" lat="38.961452" lon="-77.086037" secsSinceReport="40" predictable="true" heading="347" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6188" routeTag="J9" dirTag="null" lat="38.983974" lon="-77.097313" secsSinceReport="2" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And the only two Xcelsiors still not online yet are 7044 and 7059. The rest are either at CET or in service.
And 2076 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2076" routeTag="Z8" dirTag="null" lat="38.921989" lon="-76.971313" secsSinceReport="526460" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3027 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3027" routeTag="3T" dirTag="null" lat="38.843231" lon="-77.053207" secsSinceReport="2501" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2632 replaces it at Bladensburg. (another 2600... yawn)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2632" routeTag="7Y" dirTag="null" lat="38.922844" lon="-76.971169" secsSinceReport="63589" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
those 6180s and 6190 moving to Montgomery put a smile on my face. apparently, Nextbus did that GPS reset thing again and plenty of buses such as 2587, 2665, 2462, 3025, etc are not showing any data. I hate when that happens to be honest. Speaking of 3025, that went to Bladensburg before 3027, and at some point ended up in some remote place near Chantilly, then back at Bladensburg, I'm guessing that one is rehab 1533, guess we'll find out someday.
Also, I made a list predicting what the future rehab numbers will be for the currently unrehabbed (and in-progess rehab) buses, 2632 was the very last one in my list, looks like I got that wrong (2501 was way up there too)
2504 at Bladensburg for some reason
<vehicle id="2504" routeTag="null" dirTag="null" lat="38.921825" lon="-76.971207" secsSinceReport="6906" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on November 18, 2011, 04:22:37 PM
2504 at Bladensburg for some reason
<vehicle id="2504" routeTag="null" dirTag="null" lat="38.921825" lon="-76.971207" secsSinceReport="6906" predictable="false" heading="-4" speedKmHr="0.0"/>
Yeah, it's been there for at least two weeks now, along with 2517. In regards to that future rehab list you mentioned, I've always felt that the last two would be 2537 and 2648. (just watch, now that I've said this, they'll be the next ones at Bladensburg)
In other news, 7063 is at... Montgomery? Okay then...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7063" routeTag="Z8" dirTag="Z8_Z8v2_1" lat="39.019066" lon="-77.0140459" secsSinceReport="147" predictable="true" heading="210" speedKmHr="35.388"/>
</body>
looks like 3924 is back at Western (I do remember way back in the day seeing this bus on a Western route, not sure how long it's been away from Western but now it's back)
<vehicle id="3924" routeTag="E6" dirTag="null" lat="38.959389" lon="-77.087547" secsSinceReport="5099" predictable="false" heading="210" speedKmHr="28.943999999999996"/>
6151 is back at Annex. Maybe it's rehabbed, and maybe not.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6151" routeTag="null" dirTag="null" lat="38.873013" lon="-76.931862" secsSinceReport="1876" predictable="false" heading="195" speedKmHr="27.324"/>
</body>
2547 is back at FMR...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2547" routeTag="null" dirTag="null" lat="38.843643" lon="-77.054016" secsSinceReport="9" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
...with 2567 replacing it at Bladensburg...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2567" routeTag="23C" dirTag="null" lat="38.922871" lon="-76.9711" secsSinceReport="4819" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
...and 2514 leaving Herndon-Monroe, most likely on an unmarked 5A run.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2514" routeTag="null" dirTag="null" lat="38.952736" lon="-77.38382" secsSinceReport="59" predictable="false" heading="360" speedKmHr="37.008"/>
</body>
2669 is back at FMR as well.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2669" routeTag="null" dirTag="null" lat="38.843063" lon="-77.052261" secsSinceReport="100" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And its replacement at B-burg is 2508.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2508" routeTag="9S" dirTag="null" lat="38.92342" lon="-76.970436" secsSinceReport="3110" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Two rehabs returning in one day? I haven't seen that happen since 2593 and 2517 returned to Four Mile Run together a couple months back (btw, the latter is back at Bladensburg).
At any rate, the returning bus is 3025 (maybe this is the missing 1533).
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3025" routeTag="null" dirTag="null" lat="38.843063" lon="-77.053284" secsSinceReport="136" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2702 has taken its place in line for rehab.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2702" routeTag="16A" dirTag="null" lat="38.923943" lon="-76.970123" secsSinceReport="4414" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
damn man you beat me to all that, i was just gonna post 3025 returning to FMR. I checked literally a couple of hours ago and it was still at Bladensburg. yeah I also have the feeling that 3025 is 1533, but you never know
also, it seems like all the buses serve routes right before going to rehab. on the routeTag for the new rehabs, they always seem to show route numbers (example: 16A on 2702, 9S on 2508, 23C on 2567, and back when it first went to rehab, 2501 had 15K (or 17K, one of those))
5422 is on the 87 right now. That's like a once in a lifetime photo op
<body copyright="All data copyright WMATA Washington 2011."><vehicle id="5422" routeTag="87" dirTag="87_87_0" lat="39.078053" lon="-76.848076" secsSinceReport="17" predictable="true" heading="90" speedKmHr="12.852"/></body>
And 5418 is on the B30
<body copyright="All data copyright WMATA Washington 2011."><vehicle id="5418" routeTag="B30" dirTag="B30_B30_0" lat="39.189289" lon="-76.676643" secsSinceReport="73" predictable="true" heading="180" speedKmHr="3.204"/></body>
6331 on the U8.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6331" routeTag="U8" dirTag="U8_U8_0" lat="38.899303" lon="-76.946007" secsSinceReport="55" predictable="true" heading="225" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on November 23, 2011, 09:01:38 AM
6331 on the U8.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6331" routeTag="U8" dirTag="U8_U8_0" lat="38.899303" lon="-76.946007" secsSinceReport="55" predictable="true" heading="225" speedKmHr="0.0"/>
</body>
Hmm. Really odd one there. Must be some Landover/Bburg swap since a couple of the tics are on the B30 and probably some buses had went to the X2 to cover those tic runs.
7115 and 7116 online
<vehicle id="7115" routeTag="null" dirTag="null" lat="38.94091" lon="-76.8787" secsSinceReport="25476" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7116" routeTag="null" dirTag="null" lat="38.940964" lon="-76.8787" secsSinceReport="25478" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: RideOn5905 on November 23, 2011, 09:01:38 AM
6331 on the U8.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6331" routeTag="U8" dirTag="U8_U8_0" lat="38.899303" lon="-76.946007" secsSinceReport="55" predictable="true" heading="225" speedKmHr="0.0"/>
</body>
I saw that bus on the B2 about an hour ago. Block BB24. It was only going to Bladensburg and V St.
4340 is back online and at Montgomery, looks like it's not retired yet (hopefully)
<vehicle id="4340" routeTag="null" dirTag="null" lat="39.046124" lon="-77.107147" secsSinceReport="50904" predictable="false" heading="-4" speedKmHr="0.0"/>
3908 is at Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3908" routeTag="F12" dirTag="F12_F12_1" lat="38.936428" lon="-76.877403" secsSinceReport="191" predictable="true" heading="225" speedKmHr="33.768"/>
</body>
3021 is back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3021" routeTag="null" dirTag="null" lat="38.844414" lon="-77.053978" secsSinceReport="6147" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2664 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2664" routeTag="null" dirTag="null" lat="38.923393" lon="-76.970467" secsSinceReport="15345" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
5404 is also at Landover; most likely for the extra B30 service.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5404" routeTag="null" dirTag="null" lat="38.936893" lon="-76.874535" secsSinceReport="16" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6171 on the 97
- (http://www.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=1000751#) <predictions agencyTitle="
WMATA Washington" routeTitle="
97 EAST CAP-CARDOZO" routeTag="
97" stopTitle="
Stadium Armory Station + Bus Bay C" stopTag="
4967">
- (http://www.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=1000751#) <direction title="
West to Union Station">
<prediction epochTime="
1322254633273" seconds="
1774" minutes="
29" isDeparture="
false" affectedByLayover="
true" dirTag="
97_97_1" vehicle="
6171" block="
NJ01"
6331 is still at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011."><vehicle id="6331" routeTag="null" dirTag="null" lat="38.922924" lon="-76.969177" secsSinceReport="122" predictable="false" heading="-4" speedKmHr="0.0"/></body>
Is it possible that Landover and Bladensburg swapped buses? Two buses at Landover from Bladensburg (5418 and 5422), and two buses from Landover at Bladensburg (6331 and another one yet to be seen)? Just for the Thanksgiving holiday.
6137 is in Langdon Park, like, LITERALLY inside the park, next to the swimming pool.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6137" routeTag="null" dirTag="null" lat="38.926582" lon="-76.973518" secsSinceReport="8998" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And it seems we've had another GPS reset; more buses have gone offline, particularly the Orion VIIs that are at Bladensburg for rehab.
EDIT: Uhhh.................... WTF?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7777" routeTag="D33" dirTag="null" lat="38.939068" lon="-76.878349" secsSinceReport="90" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3022 back at FMR
<vehicle id="3022" routeTag="null" dirTag="null" lat="38.842846" lon="-77.052513" secsSinceReport="7383" predictable="false" heading="-4" speedKmHr="0.0"/>
2570 takes its place
<vehicle id="2570" routeTag="null" dirTag="null" lat="38.92342" lon="-76.970467" secsSinceReport="13859" predictable="false" heading="-4" speedKmHr="0.0"/>
5422 on the 87
<vehicle id="5422" routeTag="87" dirTag="87_87_0" lat="39.074257" lon="-76.8479" secsSinceReport="43" predictable="true" heading="330" speedKmHr="12.852"/>
and 2671 has been offline for a long time, I have a feeling it may be getting rehabbed as well
2638 is heading northbound on I-395 in D.C., I saw it leaving the D.C. DMV inspection station, so it should be back at Four Mile Run shortly.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2638" routeTag="null" dirTag="null" lat="38.895397" lon="-77.0140459" secsSinceReport="21" predictable="false" heading="345" speedKmHr="48.276"/>
</body>
6331 and 5404 are both back where they belong.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6331" routeTag="A12" dirTag="A12_A12_1" lat="38.918442" lon="-76.869217" secsSinceReport="201" predictable="true" heading="75" speedKmHr="33.768"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5404" routeTag="null" dirTag="null" lat="38.923889" lon="-76.9701539" secsSinceReport="22653" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2638 is... BACK at the DMV inspection station?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2638" routeTag="null" dirTag="null" lat="38.877743" lon="-77.011597" secsSinceReport="45" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
There is something missing here. Can you guess what it is?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6202" lat="39.037407" lon="-77.051323" secsSinceReport="134" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on December 01, 2011, 12:02:50 PM
There is something missing here. Can you guess what it is?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6202" lat="39.037407" lon="-77.051323" secsSinceReport="134" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I noticed this too this morning. the routeTag and dirTag is missing, this seems to be the case for the buses that are not in service. when it comes into service, those tags appear again
BTW saw 4340 in service today on the C4, glad to see it hasn't retired
6006 is at Bladensburg; I have a feeling 6002 and 6048 will follow suit before too long.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6006" lat="38.922401" lon="-76.970924" secsSinceReport="23712" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
As a side note regarding the Orion VIIs: There are 250 of them. I did a head count; the first one to be rehabbed was 2582, which has a rehab # of 1437. The latest one to be rehabbed is 3022, which will (most likely) be #1543. That is a total of 107 rehab numbers, but three of them are Neoplans, so that means 104 Orion VIIs have completed rehab, with 23 more in the process of it, for a total of 127, which is a little more than half the grand total. Bladensburg's newest arrivals (the likes of 2702 and 2570) will probably be done with rehab around mid-late February. This coming week will mark the one-year anniversary of 2582's return. Assuming Metro will only be rehabbing the Orions for the time being, they should all be done by May 2013.
Quote from: RideOn5905 on December 01, 2011, 08:00:15 PM
6006 is at Bladensburg; I have a feeling 6002 and 6048 will follow suit before too long.
I was at Bladensburg this morning and saw 6012 getting work done on it and 6013 was parked in the lot.
7115 At Bladensburg <body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7115" lat="38.9224279" lon="-76.971626" secsSinceReport="4970" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I just noticed something: Yesterday, the routeTag and dirTag had disappeared on all buses that were not in service. Later that day, the NextBus map on Metro's website stopped working for me. Has it stopped working for anyone else? I have reason to believe that these two events are related in some way.
6191 is at Landover. I saw it operating the Red Line shuttle today, so this is most likely either a fuel up or an overnight stay. Or possibly both.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6191" lat="38.936096" lon="-76.8748169" secsSinceReport="5571" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on December 02, 2011, 04:26:54 PM
I just noticed something: Yesterday, the routeTag and dirTag had disappeared on all buses that were not in service. Later that day, the NextBus map on Metro's website stopped working for me. Has it stopped working for anyone else? I have reason to believe that these two events are related in some way.
It's some recent change that's on Nextbus's end. UMD's map that they have on the monitor stopped working because of the changes. If you go to the test site, the buses will show up. Maybe they'll correct this in the future.
Quote from: 79MetroExtraMD on December 04, 2011, 03:01:11 AM
Quote from: RideOn5905 on December 02, 2011, 04:26:54 PM
I just noticed something: Yesterday, the routeTag and dirTag had disappeared on all buses that were not in service. Later that day, the NextBus map on Metro's website stopped working for me. Has it stopped working for anyone else? I have reason to believe that these two events are related in some way.
It's some recent change that's on Nextbus's end. UMD's map that they have on the monitor stopped working because of the changes. If you go to the test site, the buses will show up. Maybe they'll correct this in the future.
I checked on it just now. The map is indeed back up, and it also shows other places, like restaurants, shops, and the like. A nice touch, I must say.
Quote from: RideOn5905 on December 04, 2011, 11:11:47 AM
Quote from: 79MetroExtraMD on December 04, 2011, 03:01:11 AM
Quote from: RideOn5905 on December 02, 2011, 04:26:54 PM
I just noticed something: Yesterday, the routeTag and dirTag had disappeared on all buses that were not in service. Later that day, the NextBus map on Metro's website stopped working for me. Has it stopped working for anyone else? I have reason to believe that these two events are related in some way.
It's some recent change that's on Nextbus's end. UMD's map that they have on the monitor stopped working because of the changes. If you go to the test site, the buses will show up. Maybe they'll correct this in the future.
I checked on it just now. The map is indeed back up, and it also shows other places, like restaurants, shops, and the like. A nice touch, I must say.
Still not working for me...
7061, 7062, and 6185 are at Montgomery.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7061" routeTag="K6" dirTag="K6_K6_1" lat="38.960323" lon="-77.006592" secsSinceReport="47" predictable="true" heading="195" speedKmHr="57.924"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7062" routeTag="C4" dirTag="C4_C4_0" lat="39.05608" lon="-77.107567" secsSinceReport="110" predictable="true" heading="320" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6185" routeTag="D14" lat="39.046867" lon="-77.108475" secsSinceReport="18217" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And the same thing might also be true for 6183 and 6184.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6183" lat="38.8450429" lon="-76.988144" secsSinceReport="303839" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6184" routeTag="W4" lat="38.862728" lon="-76.996124" secsSinceReport="660391" predictable="true" heading="240" speedKmHr="16.092"/>
</body>
And 5415 is back in service.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5415" routeTag="X2" dirTag="X2_X2_1" lat="38.901337" lon="-77.029762" secsSinceReport="201" predictable="true" heading="270" speedKmHr="19.296"/>
</body>
Woahh <body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7001" routeTag="W4" dirTag="W4_W4v1_1" lat="38.908211" lon="-76.9345249" secsSinceReport="298" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
2513 and 2638 back at FMR
<vehicle id="2513" lat="38.843586" lon="-77.053207" secsSinceReport="59" predictable="false" heading="90" speedKmHr="12.852"/>
<vehicle id="2638" lat="38.842873" lon="-77.052963" secsSinceReport="2026" predictable="false" heading="-4" speedKmHr="0.0"/>
nothing seems to have taken their places yet, but after rush hour this evening there will most likely be.
in the meantime, I found (via nextbus of course) 3024 at Landover
<vehicle id="3024" routeTag="9A" lat="38.937336" lon="-76.873871" secsSinceReport="6425" predictable="false" heading="-4" speedKmHr="0.0"/>
Also in the meantime, 6013 has returned to Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6013" lat="38.9356579" lon="-76.874992" secsSinceReport="14341" predictable="false" heading="60" speedKmHr="3.204"/>
</body>
As has 3024 to FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3024" routeTag="29H" dirTag="29H_29H_0" lat="38.824421" lon="-77.201363" secsSinceReport="1" predictable="true" heading="195" speedKmHr="45.036"/>
</body>
It's kinda strange... 2513 and 2638 are back, yet 2587 and 2711 have been at Bladensburg longer than them, and neither of those two buses is showing data at the moment.
well since 2587 and 2711 haven't been showing data, you never know, they might be back as well. as of right now, there still hasn't been any other buses going to Bladensburg, however I've got my eye on 2600 since the seconds count is pretty high.
<vehicle id="2600" lat="38.842075" lon="-77.054436" secsSinceReport="495181" predictable="false" heading="-4" speedKmHr="0.0"/>
speaking of not showing data, 2656, 2715, and 3032 are back online, at Bladensburg of course. along with 2587 and 2711; 2008, 2456, 2462, 2567, 2632, 2639, 2652, 2665, 2671, 2681, 2703, 2709, 2723, 2724, 2726, 3012, 4208, 5301, 5305, 5306, 5308, 6002, 6040, and 6048 are not showing data
also, don't quote me on this, but 3003 hasn't been in service for days, and even though the seconds count isn't that high, I think it might be going to rehab. again, don't take my word for it.
and finally, 2001 and 6137 at Bladensburg
<vehicle id="2001" lat="38.922047" lon="-76.971237" secsSinceReport="701699" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6137" lat="38.922623" lon="-76.971413" secsSinceReport="25750" predictable="false" heading="-4" speedKmHr="0.0"/>
EDIT - This just in, 5320 is finally back online! It shows that it's at Bladensburg, so it's quite possible it's been getting rehabbed
<vehicle id="5320" lat="38.922291" lon="-76.971588" secsSinceReport="24860" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on December 07, 2011, 04:54:54 PM
well since 2587 and 2711 haven't been showing data, you never know, they might be back as well. as of right now, there still hasn't been any other buses going to Bladensburg, however I've got my eye on 2600 since the seconds count is pretty high.
<vehicle id="2600" lat="38.842075" lon="-77.054436" secsSinceReport="495181" predictable="false" heading="-4" speedKmHr="0.0"/>
speaking of not showing data, 2656, 2715, and 3032 are back online, at Bladensburg of course. along with 2587 and 2711; 2008, 2456, 2462, 2567, 2632, 2639, 2652, 2665, 2671, 2681, 2703, 2709, 2723, 2724, 2726, 3012, 4208, 5301, 5305, 5306, 5308, 6002, 6040, and 6048 are not showing data
also, don't quote me on this, but 3003 hasn't been in service for days, and even though the seconds count isn't that high, I think it might be going to rehab. again, don't take my word for it.
and finally, 2001 and 6137 at Bladensburg
<vehicle id="2001" lat="38.922047" lon="-76.971237" secsSinceReport="701699" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6137" lat="38.922623" lon="-76.971413" secsSinceReport="25750" predictable="false" heading="-4" speedKmHr="0.0"/>
EDIT - This just in, 5320 is finally back online! It shows that it's at Bladensburg, so it's quite possible it's been getting rehabbed
<vehicle id="5320" lat="38.922291" lon="-76.971588" secsSinceReport="24860" predictable="false" heading="-4" speedKmHr="0.0"/>
We should probably be keeping an eye on 2706 as well, its seconds count is even higher than 2600's.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2706" lat="38.843918" lon="-77.053772" secsSinceReport="678606" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And I forgot to mention this, but 6547 is at Johnson Truck Center in Landover.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6547" lat="38.942036" lon="-76.858711" secsSinceReport="4324" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 6107, it is after midnight. What in God's name are you doing on a Bladensburg route?
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6107" routeTag="D4" dirTag="D4_D4_1" lat="38.901283" lon="-77.030144" secsSinceReport="207" predictable="true" heading="270" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: (4/16/12) Guess what? 2706
was at Bladensburg the whole time. It must've had a dead GPS during its stay. This and 3015 were the real replacements for 2513 and 2638.
6345 is on stroll, in Lombard St In Baltimore!, Well before it was on the move, it was sitting there.
<vehicle id="6345" lat="39.265491" lon="-76.668175" secsSinceReport="84" predictable="false" heading="240" speedKmHr="96.552"/>
6107 on the 90.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6107" routeTag="90" dirTag="90_90_0" lat="38.881016" lon="-76.995003" secsSinceReport="38" predictable="true" heading="360" speedKmHr="16.092"/>
</body>
6183 back at Montgomery as well. They just keep on coming!
<vehicle id="6183" routeTag="Y8" dirTag="Y8_Y8_0" lat="38.993736" lon="-77.026817" secsSinceReport="164" predictable="true" heading="165" speedKmHr="14.471999999999998"/>
6184's GPS hasn't been updated in a while, it may be at Montgomery as well
<vehicle id="6184" routeTag="W4" lat="38.862728" lon="-76.996124" secsSinceReport="1124233" predictable="true" heading="240" speedKmHr="16.092"/>
and after all that, 6107 is back at Annex
<vehicle id="6107" routeTag="92" lat="38.872105" lon="-76.933372" secsSinceReport="48836" predictable="false" heading="-4" speedKmHr="0.0"/>
7030 and 7031 now at Bladensburg
<vehicle id="7030" routeTag="D4" dirTag="D4_D4_1" lat="38.901337" lon="-77.030212" secsSinceReport="156" predictable="true" heading="270" speedKmHr="0.0"/>
<vehicle id="7031" routeTag="D8" dirTag="D8_D8_0" lat="38.924107" lon="-76.99826" secsSinceReport="24" predictable="true" heading="243" speedKmHr="0.0"/>
7105, 7118, and 7128 are now online
<vehicle id="7105" lat="38.941132" lon="-76.878242" secsSinceReport="191344" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7118" lat="38.941101" lon="-76.878418" secsSinceReport="123813" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7128" lat="38.941101" lon="-76.878349" secsSinceReport="123987" predictable="false" heading="-4" speedKmHr="0.0"/>
I've compiled a list of all the 42-43-4400s (besides 4200-4207, which are already gone) that are either offline or at CET:
Landover: 4208, 4250, 4375, 4376, 4380, 4381, 4390, 4393, 4394
West Ox: 4214, 4219, 4236, 4363, 4365
Annex: 4246, 4247, 4248, 4388, 4389, 4396, 4398
Northern: 4278, 4287, 4295, 4296, 4299, 4303
Montgomery: 4310, 4313, 4319, 4320, 4323, 4326, 4330, 4332, 4335, 4341, 4351, 4353
And 4293 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4293" lat="38.922237" lon="-76.96907" secsSinceReport="68500" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4393 is back online; looks like it's not retired... yet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4393" lat="38.937168" lon="-76.874428" secsSinceReport="1696" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6307 is also back online; at Bladensburg, natch.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6307" lat="38.921768" lon="-76.970398" secsSinceReport="31299" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
2639, 2652, 2709, and 2723 are all back online. Three guesses where, and the first two don't count.
2587 is back online; it's still at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2587" lat="38.922264" lon="-76.971207" secsSinceReport="2105" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on December 10, 2011, 07:55:39 PM
I've compiled a list of all the 42-43-4400s (besides 4200-4207, which are already gone) that are either offline or at CET:
Landover: 4208, 4250, 4375, 4376, 4380, 4381, 4390, 4393, 4394
West Ox: 4214, 4219, 4236, 4363, 4365
Annex: 4246, 4247, 4248, 4388, 4389, 4396, 4398
Northern: 4278, 4287, 4295, 4296, 4299, 4303
Montgomery: 4310, 4313, 4319, 4320, 4323, 4326, 4330, 4332, 4335, 4341, 4351, 4353
And 4293 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4293" lat="38.922237" lon="-76.96907" secsSinceReport="68500" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I don't like the looks of this...I hope my 4309 and 4317 are doing alright
Quote from: RideOn5905 on December 14, 2011, 10:05:07 AM
2587 is back online; it's still at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2587" lat="38.922264" lon="-76.971207" secsSinceReport="2105" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
of course it is...looks like we got another 2593 here...
2726 and 6048 are back online. 2726 is still at Johnson Truck Center.
<vehicle id="2726" lat="38.942368" lon="-76.858154" secsSinceReport="26751" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6048" lat="38.937115" lon="-76.874992" secsSinceReport="14084" predictable="false" heading="-4" speedKmHr="0.0"/>
4309, unfortunately, has a timeout of over a million seconds. 4317, on the other hand, is on the Q4 right now.
And 6158 is back at Annex.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6158" routeTag="W4" lat="38.872326" lon="-76.932602" secsSinceReport="9627" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6012 is back at Landover. Finally...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6012" lat="38.936234" lon="-76.874992" secsSinceReport="148493" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Nextbus did that restart thing again, great...
since then, a large chunk of 42-4400s have been offline, including ALL of Annex's and West Ox's 42-4300s
Here's a list of what's missing data: (for all 42-4400s)
4200-4232
4236-4238
4243-4248
4250, 4251
4262, 4265, 4266, 4269, 4278, 4282, 4285, 4287, 4295, 4296, 4297, 4299, 4303
4307 (obv), 4309, 4310, 4313, 4314, 4319, 4320, 4323, 4326, 4330, 4332, 4335, 4336, 4339, 4341, 4347, 4351, 4353, 4355
4358, 4360-4366
4375, 4376, 4380, 4381, 4388, 4389, 4390, 4394, 4396, 4397, 4398, 4411
while I searched those 42-4400s up, I found 4276 and 4298 at Western:
<vehicle id="4276" lat="38.958015" lon="-77.085373" secsSinceReport="19318" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4298" lat="38.9579049" lon="-77.0853039" secsSinceReport="36949" predictable="false" heading="-4" speedKmHr="0.0"/>
I hope most of those buses go back online tomorrow
EDIT - ALL of West Ox's Orion VIs are offline as well, don't tell me those are retiring as well... (they are 2024-2032, 2052-2063, 2065-2072)
also, despite being offline for a while before the Nextbus restart, 2446 and 2456 are back online right now
<vehicle id="2446" routeTag="H4" lat="38.921413" lon="-76.969734" secsSinceReport="1265" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2456" routeTag="G8" dirTag="G8_G8_1" lat="38.911541" lon="-77.024055" secsSinceReport="52" predictable="true" heading="165" speedKmHr="27.324"/>
Regarding the West Ox buses, they're probably all offline b/c West Ox is closed on weekends. They should be back on come tomorrow. Besides, the Orions make up the bulk of W.O.'s fleet, I doubt they're getting canned all at once.
3028 is at Gordon Boulevard and Horner Road in Woodbridge, Virginia.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3028" routeTag="9A" lat="38.663601" lon="-77.249557" secsSinceReport="66" predictable="false" heading="120" speedKmHr="6.408"/>
</body>
2667 is at Davidsonville Park and Ride; it should be back at FMR shortly.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2667" lat="38.959198" lon="-76.651093" secsSinceReport="138" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Look What i Found at Western
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7105" lat="38.9582369" lon="-77.0851969" secsSinceReport="24115" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="7115" lat="38.957989" lon="-77.085373" secsSinceReport="20239" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2711 is back online; still at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2711" lat="38.922981" lon="-76.9708859" secsSinceReport="302" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2587 and 2667 are both back at FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2587" lat="38.844276" lon="-77.054047" secsSinceReport="4329" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2667" lat="38.844193" lon="-77.054085" secsSinceReport="4181" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2601 and 2726 replace them at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2601" lat="38.923447" lon="-76.970467" secsSinceReport="1311" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2726" lat="38.923229" lon="-76.970398" secsSinceReport="330" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4287 on the 36; looks like this one's not retired yet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4287" routeTag="36" dirTag="36_36_1" lat="38.882858" lon="-76.992065" secsSinceReport="96" predictable="true" heading="105" speedKmHr="12.852"/>
</body>
And 6012 is BACK at Bladensburg... this one's up for interpretation...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6012" routeTag="T18" lat="38.921082" lon="-76.970398" secsSinceReport="17007" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And speaking of which, among Landover's DE40LFs, 6002, 6005, 6006, 6008, 6013, and 6014 are all offline right now (6006 was last shown at Bladensburg). Montgomery, meanwhile, only has one; 6033, as well as three D40LFRs: 6198, 6200, and 6204. From my observations, 6200 and 6204 have been out of service for about the same time (about 2 months, I'd say), I just hope they're okay; 6200 is my favorite bus...
Quote from: RideOn5905 on December 21, 2011, 04:28:34 PM
4287 on the 36; looks like this one's not retired yet.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="4287" routeTag="36" dirTag="36_36_1" lat="38.882858" lon="-76.992065" secsSinceReport="96" predictable="true" heading="105" speedKmHr="12.852"/>
</body>
And 6012 is BACK at Bladensburg... this one's up for interpretation...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6012" routeTag="T18" lat="38.921082" lon="-76.970398" secsSinceReport="17007" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And speaking of which, among Landover's DE40LFs, 6002, 6005, 6006, 6008, 6013, and 6014 are all offline right now (6006 was last shown at Bladensburg). Montgomery, meanwhile, only has one; 6033, as well as three D40LFRs: 6198, 6200, and 6204. From my observations, 6200 and 6204 have been out of service for about the same time (about 2 months, I'd say), I just hope they're okay; 6200 is my favorite bus...
you forgot 6184, although it hasn't shown data since it was at Annex, it is now a Montgomery bus
about 2601 and 2726, 2601 had a timeout of about a million seconds before finally showing data, I figured it might have been one of the buses taking place of 2513 and 2638. 2726 was at Johnson Truck Center for a long while, never seen a bus go directly from there to Bladensburg. 2600 is still at FMR, seen on the 38B the other day (back online as well), and 2706 is still up for questioning.
6040 is back online yet again, I wonder what will become of that bus, I hope it's alright
<vehicle id="6040" lat="38.920971" lon="-76.970505" secsSinceReport="47099" predictable="false" heading="-4" speedKmHr="0.0"/>
2709 and 2715 are both on South Dakota Avenue, about to merge onto New York Avenue heading towards PG County. (probably going to Davidsonville P&R)
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2709" lat="38.917892" lon="-76.954475" secsSinceReport="113" predictable="false" heading="105" speedKmHr="49.86"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2715" lat="38.918331" lon="-76.955177" secsSinceReport="185" predictable="false" heading="135" speedKmHr="48.276"/>
</body>
You know what that means: it won't be long before they return to Four Mile Run. And for the record, I didn't include 6184 b/c you mentioned that its GPS didn't work.
Speaking of which, 6198, 6200, and 6204 are all back online; at Montgomery, of course. That's a relief...
EDIT: 2671 is finally back online; it's at Johnson Truck Center.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2671" lat="38.941982" lon="-76.858711" secsSinceReport="117191" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 6012 is back at Landover again...
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6012" routeTag="T18" lat="38.936455" lon="-76.8749239" secsSinceReport="3134" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6158 on the 36.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="6158" routeTag="36" dirTag="36_36_1" lat="38.893581" lon="-77.023354" secsSinceReport="25" predictable="true" heading="105" speedKmHr="33.768"/>
</body>
2709 and 2715 have both returned to FMR.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2709" lat="38.844414" lon="-77.054016" secsSinceReport="1374" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2715" lat="38.842735" lon="-77.052406" secsSinceReport="100" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2645 has replaced them at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2645" routeTag="16B" lat="38.923996" lon="-76.9701539" secsSinceReport="4063" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
So far, nothing else has joined 2645 yet; though I am keeping an eye on 2521, 2600, and 2708, who all have long timeouts, and 2706 and 2713, who are offline.
5414 and 5422 are at Landover; presumably for the B30.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5414" lat="38.937664" lon="-76.874992" secsSinceReport="21845" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5422" routeTag="B30" lat="38.937691" lon="-76.874992" secsSinceReport="11104" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I spotted 6158 at the back of Western this afternoon.
5313 and 5315 with no info showing and 5314 at CET
<vehicle id="5314" lat="38.9408" lon="-76.878525" secsSinceReport="119776" predictable="false" heading="-4" speedKmHr="0.0"/>
and yeah 6158 also shows it's at Western on nextbus
<vehicle id="6158" lat="38.958759" lon="-77.085938" secsSinceReport="74" predictable="false" heading="345" speedKmHr="6.408"/>
2076 back offline, time for 4085 again?
4246, 4247, and 4251 at CET...
<vehicle id="4246" lat="38.941269" lon="-76.878593" secsSinceReport="122881" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4247" lat="38.941322" lon="-76.878418" secsSinceReport="123238" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4251" lat="38.941322" lon="-76.87793" secsSinceReport="185746" predictable="false" heading="-4" speedKmHr="0.0"/>
I know i said this hundreds of times, but man I'm really gonna miss the 42-4400s immensely.
2671 back at FMR, after all this time it's been MIA, there's a slight chance it may be rehabbed, but don't count on it.
<vehicle id="2671" lat="38.843174" lon="-77.054329" secsSinceReport="11427" predictable="false" heading="-4" speedKmHr="0.0"/>
We've got a new rehab; 2713 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2713" lat="38.9231989" lon="-76.970398" secsSinceReport="186" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2501 and 3032 are at the D.C. DMV inspection station; they should be back at FMR within a few days.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2501" lat="38.877304" lon="-77.013657" secsSinceReport="8" predictable="false" heading="360" speedKmHr="25.74"/>
</body>
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3032" lat="38.877632" lon="-77.011559" secsSinceReport="124" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And judging by its last seconds count, 3015 could be getting rehabbed.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="3015" lat="38.922981" lon="-76.970749" secsSinceReport="260740" predictable="false" heading="150" speedKmHr="6.408"/>
</body>
5314 is back at Northern.
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="5314" lat="38.9479479" lon="-77.032211" secsSinceReport="43803" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Finally 2665 Is Back Online
<body copyright="All data copyright WMATA Washington 2011.">
<vehicle id="2665" lat="38.922153" lon="-76.971275" secsSinceReport="249334" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2540 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2540" lat="38.923393" lon="-76.970467" secsSinceReport="548" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 2007 and 2075 are also at Bladensburg, and 2079 is offline.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2007" lat="38.920944" lon="-76.970543" secsSinceReport="339565" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2075" lat="38.920918" lon="-76.970222" secsSinceReport="339254" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: And 2501 is back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2501" lat="38.844028" lon="-77.053841" secsSinceReport="356" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
damn u beat me to it yet again
oh well but I found this: 5311 at CET
<vehicle id="5311" lat="38.941158" lon="-76.878807" secsSinceReport="13127" predictable="false" heading="-4" speedKmHr="0.0"/>
and no info showing for 5315 (i could make a huge list of what else is offline but it's not that important)
and 6506 is back online, still at Bladensburg
<vehicle id="6506" lat="38.9218789" lon="-76.971138" secsSinceReport="2657" predictable="false" heading="-4" speedKmHr="0.0"/>
anyone else notice that route 74 uses nothing but 6500s?
edit:
if 2501 is back, 3032 should be back later today or tomorrow as well. if that's the case, a new unrehabbed bus will probably take it's place as well. 2613 here looks like it may have been on the way to Bladensburg but the GPS stopped updating after passing 14th and New York NW (though i've observed plenty of drivers would take the 395 up to NY Ave instead, but who knows...)
<vehicle id="2613" lat="38.898998" lon="-77.031822" secsSinceReport="17728" predictable="false" heading="180" speedKmHr="35.388"/>
3032 back at FMR
<vehicle id="3032" lat="38.844002" lon="-77.053528" secsSinceReport="16738" predictable="false" heading="-4" speedKmHr="0.0" />
3029 takes its place at Bladensburg
<vehicle id="3029" routeTag="3T" lat="38.923229" lon="-76.970398" secsSinceReport="349" predictable="false" heading="-4" speedKmHr="0.0" />
2462 is not only online, but it's back in service! For the last 2 days it was on the P6 and would have posted the sighting but this site was down
<vehicle id="2462" lat="38.921413" lon="-76.969772" secsSinceReport="9305" predictable="false" heading="-4" speedKmHr="0.0" />
Yesterday, I saw 2711 at Davidsonville Park and Ride. It should be back at FMR by next week.
Three more 42/4300s are back online. 4262 is at Annex, 4309 and 4335 are at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4262" lat="38.874496" lon="-76.93309" secsSinceReport="278409" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4309" lat="39.045326" lon="-77.107918" secsSinceReport="137796" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4335" lat="39.046398" lon="-77.107147" secsSinceReport="13379" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
5313 and 5314 are both back in service.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5313" routeTag="70" dirTag="70_70_1" lat="38.946217" lon="-77.026749" secsSinceReport="9" predictable="true" heading="168" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5314" routeTag="70" dirTag="70_70_0" lat="38.983536" lon="-77.026505" secsSinceReport="66" predictable="true" heading="360" speedKmHr="3.204"/>
</body>
And you know what else has entered service? The 7100s.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="7110" routeTag="32" dirTag="32_32_1" lat="38.884232" lon="-76.995529" secsSinceReport="113" predictable="true" heading="116" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="7115" routeTag="E2" dirTag="E2_E2_0" lat="38.938244" lon="-76.979988" secsSinceReport="47" predictable="true" heading="345" speedKmHr="46.656"/>
</body>
7128 in service on the 62. W649 block. Man they are sprouting up really fast.
- <predictions agencyTitle="WMATA Washington" routeTitle="62 TAKOMA-PETWORTH" routeTag="62" stopTitle="Georgia Ave + New Hampshire Ave F/S" stopTag="15236">
- <direction title="North to Takoma Station">
<prediction epochTime="1325897340000" seconds="740" minutes="12" isDeparture="true" affectedByLayover="true" dirTag="62_62_0" vehicle="
7128" block="
W649" tripTag="4017871" />
2656 is back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2656" lat="38.844852" lon="-77.053703" secsSinceReport="7523" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And, to my dismay, its replacement is 2708; another rocking John Deere that's about to get neutered.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2708" lat="38.9231989" lon="-76.970467" secsSinceReport="881" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
You know, I wonder what WMATA plans to do with those engines...
6178, 6179, 6180, 6181, 2210, 2211, 2212, 2213, and 2214 are all at Montgomery (I saw 6179 on the Z6 earlier).
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6178" routeTag="D13" lat="39.046539" lon="-77.108406" secsSinceReport="11548" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6179" lat="38.966293" lon="-77.0771479" secsSinceReport="21" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6180" routeTag="Z9" dirTag="Z9_Z9_0" lat="39.05938" lon="-77.061539" secsSinceReport="26" predictable="true" heading="60" speedKmHr="65.952"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6181" lat="39.045631" lon="-77.107246" secsSinceReport="47746" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2210" routeTag="63" lat="39.046646" lon="-77.108437" secsSinceReport="5059" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2211" routeTag="N3" lat="39.046429" lon="-77.108368" secsSinceReport="4442" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2212" routeTag="31" lat="39.047005" lon="-77.108475" secsSinceReport="29905" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2213" routeTag="E4" lat="39.047005" lon="-77.108437" secsSinceReport="3350" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2214" routeTag="42" lat="39.0458489" lon="-77.107147" secsSinceReport="34284" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And somehow, 6182 is still at Annex...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6182" routeTag="94" lat="38.873039" lon="-76.932846" secsSinceReport="31401" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
aha, I knew the 7100s would displace something, I thought it would be the 6300s going to West Ox (since 6347 and 6348 are there), and I kinda expected this, but not the first thing I had in mind. Also, I can't believe it, not only did Montgomery get ALL their 6100s back (except 6182 which should be back soon), they're starting to get some of the ex-Landover ones, amazing...
I did happen to see (via nextbus) 6183 and 6192 at Western Division, idk why they're there, but they're there...
<vehicle id="6183" lat="38.958317" lon="-77.085167" secsSinceReport="86" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6192" routeTag="Y8" lat="38.957851" lon="-77.085342" secsSinceReport="324" predictable="false" heading="-4" speedKmHr="0.0"/>
also, if it's any consolation, we at least still have 2633 and 2716 unrehabbed, which have awesome JD engines
and if you ask me, 2656 is back pretty early, I'm pretty sure 2634, 2652, and 2723 came to Bladensburg first (and definitely 2711)
edit - 2032 at FMR? okay then...
<vehicle id="2032" routeTag="24T" lat="38.84367" lon="-77.053246" secsSinceReport="246" predictable="false" heading="30" speedKmHr="20.916"/>
edit 2 - looks like Western displaced an Orion VI to Montgomery as well
<vehicle id="2051" lat="39.046867" lon="-77.10746" secsSinceReport="1720" predictable="false" heading="-4" speedKmHr="0.0"/>
edit 3 - 2176 and 2177 have moved to Northern
<vehicle id="2176" routeTag="S4" dirTag="S4_S4_0" lat="38.892731" lon="-77.028046" secsSinceReport="29" predictable="true" heading="360" speedKmHr="30.564"/>
<vehicle id="2177" routeTag="S9" lat="38.947456" lon="-77.032173" secsSinceReport="30" predictable="false" heading="-4" speedKmHr="0.0"/>
edit 4 - 5321 at CET
<vehicle id="5321" lat="38.9408" lon="-76.878525" secsSinceReport="36620" predictable="false" heading="-4" speedKmHr="0.0"/>
Oh, I almost forgot: 2162 is back at Northern as well.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2162" lat="38.947319" lon="-77.032036" secsSinceReport="2386" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2706 is still offline... How much you wanna bet that when it shows up online again, it'll be at Johnson Truck Center like 2671 and 2726?
Wait. That's really odd because I saw 2162 running out of Western just a couple days ago.
i wonder if this a glitch or something but aparrently 2821 is in a neighborhood somewhere in silever spring <body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2821" lat="39.0025369" lon="-76.991257" secsSinceReport="622" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6335, 6336, and 6337 are now at west ox, id post the xml codes but im on my phone and cant copy and paste certain stuff
edit - here they are
<vehicle id="6335" lat="38.848675" lon="-77.378326" secsSinceReport="226797" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6336" routeTag="52" lat="38.848785" lon="-77.378326" secsSinceReport="86283" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6337" lat="38.848839" lon="-77.378357" secsSinceReport="50113" predictable="false" heading="-4" speedKmHr="0.0"/>
so West Ox has a pretty diverse set of 6300s, from 6301-6309, and a few 6330s, 6340s, and 6390s. from past observations (like all the 6100s moving to Annex and most of Northern's 2100s moving to Royal), West Ox may be moving forward to become a primarily 6300s, another factor could be that they have a lot of 4200s which are gonna go soon anyways.
edit 2 - 6307 and 6506 (again) at Bladensburg, 6352 and 6592 at some Cummins place in Glen Burnie, 6389 and 6457 at Johnson Truck Center, 6393 was apparently at Western then came back?, 6514 at CET, and 6384 has no data (yeah I was that bored that I looked up the DE42LFAs)
<vehicle id="6307" lat="38.922184" lon="-76.970573" secsSinceReport="359622" predictable="false" heading="330" speedKmHr="6.408"/>
<vehicle id="6506" lat="38.9218789" lon="-76.971138" secsSinceReport="952703" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6352" routeTag="E3" lat="39.157692" lon="-76.664955" secsSinceReport="78213" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6592" routeTag="36" lat="39.158215" lon="-76.666351" secsSinceReport="79759" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6389" lat="38.941956" lon="-76.858437" secsSinceReport="222374" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6457" lat="38.942451" lon="-76.858261" secsSinceReport="136540" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6393" routeTag="36" lat="39.046398" lon="-77.108093" secsSinceReport="190" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6514" lat="38.940056" lon="-76.878242" secsSinceReport="13" predictable="false" heading="-4" speedKmHr="0.0"/>
2652 is back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2652" lat="38.842899" lon="-77.05265" secsSinceReport="4806" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2361 on the K6??
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2361" routeTag="K6" dirTag="K6_K6_1" lat="39.041862" lon="-76.987198" secsSinceReport="86" predictable="true" heading="191" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on January 15, 2012, 10:52:46 AM
2361 on the K6??
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2361" routeTag="K6" dirTag="K6_K6_1" lat="39.041862" lon="-76.987198" secsSinceReport="86" predictable="true" heading="191" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on January 15, 2012, 10:52:46 AM
2361 on the K6??
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2361" routeTag="K6" dirTag="K6_K6_1" lat="39.041862" lon="-76.987198" secsSinceReport="86" predictable="true" heading="191" speedKmHr="0.0"/>
</body>
Seems like a few years ago when Bladensburg also did some K6 work.
5434 is at Johnson Truck Center (by the by, I checked their website, and apparently they're capable of doing warranty work on John Deere engines).
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5434" lat="38.942009" lon="-76.857979" secsSinceReport="1038121" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4226 is back in service.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4226" routeTag="18G" dirTag="18G_18G_0" lat="38.821423" lon="-77.127724" secsSinceReport="209" predictable="true" heading="225" speedKmHr="99.756"/>
</body>
4236, 4303, 4323, 4330, 4376, and 2021 are at CET.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4236" lat="38.941132" lon="-76.878143" secsSinceReport="74470" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4303" lat="38.941132" lon="-76.878319" secsSinceReport="78415" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4323" lat="38.941185" lon="-76.878067" secsSinceReport="527098" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4330" lat="38.941074" lon="-76.878563" secsSinceReport="110067" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4376" lat="38.941074" lon="-76.878487" secsSinceReport="1886982" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2021" lat="38.941132" lon="-76.878349" secsSinceReport="498010" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2034 and 2056 have no data.
Quote from: RideOn5905 on January 17, 2012, 05:40:04 PM
2034 and 2056 have no data.
2056 has been gone for over a year. apparently no one knows what happened to it, but the last time it was online, it was showing that it was at CET at around 31 million seconds.
2008 is also offline btw, and 2018 is finally back online (which is good because that bus is an awesome screamer)
as for the Orion VII rehabs, after 2652 came back, nothing seems to have gone to Bladensburg yet...unless maybe it's one of Bladensburg's 3000s (possibly 3014; in addition to 3012 and 3015)
Quote from: NewFlyer9736BCT on January 17, 2012, 07:43:11 PM
Quote from: RideOn5905 on January 17, 2012, 05:40:04 PM
2034 and 2056 have no data.
2056 has been gone for over a year. apparently no one knows what happened to it, but the last time it was online, it was showing that it was at CET at around 31 million seconds.
2008 is also offline btw, and 2018 is finally back online (which is good because that bus is an awesome screamer)
as for the Orion VII rehabs, after 2652 came back, nothing seems to have gone to Bladensburg yet...unless maybe it's one of Bladensburg's 3000s (possibly 3014; in addition to 3012 and 3015)
2525, 2618, and 2626 all have pretty long timeouts, too (around 600,000 each), so maybe one of those buses is its replacement; who knows.
Oh, and I forgot to mention; I saw 2033 at Bladensburg the other day, it's back at Western now. And it has been four months and seven days since 2711 arrived at Bladensburg; I think it has officially triumphed over 2593 for the second-longest stay at Bladensburg, with 2588 being the longest at about 7-8 months ( I believe you said it had a timeout of 20 million seconds at one point).
Well, looks like they've nabbed another one...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2710" routeTag="25A" lat="38.923256" lon="-76.970436" secsSinceReport="59" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
so it looks like 2639 is heading back home right now, must be the one 2710 is replacing.
<vehicle id="2639" lat="38.856155" lon="-77.053207" secsSinceReport="101" predictable="false" heading="180" speedKmHr="33.768"/>
edit - yeah it's back alright
<vehicle id="2639" lat="38.842957" lon="-77.054222" secsSinceReport="560" predictable="false" heading="-4" speedKmHr="0.0"/>
is there hope for this bus after all?
<vehicle id="2086" lat="38.946522" lon="-77.031929" secsSinceReport="9880" predictable="false" heading="-4" speedKmHr="0.0"/>
3012 looks like it was headed to Davidsonville P&R, so it may return to service soon (speaking of which, 2711 already went there but it's still not back...)
<vehicle id="3012" lat="38.953972" lon="-76.722145" secsSinceReport="39193" predictable="false" heading="75" speedKmHr="93.312"/>
and apparently 3014 is not being rehabbed yet
<vehicle id="3014" routeTag="H6" dirTag="H6_H6_1" lat="38.932907" lon="-76.993637" secsSinceReport="9" predictable="true" heading="60" speedKmHr="17.676"/>
by the way, the nextbus XML websites (except the maps) are now on webservices.nextbus.com, so just change the "www" to "webservices"
Apparently Royal Street is open on Sundays now. Got a few buses out on the 28A
<vehicle id="2131" routeTag="28A" lat="38.811138" lon="-77.043198" secsSinceReport="128" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2108" routeTag="28A" dirTag="28A_28A_0" lat="38.811138" lon="-77.042427" secsSinceReport="191" predictable="true" heading="218" speedKmHr="0.0" />
<vehicle id="2584" routeTag="28A" dirTag="28A_28A_1" lat="38.916325" lon="-77.22065" secsSinceReport="106" predictable="true" heading="218" speedKmHr="0.0" />
<vehicle id="2115" routeTag="28A" lat="38.811028" lon="-77.043167" secsSinceReport="112" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2122" routeTag="28A" lat="38.811081" lon="-77.043098" secsSinceReport="86" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2107" routeTag="28A" lat="38.809212" lon="-77.042328" secsSinceReport="112" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2525" routeTag="28A" dirTag="28A_28A_0" lat="38.821533" lon="-77.079773" secsSinceReport="107" predictable="true" heading="315" speedKmHr="65.952" />
<vehicle id="2100" routeTag="28A" lat="38.810532" lon="-77.043304" secsSinceReport="180" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2117" routeTag="28A" lat="38.810944" lon="-77.042503" secsSinceReport="101" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2730" routeTag="28A" dirTag="28A_28A_1" lat="38.826866" lon="-77.088562" secsSinceReport="18" predictable="true" heading="95" speedKmHr="0.0" />
and the 10 line
<vehicle id="2549" routeTag="10B" dirTag="10B_10B_1" lat="38.863636" lon="-77.087158" secsSinceReport="69" predictable="true" heading="345" speedKmHr="43.452" />
<vehicle id="2123" routeTag="10B" dirTag="10B_10B_0" lat="38.8112179" lon="-77.0430219" secsSinceReport="27" predictable="true" heading="218" speedKmHr="0.0" />
<vehicle id="2142" routeTag="10B" dirTag="10B_10Bc_0" lat="38.811413" lon="-77.043098" secsSinceReport="95" predictable="true" heading="218" speedKmHr="0.0" />
<vehicle id="2116" routeTag="10B" lat="38.811386" lon="-77.042572" secsSinceReport="85" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="2104" routeTag="10B" lat="38.810806" lon="-77.0431289" secsSinceReport="27" predictable="false" heading="-4" speedKmHr="0.0" />
<lastTime time="1327282660667" />
We have movement! 2033, 2035-38, 2040, and 2043 have gone to Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2033" lat="38.936729" lon="-76.874573" secsSinceReport="5313" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2035" routeTag="87" dirTag="87_87_0" lat="39.075603" lon="-76.848389" secsSinceReport="7" predictable="true" heading="352" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2036" lat="38.937031" lon="-76.874886" secsSinceReport="1455" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2037" lat="38.920204" lon="-76.860252" secsSinceReport="181" predictable="false" heading="180" speedKmHr="33.768"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2038" routeTag="43" lat="38.936455" lon="-76.874992" secsSinceReport="68" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2040" routeTag="89" lat="39.011776" lon="-76.90992" secsSinceReport="16" predictable="false" heading="210" speedKmHr="11.232"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2043" routeTag="F8" dirTag="F8_F8_1" lat="38.915966" lon="-76.915627" secsSinceReport="503" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
EDIT: 2075 is back at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2075" routeTag="J5" dirTag="J5_J5_1" lat="39.046318" lon="-77.10746" secsSinceReport="51" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: And it doesn't stop there. 2064 is at West Ox...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2064" routeTag="64" lat="38.849113" lon="-77.3799669" secsSinceReport="78993" predictable="false" heading="60" speedKmHr="11.232"/>
</body>
...while 6346 and 6349 have moved to Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6346" routeTag="S2" dirTag="S2_S2_1" lat="38.951111" lon="-77.0365829" secsSinceReport="92" predictable="true" heading="180" speedKmHr="32.184"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6349" routeTag="96" dirTag="96_96c_0" lat="38.889126" lon="-76.988708" secsSinceReport="97" predictable="true" heading="105" speedKmHr="28.943999999999996"/>
</body>
2723 back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2723" lat="38.843533" lon="-77.0539469" secsSinceReport="1870" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2683 replaces it at B-burg. Looks like we have our first REXhab, guys! ......Yeah, that was bad. (I did have it in yellow font, but it was hard to see, so I changed it back to normal)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2683" routeTag="REX" lat="38.923229" lon="-76.970505" secsSinceReport="7372" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And three more buses are at Landover; 2041, 2042, and the return of 6307.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2041" routeTag="E4" lat="38.937363" lon="-76.874847" secsSinceReport="3898" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2042" routeTag="C22" dirTag="C22_C22v1_1" lat="38.905628" lon="-76.840622" secsSinceReport="244" predictable="true" heading="93" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6307" routeTag="G14" dirTag="G14_G14_1" lat="38.993599" lon="-76.8271479" secsSinceReport="73" predictable="true" heading="360" speedKmHr="25.74"/>
</body>
3012 is... possibly back in service?
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3012" routeTag="X1" lat="38.921577" lon="-76.969353" secsSinceReport="149" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2039 is at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2039" routeTag="36" lat="38.936756" lon="-76.874428" secsSinceReport="9373" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6008 has finally updated; it's also at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6008" lat="38.936428" lon="-76.874535" secsSinceReport="81735" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Am I the only one who notice NB is down?
Quote from: Flxible_Metro_8700 on January 26, 2012, 09:48:53 AM
Am I the only one who notice NB is down?
it's not down, just change the "www" to "webservices"
example:
http://webservices.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=vehicleLocation&a=wmata&v=2711&t=0
same with the routes, but the maps link stays the same
4262 on the X2.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4262" routeTag="X2" dirTag="X2_X2_0" lat="38.895618" lon="-76.9487" secsSinceReport="28" predictable="true" heading="34" speedKmHr="0.0"/>
</body>
to add to that, 4264 is at Western
<vehicle id="4264" routeTag="42" lat="38.958786" lon="-77.085587" secsSinceReport="906" predictable="false" heading="-4" speedKmHr="0.0"/>
I think I might have mentioned that before though
2619 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2619" lat="38.9231989" lon="-76.970398" secsSinceReport="1349" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And what is 2619 replacing, you may ask? None other than 2711 (finally!)
here's some time points i got as it's making its way home
10:27 am
<vehicle id="2711" lat="38.894573" lon="-77.014252" secsSinceReport="3" predictable="false" heading="180" speedKmHr="53.1"/>
10:31 am
<vehicle id="2711" lat="38.874306" lon="-77.04348" secsSinceReport="97" predictable="false" heading="210" speedKmHr="69.192"/>
10:34 am
<vehicle id="2711" lat="38.848896" lon="-77.053032" secsSinceReport="25" predictable="false" heading="-4" speedKmHr="0.0"/>
10:37 am home sweet home
<vehicle id="2711" lat="38.842789" lon="-77.052856" secsSinceReport="6" predictable="false" heading="-4" speedKmHr="0.0"/>
And now we've got more Orion VIs fleeing to West Ox. 2048 and 2050 are already there...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2048" lat="38.848728" lon="-77.3784639" secsSinceReport="29750" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2050" lat="38.848869" lon="-77.378258" secsSinceReport="209" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
And 2049 seems to be headed there as well; it timed out while traveling WB on the Beltway past Fernwood Road.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2049" routeTag="42" lat="39.01318" lon="-77.136581" secsSinceReport="46653" predictable="false" heading="270" speedKmHr="70.776"/>
</body>
2008 is back online; it's at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2008" lat="38.935989" lon="-76.8749239" secsSinceReport="871" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2665 is at Davidsonville Park & Ride; you know what that means...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2665" lat="38.959198" lon="-76.651062" secsSinceReport="76" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
So 2665 is in the local scheme now.
3005 on the 32 cut to Tenleytown. What is going on at Bburg?
- <predictions agencyTitle="WMATA Washington" routeTitle="32 PENNSYLVANIA AVE" routeTag="32" stopTitle="Wisconsin Ave Nw + Woodley Rd Nw" stopTag="7648">
- <direction title="West to Tenleytown Station">
<prediction epochTime="1327703689563" seconds="712" minutes="11" isDeparture="false" dirTag="32_32cv4_0" vehicle="2439" block="B360" tripTag="4027123" />
<prediction epochTime="1327704790986" seconds="1813" minutes="30" isDeparture="false" dirTag="32_32cv4_0" vehicle="
3005" block="
B362" tripTag="4027156" />
</direction>
2824 on the 42
<predictions agencyTitle="
WMATA Washington" routeTitle="
42 MOUNT PLEASANT" routeTag="
42" stopTitle="
Connecticut Ave Nw + Q St Nw" stopTag="
6573"> - (http://forums.dctransit.info/#) <direction title="
North to Mt Pleasant Via Adams Morgan">
<prediction epochTime="
1327705855909" seconds="
2730" minutes="
45" isDeparture="
false" affectedByLayover="
true" dirTag="
42_42_1" vehicle="
2824" block="
B450" tripTag="
4023843" /> </direction>
2325 and
2340 on the
79 <vehicle id="
2325" routeTag="
79" dirTag="
79_79_0" lat="
38.993931" lon="
-77.028152" secsSinceReport="
104" predictable="
true" heading="
90" speedKmHr="
0.0" /> <vehicle id="
2340" routeTag="
79" dirTag="
79_79_1" lat="
38.892784" lon="
-77.02388" secsSinceReport="
150" predictable="
true" heading="
15" speedKmHr="
0.0" />
2809 on the X2 (smh thrice)
- (http://forums.dctransit.info/#) <predictions agencyTitle="
WMATA Washington" routeTitle="
X2 BENNING RD-H ST" routeTag="
X2" stopTitle="
H St Nw + 7th St Nw" stopTag="
5801"> - (http://forums.dctransit.info/#) <direction title="
East to Minnesota Ave Station"> <prediction epochTime="
1327703579698" seconds="
230" minutes="
3" isDeparture="
false" affectedByLayover="
true" dirTag="
X2_X2_0" vehicle="
2809" block="
BX24" tripTag="
3997885" />
2341 on the
X9- (http://forums.dctransit.info/#) <predictions agencyTitle="WMATA Washington" routeTitle="X9 BENNING RD-H ST EXP" routeTag="X9" stopTitle="H St Nw + 7th St Nw" stopTag="5825"> - (http://forums.dctransit.info/#) <direction title="West to Metro Center"> <prediction epochTime="1327703870667" seconds="427" minutes="7" isDeparture="false" dirTag="X9_X9_1" vehicle="2341" block="BX93" tripTag="3991668" /> So its official, Bladensburg can't assign buses properly.
No 2665 Is still blue, I saw it Yesterday leaving CET, with 2570 behind it.
speaking of 2570, it's apparently back so soon. This is probably the fastest rehab job so far.
<vehicle id="2570" lat="38.843094" lon="-77.053627" secsSinceReport="50" predictable="false" heading="-4" speedKmHr="0.0"/>
and wow, really metro? have a non-suburban seater in the blue paint but not any of the 2700s? well at least 2665 is keeping its uniqueness
edit - unfortunately, the really awesome screamer 2633 is now at Bladensburg
<vehicle id="2633" routeTag="7A" lat="38.923393" lon="-76.970436" secsSinceReport="2055" predictable="false" heading="-4" speedKmHr="0.0"/>
edit 2 - look who else decided to join
<vehicle id="2681" lat="38.923393" lon="-76.970436" secsSinceReport="1676" predictable="false" heading="-4" speedKmHr="0.0"/>
They got 2633? Aww, man... Hopefully, the Cummins they'll no doubt equip it with will sound good, like 2720, which has a great whine, and 2638, which is a "singer". (By the way, 2638 is my favorite ex-JD rehab in that regard.)
And I checked; 2570 has spent exactly two months at Bladensburg, so it could indeed be the fastest.
And on an unrelated note, 4262 is back at Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4262" lat="38.947071" lon="-77.031227" secsSinceReport="29609" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
looks like 2665 is back
<vehicle id="2665" lat="38.842541" lon="-77.052544" secsSinceReport="24035" predictable="false" heading="-4" speedKmHr="0.0"/>
I hope they put that blue stripe on the front at least. I also hope they spared this bus from becoming C-gassed
about 2570:
2567, 2508, 2664, 2702, 2703, 2632, 2634 were at Bladensburg for a longer time (especially 2634, which has been at Bburg for over 3.5 months) and they're still not home yet.
Quote from: NewFlyer9736BCT on January 28, 2012, 06:08:46 PM
looks like 2665 is back
<vehicle id="2665" lat="38.842541" lon="-77.052544" secsSinceReport="24035" predictable="false" heading="-4" speedKmHr="0.0"/>
I hope they put that blue stripe on the front at least. I also hope they spared this bus from becoming C-gassed
about 2570:
2567, 2508, 2664, 2702, 2703, 2632, 2634 were at Bladensburg for a longer time (especially 2634, which has been at Bburg for over 3.5 months) and they're still not home yet.
It does have the blue stripe, and it did get repowered.
6360 at Bladensburg
<vehicle id="6360" routeTag="D6" lat="38.9227599" lon="-76.969109" secsSinceReport="18122" predictable="false" heading="-4" speedKmHr="0.0"/>
and 6384 is back online
<vehicle id="6384" lat="39.045273" lon="-77.1078409" secsSinceReport="24219" predictable="false" heading="-4" speedKmHr="0.0"/>
NextBus reset again recently (dontcha hate when that happens?), so quick update on the Orion Vs:
Not online: 4200-08, 4214, 4219, 4236, 4241, 4247, 4250-51, 4278-79, 4288, 4294, 4296, 4300-04, 4309-10 (sorry George), 4312-13, 4315-16, 4319-20, 4323, 4326, 4330, 4332-37, 4339, 4341-42, 4344-46, 4348, 4351, 4353-54, 4357, 4359, 4365, 4375-76, 4380-82, 4388-89, 4394, 4396-98
At CET: 4245, 4322, 4325, 4331, 4356, 4363, 4390
This is such a sad sight to see... (at least my favorite V, 4355, is still out and about; it's on the Q4)
Elsewhere: 4246, 4248, and 4272 are at Annex. (4244 is still there as well)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4246" lat="38.872627" lon="-76.933929" secsSinceReport="114956" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4248" lat="38.872601" lon="-76.934067" secsSinceReport="51600" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4272" routeTag="90" lat="38.872791" lon="-76.9337539" secsSinceReport="8004" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4292 on the 42 (does Northern do some 42 runs? It seems that every once in a while, I see a Northerner on the 42)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4292" routeTag="42" dirTag="42_42_0" lat="38.910358" lon="-77.044037" secsSinceReport="279" predictable="true" heading="150" speedKmHr="17.676"/>
</body>
4241 and 4336 are back in service, and 4244 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4241" lat="38.810589" lon="-77.043304" secsSinceReport="8692" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4244" lat="38.920971" lon="-76.970299" secsSinceReport="34789" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4336" routeTag="Q1" dirTag="Q1_Q1_0" lat="39.038151" lon="-77.051323" secsSinceReport="11" predictable="true" heading="255" speedKmHr="11.232"/>
</body>
5448, 5450, and 5451 are at Montgomery for some reason...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5448" lat="39.046017" lon="-77.10746" secsSinceReport="51076" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5450" routeTag="Z8" dirTag="Z8_Z8v3_1" lat="39.0809939" lon="-76.9460749" secsSinceReport="9" predictable="true" heading="330" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5451" lat="39.045769" lon="-77.107422" secsSinceReport="27704" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2044 is also at Montgomery, and I saw 2226 on the C2 earlier; looks like the latter is back at Western.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2044" lat="39.046398" lon="-77.108269" secsSinceReport="5" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2226" lat="38.957851" lon="-77.08506" secsSinceReport="9857" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And to top it all off, 6182 is going to spend the night at Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6182" lat="38.946381" lon="-77.032143" secsSinceReport="3514" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2706 is still offline, as are 2531 and 2618.
2703 is back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2703" lat="38.842873" lon="-77.0539469" secsSinceReport="8942" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Nothing new at Bladensburg yet, but 3026 was last seen on the Beltway near Landover Road.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3026" lat="38.913189" lon="-76.850212" secsSinceReport="169178" predictable="false" heading="345" speedKmHr="69.192"/>
</body>
*gulps* 6040 is at CET. That can't be good...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" lat="38.940937" lon="-76.878036" secsSinceReport="181386" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Oh, and I forgot: 6005 is back in service; at Landover, natch.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6005" lat="38.937115" lon="-76.874535" secsSinceReport="2639" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 2664 going home at 11:52 am...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2664" lat="38.91011" lon="-77.00106" secsSinceReport="68" predictable="false" heading="240" speedKmHr="41.832"/>
11:54...
<vehicle id="2664" lat="38.906536" lon="-77.011703" secsSinceReport="3" predictable="false" heading="-4" speedKmHr="0.0"/>
11:58...
<vehicle id="2664" lat="38.888634" lon="-77.015724" secsSinceReport="25" predictable="false" heading="-4" speedKmHr="0.0"/>
12:01...
<vehicle id="2664" lat="38.881344" lon="-77.0299" secsSinceReport="43" predictable="false" heading="225" speedKmHr="62.748"/>
12:03...
<vehicle id="2664" lat="38.869053" lon="-77.0475079" secsSinceReport="41" predictable="false" heading="210" speedKmHr="61.128"/>
12:08: Back at FMR, safe and sound.
<vehicle id="2664" lat="38.844276" lon="-77.054085" secsSinceReport="31" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: Wow. two buses have returned from rehab in the past couple days, and nothing has replaced them yet. I've got some suspects, though: 2622 and 2730 have somewhat long timeouts, and 2531, 2618, 2725, and 3010 are all offline. 2706 is also offline, but it's been like that for a couple months, which leads me to believe it'll resurface at Johnson Truck Center in the not-too-distant future (next Sunday A.D., lol). In the meantime, we've got 3034 at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3034" routeTag="3T" lat="38.937775" lon="-76.8739779" secsSinceReport="349" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6048 and 6104 have no data.
you can cross 2725 off that list, saw it on the 38B about 30 min ago
also; 2018, 2034, 2045, and 2064 also have no data (2064 was recently seen at West Ox via Nextbus but soon after that, it went to CET but I never said anything about it until now)
2567 at the DC DMV, should be home soon
<vehicle id="2567" lat="38.877853" lon="-77.011597" secsSinceReport="33" predictable="false" heading="-4" speedKmHr="0.0"/>
2632 also around the DC DMV area
<vehicle id="2632" lat="38.879253" lon="-77.009422" secsSinceReport="149" predictable="false" heading="90" speedKmHr="6.408"/>
edit - 2044, 2047, and 2051 moved to Montgomery (2045 remains offline, but knowing WMATA, it could be anywhere from CET to Landover to West Ox, etc...)
<vehicle id="2044" lat="39.046841" lon="-77.107597" secsSinceReport="142" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2047" lat="39.047554" lon="-77.108368" secsSinceReport="85" predictable="false" heading="75" speedKmHr="22.5"/>
<vehicle id="2051" routeTag="D3" lat="39.046646" lon="-77.108513" secsSinceReport="8195" predictable="false" heading="-4" speedKmHr="0.0"/>
so it looks like 2046 is the only remaining Orion VI at Western that's online.
in addition to 2045 - 2018, 2021, 2034, and 2064 are offline
a bunch of LFAs have moved as well
6349-6352 have moved to Northern
<vehicle id="6349" routeTag="92" lat="38.947346" lon="-77.031471" secsSinceReport="8855" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6350" routeTag="43" lat="38.948143" lon="-77.030632" secsSinceReport="19877" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6351" routeTag="E4" lat="38.947346" lon="-77.031227" secsSinceReport="20675" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6352" routeTag="60" lat="38.948116" lon="-77.031967" secsSinceReport="4240" predictable="false" heading="-4" speedKmHr="0.0"/>
6307 is back at West Ox, and has brought along 6310 and 6311
<vehicle id="6307" routeTag="H11" lat="38.848511" lon="-77.379128" secsSinceReport="2797" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6310" routeTag="G14" lat="38.848675" lon="-77.378326" secsSinceReport="16705" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6311" lat="38.848812" lon="-77.378357" secsSinceReport="15771" predictable="false" heading="-4" speedKmHr="0.0"/>
6365, 6366 and 6372 now at Northern (6371 still at Montgomery apparently)
<vehicle id="6365" routeTag="J3" lat="38.947289" lon="-77.031334" secsSinceReport="14999" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6366" routeTag="K6" lat="38.947868" lon="-77.031967" secsSinceReport="4260" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6372" routeTag="J2" lat="38.948059" lon="-77.031998" secsSinceReport="4543" predictable="false" heading="-4" speedKmHr="0.0"/>
6315 and 6370 have no data showing
2046 is at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2046" routeTag="42" lat="39.047199" lon="-77.11264" secsSinceReport="7060" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6002 and 6006 are back online; both are at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6002" lat="38.9364009" lon="-76.875443" secsSinceReport="1660" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6006" lat="38.936207" lon="-76.875092" secsSinceReport="744" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 2725 is back online, 6342 is at Bladensburg, and 6393 has no data.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2725" lat="38.841305" lon="-77.053978" secsSinceReport="1630" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6342" routeTag="H8" lat="38.922924" lon="-76.969177" secsSinceReport="9" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2634 is also back online, still at Bladensburg of course
<vehicle id="2634" lat="38.922512" lon="-76.971169" secsSinceReport="7410" predictable="false" heading="-4" speedKmHr="0.0"/>
also, apparently the only B30 bus that's on the B30 is 6212 (plus 6214 has no data), while 2012 is also on the B30
2632 back at FMR
<vehicle id="2632" lat="38.844578" lon="-77.0539469" secsSinceReport="594" predictable="false" heading="-4" speedKmHr="0.0"/>
2622 at Bladensburg, though this might be one of the ones to replace 2664 or 2703
<vehicle id="2622" lat="38.922844" lon="-76.971169" secsSinceReport="2430" predictable="false" heading="-4" speedKmHr="0.0"/>
nothing else new at Bladensburg, 2730 finally updated as well but it's at FMR
<vehicle id="2730" lat="38.842598" lon="-77.053421" secsSinceReport="4958" predictable="false" heading="-4" speedKmHr="0.0"/>
6040 (I wish 'silver' was available under "Change Color") is back at Bladensburg. I just hope it returns to service before too long...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" lat="38.922981" lon="-76.970924" secsSinceReport="105391" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6342 is back at Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6342" routeTag="S4" dirTag="S2_S2_1" lat="38.994591" lon="-77.028183" secsSinceReport="109" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
Time for another Orion V update: Here's a list of buses that have moved to CET over the past week (not counting the ones that were there since the reset): 4244, 4247, 4294, 4305, 4308, 4311, 4314, 4317-18, 4327-28, 4344, 4358, 4360-62, 4378, 4384-89, 4391, 4393, 4395-96, and 4398.
Meanwhile, 4242, 4255, and 4261-64 have moved to Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4242" lat="38.936234" lon="-76.874954" secsSinceReport="184121" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4255" lat="38.937061" lon="-76.873871" secsSinceReport="78861" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4261" lat="38.935711" lon="-76.8754809" secsSinceReport="76902" predictable="false" heading="120" speedKmHr="30.564"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4262" lat="38.936676" lon="-76.874573" secsSinceReport="94520" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4263" lat="38.936481" lon="-76.874359" secsSinceReport="187907" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4264" lat="38.936893" lon="-76.873871" secsSinceReport="80817" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4325 on the 32? Okay.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4325" routeTag="32" dirTag="32_32_1" lat="38.871307" lon="-76.970993" secsSinceReport="10" predictable="true" heading="193" speedKmHr="1.584"/>
</body>
3941 has no data.
So, none of the 4400s have gone yet. I'm wondering if WMATA's next 40-foot order is going to include any buses with suburban seating...
2702 back at FMR
<vehicle id="2702" lat="38.843063" lon="-77.053139" secsSinceReport="7020" predictable="false" heading="-4" speedKmHr="0.0"/>
and now, what do ya know...2730 is its replacement
<vehicle id="2730" lat="38.921055" lon="-76.970573" secsSinceReport="50202" predictable="false" heading="-4" speedKmHr="0.0"/>
edit - 2661 has also decided to join 2730
<vehicle id="2661" routeTag="16P" lat="38.923229" lon="-76.970367" secsSinceReport="12823" predictable="false" heading="-4" speedKmHr="0.0"/>
and 6214 is back online
<vehicle id="6214" lat="38.936291" lon="-76.874397" secsSinceReport="108422" predictable="false" heading="-4" speedKmHr="0.0"/>
2531 headed to Bladensburg.
11:14 a.m.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2531" lat="38.882225" lon="-77.018768" secsSinceReport="13" predictable="false" heading="90" speedKmHr="70.776"/>
11:16
<vehicle id="2531" lat="38.896664" lon="-77.0140459" secsSinceReport="7" predictable="false" heading="360" speedKmHr="48.276"/>
11:20
<vehicle id="2531" lat="38.90802" lon="-77.006905" secsSinceReport="35" predictable="false" heading="-4" speedKmHr="0.0"/>
11:23
<vehicle id="2531" lat="38.909641" lon="-77.002182" secsSinceReport="76" predictable="false" heading="-4" speedKmHr="0.0"/>
11:27
<vehicle id="2531" lat="38.9116519" lon="-76.996338" secsSinceReport="171" predictable="false" heading="60" speedKmHr="48.276"/>
11:32 There we go, right on cue.
<vehicle id="2531" lat="38.923393" lon="-76.970436" secsSinceReport="33" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Looks like it had replaced 2567.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2567" lat="38.844219" lon="-77.054085" secsSinceReport="3982" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6014 is at Bladensburg, 6023 is at Johnson Truck Center, and 6033 is back at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6014" lat="38.9221" lon="-76.970642" secsSinceReport="174927" predictable="false" heading="150" speedKmHr="9.648"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6023" lat="38.941132" lon="-76.859558" secsSinceReport="503399" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6033" lat="39.047554" lon="-77.108299" secsSinceReport="2564" predictable="false" heading="90" speedKmHr="17.676"/>
</body>
2045 is back online, it's at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2045" lat="39.047115" lon="-77.10746" secsSinceReport="7671" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2216 is at Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2216" routeTag="62" lat="38.946548" lon="-77.031792" secsSinceReport="306" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6353, 6354, and 6356 are at Northern. (6355 seems to still be a Western bus; it was last shown at the National Cathedral)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6353" lat="38.947647" lon="-77.031441" secsSinceReport="4965" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6354" routeTag="92" dirTag="92_92v1_1" lat="38.866772" lon="-76.985344" secsSinceReport="163" predictable="true" heading="102" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6356" lat="38.9479789" lon="-77.032242" secsSinceReport="10639" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6357, 6358, and 6359 are at West Ox.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6357" routeTag="60" lat="38.849388" lon="-77.377556" secsSinceReport="8647" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6358" routeTag="E4" lat="38.848701" lon="-77.378815" secsSinceReport="8816" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6359" routeTag="18S" lat="38.849087" lon="-77.377975" secsSinceReport="16691" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6360, 6361, 6371, and 6373 all have rather long timeouts, so they're either about to flee elsewhere, or they already have.
6604 on the 96.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6604" routeTag="96" dirTag="96_96_0" lat="38.9005129" lon="-77.009178" secsSinceReport="41" predictable="true" heading="195" speedKmHr="8.028"/>
</body>
6361 and 6371 have both updated; they're still at their own homes.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6361" routeTag="32" dirTag="32_32_1" lat="38.961231" lon="-77.085373" secsSinceReport="751" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6371" lat="39.045273" lon="-77.107918" secsSinceReport="3374" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2508 back at FMR, i will now check to see if it has a replacemtn (im on my phone btw)
Here's 2508.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2508" lat="38.842873" lon="-77.052826" secsSinceReport="1585" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And its replacement is 3023. Well, at least it's not another 26-2700...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3023" routeTag="9A" lat="38.923393" lon="-76.970467" secsSinceReport="14203" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
EDIT: I hope that when 2634 returns, its replacement will be a 2500; there are only two of them at Bladensburg right now (three if you count 2601). Oh, and speaking of rehab, I think 3010 might be going through it, it's been offline since the last reset.
And 6360 has reset, still at Western.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6360" lat="38.958317" lon="-77.085274" secsSinceReport="4339" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2653 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2653" lat="38.920918" lon="-76.970367" secsSinceReport="199590" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Nextbus reset again (ain't that lovely)
You got your wish 5905, a new 2500 is now at Bladensburg, this time it's 2569
<vehicle id="2569" routeTag="38B" lat="38.921577" lon="-76.969353" secsSinceReport="11686" predictable="false" heading="-4" speedKmHr="0.0"/>
I don't think it has replaced anything yet, I checked the soon-to-be-back buses but they're still at Bladensburg
also, 2540 and 3029 are back online, still at Bburg
EDIT - check 2 posts down regarding 2569
Cool. I have a feeling it'll be displacing 2634 later today; or possibly 3015.
2645, 2713, and 2726 are all back online as well, at Bladensburg, though 2636 has slipped offline.
In other news, 6361-64 have fled to Northern, while 6355 and 6360 have also slipped offline.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6361" routeTag="90" dirTag="90_90_0" lat="38.861794" lon="-76.995247" secsSinceReport="10" predictable="true" heading="90" speedKmHr="9.648"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6362" lat="38.946602" lon="-77.030388" secsSinceReport="12646" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6363" lat="38.946712" lon="-77.031754" secsSinceReport="13714" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6364" routeTag="90" dirTag="90_90_0" lat="38.911236" lon="-77.010017" secsSinceReport="90" predictable="true" heading="285" speedKmHr="28.943999999999996"/>
</body>
Sadly, only 8 of Montgomery's 42-4300s remain online: 4258-59, 4321, 4338, 4340, 4343, 4347, and 4350.
4325 is still at Western, though I have a feeling it's really a 7100 disguised as 4325, like what happened with the Flxibles several months back.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4325" routeTag="36" dirTag="36_36_0" lat="38.8739739" lon="-76.971382" secsSinceReport="2" predictable="true" heading="300" speedKmHr="22.5"/>
</body>
false alarm
<vehicle id="2569" routeTag="22A" dirTag="22A_22Av2_1" lat="38.8431209" lon="-77.054329" secsSinceReport="180" predictable="true" heading="218" speedKmHr="0.0"/>
good thing too, I was predicting this bus would be one of the last to be rehabbed, haha...
EDIT - 2636 is back online, at Johnson Truck Center (I think it's been there before actually)
<vehicle id="2636" lat="38.942284" lon="-76.858223" secsSinceReport="3113" predictable="false" heading="-4" speedKmHr="0.0"/>
however, 2586 remains offline, as well as some of the ones at Bburg awaiting rehab
EDIT2 - 6317 and 6371 are also at JTC
<vehicle id="6317" lat="38.942314" lon="-76.858223" secsSinceReport="21449" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6371" lat="38.942394" lon="-76.858818" secsSinceReport="13333" predictable="false" heading="-4" speedKmHr="0.0"/>
and 6506 is back in service, on none other than route 74
<vehicle id="6506" routeTag="74" dirTag="74_74v1_0" lat="38.892071" lon="-77.022026" secsSinceReport="31" predictable="true" heading="165" speedKmHr="14.471999999999998"/>
Come to think of it, I think I'll list the 42-43-4400s from each division that are still online, as opposed to the ones that are offline.
West Ox: 4209-13, 4215-18, 4220-32, 4237
Royal: 4233-35, 4238-41, 4256-57, 4260, 4399, 4401-12
Annex: 4246, 4248
Landover: 4249, 4252-55, 4261-64, 4367-74, 4377-79, 4383-86
Northern: 4265-77, 4280-87, 4289-93, 4295, 4297-99
Montgomery: see 2 posts above
You've gotta be kidding me... NextBus reset yet again. Evidence? 2540 and 2634 have slipped offline again, as have countless other buses, including 6137 and 6312.
On that note, 6360 is back online, still at Western.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6360" lat="38.9582059" lon="-77.085274" secsSinceReport="56" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6360 has finally made the move to Northern
<vehicle id="6360" routeTag="74" dirTag="74_74_0" lat="38.881096" lon="-77.021812" secsSinceReport="112" predictable="true" heading="360" speedKmHr="14.471999999999998"/>
6355 is back online, also at Northern
<vehicle id="6355" routeTag="S1" dirTag="S1_S1_1" lat="38.902683" lon="-77.036652" secsSinceReport="52" predictable="true" heading="245" speedKmHr="0.0"/>
so that's it, Western has no more 6300s and 2000s
also...4317 is back online and back at Montgomery (after being at CET about a week ago), I really hope it's not done and I hope it still screams
<vehicle id="4317" lat="39.045685" lon="-77.107246" secsSinceReport="7431" predictable="false" heading="-4" speedKmHr="0.0"/>
7114 is at Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="7114" routeTag="62" lat="38.946354" lon="-77.031898" secsSinceReport="14237" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2634 is back online, still at Bladensburg (by this point, I think it's been in rehab even longer than 2711).
5447 and 5449 are also back online, still at Northern.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5447" lat="38.946491" lon="-77.031723" secsSinceReport="8871" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5449" lat="38.946629" lon="-77.031685" secsSinceReport="8879" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3015 was at Brookland Station a couple minutes ago, now it's at 14th and Irving NE, possibly on the H6. I think it's safe to say this bus is back from rehab.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3015" lat="38.929031" lon="-76.986115" secsSinceReport="45" predictable="false" heading="165" speedKmHr="19.296"/>
</body>
"4359" is at Western (either it's an Xcel in disguise, or it really is 4359).
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4359" lat="38.961094" lon="-77.085968" secsSinceReport="57" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
If 3015 is back then it looks like 2675 is its replacement
<vehicle id="2675" routeTag="REX" lat="38.922871" lon="-76.971207" secsSinceReport="140699" predictable="false" heading="-4" speedKmHr="0.0"/>
Judging from its seconds count and its location within Bladensburg, 3017 might be getting rehabbed as well. Emphasis on might.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3017" lat="38.923283" lon="-76.970222" secsSinceReport="167005" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And speaking of Bladensburg, 2619 and 2708 are back online; they're still there.
Don't forget 3011 which has an even higher seconds count
<vehicle id="3011" lat="38.921551" lon="-76.9693829" secsSinceReport="178184" predictable="false" heading="-4" speedKmHr="0.0"/>
Never mind...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3017" routeTag="B8" lat="38.921604" lon="-76.969353" secsSinceReport="11744" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Double never mind...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3011" routeTag="U4" dirTag="U4_U4_0" lat="38.902931" lon="-76.93351" secsSinceReport="210" predictable="true" heading="255" speedKmHr="4.824"/>
</body>
DOUBLE EDIT: The list of buses at CET is growing; among the group there, we've got 4321, 4324, 4364, 6040 and 6137. I hope the last two are okay...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4321" lat="38.941132" lon="-76.877686" secsSinceReport="5781" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4324" lat="38.941101" lon="-76.877686" secsSinceReport="5907" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4364" lat="38.941074" lon="-76.877724" secsSinceReport="397646" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" lat="38.941158" lon="-76.878738" secsSinceReport="5110" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6137" lat="38.941269" lon="-76.878418" secsSinceReport="265" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
TRIPLE EDIT: NextBus must be having technical difficulties or something; almost none of the routes are showing any buses. All the buses that are on routes have timeouts of 12-1300 seconds.
While searching for buses, I found 6469 at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6469" lat="38.921494" lon="-76.9701539" secsSinceReport="269978" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
This just in: 6137 is finally back home at Annex!
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6137" lat="38.873123" lon="-76.932953" secsSinceReport="20170" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Now all that's left is for 6040 to return to Landover. Oh, and 6212 is at CET for some reason...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6212" routeTag="B30" lat="38.940636" lon="-76.878349" secsSinceReport="9248" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6040 is returning with a bit of a surprise...
Quote from: rideonrulez on February 28, 2012, 04:52:32 PM
6040 is returning with a bit of a surprise...
I figured that's the one I saw at CET all decked out. I wonder when they'll put it into service.
(regarding 6040)
I think someone said it was painted in the express scheme? or local or something like that
anyways, how long has it been since that train collision? I'm thinking it's been out of service longer than 5818 has for Ride On (speaking of which, anyone have any news about 5948?)
Quote from: NewFlyer9736BCT on February 28, 2012, 05:36:34 PM
(regarding 6040)
I think someone said it was painted in the express scheme? or local or something like that
anyways, how long has it been since that train collision? I'm thinking it's been out of service longer than 5818 has for Ride On (speaking of which, anyone have any news about 5948?)
I just checked, it's in the express scheme.You know, I'm starting to wonder if it was rehabbed during its 35-month hiatus. What about 6137? Could it have been decked out in the local scheme/rehabbed during its sojourn at Blade?
Sadly, I have not heard anything about 5948, nor have I seen it since the accident.
6014 is back at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6014" lat="38.936893" lon="-76.874992" secsSinceReport="286" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6106 on the 79.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6106" routeTag="79" dirTag="79_79_1" lat="38.937721" lon="-77.024513" secsSinceReport="34" predictable="true" heading="345" speedKmHr="24.12"/>
</body>
Quote from: RideOn5905 on February 28, 2012, 06:03:43 PM
Quote from: NewFlyer9736BCT on February 28, 2012, 05:36:34 PM
(regarding 6040)
I think someone said it was painted in the express scheme? or local or something like that
anyways, how long has it been since that train collision? I'm thinking it's been out of service longer than 5818 has for Ride On (speaking of which, anyone have any news about 5948?)
I just checked, it's in the express scheme.You know, I'm starting to wonder if it was rehabbed during its 35-month hiatus. What about 6137? Could it have been decked out in the local scheme/rehabbed during its sojourn at Blade?
Sadly, I have not heard anything about 5948, nor have I seen it since the accident.
5948 looks like its being parted out. It can be seen from the street when driving up Crabbs Branch Rd.
Breaking News: 6040 is finally back at Landover!!
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" lat="38.935604" lon="-76.874992" secsSinceReport="6897" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 2079 is back online; it is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2079" lat="38.922539" lon="-76.971413" secsSinceReport="6397" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2636 is back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2636" lat="38.856346" lon="-77.052406" secsSinceReport="121" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2618 is still offline, as is 2706... If neither of them reappears at Johnson Truck Center, I'll eat my socks.
6040 at the DC DMV. Should be back in service by next week (or maybe sooner, who knows) after about 3 years of playing dead
<vehicle id="6040" lat="38.878265" lon="-77.011276" secsSinceReport="29" predictable="false" heading="-4" speedKmHr="0.0"/>
2645 back at FMR
<vehicle id="2645" lat="38.844193" lon="-77.054123" secsSinceReport="221" predictable="false" heading="-4" speedKmHr="0.0"/>
2618 is back online finally, at Bladensburg
<vehicle id="2618" lat="38.923008" lon="-76.970818" secsSinceReport="7888" predictable="false" heading="-4" speedKmHr="0.0"/>
also they've got another REX bus, this time 2678
<vehicle id="2678" lat="38.923172" lon="-76.970367" secsSinceReport="1642" predictable="false" heading="-4" speedKmHr="0.0"/>
Attention patrons of the forums:
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" routeTag="F4" dirTag="F4_F4_1" lat="38.960049" lon="-76.916428" secsSinceReport="410" predictable="true" heading="255" speedKmHr="37.008"/>
</body>
That is all.
EDIT: After spending almost FIVE months in rehab, 2634 is FINALLY returning to Four Mile Run... possibly. GPS shows it's traveling on the inner loop of the Beltway, near Van Dorn Metro.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2634" lat="38.801182" lon="-77.114532" secsSinceReport="635" predictable="false" heading="240" speedKmHr="74.016"/>
</body>
And it's replacement at Bladensburg is 2662. (another 2600? I'm getting sick of this happening)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2662" lat="38.923889" lon="-76.9702609" secsSinceReport="3051" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: Yep, I knew it. 2634 is indeed back.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2634" lat="38.843559" lon="-77.053284" secsSinceReport="4617" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
finally 2634 is back! glad to finally see this day.
In regards to the recent incident involving 6105 at Penn and Southern Ave SE, 6105 awaits repairs at Bladensburg (damage doesn't seem too bad, shouldn't take too long)
<vehicle id="6105" routeTag="M6" lat="38.920891" lon="-76.970367" secsSinceReport="10664" predictable="false" heading="-4" speedKmHr="0.0"/>
Judging from its seconds count, I'd say 3003 is also getting 'habbed.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3003" lat="38.9230919" lon="-76.970398" secsSinceReport="575380" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2726 is back
<vehicle id="2726" lat="38.842899" lon="-77.052437" secsSinceReport="5967" predictable="false" heading="-4" speedKmHr="0.0"/>
and another fellow 2700 replaces it
<vehicle id="2722" lat="38.923393" lon="-76.970505" secsSinceReport="12503" predictable="false" heading="-4" speedKmHr="0.0"/>
Speaking of 2726, before it showed up at Blade, it was at Johnson Truck Center. At the top of page 29, I mentioned that Johnson was capable of doing warranty work on John Deere engines. Put 2 and 2 together, and I think there's a slight chance that this bus could still have its John Deere intact. It probably was repowered like everyone else, but there is a chance it was spared from that. No pun intended.
In unrelated news, 5308 is at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5308" lat="39.045712" lon="-77.10788" secsSinceReport="7370" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: I did a headcount of all unrehabbed Orion VIIs. They are broken down thus:
2503-2615: 38 buses
2616-2685, 2700s: 47 buses
30-footers: 13 buses
Overall Cummins/John Deere ratio: 52/46 (remember, 2679 is repowered, but not rehabbed)
I hope that WMATA alternates which buses it rehabs from here on out. (for instance; 2515, then 2644, then 2573, etc.)
3016 on the 80
<vehicle id="3016" routeTag="80" dirTag="80_80_1" lat="38.902603" lon="-77.043442" secsSinceReport="72" predictable="true" heading="232" speedKmHr="0.0"/>
also 2710 is back online at Bladensburg of course
<vehicle id="2710" lat="38.922981" lon="-76.9708859" secsSinceReport="2406" predictable="false" heading="-4" speedKmHr="0.0"/>
3020 is at the Annapolis MVA.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3020" routeTag="25C" lat="38.980759" lon="-76.557297" secsSinceReport="7779" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Well, it appears I do have to eat my socks...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2706" lat="38.867538" lon="-77.053665" secsSinceReport="88" predictable="false" heading="15" speedKmHr="24.12"/>
</body>
Could it be rehabbed? I don't know...
EDIT: Oh, dear... 6040 is back at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" lat="38.920944" lon="-76.970398" secsSinceReport="2039" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: And now it's back at Landover again? Okay...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6040" lat="38.936428" lon="-76.874641" secsSinceReport="2616" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2601 and 2713 heading back to FMR (caught them both in action!)
For 2601
12:26 PM - New York and Montana Ave NE
<vehicle id="2601" lat="38.917316" lon="-76.977295" secsSinceReport="194" predictable="false" heading="255" speedKmHr="32.184"/>
12:30 - New York and North Capitol NE
<vehicle id="2601" lat="38.907581" lon="-77.008827" secsSinceReport="31" predictable="false" heading="-4" speedKmHr="1.584"/>
12:36 - 395 about to merge with the SW-SE Freeway
<vehicle id="2601" lat="38.885197" lon="-77.012924" secsSinceReport="106" predictable="false" heading="150" speedKmHr="65.952"/>
Skipping further details because well...you get the point
12:45 - Home at FMR
<vehicle id="2601" lat="38.842625" lon="-77.053284" secsSinceReport="50" predictable="false" heading="270" speedKmHr="28.943999999999996"/>
For 2713
12:32 - New York and N NW
<vehicle id="2713" lat="38.906948" lon="-77.010475" secsSinceReport="31" predictable="false" heading="240" speedKmHr="3.204"/>
12:34 - New York and New Jersey NW
<vehicle id="2713" lat="38.90538" lon="-77.015022" secsSinceReport="43" predictable="false" heading="240" speedKmHr="19.296"/>
12:37 - 395 at D St NW
<vehicle id="2713" lat="38.893993" lon="-77.014397" secsSinceReport="67" predictable="false" heading="180" speedKmHr="74.016"/>
skipping more details...
12:45 - Home at FMR
<vehicle id="2713" lat="38.843231" lon="-77.053207" secsSinceReport="28" predictable="false" heading="195" speedKmHr="4.824"/>
Next in the rehab queue? 2603 and 2668
<vehicle id="2603" lat="38.923061" lon="-76.970398" secsSinceReport="111" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2668" lat="38.923336" lon="-76.970436" secsSinceReport="7397" predictable="false" heading="-4" speedKmHr="0.0"/>
So the remaining branded buses at FMR are as follows:
38B: 2600, 2607 (2 out of the original 7, of course 2602 does not count)
Pike Ride: 2640, 2641, 2643, 2644, 2646, 2647, 2648, 2649, 2650, 2651, 2654, 2655, 2658, 2659, 2660, 2663, 2666 (17/33)
9S: 2670, 2671, 2673 (3/5)
REX: 2674, 2676, 2677, 2679, 2680, 2682, 2684, 2685 (8/12)
2536 at Western.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2536" lat="38.958263" lon="-77.085236" secsSinceReport="4603" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2681 and 3010 are both back online at Bladensburg; since the latter is already a Bladensburg bus, I can tell that it's being rehabbed because it's over by the heavy work facility, with the likes of 2619 and 3029.
Bladensburg lost more 2100s to Royal
<vehicle id="2178" routeTag="10A" lat="38.810532" lon="-77.0432359" secsSinceReport="9344" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2180" routeTag="28A" dirTag="28A_28A_1" lat="38.837399" lon="-77.114845" secsSinceReport="52" predictable="true" heading="135" speedKmHr="33.768"/>
<vehicle id="2182" lat="38.811138" lon="-77.0431289" secsSinceReport="7" predictable="false" heading="-4" speedKmHr="0.0"/>
Data unavailable for the following buses:
2021, 2034, 2164, 2165, 2195
and even though 4388 is offline and that may be a sign of retirement, I did see it today near Federal Triangle, it was on driver training, so it may be an exclusive training bus, or the GPS is just not working
2019 and 6370 are back online, both at Bladensburg
<vehicle id="2019" lat="38.920918" lon="-76.970222" secsSinceReport="456971" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6370" lat="38.920891" lon="-76.970398" secsSinceReport="30095" predictable="false" heading="-4" speedKmHr="0.0"/>
2079 is back at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2079" lat="39.046619" lon="-77.10746" secsSinceReport="1452" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6312 is at Bladensburg, while 6371 is at Johnson Truck Ctr.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6312" lat="38.9221" lon="-76.970924" secsSinceReport="98291" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6371" lat="38.942009" lon="-76.858887" secsSinceReport="562882" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
5306 back online finally :D
looks like it's still being rehabbed, I wonder for how much longer
<vehicle id="5306" lat="38.922871" lon="-76.970123" secsSinceReport="3214" predictable="false" heading="-4" speedKmHr="0.0"/>
also, 2008 is finally back in service, not sure why it was out of service for so long, but it's back
<vehicle id="2008" routeTag="A12" dirTag="A12_A12_1" lat="38.896553" lon="-76.906387" secsSinceReport="298" predictable="true" heading="45" speedKmHr="35.388"/>
More 2100 news: 2179 is back online (at Bladensburg), 2181 has a long timeout (meaning it may have also fled the coop), 2190 is at Northern, 2195 has no data, and 2222 is at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2179" lat="38.9214399" lon="-76.970963" secsSinceReport="49845" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2181" lat="38.923393" lon="-76.970924" secsSinceReport="1244777" predictable="false" heading="315" speedKmHr="4.824"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2190" lat="38.94751" lon="-77.031441" secsSinceReport="75" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2222" lat="39.046234" lon="-77.107178" secsSinceReport="111" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6577 on the A12.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6577" routeTag="A12" dirTag="A12_A12_1" lat="38.920532" lon="-76.853394" secsSinceReport="258" predictable="true" heading="345" speedKmHr="53.1"/>
</body>
3029 is back at FMR
<vehicle id="3029" lat="38.843147" lon="-77.053139" secsSinceReport="6" predictable="false" heading="-4" speedKmHr="0.0"/>
2725 is now in line for rehab
<vehicle id="2725" routeTag="5A" lat="38.923119" lon="-76.970436" secsSinceReport="384" predictable="false" heading="-4" speedKmHr="0.0"/>
Quote from: NewFlyer9736BCT on March 17, 2012, 01:59:49 PM
3029 is back at FMR
<vehicle id="3029" lat="38.843147" lon="-77.053139" secsSinceReport="6" predictable="false" heading="-4" speedKmHr="0.0"/>
2725 is now in line for rehab
<vehicle id="2725" routeTag="5A" lat="38.923119" lon="-76.970436" secsSinceReport="384" predictable="false" heading="-4" speedKmHr="0.0"/>
Another one? At this rate, by the time all the Deeres are done with rehab, there will still be at least 30 2500s left to go. WMATA, PLEASE ALTERNATE BETWEEN THE TWO FROM HERE ON OUT!
In other news, 5308 is back at Northern, after about a week of sitting at Montgomery doing squat.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5308" lat="38.946934" lon="-77.031441" secsSinceReport="90" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 2633 is back online; at the place where John Deere engines go to die.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2633" lat="38.923172" lon="-76.970924" secsSinceReport="43699" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2540 is at the D.C. DMV. It should be back at Four Mile Run shortly.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2540" lat="38.877659" lon="-77.011597" secsSinceReport="108" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Also, 6182 on the 92.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6182" routeTag="92" dirTag="92_92v1_1" lat="38.854065" lon="-76.9700469" secsSinceReport="14" predictable="true" heading="182" speedKmHr="0.0"/>
</body>
2619 traveling northbound on I-395; I'm assuming it's returning from the D.C. DMV inspection station.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2619" lat="38.887093" lon="-77.013031" secsSinceReport="15" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And I don't know how long it's been back in service, but 7016 has returned from the accident.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="7016" routeTag="G8" dirTag="G8_G8_1" lat="38.924877" lon="-76.996681" secsSinceReport="131" predictable="true" heading="235" speedKmHr="0.0"/>
</body>
2540 and 2619 at Davidsonville P&R
<vehicle id="2540" lat="38.959309" lon="-76.651306" secsSinceReport="60" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2619" lat="38.959225" lon="-76.651131" secsSinceReport="679" predictable="false" heading="-4" speedKmHr="0.0"/>
and 2708 looks like it may be heading there too, or back
<vehicle id="2708" lat="38.91869" lon="-76.955841" secsSinceReport="2087" predictable="false" heading="-4" speedKmHr="0.0"/>
also, 3033 is at the DC DMV, I guess non-rehabbed buses also go there...
<vehicle id="3033" routeTag="9A" lat="38.8772469" lon="-77.010719" secsSinceReport="52" predictable="false" heading="165" speedKmHr="19.296"/>
one more find: 2624 at Bladensburg
<vehicle id="2624" lat="38.9224279" lon="-76.971695" secsSinceReport="3082" predictable="false" heading="-4" speedKmHr="0.0"/>
2619 and 2708 back at FMR
<vehicle id="2619" lat="38.843063" lon="-77.052338" secsSinceReport="25" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2708" lat="38.842957" lon="-77.053841" secsSinceReport="4082" predictable="false" heading="-4" speedKmHr="0.0"/>
Sorry 5905, but it looks like more JD buses are gonna get it...
2627 and 2727 next in line at Bladensburg
<vehicle id="2627" lat="38.923393" lon="-76.970467" secsSinceReport="8171" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2727" lat="38.923256" lon="-76.970398" secsSinceReport="8456" predictable="false" heading="-4" speedKmHr="0.0"/>
2540 is back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2540" lat="38.843231" lon="-77.053108" secsSinceReport="123" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
So far, nothing has replaced it at Bladensburg, but 3034 is on the 16B right now.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3034" routeTag="16B" dirTag="16B_16B_0" lat="38.837952" lon="-77.166641" secsSinceReport="20" predictable="true" heading="255" speedKmHr="16.092"/>
</body>
And speaking of 2619, I think this has been the fastest rehab job so far: I first spotted it at Blade on Jan. 27.
if anything is replacing 2540, it just might be 5318, but knowing WMATA it could be there just for a quick fix even if it's long overdue for a rehab
<vehicle id="5318" lat="38.920918" lon="-76.9700469" secsSinceReport="175396" predictable="false" heading="-4" speedKmHr="0.0"/>
Update on the 42/43/4400s:
4209 and 4378 are at CET.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4209" lat="38.9408" lon="-76.878143" secsSinceReport="166166" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4378" lat="38.940716" lon="-76.877998" secsSinceReport="168963" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4210-13 are at Western.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4210" lat="38.958069" lon="-77.085167" secsSinceReport="58694" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4211" lat="38.957989" lon="-77.085373" secsSinceReport="2056" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4212" lat="38.958069" lon="-77.084953" secsSinceReport="11073" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4213" lat="38.958069" lon="-77.085129" secsSinceReport="58993" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
4374 is at Northern, as is 4288 (which was offline for a while)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4374" lat="38.9479789" lon="-77.032104" secsSinceReport="206498" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4288" routeTag="70" lat="38.947208" lon="-77.031822" secsSinceReport="6772" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Several buses are still online, but with long timeouts, including 4246, 4343, and 4379.
4347, 4367, and 4383-85 have no data.
2034 is back online; it is at Bladensburg. Speaking of which...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2034" lat="38.922733" lon="-76.971169" secsSinceReport="11486" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I think I may have found 2540's real rehab replacement.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3017" lat="38.923172" lon="-76.969246" secsSinceReport="283007" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2618 has been updating a lot lately; a surefire sign that a bus is almost finished with rehab. It appeared at Bladensburg just early this month, but it was offline for a while before that, so it could have arrived during that time slot. And 2622 and 2661 are back online; both buses are at Bladensburg.
5306 has also been updating quite frequently recently (unlike a one-time thing with 5320 and 2086), seems like a good sign, this just may be rehab 1569.
so the next few buses that are due to return to service are 2618, 3010, 2633, 2710, 2683, and 2681 (in no order)
I heard that the REX buses will remain with the REX paint. Until we find out for sure, I'm not coloring in any of the REX buses
also, how do you know 3017 is in rehab?
3017's timeout is moderately high. That being said, I could be wrong, but no other Orion VIIs have arrived in 2540's place yet. Yeah, 5318 came up right afterwards, but I don't know if it would really count as a replacement. Besides, I said I may have found its replacement. As in, "I could be wrong, but I could also be right."
In other news, 2179 is back at Royal, and 2185 is on the 70.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2179" lat="38.811275" lon="-77.042992" secsSinceReport="12394" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2185" routeTag="70" dirTag="70_70_1" lat="38.977734" lon="-77.026505" secsSinceReport="105" predictable="true" heading="180" speedKmHr="48.276"/>
</body>
Bad news: webservices.nextbus is having some sort of technical difficulties (on my end, at least). To be precise; I get 404 error messages. I hope it gets fixed soon.
Quote from: RideOn5905 on March 27, 2012, 06:47:08 PM
Bad news: webservices.nextbus is having some sort of technical difficulties (on my end, at least). To be precise; I get 404 error messages. I hope it gets fixed soon.
they moved the site once again, now it's wmata.nextbus.com
6123 on the 36. It's been on this line since at least 1 p.m.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6123" routeTag="36" dirTag="36_36_1" lat="38.910522" lon="-77.0650409" secsSinceReport="28" predictable="true" heading="150" speedKmHr="27.324"/>
</body>
2607 at Bladensburg
Looks like 2600 is the only one left with the 38B banner left in service
<vehicle id="2607" lat="38.921028" lon="-76.970436" secsSinceReport="107577" predictable="false" heading="-4" speedKmHr="0.0"/>
this may be the replacement for 2618, though it seems like either it's still taking a test drive or just taking a different route home
<vehicle id="2618" lat="38.917507" lon="-76.933891" secsSinceReport="119" predictable="false" heading="135" speedKmHr="38.592"/>
Survey says: it is indeed 2618's replacement.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2618" lat="38.843506" lon="-77.051666" secsSinceReport="9803" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I have three words to say about this: IT'S. ABOUT. TIME. Then again, I had 2607 as one of the last ones on my list...
2607 was in the lower 1600s on my list, though knowing WMATA and how some buses can be in rehab much longer than others, my original prediction may actually be right.
but anyways that sucks only one rehab is back this weekend, there's still 2633, 2683, 2710, 3010, and 5306 that should be due to return to service soon
a lot of buses seem to go to rehab in pairs (examples below, even before the Orion VII rehabs), not too long ago it was 2627, and now 2628 has joined it at Bburg
<vehicle id="2628" lat="38.9231989" lon="-76.970436" secsSinceReport="3085" predictable="false" heading="-4" speedKmHr="0.0"/>
also 2531 is back online, still at Bburg of course
<vehicle id="2531" lat="38.921825" lon="-76.971275" secsSinceReport="104855" predictable="false" heading="-4" speedKmHr="0.0"/>
here's many examples of the pairings: (in which they are + or - 1 or 2 from each other)
3021, 3022 (1541, 1543)
2630, 2631 (1525, 1527)
2529, 2530 (1501, 1503)
2544, 2545 (1475, 1477)
2560, 2561 (1454, 1456)
2461, 2462 (1419, 1420)
2428, 2429 (1286, 1288)
2038, 2039 (1259, 1261)
2092, 2093 (1252, 1254)
2029, 2028, 2027 (1213, 1215, and 1216)
2084, 2083 (1197, 1199)
2002, 2001 (1187, 1189)
2053, 2052 (1167, 1168)
2172, 2171 (1174, 1175)
2147, 2148 (1065, 1066)
4305, 4306 (1000, 1002)
4298, 4299 (826, 827)
4203, 4204 (773, 775)
and no one has found the rehab number of 2618, but it may be 1578, and 2619 is 1576, so that's another
Curious... 2628 is at Bladensburg, but 2633, 2683 and 2710 still are not done yet. My guess is either 3010 or 5306 is done.
4210-12 are at CET. (4213 is still at Western)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4210" routeTag="43" lat="38.940746" lon="-76.878662" secsSinceReport="99869" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4211" routeTag="E2" lat="38.9408839" lon="-76.8787" secsSinceReport="100459" predictable="false" heading="210" speedKmHr="8.028"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4212" routeTag="N4" lat="38.940746" lon="-76.878662" secsSinceReport="99902" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 6312 and 6371 are back at their homes.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6312" routeTag="V12" lat="38.936371" lon="-76.874992" secsSinceReport="52834" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6371" lat="39.046509" lon="-77.108093" secsSinceReport="1234" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Oh, and 2215 is now a Montgomery bus.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2215" lat="39.046509" lon="-77.107285" secsSinceReport="2525" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2710 at DC DMV
<vehicle id="2710" lat="38.877632" lon="-77.011559" secsSinceReport="17" predictable="false" heading="-4" speedKmHr="0.0"/>
It looks like 2215 is back at Western, either that or it's staying over there temporarily like other Montgomery buses do sometimes
<vehicle id="2215" routeTag="K6" lat="38.957932" lon="-77.0847469" secsSinceReport="6610" predictable="false" heading="-4" speedKmHr="0.0"/>
In other news, 2168 and 6336 are at Bladensburg, 6369 at Johnson Truck Center, , 6500 last shown at Cummins Power Systems in Glen Burnie, and 2019 is back at Landover
<vehicle id="2168" lat="38.920807" lon="-76.9700469" secsSinceReport="1119092" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6336" routeTag="18H" lat="38.922459" lon="-76.971733" secsSinceReport="26167" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6369" lat="38.94223" lon="-76.858261" secsSinceReport="1187676" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6500" lat="39.157776" lon="-76.664467" secsSinceReport="269074" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2019" lat="38.936096" lon="-76.875061" secsSinceReport="17878" predictable="false" heading="-4" speedKmHr="0.0"/>
2077 and 6048 are back online. The former is at Bladensburg, the latter at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2077" lat="38.921055" lon="-76.970398" secsSinceReport="32994" predictable="false" heading="285" speedKmHr="3.204"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6048" lat="38.9364009" lon="-76.875198" secsSinceReport="14568" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2683 at the DC DMV
<vehicle id="2683" lat="38.8777959" lon="-77.011597" secsSinceReport="216" predictable="false" heading="-4" speedKmHr="0.0"/>
2683 and 2710 going for a test drive down Annapolis Road. I followed these two from U.S. 50 to Veterans Pkwy to Annapolis, where they've been ever since.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2683" lat="38.9396739" lon="-76.930153" secsSinceReport="2" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2710" lat="38.939644" lon="-76.930466" secsSinceReport="26" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2683 and 2710 are back at FMR
<vehicle id="2683" lat="38.843094" lon="-77.054924" secsSinceReport="3723" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2710" lat="38.844494" lon="-77.054016" secsSinceReport="4941" predictable="false" heading="-4" speedKmHr="0.0"/>
Next in the rehab queue: 2650 and 2676
<vehicle id="2650" routeTag="3E" lat="38.922897" lon="-76.96907" secsSinceReport="404" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2676" routeTag="REX" lat="38.92342" lon="-76.970467" secsSinceReport="2749" predictable="false" heading="-4" speedKmHr="0.0"/>
and lastly...Nextbus has reset again
...and you know what that means! 42/43/4400 update! Here are the buses that are still online, listed at each division:
West Ox: 4215, 4216, 4218, 4220-32, 4237 (total 17)
Royal: 4233-35, 4238-41, 4256, 4260, 4399, 4401-12 (total 22)
Landover: 4242, 4249, 4252-55, 4261, 4263-65, 4371, 4372 (total 12)
Montgomery: 4258, 4259, 4338 (total 3)
Northern: 4272, 4274, 4276, 4277, 4280-86, 4288-91, 4293, 4295, 4297-99 (total 20)
Western: "4359" (total 1)
Everybody else is either offline or at CET. Except for 4217, which is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="4217" lat="38.920864" lon="-76.970016" secsSinceReport="17796" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3010 at the DC DMV
<vehicle id="3010" lat="38.876751" lon="-77.010689" secsSinceReport="110" predictable="false" heading="-4" speedKmHr="0.0"/>
What the crap?!?
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2436" routeTag="28A" dirTag="28A_28A_0" lat="38.874332" lon="-77.1582789" secsSinceReport="10" predictable="true" heading="300" speedKmHr="4.824"/>
</body>
In other news, 2565 and 2646 have no data.
EDIT: Whaaa??
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="11" routeTag="10B" dirTag="10B_10B_0" lat="38.827003" lon="-77.058884" secsSinceReport="114" predictable="true" heading="173" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on April 10, 2012, 03:30:50 PM
What the crap?!?
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2436" routeTag="28A" dirTag="28A_28A_0" lat="38.874332" lon="-77.1582789" secsSinceReport="10" predictable="true" heading="300" speedKmHr="4.824"/>
</body>
In other news, 2565 and 2646 have no data.
EDIT: Whaaa??
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="11" routeTag="10B" dirTag="10B_10B_0" lat="38.827003" lon="-77.058884" secsSinceReport="114" predictable="true" heading="173" speedKmHr="0.0"/>
</body>
The culprit? "2436" is actually 2136, and "11" is actually 2145.
(I thought it was too good to be true, but just in case it actually was true, I waited at West Falls Church for 2436, getting ready for a shot of what would have been such a rarity)
Take a look at Nextbus, 2136 shows no data, and neither does 2145.
Also, 2565 is still around, saw it on the 4 line at Rosslyn today
Here's the so called "2436" and "11":
(http://i1212.photobucket.com/albums/cc446/gpbusgallery2/WMATA/2136a.jpg)
(http://i1212.photobucket.com/albums/cc446/gpbusgallery2/WMATA/2145a.jpg)
and one more thing: 6181 shows no data
3036 is online, I guess this is the time to enjoy the last few rides of the 3900s while we can
<vehicle id="3036" lat="38.941296" lon="-76.878212" secsSinceReport="1571" predictable="false" heading="-4" speedKmHr="0.0"/>
6016 is at Western, and 6030 is at Johnson Truck Center (wasn't it there at some point last year?)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6016" lat="38.957851" lon="-77.085274" secsSinceReport="17673" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6030" lat="38.942009" lon="-76.858154" secsSinceReport="130013" predictable="false" heading="75" speedKmHr="11.232"/>
</body>
3017 has no data. It would appear that my guess about it starting rehab is correct...
2633 and 2681 are back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2633" lat="38.842899" lon="-77.053703" secsSinceReport="1198" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2681" lat="38.843037" lon="-77.053802" secsSinceReport="3621" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2626 and 2684 have taken their place in line.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2626" lat="38.9231989" lon="-76.970367" secsSinceReport="1737" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2684" lat="38.923393" lon="-76.970467" secsSinceReport="6572" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: 3006 has no data. I wonder if this one's also going through rehab...
3010 on the B8; back in service.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3010" routeTag="B8" dirTag="B8_B8_1" lat="38.927326" lon="-76.958923" secsSinceReport="32" predictable="true" heading="15" speedKmHr="49.86"/>
</body>
Nothing new has appeared from FMR, so it looks like its replacement is 3006.
In light of the Orion VI recalls due to the fires of 2028 and 2011, various buses are being run as replacements. Most of them are 42/4300s, but here are a few runs that you certainly don't see every day:
2814 and 2343 on the C2:
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2814" routeTag="C2" dirTag="C2_C2_1" lat="39.004875" lon="-77.037636" secsSinceReport="60" predictable="true" heading="300" speedKmHr="6.408"/>
<vehicle id="2343" routeTag="C2" dirTag="C2_C2_1" lat="39.037601" lon="-77.051392" secsSinceReport="196" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
6167 on the T18:
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6167" routeTag="T18" dirTag="T18_T18_1" lat="38.946465" lon="-76.89431" secsSinceReport="5" predictable="true" heading="240" speedKmHr="33.768"/>
</body>
Aw man, I knew I should have gone out yesterday.
Anyways, here's what's for today:
4210 on the F4, 4321 on the F6, 4314 on the 2C, 4260 on the 2B (I think this bus was still around anyways, but on Royal routes), 4256 on the 1B, 2193 on the 17B, 4211 and 4366 on the A12, and the rest you can see below
<vehicle id="4210" routeTag="F4" dirTag="F4_F4_0" lat="38.963791" lon="-76.947861" secsSinceReport="108" predictable="true" heading="90" speedKmHr="35.388"/>
<vehicle id="4321" routeTag="F6" dirTag="F6_F6_0" lat="38.988541" lon="-76.935471" secsSinceReport="99" predictable="true" heading="97" speedKmHr="0.0"/>
<vehicle id="4314" routeTag="2C" dirTag="2C_2C_0" lat="38.892097" lon="-77.224953" secsSinceReport="2" predictable="true" heading="360" speedKmHr="38.592"/>
<vehicle id="4260" routeTag="2B" dirTag="2B_2B_1" lat="38.879696" lon="-77.176064" secsSinceReport="28" predictable="true" heading="75" speedKmHr="14.471999999999998"/>
<vehicle id="4256" routeTag="1B" dirTag="1B_1B_0" lat="38.870869" lon="-77.147148" secsSinceReport="119" predictable="true" heading="120" speedKmHr="45.036"/>
<vehicle id="2193" routeTag="17B" dirTag="17B_17B_1" lat="38.808441" lon="-77.255371" secsSinceReport="80" predictable="true" heading="150" speedKmHr="17.676"/>
<vehicle id="4211" routeTag="A12" lat="38.94421" lon="-76.880486" secsSinceReport="40" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="4366" routeTag="A12" dirTag="A12_A12_0" lat="38.914703" lon="-76.885628" secsSinceReport="259" predictable="true" heading="225" speedKmHr="24.12"/>
<vehicle id="4246" routeTag="R12" dirTag="R12_R12_1" lat="38.996407" lon="-76.900398" secsSinceReport="47" predictable="true" heading="274" speedKmHr="0.0"/>
<vehicle id="4362" routeTag="G12" dirTag="G12_G12_0" lat="38.994316" lon="-76.878174" secsSinceReport="148" predictable="true" heading="270" speedKmHr="40.212"/>
<vehicle id="4364" routeTag="G14" dirTag="G14_G14_1" lat="38.998219" lon="-76.912056" secsSinceReport="149" predictable="true" heading="187" speedKmHr="0.0"/>
<vehicle id="4209" routeTag="F14" dirTag="F14_F14_0" lat="38.917839" lon="-76.860153" secsSinceReport="61" predictable="true" heading="11" speedKmHr="0.0"/>
<vehicle id="4327" routeTag="F8" dirTag="F8_F8_1" lat="38.970005" lon="-76.949959" secsSinceReport="59" predictable="true" heading="75" speedKmHr="33.768"/>
<vehicle id="4360" routeTag="F1" dirTag="F1_F1_1" lat="38.918716" lon="-76.916672" secsSinceReport="94" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="6167" routeTag="F13" dirTag="F13_F13_1" lat="38.961369" lon="-76.857452" secsSinceReport="80" predictable="true" heading="360" speedKmHr="53.1"/>
<vehicle id="4248" routeTag="T18" dirTag="T18_T18_1" lat="38.938656" lon="-76.955772" secsSinceReport="169" predictable="true" heading="345" speedKmHr="17.676"/>
<vehicle id="4272" routeTag="J2" dirTag="J2_J2v2_0" lat="39.0152969" lon="-77.118797" secsSinceReport="16" predictable="true" heading="330" speedKmHr="62.748"/>
<vehicle id="2230" routeTag="J2" lat="39.079979" lon="-77.1385729" secsSinceReport="44" predictable="false" heading="270" speedKmHr="51.48"/>
<vehicle id="4266" routeTag="L2" dirTag="L2_L2_1" lat="38.906784" lon="-77.046173" secsSinceReport="20" predictable="true" heading="229" speedKmHr="0.0"/>
<vehicle id="4244" routeTag="V14" dirTag="V14_V14_1" lat="38.886871" lon="-76.896446" secsSinceReport="253" predictable="true" heading="345" speedKmHr="6.408"/>
and so on...
even though this may be temporary, it does my heart good to see some of these offline/semi-retired Orion Vs to come back to service, I hope this goes on at least until tomorrow so I can snap some shots
and one last thing: 2622 at the DC DMV
<vehicle id="2622" lat="38.87854" lon="-77.010719" secsSinceReport="303" predictable="false" heading="-4" speedKmHr="0.0"/>
6114 at Montgomery.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6114" routeTag="36" dirTag="36_36_1" lat="39.046814" lon="-77.108688" secsSinceReport="916" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
5448 is at Cummins Power Systems in Glen Burnie.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5448" routeTag="Z11" lat="39.157471" lon="-76.663979" secsSinceReport="2006" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2376 and 6156 have no data.
Apparently I was wrong about 3006...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3006" routeTag="H6" dirTag="H6_H6_1" lat="38.925537" lon="-76.981499" secsSinceReport="139" predictable="true" heading="90" speedKmHr="38.592"/>
</body>
3003 is back online; in the same area at Bladensburg as 2622 and the others.
2651 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2651" lat="38.923336" lon="-76.970467" secsSinceReport="2818" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2661 appears to be heading home to Four Mile Run.
9:37 A.M.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2661" lat="38.905132" lon="-77.0155489" secsSinceReport="110" predictable="false" heading="-4" speedKmHr="0.0"/>
9:40 A.M.
<vehicle id="2661" lat="38.882389" lon="-77.028152" secsSinceReport="114" predictable="false" heading="240" speedKmHr="70.776"/>
9:42 A.M.
<vehicle id="2661" lat="38.867016" lon="-77.049538" secsSinceReport="111" predictable="false" heading="225" speedKmHr="78.84"/>
9:47 A.M.
<vehicle id="2661" lat="38.857201" lon="-77.055168" secsSinceReport="31" predictable="false" heading="90" speedKmHr="40.212"/>
9:53 A.M. Welcome home.
<vehicle id="2661" lat="38.8431209" lon="-77.053139" secsSinceReport="19" predictable="false" heading="180" speedKmHr="3.204"/>
</body>
6155 was last spotted around Silver Spring, so it appears to be at Montgomery as well. I know this because it was on the L2 yesterday morning, then in the afternoon, I spotted it here.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6155" routeTag="Z2" lat="38.994427" lon="-77.0343089" secsSinceReport="56485" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
EDIT: 2637 is also at Bladensburg... and may have been on the D6; I don't know.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2637" routeTag="D6" lat="38.922375" lon="-76.969002" secsSinceReport="13092" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: Almost forgot; 6002, 6003, and 6009 have no data, and 6042 and 6046 are at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6042" lat="38.9221" lon="-76.970993" secsSinceReport="99904" predictable="false" heading="330" speedKmHr="3.204"/>
<vehicle id="6046" lat="38.921551" lon="-76.970329" secsSinceReport="296220" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
TRIPLE EDIT: One more thing: 2560, 2596, and 2605 are at Bladensburg as well.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2560" routeTag="16A" lat="38.920971" lon="-76.970367" secsSinceReport="108043" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2596" lat="38.920971" lon="-76.970398" secsSinceReport="100510" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2605" lat="38.920891" lon="-76.969948" secsSinceReport="78277" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2637 on the Bladensburg employee shuttle.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2637" routeTag="B99" dirTag="B99_B99_1" lat="38.921577" lon="-76.9695969" secsSinceReport="56" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
2145's GPS is back online; it's at CET.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2145" lat="38.9408" lon="-76.878525" secsSinceReport="148917" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And check out the routeTag on the following buses:
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2516" routeTag="117" lat="38.896168" lon="-77.071617" secsSinceReport="127" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2502" routeTag="110" dirTag="110_PATBL_0" lat="38.868805" lon="-77.054153" secsSinceReport="385" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="2547" routeTag="117" lat="38.862839" lon="-77.054298" secsSinceReport="73" predictable="false" heading="165" speedKmHr="37.008"/>
<vehicle id="2584" routeTag="110" dirTag="110_PATBL_0" lat="38.868309" lon="-77.054787" secsSinceReport="83" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="2588" routeTag="110" lat="38.869274" lon="-77.053177" secsSinceReport="713" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2591" routeTag="110" dirTag="110_PATBL_0" lat="38.896194" lon="-77.071655" secsSinceReport="356" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="2593" routeTag="117" lat="38.896305" lon="-77.071617" secsSinceReport="286" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
This must be a "shuttle" code; everyone's either at Pentagon or Rosslyn.
2637 on the H2? 2605 on the R3? Is this really happening?
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2637" routeTag="H2" dirTag="H2_H2_0" lat="38.930046" lon="-77.011734" secsSinceReport="223" predictable="true" heading="90" speedKmHr="8.028"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2605" routeTag="R3" dirTag="R3_R3_0" lat="38.982296" lon="-76.973343" secsSinceReport="638" predictable="true" heading="210" speedKmHr="40.212"/>
</body>
2622 back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2622" lat="38.843147" lon="-77.052963" secsSinceReport="4284" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2705 replaces it at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2705" routeTag="5A" lat="38.923473" lon="-76.970505" secsSinceReport="8655" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
I've been noticing that 2436's GPS seems to be fluctuating back and forth between Bladensburg and Royal. It must be the 2136 debacle...
2603 Is offline. I wonder if it will make a shift to Blade also.
<Error shouldRetry="false">
No data available for vehicle=2603
</Error></body>
Quote from: Flxible_Metro_8700 on April 24, 2012, 02:11:43 PM
2603 Is offline. I wonder if it will make a shift to Blade also.
<Error shouldRetry="false">
No data available for vehicle=2603
</Error></body>
It's been at Bladensburg for over a month. Go to page 34, and check the 1st post.
Quote from: RideOn5905 on April 24, 2012, 06:12:11 PM
Quote from: Flxible_Metro_8700 on April 24, 2012, 02:11:43 PM
2603 Is offline. I wonder if it will make a shift to Blade also.
<Error shouldRetry="false">
No data available for vehicle=2603
</Error></body>
It's been at Bladensburg for over a month. Go to page 34, and check the 1st post.
Oh ok. I couldnt find the post about it. Thanks.
6009 is back online; it's at Landover along with 6046.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6009" routeTag="T18" dirTag="T18_T18_1" lat="38.948582" lon="-76.87233" secsSinceReport="55" predictable="true" heading="50" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6046" lat="38.935932" lon="-76.875519" secsSinceReport="1095" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2662 is back online at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2662" lat="38.9218789" lon="-76.971062" secsSinceReport="4437" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2531 and 3023 are back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2531" lat="38.843094" lon="-77.053177" secsSinceReport="3687" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3023" lat="38.844276" lon="-77.054085" secsSinceReport="1107" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Next in line: 2629 (you have GOT to be kidding me...) and 3034.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2629" lat="38.923145" lon="-76.970436" secsSinceReport="475" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3034" routeTag="3B" lat="38.92342" lon="-76.970505" secsSinceReport="3777" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Seriously, WMATA? You have this GOLDEN opportunity to send another 2500 to rehab in place of 2531, but instead you decided to waste another John Deere. At this rate, the final 30-something rehabs will all be 2500s. If it was, say, 2730 returning from rehab, then I'd be fine with it. But 2531? There's no fucking excuse.
I hate you, WMATA. I hate you. (Incidentally, I had a feeling 3034 would be one of the next ones to get it; I'm glad I got that one right.)
In other news, NextBus reset again (which at this point is basically adding insult to injury), and 2722 is back online at Bladensburg.
EDIT: I think there's a 99.999% chance that the last VII to be rehabbed will be a 2500 (I'm thinking 2537, which was my original second-to-last pick; 2648 was my last one. But due to these circumstances, I'm shifting over to 2537.)
2463 is Offline. Guess If its running,Id catch it by luck.
2675 and 2730 are back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2675" lat="38.843147" lon="-77.053703" secsSinceReport="9562" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2730" lat="38.842846" lon="-77.053909" secsSinceReport="7036" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2641 and 2643 replace them at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2641" lat="38.923119" lon="-76.970398" secsSinceReport="9665" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2643" lat="38.92342" lon="-76.970505" secsSinceReport="20015" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2603, 5306 and 5318 are back online; all three are at Bladensburg. Meanwhile, 6048 is at Johnson Truck Center.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6048" lat="38.942696" lon="-76.858437" secsSinceReport="148836" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: I almost forgot: 2596 is back at FMR as well.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2596" routeTag="38B" lat="38.842239" lon="-77.053665" secsSinceReport="213" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6417 on the U6. (probably an emergency run from Landover)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6417" routeTag="U6" dirTag="U6_U6_0" lat="38.8897059" lon="-76.934982" secsSinceReport="240" predictable="true" heading="90" speedKmHr="48.276"/>
</body>
2668 is back online, at Bladensburg.
Quote from: RideOn5905 on May 05, 2012, 03:14:31 PM
2641 and 2643 replace them at Bladensburg.
Just great...2641 was the one I predicted to be the last rehab after 2632 got rehabbed. I also had 2501, 3012, 2645, and 2668 way up there, but now they're either rehabbed or in the process. I'm gonna do what you do and publicly announce what I think will be last (as well as choose an already-existing C Gas), seems to be working fine for you since 2537 and 2648 are still not rehabbed. Therefore, 2586 will now be the one I predict to be the last rehab, followed by (in no order) 2520, 2555, 2563, 2579, 2602, 2646, and 3006.
In related news, 6417 is back home, 3003 has updated recently, and 2463 is back online
<vehicle id="6417" lat="38.936428" lon="-76.874397" secsSinceReport="9301" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3003" lat="38.922401" lon="-76.971237" secsSinceReport="28407" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2463" routeTag="V7" lat="38.922951" lon="-76.968895" secsSinceReport="43203" predictable="false" heading="-4" speedKmHr="0.0"/>
2012 Xcelsiors 7153,7154, & 7155 Are Online on nextbus.
3031 is on the 18R (AP89)
<predictions agencyTitle="WMATA Washington" routeTitle="18R BURKE CENTRE" routeTag="18R" stopTitle="Franconia-Sprgfld Sta + Bus Bay D" stopTag="256"><direction title="West to Burke Centre"><prediction epochTime="1337034480000" seconds="437" minutes="7" isDeparture="true" affectedByLayover="true" dirTag="
18R_18R_0" vehicle="
3031" block="
AP89" tripTag="4208772"/>
Quote from: RideOn5905 on April 22, 2012, 05:54:49 PM
2637 on the Bladensburg employee shuttle.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2637" routeTag="B99" dirTag="B99_B99_1" lat="38.921577" lon="-76.9695969" secsSinceReport="56" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
2145's GPS is back online; it's at CET.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2145" lat="38.9408" lon="-76.878525" secsSinceReport="148917" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And check out the routeTag on the following buses:
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2516" routeTag="117" lat="38.896168" lon="-77.071617" secsSinceReport="127" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2502" routeTag="110" dirTag="110_PATBL_0" lat="38.868805" lon="-77.054153" secsSinceReport="385" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="2547" routeTag="117" lat="38.862839" lon="-77.054298" secsSinceReport="73" predictable="false" heading="165" speedKmHr="37.008"/>
<vehicle id="2584" routeTag="110" dirTag="110_PATBL_0" lat="38.868309" lon="-77.054787" secsSinceReport="83" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="2588" routeTag="110" lat="38.869274" lon="-77.053177" secsSinceReport="713" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2591" routeTag="110" dirTag="110_PATBL_0" lat="38.896194" lon="-77.071655" secsSinceReport="356" predictable="true" heading="218" speedKmHr="0.0"/>
<vehicle id="2593" routeTag="117" lat="38.896305" lon="-77.071617" secsSinceReport="286" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
This must be a "shuttle" code; everyone's either at Pentagon or Rosslyn.
Routes 110-118 are test garage patterns. Basically, these are test "routes" that test out the CAD/AVL systems on the buses.
110: Bladensburg
111: Four Mile Run
112: Landover
113: Montgomery
114: Northern
115: Royal
116: Southern Avenue
117: West Ox
118: Western
unbelievable, apparently no bus has returned from rehab last weekend, nor has one gone to Bladensburg. This is of course talking about FMR buses, as for Bburg buses, 3003 might be done and another Bburg 3000 may get rehabbed soon.
while I'm posting this, I might as well mention that 2672, 2723, and 7143 have no data showing
and also, 2531 hasn't shown that it's been on any route since its return to FMR, hopefully that will change tomorrow
Quote from: NewFlyer9736BCT on May 14, 2012, 08:47:43 PM
unbelievable, apparently no bus has returned from rehab last weekend, nor has one gone to Bladensburg. This is of course talking about FMR buses, as for Bburg buses, 3003 might be done and another Bburg 3000 may get rehabbed soon.
while I'm posting this, I might as well mention that 2672, 2723, and 7143 have no data showing
and also, 2531 hasn't shown that it's been on any route since its return to FMR, hopefully that will change tomorrow
I hate to burst your bubble, but it appears 3006 may be 3003's replacement, judging by its location within Bladensburg, and the somewhat long timeout. Who knows...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3006" routeTag="D3" lat="38.9231989" lon="-76.970467" secsSinceReport="110030" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
In other news, 2627 and 2727 are back online; both at Blade. Oddly enough, though, 2678 and 2725 remain offline, despite being at Bladensburg longer than those two. By the way, all Xcelsiors are online; the highest is 7167.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="7167" lat="38.940773" lon="-76.878281" secsSinceReport="122132" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 6048 is back at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6048" routeTag="84" lat="38.936977" lon="-76.874847" secsSinceReport="78" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: OrionFlyer on May 14, 2012, 06:22:46 PM
3031 is on the 18R (AP89)
<predictions agencyTitle="WMATA Washington" routeTitle="18R BURKE CENTRE" routeTag="18R" stopTitle="Franconia-Sprgfld Sta + Bus Bay D" stopTag="256"><direction title="West to Burke Centre"><prediction epochTime="1337034480000" seconds="437" minutes="7" isDeparture="true" affectedByLayover="true" dirTag="18R_18R_0" vehicle="3031" block="AP89" tripTag="4208772"/>
how do you get it to say the block number
Quote from: DCAreaTransitFan on May 15, 2012, 07:32:45 PM
Quote from: OrionFlyer on May 14, 2012, 06:22:46 PM
3031 is on the 18R (AP89)
<predictions agencyTitle="WMATA Washington" routeTitle="18R BURKE CENTRE" routeTag="18R" stopTitle="Franconia-Sprgfld Sta + Bus Bay D" stopTag="256"><direction title="West to Burke Centre"><prediction epochTime="1337034480000" seconds="437" minutes="7" isDeparture="true" affectedByLayover="true" dirTag="18R_18R_0" vehicle="3031" block="AP89" tripTag="4208772"/>
how do you get it to say the block number
Copy this link
http://wmata.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=
And enter a stop id after the = . And it'll give you the route, coach # and block
Also, can somebody explain this for me?
<body copyright="All data copyright WMATA Washington 2012."><vehicle id="
5" routeTag="G12" dirTag="G12_G12_0" lat="38.994259" lon="-76.87709" secsSinceReport="160" predictable="true" heading="282" speedKmHr="0.0"/></body>
and this
<body copyright="All data copyright WMATA Washington 2012."><vehicle id="
11" routeTag="11Y" lat="38.811165" lon="-77.042427" secsSinceReport="5" predictable="false" heading="-4" speedKmHr="0.0"/></body>
Quote from: OrionFlyer on May 16, 2012, 08:25:45 AM
Quote from: DCAreaTransitFan on May 15, 2012, 07:32:45 PM
Quote from: OrionFlyer on May 14, 2012, 06:22:46 PM
3031 is on the 18R (AP89)
<predictions agencyTitle="WMATA Washington" routeTitle="18R BURKE CENTRE" routeTag="18R" stopTitle="Franconia-Sprgfld Sta + Bus Bay D" stopTag="256"><direction title="West to Burke Centre"><prediction epochTime="1337034480000" seconds="437" minutes="7" isDeparture="true" affectedByLayover="true" dirTag="18R_18R_0" vehicle="3031" block="AP89" tripTag="4208772"/>
how do you get it to say the block number
Copy this link
http://wmata.nextbus.com/s/COM.NextBus.Servlets.XMLFeed?command=predictions&a=wmata&stopId=
And enter a stop id after the = . And it'll give you the route, coach # and block
Also, can somebody explain this for me?
<body copyright="All data copyright WMATA Washington 2012."><vehicle id="5" routeTag="G12" dirTag="G12_G12_0" lat="38.994259" lon="-76.87709" secsSinceReport="160" predictable="true" heading="282" speedKmHr="0.0"/></body>
and this
<body copyright="All data copyright WMATA Washington 2012."><vehicle id="11" routeTag="11Y" lat="38.811165" lon="-77.042427" secsSinceReport="5" predictable="false" heading="-4" speedKmHr="0.0"/></body>
The former, I have no idea. The latter, though, is 2145. And if you see 2436 on a Royal route, it's really 2136. See page 36 for more information.
EDIT: 3032 on the 38B? Oh, dear...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3032" routeTag="38B" dirTag="38B_38B_0" lat="38.8905559" lon="-77.088387" secsSinceReport="60" predictable="true" heading="240" speedKmHr="4.824"/>
</body>
DOUBLE EDIT: 6573-76 are apparently back at West Ox; it must be the Xcelsior order.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6573" lat="38.853764" lon="-77.32663" secsSinceReport="59" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6574" routeTag="1A" lat="38.9003749" lon="-77.191422" secsSinceReport="145" predictable="false" heading="75" speedKmHr="90.108"/>
<vehicle id="6575" lat="38.880024" lon="-77.112709" secsSinceReport="1682" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6576" routeTag="2C" dirTag="2C_2C_1" lat="38.9162139" lon="-77.219673" secsSinceReport="345" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
And 2560 is back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2560" lat="38.8438609" lon="-77.053665" secsSinceReport="24417" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2670 at Bladensburg
<vehicle id="2670" lat="38.923145" lon="-76.970398" secsSinceReport="108741" predictable="false" heading="-4" speedKmHr="0.0"/>
and yet it still looks like nothing came back from rehab yet, unbelievable it's been two weekends in a row, is there something that's holding them back?
6567 and 6577 have also made their way back to West Ox (although I think 6577 is originally from Western)
<vehicle id="6577" lat="38.849388" lon="-77.378708" secsSinceReport="173965" predictable="false" heading="-4" speedKmHr="0.0"/>
now hold up, it's not done from there, some of the 6540s have moved to West Ox as well
<vehicle id="6549" routeTag="18G" lat="38.849388" lon="-77.378708" secsSinceReport="175499" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6548" lat="38.849171" lon="-77.377869" secsSinceReport="162578" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6547" lat="38.849419" lon="-77.378777" secsSinceReport="175100" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6546" lat="38.849499" lon="-77.377556" secsSinceReport="169567" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6545" lat="38.848812" lon="-77.378326" secsSinceReport="150002" predictable="false" heading="-4" speedKmHr="0.0"/>
and I don't know if it was mentioned before, but 6312 is also at West Ox (been there for about a month I think)
<vehicle id="6545" lat="38.848812" lon="-77.378326" secsSinceReport="150002" predictable="false" heading="-4" speedKmHr="0.0"/>
and 6542 on the B30
<vehicle id="6542" routeTag="B30" dirTag="B30_B30_1" lat="39.190666" lon="-76.676537" secsSinceReport="512" predictable="true" heading="180" speedKmHr="30.564"/>
Quote from: NewFlyer9736BCT on May 20, 2012, 07:36:02 PM
2670 at Bladensburg
<vehicle id="2670" lat="38.923145" lon="-76.970398" secsSinceReport="108741" predictable="false" heading="-4" speedKmHr="0.0"/>
and yet it still looks like nothing came back from rehab yet, unbelievable it's been two weekends in a row, is there something that's holding them back?
6567 and 6577 have also made their way back to West Ox (although I think 6577 is originally from Western)
<vehicle id="6577" lat="38.849388" lon="-77.378708" secsSinceReport="173965" predictable="false" heading="-4" speedKmHr="0.0"/>
now hold up, it's not done from there, some of the 6540s have moved to West Ox as well
<vehicle id="6549" routeTag="18G" lat="38.849388" lon="-77.378708" secsSinceReport="175499" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6548" lat="38.849171" lon="-77.377869" secsSinceReport="162578" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6547" lat="38.849419" lon="-77.378777" secsSinceReport="175100" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6546" lat="38.849499" lon="-77.377556" secsSinceReport="169567" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6545" lat="38.848812" lon="-77.378326" secsSinceReport="150002" predictable="false" heading="-4" speedKmHr="0.0"/>
and I don't know if it was mentioned before, but 6312 is also at West Ox (been there for about a month I think)
<vehicle id="6545" lat="38.848812" lon="-77.378326" secsSinceReport="150002" predictable="false" heading="-4" speedKmHr="0.0"/>
and 6542 on the B30
<vehicle id="6542" routeTag="B30" dirTag="B30_B30_1" lat="39.190666" lon="-76.676537" secsSinceReport="512" predictable="true" heading="180" speedKmHr="30.564"/>
Well, for what it's worth, 2678 has been offline for the longest time, so it could be back. EDIT: And I almost forgot; 2725 is back online at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2725" lat="38.921825" lon="-76.971275" secsSinceReport="10926" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Well, I have found the two Bladensburg/Montgomery blocks for the C2.
<predictions agencyTitle="WMATA Washington" routeTitle="C2 GBLT-TWINBROOK" routeTag="C2" stopTitle="University Blvd + Colesville Rd" stopTag="10409">
<direction title="East to Greenbelt Station">
<prediction epochTime="1337632054280" seconds="413" minutes="6" isDeparture="false" dirTag="C2_C2_1" vehicle="7037" block="MC44" tripTag="4190067"/>
<prediction epochTime="1337632757419" seconds="1117" minutes="18" isDeparture="false" affectedByLayover="true" dirTag="C2_C2_1"
vehicle="2817" block="MC68" tripTag="4190068"/>
<prediction epochTime="1337633537419" seconds="1897" minutes="31" isDeparture="false" affectedByLayover="true" dirTag="C2_C2_1" vehicle="6027" block="MC50" tripTag="4190069"/>
<prediction epochTime="1337634317419" seconds="2677" minutes="44" isDeparture="false" affectedByLayover="true" dirTag="C2_C2_1"
vehicle="2422" block="MC69" tripTag="4190070"/>
</direction>
</predictions>
</body>
2662 and 2722 are at the DC DMV Inspection Station; meaning they should be back at FMR by this weekend.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2662" lat="38.879227" lon="-77.012299" secsSinceReport="21" predictable="false" heading="90" speedKmHr="25.74"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2722" lat="38.878704" lon="-77.010719" secsSinceReport="51" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: Oh, boy... I would hate to be on this bus right now...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3014" routeTag="C2" dirTag="C2_C2_1" lat="39.0198899" lon="-77.013588" secsSinceReport="45" predictable="true" heading="133" speedKmHr="0.0"/>
</body>
It's official; 3003 is back from rehab.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3003" routeTag="H6" dirTag="H6_H6_1" lat="38.926006" lon="-76.966309" secsSinceReport="3" predictable="true" heading="135" speedKmHr="38.592"/>
</body>
And its replacement is (most likely) 3006.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3006" routeTag="D3" lat="38.9231989" lon="-76.970467" secsSinceReport="867847" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
A good amount of the new 3000's are online.
Even though 5320 is still offline, I found this picture on Facebook
(https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-ash3/s720x720/536111_367236930005259_100001568652837_1062955_1247550647_n.jpg)
Quote from: NewFlyer9736BCT on May 27, 2012, 11:05:55 AM
Even though 5320 is still offline, I found this picture on Facebook
(https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-ash3/s720x720/536111_367236930005259_100001568652837_1062955_1247550647_n.jpg)
Cool. I wonder if this could be the #1569 that we're
still missing? And surprisingly, 2662 and 2722 are still at Bladensburg. I would've thought they'd be back by now. I guess not...
3 weekends in a row without anything coming back to FMR? This is making me super impatient, let's hope it's worth the wait.
Well, today may be Monday but it is also Memorial Day so most would consider this day to still be part of the weekend, but let's hope something comes back in the next day or 2.
In the meantime, 7149 and 7151 are now online, as well as 2676
<vehicle id="7149" lat="38.941101" lon="-76.878387" secsSinceReport="358862" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7151" lat="38.941101" lon="-76.878281" secsSinceReport="284489" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2676" lat="38.923035" lon="-76.970856" secsSinceReport="276442" predictable="false" heading="-4" speedKmHr="0.0"/>
Just curious about how effective searching the NextBus XML data is for finding active vehicles on the road - I just scanned a bunch and the refresh numbers on most was kind of high and more were showing as unassigned to any route than I would expect in PM rush. My experience in accessing this data from other systems is that the refresh rate should yield much lower numbers. Thanks.
Quote from: NewFlyer9736BCT on May 28, 2012, 05:57:15 PM
3 weekends in a row without anything coming back to FMR? This is making me super impatient, let's hope it's worth the wait.
Well, today may be Monday but it is also Memorial Day so most would consider this day to still be part of the weekend, but let's hope something comes back in the next day or 2.
In the meantime, 7149 and 7151 are now online, as well as 2676
<vehicle id="7149" lat="38.941101" lon="-76.878387" secsSinceReport="358862" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="7151" lat="38.941101" lon="-76.878281" secsSinceReport="284489" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2676" lat="38.923035" lon="-76.970856" secsSinceReport="276442" predictable="false" heading="-4" speedKmHr="0.0"/>
We can now add 2650 to that list.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2650" lat="38.921989" lon="-76.971169" secsSinceReport="374537" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Like I said before, 2678 has been offline ever since it first began rehab back in early March. Since you noticed 2670 at Bladensburg last week, and seeing how 5320 is back in service despite being offline, I'm gonna assume that 2678 is back at Four Mile Run, in that same manner. Also, I don't know if you noticed, but 3003 is back in service.
Quote from: Orion 1200 on May 28, 2012, 06:45:06 PM
Just curious about how effective searching the NextBus XML data is for finding active vehicles on the road - I just scanned a bunch and the refresh numbers on most was kind of high and more were showing as unassigned to any route than I would expect in PM rush. My experience in accessing this data from other systems is that the refresh rate should yield much lower numbers. Thanks.
Was this from today? If so, then it makes sense, since today's a holiday, and Metro's operating on a Sunday schedule. Try it again tomorrow, and everything should be back to normal.
2662 and 2722 have returned to FMR at last.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2662" lat="38.8431209" lon="-77.052933" secsSinceReport="2887" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2722" lat="38.842735" lon="-77.052788" secsSinceReport="1152" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2644 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2644" lat="38.9231989" lon="-76.970398" secsSinceReport="6854" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905 on May 28, 2012, 11:13:24 PM
Was this from today? If so, then it makes sense, since today's a holiday, and Metro's operating on a Sunday schedule. Try it again tomorrow, and everything should be back to normal.
My bad - I forgot about that as I had to work! Some of the refresh numbers look a bit higher than I'm used to with other NextBus systems providing open data but it does seem more like what I would expect. Thanks for this information as I didn't know this existed until now.
2224 and 2230 are at Montgomery
<vehicle id="2224" lat="39.046677" lon="-77.108093" secsSinceReport="1336" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2230" routeTag="C4" lat="39.047142" lon="-77.107498" secsSinceReport="277" predictable="false" heading="-4" speedKmHr="0.0"/>
2668 at the DC DMV
<vehicle id="2668" lat="38.877659" lon="-77.011597" secsSinceReport="313" predictable="false" heading="-4" speedKmHr="0.0"/>
2145's GPS is finally back up and running. Now all that's left is 2136...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2145" routeTag="7M" dirTag="7M_7M_1" lat="38.867432" lon="-77.060768" secsSinceReport="100" predictable="true" heading="285" speedKmHr="67.572"/>
</body>
5320 finally back online
<vehicle id="5320" lat="38.947784" lon="-77.031967" secsSinceReport="21183" predictable="false" heading="-4" speedKmHr="0.0" />
Quote from: NewFlyer9736BCT on May 31, 2012, 04:15:47 PM
5320 finally back online
<vehicle id="5320" lat="38.947784" lon="-77.031967" secsSinceReport="21183" predictable="false" heading="-4" speedKmHr="0.0" />
...as is 5301.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5301" lat="38.9223209" lon="-76.971451" secsSinceReport="83151" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And it looks like the process has just begun...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3047" routeTag="W3" dirTag="W3_W3v1_1" lat="38.845871" lon="-77.001724" secsSinceReport="75" predictable="true" heading="270" speedKmHr="33.768"/>
</body>
2531 is finally back in service, not sure why it took so long after coming back to FMR
<vehicle id="2531" routeTag="29G" dirTag="29G_29G_0" lat="38.869686" lon="-77.052406" secsSinceReport="2" predictable="true" heading="52" speedKmHr="0.0"/>
2668 is back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2668" lat="38.84301" lon="-77.052757" secsSinceReport="2300" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
So far, nothing has replaced it. We should probably keep an eye on 2640, though.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2640" lat="38.844551" lon="-77.053978" secsSinceReport="755715" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 3033 is at Landover.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3033" routeTag="25C" lat="38.937721" lon="-76.873871" secsSinceReport="19447" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT
Quote from: RideOn5905
So far, nothing has replaced it. We should probably keep an eye on 2640, though.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2640" lat="38.844551" lon="-77.053978" secsSinceReport="755715" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Good call, it's at Bladensburg now
<vehicle id="2640" lat="38.9231989" lon="-76.970367" secsSinceReport="23076" predictable="false" heading="-4" speedKmHr="0.0"/>
and 2628 is back online
<vehicle id="2628" lat="38.9218789" lon="-76.971275" secsSinceReport="13412" predictable="false" heading="-4" speedKmHr="0.0"/>
2627 is at the D.C. DMV station.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2627" lat="38.8765069" lon="-77.010826" secsSinceReport="183" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2528 is at Bladensburg! WOO-HOO!!
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2528" lat="38.920971" lon="-76.970398" secsSinceReport="28553" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 2605 is at Annex.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2605" lat="38.872681" lon="-76.9338609" secsSinceReport="4131" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2607 and 2627 are at Davidsonville Park & Ride.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2607" lat="38.959335" lon="-76.651337" secsSinceReport="136" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2627" lat="38.959225" lon="-76.651161" secsSinceReport="312" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 5318 is back in service. Looks like it wasn't rehabbed, given it was at Bladensburg for only a couple of months.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="5318" routeTag="70" dirTag="70_70_0" lat="38.893581" lon="-77.023811" secsSinceReport="120" predictable="true" heading="360" speedKmHr="6.408"/>
</body>
Speaking of Bladensburg, 6003 is back online; it's there.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6003" lat="38.922512" lon="-76.971237" secsSinceReport="2625" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2603 back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2603" lat="38.843395" lon="-77.054329" secsSinceReport="148" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2646 takes its place at Blade.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2646" routeTag="16K" lat="38.923119" lon="-76.970436" secsSinceReport="3094" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Quote from: RideOn5905
2646 takes its place at Blade.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2646" routeTag="16K" lat="38.923119" lon="-76.970436" secsSinceReport="3094" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
ugh this whole bus rehab prediction thing obviously isn't working in my favor
Yeah, first 3006 and now this... And I almost forgot: 2592 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2592" routeTag="4H" lat="38.9214399" lon="-76.971062" secsSinceReport="102499" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
3946-49 are at Royal.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3946" routeTag="W6" lat="38.811275" lon="-77.0430219" secsSinceReport="8800" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3947" lat="38.811302" lon="-77.042603" secsSinceReport="11487" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3948" lat="38.811329" lon="-77.042572" secsSinceReport="7768" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3949" routeTag="W6" lat="38.811413" lon="-77.042671" secsSinceReport="7503" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2626 is back online
<vehicle id="2626" lat="38.921249" lon="-76.970818" secsSinceReport="124238" predictable="false" heading="135" speedKmHr="9.648"/>
Quote from: RideOn5905 on June 13, 2012, 08:38:14 PM
3946-49 are at Royal.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3946" routeTag="W6" lat="38.811275" lon="-77.0430219" secsSinceReport="8800" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3947" lat="38.811302" lon="-77.042603" secsSinceReport="11487" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3948" lat="38.811329" lon="-77.042572" secsSinceReport="7768" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3949" routeTag="W6" lat="38.811413" lon="-77.042671" secsSinceReport="7503" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
speaking of which, around 2 pm I saw 3950 at Medical Center Station with "Special" on the sign
2544 is back online, it's at Bladensburg
<vehicle id="2544" lat="38.923145" lon="-76.970436" secsSinceReport="163" predictable="false" heading="-4" speedKmHr="0.0"/>
2628 and 2727 are at Davidsonville P&R.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2628" lat="38.959335" lon="-76.651375" secsSinceReport="625" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2727" lat="38.959278" lon="-76.651237" secsSinceReport="84" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2592 is back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2592" routeTag="38B" lat="38.891464" lon="-77.084221" secsSinceReport="3763" predictable="true" heading="75" speedKmHr="8.028"/>
</body>
3941-45 are at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3941" lat="38.922981" lon="-76.969177" secsSinceReport="99" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3942" routeTag="W2" lat="38.923119" lon="-76.968857" secsSinceReport="156" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3943" lat="38.920448" lon="-76.962769" secsSinceReport="4188" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3944" lat="38.9223209" lon="-76.969139" secsSinceReport="49" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3945" routeTag="M8" lat="38.923035" lon="-76.968933" secsSinceReport="1567" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
Several more Orion VII 3G's are online; the highest of which is 3063.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3063" lat="38.940746" lon="-76.878281" secsSinceReport="37548" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 6407 is at the back of some lot in Elkridge, MD (In fact, I think it's the same one that 2503 appeared in last year).
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6407" lat="39.181919" lon="-76.762886" secsSinceReport="10581" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2627 is back at FMR
<vehicle id="2627" lat="38.842926" lon="-77.053879" secsSinceReport="22" predictable="false" heading="-4" speedKmHr="0.0" />
2682 now awaits rehab at Bladensburg
<vehicle id="2682" lat="38.923061" lon="-76.970436" secsSinceReport="5104" predictable="false" heading="-4" speedKmHr="0.0" />
and 2684 is back online
<vehicle id="2684" lat="38.9230919" lon="-76.970787" secsSinceReport="2510" predictable="false" heading="-4" speedKmHr="0.0" />
6137 and 6167 are at Western.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6137" routeTag="36" lat="38.961506" lon="-77.0855179" secsSinceReport="185510" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6167" lat="38.958839" lon="-77.085617" secsSinceReport="232" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
6114 and 6155 are back at Annex.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6114" lat="38.872215" lon="-76.933472" secsSinceReport="10496" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6155" routeTag="A2" dirTag="A2_A2_0" lat="38.859509" lon="-76.995148" secsSinceReport="58" predictable="true" heading="213" speedKmHr="0.0"/>
</body>
Taking their place at Montgomery: 6176, 6177, and 6182!
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6176" lat="39.047142" lon="-77.107635" secsSinceReport="26398" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6177" routeTag="D14" lat="39.046646" lon="-77.1079479" secsSinceReport="11205" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6182" lat="39.046318" lon="-77.107597" secsSinceReport="5785" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
EDIT: And what do you know... 2605 and 2637 are back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2605" routeTag="25B" dirTag="25B_25B_1" lat="38.808361" lon="-77.13308" secsSinceReport="62" predictable="true" heading="180" speedKmHr="17.676"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2637" lat="38.841442" lon="-77.054153" secsSinceReport="77869" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
DOUBLE EDIT: And now we've got 2606 at Bladensburg...
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2606" lat="38.921852" lon="-76.971031" secsSinceReport="36481" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Wow, so it looks like everything is back to normal, with the exception of Montgomery having some of the ex-Landover 6100s that is also now ex-Annex. I really wish I didn't screw up that shot of 6114 on the L2 but at least I got a decent shot of 6155 on the Z11.
Also, might as well use the rest of this post to show which branded buses are still not rehabbed or in the process:
38B: 2600
Pike Ride: 2647, 2648, 2649, 2654, 2655, 2658, 2659, 2660, 2663, 2666
9S: 2671, 2673
REX: 2674, 2677, 2679, 2680, 2685
And the rest: (not counting the branded buses)
C Gas+: 2503, 2507, 2510, 2514, 2515, 2519, 2520, 2521, 2522, 2524, 2525, 2534, 2537, 2541, 2542, 2549, 2552, 2555, 2557, 2563, 2565, 2569, 2572, 2573, 2579, 2585, 2586, 2595, 2599, 2602, 2609, 2611, 2613, 2614, 3005, 3008, 3009, 3011, 3014, 3020, 3024, 3026, 3030, 3033
JD: 2616, 2625, 2635, 2636, 2704, 2716, 2718, 2721, 2728, 2729
Total: (why? because I'm bored)
2503, 2507, 2510, 2514, 2515, 2519, 2520, 2521, 2522, 2524, 2525, 2534, 2537, 2541, 2542, 2549, 2552, 2555, 2557, 2563, 2565, 2569, 2572, 2573, 2579, 2585, 2586, 2595, 2599, 2600, 2602, 2609, 2611, 2613, 2614, 2616, 2625, 2635, 2636, 2647, 2648, 2649, 2654, 2655, 2658, 2659, 2660, 2663, 2666, 2671, 2673, 2674, 2677, 2679, 2680, 2685, 2704, 2716, 2718, 2721, 2728, 2729, 3005, 3008, 3009, 3011, 3014, 3020, 3024, 3026, 3030, 3033
That's a total of 72 buses
NextBus has reset; wonderful. Orion V check!
Landover: 4210-13, 4242, 4244-46, 4248-49, 4252-53, 4255, 4261, 4263-65, 4317-18, 4321, 4327, 4358, 4360-62, 4364, 4366, 4371-72, 4378, 4391, 4393, 4395, 4397-98 (Total: 35)
Montgomery: 4202-05, 4235, 4238-40, 4258-60, 4266-73, 4305, 4308, 4314, 4324, 4328, 4334, 4338, 4342-45, 4348, 4356 (Total: 32)
Northern: 4274-77, 4280-93, 4295, 4297-99 (Total: 22)
Royal: 4399, 4401-12 (Total: 13)
West Ox: 4207, 4216-18, 4220-27, 4230-34, 4237, 4247, 4256-57, 4311, 4387-89 (Total: 25)
Grand total: 127 in service
And for the rest: 6167 is at Annex.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6167" routeTag="W4" dirTag="W4_W4v1_1" lat="38.908047" lon="-76.934837" secsSinceReport="47" predictable="true" heading="120" speedKmHr="0.0"/>
</body>
6127 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6127" lat="38.9210009" lon="-76.970467" secsSinceReport="10676" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And a number of D40LFRs are offline for some reason: 6105 (except this one; this one is obvious), 6121, 6124, 6126, 6131, 6137, 6140, 6157, 6164, 6181, 6201, 6206 (see 6105), and 6215.
And so are a few DE40LF(R)s: 6009, 6018, 6027, 6030, and 6046. Also 2613.
3941-3945 have moved to Bladensburg
<vehicle id="3941" routeTag="B8" dirTag="B8_B8_0" lat="38.923584" lon="-76.988358" secsSinceReport="65" predictable="true" heading="70" speedKmHr="0.0" />
<vehicle id="3942" routeTag="W2" lat="38.922401" lon="-76.969032" secsSinceReport="40" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="3943" routeTag="D8" lat="38.922596" lon="-76.969528" secsSinceReport="15589" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="3944" routeTag="D4" lat="38.924603" lon="-76.96991" secsSinceReport="43029" predictable="false" heading="-4" speedKmHr="0.0" />
<vehicle id="3945" routeTag="H6" dirTag="H6_H6_1" lat="38.925564" lon="-76.972359" secsSinceReport="44" predictable="true" heading="90" speedKmHr="40.212" />
3949 on the 18E, I know it's been mentioned before that some of these have moved to Royal, but it's interesting to see them in VA many years after they left VA
<vehicle id="3949" routeTag="18E" dirTag="18E_18E_0" lat="38.867153" lon="-77.054047" secsSinceReport="251" predictable="true" heading="195" speedKmHr="11.232" />
Also 6439 is back at Western
<vehicle id="6439" routeTag="39" dirTag="39_39_0" lat="38.878925" lon="-76.982437" secsSinceReport="46" predictable="true" heading="105" speedKmHr="45.036" />
2685 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2685" lat="38.923256" lon="-76.970299" secsSinceReport="88187" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2606 is back at FMR, alongside 3946 and 2613 (back online, obviously)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2606" lat="38.843834" lon="-77.053596" secsSinceReport="12162" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="3946" routeTag="18E" lat="38.843311" lon="-77.053978" secsSinceReport="6398" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="2613" lat="38.85973" lon="-77.05265" secsSinceReport="2824" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And 3904 is on the 87.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3904" routeTag="87" dirTag="87_87_0" lat="39.011284" lon="-76.909607" secsSinceReport="127" predictable="true" heading="218" speedKmHr="0.0"/>
</body>
2563 has no data.
2199 and 2200 are now Royal buses (saw 2200 on the 10A in person today)
<vehicle id="2199" routeTag="21A" dirTag="21A_21A_0" lat="38.84367" lon="-77.082047" secsSinceReport="85" predictable="true" heading="210" speedKmHr="88.488"/>
<vehicle id="2200" routeTag="10A" dirTag="10A_10A_0" lat="38.860611" lon="-77.059441" secsSinceReport="19" predictable="true" heading="270" speedKmHr="0.0"/>
2229 at Montgomery
<vehicle id="2229" lat="39.047115" lon="-77.109032" secsSinceReport="573" predictable="false" heading="-4" speedKmHr="0.0"/>
6578-6585 are now at West Ox (I saw 6579 at Ballston today)
<vehicle id="6578" routeTag="28X" dirTag="28X_28X_1" lat="38.878952" lon="-77.166153" secsSinceReport="45" predictable="true" heading="120" speedKmHr="43.452"/>
<vehicle id="6579" routeTag="1A" dirTag="1A_1A_1" lat="38.869797" lon="-77.1735379" secsSinceReport="116" predictable="true" heading="75" speedKmHr="43.452"/>
<vehicle id="6580" routeTag="1C" dirTag="1C_1C_0" lat="38.86105" lon="-77.342796" secsSinceReport="146" predictable="true" heading="315" speedKmHr="67.572"/>
<vehicle id="6581" routeTag="29N" dirTag="29N_29N_0" lat="38.803631" lon="-77.053978" secsSinceReport="99" predictable="true" heading="270" speedKmHr="35.388"/>
<vehicle id="6582" routeTag="17G" dirTag="17G_17G_0" lat="38.867264" lon="-77.06147" secsSinceReport="230" predictable="true" heading="270" speedKmHr="59.544"/>
<vehicle id="6583" lat="38.849419" lon="-77.378746" secsSinceReport="151" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6584" lat="38.849388" lon="-77.378815" secsSinceReport="430" predictable="false" heading="-4" speedKmHr="0.0"/>
<vehicle id="6585" routeTag="2C" lat="38.8825" lon="-77.115898" secsSinceReport="10465" predictable="true" heading="330" speedKmHr="27.324"/>
and no data showing for 2179, 2217, 2223, and 2231
4286 on the 79
<predictions agencyTitle="WMATA Washington" routeTitle="79 GEORGIA AVE LIMITED" routeTag="79" stopTitle="Georgia Ave + New Hampshire Ave F/S" stopTag="15236">
<direction title="North to Silver Spring Station">
<prediction epochTime="1340400804802" seconds="470" minutes="7" isDeparture="false" dirTag="79_79_1" vehicle="2821" block="B787" tripTag="4308714" />
<prediction epochTime="1340400982533" seconds="648" minutes="10" isDeparture="false" dirTag="79_79_1" vehicle="
4286" block="
B777" tripTag="4308713" />
2607 is back at FMR. (EDIT: It was red. Metro, do you think maybe you could make up your mind?)
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2607" lat="38.842789" lon="-77.053841" secsSinceReport="10931" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2636 is next in line.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2636" lat="38.923145" lon="-76.970436" secsSinceReport="63" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
Speaking of the new scheme, I wonder if 2665 will be getting MetroExtra logos...
2562 on the 5A.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2562" routeTag="5A" dirTag="5A_5A_0" lat="38.949516" lon="-77.346687" secsSinceReport="60" predictable="true" heading="105" speedKmHr="109.404"/>
</body>
2650 and 2676 are at Davidsonville Park & Ride.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2650" lat="38.959034" lon="-76.6507419" secsSinceReport="35" predictable="false" heading="120" speedKmHr="12.852"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2676" lat="38.959309" lon="-76.651306" secsSinceReport="200" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2634 is at Bladensburg.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2634" routeTag="23A" lat="38.9223209" lon="-76.971207" secsSinceReport="8612" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2678 finally back online; it is indeed back at Four Mile Run.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2678" lat="38.841717" lon="-77.053703" secsSinceReport="6495" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
2563 and 3034 (I doubt they'll MetroExtra the baby buses) are both also back online.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2563" lat="38.8437539" lon="-77.053734" secsSinceReport="13" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="3034" lat="38.921936" lon="-76.971062" secsSinceReport="182036" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And one more thing I forgot: 6127 is back at Annex.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="6127" lat="38.872162" lon="-76.933052" secsSinceReport="9788" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
5306 is finally back!
<vehicle id="5306" routeTag="70" dirTag="70_70_1" lat="38.994259" lon="-77.029167" secsSinceReport="640" predictable="true" heading="103" speedKmHr="0.0"/>
As for the Orion VIIs, nothing seems to have come back to service yet...
...until now. 2650 and 2727 are back at FMR.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2650" lat="38.8437539" lon="-77.054153" secsSinceReport="109" predictable="false" heading="270" speedKmHr="8.028"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2727" lat="38.843971" lon="-77.053703" secsSinceReport="61" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
And taking their respective place in line: 2625 and 2635.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2625" lat="38.923832" lon="-76.9702609" secsSinceReport="8494" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2635" routeTag="16G" lat="38.923832" lon="-76.970299" secsSinceReport="8503" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
So it looks like no more non-rehabbed 2620s and 2630s will be running the streets. Besides that, looks like they're REALLY trying to get the JDs out of the way, seeing as there's only one 40-ft non-JD in rehab (2528).
Also, we should definitely be in the 1600s now, there are three new rehabs back and only two spaces left in the 1500s, I look forward to getting them rehab numbers on Thursday
2676 is back at FMR
<vehicle id="2676" lat="38.842926" lon="-77.05265" secsSinceReport="677" predictable="false" heading="-4" speedKmHr="0.0"/>
and replacing it at Bladensburg is fellow REX bus 2674
<vehicle id="2674" lat="38.923172" lon="-76.970436" secsSinceReport="310" predictable="false" heading="-4" speedKmHr="0.0"/>
2628 has also returned.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2628" lat="38.843063" lon="-77.0539469" secsSinceReport="32" predictable="false" heading="-4" speedKmHr="1.584"/>
</body>
2654 has taken its place in line.
<body copyright="All data copyright WMATA Washington 2012.">
<vehicle id="2654" lat="38.923309" lon="-76.970436" secsSinceReport="9352" predictable="false" heading="-4" speedKmHr="0.0"/>
</body>
"Apache Tomcat/6.0.29 - Error Report"
Don't tell me they've changed the URL again...
Nextbus is trying to get agencies to release their public feeds. Metro is being so blunt about using their API which is spotty at best instead of doing it through Nextbus.
Great, just great, back to the dark ages we go...
I really hope this can get resolved soon, the dark ages was no fun
Now this isn't as good as Nextbus, but here's a link for y'all to look at, under "routeID" you can put a route and it will show what buses are on it, otherwise if you leave it blank, it will show every bus in the system that's running.
http://api.wmata.com/Bus.svc/BusPositions?routeId=&api_key=etgnvtnbpnpj32s8ztdjsujf
That said, it looks like 2626 is back from rehab
<BusPosition><DateTime>2012-07-14T16:19:08</DateTime><Deviation>-1.25</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.883244</Lat><Lon>-77.136688</Lon><RouteID>2C</RouteID><TripEndTime>1753-01-01T16:25:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>4046_22</TripID><TripStartTime>1753-01-01T15:39:00</TripStartTime><VehicleID>2626</VehicleID></BusPosition>
2725 is back
<BusPosition><DateTime>2012-07-15T18:46:01</DateTime><Deviation>-2.53</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.870373</Lat><Lon>-77.154221</Lon><RouteID>28A</RouteID><TripEndTime>1753-01-01T19:15:00</TripEndTime><TripHeadsign>KING ST STATION</TripHeadsign><TripID>3991_23</TripID><TripStartTime>1753-01-01T18:10:00</TripStartTime><VehicleID>2725</VehicleID></BusPosition>
so it looks like 4324 is back at Montgomery
<DateTime>2012-07-17T22:34:17</DateTime><Deviation>-38.57</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.055943</Lat><Lon>-77.082222</Lon><RouteID>C2v2</RouteID><TripEndTime>1753-01-01T21:56:00</TripEndTime><TripHeadsign>RANDOLPH RD & PARKLAWN DR</TripHeadsign><TripID>12244_21</TripID><TripStartTime>1753-01-01T20:49:00</TripStartTime><VehicleID>4324</VehicleID>
Also, about the Orion VIIs, let's do a roll call of the unrehabbed ones that are in service right now. The ones not listed may be just sitting at FMR, have a non-working GPS for now, or have gone to Bburg to replace the recent rehabs. So here goes, those buses not in rehab yet (for sure) are as follows:
2507, 2510, 2519, 2520, 2522, 2524, 2549, 2552, 2563, 2569, 2572, 2573, 2579, 2595, 2600, 2614, 2616, 2648, 2649, 2655, 2658, 2660, 2663, 2666, 2673, 2677, 2721, 2729, 3005, 3008, 3009, 3014, 3020, 3026
6181....back at Annex??
<BusPosition><DateTime>2012-07-20T07:58:26</DateTime><Deviation>0.68</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.828217</Lat><Lon>-77.017265</Lon><RouteID>A4</RouteID><TripEndTime>1753-01-01T08:23:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>17873_21</TripID><TripStartTime>1753-01-01T07:55:00</TripStartTime><VehicleID>6181</VehicleID></BusPosition>
5301 is finally back in service
<BusPosition><DateTime>2012-07-20T12:49:56</DateTime><Deviation>-73.95</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.977184</Lat><Lon>-77.026436</Lon><RouteID>70</RouteID><TripEndTime>1753-01-01T11:46:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>15121_21</TripID><TripStartTime>1753-01-01T10:48:00</TripStartTime><VehicleID>5301</VehicleID></BusPosition>
2684 is back from rehab
<BusPosition><DateTime>2012-07-22T10:42:56</DateTime><Deviation>-0.27</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.720772</Lat><Lon>-77.125099</Lon><RouteID>R99</RouteID><TripEndTime>1753-01-01T10:55:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>3538_23</TripID><TripStartTime>1753-01-01T10:06:00</TripStartTime><VehicleID>2684</VehicleID></BusPosition>
2629 is back at FMR
<BusPosition><DateTime>2012-07-29T17:58:06</DateTime><Deviation>1.83</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.903622</Lat><Lon>-77.05307</Lon><RouteID>38B</RouteID><TripEndTime>1753-01-01T18:26:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>4163_23</TripID><TripStartTime>1753-01-01T17:53:00</TripStartTime><VehicleID>2629</VehicleID></BusPosition>
2544 and 2641 are back in service
<BusPosition><DateTime>2012-08-02T19:29:45</DateTime><Deviation>-11.03</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.874249</Lat><Lon>-77.10585</Lon><RouteID>23A</RouteID><TripEndTime>1753-01-01T19:52:00</TripEndTime><TripHeadsign>CRYSTAL CITY</TripHeadsign><TripID>11626_21</TripID><TripStartTime>1753-01-01T18:26:00</TripStartTime><VehicleID>2544</VehicleID></BusPosition>
<BusPosition><DateTime>2012-08-02T19:25:37</DateTime><Deviation>1.65</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.902218</Lat><Lon>-77.038612</Lon><RouteID>38B</RouteID><TripEndTime>1753-01-01T19:28:00</TripEndTime><TripHeadsign>FARRAGUT SQUARE</TripHeadsign><TripID>11327_21</TripID><TripStartTime>1753-01-01T18:45:00</TripStartTime><VehicleID>2641</VehicleID></BusPosition>
3006 and 3034 are back from rehab (not sure if 3006 was rehabbed since it seemed like it was done too quick, who knows)
<BusPosition><DateTime>2012-08-06T08:37:26</DateTime><Deviation>-11.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.937252</Lat><Lon>-76.991753</Lon><RouteID>H6</RouteID><TripEndTime>1753-01-01T08:28:00</TripEndTime><TripHeadsign>BROOKLAND STATION</TripHeadsign><TripID>6748_21</TripID><TripStartTime>1753-01-01T07:58:00</TripStartTime><VehicleID>3006</VehicleID></BusPosition>
<BusPosition><DateTime>2012-08-06T08:37:17</DateTime><Deviation>-3.87</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.913986</Lat><Lon>-77.207489</Lon><RouteID>3T</RouteID><TripEndTime>1753-01-01T08:46:00</TripEndTime><TripHeadsign>TYSONS CORNER</TripHeadsign><TripID>8814_21</TripID><TripStartTime>1753-01-01T08:20:00</TripStartTime><VehicleID>3034</VehicleID></BusPosition>
Roll call 8/6/12 for unrehabbed buses still in service:
2520, 2521, 2522, 2525, 2534, 2537, 2541, 2542, 2555, 2563, 2579, 2585, 2595, 2600, 2609, 2611, 2614, 2647, 2648, 2649, 2658, 2666, 2671, 2673, 2677, 2679, 2680, 2704, 2716, 2729, 3008, 3009, 3014, 3020, 3024
Well, I'm back. The reason why I've been so inactive is because, for me, at least, this site has been marked as dangerous. (Once I got access to the main site, I get bombarded with attacks; thank God for Norton 360) Does anyone else have this problem? In regards to which buses are replacing all these at Bladensburg, I've found out at least one: 2616. I've been using this site to keep track of buses:
http://api.wmata.com/maps/view
So about a week or so ago, I was checking out the 3A, at it showed 2616 as being on that route, but with the bus indicator showing it at Bladensburg division. I think 2718 might be there as well, since I haven't seen it since I started using this new URL around mid-July. (Then again, the same was true for 2659, and I saw it on the 16Y about 20 minutes ago) Oh well; those are the breaks.
^^^yeah recently every time I try to go on this site, it says it's been reported as an attack site (I use Firefox)
I did mention in a post earlier that 2616 was at Bladensburg, I saw it there in person. I also thought 2659 was there, but I saw it active again on the API earlier today.
I also mentioned in another post that I was using this link (http://api.wmata.com/Bus.svc/BusPositions?routeId=&includingVariations=true&lat=38.878586&lon=-76.989626&radius=50000&api_key=etgnvtnbpnpj32s8ztdjsujf) for tracking buses, it should show every bus that's running on any route. Of course, this whole WMATA's API thing isn't nearly as great as Nextbus, I really hope they resolve that whole issue soon.
3012 is on the 86
<BusPosition><DateTime>2012-08-10T19:50:34</DateTime><Deviation>-18.15</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.965275</Lat><Lon>-76.95787</Lon><RouteID>86</RouteID><TripEndTime>1753-01-01T20:11:00</TripEndTime><TripHeadsign>CALVERTON</TripHeadsign><TripID>4858_21</TripID><TripStartTime>1753-01-01T19:05:00</TripStartTime><VehicleID>3012</VehicleID></BusPosition>
6169 on the 92.
<BusPosition><DateTime>2012-08-10T20:06:11</DateTime><Deviation>-4.27</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.891327</Lat><Lon>-76.995003</Lon><RouteID>92v1</RouteID><TripEndTime>1753-01-01T20:30:00</TripEndTime><TripHeadsign>CONGRESS HEIGHTS STATION</TripHeadsign><TripID>15398_21</TripID><TripStartTime>1753-01-01T19:35:00</TripStartTime><VehicleID>6169</VehicleID></BusPosition>
3017 back in service; on the H6.
<BusPosition><DateTime>2012-08-11T15:38:46</DateTime><Deviation>-1.03</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.933899</Lat><Lon>-76.994026</Lon><RouteID>H6</RouteID><TripEndTime>1753-01-01T15:38:00</TripEndTime><TripHeadsign>BROOKLAND STATION</TripHeadsign><TripID>2993_22</TripID><TripStartTime>1753-01-01T15:09:00</TripStartTime><VehicleID>3017</VehicleID></BusPosition>
Also, I haven't heard from 3011 or 3026 since 3006 and 3034 returned; maybe they're next in line for rehab?
2670 is back, and as usual with all new rehabs, it's on the 38B
<BusPosition><DateTime>2012-08-13T08:31:50</DateTime><Deviation>-6.90</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.885662</Lat><Lon>-77.110855</Lon><RouteID>38B</RouteID><TripEndTime>1753-01-01T08:32:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>11250_21</TripID><TripStartTime>1753-01-01T07:49:00</TripStartTime><VehicleID>2670</VehicleID></BusPosition>
6469 at Montgomery?
<BusPosition><DateTime>2012-08-17T19:15:06</DateTime><Deviation>0.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.04541</Lat><Lon>-77.107948</Lon><RouteID>S2</RouteID><TripEndTime>1753-01-01T19:18:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>16388_21</TripID><TripStartTime>1753-01-01T18:27:00</TripStartTime><VehicleID>6469</VehicleID></BusPosition>
For the record, I've been keeping track of non-rehabbed Orion VIIs. So far:
2586 and 2718 have not been online in over a month. Unless you've seen either of them, I'm marking them as in rehab.
2602 and 2721 have not been online in 2-3 weeks. These are definitely more questionable, but they may have also fled the coop.
3011 and 3026 have not been online in the past week or two. I'm fairly certain that 3026 is being rehabbed since it hasn't been seen since 3034's return, and the same might be true for 3011.
And for this week, the only 3 buses I have not seen online are 2557, 2648, and 2659.
So here's what I think the list of rehab replacements has been:
2626/2725 - 2586/2718
2651/2684 - 2616/2721
2629/2641 - 2602
3006/3034 - 3011/3026
3017/2670 - 2659
Quote from: RideOn5905
6469 at Montgomery?
<BusPosition><DateTime>2012-08-17T19:15:06</DateTime><Deviation>0.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.04541</Lat><Lon>-77.107948</Lon><RouteID>S2</RouteID><TripEndTime>1753-01-01T19:18:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>16388_21</TripID><TripStartTime>1753-01-01T18:27:00</TripStartTime><VehicleID>6469</VehicleID></BusPosition>
For the record, I've been keeping track of non-rehabbed Orion VIIs. So far:
2586 and 2718 have not been online in over a month. Unless you've seen either of them, I'm marking them as in rehab.
2602 and 2721 have not been online in 2-3 weeks. These are definitely more questionable, but they may have also fled the coop.
3011 and 3026 have not been online in the past week or two. I'm fairly certain that 3026 is being rehabbed since it hasn't been seen since 3034's return, and the same might be true for 3011.
And for this week, the only 3 buses I have not seen online are 2557, 2648, and 2659.
So here's what I think the list of rehab replacements has been:
2626/2725 - 2586/2718
2651/2684 - 2616/2721
2629/2641 - 2602
3006/3034 - 3011/3026
3017/2670 - 2659
Yeah unfortunately I've been having the same feeling with 2586 and 2602, I had 2586 marked as the last to be rehabbed in my predictions, 2602 was one of the last 5 I think too. Also, I haven't heard from 2563 in a while either. Looks like I gotta redo my predictions yet
again
Quote from: NewFlyer9736BCT on August 17, 2012, 09:39:42 PM
Quote from: RideOn5905
6469 at Montgomery?
<BusPosition><DateTime>2012-08-17T19:15:06</DateTime><Deviation>0.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.04541</Lat><Lon>-77.107948</Lon><RouteID>S2</RouteID><TripEndTime>1753-01-01T19:18:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>16388_21</TripID><TripStartTime>1753-01-01T18:27:00</TripStartTime><VehicleID>6469</VehicleID></BusPosition>
For the record, I've been keeping track of non-rehabbed Orion VIIs. So far:
2586 and 2718 have not been online in over a month. Unless you've seen either of them, I'm marking them as in rehab.
2602 and 2721 have not been online in 2-3 weeks. These are definitely more questionable, but they may have also fled the coop.
3011 and 3026 have not been online in the past week or two. I'm fairly certain that 3026 is being rehabbed since it hasn't been seen since 3034's return, and the same might be true for 3011.
And for this week, the only 3 buses I have not seen online are 2557, 2648, and 2659.
So here's what I think the list of rehab replacements has been:
2626/2725 - 2586/2718
2651/2684 - 2616/2721
2629/2641 - 2602
3006/3034 - 3011/3026
3017/2670 - 2659
Yeah unfortunately I've been having the same feeling with 2586 and 2602, I had 2586 marked as the last to be rehabbed in my predictions, 2602 was one of the last 5 I think too. Also, I haven't heard from 2563 in a while either. Looks like I gotta redo my predictions yet again
I saw 2563 earlier this week. Also if it turns out to be 2648 at Bladensburg, I'm switching my last John Deere rehab to 2673.
EDIT: Well, what do you know; 2705 is back at Four Mile Run.
<BusPosition><DateTime>2012-08-18T18:30:05</DateTime><Deviation>-10.10</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.792713</Lat><Lon>-77.049637</Lon><RouteID>
10B</RouteID><TripEndTime>1753-01-01T18:20:00</TripEndTime><TripHeadsign>
HUNTING POINT</TripHeadsign><TripID>5437_22</TripID><TripStartTime>1753-01-01T17:22:00</TripStartTime><VehicleID>
2705</VehicleID></BusPosition>
2643 is also back at FMR.
<BusPosition><DateTime>2012-08-20T10:30:33</DateTime><Deviation>4.43</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.703171</Lat><Lon>-77.150124</Lon><RouteID>R99</RouteID><TripEndTime>1753-01-01T10:35:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9627_21</TripID><TripStartTime>1753-01-01T09:40:00</TripStartTime><VehicleID>2643</VehicleID></BusPosition>
EDIT: And here's 2563, still at FMR.
<BusPosition><DateTime>2012-08-20T10:44:35</DateTime><Deviation>-11.07</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.841251</Lat><Lon>-77.114914</Lon><RouteID>25B</RouteID><TripEndTime>1753-01-01T11:10:00</TripEndTime><TripHeadsign>VAN DORN ST STATION</TripHeadsign><TripID>11700_21</TripID><TripStartTime>1753-01-01T10:09:00</TripStartTime><VehicleID>2563</VehicleID></BusPosition>
Here we are at the end of the week. And among all unrehabbed Orion VIIs, the following ones have not been seen this week:
2557*
2648*
2680
2728
3008
* - haven't been seen last week, either
I don't know what's up with 2659; as soon as I write it off, it shows up in service. This week, it was on the 16G on Tuesday, I believe.
At any rate, methinks that the first three buses listed here have replaced 2643, 2670, and 2705 at Bladensburg. What a bummer; on my list, 2557 was in the final five, 2648 was the last Deere, and 2680 was the last REX bus. At any rate, here's my revised final 10 rehab list in order: 2572, 3009, 2599, 2649, 2521, 2542, 2673, 3020, 2507, 2537.
2640 is back at FMR.
<BusPosition><DateTime>2012-08-27T10:10:30</DateTime><Deviation>0.42</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.903702</Lat><Lon>-77.069344</Lon><RouteID>38B</RouteID><TripEndTime>1753-01-01T10:30:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>11214_21</TripID><TripStartTime>1753-01-01T09:55:00</TripStartTime><VehicleID>2640</VehicleID></BusPosition>
2528 is also back, on none other than the 38B
<BusPosition><DateTime>2012-08-28T07:15:51</DateTime><Deviation>-1.00</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.901501</Lat><Lon>-77.038651</Lon><RouteID>38B</RouteID><TripEndTime>1753-01-01T07:15:00</TripEndTime><TripHeadsign>FARRAGUT SQUARE</TripHeadsign><TripID>11244_21</TripID><TripStartTime>1753-01-01T06:38:00</TripStartTime><VehicleID>2528</VehicleID></BusPosition>
Also, to go in detail with the final few to be rehabbed (now that 2586, 2602, and 3026 may be getting rehabbed, might as well rearrange the list)
Last 10 to be rehabbed (in this order): 2716, 2525, 2569, 2658, 2534, 2599, 2563, 2579, 2555, 2520
Last REX: 2677
Last 2700: 2716
Last JD: 2658
Last 3000: 3014
2644 and 2682 are back
<BusPosition><DateTime>2012-09-04T10:42:18</DateTime><Deviation>-1.72</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.868256</Lat><Lon>-77.065353</Lon><RouteID>16G</RouteID><TripEndTime>1753-01-01T10:44:00</TripEndTime><TripHeadsign>PENTAGON CITY STATION</TripHeadsign><TripID>10463_21</TripID><TripStartTime>1753-01-01T10:27:00</TripStartTime><VehicleID>2644</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-04T10:32:45</DateTime><Deviation>2.23</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.703144</Lat><Lon>-77.150124</Lon><RouteID>R99</RouteID><TripEndTime>1753-01-01T10:35:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9627_21</TripID><TripStartTime>1753-01-01T09:40:00</TripStartTime><VehicleID>2682</VehicleID></BusPosition>
according to the system, the following buses are still unrehabbed and in service: (those not listed may or may not be in rehab, who knows)
Last update: 9/6/12
2510, 2514, 2515, 2520, 2521, 2522, 2524, 2534, 2549, 2563, 2565, 2569, 2572, 2573, 2579, 2585, 2595, 2600, 2609, 2611, 2614, 2655, 2660, 2663, 2666, 2671, 2673, 2677, 2679, 2704, 3005, 3008, 3009, 3014, 3033
I've narrowed it down to five unseen buses:
2649
2658
2659*
2716*
2729*
*-haven't been seen last week, either
Based on what I saw in person yesterday and what I'm finding on the API, here's what's still unrehabbed:
2503, 2507, 2510, 2514, 2519, 2520, 2521, 2522, 2524, 2525, 2534, 2541, 2542, 2549, 2555, 2563, 2569, 2572, 2585, 2595, 2599, 2600, 2609, 2611, 2647, 2658, 2660, 2663, 2666, 2671, 2673, 2679, 3005, 3008, 3009, 3020, 3030, 3033
Quote from: NewFlyer9736BCT on September 11, 2012, 08:46:03 AM
Based on what I saw in person yesterday and what I'm finding on the API, here's what's still unrehabbed:
2503, 2507, 2510, 2514, 2519, 2520, 2521, 2522, 2524, 2525, 2534, 2541, 2542, 2549, 2555, 2563, 2569, 2572, 2585, 2595, 2599, 2600, 2609, 2611, 2647, 2658, 2660, 2663, 2666, 2671, 2673, 2679, 3005, 3008, 3009, 3020, 3030, 3033
Ah, so 2658 is still around. It looks like 2649 has most likely joined the above starred buses (2659, 2716, 2729) at Bladensburg.
In other news, 2646 back at FMR.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Culmore</DirectionText><Minutes>10</Minutes><RouteID>16B</RouteID><VehicleID>
2646</VehicleID></NextBusPrediction>
2685 is also back
<BusPosition><DateTime>2012-09-12T13:31:04</DateTime><Deviation>-9.47</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.78339</Lat><Lon>-77.075577</Lon><RouteID>R99</RouteID><TripEndTime>1753-01-01T13:54:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9647_21</TripID><TripStartTime>1753-01-01T13:07:00</TripStartTime><VehicleID>2685</VehicleID></BusPosition>
At this point, 2677 might be in rehab since I haven't seen it at all this week, and since 2679 is already repowered, not sure when that will go to rehab
We have a legit new rehab! 2660 is at Bladensburg.
<BusPosition><DateTime>2012-09-17T16:36:21</DateTime><Deviation>-2.78</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.923172</Lat><Lon>-76.970367</Lon><RouteID>16A</RouteID><TripEndTime>1753-01-01T16:53:00</TripEndTime><TripHeadsign/><TripID>10311_21</TripID><TripStartTime>1753-01-01T16:00:00</TripStartTime><VehicleID>2660</VehicleID></BusPosition>
2636 and 2674 are back
<BusPosition><DateTime>2012-09-19T08:49:15</DateTime><Deviation>-13.70</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.879944</Lat><Lon>-77.031548</Lon><RouteID>38B</RouteID><TripEndTime>1753-01-01T08:56:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>11212_21</TripID><TripStartTime>1753-01-01T08:13:00</TripStartTime><VehicleID>2636</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-19T08:52:18</DateTime><Deviation>-1.92</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.717087</Lat><Lon>-77.132446</Lon><RouteID>R99</RouteID><TripEndTime>1753-01-01T09:03:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9579_21</TripID><TripStartTime>1753-01-01T08:15:00</TripStartTime><VehicleID>2674</VehicleID></BusPosition>
According to the API; 2655, 2658, 2666, 2671, and 2673 are still around. As for 2647, 2663, and 2704, they could just be off duty this morning. Now that I think about it, I can't believe it's come down to this few amount of JDs now...
Other buses still in service unrehabbed, according to the API and what I saw in person:
2503, 2507, 2510, 2514, 2515, 2519, 2521, 2522, 2524, 2525, 2534, 2541, 2542, 2552, 2563, 2565, 2569, 2572, 2573, 2579, 2595, 2600, 2609, 2611, 2613, 2614, 3008, 3009, 3020, 3030
2625 is back
<BusPosition><DateTime>2012-09-22T18:00:22</DateTime><Deviation>-2.48</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.856209</Lat><Lon>-77.111069</Lon><RouteID>16G</RouteID><TripEndTime>1753-01-01T18:09:00</TripEndTime><TripHeadsign/><TripID>5001_22</TripID><TripStartTime>1753-01-01T17:40:00</TripStartTime><VehicleID>2625</VehicleID></BusPosition>
Update 9/24/12:
2635 is also back
<BusPosition><DateTime>2012-09-24T09:30:04</DateTime><Deviation>-1.20</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.862148</Lat><Lon>-77.088806</Lon><RouteID>16J</RouteID><TripEndTime>1753-01-01T09:53:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>10195_21</TripID><TripStartTime>1753-01-01T09:15:00</TripStartTime><VehicleID>2635</VehicleID></BusPosition>
Northern and Royal appear to be trading 2100s, with Northern also getting the leftover 3900s.
Here are the ones for Royal:
<BusPosition><DateTime>2012-09-24T12:04:34</DateTime><Deviation>-8.15</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.844467</Lat><Lon>-77.296707</Lon><RouteID>29K</RouteID><TripEndTime>1753-01-01T12:02:00</TripEndTime><TripHeadsign>GEORGE MASON UNIVERSITY</TripHeadsign><TripID>19824_21</TripID><TripStartTime>1753-01-01T10:45:00</TripStartTime><VehicleID>2159</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T12:05:51</DateTime><Deviation>-3.82</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.800606</Lat><Lon>-77.047997</Lon><RouteID>10A</RouteID><TripEndTime>1753-01-01T12:07:00</TripEndTime><TripHeadsign>HUNTING POINT</TripHeadsign><TripID>20095_21</TripID><TripStartTime>1753-01-01T11:25:00</TripStartTime><VehicleID>2154</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T12:05:00</DateTime><Deviation>1.32</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.870178</Lat><Lon>-77.152542</Lon><RouteID>28A</RouteID><TripEndTime>1753-01-01T12:49:00</TripEndTime><TripHeadsign>KING ST STATION</TripHeadsign><TripID>19721_21</TripID><TripStartTime>1753-01-01T11:30:00</TripStartTime><VehicleID>2149</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T11:56:07</DateTime><Deviation>3.83</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.831486</Lat><Lon>-77.11747</Lon><RouteID>7M</RouteID><TripEndTime>1753-01-01T12:00:00</TripEndTime><TripHeadsign>MARK CENTER</TripHeadsign><TripID>19489_21</TripID><TripStartTime>1753-01-01T11:45:00</TripStartTime><VehicleID>2150</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T12:05:04</DateTime><Deviation>0.38</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.831379</Lat><Lon>-77.059616</Lon><RouteID>10B</RouteID><TripEndTime>1753-01-01T12:42:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>19957_21</TripID><TripStartTime>1753-01-01T11:45:00</TripStartTime><VehicleID>2156</VehicleID></BusPosition>
Here are the ones for Northern:
<BusPosition><DateTime>2012-09-24T12:05:47</DateTime><Deviation>-2.27</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.985214</Lat><Lon>-77.026573</Lon><RouteID>70</RouteID><TripEndTime>1753-01-01T12:10:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>15093_21</TripID><TripStartTime>1753-01-01T11:12:00</TripStartTime><VehicleID>2189</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T12:03:46</DateTime><Deviation>5.10</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.892757</Lat><Lon>-77.025734</Lon><RouteID>S2</RouteID><TripEndTime>1753-01-01T12:09:00</TripEndTime><TripHeadsign>FEDERAL TRIANGLE</TripHeadsign><TripID>16357_21</TripID><TripStartTime>1753-01-01T11:15:00</TripStartTime><VehicleID>2179</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T11:56:20</DateTime><Deviation>-3.70</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.93277</Lat><Lon>-77.027237</Lon><RouteID>H8</RouteID><TripEndTime>1753-01-01T12:22:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>15869_21</TripID><TripStartTime>1753-01-01T11:43:00</TripStartTime><VehicleID>3947</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T12:04:17</DateTime><Deviation>2.17</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.937416</Lat><Lon>-77.032806</Lon><RouteID>53</RouteID><TripEndTime>1753-01-01T12:33:00</TripEndTime><TripHeadsign>MCPHERSON SQUARE</TripHeadsign><TripID>14702_21</TripID><TripStartTime>1753-01-01T11:44:00</TripStartTime><VehicleID>2184</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-24T12:02:33</DateTime><Deviation>2.67</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.894711</Lat><Lon>-77.028084</Lon><RouteID>S2</RouteID><TripEndTime>1753-01-01T12:52:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>16323_21</TripID><TripStartTime>1753-01-01T12:02:00</TripStartTime><VehicleID>2182</VehicleID></BusPosition>
I also saw 3946 on the G2, but it wasn't there anymore when I went to copy this down. In other news, 3937 is still alive!
<BusPosition><DateTime>2012-09-24T12:03:59</DateTime><Deviation>-0.22</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.866302</Lat><Lon>-76.943451</Lon><RouteID>P99</RouteID><TripEndTime>1753-01-01T12:10:00</TripEndTime><TripHeadsign>SHUTTLE</TripHeadsign><TripID>17214_21</TripID><TripStartTime>1753-01-01T12:00:00</TripStartTime><VehicleID>3937</VehicleID></BusPosition>
And dating from last week, there are still 3 Orion VIIs that haven't been in service: 2599, 2647, and 2704.
6178, 6185 and 6189 are now apparently at Landover
<BusPosition><DateTime>2012-09-25T20:54:24</DateTime><Deviation>-7.30</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.997917</Lat><Lon>-76.909569</Lon><RouteID>G16</RouteID><TripEndTime>1753-01-01T21:25:00</TripEndTime><TripHeadsign>NEW CARROLLTON STATION</TripHeadsign><TripID>2460_21</TripID><TripStartTime>1753-01-01T20:42:00</TripStartTime><VehicleID>6178</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-25T20:57:40</DateTime><Deviation>0.27</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.890862</Lat><Lon>-76.853783</Lon><RouteID>C22v1</RouteID><TripEndTime>1753-01-01T21:04:00</TripEndTime><TripHeadsign>ADDISON RD STATION</TripHeadsign><TripID>1636_21</TripID><TripStartTime>1753-01-01T20:21:00</TripStartTime><VehicleID>6185</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-25T20:58:29</DateTime><Deviation>0.50</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.836849</Lat><Lon>-76.952553</Lon><RouteID>P12v1</RouteID><TripEndTime>1753-01-01T21:31:00</TripEndTime><TripHeadsign>EASTOVER</TripHeadsign><TripID>2865_21</TripID><TripStartTime>1753-01-01T20:25:00</TripStartTime><VehicleID>6189</VehicleID></BusPosition>
Update: 6177, 80, 82, 86, 87, and 88 have also joined the move
<BusPosition><DateTime>2012-09-27T08:37:40</DateTime><Deviation>-3.22</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.971874</Lat><Lon>-76.744759</Lon><RouteID>B24</RouteID><TripEndTime>1753-01-01T09:08:00</TripEndTime><TripHeadsign>NEW CARROLLTON STATION</TripHeadsign><TripID>1379_21</TripID><TripStartTime>1753-01-01T08:25:00</TripStartTime><VehicleID>6177</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:33:06</DateTime><Deviation>-10.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.839874</Lat><Lon>-76.976456</Lon><RouteID>P12</RouteID><TripEndTime>1753-01-01T09:10:00</TripEndTime><TripHeadsign>ADDISON RD STATION</TripHeadsign><TripID>2790_21</TripID><TripStartTime>1753-01-01T08:00:00</TripStartTime><VehicleID>6180</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:35:45</DateTime><Deviation>-9.83</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.948196</Lat><Lon>-76.872887</Lon><RouteID>84</RouteID><TripEndTime>1753-01-01T08:26:00</TripEndTime><TripHeadsign>NEW CARROLLTON STATION</TripHeadsign><TripID>23_21</TripID><TripStartTime>1753-01-01T07:40:00</TripStartTime><VehicleID>6182</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:35:40</DateTime><Deviation>0.35</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.963486</Lat><Lon>-76.900047</Lon><RouteID>F4</RouteID><TripEndTime>1753-01-01T09:31:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>2116_21</TripID><TripStartTime>1753-01-01T08:23:00</TripStartTime><VehicleID>6186</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:36:55</DateTime><Deviation>3.40</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.964176</Lat><Lon>-76.937813</Lon><RouteID>F4</RouteID><TripEndTime>1753-01-01T09:18:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>2064_21</TripID><TripStartTime>1753-01-01T08:10:00</TripStartTime><VehicleID>6187</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:37:16</DateTime><Deviation>-4.37</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.94817</Lat><Lon>-76.873062</Lon><RouteID>B24</RouteID><TripEndTime>1753-01-01T08:33:00</TripEndTime><TripHeadsign>NEW CARROLLTON STATION</TripHeadsign><TripID>1368_21</TripID><TripStartTime>1753-01-01T07:50:00</TripStartTime><VehicleID>6188</VehicleID></BusPosition>
Just updated my previous post with more 6100s moving to Landover.
In addition to that, 4327 is in Landover and 4333 in Royal
<BusPosition><DateTime>2012-09-27T08:34:44</DateTime><Deviation>-1.00</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.915966</Lat><Lon>-76.915627</Lon><RouteID>F1</RouteID><TripEndTime>1753-01-01T08:34:00</TripEndTime><TripHeadsign>CHEVERLY STATION</TripHeadsign><TripID>1970_21</TripID><TripStartTime>1753-01-01T07:41:00</TripStartTime><VehicleID>4327</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:33:40</DateTime><Deviation>-4.70</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.868805</Lat><Lon>-77.052895</Lon><RouteID>8X</RouteID><TripEndTime>1753-01-01T08:29:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>19533_21</TripID><TripStartTime>1753-01-01T07:59:00</TripStartTime><VehicleID>4333</VehicleID></BusPosition>
And now, here's another round of Bussian Roulette!
6408, 6409, 6410, 6412, 6413, 6414, 6416, 6419, and 6420 have moved to Montgomery
<BusPosition><DateTime>2012-09-27T08:43:12</DateTime><Deviation>-24.20</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.017223</Lat><Lon>-77.006378</Lon><RouteID>C4</RouteID><TripEndTime>1753-01-01T08:57:00</TripEndTime><TripHeadsign>TWINBROOK STATION</TripHeadsign><TripID>12107_21</TripID><TripStartTime>1753-01-01T07:48:00</TripStartTime><VehicleID>6408</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:41:08</DateTime><Deviation>-2.25</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.035702</Lat><Lon>-77.194397</Lon><RouteID>T2</RouteID><TripEndTime>1753-01-01T09:09:00</TripEndTime><TripHeadsign>FRIENDSHIP HEIGHTS STATION</TripHeadsign><TripID>13773_21</TripID><TripStartTime>1753-01-01T08:19:00</TripStartTime><VehicleID>6409</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:37:46</DateTime><Deviation>-14.43</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.9617</Lat><Lon>-77.084816</Lon><RouteID>N4</RouteID><TripEndTime>1753-01-01T09:07:00</TripEndTime><TripHeadsign>FARRAGUT SQUARE</TripHeadsign><TripID>13204_21</TripID><TripStartTime>1753-01-01T08:23:00</TripStartTime><VehicleID>6410</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:42:49</DateTime><Deviation>-16.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>39.057896</Lat><Lon>-77.05027</Lon><RouteID>C8</RouteID><TripEndTime>1753-01-01T09:20:00</TripEndTime><TripHeadsign>COLLEGE PARK STATION</TripHeadsign><TripID>12338_21</TripID><TripStartTime>1753-01-01T08:05:00</TripStartTime><VehicleID>6412</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:42:43</DateTime><Deviation>-1.88</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.994617</Lat><Lon>-77.027489</Lon><RouteID>J4</RouteID><TripEndTime>1753-01-01T09:00:00</TripEndTime><TripHeadsign>BETHESDA STATION</TripHeadsign><TripID>11996_21</TripID><TripStartTime>1753-01-01T08:08:00</TripStartTime><VehicleID>6413</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:44:15</DateTime><Deviation>-4.30</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.978256</Lat><Lon>-76.927353</Lon><RouteID>J4</RouteID><TripEndTime>1753-01-01T08:40:00</TripEndTime><TripHeadsign>COLLEGE PARK STATION</TripHeadsign><TripID>12005_21</TripID><TripStartTime>1753-01-01T07:51:00</TripStartTime><VehicleID>6414</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:30:56</DateTime><Deviation>-0.03</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.085339</Lat><Lon>-77.145996</Lon><RouteID>T2</RouteID><TripEndTime>1753-01-01T08:31:00</TripEndTime><TripHeadsign>ROCKVILLE STATION</TripHeadsign><TripID>13828_21</TripID><TripStartTime>1753-01-01T07:45:00</TripStartTime><VehicleID>6416</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:43:07</DateTime><Deviation>0.63</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.05883</Lat><Lon>-76.997559</Lon><RouteID>C8</RouteID><TripEndTime>1753-01-01T09:22:00</TripEndTime><TripHeadsign>WHITE FLINT STATION</TripHeadsign><TripID>12387_21</TripID><TripStartTime>1753-01-01T08:07:00</TripStartTime><VehicleID>6419</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:43:38</DateTime><Deviation>-9.48</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.985294</Lat><Lon>-77.095177</Lon><RouteID>J4</RouteID><TripEndTime>1753-01-01T08:35:00</TripEndTime><TripHeadsign>BETHESDA STATION</TripHeadsign><TripID>11991_21</TripID><TripStartTime>1753-01-01T07:43:00</TripStartTime><VehicleID>6420</VehicleID></BusPosition>
6447, 6448, 6450, and 6451 have moved to Northern
<BusPosition><DateTime>2012-09-27T08:43:54</DateTime><Deviation>-3.92</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.901363</Lat><Lon>-77.030708</Lon><RouteID>S9</RouteID><TripEndTime>1753-01-01T08:40:00</TripEndTime><TripHeadsign>MCPHERSON SQUARE</TripHeadsign><TripID>16682_21</TripID><TripStartTime>1753-01-01T08:00:00</TripStartTime><VehicleID>6447</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:42:52</DateTime><Deviation>-4.37</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.940662</Lat><Lon>-77.036552</Lon><RouteID>S9</RouteID><TripEndTime>1753-01-01T09:02:00</TripEndTime><TripHeadsign>MCPHERSON SQUARE</TripHeadsign><TripID>16741_21</TripID><TripStartTime>1753-01-01T08:22:00</TripStartTime><VehicleID>6448</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:40:44</DateTime><Deviation>-3.17</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.990025</Lat><Lon>-77.033684</Lon><RouteID>S9</RouteID><TripEndTime>1753-01-01T09:17:00</TripEndTime><TripHeadsign>MCPHERSON SQUARE</TripHeadsign><TripID>16714_21</TripID><TripStartTime>1753-01-01T08:37:00</TripStartTime><VehicleID>6450</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:42:59</DateTime><Deviation>0.97</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.946106</Lat><Lon>-77.036552</Lon><RouteID>S9</RouteID><TripEndTime>1753-01-01T09:10:00</TripEndTime><TripHeadsign>MCPHERSON SQUARE</TripHeadsign><TripID>16701_21</TripID><TripStartTime>1753-01-01T08:30:00</TripStartTime><VehicleID>6451</VehicleID></BusPosition>
6375, 6379, 6387, 6388, 6389, 6390, 6391, 6393, 6431 and 6436 moved to West Ox (6435 is still Northern, and the others in between show no data, so they may have moved as well)
<BusPosition><DateTime>2012-09-27T09:16:41</DateTime><Deviation>-8.85</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.872959</Lat><Lon>-77.248161</Lon><RouteID>2B</RouteID><TripEndTime>1753-01-01T09:38:00</TripEndTime><TripHeadsign>FAIR OAKS MALL</TripHeadsign><TripID>3554_21</TripID><TripStartTime>1753-01-01T08:30:00</TripStartTime><VehicleID>6375</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:02:46</DateTime><Deviation>-6.32</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.768513</Lat><Lon>-77.171265</Lon><RouteID>18R</RouteID><TripEndTime>1753-01-01T08:57:00</TripEndTime><TripHeadsign>FRANCONIA - SPRINGFIELD</TripHeadsign><TripID>4020_21</TripID><TripStartTime>1753-01-01T08:15:00</TripStartTime><VehicleID>6379</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:17:00</DateTime><Deviation>-7.07</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.899632</Lat><Lon>-77.187889</Lon><RouteID>28T</RouteID><TripEndTime>1753-01-01T09:10:00</TripEndTime><TripHeadsign>WEST FALLS CHURCH STATION</TripHeadsign><TripID>3832_21</TripID><TripStartTime>1753-01-01T08:35:00</TripStartTime><VehicleID>6387</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:16:13</DateTime><Deviation>-7.57</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.898891</Lat><Lon>-77.266922</Lon><RouteID>2T</RouteID><TripEndTime>1753-01-01T09:38:00</TripEndTime><TripHeadsign>TYSONS CORNER</TripHeadsign><TripID>3637_21</TripID><TripStartTime>1753-01-01T08:48:00</TripStartTime><VehicleID>6388</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:14:46</DateTime><Deviation>-16.78</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.868832</Lat><Lon>-77.052895</Lon><RouteID>17H</RouteID><TripEndTime>1753-01-01T08:58:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>4163_21</TripID><TripStartTime>1753-01-01T08:15:00</TripStartTime><VehicleID>6389</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:09:19</DateTime><Deviation>-31.38</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.869381</Lat><Lon>-77.053383</Lon><RouteID>17H</RouteID><TripEndTime>1753-01-01T08:38:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>4250_21</TripID><TripStartTime>1753-01-01T07:55:00</TripStartTime><VehicleID>6390</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:15:24</DateTime><Deviation>-16.37</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.811138</Lat><Lon>-77.235001</Lon><RouteID>17F</RouteID><TripEndTime>1753-01-01T09:06:00</TripEndTime><TripHeadsign>KINGS PARK WEST</TripHeadsign><TripID>4236_21</TripID><TripStartTime>1753-01-01T08:40:00</TripStartTime><VehicleID>6391</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T09:14:23</DateTime><Deviation>-1.20</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.874496</Lat><Lon>-77.231567</Lon><RouteID>1C</RouteID><TripEndTime>1753-01-01T09:54:00</TripEndTime><TripHeadsign>FAIR OAKS MALL</TripHeadsign><TripID>3269_21</TripID><TripStartTime>1753-01-01T09:10:00</TripStartTime><VehicleID>6393</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:42:18</DateTime><Deviation>0.98</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.882748</Lat><Lon>-77.171791</Lon><RouteID>28X</RouteID><TripEndTime>1753-01-01T09:04:00</TripEndTime><TripHeadsign>TYSONS CORNER</TripHeadsign><TripID>3879_21</TripID><TripStartTime>1753-01-01T08:10:00</TripStartTime><VehicleID>6431</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-27T08:43:06</DateTime><Deviation>-10.10</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.916325</Lat><Lon>-77.221107</Lon><RouteID>28X</RouteID><TripEndTime>1753-01-01T08:33:00</TripEndTime><TripHeadsign>TYSONS CORNER</TripHeadsign><TripID>3889_21</TripID><TripStartTime>1753-01-01T07:39:00</TripStartTime><VehicleID>6436</VehicleID></BusPosition>
And...for the first time since they started service, the original hybrids (6000s) may be making a move as well. 6015 is at Landover, no data was showing for 6016 and 6017 but they might be there too. 6018 and up are still at Montgomery
<BusPosition><DateTime>2012-09-27T09:16:55</DateTime><Deviation>-3.62</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.967503</Lat><Lon>-76.919128</Lon><RouteID>R12</RouteID><TripEndTime>1753-01-01T09:43:00</TripEndTime><TripHeadsign>GREENBELT STATION</TripHeadsign><TripID>2908_21</TripID><TripStartTime>1753-01-01T08:56:00</TripStartTime><VehicleID>6015</VehicleID></BusPosition>
Ooooh but it's not over yet...
Some, if not all of the 4400s have moved to Bladensburg
<BusPosition><DateTime>2012-09-28T12:28:14</DateTime><Deviation>-1.53</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.896252</Lat><Lon>-77.020378</Lon><RouteID>D6</RouteID><TripEndTime>1753-01-01T12:52:00</TripEndTime><TripHeadsign>STADIUM - ARMORY</TripHeadsign><TripID>5892_21</TripID><TripStartTime>1753-01-01T11:35:00</TripStartTime><VehicleID>4403</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-28T12:29:06</DateTime><Deviation>6.92</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.973194</Lat><Lon>-76.971733</Lon><RouteID>R2</RouteID><TripEndTime>1753-01-01T12:46:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>7122_21</TripID><TripStartTime>1753-01-01T12:05:00</TripStartTime><VehicleID>4405</VehicleID></BusPosition>
6405 and 6423 at Montgomery
<BusPosition><DateTime>2012-09-28T12:24:54</DateTime><Deviation>-5.92</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.045109</Lat><Lon>-77.065323</Lon><RouteID>Q4</RouteID><TripEndTime>1753-01-01T12:43:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>13578_21</TripID><TripStartTime>1753-01-01T11:55:00</TripStartTime><VehicleID>6405</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-28T12:17:39</DateTime><Deviation>3.20</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.966404</Lat><Lon>-77.07708</Lon><RouteID>L2</RouteID><TripEndTime>1753-01-01T12:21:00</TripEndTime><TripHeadsign>CHEVY CHASE CIRCLE</TripHeadsign><TripID>13098_21</TripID><TripStartTime>1753-01-01T11:40:00</TripStartTime><VehicleID>6423</VehicleID></BusPosition>
6374 remains at Montgomery (as well as 6371 but that was this morning and now there's no data for it)
<BusPosition><DateTime>2012-09-28T12:27:50</DateTime><Deviation>-2.05</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.081684</Lat><Lon>-77.160172</Lon><RouteID>T2</RouteID><TripEndTime>1753-01-01T12:30:00</TripEndTime><TripHeadsign>ROCKVILLE STATION</TripHeadsign><TripID>13761_21</TripID><TripStartTime>1753-01-01T11:45:00</TripStartTime><VehicleID>6374</VehicleID></BusPosition>
4257, 6511, 6512 and 6513 at Northern
<BusPosition><DateTime>2012-09-28T12:28:13</DateTime><Deviation>-18.12</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.94894</Lat><Lon>-77.036552</Lon><RouteID>S2</RouteID><TripEndTime>1753-01-01T12:25:00</TripEndTime><TripHeadsign>FEDERAL TRIANGLE</TripHeadsign><TripID>16211_21</TripID><TripStartTime>1753-01-01T11:31:00</TripStartTime><VehicleID>4257</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-28T22:13:18</DateTime><Deviation>-19.90</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.896828</Lat><Lon>-76.995003</Lon><RouteID>92v1</RouteID><TripEndTime>1753-01-01T22:24:00</TripEndTime><TripHeadsign>CONGRESS HEIGHTS STATION</TripHeadsign><TripID>15684_21</TripID><TripStartTime>1753-01-01T21:29:00</TripStartTime><VehicleID>6511</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-28T12:27:18</DateTime><Deviation>-8.45</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.930462</Lat><Lon>-77.032875</Lon><RouteID>52v1</RouteID><TripEndTime>1753-01-01T12:52:00</TripEndTime><TripHeadsign>L`ENFANT PLAZA STATION</TripHeadsign><TripID>14781_21</TripID><TripStartTime>1753-01-01T12:06:00</TripStartTime><VehicleID>6512</VehicleID></BusPosition>
<BusPosition><DateTime>2012-09-28T12:28:39</DateTime><Deviation>1.28</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.889843</Lat><Lon>-76.922661</Lon><RouteID>96</RouteID><TripEndTime>1753-01-01T13:41:00</TripEndTime><TripHeadsign>MCLEAN GARDENS</TripHeadsign><TripID>16019_21</TripID><TripStartTime>1753-01-01T12:27:00</TripStartTime><VehicleID>6513</VehicleID></BusPosition>
3768 at Western
<BusPosition><DateTime>2012-09-28T22:09:34</DateTime><Deviation>-53.67</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.911098</Lat><Lon>-77.044601</Lon><RouteID>D2</RouteID><TripEndTime>1753-01-01T21:16:00</TripEndTime><TripHeadsign>DUPONT CIRCLE</TripHeadsign><TripID>21661_21</TripID><TripStartTime>1753-01-01T20:58:00</TripStartTime><VehicleID>3768</VehicleID></BusPosition>
At long last, we have a returning bus: 2654!
<BusPosition><DateTime>2012-10-04T16:27:00</DateTime><Deviation>-7.25</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.865753</Lat><Lon>-77.074738</Lon><RouteID>16Bc</RouteID><TripEndTime>1753-01-01T16:48:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>9861_31</TripID><TripStartTime>1753-01-01T16:10:00</TripStartTime><VehicleID>2654</VehicleID></BusPosition>
And so far, only two buses have not shown up this week: 2655 and 2673. I was going to include 3020, but I checked, and as I type this, it's on the Bladensburg employee shuttle.
2602 has also returned from what was most likely rehab.
<BusPosition><DateTime>2012-10-06T20:49:44</DateTime><Deviation>-3.02</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.856457</Lat><Lon>-77.053032</Lon><RouteID>9A</RouteID><TripEndTime>1753-01-01T20:51:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>4614_32</TripID><TripStartTime>1753-01-01T20:22:00</TripStartTime><VehicleID>2602</VehicleID></BusPosition>
...And so has 2718.
<BusPosition><DateTime>2012-10-08T18:26:27</DateTime><Deviation>3.93</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.805553</Lat><Lon>-77.251312</Lon><RouteID>17G</RouteID><TripEndTime>2012-10-08T18:51:00</TripEndTime><TripHeadsign>GEORGE MASON UNIVERSITY</TripHeadsign><TripID>6848_34</TripID><TripStartTime>2012-10-08T18:05:00</TripStartTime><VehicleID>2718</VehicleID></BusPosition>
And now we've got 3011 returning.
<BusPosition><DateTime>2012-10-09T16:57:44</DateTime><Deviation>-0.18</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.937691</Lat><Lon>-77.023148</Lon><RouteID>H8</RouteID><TripEndTime>2012-10-09T17:13:00</TripEndTime><TripHeadsign>MT PLEASANT</TripHeadsign><TripID>7143_31</TripID><TripStartTime>2012-10-09T16:34:00</TripStartTime><VehicleID>3011</VehicleID></BusPosition>
Do not adjust your monitors. Yes, this even shocked me.
vehicleID=3081, block=W423, dirTag=42_42_1
prediction=9:58 or 11:43:01PM
2616 is back. considering it's on the 16Y, it might be the missing link 1619 and therefore may be blue
<BusPosition><DateTime>2012-10-15T08:40:33</DateTime><Deviation>-5.03</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.890614</Lat><Lon>-77.076523</Lon><RouteID>16Y</RouteID><TripEndTime>2012-10-15T08:57:00</TripEndTime><TripHeadsign>MCPHERSON SQUARE</TripHeadsign><TripID>11382_31</TripID><TripStartTime>2012-10-15T08:12:00</TripStartTime><VehicleID>2616</VehicleID></BusPosition>
2557 is also back.
<BusPosition><DateTime>2012-10-15T16:20:36</DateTime><Deviation>-1.23</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.868256</Lat><Lon>-77.054047</Lon><RouteID>22A</RouteID><TripEndTime>2012-10-15T16:58:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>9633_31</TripID><TripStartTime>2012-10-15T16:19:00</TripStartTime><VehicleID>2557</VehicleID></BusPosition>
Oh, and for the record, the only two buses I didn't see last week were 2671 and 3014, so those two have probably begun rehab.
Gonna be a tight ride on the 39. 3007 is on there.
(http://farm9.staticflickr.com/8196/8100964251_99d2225644_b.jpg)
2586 and 3026 are back
<BusPosition><DateTime>2012-10-24T08:38:42</DateTime><Deviation>0.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>LOOP</DirectionText><Lat>38.852444</Lat><Lon>-77.051811</Lon><RouteID>9S</RouteID><TripEndTime>2012-10-24T08:52:00</TripEndTime><TripHeadsign>POTOMAC YARD-CRYSTAL CITY STATION</TripHeadsign><TripID>9479_31</TripID><TripStartTime>2012-10-24T08:35:00</TripStartTime><VehicleID>2586</VehicleID></BusPosition>
<BusPosition><DateTime>2012-10-24T08:31:36</DateTime><Deviation>-30.80</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.79483</Lat><Lon>-77.053284</Lon><RouteID>9A</RouteID><TripEndTime>2012-10-24T08:07:00</TripEndTime><TripHeadsign>HUNTINGTON STATION N</TripHeadsign><TripID>9324_31</TripID><TripStartTime>2012-10-24T07:33:00</TripStartTime><VehicleID>3026</VehicleID></BusPosition>
After doing my weekly tally of unrehabbed buses, only two have not shown up so far: 2595 and 3008. This is it - only Cummins-powered buses remain. It appears we have entered the homestretch in the Orion VII rehab session.
^^^I'm guessing this means that 2663, 2666, and 2673 haven't been around either? Well looks like this is it, no more JDs on the Orion VIIs :(
But anyways, here's a couple of moves:
4318, 6402, and 6403 to Montgomery
<BusPosition><DateTime>2012-10-26T07:21:13</DateTime><Deviation>-0.17</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.074394</Lat><Lon>-77.164055</Lon><RouteID>T2</RouteID><TripEndTime>2012-10-26T07:28:00</TripEndTime><TripHeadsign>ROCKVILLE STATION</TripHeadsign><TripID>12893_31</TripID><TripStartTime>2012-10-26T06:45:00</TripStartTime><VehicleID>4318</VehicleID></BusPosition>
<BusPosition><DateTime>2012-10-26T07:18:02</DateTime><Deviation>-1.75</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.075771</Lat><Lon>-77.003265</Lon><RouteID>C8</RouteID><TripEndTime>2012-10-26T07:52:00</TripEndTime><TripHeadsign>WHITE FLINT STATION</TripHeadsign><TripID>11801_31</TripID><TripStartTime>2012-10-26T06:34:00</TripStartTime><VehicleID>6402</VehicleID></BusPosition>
<BusPosition><DateTime>2012-10-26T07:21:51</DateTime><Deviation>-2.93</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.988071</Lat><Lon>-77.076698</Lon><RouteID>J2v2</RouteID><TripEndTime>2012-10-26T07:51:00</TripEndTime><TripHeadsign>MONTGOMERY MALL</TripHeadsign><TripID>11918_31</TripID><TripStartTime>2012-10-26T07:05:00</TripStartTime><VehicleID>6403</VehicleID></BusPosition>
Nothing showing yet for 6401 so it might have moved as well.
(edit: 6399 and 6400 are still at West Ox)
Quote from: NewFlyer9736BCT on October 26, 2012, 07:29:38 AM
^^^I'm guessing this means that 2663, 2666, and 2673 haven't been around either? Well looks like this is it, no more JDs on the Orion VIIs :(
But anyways, here's a couple of moves:
4318, 6402, and 6403 to Montgomery
<BusPosition><DateTime>2012-10-26T07:21:13</DateTime><Deviation>-0.17</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.074394</Lat><Lon>-77.164055</Lon><RouteID>T2</RouteID><TripEndTime>2012-10-26T07:28:00</TripEndTime><TripHeadsign>ROCKVILLE STATION</TripHeadsign><TripID>12893_31</TripID><TripStartTime>2012-10-26T06:45:00</TripStartTime><VehicleID>4318</VehicleID></BusPosition>
<BusPosition><DateTime>2012-10-26T07:18:02</DateTime><Deviation>-1.75</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.075771</Lat><Lon>-77.003265</Lon><RouteID>C8</RouteID><TripEndTime>2012-10-26T07:52:00</TripEndTime><TripHeadsign>WHITE FLINT STATION</TripHeadsign><TripID>11801_31</TripID><TripStartTime>2012-10-26T06:34:00</TripStartTime><VehicleID>6402</VehicleID></BusPosition>
<BusPosition><DateTime>2012-10-26T07:21:51</DateTime><Deviation>-2.93</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.988071</Lat><Lon>-77.076698</Lon><RouteID>J2v2</RouteID><TripEndTime>2012-10-26T07:51:00</TripEndTime><TripHeadsign>MONTGOMERY MALL</TripHeadsign><TripID>11918_31</TripID><TripStartTime>2012-10-26T07:05:00</TripStartTime><VehicleID>6403</VehicleID></BusPosition>
Nothing showing yet for 6401 so it might have moved as well.
(edit: 6399 and 6400 are still at West Ox)
And apparently, not even
former John Deeres are spared: 2679 is at Bladensburg (which means that 2680 might be returning this weekend).
<BusPosition><DateTime>2012-10-26T13:51:46</DateTime><Deviation>0.12</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>
38.923172</Lat><Lon>
-76.970367</Lon><RouteID>R99</RouteID><TripEndTime>2012-10-26T13:54:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9222_31</TripID><TripStartTime>2012-10-26T13:07:00</TripStartTime><VehicleID>
2679</VehicleID></BusPosition>
So the mysterious 7777 is out and about today:
<BusPosition><DateTime>2012-10-29T10:54:26</DateTime><Deviation>-23.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.93948</Lat><Lon>-76.87912</Lon><RouteID>32</RouteID><TripEndTime>2012-10-29T11:05:00</TripEndTime><TripHeadsign>FRIENDSHIP HEIGHTS STATION</TripHeadsign><TripID>20851_31</TripID><TripStartTime>2012-10-29T09:30:00</TripStartTime><VehicleID>7777</VehicleID></BusPosition>
According to the API, this bus is just one of only 7 in the entire system that's running today, on routes 32, U8, 53, S2 (2 buses on this route now), 96, and H4.
EDIT - So I just noticed the coordinates on 7777, it's still in that place near CET but I guess it's just tagged on the 32.
Also, plenty more Metrobuses are now in service (not gonna count them all)
EDIT 2 - Just noticed that the coordinates of ALL buses that are up on the API show that the buses are in their respective bus divisions, so I was wrong all along. That said, with the Shepherd Pkwy buses sitting at home, we can now determine that the coords of Shep are around 38.815 lat and -77.016 lon
Metrorail/Metrobus service has returned, and with it, 2721.
<BusPosition><DateTime>2012-10-30T14:04:35</DateTime><Deviation>2.23</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.884701</Lat><Lon>-77.023323</Lon><RouteID>5A</RouteID><TripEndTime>2012-10-30T14:07:00</TripEndTime><TripHeadsign>L`ENFANT PLAZA STATION</TripHeadsign><TripID>10375_31</TripID><TripStartTime>2012-10-30T13:20:00</TripStartTime><VehicleID>2721</VehicleID></BusPosition>
So this time I monitored the unrehabbed buses for this week, and here's what hasn't been in service this week
2585
2595*
3005
3014*
*Hasn't been seen last week either
2680 is back at FMR.
<BusPosition><DateTime>2012-11-05T16:56:08</DateTime><Deviation>-13.77</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.803959</Lat><Lon>-77.056572</Lon><RouteID>R99</RouteID><TripEndTime>2012-11-05T17:36:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9276_31</TripID><TripStartTime>2012-11-05T16:40:00</TripStartTime><VehicleID>2680</VehicleID></BusPosition>
And so is 2648
<BusPosition><DateTime>2012-11-08T18:02:05</DateTime><Deviation>-30.65</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.751244</Lat><Lon>-77.083382</Lon><RouteID>R99</RouteID><TripEndTime>2012-11-08T18:00:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9261_31</TripID><TripStartTime>2012-11-08T17:04:00</TripStartTime><VehicleID>2648</VehicleID></BusPosition>
Here I am at Huntington Station, where I'm waiting for 2680, and as a bonus, 2648 will come around here too. Don't expect pics of them since it's dark out already.
Update: So I got the rehab numbers, they are in the rehab numbers thread. Also, from this week, the following buses have not been heard from, so it's possible they're about to start rehab:
2613
3030
2521 has not been on the API all week either, but last night I saw it on the 9A so I can confirm that it's still around.
2716 back at FMR.
<BusPosition><DateTime>2012-11-10T15:39:20</DateTime><Deviation>-1.93</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.89537</Lat><Lon>-77.095108</Lon><RouteID>3A</RouteID><TripEndTime>2012-11-10T15:42:00</TripEndTime><TripHeadsign>ROSSLYN STATION</TripHeadsign><TripID>4203_32</TripID><TripStartTime>2012-11-10T14:51:00</TripStartTime><VehicleID>2716</VehicleID></BusPosition>
EDIT: 2613 is still at FMR.
<BusPosition><DateTime>2012-11-13T16:43:23</DateTime><Deviation>1.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.863415</Lat><Lon>-77.08387</Lon><RouteID>16H</RouteID><TripEndTime>2012-11-13T17:05:00</TripEndTime><TripHeadsign>SKYLINE CITY</TripHeadsign><TripID>10199_31</TripID><TripStartTime>2012-11-13T16:33:00</TripStartTime><VehicleID>2613</VehicleID></BusPosition>
2659 is back from rehab
<BusPosition><DateTime>2012-11-20T16:47:19</DateTime><Deviation>-5.67</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.863937</Lat><Lon>-77.081879</Lon><RouteID>16D</RouteID><TripEndTime>2012-11-20T17:24:00</TripEndTime><TripHeadsign/><TripID>9892_31</TripID><TripStartTime>2012-11-20T16:30:00</TripStartTime><VehicleID>2659</VehicleID></BusPosition>
...as is 2729.
<BusPosition><DateTime>2012-11-20T17:37:18</DateTime><Deviation>-2.30</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.818451</Lat><Lon>-77.138016</Lon><RouteID>7W</RouteID><TripEndTime>2012-11-20T17:35:00</TripEndTime><TripHeadsign>LINCOLNIA</TripHeadsign><TripID>9114_31</TripID><TripStartTime>2012-11-20T17:10:00</TripStartTime><VehicleID>2729</VehicleID></BusPosition>
and let's not forget 2728
<BusPosition><DateTime>2012-11-21T09:51:35</DateTime><Deviation>-1.98</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.896084</Lat><Lon>-77.086426</Lon><RouteID>3A</RouteID><TripEndTime>2012-11-21T10:40:00</TripEndTime><TripHeadsign>ANNANDALE</TripHeadsign><TripID>8408_31</TripID><TripStartTime>2012-11-21T09:45:00</TripStartTime><VehicleID>2728</VehicleID></BusPosition>
wow, so it looks like 2704 will be the last one then, should be back no later than next month
2649 is back
<BusPosition><DateTime>2012-11-25T12:11:00</DateTime><Deviation>-5.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.856071</Lat><Lon>-77.139732</Lon><RouteID>16P</RouteID><TripEndTime>2012-11-25T12:08:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>3786_33</TripID><TripStartTime>2012-11-25T11:30:00</TripStartTime><VehicleID>2649</VehicleID></BusPosition>
And now we can add 2660 to the list.
<BusPosition><DateTime>2012-11-26T06:51:39</DateTime><Deviation>-2.95</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.89856</Lat><Lon>-77.118134</Lon><RouteID>3A</RouteID><TripEndTime>2012-11-26T07:00:00</TripEndTime><TripHeadsign>ROSSLYN STATION</TripHeadsign><TripID>8225_31</TripID><TripStartTime>2012-11-26T06:05:00</TripStartTime><VehicleID>2660</VehicleID></BusPosition>
2677 is back at FMR.
<BusPosition><DateTime>2012-12-03T06:58:56</DateTime><Deviation>2.33</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.723717</Lat><Lon>-77.118523</Lon><RouteID>R99</RouteID><TripEndTime>2012-12-03T07:39:00</TripEndTime><TripHeadsign>KING ST STATION</TripHeadsign><TripID>9181_31</TripID><TripStartTime>2012-12-03T06:48:00</TripStartTime><VehicleID>2677</VehicleID></BusPosition>
2521 is finally back online
<BusPosition><DateTime>2012-12-06T16:27:15</DateTime><Deviation>-3.78</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.862427</Lat><Lon>-77.087822</Lon><RouteID>16Bc</RouteID><TripEndTime>2012-12-06T16:48:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>9861_31</TripID><TripStartTime>2012-12-06T16:10:00</TripStartTime><VehicleID>2521</VehicleID></BusPosition>
2647 has made its return.
<BusPosition><DateTime>2012-12-08T17:09:39</DateTime><Deviation>-0.08</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.855686</Lat><Lon>-77.140289</Lon><RouteID>16J</RouteID><TripEndTime>2012-12-08T17:38:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>4835_32</TripID><TripStartTime>2012-12-08T17:08:00</TripStartTime><VehicleID>2647</VehicleID></BusPosition>
2655 is back too
<BusPosition><DateTime>2012-12-10T13:22:24</DateTime><Deviation>1.23</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.852581</Lat><Lon>-77.121948</Lon><RouteID>25E</RouteID><TripEndTime>2012-12-10T13:34:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>11234_31</TripID><TripStartTime>2012-12-10T12:45:00</TripStartTime><VehicleID>2655</VehicleID></BusPosition>
3014 is back in service.
<BusPosition><DateTime>2012-12-17T16:57:14</DateTime><Deviation>0.92</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.921165</Lat><Lon>-76.993607</Lon><RouteID>B8</RouteID><TripEndTime>2012-12-17T17:12:00</TripEndTime><TripHeadsign>FORT LINCOLN</TripHeadsign><TripID>6076_31</TripID><TripStartTime>2012-12-17T16:57:00</TripStartTime><VehicleID>3014</VehicleID></BusPosition>
EDIT: And so is 2671.
<BusPosition><DateTime>2012-12-20T17:26:27</DateTime><Deviation>-5.13</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.868008</Lat><Lon>-77.065773</Lon><RouteID>16F</RouteID><TripEndTime>2012-12-20T17:49:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>10320_31</TripID><TripStartTime>2012-12-20T16:55:00</TripStartTime><VehicleID>2671</VehicleID></BusPosition>
2658 has returned.
<BusPosition><DateTime>2012-12-23T14:27:26</DateTime><Deviation>-3.67</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.881454</Lat><Lon>-77.111763</Lon><RouteID>2C</RouteID><TripEndTime>2012-12-23T14:24:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>3468_33</TripID><TripStartTime>2012-12-23T13:41:00</TripStartTime><VehicleID>2658</VehicleID></BusPosition>
EDIT: And so has 2704.
<BusPosition><DateTime>2012-12-24T17:38:16</DateTime><Deviation>2.07</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.898586</Lat><Lon>-77.043587</Lon><RouteID>3Y</RouteID><TripEndTime>2012-12-24T18:11:00</TripEndTime><TripHeadsign>HARRISON ST & LEE HWY</TripHeadsign><TripID>11316_31</TripID><TripStartTime>2012-12-24T17:30:00</TripStartTime><VehicleID>2704</VehicleID></BusPosition>
6400 has moved to Montgomery
<BusPosition><DateTime>2012-12-30T14:50:16</DateTime><Deviation>0.63</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.080608</Lat><Lon>-77.142563</Lon><RouteID>Q5</RouteID><TripEndTime>2012-12-30T15:20:00</TripEndTime><TripHeadsign>WHEATON STATION</TripHeadsign><TripID>4134_13</TripID><TripStartTime>2012-12-30T14:32:00</TripStartTime><VehicleID>6400</VehicleID></BusPosition>
Also, how do you know that 2658 is red?
Since it's returned, I've only seen it on "regular" routes, usually the 3A or the 22A, and never on the 16F/Y.
EDIT: Speaking of Montgomery...
<BusPosition><DateTime>2012-12-30T15:43:10</DateTime><Deviation>-5.22</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.075054</Lat><Lon>-77.115372</Lon><RouteID>Q4</RouteID><TripEndTime>2012-12-30T15:46:00</TripEndTime><TripHeadsign>ROCKVILLE STATION</TripHeadsign><TripID>4115_13</TripID><TripStartTime>2012-12-30T15:01:00</TripStartTime><VehicleID>6462</VehicleID></BusPosition>
<BusPosition><DateTime>2012-12-30T15:35:50</DateTime><Deviation>0.03</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.046429</Lat><Lon>-77.108055</Lon><RouteID>Z8</RouteID><TripEndTime>2012-12-30T15:56:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>4446_13</TripID><TripStartTime>2012-12-30T15:19:00</TripStartTime><VehicleID>6181</VehicleID></BusPosition>
<BusPosition><DateTime>2012-12-30T15:43:52</DateTime><Deviation>-2.98</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.02055</Lat><Lon>-76.976875</Lon><RouteID>K6</RouteID><TripEndTime>2012-12-30T16:10:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>3992_13</TripID><TripStartTime>2012-12-30T15:34:00</TripStartTime><VehicleID>6176</VehicleID></BusPosition>
On Friday I saw 6176 on the C4, as well as 6186 on the F4, so they're not all back yet.
At last, Northern is joining Club Xcelsior
<BusPosition><DateTime>2012-12-30T16:54:29</DateTime><Deviation>1.52</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.936729</Lat><Lon>-77.024544</Lon><RouteID>62</RouteID><TripEndTime>2012-12-30T16:56:00</TripEndTime><TripHeadsign>GEORGIA AVE - PETWORTH</TripHeadsign><TripID>4916_13</TripID><TripStartTime>2012-12-30T16:39:00</TripStartTime><VehicleID>7197</VehicleID></BusPosition>
<BusPosition><DateTime>2012-12-30T16:28:54</DateTime><Deviation>-6.10</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.952213</Lat><Lon>-77.002876</Lon><RouteID>64</RouteID><TripEndTime>2012-12-30T16:23:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>4788_13</TripID><TripStartTime>2012-12-30T15:46:00</TripStartTime><VehicleID>7201</VehicleID></BusPosition>
7038 and 7040 have moved to Landover
<BusPosition><DateTime>2012-12-30T20:46:36</DateTime><Deviation>-5.90</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.852386</Lat><Lon>-76.858047</Lon><RouteID>J12</RouteID><TripEndTime>2012-12-30T20:42:00</TripEndTime><TripHeadsign/><TripID>428_13</TripID><TripStartTime>2012-12-30T20:18:00</TripStartTime><VehicleID>7038</VehicleID></BusPosition>
<BusPosition><DateTime>2012-12-30T16:26:00</DateTime><Deviation>-4.77</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.931229</Lat><Lon>-76.899529</Lon><RouteID>A12v4</RouteID><TripEndTime>2012-12-30T17:05:00</TripEndTime><TripHeadsign>CAPITOL HEIGHTS STATION</TripHeadsign><TripID>66_13</TripID><TripStartTime>2012-12-30T16:10:00</TripStartTime><VehicleID>7040</VehicleID></BusPosition>
Looks like Northern is getting some of their 3700s back
<BusPosition><DateTime>2012-12-30T16:24:25</DateTime><Deviation>-1.02</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.910027</Lat><Lon>-77.029167</Lon><RouteID>G2</RouteID><TripEndTime>2012-12-30T16:44:00</TripEndTime><TripHeadsign>GEORGETOWN UNIVERSITY</TripHeadsign><TripID>5214_13</TripID><TripStartTime>2012-12-30T16:10:00</TripStartTime><VehicleID>3767</VehicleID></BusPosition>
One more for Montgomery
<BusPosition><DateTime>2012-12-30T20:42:38</DateTime><Deviation>-0.18</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.045959</Lat><Lon>-77.10788</Lon><RouteID>Z8</RouteID><TripEndTime>2012-12-30T21:05:00</TripEndTime><TripHeadsign>BRIGGS CHANEY PARK & RIDE</TripHeadsign><TripID>4525_13</TripID><TripStartTime>2012-12-30T20:26:00</TripStartTime><VehicleID>6399</VehicleID></BusPosition>
2679 is back, wow that was quick
<BusPosition><DateTime>2012-12-31T10:46:27</DateTime><Deviation>-0.73</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.723301</Lat><Lon>-77.119987</Lon><RouteID>R99</RouteID><TripEndTime>2012-12-31T11:03:00</TripEndTime><TripHeadsign>FORT BELVOIR</TripHeadsign><TripID>9185_11</TripID><TripStartTime>2012-12-31T10:08:00</TripStartTime><VehicleID>2679</VehicleID></BusPosition>
4409 on the C4 (I heard 4407 was on that route the other day)
<BusPosition><DateTime>2013-01-02T10:44:06</DateTime><Deviation>-4.18</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.9837</Lat><Lon>-76.979256</Lon><RouteID>C4</RouteID><TripEndTime>2013-01-02T11:30:00</TripEndTime><TripHeadsign>TWINBROOK STATION</TripHeadsign><TripID>11573_11</TripID><TripStartTime>2013-01-02T10:25:00</TripStartTime><VehicleID>4409</VehicleID></BusPosition>
3005 is back from rehab
<BusPosition><DateTime>2013-01-07T08:45:38</DateTime><Deviation>-1.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.924793</Lat><Lon>-76.956047</Lon><RouteID>H6</RouteID><TripEndTime>2013-01-07T09:06:00</TripEndTime><TripHeadsign>BROOKLAND STATION</TripHeadsign><TripID>6989_11</TripID><TripStartTime>2013-01-07T08:36:00</TripStartTime><VehicleID>3005</VehicleID></BusPosition>
2585 has also returned.
<BusPosition><DateTime>2013-01-07T13:51:09</DateTime><Deviation>-1.15</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.857559</Lat><Lon>-77.051949</Lon><RouteID>23A</RouteID><TripEndTime>2013-01-07T13:50:00</TripEndTime><TripHeadsign>CRYSTAL CITY</TripHeadsign><TripID>11081_11</TripID><TripStartTime>2013-01-07T12:22:00</TripStartTime><VehicleID>2585</VehicleID></BusPosition>
2663 is back (saw it in person about 20 min ago, it's blue)
<BusPosition><DateTime>2013-01-10T17:07:03</DateTime><Deviation>-0.68</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.879116</Lat><Lon>-77.037636</Lon><RouteID>16Xv1</RouteID><TripEndTime>2013-01-10T17:20:00</TripEndTime><TripHeadsign>FEDERAL TRIANGLE</TripHeadsign><TripID>10347_11</TripID><TripStartTime>2013-01-10T17:02:00</TripStartTime><VehicleID>2663</VehicleID></BusPosition>
2673 is back. On the 9S just like old times.
<BusPosition><DateTime>2013-01-15T08:48:06</DateTime><Deviation>-18.70</Deviation><DirectionNum>0</DirectionNum><DirectionText>LOOP</DirectionText><Lat>38.857861</Lat><Lon>-77.051003</Lon><RouteID>9S</RouteID><TripEndTime>2013-01-15T08:46:00</TripEndTime><TripHeadsign>POTOMAC YARD-CRYSTAL CITY STATION</TripHeadsign><TripID>9499_11</TripID><TripStartTime>2013-01-15T08:29:00</TripStartTime><VehicleID>2673</VehicleID></BusPosition>
2595 has also returned.
<BusPosition><DateTime>2013-01-16T17:11:55</DateTime><Deviation>-0.85</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.932579</Lat><Lon>-77.231674</Lon><RouteID>23A</RouteID><TripEndTime>2013-01-16T18:48:00</TripEndTime><TripHeadsign>CRYSTAL CITY</TripHeadsign><TripID>11162_11</TripID><TripStartTime>2013-01-16T17:11:00</TripStartTime><VehicleID>2595</VehicleID></BusPosition>
2549 has returned to Four Mile Run.
<BusPosition><DateTime>2013-01-21T11:01:12</DateTime><Deviation>-1.07</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.886349</Lat><Lon>-77.156464</Lon><RouteID>3B</RouteID><TripEndTime>2013-01-21T11:20:00</TripEndTime><TripHeadsign>ROSSLYN STATION</TripHeadsign><TripID>8247_11</TripID><TripStartTime>2013-01-21T10:42:00</TripStartTime><VehicleID>2549</VehicleID></BusPosition>
EDIT: And so has 2666.
<BusPosition><DateTime>2013-01-21T17:22:27</DateTime><Deviation>8.67</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.918442</Lat><Lon>-77.217918</Lon><RouteID>23A</RouteID><TripEndTime>2013-01-21T17:49:00</TripEndTime><TripHeadsign>TYSONS CORNER - WESTPARK</TripHeadsign><TripID>11150_11</TripID><TripStartTime>2013-01-21T16:04:00</TripStartTime><VehicleID>2666</VehicleID></BusPosition>
3030 is back at FMR.
<BusPosition><DateTime>2013-01-27T16:04:35</DateTime><Deviation>-4.65</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.853405</Lat><Lon>-77.120308</Lon><RouteID>16P</RouteID><TripEndTime>2013-01-27T16:10:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>3016_13</TripID><TripStartTime>2013-01-27T15:30:00</TripStartTime><VehicleID>3030</VehicleID></BusPosition>
3008 is back from rehab
<BusPosition><DateTime>2013-03-04T15:24:33</DateTime><Deviation>-3.50</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.974377</Lat><Lon>-77.013557</Lon><RouteID>K2</RouteID><TripEndTime>2013-03-04T15:36:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>7385_11</TripID><TripStartTime>2013-03-04T15:20:00</TripStartTime><VehicleID>3008</VehicleID></BusPosition>
2613 replaces it at Bladensburg.
<BusPosition><DateTime>2013-03-05T08:09:31</DateTime><Deviation>-0.10</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.923256</Lat><Lon>-76.970398</Lon><RouteID>4B</RouteID><TripEndTime>2013-03-05T08:15:00</TripEndTime><TripHeadsign>SEVEN CORNERS</TripHeadsign><TripID>8495_11</TripID><TripStartTime>2013-03-05T07:40:00</TripStartTime><VehicleID>2613</VehicleID></BusPosition>
EDIT: 2614 has also returned from rehab.
<BusPosition><DateTime>2013-03-05T08:17:45</DateTime><Deviation>-8.80</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.884563</Lat><Lon>-77.064095</Lon><RouteID>7Yc</RouteID><TripEndTime>2013-03-05T08:14:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>8772_11</TripID><TripStartTime>2013-03-05T08:00:00</TripStartTime><VehicleID>2614</VehicleID></BusPosition>
2611 is back too
<BusPosition><DateTime>2013-03-06T17:05:38</DateTime><Deviation>0.97</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.863991</Lat><Lon>-77.081665</Lon><RouteID>16A</RouteID><TripEndTime>2013-03-06T17:51:00</TripEndTime><TripHeadsign/><TripID>9915_11</TripID><TripStartTime>2013-03-06T16:55:00</TripStartTime><VehicleID>2611</VehicleID></BusPosition>
Also, sources say 2563 is blue, just fyi
In other news, more Xcelsiors for Montgomery
<BusPosition><DateTime>2013-03-06T17:35:16</DateTime><Deviation>-0.27</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.994617</Lat><Lon>-77.028603</Lon><RouteID>J2</RouteID><TripEndTime>2013-03-06T17:35:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>13516_11</TripID><TripStartTime>2013-03-06T16:41:00</TripStartTime><VehicleID>7250</VehicleID></BusPosition>
I guess 3020 is back
<BusPosition><DateTime>2013-03-10T20:16:36</DateTime><Deviation>-66.63</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.920448</Lat><Lon>-76.962486</Lon><RouteID>B99</RouteID><TripEndTime>2013-03-10T19:10:00</TripEndTime><TripHeadsign>SHUTTLE</TripHeadsign><TripID>1260_13</TripID><TripStartTime>2013-03-10T19:05:00</TripStartTime><VehicleID>3020</VehicleID></BusPosition>
And so is 2521.
<BusPosition><DateTime>2013-03-11T16:39:30</DateTime><Deviation>-6.48</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.867733</Lat><Lon>-77.053703</Lon><RouteID>16Bv1</RouteID><TripEndTime>2013-03-11T16:34:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>9878_11</TripID><TripStartTime>2013-03-11T16:04:00</TripStartTime><VehicleID>2521</VehicleID></BusPosition>
As well as 3033 (seems like I'm always the one to report on the 3000s)
<BusPosition><DateTime>2013-03-11T17:24:28</DateTime><Deviation>-0.80</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.914261</Lat><Lon>-77.202133</Lon><RouteID>3T</RouteID><TripEndTime>2013-03-11T17:35:00</TripEndTime><TripHeadsign>WEST FALLS CHURCH STATION</TripHeadsign><TripID>8294_11</TripID><TripStartTime>2013-03-11T17:08:00</TripStartTime><VehicleID>3033</VehicleID></BusPosition>
Week of 3/18:
2565 is back from rehab
<BusPosition><DateTime>2013-03-18T16:29:12</DateTime><Deviation>0.15</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.831074</Lat><Lon>-77.092758</Lon><RouteID>25A</RouteID><TripEndTime>2013-03-18T16:47:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>11267_11</TripID><TripStartTime>2013-03-18T15:53:00</TripStartTime><VehicleID>2565</VehicleID></BusPosition>
2501 has apparently become a Bladensburg bus...
<BusPosition><DateTime>2013-03-21T10:26:50</DateTime><Deviation>-10.42</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.902439</Lat><Lon>-77.03228</Lon><RouteID>80</RouteID><TripEndTime>2013-03-21T11:08:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>5260_11</TripID><TripStartTime>2013-03-21T09:55:00</TripStartTime><VehicleID>2501</VehicleID></BusPosition>
And then there's... this.
<BusPosition><DateTime>2013-03-21T10:29:45</DateTime><Deviation>-43.82</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.844028</Lat><Lon>-77.054016</Lon><RouteID>F99</RouteID><TripEndTime>2013-03-21T09:46:00</TripEndTime><TripHeadsign>SHUTTLE</TripHeadsign><TripID>10490_11</TripID><TripStartTime>2013-03-21T09:39:00</TripStartTime><VehicleID>20415</VehicleID></BusPosition>
20415 I believe is one of those cutaways used mainly for employee shuttles, I know Annex has a couple as well (yes it is painted in the red local scheme, of course without saying "local")
Saw a 2000 Orion V on the 7Y the other day. Forgot the #.
Yeah, I've seen that happen before. I think Royal does one run on the 7Y each day. Oh, and 2552 is back at Four Mile Run.
<BusPosition><DateTime>2013-03-24T09:52:07</DateTime><Deviation>0.07</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.844357</Lat><Lon>-77.054047</Lon><RouteID>25A</RouteID><TripEndTime>2013-03-24T10:23:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>3644_23</TripID><TripStartTime>2013-03-24T09:40:00</TripStartTime><VehicleID>2552</VehicleID></BusPosition>
I think #2501 is still @ Four Mile run depot. I saw it late last week.
#2514-15 and #2525 sure have been out for a long time. Are they almost done?
Next to return should be 2503, 2514, 2515, 2525, 2573, 2599, and 3024. Not sure which will come first, we'll have to wait and see.
In other news, 6394 and 6396 have moved to Montgomery (most likely bringing 6395 along as well)
<BusPosition><DateTime>2013-03-25T10:32:12</DateTime><Deviation>-2.53</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.061745</Lat><Lon>-77.052368</Lon><RouteID>C8</RouteID><TripEndTime>2013-03-25T10:48:00</TripEndTime><TripHeadsign>WHITE FLINT STATION</TripHeadsign><TripID>11561_21</TripID><TripStartTime>2013-03-25T09:38:00</TripStartTime><VehicleID>6394</VehicleID></BusPosition>
<BusPosition><DateTime>2013-03-25T10:33:45</DateTime><Deviation>2.47</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.10965</Lat><Lon>-77.075821</Lon><RouteID>Y8</RouteID><TripEndTime>2013-03-25T10:47:00</TripEndTime><TripHeadsign>MEDSTAR MONTGOMERY MEDICAL CENTER</TripHeadsign><TripID>12993_21</TripID><TripStartTime>2013-03-25T09:50:00</TripStartTime><VehicleID>6396</VehicleID></BusPosition>
2504 has also become a Bladensburg bus.
<BusPosition><DateTime>2013-03-25T14:29:08</DateTime><Deviation>-2.93</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.93288</Lat><Lon>-76.993637</Lon><RouteID>H4</RouteID><TripEndTime>2013-03-25T14:27:00</TripEndTime><TripHeadsign>BROOKLAND STATION</TripHeadsign><TripID>6475_21</TripID><TripStartTime>2013-03-25T13:41:00</TripStartTime><VehicleID>2504</VehicleID></BusPosition>
6162 and 6164 have moved to Landover.
<BusPosition><DateTime>2013-03-25T14:25:58</DateTime><Deviation>-2.25</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.948719</Lat><Lon>-76.873207</Lon><RouteID>F4</RouteID><TripEndTime>2013-03-25T14:24:00</TripEndTime><TripHeadsign>NEW CARROLLTON STATION</TripHeadsign><TripID>1835_21</TripID><TripStartTime>2013-03-25T13:30:00</TripStartTime><VehicleID>6162</VehicleID></BusPosition>
<BusPosition><DateTime>2013-03-25T14:28:26</DateTime><Deviation>0.00</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.936508</Lat><Lon>-76.874924</Lon><RouteID>F13</RouteID><TripEndTime>2013-03-25T15:05:00</TripEndTime><TripHeadsign>CHEVERLY STATION</TripHeadsign><TripID>1571_21</TripID><TripStartTime>2013-03-25T14:24:00</TripStartTime><VehicleID>6164</VehicleID></BusPosition>
What? #6394-96 left West Ox? And #2501 and #2504 is at Bladensburg? What did the NOVA depots get in return (if anything)? I don't trust Bladensburg with our Orion VII CNGs. They lost a C40LF due to fire back in summer of 2011 IIRC.
Bus fires can happen to any bus. Besides that one bus lost to a fire (which btw was 2336), they still have all of their C40LFs running. Also, Bladensburg division is a heavy-repair facility, so they take good care of their buses. What does FMR get in return? That we'll have to find out. Perhaps Orion Vs, like the one you mentioned earlier on the 7Y?
So I was right about one of them at least. 2573 is back from rehab
<BusPosition><DateTime>2013-03-25T17:12:48</DateTime><Deviation>-3.80</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.886929</Lat><Lon>-77.094963</Lon><RouteID>38B</RouteID><TripEndTime>2013-03-25T17:43:00</TripEndTime><TripHeadsign>FARRAGUT SQUARE</TripHeadsign><TripID>10614_21</TripID><TripStartTime>2013-03-25T17:00:00</TripStartTime><VehicleID>2573</VehicleID></BusPosition>
Side note: It's been well over a month since my last busfan trip because of me being sick and busy with school and work, I look forward for my next trip on either Thursday or Friday (or both) and find all, if not most of the rehabs from that growing list.
Confirmed, #2521 is back in service. Spotted at Pentagon on the 7Y I believe.
2503 is back from rehab, as a Bladensburg bus
<BusPosition><DateTime>2013-03-28T08:47:16</DateTime><Deviation>-6.30</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.896305</Lat><Lon>-77.007324</Lon><RouteID>D6c</RouteID><TripEndTime>2013-03-28T09:20:00</TripEndTime><TripHeadsign>DUPONT CIRCLE</TripHeadsign><TripID>5888_21</TripID><TripStartTime>2013-03-28T08:25:00</TripStartTime><VehicleID>2503</VehicleID></BusPosition>
2502 has also made the move
<BusPosition><DateTime>2013-03-28T08:39:08</DateTime><Deviation>-18.20</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.896912</Lat><Lon>-77.007988</Lon><RouteID>97</RouteID><TripEndTime>2013-03-28T08:21:00</TripEndTime><TripHeadsign>UNION STATION</TripHeadsign><TripID>7044_21</TripID><TripStartTime>2013-03-28T07:49:00</TripStartTime><VehicleID>2502</VehicleID></BusPosition>
I saw #2505 yesterday on the 16G. Are they going to take that one next?
2514 is back, also as a Bladensburg bus apparently
<BusPosition><DateTime>2013-04-01T08:19:56</DateTime><Deviation>-1.53</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.937553</Lat><Lon>-76.958427</Lon><RouteID>83</RouteID><TripEndTime>2013-04-01T08:59:00</TripEndTime><TripHeadsign>CHERRY HILL</TripHeadsign><TripID>4718_21</TripID><TripStartTime>2013-04-01T08:05:00</TripStartTime><VehicleID>2514</VehicleID></BusPosition>
2599 is back home at FMR'
<BusPosition><DateTime>2013-04-01T08:16:50</DateTime><Deviation>3.33</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.870262</Lat><Lon>-77.152367</Lon><RouteID>4A</RouteID><TripEndTime>2013-04-01T08:29:00</TripEndTime><TripHeadsign>CULMORE</TripHeadsign><TripID>8261_21</TripID><TripStartTime>2013-04-01T07:55:00</TripStartTime><VehicleID>2599</VehicleID></BusPosition>
2555 is back at FMR.
<BusPosition><DateTime>2013-04-10T17:31:14</DateTime><Deviation>1.13</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.836685</Lat><Lon>-77.158875</Lon><RouteID>16A</RouteID><TripEndTime>2013-04-10T17:51:00</TripEndTime><TripHeadsign>ANNANDALE VIA COLUMBIA PIKE</TripHeadsign><TripID>9655_21</TripID><TripStartTime>2013-04-10T16:55:00</TripStartTime><VehicleID>2555</VehicleID></BusPosition>
2592 on the 5A.
<BusPosition><DateTime>2013-04-10T17:38:51</DateTime><Deviation>-7.63</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.884949</Lat><Lon>-77.023636</Lon><RouteID>5A</RouteID><TripEndTime>2013-04-10T18:33:00</TripEndTime><TripHeadsign>DULLES AIRPORT</TripHeadsign><TripID>10166_21</TripID><TripStartTime>2013-04-10T17:30:00</TripStartTime><VehicleID>2592</VehicleID></BusPosition>
2515 is back, seems to be Bladensburg as well
<BusPosition><DateTime>2013-04-14T12:34:24</DateTime><Deviation>-60.48</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.921387</Lat><Lon>-76.969109</Lon><RouteID>B99</RouteID><TripEndTime>2013-04-14T11:34:00</TripEndTime><TripHeadsign>SHUTTLE</TripHeadsign><TripID>1169_23</TripID><TripStartTime>2013-04-14T11:30:00</TripStartTime><VehicleID>2515</VehicleID></BusPosition>
2505 and 2506 have moved to Bladensburg
<BusPosition><DateTime>2013-04-17T17:21:54</DateTime><Deviation>-63.08</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.971821</Lat><Lon>-76.979675</Lon><RouteID>R1</RouteID><TripEndTime>2013-04-17T16:40:00</TripEndTime><TripHeadsign>ADELPHI</TripHeadsign><TripID>7253_21</TripID><TripStartTime>2013-04-17T16:08:00</TripStartTime><VehicleID>2505</VehicleID></BusPosition>
<BusPosition><DateTime>2013-04-17T17:23:13</DateTime><Deviation>-11.27</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.952679</Lat><Lon>-77.002007</Lon><RouteID>R2</RouteID><TripEndTime>2013-04-17T17:12:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>7261_21</TripID><TripStartTime>2013-04-17T16:27:00</TripStartTime><VehicleID>2506</VehicleID></BusPosition>
6371 has moved to West Ox
<BusPosition><DateTime>2013-04-17T17:29:08</DateTime><Deviation>-10.13</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.91605</Lat><Lon>-77.221909</Lon><RouteID>2T</RouteID><TripEndTime>2013-04-17T17:19:00</TripEndTime><TripHeadsign>TYSONS CORNER</TripHeadsign><TripID>3478_21</TripID><TripStartTime>2013-04-17T16:30:00</TripStartTime><VehicleID>6371</VehicleID></BusPosition>
I just saw #2506 a few days ago! As for #6371, I thought West Ox already had that one. Did #6370 come with it? And what happened to #3751-3760?
#2509 remains at FMR. Saw it yesterday at Pentagon.
3024 is back from rehab
<BusPosition><DateTime>2013-04-22T17:16:24</DateTime><Deviation>-4.48</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.916351</Lat><Lon>-77.220474</Lon><RouteID>3T</RouteID><TripEndTime>2013-04-22T17:12:00</TripEndTime><TripHeadsign>TYSONS CORNER</TripHeadsign><TripID>8028_21</TripID><TripStartTime>2013-04-22T16:40:00</TripStartTime><VehicleID>3024</VehicleID></BusPosition>
One more baby Orion VII left for rehab, and that's 3009
So, #3009 is the last Orion VII to be rehabbed (not counting the other 52 new ones from last year)?
That's what I just said, yes
Also, 2508 has moved to Bladensburg
<BusPosition><DateTime>2013-04-22T20:02:34</DateTime><Deviation>0.25</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.900211</Lat><Lon>-77.034134</Lon><RouteID>G8</RouteID><TripEndTime>2013-04-22T20:51:00</TripEndTime><TripHeadsign>AVONDALE</TripHeadsign><TripID>6360_21</TripID><TripStartTime>2013-04-22T20:00:00</TripStartTime><VehicleID>2508</VehicleID></BusPosition>
I going to assume that Bladenburg is going to end up with #2501-2515 and #3001-3022? For now, we (FMR) still have #2509, #2511-2513 and I think #2515.
2525 is back at FMR.
<BusPosition><DateTime>2013-04-23T08:04:22</DateTime><Deviation>-5.00</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.867676</Lat><Lon>-77.106934</Lon><RouteID>22B</RouteID><TripEndTime>2013-04-23T08:08:00</TripEndTime><TripHeadsign>BALLSTON STATION</TripHeadsign><TripID>9366_21</TripID><TripStartTime>2013-04-23T07:50:00</TripStartTime><VehicleID>2525</VehicleID></BusPosition>
2519 is back from rehab. At none other than Bladensburg
<BusPosition><DateTime>2013-04-25T16:40:43</DateTime><Deviation>0.13</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.922512</Lat><Lon>-77.042847</Lon><RouteID>43</RouteID><TripEndTime>2013-04-25T16:50:00</TripEndTime><TripHeadsign>MT PLEASANT VIA ADAMS MORGAN</TripHeadsign><TripID>4276_21</TripID><TripStartTime>2013-04-25T16:23:00</TripStartTime><VehicleID>2519</VehicleID></BusPosition>
And 7190 has moved to Landover
<BusPosition><DateTime>2013-04-25T17:50:16</DateTime><Deviation>-4.83</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.939812</Lat><Lon>-76.861374</Lon><RouteID>F14</RouteID><TripEndTime>2013-04-25T17:50:00</TripEndTime><TripHeadsign>NEW CARROLLTON STATION</TripHeadsign><TripID>1686_21</TripID><TripStartTime>2013-04-25T16:42:00</TripStartTime><VehicleID>7190</VehicleID></BusPosition>
I would guess that we'll (FMR) get #2520 back. BTW, was #2520 the first WMATA Orion 7 delivered?
2510 is back from rehab
<BusPosition><DateTime>2013-04-30T08:37:57</DateTime><Deviation>-19.63</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.931423</Lat><Lon>-77.028252</Lon><RouteID>H8</RouteID><TripEndTime>2013-04-30T08:30:00</TripEndTime><TripHeadsign>MT PLEASANT</TripHeadsign><TripID>7203_41</TripID><TripStartTime>2013-04-30T07:51:00</TripStartTime><VehicleID>2510</VehicleID></BusPosition>
#2509 remains at FMR.
2579 is back. What it was doing on the S2 is beyond my knowledge (it's heading back to FMR according to the coords)
<BusPosition><DateTime>2013-05-06T09:40:22</DateTime><Deviation>-1.10</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.841358</Lat><Lon>-77.054153</Lon><RouteID>S2</RouteID><TripEndTime>2013-05-06T09:55:00</TripEndTime><TripHeadsign>FEDERAL TRIANGLE</TripHeadsign><TripID>15186_31</TripID><TripStartTime>2013-05-06T09:01:00</TripStartTime><VehicleID>2579</VehicleID></BusPosition>
Four Mile has 3 blocks (F250-252) on the S2 in the morning. All trips are from 16th & Harvard Sts NW to 14th & I St NW.
2537 has also returned to FMR.
<BusPosition><DateTime>2013-05-06T15:07:06</DateTime><Deviation>-3.92</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.868996</Lat><Lon>-77.10627</Lon><RouteID>4A</RouteID><TripEndTime>2013-05-06T15:13:00</TripEndTime><TripHeadsign>ROSSLYN STATION</TripHeadsign><TripID>8574_31</TripID><TripStartTime>2013-05-06T14:40:00</TripStartTime><VehicleID>2537</VehicleID></BusPosition>
Wasn't that bus back for a while now?
@Chargerdodge: nope, that's one of the last few to go in to rehab
2520 is back as well. Looks like 2519 and 2520 are the cutoffs between Bburg and FMR
<BusPosition><DateTime>2013-05-06T17:23:12</DateTime><Deviation>3.80</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.856266</Lat><Lon>-77.112602</Lon><RouteID>16G</RouteID><TripEndTime>2013-05-06T17:27:00</TripEndTime><TripHeadsign>COLUMBIA HEIGHTS WEST</TripHeadsign><TripID>10189_31</TripID><TripStartTime>2013-05-06T16:54:00</TripStartTime><VehicleID>2520</VehicleID></BusPosition>
In other news: 2509, 2511, and 2512 have moved to Bburg
<BusPosition><DateTime>2013-05-06T17:34:55</DateTime><Deviation>2.65</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.902439</Lat><Lon>-77.0299</Lon><RouteID>D4</RouteID><TripEndTime>2013-05-06T18:04:00</TripEndTime><TripHeadsign>IVY CITY</TripHeadsign><TripID>6357_31</TripID><TripStartTime>2013-05-06T17:36:00</TripStartTime><VehicleID>2509</VehicleID></BusPosition>
<BusPosition><DateTime>2013-05-06T17:32:57</DateTime><Deviation>-7.10</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.901119</Lat><Lon>-77.019119</Lon><RouteID>D4</RouteID><TripEndTime>2013-05-06T17:48:00</TripEndTime><TripHeadsign>IVY CITY</TripHeadsign><TripID>6383_31</TripID><TripStartTime>2013-05-06T17:20:00</TripStartTime><VehicleID>2511</VehicleID></BusPosition>
<BusPosition><DateTime>2013-05-06T17:32:18</DateTime><Deviation>-1.87</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.919788</Lat><Lon>-76.995461</Lon><RouteID>83</RouteID><TripEndTime>2013-05-06T18:34:00</TripEndTime><TripHeadsign>CHERRY HILL</TripHeadsign><TripID>5074_31</TripID><TripStartTime>2013-05-06T17:30:00</TripStartTime><VehicleID>2512</VehicleID></BusPosition>
So because the highest 2500 for Bburg goes up to 2519, we should eventually expect 2513, 2516, 2517, and 2518 to move as well.
One more thing, 6156 can be taken off the possible rehab list
<BusPosition><DateTime>2013-05-06T17:32:53</DateTime><Deviation>-2.00</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.843807</Lat><Lon>-76.92952</Lon><RouteID>D14c</RouteID><TripEndTime>2013-05-06T17:53:00</TripEndTime><TripHeadsign>CAMP SPRINGS</TripHeadsign><TripID>16183_31</TripID><TripStartTime>2013-05-06T17:30:00</TripStartTime><VehicleID>6156</VehicleID></BusPosition>
Well, I saw both #2513 and #2518 earlier, so you could be right.
2604 on the 5A, I hope there's not too many people on board
<BusPosition><DateTime>2013-05-09T16:58:07</DateTime><Deviation>0.47</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.962772</Lat><Lon>-77.430122</Lon><RouteID>5A</RouteID><TripEndTime>2013-05-09T17:03:00</TripEndTime><TripHeadsign>DULLES AIRPORT</TripHeadsign><TripID>10430_31</TripID><TripStartTime>2013-05-09T16:00:00</TripStartTime><VehicleID>2604</VehicleID></BusPosition>
Also, according to the API, 4298, 4299, 4305, 4358, 4360, 4361, 4362, 4378, and 4387 have moved to Annex
I'm guessing they're gonna try to get some Annex 6100s in rehab as fast as possible
Quote from: NewFlyer9736BCT on May 09, 2013, 05:16:48 PM
2604 on the 5A, I hope there's not too many people on board
<BusPosition><DateTime>2013-05-09T16:58:07</DateTime><Deviation>0.47</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.962772</Lat><Lon>-77.430122</Lon><RouteID>5A</RouteID><TripEndTime>2013-05-09T17:03:00</TripEndTime><TripHeadsign>DULLES AIRPORT</TripHeadsign><TripID>10430_31</TripID><TripStartTime>2013-05-09T16:00:00</TripStartTime><VehicleID>2604</VehicleID></BusPosition>
Also, according to the API, 4298, 4299, 4305, 4358, 4360, 4361, 4362, 4378, and 4387 have moved to Annex
I'm guessing they're gonna try to get some Annex 6100s in rehab as fast as possible
That reminds me, how many 1997s are left anyway? About 60? Since NOVA no longer has them, there are only so many places they could go.
2609 is back
<BusPosition><DateTime>2013-05-13T11:07:58</DateTime><Deviation>-5.98</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.853489</Lat><Lon>-77.119293</Lon><RouteID>16A</RouteID><TripEndTime>2013-05-13T11:22:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>9808_31</TripID><TripStartTime>2013-05-13T10:36:00</TripStartTime><VehicleID>2609</VehicleID></BusPosition>
2516 has moved to Bladensburg
<BusPosition><DateTime>2013-05-13T11:12:16</DateTime><Deviation>2.55</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.965607</Lat><Lon>-76.939003</Lon><RouteID>86</RouteID><TripEndTime>2013-05-13T11:50:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>4993_31</TripID><TripStartTime>2013-05-13T10:38:00</TripStartTime><VehicleID>2516</VehicleID></BusPosition>
and 6393 is back at Montgomery
<BusPosition><DateTime>2013-05-14T22:24:23</DateTime><Deviation>-0.05</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.045216</Lat><Lon>-77.107597</Lon><RouteID>Z8</RouteID><TripEndTime>2013-05-14T22:40:00</TripEndTime><TripHeadsign>BRIGGS CHANEY PARK & RIDE</TripHeadsign><TripID>13543_31</TripID><TripStartTime>2013-05-14T22:07:00</TripStartTime><VehicleID>6393</VehicleID></BusPosition>
I don't know if anyone's noticed, but the are two kinds of buses that are not showing up online; the C40LFs and Annex's D40LFRs (the ones at Landover and Montgomery are perfectly functional). Fortunately, I have another way to keep track of them. While searching, I found 6142 back online, along with 6157.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>42</Minutes><RouteID>D14</RouteID><VehicleID>6157</VehicleID></NextBusPrediction>
I couldn't find 6142 again (it was on the U2), but trust me, it was there.
What nextbus program/website is that? Speaking of which, on my phone I saw that 6141 was in service on the U's as well.
What depots have the D40LFRs?
6392 has returned to Montgomery
<BusPosition><DateTime>2013-05-16T09:16:06</DateTime><Deviation>-0.10</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.085449</Lat><Lon>-77.146027</Lon><RouteID>T2</RouteID><TripEndTime>2013-05-16T09:16:00</TripEndTime><TripHeadsign>ROCKVILLE STATION</TripHeadsign><TripID>13007_31</TripID><TripStartTime>2013-05-16T08:30:00</TripStartTime><VehicleID>6392</VehicleID></BusPosition>
Update: as well as 6391
<BusPosition><DateTime>2013-05-16T15:23:10</DateTime><Deviation>-1.42</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.057785</Lat><Lon>-76.943764</Lon><RouteID>Z6</RouteID><TripEndTime>2013-05-16T15:52:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>13707_31</TripID><TripStartTime>2013-05-16T14:58:00</TripStartTime><VehicleID>6391</VehicleID></BusPosition>
Quote from: NewFlyer9736BCT on May 15, 2013, 10:02:57 PM
What nextbus program/website is that? Speaking of which, on my phone I saw that 6141 was in service on the U's as well.
Here you go.
http://api.wmata.com/NextBusService.svc/Predictions?StopID=6001234&api_key=etgnvtnbpnpj32s8ztdjsujf
Thanks man
Here's something weird I found with that (both from stop 3000664):
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Addison Rd Station</DirectionText><Minutes>26</Minutes><RouteID>P12</RouteID><VehicleID>6</VehicleID></NextBusPrediction>
Plus 7196 now being a Landover bus
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Addison Rd Station</DirectionText><Minutes>53</Minutes><RouteID>V12</RouteID><VehicleID>7196</VehicleID></NextBusPrediction>
3009 has returned from rehab
<BusPosition><DateTime>2013-05-20T17:23:25</DateTime><Deviation>0.03</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.892704</Lat><Lon>-77.046768</Lon><RouteID>H1</RouteID><TripEndTime>2013-05-20T18:22:00</TripEndTime><TripHeadsign>BROOKLAND STATION</TripHeadsign><TripID>6698_31</TripID><TripStartTime>2013-05-20T17:20:00</TripStartTime><VehicleID>3009</VehicleID></BusPosition>
Quote from: NewFlyer9736BCT on May 20, 2013, 05:29:51 PM
3009 has returned from rehab
<BusPosition><DateTime>2013-05-20T17:23:25</DateTime><Deviation>0.03</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.892704</Lat><Lon>-77.046768</Lon><RouteID>H1</RouteID><TripEndTime>2013-05-20T18:22:00</TripEndTime><TripHeadsign>BROOKLAND STATION</TripHeadsign><TripID>6698_31</TripID><TripStartTime>2013-05-20T17:20:00</TripStartTime><VehicleID>3009</VehicleID></BusPosition>
And with that, the Orion VII CNGs are finally complete, though I think FMR is still missing #2609 and #2613.
2197 and 2198 have moved to Montgomery yet again
<BusPosition><DateTime>2013-05-22T15:46:43</DateTime><Deviation>-6.75</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.989143</Lat><Lon>-76.988113</Lon><RouteID>C4</RouteID><TripEndTime>2013-05-22T15:59:00</TripEndTime><TripHeadsign>P G PLAZA STATION</TripHeadsign><TripID>11720_31</TripID><TripStartTime>2013-05-22T14:50:00</TripStartTime><VehicleID>2197</VehicleID></BusPosition>
<BusPosition><DateTime>2013-05-22T15:47:12</DateTime><Deviation>-10.98</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>39.006664</Lat><Lon>-77.112045</Lon><RouteID>J2</RouteID><TripEndTime>2013-05-22T16:16:00</TripEndTime><TripHeadsign>SILVER SPRING STATION</TripHeadsign><TripID>12083_31</TripID><TripStartTime>2013-05-22T15:23:00</TripStartTime><VehicleID>2198</VehicleID></BusPosition>
6420 and 6423 have moved to Shepherd (most likely bringing 6421 and 6422 along)
<BusPosition><DateTime>2013-05-22T15:45:01</DateTime><Deviation>-0.42</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.897129</Lat><Lon>-77.029518</Lon><RouteID>A9</RouteID><TripEndTime>2013-05-22T16:29:00</TripEndTime><TripHeadsign>LIVINGSTON VIA SOUTH CAPITOL</TripHeadsign><TripID>18697_31</TripID><TripStartTime>2013-05-22T15:40:00</TripStartTime><VehicleID>6420</VehicleID></BusPosition>
6423 isn't online right now, but here's a screenshot of my phone from yesterday morning showing that bus on the 34
(https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-ash3/941830_346375968821161_1298962386_n.jpg)
Confirmed! #6368 and #6370 are both West Ox buses now. Both spotted at Pentagon yesterday. Also #2520 is back as well.
29C 2630
29K 2151
16B 2580
9A 3027
22A 2568
25A 2716
ART 41 5049 (Designline CNG)
PRTC S1 382.
On an unrelated side note, I finally saw a V-22 Osprey yesterday! It was flying over Four Mile Run (not the depot) heading east. Never saw one before.
Well, it looks like 6013 WASN'T ready to be rehabbed yet...
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Greenbelt Station</DirectionText><Minutes>19</Minutes><RouteID>G14</RouteID><VehicleID>6013</VehicleID></NextBusPrediction>
Why don't they rehabbed those buses already? It's only 39 of them....
2613 is back at Four Mile Run...
<BusPosition><DateTime>2013-05-27T17:26:44</DateTime><Deviation>-7.55</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.905434</Lat><Lon>-77.01429</Lon><RouteID>P6</RouteID><TripEndTime>2013-05-27T17:35:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>3624_33</TripID><TripStartTime>2013-05-27T16:45:00</TripStartTime><VehicleID>2613</VehicleID></BusPosition>
Awesome. I think that's the last one right?
Nope there's still 2542. Although it is possible that it's back as well, but no one has seen it online yet.
2517 is at Bladensburg. All that remains is 2518.
<BusPosition><DateTime>2013-05-28T17:30:27</DateTime><Deviation>-14.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.873974</Lat><Lon>-76.971237</Lon><RouteID>X1</RouteID><TripEndTime>2013-05-28T17:16:00</TripEndTime><TripHeadsign>MINNESOTA AVE STATION</TripHeadsign><TripID>7722_31</TripID><TripStartTime>2013-05-28T16:28:00</TripStartTime><VehicleID>2517</VehicleID></BusPosition>
You might as well add that one too, because I haven't seen it in a while.
Quote from: Chargerdodge9 on May 28, 2013, 08:43:40 PM
You might as well add that one too, because I haven't seen it in a while.
Nope. According to this, it's still at FMR.
<BusPosition><DateTime>2013-05-29T11:59:36</DateTime><Deviation>4.40</Deviation><DirectionNum>1</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.825741</Lat><Lon>-77.219421</Lon><RouteID>
16D</RouteID><TripEndTime>2013-05-29T12:52:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>9799_31</TripID><TripStartTime>2013-05-29T12:04:00</TripStartTime><VehicleID>
2518</VehicleID></BusPosition>
And 6011 is back at Landover (I hope I'm right about it being rehabbed this time).
<BusPosition><DateTime>2013-05-29T11:56:38</DateTime><Deviation>-3.50</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.964863</Lat><Lon>-76.896652</Lon><RouteID>
F6</RouteID><TripEndTime>2013-05-29T12:48:00</TripEndTime><TripHeadsign>FORT TOTTEN STATION</TripHeadsign><TripID>2315_31</TripID><TripStartTime>2013-05-29T11:46:00</TripStartTime><VehicleID>
6011</VehicleID></BusPosition>
Man, I'm dying to see a rehabbed DE40LF.
And another one returns (possibly); this time it's 6030.
<BusPosition><DateTime>2013-06-01T13:47:07</DateTime><Deviation>-2.02</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.006882</Lat><Lon>-76.986252</Lon><RouteID>K6</RouteID><TripEndTime>2013-06-01T14:02:00</TripEndTime><TripHeadsign>WHITE OAK</TripHeadsign><TripID>5620_32</TripID><TripStartTime>2013-06-01T13:15:00</TripStartTime><VehicleID>6030</VehicleID></BusPosition>
The mysterious bus #6
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>5</Minutes><RouteID>F4</RouteID><VehicleID>6</VehicleID></NextBusPrediction>
...turns out to be none other than 7013, confirmed about an hour ago at Silver Spring Station
At last! The final Orion VII rehab has returned to service! (2542 for those of you just tuning in)
I'm really hoping that two buses returned from rehab this time instead of one, so that we can finally see a rehabbed DE40LF or another D40LFR
<BusPosition><DateTime>2013-06-03T18:47:28</DateTime><Deviation>-21.57</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.829536</Lat><Lon>-77.21064</Lon><RouteID>29G</RouteID><TripEndTime>2013-06-03T18:26:00</TripEndTime><TripHeadsign>ANNANDALE</TripHeadsign><TripID>10708_31</TripID><TripStartTime>2013-06-03T17:48:00</TripStartTime><VehicleID>2542</VehicleID></BusPosition>
And apparently there's a Landover bus on the D14
<BusPosition><DateTime>2013-06-03T18:53:11</DateTime><Deviation>-28.18</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.840481</Lat><Lon>-76.97551</Lon><RouteID>D14</RouteID><TripEndTime>2013-06-03T18:25:00</TripEndTime><TripHeadsign>SOUTHERN AVE STATION</TripHeadsign><TripID>16187_31</TripID><TripStartTime>2013-06-03T17:05:00</TripStartTime><VehicleID>6015</VehicleID></BusPosition>
Funny thing, I just saw #2542 a few hours ago. I wasn't able to get the rehab number though. Also #2613 is back as well.
Is it me, or is the API info stuck with yesterday's data? It's showing almost all of the same thing that was seen yesterday (plus the date says 6/03)
I really hope that this is fixed soon (plus the 6100s and C40LFs showing up soon). In the meantime, I'm trying to figure out how we can get individual bus data (without it being on a route) just like the good old days.
How are you able to get this data? I want to learn how to do that!
Chargerdodge9: Here's the link (http://api.wmata.com/Bus.svc/BusPositions?routeId=&includingVariations=true&api_key=etgnvtnbpnpj32s8ztdjsujf). As far as I know, it only works on the computer, not phone.
Anyways, see this?
<BusPosition><DateTime>2013-06-05T23:09:02</DateTime><Deviation>-2.65</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.922401</Lat><Lon>-77.072777</Lon><RouteID>31</RouteID><TripEndTime>2013-06-05T23:23:00</TripEndTime><TripHeadsign>FRIENDSHIP HEIGHTS STATION</TripHeadsign><TripID>20929_31</TripID><TripStartTime>2013-06-05T22:51:00</TripStartTime><VehicleID>7164</VehicleID></BusPosition>
It's actually 2228, not 7164. I found out about that while I was out today.
If I didn't already find that bus #6 is 7013, I would have assumed it would be the real 7164 instead
Interesting, at this time, it appears that #2683 is on the 10B.
Weird that the data don't show any C40LFs running anywhere....
What the...!?! I'm I reading this right? A DE42LFA on the 16B?
-<BusPosition><DateTime>2013-06-08T20:13:02</DateTime><Deviation>-22.75</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.826042</Lat><Lon>-77.017372</Lon><RouteID>16B</RouteID><TripEndTime>2013-06-08T20:12:00</TripEndTime><TripHeadsign>ANNANDALE VIA CULMORE</TripHeadsign><TripID>4245_32</TripID><TripStartTime>2013-06-08T19:30:00</TripStartTime><VehicleID>6540</VehicleID></BusPosition>
Could it be #2540 or #2640 on the 16B? I don't think Four Mile Run have the technology to maintain DE42LFAs, but I could be wrong.
Interesting, and a Shepherd Pkwy bus at that. Might be a strategic. Kinda how a couple of weeks ago during the red and orange line shuttles, I saw 7146 on the 2C with a W block, but that kinda made sense since FMR had their hands full with the shuttles
Was that on a weekend? Also, was that Xcelsior working for Western, West Ox, or Four Mile Run?
What's this? A FMR bus on the P6?
-<BusPosition><DateTime>2013-06-09T19:59:49</DateTime><Deviation>-3.67</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.876534</Lat><Lon>-77.008339</Lon><RouteID>P6</RouteID><TripEndTime>2013-06-09T20:31:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>3606_33</TripID><TripStartTime>2013-06-09T19:45:00</TripStartTime><VehicleID>2609</VehicleID></BusPosition>
QuoteWas that on a weekend? Also, was that Xcelsior working for Western, West Ox, or Four Mile Run?
Yes it was during Memorial Day weekend. 7146 is a Western bus, as the W block stands for Western. For West Ox, the block is A for Arlington since it replaced the old Arlington facility
Quote
What's this? A FMR bus on the P6?
-<BusPosition><DateTime>2013-06-09T19:59:49</DateTime><Deviation>-3.67</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.876534</Lat><Lon>-77.008339</Lon><RouteID>P6</RouteID><TripEndTime>2013-06-09T20:31:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>3606_33</TripID><TripStartTime>2013-06-09T19:45:00</TripStartTime><VehicleID>2609</VehicleID></BusPosition>
On Sundays, most P6 runs are operated by FMR. It's been that way since the old Southeast garage closed, and I guess they kept it like that.
Oh, okay. That explains why I've seen bus #2567 on the P6 before.
7117 on the M6.
<BusPosition><DateTime>2013-06-26T17:09:00</DateTime><Deviation>-4.00</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.880604</Lat><Lon>-76.985344</Lon><RouteID>M6</RouteID><TripEndTime>2013-06-26T17:05:00</TripEndTime><TripHeadsign>POTOMAC AVE STATION</TripHeadsign><TripID>16381_31</TripID><TripStartTime>2013-06-26T16:43:00</TripStartTime><VehicleID>7117</VehicleID></BusPosition>
#4321@ FMR.
-<BusPosition><DateTime>2013-06-26T18:01:31</DateTime><Deviation>-1.22</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.834815999999996</Lat><Lon>-77.098534</Lon><RouteID>7W</RouteID><TripEndTime>2013-06-26T18:17:00</TripEndTime><TripHeadsign>LINCOLNIA</TripHeadsign><TripID>9142_31</TripID><TripStartTime>2013-06-26T17:52:00</TripStartTime><VehicleID>4321</VehicleID></BusPosition>
Interesting, #2588 is working on the 9S.
-<BusPosition><DateTime>2013-06-27T15:04:20</DateTime><Deviation>-1.02</Deviation><DirectionNum>0</DirectionNum><DirectionText>LOOP</DirectionText><Lat>38.858109</Lat><Lon>-77.051392</Lon><RouteID>9S</RouteID><TripEndTime>2013-06-27T15:22:00</TripEndTime><TripHeadsign>POTOMAC YARD-CRYSTAL CITY STATION</TripHeadsign><TripID>9553_31</TripID><TripStartTime>2013-06-27T15:03:00</TripStartTime><VehicleID>2588</VehicleID></BusPosition>
6174 is back in service (I just hope I'm right about it being rehabbed this time).
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>69</Minutes><RouteID>84</RouteID><VehicleID>6174</VehicleID></NextBusPrediction>
I sure hope so too, it's been way too long since the last rehab returned, at least as seen via online
Also, I see 6016, 6102, 6140, 6153, and 6155 have been removed from your list. So just to be clear, have they been found unrehabbed still?
Quote from: NewFlyer9736BCT on July 01, 2013, 05:48:12 PM
I sure hope so too, it's been way too long since the last rehab returned, at least as seen via online
Also, I see 6016, 6102, 6140, 6153, and 6155 have been removed from your list. So just to be clear, have they been found unrehabbed still?
No, I haven't found them, but they might still be unrehabbed, like what happened with 6011 and 6030.
#4264 is now at FMR. #2118 was seen at FMR earlier too.
Forgot to mention that #7041 and #7042 are back at West Ox now.
@RideOn5905 I would leave them on the list, they've been off the radar long enough, way longer than 6011 and 6030.
@ChargerDodge9 I thought 7041 was the highest at Landover (obviously not counting the 7100s), but good to see it's back at Ox
Quote from: NewFlyer9736BCT on July 03, 2013, 02:27:56 PM
@RideOn5905 I would leave them on the list, they've been off the radar long enough, way longer than 6011 and 6030.
@ChargerDodge9 I thought 7041 was the highest at Landover (obviously not counting the 7100s), but good to see it's back at Ox
I would not be shocked if #7040 came back as well.
2551 on the H8
<DirectionNum>0</DirectionNum><DirectionText>West to Mt Pleasant</DirectionText><Minutes>45</Minutes><RouteID>H8</RouteID><VehicleID>2551</VehicleID>
2188 and 7100 have moved to Montgomery
<DirectionNum>1</DirectionNum><DirectionText>North to Greencastle Park & Ride</DirectionText><Minutes>20</Minutes><RouteID>Z11</RouteID><VehicleID>7100</VehicleID>
<DirectionNum>0</DirectionNum><DirectionText>North to White Oak</DirectionText><Minutes>34</Minutes><RouteID>K6</RouteID><VehicleID>2188</VehicleID>
6418 has moved to Shepherd Pkwy
<DirectionNum>0</DirectionNum><DirectionText>South to Camp Springs</DirectionText><Minutes>39</Minutes><RouteID>W15</RouteID><VehicleID>6418</VehicleID>
Yesterday I rode 6417 on the Q4 so that one should still be there.
So the other day on the API I saw 2650 on the X9, and now here's 2651 on the X9
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Metro Center</DirectionText><Minutes>61</Minutes><RouteID>X9</RouteID><VehicleID>2651</VehicleID>
Hmm, that's weird. A hybrid on the 7W (this is outdated but from earlier today)?
-<BusPosition><DateTime>2013-07-12T09:39:11</DateTime><Deviation>-8.22</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.81815</Lat><Lon>-77.135986</Lon><RouteID>7W</RouteID><TripEndTime>2013-07-12T08:59:00</TripEndTime><TripHeadsign>PENTAGON</TripHeadsign><TripID>8836_51</TripID><TripStartTime>2013-07-12T08:33:00</TripStartTime><VehicleID>6438</VehicleID></BusPosition>
6161 is back at Annex.
<BusPosition><DateTime>2013-07-16T12:16:28</DateTime><Deviation>1.45</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.865833</Lat><Lon>-76.944153</Lon><RouteID>M6</RouteID><TripEndTime>2013-07-16T12:12:00</TripEndTime><TripHeadsign>FAIRFAX VILLAGE</TripHeadsign><TripID>16441_51</TripID><TripStartTime>2013-07-16T12:00:00</TripStartTime><VehicleID>6161</VehicleID></BusPosition>
EDIT: And it looks like it brought along company...
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Southern Ave Station</DirectionText><Minutes>16</Minutes><RouteID>D14</RouteID><VehicleID>6153</VehicleID></NextBusPrediction>
Cool, a hybird on the 29K at this time of night.
-<BusPosition><DateTime>2013-07-18T21:52:22</DateTime><Deviation>0.52</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.810616</Lat><Lon>-77.042328</Lon><RouteID>29K</RouteID><TripEndTime>2013-07-18T20:31:00</TripEndTime><TripHeadsign>GEORGE MASON UNIVERSITY</TripHeadsign><TripID>4001_51</TripID><TripStartTime>2013-07-18T19:20:00</TripStartTime><VehicleID>7052</VehicleID></BusPosition>
6118 and 6155 are back in service.
<BusPosition><DateTime>2013-07-23T11:04:20</DateTime><Deviation>-2.87</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.831379</Lat><Lon>-76.942436</Lon><RouteID>D12</RouteID><TripEndTime>2013-07-23T10:27:00</TripEndTime><TripHeadsign>SUITLAND STATION</TripHeadsign><TripID>16139_51</TripID><TripStartTime>2013-07-23T09:30:00</TripStartTime><VehicleID>6155</VehicleID></BusPosition>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>35</Minutes><RouteID>D12</RouteID><VehicleID>6118</VehicleID></NextBusPrediction>
I also saw on the api that 6120 is back on the radar. also I found 6155 today, I'll post the rehab # later today
check stop # 1003327 now, 6120 should be on the D14 in 65 min from now
update: 6120 is also rehabbed. got the # to report later as well
6102 has returned
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Branch Ave Station</DirectionText><Minutes>19</Minutes><RouteID>C14</RouteID><VehicleID>6102</VehicleID></NextBusPrediction>
update: as well as 6129
More DE42LFAs are arriving at Shep. In addition to these, I saw 6579, 6580, 6581, and I think 6583 over the weekend.
<BusPosition><DateTime>2013-08-05T09:58:49</DateTime><Deviation>-1.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.814823</Lat><Lon>-77.015968</Lon><RouteID>90</RouteID><TripEndTime>2013-08-05T08:50:00</TripEndTime><TripHeadsign>ELLINGTON BRIDGE</TripHeadsign><TripID>17528_51</TripID><TripStartTime>2013-08-05T07:50:00</TripStartTime><VehicleID>6585</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-05T10:11:20</DateTime><Deviation>1.08</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.887039</Lat><Lon>-76.994972</Lon><RouteID>90</RouteID><TripEndTime>2013-08-05T09:41:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>17515_51</TripID><TripStartTime>2013-08-05T08:41:00</TripStartTime><VehicleID>6582</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-05T10:05:00</DateTime><Deviation>-1.92</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.909424</Lat><Lon>-77.009216</Lon><RouteID>P6</RouteID><TripEndTime>2013-08-05T09:40:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>18961_51</TripID><TripStartTime>2013-08-05T08:42:00</TripStartTime><VehicleID>6584</VehicleID></BusPosition>
I've got two things to report as far as Landover goes:
First, for whatever reason, almost all of their DE40LFs and DE40LFRs are not showing up, on either the main API or the stop-by-stop one. I'm assuming they're all still at Landover, since it'd be crazy to have 20+ buses suddenly show up at Bladensburg for rehab all at once, but I hope they come back online soon...
And second, this.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Rhode Island Ave Station</DirectionText><Minutes>23</Minutes><RouteID>T18</RouteID><VehicleID>5</VehicleID></NextBusPrediction>
The other day I noticed a lot of Landover buses not showing up online at all, even the Xcelsiors (7012, 7027, and 7154 to name a few), but now 7027 and 7154 are back online, and maybe 7012. I saw that "5" bus online as well, I'm thinking it could be one of the new rehabs to come back this week since apparently nothing else showed up.
"5" is none other than 4209, I'm riding it now and assumed that this bus was off the radar until I checked the stop number that I was just at
Okay, good. Glad that's cleared up.
Back to business: Something has finally returned from rehab; its 6101.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>55</Minutes><RouteID>D12</RouteID><VehicleID>6101</VehicleID></NextBusPrediction>
It's not that often you see the weekly rehabs return later in the week as opposed to earlier.
That said, 6143 is also back from rehab
<BusPosition><DateTime>2013-08-09T09:51:26</DateTime><Deviation>-4.03</Deviation><DirectionNum>0</DirectionNum><DirectionText>LOOP</DirectionText><Lat>38.883572</Lat><Lon>-76.947197</Lon><RouteID>U5</RouteID><TripEndTime>2013-08-09T09:19:00</TripEndTime><TripHeadsign>MAYFAIR-MARSHALL HTS-LINCOLN HTS</TripHeadsign><TripID>16676_51</TripID><TripStartTime>2013-08-09T08:11:00</TripStartTime><VehicleID>6143</VehicleID></BusPosition>
I wonder what's up with 6140, that one has been off the radar longer than the others now. I'm thinking rehab 1694 is either that bus or 6016.
Quote from: RideOn5905 on August 05, 2013, 10:27:23 AM
More DE42LFAs are arriving at Shep. In addition to these, I saw 6579, 6580, 6581, and I think 6583 over the weekend.
<BusPosition><DateTime>2013-08-05T09:58:49</DateTime><Deviation>-1.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.814823</Lat><Lon>-77.015968</Lon><RouteID>90</RouteID><TripEndTime>2013-08-05T08:50:00</TripEndTime><TripHeadsign>ELLINGTON BRIDGE</TripHeadsign><TripID>17528_51</TripID><TripStartTime>2013-08-05T07:50:00</TripStartTime><VehicleID>6585</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-05T10:11:20</DateTime><Deviation>1.08</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.887039</Lat><Lon>-76.994972</Lon><RouteID>90</RouteID><TripEndTime>2013-08-05T09:41:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>17515_51</TripID><TripStartTime>2013-08-05T08:41:00</TripStartTime><VehicleID>6582</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-05T10:05:00</DateTime><Deviation>-1.92</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.909424</Lat><Lon>-77.009216</Lon><RouteID>P6</RouteID><TripEndTime>2013-08-05T09:40:00</TripEndTime><TripHeadsign>RHODE ISLAND AVE STATION</TripHeadsign><TripID>18961_51</TripID><TripStartTime>2013-08-05T08:42:00</TripStartTime><VehicleID>6584</VehicleID></BusPosition>
West Ox just lost 7-8 DE42LFAs and got nothing back? Really?
Also, in case this wasn't reported, all of Four Mile Run's Orion Vs are now gone and so are their older TAGS cutaways it seems.
6106 has returned
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Southern Ave Station</DirectionText><Minutes>6</Minutes><RouteID>D12</RouteID><VehicleID>6106</VehicleID></NextBusPrediction>
I've also noticed some more old Orion Vs coming to Montgomery, at least that's what they are tagged as.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Rockville Station</DirectionText><Minutes>13</Minutes><RouteID>T2</RouteID><VehicleID>4237</VehicleID>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Olney</DirectionText><Minutes>20</Minutes><RouteID>Z2</RouteID><VehicleID>4282</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Rockville Station</DirectionText><Minutes>47</Minutes><RouteID>Q4</RouteID><VehicleID>4288</VehicleID></NextBusPrediction>
....and now it's Shepherd Pkwy's turn with the same group of 42-4300s that have been touring around the region
<BusPosition><DateTime>2013-08-20T11:32:17</DateTime><Deviation>-0.63</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.848263</Lat><Lon>-76.978134</Lon><RouteID>92v1</RouteID><TripEndTime>2013-08-20T11:18:00</TripEndTime><TripHeadsign>CONGRESS HEIGHTS STATION</TripHeadsign><TripID>17380_51</TripID><TripStartTime>2013-08-20T10:18:00</TripStartTime><VehicleID>4264</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:33:07</DateTime><Deviation>2.85</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.90538</Lat><Lon>-76.996262</Lon><RouteID>92v1</RouteID><TripEndTime>2013-08-20T10:46:00</TripEndTime><TripHeadsign>CONGRESS HEIGHTS STATION</TripHeadsign><TripID>17427_51</TripID><TripStartTime>2013-08-20T09:46:00</TripStartTime><VehicleID>4298</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:31:57</DateTime><Deviation>-1.12</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.855194</Lat><Lon>-76.996162</Lon><RouteID>A4</RouteID><TripEndTime>2013-08-20T11:20:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>18186_51</TripID><TripStartTime>2013-08-20T10:55:00</TripStartTime><VehicleID>4305</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:32:49</DateTime><Deviation>-2.90</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.914181</Lat><Lon>-77.016914</Lon><RouteID>92v1</RouteID><TripEndTime>2013-08-20T10:30:00</TripEndTime><TripHeadsign>CONGRESS HEIGHTS STATION</TripHeadsign><TripID>17392_51</TripID><TripStartTime>2013-08-20T09:30:00</TripStartTime><VehicleID>4321</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:32:46</DateTime><Deviation>0.23</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.861904</Lat><Lon>-76.993431</Lon><RouteID>90</RouteID><TripEndTime>2013-08-20T11:17:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>17413_51</TripID><TripStartTime>2013-08-20T10:17:00</TripStartTime><VehicleID>4361</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:29:50</DateTime><Deviation>-3.20</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.878429</Lat><Lon>-76.994972</Lon><RouteID>90</RouteID><TripEndTime>2013-08-20T11:01:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>17487_51</TripID><TripStartTime>2013-08-20T10:01:00</TripStartTime><VehicleID>4362</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:33:05</DateTime><Deviation>2.82</Deviation><DirectionNum>0</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.869602</Lat><Lon>-76.972328</Lon><RouteID>34</RouteID><TripEndTime>2013-08-20T11:09:00</TripEndTime><TripHeadsign>NAYLOR RD STATION</TripHeadsign><TripID>17247_51</TripID><TripStartTime>2013-08-20T10:36:00</TripStartTime><VehicleID>4366</VehicleID></BusPosition>
<BusPosition><DateTime>2013-08-20T11:31:47</DateTime><Deviation>1.83</Deviation><DirectionNum>0</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.89801</Lat><Lon>-77.026993</Lon><RouteID>P6</RouteID><TripEndTime>2013-08-20T10:48:00</TripEndTime><TripHeadsign>ANACOSTIA STATION</TripHeadsign><TripID>18962_51</TripID><TripStartTime>2013-08-20T09:50:00</TripStartTime><VehicleID>4378</VehicleID></BusPosition>
Update: Found 6048.............on the C2
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Wheaton Station</DirectionText><Minutes>0</Minutes><RouteID>C2</RouteID><VehicleID>6048</VehicleID></NextBusPrediction>
Even though my theories tend to be false, I'll give another one anyway. The real 6048 might actually be in rehab, and its GPS has been hooked onto a recent rehab Montgomery bus. Although, weird things happen on the C2 anyways, so this could actually be legit.
Yeah, that could be true. I remember last year, when the C2 actually had a Bladensburg block in the afternoon for a short period of time. If it is indeed another rehab in disguise, then it could be either 6016 or 6193. And look who else finally decided to show up...
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Silver Spring Station</DirectionText><Minutes>24</Minutes><RouteID>Z2</RouteID><VehicleID>6024</VehicleID></NextBusPrediction>
And of course, another letdown. "6048" is actually 6408, dyslexic error just as I thought.
Also, I saw 6024 the other day on the Q's, unrehabbed in case you wondered
In other news... 6185 and 6190 have returned
6191 is back.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>North to Greencastle Park & Ride</DirectionText><Minutes>36</Minutes><RouteID>Z11</RouteID><VehicleID>6191</VehicleID></NextBusPrediction>
Did West Ox get anything back from because of the hybrids they lost?
Quote from: Chargerdodge9 on August 31, 2013, 11:48:02 AM
Did West Ox get anything back from because of the hybrids they lost?
Which ones, 6578-6585?
Yes, they took some of Montgomery's LFAs (6390-6397)
6140 is finally back, I'm assuming it's rehabbed
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>76</Minutes><RouteID>D12</RouteID><VehicleID>6140</VehicleID></NextBusPrediction>
UPDATE: 6149 has also returned
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText><Minutes>47</Minutes><RouteID>U6</RouteID><VehicleID>6149</VehicleID></NextBusPrediction>
...and so has 6033.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to P G Plaza Station</DirectionText><Minutes>38</Minutes><RouteID>C4</RouteID><VehicleID>6033</VehicleID></NextBusPrediction>
And it doesn't end there. 6193 has also returned
In fact, I'm at Rockville Station looking at it, looks great.
This stop is supposed to say Rockville Station but for some reason it says Springhill and Cherrywood
UPDATE: just saw 6033, not rehabbed. ..
6162 is back from potential rehab (I don't think it was gone long enough, unless it was done really fast)
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Naylor Rd Station</DirectionText><Minutes>89</Minutes><RouteID>C14</RouteID><VehicleID>6162</VehicleID></NextBusPrediction>
6050 is also back online, but I highly highly doubt it was rehabbed during such a short time (and last week 6001 also showed up online, not rehabbed I'm assuming)
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Greenbelt Station</DirectionText><Minutes>33</Minutes><RouteID>G12</RouteID><VehicleID>6050</VehicleID></NextBusPrediction>
UPDATE: Most likely temporary, but you certainly don't see this every day
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Shady Grove Station</DirectionText><Minutes>79</Minutes><RouteID>Q6</RouteID><VehicleID>6476</VehicleID></NextBusPrediction>
6215 is back at Landover.
<BusPosition><DateTime>2013-09-16T16:58:31</DateTime><Deviation>-18.28</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.076183</Lat><Lon>-76.848457</Lon><RouteID>87</RouteID><TripEndTime>2013-09-16T17:08:00</TripEndTime><TripHeadsign>LAUREL</TripHeadsign><TripID>146_51</TripID><TripStartTime>2013-09-16T16:20:00</TripStartTime><VehicleID>6215</VehicleID></BusPosition>
EDIT: 6030 is also back online; probably not rehabbed because A) the DE40LFs have faked us out before (most notably 6033), and B) it isn't showing up on the individual bus position data like all the other rehabs.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to White Oak</DirectionText><Minutes>20</Minutes><RouteID>K6</RouteID><VehicleID>6030</VehicleID></NextBusPrediction>
And 7265 is in service (the highest # I've seen up until this point was 7263 iirc)
<BusPosition><DateTime>2013-09-16T17:13:54</DateTime><Deviation>1.00</Deviation><DirectionNum>0</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.910221</Lat><Lon>-77.043762</Lon><RouteID>N4</RouteID><TripEndTime>2013-09-16T17:45:00</TripEndTime><TripHeadsign>FRIENDSHIP HEIGHTS</TripHeadsign><TripID>12728_51</TripID><TripStartTime>2013-09-16T17:03:00</TripStartTime><VehicleID>7265</VehicleID></BusPosition>
Yeah those DE40LFs keep faking on us. In fact, 6030 has done it before already.
Anyways, 6192 is back from rehab as well
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Silver Spring Station</DirectionText><Minutes>43</Minutes><RouteID>J2</RouteID><VehicleID>6192</VehicleID></NextBusPrediction>
Also, 6115 and 6142 are back online. I doubt they're rehabbed since it hasn't been long enough, but who knows...
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>North to L'enfant Plaza Station</DirectionText><Minutes>18</Minutes><RouteID>V5</RouteID><VehicleID>6115</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Southern Ave Station</DirectionText><Minutes>52</Minutes><RouteID>D12</RouteID><VehicleID>6142</VehicleID></NextBusPrediction>
UPDATE: 6157 has also returned. Rehabbed? Maybe, but it has faked on us once before.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Branch Ave Station</DirectionText><Minutes>94</Minutes><RouteID>C14</RouteID><VehicleID>6157</VehicleID></NextBusPrediction>
6122 is also back online. Since it didn't show up on the individual position data, this one probably isn't rehabbed, either.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>2</Minutes><RouteID>D12</RouteID><VehicleID>6122</VehicleID></NextBusPrediction>
6163 is back from rehab.
<BusPosition><DateTime>2013-09-23T16:44:13</DateTime><Deviation>-4.50</Deviation><DirectionNum>0</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.074532</Lat><Lon>-76.848076</Lon><RouteID>87</RouteID><TripEndTime>2013-09-23T17:08:00</TripEndTime><TripHeadsign>LAUREL</TripHeadsign><TripID>146_51</TripID><TripStartTime>2013-09-23T16:20:00</TripStartTime><VehicleID>6163</VehicleID></BusPosition>
6187 is back. Even though its rehab number is already tallied, this is its first time back in service.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Eastover</DirectionText><Minutes>87</Minutes><RouteID>P12</RouteID><VehicleID>6187</VehicleID></NextBusPrediction>
Same with 6180
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Eastover</DirectionText><Minutes>20</Minutes><RouteID>P12</RouteID><VehicleID>6180</VehicleID></NextBusPrediction>
6162 is back
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText><Minutes>12</Minutes><RouteID>U5</RouteID><VehicleID>6162</VehicleID></NextBusPrediction>
7196 on the V7
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Deanwood Station</DirectionText><Minutes>21</Minutes><RouteID>V7</RouteID><VehicleID>7196</VehicleID></NextBusPrediction>
7241 on the R1
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Adelphi</DirectionText><Minutes>15</Minutes><RouteID>R1</RouteID><VehicleID>7241</VehicleID></NextBusPrediction>
Quote from: NewFlyer9736BCT on October 07, 2013, 03:22:17 PM
6162 is back
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText><Minutes>12</Minutes><RouteID>U5</RouteID><VehicleID>6162</VehicleID></NextBusPrediction>
7196 on the V7
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Deanwood Station</DirectionText><Minutes>21</Minutes><RouteID>V7</RouteID><VehicleID>7196</VehicleID></NextBusPrediction>
7241 on the R1
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Adelphi</DirectionText><Minutes>15</Minutes><RouteID>R1</RouteID><VehicleID>7241</VehicleID></NextBusPrediction>
Do you know what happened to those white Xcelisors reported a while back?
The white Xcelsiors... To tell you the truth, I really don't know. At any rate, 6184 is back from rehab.
<BusPosition><DateTime>2013-10-18T17:13:50</DateTime><Deviation>-21.40</Deviation><DirectionNum>1</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.917233</Lat><Lon>-76.881393</Lon><RouteID>A12</RouteID><TripEndTime>2013-10-18T17:32:00</TripEndTime><TripHeadsign>CAPITAL PLAZA</TripHeadsign><TripID>1208_11</TripID><TripStartTime>2013-10-18T16:38:00</TripStartTime><VehicleID>6184</VehicleID></BusPosition>
6199 is back online (after apparently being back from rehab since a couple of weeks ago)
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Rockville Station</DirectionText><Minutes>3</Minutes><RouteID>Q4</RouteID><VehicleID>6199</VehicleID></NextBusPrediction>
And 6115 is back from........wherever it's been (again). Rehabbed? Possibly
....and I can't seem to find it again. I found it earlier on my phone, supposedly on the U5/U6
...and the site is finally back up. On that note, 6112, 6119, and 6213 have all returned.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Anacostia Station</DirectionText><Minutes>1</Minutes><RouteID>W4</RouteID><VehicleID>6119</VehicleID></NextBusPrediction>
<BusPosition><DateTime>2013-10-30T22:25:01</DateTime><Deviation>-3.45</Deviation><DirectionNum>1</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>39.192371</Lat><Lon>-76.687462</Lon><RouteID>B30</RouteID><TripEndTime>2013-10-30T22:49:00</TripEndTime><TripHeadsign>GREENBELT STATION</TripHeadsign><TripID>1459_11</TripID><TripStartTime>2013-10-30T22:14:00</TripStartTime><VehicleID>6213</VehicleID></BusPosition>
And 6112 isn't online right now, of course, but I did see it earlier, on... the U2, iirc.
I wonder if they fixed that GPS on 6112. I hope they did, because I hate having to look for something without being able to track it.
Also not online yet, 6147, however it is back on the road rehabbed.
Also, 6408's GPS has been corrected, no longer showing up as 6048
Update: 6112 is showing up after all
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText><Minutes>15</Minutes><RouteID>U6</RouteID><VehicleID>6112</VehicleID></NextBusPrediction>
Update 2: 2392 is back in service after that accident on N. Capitol and Rhode Island Ave (that was fast)
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Farragut Square</DirectionText><Minutes>60</Minutes><RouteID>G8</RouteID><VehicleID>2392</VehicleID></NextBusPrediction>
6033 is also back online. I don't think it's rehabbed, but I'd still keep my eyes peeled for it.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Rockville Station</DirectionText><Minutes>7</Minutes><RouteID>Q4</RouteID><VehicleID>6033</VehicleID></NextBusPrediction>
Speaking of hybrids, 6016 has been gone for WAY too long now (7-8 months, I think). I'm starting to think it might actually be at Johnson Truck Center in Landover, or wherever, getting some repair work done.
Also, as you know, the bus position data for NextBus has only been showing data for: the new Xcelsiors (7265-69), the new cutaways used for the S80, buses returning from rehab, and a few of the Orion Vs. But today, I spotted this:
<BusPosition><DateTime>2013-11-01T17:16:35</DateTime><Deviation>-5.90</Deviation><DirectionNum>1</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.900154</Lat><Lon>-77.035988</Lon><RouteID>X2</RouteID><TripEndTime>2013-11-01T17:11:00</TripEndTime><TripHeadsign>LAFAYETTE SQUARE</TripHeadsign><TripID>7894_11</TripID><TripStartTime>2013-11-01T16:35:00</TripStartTime><VehicleID>5415</VehicleID></BusPosition>
Make of it what you will.
6013 is back at Landover. Rehabbed? Maybe.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Langley Park</DirectionText><Minutes>21</Minutes><RouteID>F8</RouteID><VehicleID>6013</VehicleID></NextBusPrediction>
Quote from: RideOn5905 on November 04, 2013, 05:01:02 PM
6013 is back at Landover. Rehabbed? Maybe.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Langley Park</DirectionText><Minutes>21</Minutes><RouteID>F8</RouteID><VehicleID>6013</VehicleID></NextBusPrediction>
Just saw it on the T18 now. Still not rehabbed.
I guess it's just not their time yet, maybe they have a longer life span
Also, 6115 is back from rehab
6168 has returned
And so has 6181.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>0</Minutes><RouteID>F4</RouteID><VehicleID>6181</VehicleID></NextBusPrediction>
EDIT: 6195 is also back.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Silver Spring Station</DirectionText><Minutes>19</Minutes><RouteID>J1</RouteID><VehicleID>6195</VehicleID></NextBusPrediction>
6214 is back
6142 and 6160 have returned
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Deanwood Station</DirectionText><Minutes>29</Minutes><RouteID>W4</RouteID><VehicleID>6142</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>South to Fairfax Village</DirectionText><Minutes>71</Minutes><RouteID>V5</RouteID><VehicleID>6160</VehicleID></NextBusPrediction>
And so has 6194.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to P G Plaza Station</DirectionText><Minutes>42</Minutes><RouteID>C4</RouteID><VehicleID>6194</VehicleID></NextBusPrediction>
And of course, let's not forget 6196
EDIT: In case you haven't had enough, 6124 is also back
EDIT 2: Maybe I spoke too soon, since 6124 is not showing up on the C12/14 anymore (it showed up several times earlier on stop 3000700)
What the...?
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to White Oak</DirectionText><Minutes>36</Minutes><RouteID>Z8</RouteID><VehicleID>6139</VehicleID></NextBusPrediction>
Either it's another "dyslexic error" and it's really 6193, or it's an Annex strategic, or idk what. For one thing, this morning on the API I did see this bus on an Annex route (one of the U's I believe)
Update: Nope, here's 6193
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Silver Spring Station</DirectionText><Minutes>16</Minutes><RouteID>J3</RouteID><VehicleID>6193</VehicleID></NextBusPrediction>
I wish I could catch 6139 today but I have to go to work soon...
6041 is back online.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>North to Greenbelt Station</DirectionText><Minutes>7</Minutes><RouteID>R12</RouteID><VehicleID>6041</VehicleID></NextBusPrediction>
Finally...a possible new rehab is back 6178
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Forestville</DirectionText><Minutes>93</Minutes><RouteID>J11</RouteID><VehicleID>6178</VehicleID></NextBusPrediction>
UPDATE: and 6111
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText><Minutes>16</Minutes><RouteID>U6</RouteID><VehicleID>6111</VehicleID></NextBusPrediction>
6175 has also returned.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>25</Minutes><RouteID>F6</RouteID><VehicleID>6175</VehicleID></NextBusPrediction>
EDIT: 6025 is also back online.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to P G Plaza Station</DirectionText><Minutes>15</Minutes><RouteID>C4</RouteID><VehicleID>6025</VehicleID></NextBusPrediction>
6179 is back from rehab.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Rhode Island Ave Station</DirectionText><Minutes>9</Minutes><RouteID>T18</RouteID><VehicleID>6179</VehicleID></NextBusPrediction>
EDIT: And now we've got... 7242 at Bladensburg?
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Cherry Hill</DirectionText><Minutes>16</Minutes><RouteID>83</RouteID><VehicleID>7242</VehicleID></NextBusPrediction>
Nothing else has returned yet, which is weird since there should be hordes of buses due to return soon. But the reason for this post is to say that I will not be able to post next week (Jan 5-12), because I will be going on a cruise in the Caribbean on Royal Caribbean's Adventure of the Seas. I'm so excited; I haven't been on a cruise since Christmas 2007! (For the record, this will be my fourth cruise.) But yeah, I won't be able to post during that time because even though the ship does have an internet café, the fee they charge is ridiculous (I am not even fucking exaggerating when I say it costs $3 per minute to go online). I can't even use my phone because since I'll be overseas, that means my phone bill will be though the roof.
9736BCT, would you mind taking over until I get back?
Ditto for me. I'm also going out of town for about a week or so (Going to NY on the 2nd, then to Florida on the 6th. I will at least be able to keep up on what's going on in the 5 boroughs and Long Island while up there transit wise). Enjoy your cruise Ride-on and happy holidays!
Enjoy your cruise, Ride On
Here's what I have so far:
6113 back from possible rehab:
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Southern Ave Station</DirectionText><Minutes>90</Minutes><RouteID>D14</RouteID><VehicleID>6113</VehicleID></NextBusPrediction>
And 6163 has moved to Annex:
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText><Minutes>30</Minutes><RouteID>U5</RouteID><VehicleID>6163</VehicleID></NextBusPrediction>
Have you heard over he news about that bus operator being crushed to death by that XDE40 in Montgomery Mall yesterday? Think it was #7079.
6136 has returned
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Deanwood Station</DirectionText><Minutes>36</Minutes><RouteID>
W4</RouteID><VehicleID>
6136</VehicleID></NextBusPrediction>
Quote from: Chargerdodge9 on December 31, 2013, 10:15:29 PM
Have you heard over he news about that bus operator being crushed to death by that XDE40 in Montgomery Mall yesterday? Think it was #7079.
I have heard, how tragic :(
BTW it was 7078 at White Oak
UPDATE: 6014 is finally back online. After being gone for so long (albeit not as long as 6016), it's possible this might be rehabbed.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Cheverly Station</DirectionText><Minutes>41</Minutes><RouteID>
F13</RouteID><VehicleID>
6014</VehicleID></NextBusPrediction>
UPDATE 2: 6171 is also back
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Silver Spring Station</DirectionText><Minutes>37</Minutes><RouteID>
F4</RouteID><VehicleID>
6171</VehicleID></NextBusPrediction>
Went out today and noticed a few observations:
1, #2181 is now back at Royal Street depot. Saw it parked at Pentagon, so I assume that #2180 is also back.
2, #6397 is now back at West Ox. Also saw it at the Pentagon serving the 18G a couple of hours ago.
3, In case not already reported, #3018 is at Bladensburg from FMR. Saw it on the R3 today at Greenbelt station.
I'm back, everyone! I had so much fun this past week, although we were lucky to get down to San Juan in time to make it to the ship. We were supposed to fly from DCA directly to San Juan on the morning of, but JetBlue canceled our flight due to weather conditions (our plane was coming in from Boston or whatever). Luckily, we were able to make last-minute arrangements so we could get down there the day before (God bless you, Delta) as opposed to missing the ship and having to fly to its first port of call. Admittedly, we weren't the only ones who got the short end of Mother Nature's stick; shortly after dinner on the second night, we came across a large group from New York who had just arrived that day, albeit without their luggage, and there were several others who also got caught up in the weather. But, I'm finally back, and I am pleased to report that 6140 and 6141 have both returned.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Naylor Rd Station</DirectionText><Minutes>41</Minutes><RouteID>C14</RouteID><VehicleID>6140</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Capitol Heights - Benning Heights</DirectionText><Minutes>25</Minutes><RouteID>U8</RouteID><VehicleID>6141</VehicleID></NextBusPrediction>
EDIT: And so has 6135.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Potomac Ave Station</DirectionText><Minutes>60</Minutes><RouteID>M6</RouteID><VehicleID>6135</VehicleID></NextBusPrediction>
6152 and 6188 are back
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>South to Anacostia Station</DirectionText><Minutes>50</Minutes><RouteID>U2</RouteID><VehicleID>6152</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Eastover</DirectionText><Minutes>58</Minutes><RouteID>P12</RouteID><VehicleID>6188</VehicleID></NextBusPrediction>
And so is 6158.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Capitol Heights - Benning Heights</DirectionText><Minutes>12</Minutes><RouteID>U8</RouteID><VehicleID>6158</VehicleID></NextBusPrediction>
I can confirm that #2518 is back at Four Mile Run. Saw it on the 2B earlier in Ballston. I am also going to assume that #2519 is back as well.
Forgot to mention that I saw a 2008 NABI BRT-60 CNG freshly rehabbed at West Farragut yesterday. It also sported a pedestrian detection system on the roof, but I didn't see the number since it was a few blocks away.
6048 is back at Landover. Rehabbed? Maybe.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Laurel</DirectionText><Minutes>73</Minutes><RouteID>87</RouteID><VehicleID>6048</VehicleID></NextBusPrediction>
Spotted PRTC MCI D4500CL #331 training on the SR-1 line in Dumfries earlier yesterday morning.
6164 is back
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>North to Greenbelt Station</DirectionText><Minutes>24</Minutes><RouteID>R12</RouteID><VehicleID>6164</VehicleID></NextBusPrediction>
6198 is also back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to College Park Station</DirectionText><Minutes>9</Minutes><RouteID>J4</RouteID><VehicleID>6198</VehicleID></NextBusPrediction>
Also, more Orions are returning to Four Mile Run: There's 2514, 2516, and 2517, plus I saw 2515 yesterday; it, too, is back.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Crystal City</DirectionText><Minutes>63</Minutes><RouteID>23A</RouteID><VehicleID>2514</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Seven Corners</DirectionText><Minutes>36</Minutes><RouteID>4A</RouteID><VehicleID>2516</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Seven Corners</DirectionText><Minutes>91</Minutes><RouteID>4B</RouteID><VehicleID>2517</VehicleID></NextBusPrediction>
EDIT: And look at that; 6169 has also returned.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Largo Town Center Station</DirectionText><Minutes>11</Minutes><RouteID>C26</RouteID><VehicleID>6169</VehicleID></NextBusPrediction>
6216 is back.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Eastover</DirectionText><Minutes>65</Minutes><RouteID>P12</RouteID><VehicleID>6216</VehicleID></NextBusPrediction>
EDIT: And so is 6197.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>North to Greencastle Park & Ride</DirectionText><Minutes>1</Minutes><RouteID>Z11</RouteID><VehicleID>6197</VehicleID></NextBusPrediction>
5412 and 6116 are both back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Minnesota Ave Station</DirectionText><Minutes>16</Minutes><RouteID>X2</RouteID><VehicleID>5412</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Clinton Park & Ride</DirectionText><Minutes>24</Minutes><RouteID>C11</RouteID><VehicleID>6116</VehicleID></NextBusPrediction>
6176 has returned.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>51</Minutes><RouteID>G14</RouteID><VehicleID>6176</VehicleID></NextBusPrediction>
EDIT: 6165 has also returned.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>North to Capital Plaza</DirectionText><Minutes>42</Minutes><RouteID>A12</RouteID><VehicleID>6165</VehicleID></NextBusPrediction>
6202 is back at Montgomery.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to White Oak</DirectionText><Minutes>44</Minutes><RouteID>K6</RouteID><VehicleID>6202</VehicleID></NextBusPrediction>
6123 has returned to Annex
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Naylor Rd Station</DirectionText><Minutes>15</Minutes><RouteID>C14</RouteID><VehicleID>6123</VehicleID></NextBusPrediction>
Also, the other day I saw 6034 in person (it's also back online as well), not rehabbed
Has WMATA even begun to rehab the DE40LFs? I have yet to hear about any being repainted or receive engine overhauls yet. Also, any word as to when the first NABI BRT 42 is suppose to get here? If IIRC, the first XDE40 arrived here about this time 3 years ago with the full order starting soon after.
In case not already reported, #2516 is back at Four Mile Run. Saw on it working the 23A yesterday.
6208 has returned.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Lakeforest</DirectionText><Minutes>55</Minutes><RouteID>J9</RouteID><VehicleID>6208</VehicleID></NextBusPrediction>
I also saw 5418 back online earlier; probably not rehabbed, though.
EDIT: 6170 has also returned, and 6018 is back online; like 5418, this one's probably not rehabbed.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Suitland Station</DirectionText><Minutes>12</Minutes><RouteID>V12</RouteID><VehicleID>6170</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Silver Spring Station</DirectionText><Minutes>35</Minutes><RouteID>Y9</RouteID><VehicleID>6018</VehicleID></NextBusPrediction>
Orion VII CNG #2508 back at FMR? Can someone confirm this because I could of sworn I saw that bus yesterday on the 25A.
6150 is back.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Naylor Rd Station</DirectionText><Minutes>0</Minutes><RouteID>C14</RouteID><VehicleID>6150</VehicleID></NextBusPrediction>
EDIT: So is 6146.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Capitol Heights - Benning Heights</DirectionText><Minutes>24</Minutes><RouteID>U8</RouteID><VehicleID>6146</VehicleID></NextBusPrediction>
6217 is on the radar but I doubt it's back since it has the same ETA as 6213, this happened with other in-progress rehabs in the past, such as 6113, 6124, 6164, and 6169
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Greenbelt Station</DirectionText><Minutes>80</Minutes><RouteID>B30</RouteID><VehicleID>6217</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Greenbelt Station</DirectionText><Minutes>80</Minutes><RouteID>B30</RouteID><VehicleID>6213</VehicleID></NextBusPrediction>
And 6177 should be back for real, no other buses with the same ETA
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>West to Largo Town Center Station</DirectionText><Minutes>10</Minutes><RouteID>C26</RouteID><VehicleID>6177</VehicleID></NextBusPrediction>
UPDATE: 6140 is back too, given the mysteriousness of this bus, who knows if it's rehabbed
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Southern Ave Station</DirectionText><Minutes>47</Minutes><RouteID>D14</RouteID><VehicleID>6140</VehicleID></NextBusPrediction>
5411 is back online.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Lafayette Square</DirectionText><Minutes>16</Minutes><RouteID>X2</RouteID><VehicleID>5411</VehicleID></NextBusPrediction>
And so is 6114
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>2</Minutes><RouteID>D12</RouteID><VehicleID>6114</VehicleID></NextBusPrediction>
Also, I've been told that 6140 remains unrehabbed, but it looks like it's online regularly now, so now we wait
6104 has returned.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>27</Minutes><RouteID>D13</RouteID><VehicleID>6104</VehicleID></NextBusPrediction>
And 6043 is back online.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Silver Spring Station</DirectionText><Minutes>32</Minutes><RouteID>F4</RouteID><VehicleID>6043</VehicleID></NextBusPrediction>
On top of that, 6163 seems to be at Landover... again...
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>11</Minutes><RouteID>F4</RouteID><VehicleID>6163</VehicleID></NextBusPrediction>
EDIT: We've also got the return of 6126.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Deanwood Station</DirectionText><Minutes>27</Minutes><RouteID>W4</RouteID><VehicleID>6126</VehicleID></NextBusPrediction>
Don't forget 6209
EDIT - never mind, I've been fooled once again (look at second attachment)
6166 is back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>South to Addison Rd Station</DirectionText><Minutes>19</Minutes><RouteID>A12</RouteID><VehicleID>6166</VehicleID></NextBusPrediction>
6144 has also returned
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Clinton Park & Ride</DirectionText><Minutes>26</Minutes><RouteID>C11</RouteID><VehicleID>6144</VehicleID></NextBusPrediction>
UPDATE 4/22: 6103 is back
<NextBusPrediction>[/size]<DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>6</Minutes><RouteID>D12</RouteID><VehicleID>6103</VehicleID>[/size]</NextBusPrediction>
6211 has returned
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Lakeforest</DirectionText><Minutes>69</Minutes><RouteID>J9</RouteID><VehicleID>6211</VehicleID></NextBusPrediction>
...and so has 6172 (that was rather fast)
<NextBusPrediction>[/size]<DirectionNum>0</DirectionNum><DirectionText>East to Penn Mar</DirectionText><Minutes>82</Minutes><RouteID>V14</RouteID><VehicleID>6172</VehicleID>[/size]</NextBusPrediction>
6209 is also back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Lakeforest</DirectionText><Minutes>65</Minutes><RouteID>J9</RouteID><VehicleID>6209</VehicleID></NextBusPrediction>
You beat me to it. However, yesterday I did see 6139 online, and here it is today right now on the C14
<NextBusPrediction>
<DirectionNum>1</DirectionNum>
<DirectionText>West to Naylor Rd Station</DirectionText>
<Minutes>40</Minutes>
<RouteID>C14</RouteID>
<VehicleID>6139</VehicleID>
</NextBusPrediction>
UPDATE: here's 6140 as well
No new rehabs yet, but here's something interesting......
<NextBusPrediction>[/size]<DirectionNum>1</DirectionNum><DirectionText>South to Suitland Station</DirectionText><Minutes>67</Minutes><RouteID>V12</RouteID><VehicleID>2651</VehicleID>[/size]</NextBusPrediction>
Also, 6013 is back online
[/size]<NextBusPrediction>[/size]<DirectionNum>1</DirectionNum><DirectionText>East to Pointer Ridge</DirectionText><Minutes>79</Minutes><RouteID>C21</RouteID><VehicleID>6013</VehicleID>[/size]</NextBusPrediction>
Isn't #2650 and #2651 still at Bladensburg depot?
Found one! Here's 6151.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>74</Minutes><RouteID>D12</RouteID><VehicleID>6151</VehicleID></NextBusPrediction>
Found another, here's 6217
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Bwi - Thurgood Marshall Airport</DirectionText><Minutes>10</Minutes><RouteID>
B30</RouteID><VehicleID>
6217</VehicleID>
</NextBusPrediction>Quote from: Chargerdodge9 on May 05, 2014, 10:44:06 AM
Isn't #2650 and #2651 still at Bladensburg depot?
Yes, as it turns out, it was 4249 that was on the V12, not 2651.
UPDATE:
6183 is back
<NextBusPrediction>[/size]<DirectionNum>1</DirectionNum><DirectionText>North to Capital Plaza</DirectionText><Minutes>71</Minutes><RouteID>
A12</RouteID><VehicleID>
6183</VehicleID>
[/size]</NextBusPrediction>
Made a few observations while I was out yesterday:
-#2182 is back at Royal street Depot.
-West Ox depot now gained XDE40s #7057 and 7058 as I saw both of them in service yesterday (#7058 was on the 1E IIRC).
-West Ox also got back #6390-6396. DE42LFA #6394 seemed to have been repainted recently as it has the red curve under the windshield that you see under Xcelsior hybrids and Orion VIIs.
- Also returning to West Ox is #7041. That bus was on the 1B yesterday afternoon. Also, I spotted PRTC #250 in training around Woodbridge yesterday afternoon.
6154 is back, still no sign of 6016 as of yet.
<NextBusPrediction>
<DirectionNum>0</DirectionNum>
<DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText>
<Minutes>39</Minutes>
<RouteID>
U5</RouteID>
<VehicleID>
6154</VehicleID>
</NextBusPrediction>
Quote from: Chargerdodge9 on May 14, 2014, 07:06:07 AMDE42LFA #6394 seemed to have been repainted recently as it has the red curve under the windshield that you see under Xcelsior hybrids and Orion VIIs.
Sweet! The only thing I don't like from this is that when the time comes for those buses to be rehabbed, it will be harder to determine which ones are rehabbed unless you look closely and see a rehab number on the front. Do you remember seeing the "local" decals on that bus, whether or not they have been removed?
Quote from: NewFlyer9736BCT on May 21, 2014, 09:57:16 AM
6154 is back, still no sign of 6016 as of yet.
<NextBusPrediction>
<DirectionNum>0</DirectionNum>
<DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText>
<Minutes>39</Minutes>
<RouteID>U5</RouteID>
<VehicleID>6154</VehicleID>
</NextBusPrediction>
Until now!
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Prince Georges Plaza Station</DirectionText><Minutes>9</Minutes><RouteID>
C4</RouteID><VehicleID>
6016</VehicleID></NextBusPrediction>
EDIT: 6035 is also back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Shady Grove Station</DirectionText><Minutes>63</Minutes><RouteID>
Q6</RouteID><VehicleID>
6035</VehicleID></NextBusPrediction>
Quote from: NewFlyer9736BCT on May 21, 2014, 09:57:16 AM
6154 is back, still no sign of 6016 as of yet.
<NextBusPrediction>
<DirectionNum>0</DirectionNum>
<DirectionText>Loop to Mayfair-Marshall Hts-Lincoln Hts</DirectionText>
<Minutes>39</Minutes>
<RouteID>U5</RouteID>
<VehicleID>6154</VehicleID>
</NextBusPrediction>
Quote from: Chargerdodge9 on May 14, 2014, 07:06:07 AMDE42LFA #6394 seemed to have been repainted recently as it has the red curve under the windshield that you see under Xcelsior hybrids and Orion VIIs.
Sweet! The only thing I don't like from this is that when the time comes for those buses to be rehabbed, it will be harder to determine which ones are rehabbed unless you look closely and see a rehab number on the front. Do you remember seeing the "local" decals on that bus, whether or not they have been removed?
Actually, I don't remember looking to see if the bus still had that feature. I might go out fanning this Friday to take a better look at what's going on with West Ox as I rarely report about them anymore.
6203 is back
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>East to Prince Georges Plaza Station</DirectionText><Minutes>17</Minutes><RouteID>C4</RouteID><VehicleID>6203</VehicleID></NextBusPrediction>
Also I heard 5409 has been rehabbed, and should be back in service now
UPDATE: 6189 has also returned
<NextBusPrediction>[/size]<DirectionNum>0</DirectionNum><DirectionText>North to Laurel</DirectionText><Minutes>25</Minutes><RouteID>87</RouteID><VehicleID>6189</VehicleID>[/size]</NextBusPrediction>
So has 6044.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to New Carrollton Station</DirectionText><Minutes>51</Minutes><RouteID>B21</RouteID><VehicleID>6044</VehicleID></NextBusPrediction>
6173 is back
<NextBusPrediction>[/size][/font][/size]<DirectionNum>1</DirectionNum><DirectionText>South to Suitland Station</DirectionText><Minutes>23</Minutes><RouteID>V12</RouteID><VehicleID>6173</VehicleID>[/size]</NextBusPrediction>
And here's 6122, just like you said.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Anacostia Station</DirectionText><Minutes>38</Minutes><RouteID>W4</RouteID><VehicleID>6122</VehicleID></NextBusPrediction>
Slightly off topic, but does anyone know where NABI BRT-42 #8001 is at this time? I think it's on property, but I don't know where? Also, any info as to when the production buses will arrive?
5403 and 5419 are back online. Although, I don't think 5419 is rehabbed yet. We'll see
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Lafayette Square</DirectionText><Minutes>22</Minutes><RouteID>X2</RouteID><TripID>6356673</TripID><VehicleID>5403</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Lafayette Square</DirectionText><Minutes>15</Minutes><RouteID>X2</RouteID><TripID>6356672</TripID><VehicleID>5419</VehicleID></NextBusPrediction>
UPDATE:
FINALLY after several months, 6201 is back online
<NextBusPrediction>[/size]<DirectionNum>0</DirectionNum><DirectionText>North to Burtonsville Park & Ride</DirectionText><Minutes>53</Minutes><RouteID>Z6</RouteID><TripID>6358914</TripID><VehicleID>6201</VehicleID>[/size]</NextBusPrediction>
6159 on the X2.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Minnesota Ave Station</DirectionText><Minutes>8</Minutes><RouteID>X2</RouteID><TripID>6356537</TripID><VehicleID>6159</VehicleID></NextBusPrediction>
6125 is back (attachment)
UPDATE:
6172 is back as well. I think when I saw it online a few weeks ago, it was a test or something, I knew it was too early...
<NextBusPrediction>[/size]<DirectionNum>1</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>8</Minutes><RouteID>G12</RouteID><TripID>6371893</TripID><VehicleID>6172</VehicleID>[/size]</NextBusPrediction>
6156 has returned.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>South to Anacostia Station</DirectionText><Minutes>24</Minutes><RouteID>U2</RouteID><TripID>6453190</TripID><VehicleID>6156</VehicleID></NextBusPrediction>
EDIT: 6210 is also back online (I know its rehab # has already been tallied).
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Lakeforest</DirectionText><Minutes>8</Minutes><RouteID>J9</RouteID><TripID>6475051</TripID><VehicleID>6210</VehicleID></NextBusPrediction>
DOUBLE EDIT: And 6212 is also back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>North to Bwi - Thurgood Marshall Airport</DirectionText><Minutes>44</Minutes><RouteID>B30</RouteID><TripID>6475519</TripID><VehicleID>6212</VehicleID></NextBusPrediction>
6186 is back too. So it's not the last like I hoped, but at least it came back on my birthday
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>South to Deanwood Station</DirectionText><Minutes>49</Minutes><RouteID>R12</RouteID><TripID>6463223</TripID><VehicleID>6186</VehicleID></NextBusPrediction>
Also, 6217 is back online, what a relief
<NextBusPrediction>[/size]<DirectionNum>1</DirectionNum><DirectionText>South to Greenbelt Station</DirectionText><Minutes>32</Minutes><RouteID>B30</RouteID><TripID>6475550</TripID><VehicleID>6217</VehicleID>[/size]</NextBusPrediction>
Orion VII OG CNG #2674 is no longer a REX bus. Saw it earlier today at Pentagon with a local red paint scheme. Are they going to remove the REX paint from #2675-2685 as well?
Also spotted PRTC Omniride Orion V #182 on the SR/1 line this afternoon (which I missed >:().
Yay! We hit page 60!
On that note, 6121 and 6167 are back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Capitol Heights - Benning Heights</DirectionText><Minutes>22</Minutes><RouteID>U8</RouteID><TripID>6464618</TripID><VehicleID>6121</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to New Carrollton Station</DirectionText><Minutes>55</Minutes><RouteID>84</RouteID><TripID>6470786</TripID><VehicleID>6167</VehicleID></NextBusPrediction>
6117 is back (attachment)
UPDATE: And so is 6108
<NextBusPrediction>[/size]<DirectionNum>0</DirectionNum><DirectionText>East to Suitland Station</DirectionText><Minutes>3</Minutes><RouteID>D13</RouteID><TripID>6474203</TripID><VehicleID>6108</VehicleID>[/size]</NextBusPrediction>
5410 and 6109 are back online.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Lafayette Square</DirectionText><Minutes>2</Minutes><RouteID>X2</RouteID><TripID>6454351</TripID><VehicleID>5410</VehicleID></NextBusPrediction>
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>West to Naylor Rd Station</DirectionText><Minutes>72</Minutes><RouteID>C14</RouteID><TripID>6475236</TripID><VehicleID>6109</VehicleID></NextBusPrediction>
6148 has returned
And so has 6118.
<NextBusPrediction><DirectionNum>1</DirectionNum><DirectionText>South to Clinton Park & Ride</DirectionText><Minutes>29</Minutes><RouteID>C11</RouteID><TripID>6461014</TripID><VehicleID>6118</VehicleID></NextBusPrediction>
And 6204
And now 6127 is back.
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>Loop to Capitol Heights - Benning Heights</DirectionText><Minutes>36</Minutes><RouteID>U8</RouteID><TripID>6464583</TripID><VehicleID>6127</VehicleID></NextBusPrediction>
6140 is back online. I saw it in person, still not rehabbed.
Also, 6107 and 6145 are shown here but I think they were just testing the run #s
5416 is back online, not sure how long it was offline since I don't really pay attention to the 5400s (now that the 6100s are finishing up, I probably should)
<NextBusPrediction><DirectionNum>0</DirectionNum><DirectionText>East to Minnesota Ave Station</DirectionText><Minutes>13</Minutes><RouteID>X2</RouteID><TripID>6454219</TripID><VehicleID>5416</VehicleID></NextBusPrediction>
UPDATE
6029 is back online, though I know that one can't be rehabbed yet, I saw it last week unrehabbed
<NextBusPrediction>[/size]<DirectionNum>0</DirectionNum><DirectionText>West to Montgomery Mall</DirectionText><Minutes>40</Minutes><RouteID>J2</RouteID><TripID>6459097</TripID><VehicleID>6029</VehicleID>[/size]</NextBusPrediction>
6207 has returned.
<BusPosition><DateTime>2014-08-07T16:53:25</DateTime><Deviation>5.0000000000</Deviation><DirectionNum>10</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.99929</Lat><Lon>-77.097946</Lon><RouteID>J9</RouteID><TripEndTime>2014-08-07T17:28:00</TripEndTime><TripHeadsign>LAKEFOREST TC</TripHeadsign><TripID>6475046</TripID><TripStartTime>2014-08-07T16:36:00</TripStartTime><VehicleID>6207</VehicleID></BusPosition>
(Yes, this is part of the NextBus data that shows all buses. I clicked it by mistake, and to my surprise, it's fully functional again, and appears to be showing all buses, like the good old days.
Looks like Orion VII 3G Hybrid #3072 is back in service. -<BusPosition>
<DateTime>2014-08-07T18:39:40</DateTime>
<Deviation>0.0000000000</Deviation>
<DirectionNum>14</DirectionNum>
<DirectionText>EAST</DirectionText>
<Lat>38.841194</Lat>
<Lon>-76.97522</Lon>
<RouteID>W2</RouteID>
<TripEndTime>2014-08-07T18:28:00</TripEndTime>
<TripHeadsign>UNITED MEDICAL CTR</TripHeadsign>
<TripID>6458752</TripID>
<TripStartTime>2014-08-07T17:29:00</TripStartTime>
<VehicleID>3072</VehicleID>
</BusPosition>
And it seems that West Ox had just gained a new DE37LFA...
-<BusPosition>
<DateTime>2014-08-07T18:39:48</DateTime>
<Deviation>3.0000000000</Deviation>
<DirectionNum>14</DirectionNum>
<DirectionText>EAST</DirectionText>
<Lat>38.877842</Lat>
<Lon>-77.305069</Lon>
<RouteID>15M</RouteID>
<TripEndTime>2014-08-07T19:07:00</TripEndTime>
<TripHeadsign>TYSONS CRNR STA</TripHeadsign>
<TripID>6460513</TripID>
<TripStartTime>2014-08-07T18:26:00</TripStartTime>
<VehicleID>3761</VehicleID>
</BusPosition>
First NABI sighting! 8004 is at CET being tested.
<BusPosition><DateTime>2014-08-12T15:18:50</DateTime><Deviation>19.0000000000</Deviation><DirectionNum>13</DirectionNum><DirectionText>D0</DirectionText><Lat>38.941116</Lat><Lon>-76.87812</Lon><RouteID>110</RouteID><TripEndTime>2014-08-12T15:20:00</TripEndTime><TripHeadsign>[999]BLADENSBURG TEST ROUTE</TripHeadsign><TripID>6486050</TripID><TripStartTime>2014-08-12T15:00:00</TripStartTime><VehicleID>8004</VehicleID></BusPosition>
Actually 8001, 8003-8008 are online.
2801 is back online. Rehabbed? I honestly don't know...
<BusPosition><DateTime>2014-08-18T16:15:46</DateTime><Deviation>-1.0000000000</Deviation><DirectionNum>10</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.963161</Lat><Lon>-77.027779</Lon><RouteID>79</RouteID><TripEndTime>2014-08-18T16:29:00</TripEndTime><TripHeadsign>SILVER SPRING STA</TripHeadsign><TripID>6445941</TripID><TripStartTime>2014-08-18T15:43:00</TripStartTime><VehicleID>2801</VehicleID></BusPosition>
2801 is not rehabbed, I saw it the other day
Also 6014 is back online. Rehabbed? I shall find out tomorrow hopefully
<BusPosition>
<DateTime>2014-08-19T18:28:25</DateTime>
<Deviation>2.0000000000</Deviation>
<DirectionNum>14</DirectionNum>
<DirectionText>EAST</DirectionText>
<Lat>38.94857</Lat>
<Lon>-76.873329</Lon>
<RouteID>F13</RouteID>
<TripEndTime>2014-08-19T18:48:00</TripEndTime>
<TripHeadsign>FORBES NO BOSTON</TripHeadsign>
<TripID>6457309</TripID>
<TripStartTime>2014-08-19T18:00:00</TripStartTime>
<VehicleID>6014</VehicleID>
</BusPosition>
UPDATE: 6107 is back
6200 is finally back from rehab; as expected, it's at Landover.
<BusPosition><DateTime>2014-09-02T16:32:28</DateTime><Deviation>2.0000000000</Deviation><DirectionNum>12</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.923943</Lat><Lon>-76.884071</Lon><RouteID>A12</RouteID><TripEndTime>2014-09-02T17:06:00</TripEndTime><TripHeadsign>ADDISON RD STA</TripHeadsign><TripID>6802031</TripID><TripStartTime>2014-09-02T16:02:00</TripStartTime><VehicleID>6200</VehicleID></BusPosition>
EDIT: And one week later, 6145 (the last of the bunch for now) has returned. Now all that's left is to wait for the DE40LFs...
<BusPosition><DateTime>2014-09-09T16:48:00</DateTime><Deviation>3.0000000000</Deviation><DirectionNum>14</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.826622</Lat><Lon>-76.912155</Lon><RouteID>C12</RouteID><TripEndTime>2014-09-09T16:45:00</TripEndTime><TripHeadsign>BRANCH AVE STA</TripHeadsign><TripID>6794552</TripID><TripStartTime>2014-09-09T16:10:00</TripStartTime><VehicleID>6145</VehicleID></BusPosition>
Nothing new on the rehab front, but more NABIs have entered service:
<BusPosition><DateTime>2014-09-22T16:38:53</DateTime><Deviation>6.0000000000</Deviation><DirectionNum>12</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.825684</Lat><Lon>-77.283913</Lon><RouteID>17G</RouteID><TripEndTime>2014-09-22T16:45:00</TripEndTime><TripHeadsign>G MASON UNIV</TripHeadsign><TripID>6794424</TripID><TripStartTime>2014-09-22T15:55:00</TripStartTime><VehicleID>8022</VehicleID></BusPosition>
<BusPosition><DateTime>2014-09-22T16:38:40</DateTime><Deviation>7.0000000000</Deviation><DirectionNum>15</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.787106</Lat><Lon>-77.284851</Lon><RouteID>18S</RouteID><TripEndTime>2014-09-22T16:41:00</TripEndTime><TripHeadsign>SPRNGFLD-BURKE CENTRE</TripHeadsign><TripID>6789986</TripID><TripStartTime>2014-09-22T16:07:00</TripStartTime><VehicleID>8024</VehicleID></BusPosition>
<BusPosition><DateTime>2014-09-22T16:38:32</DateTime><Deviation>-1.0000000000</Deviation><DirectionNum>12</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.79192</Lat><Lon>-77.174614</Lon><RouteID>17K</RouteID><TripEndTime>2014-09-22T17:14:00</TripEndTime><TripHeadsign>KNGS PRK WE</TripHeadsign><TripID>6794412</TripID><TripStartTime>2014-09-22T16:26:00</TripStartTime><VehicleID>8027</VehicleID></BusPosition>
<BusPosition><DateTime>2014-09-22T16:38:41</DateTime><Deviation>28.0000000000</Deviation><DirectionNum>15</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.821934</Lat><Lon>-77.01622</Lon><RouteID>18S</RouteID><TripEndTime>2014-09-22T17:47:00</TripEndTime><TripHeadsign>SPRNGFLD-BURKE CENTRE</TripHeadsign><TripID>6790006</TripID><TripStartTime>2014-09-22T17:02:00</TripStartTime><VehicleID>8029</VehicleID></BusPosition>
<BusPosition><DateTime>2014-09-22T16:37:21</DateTime><Deviation>1.0000000000</Deviation><DirectionNum>12</DirectionNum><DirectionText>SOUTH</DirectionText><Lat>38.868851</Lat><Lon>-77.053177</Lon><RouteID>17L</RouteID><TripEndTime>2014-09-22T17:28:00</TripEndTime><TripHeadsign>BURKE</TripHeadsign><TripID>6794416</TripID><TripStartTime>2014-09-22T16:36:00</TripStartTime><VehicleID>8031</VehicleID></BusPosition>
Interesting, so I guess VA routes are getting the 8000 series NABI BRT 42s first. I wonder what was the hold up? PS: Has any 2007 New Flyer C40LFRs received a rehab yet?
Saw at least 3 2014 NABI BRT 42 hybrids in the normal local scheme. Only got two numbers though. #8017 was on the 29X and #8018 was on the 18 line.
FINALLY we have a rehab returning! (How long has it been, 5 weeks?) 6025 is back.
<BusPosition><DateTime>2014-10-07T16:54:35</DateTime><Deviation>-8.0000000000</Deviation><DirectionNum>10</DirectionNum><DirectionText>NORTH</DirectionText><Lat>39.100979</Lat><Lon>-77.075768</Lon><RouteID>Y7</RouteID><TripEndTime>2014-10-07T17:12:00</TripEndTime><TripHeadsign>GA AVE+ICC P&R</TripHeadsign><TripID>6837855</TripID><TripStartTime>2014-10-07T16:10:00</TripStartTime><VehicleID>6025</VehicleID></BusPosition>
5421 is also back. Could this be rehabbed? I don't know...
<BusPosition><DateTime>2014-10-07T16:54:22</DateTime><Deviation>-4.0000000000</Deviation><DirectionNum>14</DirectionNum><DirectionText>EAST</DirectionText><Lat>38.897964</Lat><Lon>-76.94722</Lon><RouteID>X2</RouteID><TripEndTime>2014-10-07T16:55:00</TripEndTime><TripHeadsign>MINNESOTA STA</TripHeadsign><TripID>6773271</TripID><TripStartTime>2014-10-07T16:12:00</TripStartTime><VehicleID>5421</VehicleID></BusPosition>
6030 has returned.
<BusPosition><DateTime>2014-10-20T10:42:00</DateTime><Deviation>0.0000000000</Deviation><DirectionNum>15</DirectionNum><DirectionText>WEST</DirectionText><Lat>39.008713</Lat><Lon>-77.11348</Lon><RouteID>J2</RouteID><TripEndTime>2014-10-20T10:53:00</TripEndTime><TripHeadsign>MONTGMRY MALL /CEDR</TripHeadsign><TripID>6778200</TripID><TripStartTime>2014-10-20T10:06:00</TripStartTime><VehicleID>6030</VehicleID></BusPosition>
EDIT: 6046 is also back online. I'm not so sure if this one's rehabbed, though...
<BusPosition><DateTime>2014-10-20T16:35:41</DateTime><Deviation>-3.0000000000</Deviation><DirectionNum>15</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.892765</Lat><Lon>-76.838112</Lon><RouteID>C26</RouteID><TripEndTime>2014-10-20T16:41:00</TripEndTime><TripHeadsign>LARGO TOWN CTR</TripHeadsign><TripID>6777373</TripID><TripStartTime>2014-10-20T16:20:00</TripStartTime><VehicleID>6046</VehicleID></BusPosition>
6002 has returned.
<BusPosition><DateTime>2014-10-27T17:10:24</DateTime><Deviation>3.0000000000</Deviation><DirectionNum>15</DirectionNum><DirectionText>WEST</DirectionText><Lat>38.947128</Lat><Lon>-76.826012</Lon><RouteID>B29</RouteID><TripEndTime>2014-10-27T17:12:00</TripEndTime><TripHeadsign>NEW CARROLTON (NO PR)</TripHeadsign><TripID>6794630</TripID><TripStartTime>2014-10-27T16:47:00</TripStartTime><VehicleID>6002</VehicleID></BusPosition>
EDIT: And so has 6003.
<BusPosition><DateTime>2014-11-03T16:40:04</DateTime><Deviation>-2.0000000000</Deviation><DirectionNum>10</DirectionNum><DirectionText>NORTH</DirectionText><Lat>38.850967</Lat><Lon>-76.955948</Lon><RouteID>F14</RouteID><TripEndTime>2014-11-03T17:50:00</TripEndTime><TripHeadsign>NEW CARROLTON STA</TripHeadsign><TripID>6764755</TripID><TripStartTime>2014-11-03T16:42:00</TripStartTime><VehicleID>6003</VehicleID></BusPosition>