Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on September 10, 2018, 08:47:02 pm

Title: PA: US 222/US 422/PA 12 Interchange in Reading
Post by: Markkos1992 on September 10, 2018, 08:47:02 pm
I wanted to note this to myself when I get to looking at this deeper.  I am unsure if US 422 specifically was being done correctly when this was drafted.

US 422 EB traffic directly exit off of the Warren St Bypass as it becomes PA 12.  US 222 NB and US 422 EB are on completely separate ramps.

US 422 WB traffic must use the flyover from the West Shore Bypass to meet US 222 SB before merging with the Warren St Bypass as PA 12 ends.

Another interesting interchange in PA to overthink about.   ;)

EDIT(9-11-2018):

I came up with the following options I came up earlier today.  Both of these would involve removing the marked US 222/US 422 concurrency within the interchange and I am sure would break list files.  The PA 12 file would be slightly truncated to the east.  Also the current US 422_E (US 222)/US 222_N (US 422) point would be removed under both scenarios.

1.  Have two points along the Warren St Bypass at both sets of ramps.

Point 1 would be at the merge/exit of US 222 and US 422 WB from the Warren St Bypass.

Point 2 would be at the ramps to PA 12 directly from the West Shore Bypass.

US 222:
PA12 >- US422_E (Point 1)

Next point would be Broadcasting Rd(BroRd) minus potential needing of shaping points

US 422:
PA12  >-  US222_N (Point 1)
PA12 (Point 2)

PA 12:
US222/422 (Point 2-route would be truncated to Point 2 on its west end)

2.  One point including the entire interchange.  This would be on the Warren St Bypass in the middle of both sets of ramps. 

US 222: US422/12
US 422: US222/12
PA 12: US222/422







Title: Re: PA: US 222/US 422/PA 12 Interchange in Reading
Post by: dave1693 on September 11, 2018, 10:33:54 pm
I'm in favor of option 2, one point. I have issues with option 1 but the status quo is also unsatisfactory. The one-point solution looks to be the least bad option, and to my less-experienced eye might be doable without breaking lists.
Title: Re: PA: US 222/US 422/PA 12 Interchange in Reading
Post by: yakra on September 11, 2018, 11:12:48 pm
I also favor option 2, the single point.
I don't see any reason .list files need be broken. If any of the points to be removed have labels in use, just use them as alternate labels for the new central point.
Title: Re: PA: US 222/US 422/PA 12 Interchange in Reading
Post by: Markkos1992 on September 19, 2018, 06:07:26 pm
https://github.com/TravelMapping/HighwayData/pull/2235
Title: Re: PA: US 222/US 422/PA 12 Interchange in Reading
Post by: yakra on October 09, 2018, 09:53:26 pm
Recommend repositioning point where centerlines cross (http://www.openstreetmap.org/?lat=40.350982&lon=-75.958260).
Title: Re: PA: US 222/US 422/PA 12 Interchange in Reading
Post by: Markkos1992 on October 10, 2018, 02:45:18 am
Recommend repositioning point where centerlines cross (http://www.openstreetmap.org/?lat=40.350982&lon=-75.958260).

Done as recommended.  Leaving as solved.

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