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.

NewFlyer9736BCT

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

Orion 1200

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.

RideOn5905

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.

RideOn5905

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>

Orion 1200

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.

NewFlyer9736BCT

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

RideOn5905

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>

NewFlyer9736BCT

5320 finally back online

<vehicle id="5320" lat="38.947784" lon="-77.031967" secsSinceReport="21183" predictable="false" heading="-4" speedKmHr="0.0" />
Route Q2. Destination: Silver Spring Station

RideOn5905

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>

NewFlyer9736BCT

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

RideOn5905

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

NewFlyer9736BCT

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

RideOn5905

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>

RideOn5905

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>

RideOn5905

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