Author Topic: PA: US 202/PA 29 Interchange  (Read 4577 times)

0 Members and 1 Guest are viewing this topic.

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3301
  • Last Login:Today at 10:01:09 am
PA: US 202/PA 29 Interchange
« on: September 08, 2018, 02:58:24 pm »
https://github.com/Markkos1992/HighwayData/pull/29

I edited both files at the moment to have 3 points each. 

US 202: SweRd_W, PA29, MatRd
PA 29: MatRd, US202, SweRd

I want to think that the below from the manual may apply, but that one ramp directly to PA 29 in the middle makes it crazy.

Quote
Double half interchanges: Usually use one central point and treat both halves as a single, full interchange. Exceptions: a clear gap of at least 0.5 mi/0.8 km separates the two halves, or each half connects to a different highway that we are also mapping.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4422
  • Last Login:November 11, 2024, 12:50:03 pm
  • I like C++
Re: PA: US 202/PA 29 Interchange
« Reply #1 on: September 08, 2018, 03:30:38 pm »
A gray area of "Just what is a single interchange?"

I'd say the quoted passage of the manual doesn't apply here:
SweRd_W <- 0.37 mi -> PA29
PA29 <- 0.35 mi -> MatRd
No clear gap of 0.5 mi, and only US202 & PA29 themselves are involved.

To my eye, it's a single interchange, albeit a bit of an unconventional, modified cloverleaf with some pretty weird geometry, one that incorporates local roads into some of the movements. I would do just a single point where the 202/29 center lines cross.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3301
  • Last Login:Today at 10:01:09 am
Re: PA: US 202/PA 29 Interchange
« Reply #2 on: September 08, 2018, 04:22:08 pm »
Agreed.  I will just do a single point at the 202/29 center lines. 

Two users (myself and tckma) were using SweRd though.  I removed the line completely from my .list file as it was only US202 to SweRd. 

Thankfully tckma started at US 30 so I could get away with using SweRd as an alternate label for US 202 and end it there.

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

« Last Edit: September 09, 2018, 08:00:44 pm by Markkos1992 »