DE: US 301 toll road and related changes

[Duke87]

As of this writing (2017-12-19) the toll road itself is still under construction. US 301 will need to be moved once it opens, though. Designations for the old road remain to be seen.

That said, there are a couple changes related to this project are already implemented on the ground and the routes in HB need updating to match (unless we want to just wait for the toll road to open to change everything):
DE 299 has been moved to a new alignment adjacent to the road under construction near the state line. It now intersects US 301 at the same intersection as DE 15.
DE 15 has also been moved slightly, the intersection where it meets US 301

[mapcat]

Any estimate for when the new route will open?

[Jim]

The site update I just launched includes some work in this area by @yakra.  See https://github.com/TravelMapping/HighwayData/pull/1780

[yakra]

DE 299 has been moved to a new alignment adjacent to the road under construction near the state line. It now intersects US 301 at the same intersection as DE 15.
DE 15 has also been moved slightly, the intersection where it meets US 301

Both of these changes are now live in the HB.

Any estimate for when the new route will open?

December 2018.

As of this writing (2017-12-19) the toll road itself is still under construction. US 301 will need to be moved once it opens, though. Designations for the old road remain to be seen.

All the changes that need to be made now have been, I believe.
Since we can't mark topics as solved in the 6-Month+ Outlook subforum, may as well leave this open until the toll road itself opens.

--

I wonder whether the spur road will become new DE15, with the old route becoming either DE15 or such, or unnumbered roads.

Speaking of the spur road, the interchange they have planned for its north end leaves me scratching my head. It's over-built and under-functional.
• At the south end, the directional split has a yecchy left entrance. I'd expect that the spur hwy would carry more traffic here.
• At the north end, the main thru movements are for 71/896 (and existing 301). Again, I'd expect this to be the other way around.
• Local road accessibility: Right now, traffic can move between DE15 to the west and 301/71/896 to the east. The planned interchange cuts this connection off, needlessly IMO. If someone coming from the DE286 corridor wants to access the Summit Bridge or Airmont Acres communities, ...yeah. Have fun. Why not just...
  - Connect the spur road directly into 301/71/896 to the north. A thru freeway.
  - Connect DE15 directly into 301/71/896 to the east. A thru local road.
  - Parclo interchange, with roundabouts at ramp termini.
  - Tie the northeast segment of Bethel Church Rd into the eastern roundabout, thereby retaining, and improving, a connection that can now only be made in one direction (Bethel Church SW -> 301&c N).

[Markkos1992]

DE 299 has been moved to a new alignment adjacent to the road under construction near the state line. It now intersects US 301 at the same intersection as DE 15.
DE 15 has also been moved slightly, the intersection where it meets US 301

Both of these changes are now live in the HB.

Note that the asterisk for marking OldDE15 as closed on the DE 299 file was omitted.  It is there for DE 15 and US 301.

[yakra]

Note that the asterisk for marking OldDE15 as closed on the DE 299 file was omitted.  It is there for DE 15 and US 301.

Done. Thanks for catching that.

[Markkos1992]

The new US 301 is opening tomorrow morning after morning rush hour.

EDIT:  It has officially opened. 

[Markkos1992]

I'm willing to go ahead and take the lead on this since no one maintains DE.  I do have some comments:

1.  I presume that I should keep the OldDE299 marked as closed.
2.  Is there a way to easily verify the exit numbers?  I cannot find a signing plan on the US 301 website.  I see that they are on OSM and Wikipedia.
3.  I also need verification of the exit number for US 301 SB from DE 1.  Wikipedia and OSM state that it is Exit 147.

[Markkos1992]

https://github.com/TravelMapping/HighwayData/pull/2497

1. I did remove the OldDE299 closed point as it seemed to begin after the old US 301 split; however, I did add a closed *OldUS301 point.
2 and 3.  I found signing plans via the archived contractor information on the US 301 website to verify the correct exit numbers on US 301 and DE 1.

DE 299:  I had to remove the DE15_S alternate label for *OldDE15. I needed DE15_S to replace US301_S.  (When it comes to list files, this only affects griffith.)

[Jim]

I see there's a pull request: https://github.com/TravelMapping/HighwayData/pull/2497

Would/should someone who had traveled all of US 301 on its old alignment now get 0 miles in Delaware, or is there some segment from the state line into Delaware that remains concurrent with the old?

Are others who are familiar with the changes to the routes happy with the changes submitted in the pull request?

[oscar]

I drove the entire new alignment earlier today, from south to north. This all looks right to me, including the northbound exit numbers.

I can't comment on whether the new alignment includes a part built on top of the old alignment. If there is, it would be a pretty short segment, and hard to tell what it includes (probably just the part between the state line and the weigh station, about 0.6 mile -- markkos1992 would put it about 0.15 mile north of where I'd put it), I suggest not bothering with an *OldUS301 point, but if it stays the point markkos1992 set is reasonable.

I got off at exit 5, did some tax-free shopping to offset part of the toll, and resumed my northbound travels at exit 2. Between exits 5 and 2, I traveled the old highway. I think nothing happened to the state routes that had been concurrent with the old alignment. As for the part of the old alignment south of exit 2, it looks unnumbered, signed only as something like "local traffic only, no access to US 301".

[Markkos1992]

I see there's a pull request: https://github.com/TravelMapping/HighwayData/pull/2497

Would/should someone who had traveled all of US 301 on its old alignment now get 0 miles in Delaware, or is there some segment from the state line into Delaware that remains concurrent with the old?

I believe so unless they already had the relevant sections of DE 15, DE 299, DE 71, and DE 896 in their list files already.  The new US 301 is not concurrent with any other routes.

If all of those routes are accounted for in a list file, the only portions of the old US 301 that no one would have would be the leftover part west of DE 15/299 and Middletown-Warwick Rd between DE 15/299 and DE 71 (both now unnumbered).

(EDIT:  What I was trying to state was that, everyone should have 0 miles of US 301 in Delaware if having traveled the old alignment.  The other routes would need to already be in someone's list file in order to keep the previous segments of US 301 as counted.)

I drove the entire new alignment earlier today, from south to north. This all looks right to me.

I can't comment on whether the new alignment includes a part built on top of the old alignment. If there is, it would be a pretty short segment, and hard to tell what it includes (probably just the part between the state line and the weigh station, about 0.6 mile), I suggest not bothering with an *OldUS301 point.

I got off at exit 5, did some tax-free shopping to offset part of the toll, and resumed my northbound travels at exit 2. Between exits 5 and 2, I traveled the old highway. I think nothing happened to the state routes that had been concurrent with the old alignment. As for the part of the old alignment south of exit 2, it looks unnumbered, signed only as something like "local traffic only, no access to US 301".

The very southern part up to the weigh station area was built on top of the old alignment.  US 301 traffic was already two-lane on part of this alignment during construction before shifting to the old route to head to DE 15/DE 299.  At this time, DE 299 had already been relocated with its intersection closed.  Hence why yakra had created a *OldDE299 point.  The MD/DE point is the only point on US 301 that stays as-is (despite me slightly moving it).

EDIT 2:  I probably should have gone ahead and marked it as solved.

[dave1693]

Would/should someone who had traveled all of US 301 on its old alignment now get 0 miles in Delaware, or is there some segment from the state line into Delaware that remains concurrent with the old?

I believe so unless they already had the relevant sections of DE 15, DE 299, DE 71, and DE 896 in their list files already.  The new US 301 is not concurrent with any other routes.

If all of those routes are accounted for in a list file, the only portions of the old US 301 that no one would have would be the leftover part west of DE 15/299 and Middletown-Warwick Rd between DE 15/299 and DE 71 (both now unnumbered).

(EDIT:  What I was trying to state was that, everyone should have 0 miles of US 301 in Delaware if having traveled the old alignment.  The other routes would need to already be in someone's list file in order to keep the previous segments of US 301 as counted.)

(snip)

The very southern part up to the weigh station area was built on top of the old alignment.  US 301 traffic was already two-lane on part of this alignment during construction before shifting to the old route to head to DE 15/DE 299.  At this time, DE 299 had already been relocated with its intersection closed.  Hence why yakra had created a *OldDE299 point.  The MD/DE point is the only point on US 301 that stays as-is (despite me slightly moving it).

This seems contradictory. If the very southern part of the new tollway was built on top of the old alignment, those of us who had driven the old alignment should get credit for that. Presumably that's what the *OldUS301 waypoint was put there for?

[Markkos1992]

This seems contradictory. If the very southern part of the new tollway was built on top of the old alignment, those of us who had driven the old alignment should get credit for that. Presumably that's what the *OldUS301 waypoint was put there for?

Yes, hence why I created that point.  I had not heard any further objections so I had just left it. 

[Jim]

I'm adding the MD/DE to *OldUS301 segment to my list.

This would probably be overkill, but to credit people who don't update their lists with that tiny segment, would it be safe to add all of the (in use) old US301 labels as alt labels for *OldUS301?