News:

The server restarts at 2 AM and 6 PM Eastern Time daily. This results in a short period of downtime, so if you get a 502 error at those times, that is why.
- Alex

Main Menu

Maryland

Started by Alps, May 22, 2011, 12:10:09 AM

Previous topic - Next topic

ixnay

Another moveable bridge on the Eastern Shore has been replaced on MD 331 between Easton and Preston...

http://www.stardem.com/spotlight/new-dover-bridge-officially-opens/article_f9c67e80-e3d0-5f48-bfb1-b036ace7fb29.html

ixnay


TheOneKEA

This was released earlier today by the MDTA. Personally I'm quite pleased at the outbreak of common sense, but still annoyed that the additional funds won't pay for a complete quad carriageway up to MD 543. When the revised plans are released I will be interested to see if the interchange and ROW reconstruction will include passive provision to widen the southbound side to build the missing ETL carriageway.

HOGAN ADMINISTRATION ADDS $890 MILLION TO EXTEND I-95 EXPRESS TOLL LANES TO HARFORD COUNTY

Jmiles32

Quote from: TheOneKEA on June 15, 2018, 05:13:54 PM
This was released earlier today by the MDTA. Personally I'm quite pleased at the outbreak of common sense, but still annoyed that the additional funds won't pay for a complete quad carriageway up to MD 543. When the revised plans are released I will be interested to see if the interchange and ROW reconstruction will include passive provision to widen the southbound side to build the missing ETL carriageway.
^Agreed.

http://www.baltimoresun.com/news/maryland/harford/aegis/ph-ag-expanded-express-toll-lanes-plan-0620-story.html
QuoteIn addition to building the two express lanes farther out into Harford County, the interchanges at Route 152 in Joppa and Route 24 will be reconstructed, so motorists can exit to them directly from the express lanes.

The interchange work at Route 152 also will involve changes to the existing park and ride logs, according to MDTA.

Reconstruction of the Route 24 interchange includes a two-lane flyover ramp toward Bel Air, alleviating congestion for motorists exiting I-95 to routes 24 and 924, MDTA said.

$890 million seems like way too much for whats being added on here. Its also important to note that this project is scheduled to begin in 2019 and end in 2026, something I'm sure will annoy the hell out of locals. IMHO the whole I-95 ETL project north of Baltimore should have been built under a P3 deal such as the express lanes in NOVA. However, Maryland's upcoming plans for I-495 and I-270 show that the state is learning.
Aspiring Transportation Planner at Virginia Tech. Go Hokies!

vdeane

Except that the P3 for the VA express lanes has its issues.  Namely, TransUrban does not consult the E-ZPass database in the event of a blown read.  They just send out a violation notice with exorbitant fees.
Please note: All comments here represent my own personal opinion and do not reflect the official position of NYSDOT or its affiliates.

Jmiles32

Quote from: vdeane on June 18, 2018, 12:00:53 AM
Except that the P3 for the VA express lanes has its issues.

Don't get me wrong, I am by no means defending those deals. The I-95 one in particular was horrendous. Yet terms of time and efficiency, while the 8-mile I-95 ETLS took 8 years to build(2006 to 2014), the far more complex 14-mile I-495 HOT lanes took only 4(2008 to 2012). Hell, the 22-mile Transform I-66 is projected to take only 4 years too(2018 to 2022). Would Maryland have gotten a good deal on the initial I-95 ETL project? Probably not. However, after seeing what a decent P3 deal can look like(I-66 IMO), I think Maryland could get way more bang for their buck with a P3 deal here. I would have much rather saw that extra $890 million go towards widening I-81.
Aspiring Transportation Planner at Virginia Tech. Go Hokies!

Beltway

Quote from: vdeane on June 18, 2018, 12:00:53 AM
Except that the P3 for the VA express lanes has its issues.  Namely, TransUrban does not consult the E-ZPass database in the event of a blown read.  They just send out a violation notice with exorbitant fees.

Not in my experience.  The E-ZPass online interface shows that it takes 5 days or more for my I-95 and I-495 transactions to post and deduct the toll after the trip.  One of the ETC experts on Facebook told me that is because they take that much time in order to fully verify the transaction.
http://www.roadstothefuture.com
http://www.capital-beltway.com

Baloney is a reserved word on the Internet
    (Robert Coté, 2002)

Beltway

Quote from: Jmiles32 on June 18, 2018, 11:23:10 AM
Quote from: vdeane on June 18, 2018, 12:00:53 AM
Except that the P3 for the VA express lanes has its issues.
Don't get me wrong, I am by no means defending those deals. The I-95 one in particular was horrendous. Yet terms of time and efficiency, while the 8-mile I-95 ETLS took 8 years to build(2006 to 2014), the far more complex 14-mile I-495 HOT lanes took only 4(2008 to 2012). Hell, the 22-mile Transform I-66 is projected to take only 4 years too(2018 to 2022). Would Maryland have gotten a good deal on the initial I-95 ETL project? Probably not. However, after seeing what a decent P3 deal can look like(I-66 IMO), I think Maryland could get way more bang for their buck with a P3 deal here. I would have much rather saw that extra $890 million go towards widening I-81.

Same with the Elizabeth River Tunnels project.  Massive $1.4 billion P3 project to build a new tunnel, major rehabs of the 3 older tunnels, extend the MLK Freeway.  On time and on budget, 2012-2016.  Pain in re-tolling the tunnels notwithstanding.
http://www.roadstothefuture.com
http://www.capital-beltway.com

Baloney is a reserved word on the Internet
    (Robert Coté, 2002)

vdeane

Quote from: Beltway on June 18, 2018, 01:16:08 PM
Quote from: vdeane on June 18, 2018, 12:00:53 AM
Except that the P3 for the VA express lanes has its issues.  Namely, TransUrban does not consult the E-ZPass database in the event of a blown read.  They just send out a violation notice with exorbitant fees.

Not in my experience.  The E-ZPass online interface shows that it takes 5 days or more for my I-95 and I-495 transactions to post and deduct the toll after the trip.  One of the ETC experts on Facebook told me that is because they take that much time in order to fully verify the transaction.
I think this may have resulted in a lawsuit ending with a court order to check the database.

Quote from: Beltway on June 18, 2018, 01:21:33 PM
Quote from: Jmiles32 on June 18, 2018, 11:23:10 AM
Quote from: vdeane on June 18, 2018, 12:00:53 AM
Except that the P3 for the VA express lanes has its issues.
Don't get me wrong, I am by no means defending those deals. The I-95 one in particular was horrendous. Yet terms of time and efficiency, while the 8-mile I-95 ETLS took 8 years to build(2006 to 2014), the far more complex 14-mile I-495 HOT lanes took only 4(2008 to 2012). Hell, the 22-mile Transform I-66 is projected to take only 4 years too(2018 to 2022). Would Maryland have gotten a good deal on the initial I-95 ETL project? Probably not. However, after seeing what a decent P3 deal can look like(I-66 IMO), I think Maryland could get way more bang for their buck with a P3 deal here. I would have much rather saw that extra $890 million go towards widening I-81.

Same with the Elizabeth River Tunnels project.  Massive $1.4 billion P3 project to build a new tunnel, major rehabs of the 3 older tunnels, extend the MLK Freeway.  On time and on budget, 2012-2016.  Pain in re-tolling the tunnels notwithstanding.
Didn't one of the tunnel P3s result in VDOT being unable to improve another facility if they don't pay a penalty?
Please note: All comments here represent my own personal opinion and do not reflect the official position of NYSDOT or its affiliates.

1995hoo

Quote from: vdeane on June 18, 2018, 12:00:53 AM
Except that the P3 for the VA express lanes has its issues.  Namely, TransUrban does not consult the E-ZPass database in the event of a blown read.  They just send out a violation notice with exorbitant fees.

That's not entirely true. Last year when Ms1995hoo bought a new car over Memorial Day weekend, I added it to our E-ZPass (Virginia) account before we left the dealer. We drove it in the I-95 HO/T lanes without an E-ZPass on the way home and it was properly charged to our E-ZPass account because I had the plate registered.
"You know, you never have a guaranteed spot until you have a spot guaranteed."
—Olaf Kolzig, as quoted in the Washington Times on March 28, 2003,
commenting on the Capitals clinching a playoff spot.

"That sounded stupid, didn't it?"
—Kolzig, to the same reporter a few seconds later.

Beltway

Quote from: vdeane on June 18, 2018, 08:34:22 PM
Quote from: Beltway on June 18, 2018, 01:16:08 PM
Same with the Elizabeth River Tunnels project.  Massive $1.4 billion P3 project to build a new tunnel, major rehabs of the 3 older tunnels, extend the MLK Freeway.  On time and on budget, 2012-2016.  Pain in re-tolling the tunnels notwithstanding.
Didn't one of the tunnel P3s result in VDOT being unable to improve another facility if they don't pay a penalty?

No:

Q: Will ERC receive additional compensation related to other transportation improvements in Hampton Roads?

A: The Project will not prohibit the future development of any other projects in the Hampton Roads region.  If the Commonwealth opens a competing facility during the term of the Midtown Tunnel agreement, ERC may make a claim if the revenues needed to pay back the financing for the Midtown Tunnel Project decreases because of that facility.  ERC must comply with strict notice requirements in order to make a claim and ERC bears the burden of proof in demonstrating revenue impacts.  There is no guaranteed compensation.

https://www.driveert.com/project-resources/faq/
http://www.roadstothefuture.com
http://www.capital-beltway.com

Baloney is a reserved word on the Internet
    (Robert Coté, 2002)

froggie

It wasn't a tunnel P3, but there was such a clause at least considered for either the Beltway or the initial 95/395 HO/T lanes.  I recall it being a big stink up in NoVA when the 95/395 HO/T lanes were being planned.

Beltway

#1536
Quote from: froggie on June 19, 2018, 09:40:55 AM
It wasn't a tunnel P3, but there was such a clause at least considered for either the Beltway or the initial 95/395 HO/T lanes.  I recall it being a big stink up in NoVA when the 95/395 HO/T lanes were being planned.

There is all kinds of misinformation being propagated about P3 projects regarding that issue. 
All the VA P3 projects are handled in their comprehensive agreements like as in the ERT cite that I posted yesterday.


http://www.roadstothefuture.com
http://www.capital-beltway.com

Baloney is a reserved word on the Internet
    (Robert Coté, 2002)

froggie

^ The administration of the governor at the time was being a bit secretive about project details, which certainly didn't help the misinformation situation.  Had they been more upfront, the miscommunications would have been largely avoided.

Jmiles32

http://www.baltimoresun.com/news/maryland/bs-md-feds-studying-295-transfer-20180625-story.html
QuoteThe federal government has agreed to study ways of transferring ownership of a 19-mile stretch of the Baltimore-Washington Parkway (Interstate 295) to Maryland, federal and state officials announced Monday – a key step in Gov. Larry Hogan's $9 billion highway expansion plan.

Hogan and U.S. Secretary of the Interior Ryan Zinke have signed a non-binding general agreement to "explore potential legislative solutions"  to transfer or exchange the expressway section that runs through Prince George's and Anne Arundel counties, the governor announced.

In a statement, Zinke expressed optimism for a potential trade for "land more suited to the mission of the National Park Service,"  which manages the parkway under the Interior Department.

The highway, which runs between Baltimore and Washington, carries about 120,000 commuters per day.

"The Department of the Interior is not in the business of managing commuter highways,"  Zinke said. "It makes sense to explore a potential exchange of a highway for land that is more suited to the mission of the National Park Service."

Neither Hogan nor Zinke indicated what Maryland-owned land might be considered for such a trade.

Announced last year, Hogan's plan involves widening highways by adding hundreds of miles of express toll lanes to I-295, I-270 and I-495 – the Capital Beltway.

Expanding I-295 would require the federal government to turn over the highway to the state. The Maryland Transportation Authority would build, operate and maintain the lanes, the governor said.

"While no decisions have been made, the agreement provides a framework for [the Interior Department] to collaborate with Governor Hogan and the state of Maryland to evaluate all possibilities,"  the Interior Department said in its announcement.

Looks increasing likely that the Feds will transfer ownership of B-W Parkway thus giving Maryland the green light to go ahead and build express lanes. Additionally, I found it interesting how this article and others similar kept referring to the Baltimore-Washington Parkway(MD-295) as I-295. Do most locals refer to it such?
Aspiring Transportation Planner at Virginia Tech. Go Hokies!

TheOneKEA

Very few people refer to that segment of MD 295 as I-295. It's usually referred to as the B-W Parkway, the Parkway, or "295" . The SHA maintains a complete log of the route in the relevant Highway Location Reference PDFs, and in those documents it is logged as MD 295 throughout.

abefroman329

When living in DC, I thought of the entire route from I-295 north to be DC/MD-295.

Personally, and all other things being equal, I'd prefer they pursued a new or upgraded route that would mean the B/W Parkway didn't need to be used as a commuter route at all.  I don't see how you upgrade it without destroying its character, and I'd hate to see something similar happen to the GW Parkway, Rock Creek Parkway, or any other NPS-maintained road.

Roadsguy

The very first short section in MD from the state line to US 50 is actually MD 201. 201 goes off on its own road at that interchange, and north of there is the unnumbered (though internally MD 295) NPS-owned B-W Parkway.
Mileage-based exit numbering implies the existence of mileage-cringe exit numbering.

Jmiles32

Quote from: abefroman329 on June 27, 2018, 03:35:35 PM
Personally, and all other things being equal, I'd prefer they pursued a new or upgraded route that would mean the B/W Parkway didn't need to be used as a commuter route at all.  I don't see how you upgrade it without destroying its character, and I'd hate to see something similar happen to the GW Parkway, Rock Creek Parkway, or any other NPS-maintained road.

I think the B/W Parkway could be widened to 6 lanes without destroying too much of its character, as has already been done closer to Baltimore. 8 lanes though? Highly unlikely. IMO I-95 between the Beltways is the one that should get four new HOT lanes while the B/W Parkway between the Beltways should be converted to rush hour HOT lanes similar to I-66 inside the Beltway. Use the toll revenue collected from these HOT lanes to complete six laneing the B/W Parkway.
Aspiring Transportation Planner at Virginia Tech. Go Hokies!

cpzilliacus

Quote from: Jmiles32 on June 28, 2018, 09:03:02 AM
Quote from: abefroman329 on June 27, 2018, 03:35:35 PM
Personally, and all other things being equal, I'd prefer they pursued a new or upgraded route that would mean the B/W Parkway didn't need to be used as a commuter route at all.  I don't see how you upgrade it without destroying its character, and I'd hate to see something similar happen to the GW Parkway, Rock Creek Parkway, or any other NPS-maintained road.

I think the B/W Parkway could be widened to 6 lanes without destroying too much of its character, as has already been done closer to Baltimore. 8 lanes though? Highly unlikely. IMO I-95 between the Beltways is the one that should get four new HOT lanes while the B/W Parkway between the Beltways should be converted to rush hour HOT lanes similar to I-66 inside the Beltway. Use the toll revenue collected from these HOT lanes to complete six laneing the B/W Parkway.

All Maryland toll roads and toll crossings (with two minor exceptions along the Potomac River, White's Ferry and the Oldtown Toll Bridge, both of which are privately-owned and regulated by the Maryland Public Service Commission) have (since the early 1970's) been run by the MDTA, and as a result, all debt issued is "non-recourse" toll revenue bonds, secured by the revenues collected by all Maryland toll facilities in one "basket."  That lowers the risk of default and the interest rate too.  Holders of Maryland toll revenue bonds cannot look to state taxpayers to pay them back in the event of default, hence "non-recourse."
Opinions expressed here on AAROADS are strictly personal and mine alone, and do not reflect policies or positions of MWCOG, NCRTPB or their member federal, state, county and municipal governments or any other agency.

cpzilliacus

Quote from: Roadsguy on June 28, 2018, 12:30:19 AM
The very first short section in MD from the state line to US 50 is actually MD 201. 201 goes off on its own road at that interchange, and north of there is the unnumbered (though internally MD 295) NPS-owned B-W Parkway.

It is an internal reference route by the state only (in the style of New York State reference routes), but as far as the National Park Service is concerned, the federal part of the road is simply the Baltimore-Washington Parkway.
Opinions expressed here on AAROADS are strictly personal and mine alone, and do not reflect policies or positions of MWCOG, NCRTPB or their member federal, state, county and municipal governments or any other agency.

abefroman329

Quote from: Roadsguy on June 28, 2018, 12:30:19 AM
The very first short section in MD from the state line to US 50 is actually MD 201. 201 goes off on its own road at that interchange, and north of there is the unnumbered (though internally MD 295) NPS-owned B-W Parkway.

It's not unnumbered - here is one example:

https://www.google.com/maps/@39.1849487,-76.6750159,3a,75y,264.49h,107.3t/data=!3m6!1e1!3m4!1sfF7MgJI1JxAo9mFZDdn-bA!2e0!7i13312!8i6656

Jmiles32

Quote from: abefroman329 on June 28, 2018, 10:46:56 AM
Quote from: Roadsguy on June 28, 2018, 12:30:19 AM
The very first short section in MD from the state line to US 50 is actually MD 201. 201 goes off on its own road at that interchange, and north of there is the unnumbered (though internally MD 295) NPS-owned B-W Parkway.

It's not unnumbered - here is one example:

https://www.google.com/maps/@39.1849487,-76.6750159,3a,75y,264.49h,107.3t/data=!3m6!1e1!3m4!1sfF7MgJI1JxAo9mFZDdn-bA!2e0!7i13312!8i6656

The B/W Parkway is unnumbered from the US-50/MD-201 interchange to the MD-175 interchange. Heres an example of its interchange with the Capital Beltway: https://www.google.com/maps/@38.9945939,-76.8888901,3a,25.4y,151.66h,93.44t/data=!3m6!1e1!3m4!1sV7OgHidVSQBcDAaAg0r6Tg!2e0!7i13312!8i6656?hl=en&authuser=0

North of MD-175 the state picks up ownership of the road and signs it as MD-295.
Aspiring Transportation Planner at Virginia Tech. Go Hokies!

Roadsguy

Yes, that's what I meant. Maryland sees the entire Parkway as MD 295, but the NPS section has no signed number. It's like PennDOT using 7076 and other 7xxx designations for the Turnpike roads that they don't own or maintain.

The weird thing about MD 201 though is that it's actually signed (at least from some places) on the connecting segment to DC 295. I don't think there's any mention of DC 295 at all in MD, only To I-295.
Mileage-based exit numbering implies the existence of mileage-cringe exit numbering.

cpzilliacus

Quote from: Roadsguy on June 28, 2018, 11:07:58 AM
Yes, that's what I meant. Maryland sees the entire Parkway as MD 295, but the NPS section has no signed number. It's like PennDOT using 7076 and other 7xxx designations for the Turnpike roads that they don't own or maintain.

The weird thing about MD 201 though is that it's actually signed (at least from some places) on the connecting segment to DC 295. I don't think there's any mention of DC 295 at all in MD, only To I-295.
[/quote

The signs on the southbound side of the Baltimore-Washington Parkway and most of them on U.S. 50 east and west of the interchange pre-date the official designation of Kenilworth Avenue, N.E. and the northern part of the Anacostia Freeway as SR (or D.C.) 295.  Hence TO I-295.  Were the signs to be replaced now, I think there would be reference to D.C. 295.
Opinions expressed here on AAROADS are strictly personal and mine alone, and do not reflect policies or positions of MWCOG, NCRTPB or their member federal, state, county and municipal governments or any other agency.

Roadsguy

Quote from: cpzilliacus on June 28, 2018, 11:23:03 AM
Quote from: Roadsguy on June 28, 2018, 11:07:58 AM
Yes, that's what I meant. Maryland sees the entire Parkway as MD 295, but the NPS section has no signed number. It's like PennDOT using 7076 and other 7xxx designations for the Turnpike roads that they don't own or maintain.

The weird thing about MD 201 though is that it's actually signed (at least from some places) on the connecting segment to DC 295. I don't think there's any mention of DC 295 at all in MD, only To I-295.

The signs on the southbound side of the Baltimore-Washington Parkway and most of them on U.S. 50 east and west of the interchange pre-date the official designation of Kenilworth Avenue, N.E. and the northern part of the Anacostia Freeway as SR (or D.C.) 295.  Hence TO I-295.  Were the signs to be replaced now, I think there would be reference to D.C. 295.

Oh really? How long ago was DC 295 first signed? Did it just have no posted number before that, like the NPS-owned parkway? Also your quote is broken.
Mileage-based exit numbering implies the existence of mileage-cringe exit numbering.