Nextbus Observations

DCAreaTransitFan · December 05, 2011, 02:39:56 PM

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>

NewFlyer9736BCT · December 05, 2011, 03:00:34 PM

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

RideOn5905 · December 05, 2011, 06:18:04 PM

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.

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

RideOn5905 · December 07, 2011, 07:46:48 PM

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.

C40LF_2464 · December 09, 2011, 11:39:31 AM

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

RideOn5905 · December 09, 2011, 03:00:30 PM

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>

NewFlyer9736BCT · December 10, 2011, 07:18:41 PM

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

RideOn5905 · 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>

RideOn5905 · December 12, 2011, 10:56:16 PM

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.

RideOn5905 · 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>

NewFlyer9736BCT · December 14, 2011, 01:59:49 PM

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

RideOn5905 · December 14, 2011, 03:05:01 PM

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>

RideOn5905 · December 17, 2011, 05:19:24 PM

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>

NewFlyer9736BCT · December 18, 2011, 10:01:30 PM

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

News:

Nextbus Observations