News:

No news is good news :-)

Main Menu

Nextbus Observations

Started by 79MetroExtraMD, August 27, 2010, 06:08:20 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

OrionFlyer

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"/>

Blue Line Shuttle to Franconia-Springfield.



Want me to make a destination sign for you? Just send me a PM and I'll have it made in no time.

79MetroExtraMD

#556
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
"Route 79, Limited Stop, destination: Archives"
Follow me on Twitter: @kencon06

NewFlyer9736BCT

#557
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
Route Q2. Destination: Silver Spring Station

RideOn5905

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>

DCAreaTransitFan

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
New Flyer C40LFR

OrionFlyer

#560
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>
Blue Line Shuttle to Franconia-Springfield.



Want me to make a destination sign for you? Just send me a PM and I'll have it made in no time.

RideOn5905

#561
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>

NewFlyer9736BCT

#562
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"/>
Route Q2. Destination: Silver Spring Station

RideOn5905

#563
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>

RideOn5905

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>

RideOn5905

#565
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>

RideOn5905

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>

C40LF_2464

A good amount of the new 3000's are online.

NewFlyer9736BCT

Even though 5320 is still offline, I found this picture on Facebook


Route Q2. Destination: Silver Spring Station

RideOn5905

Quote from: NewFlyer9736BCT on May 27, 2012, 11:05:55 AM
Even though 5320 is still offline, I found this picture on Facebook



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...