November 2008 Observation Photos

[LandoverDivision]

Thumbnails are easier to work with.  But you all may want to consider shrinking the photos so they can actually be seen without scrolling left to right, which can be difficult if the bar is at the bottom of your post.  Easy Thumbnails is freeware that does this easily, and I use it to make the file sizes for both photos I post to boards and to my website easier to manage for those wishing to view them.

That's the same thing I was thinking about. I hate to have to do that myself. I know just how to shrink them.

[79MetroExtraMD]

Last set. I'm posting 5 because it keeps timing out.

LMAO 89M Dunn Loring Station.

And the ironic part. I didn't notice I took that until I got home and looked thru my snaps. I guess it was a spur of the moment type of things.

[C40LF_2464]

Well here are some of my photos


and this pic of the C40LFR was at PG when i was hanging out with Brandon (Landover division)

[OrionFlyer]

When did Bladensburg have the Orion VI's?

[LandoverDivision]

When did Bladensburg have the Orion VI's?

Back in 2000-2001 when WMATA first got them. I remember riding them on the 90/92, B2. I saw them on the 80 and the G8 also.

[Tristan]

How did

When did Bladensburg have the Orion VI's?

Where did that come from?

Brandon: Well, they look like DASH buses to me :-)

[LandoverDivision]

How did

When did Bladensburg have the Orion VI's?

Where did that come from?

Brandon: Well, they look like DASH buses to me :-)

Ok smart one. I was asking what did you think of the pictures? Are they photo gallery worth?

[Tristan]

Actually I guess the lighting was on your side for the two DASH shots, so yea...wouldn't hurt to add them.

[Scrabbleship]

Last set. I'm posting 5 because it keeps timing out.

LMAO 89M Dunn Loring Station.

Last set. I'm posting 5 because it keeps timing out.

LMAO 89M Dunn Loring Station.

Well, it is ripping off the Virginia system of route numbering...

I know Montgomery is one to sometimes have buses on deadhead/layover display weird destinations that don't match to the route, Northern sometimes too (on the last day of the old bus setup at Silver Spring, the "92" made a cameo there) but Landover? Good for them though!

[WMATAGMOAGH]

Just minor driver errors, that is all.  I've seen these over the years, among others:

T3 ROCKVILLE STA instead of T2 ROCKVILLE STA
J7 FEDERAL TRIANGLE instead of N7 FEDERAL TRIANGLE

[LandoverDivision]

Just minor driver errors, that is all.  I've seen these over the years, among others:

T3 ROCKVILLE STA instead of T2 ROCKVILLE STA
J7 FEDERAL TRIANGLE instead of N7 FEDERAL TRIANGLE

Yeah that's true. It's not new for me t see it. I've seen thise happen plenty of times with Landover buses. Sometimes, the drivers are trying to switch it, but it says other things. For instance, on the F8, it said F80 CHEVERLY STATION, or the two buses that says 3839 instead of the route number.  Another example: when the F1 said something something High School. It happens a lot but it's nothing really. Just a couple of errors with the sign is all.

[OrionFlyer]

Can somebody explain to me how exactly the operator can make those errors when putting the code in for the destination when using the actual sign panel?

Like "T2 Jermantown" with a J instead of a G. But wait, the T2 does go all the way up to Germantown

And also since when is Q2 Q<>2? Saw that on a few buses a couple of days ago. Excuse what time does the Q less than greater than 2 comes? LOL

[RailBus63]

Just minor driver errors, that is all.  I've seen these over the years, among others:

T3 ROCKVILLE STA instead of T2 ROCKVILLE STA
J7 FEDERAL TRIANGLE instead of N7 FEDERAL TRIANGLE

How does WMATA number its destination sign codes for the lettered routes?  Using this example, it's possible that the codes for T2 and T3 are very similar and the driver entered the wrong code on the keypad.

Can somebody explain to me how exactly the operator can make those errors when putting the code in for the destination when using the actual sign panel?

Like "T2 Jermantown" with a J instead of a G. But wait, the T2 does go all the way up to Germantown

And also since when is Q2 Q<>2? Saw that on a few buses a couple of days ago. Excuse what time does the Q less than greater than 2 comes? LOL

Those would be errors in the sign programming.

[rideonrulez]

Can somebody explain to me how exactly the operator can make those errors when putting the code in for the destination when using the actual sign panel?

Like "T2 Jermantown" with a J instead of a G. But wait, the T2 does go all the way up to Germantown

And also since when is Q2 Q<>2? Saw that on a few buses a couple of days ago. Excuse what time does the Q less than greater than 2 comes? LOL

"Jermantown" is an actual destination for the 2B. Short trippers use to terminate on "Jermantown Rd" over by Fairfax City.

The reason why you find route numbers such as "Q<>2" and other such things is because the operators turn off the clever devices by doing that.

[OrionFlyer]

Can somebody explain to me how exactly the operator can make those errors when putting the code in for the destination when using the actual sign panel?

Like "T2 Jermantown" with a J instead of a G. But wait, the T2 does go all the way up to Germantown

And also since when is Q2 Q<>2? Saw that on a few buses a couple of days ago. Excuse what time does the Q less than greater than 2 comes? LOL

"Jermantown" is an actual destination for the 2B. Short trippers use to terminate on "Jermantown Rd" over by Fairfax City.

The reason why you find route numbers such as "Q<>2" and other such things is because the operators turn off the clever devices by doing that.

Yeah but how did the driver but T2 Jermantown? This is from a picture btw.