Author Topic: PA:PA 174 at US 11/PA 533 Recenter (plus US 11 generalization)  (Read 6189 times)

0 Members and 1 Guest are viewing this topic.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3301
  • Last Login:Yesterday at 10:44:11 pm
PA:PA 174 at US 11/PA 533 Recenter (plus US 11 generalization)
« on: February 29, 2016, 08:20:39 pm »
The point "US11/533" is very off-centered at PA 174.  This is the same problem in both the US 11 and PA 533 files at PA 174.  Also I saw many points slightly off-centered on US 11 south of I-81 (Exit 65).  (Too many to count, but this may be some epidemic or something as I saw with the US 15 Bus (Gettysburg) having similar problems.  Too early to tell on that.)

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4422
  • Last Login:November 11, 2024, 12:50:03 pm
  • I like C++
Re: PA:PA 174 at US 11/PA 533 Recenter (plus US 11 generalization)
« Reply #1 on: March 01, 2016, 02:37:13 am »
PA was one of the (if not possibly even THE) first states to get its US routes drafted, back in.... what, 2006? Maybe even late 2005?
Back then our point location data were from Google Maps, which has since been updated with more precise cartography. This could well account for many of the more minor off-center points there. (That and maybe just Tim not having the extreme focus on super-zoomed-in precision that I for one use when putting together new routes now.)

The 11/533/174 intersection is pretty egregiously off-center and should be fixed.

PA US11 PA581_W Just Kinda Bugs Me :), though I can understand the process that led to placing it where it is, even if I don't agree with the outcome. (I'd characterize this interchange as a "Misbehaving Trumpet".) Crap, this opens up a can of worms though. I was thinking of putting the points at different coords for each route, as we'd do for a more standard trumpet treatment, but that'd break the 11/581 multiplex. There are ways around this using shaping points, but... blecch. That's not really precedented, is it? I don't wanna think about this right now. Leaving the point where it is may be inelegant, but it's not Evil and Wrong.

The rest, I wouldn't be bothered to edit & recenter, myself: a lot of effort for minimal gain, diminishing returns, yadda yadda. Though PA has no official maintainer, so really, anyone who'd actually want to do the work would be welcome to do so.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4422
  • Last Login:November 11, 2024, 12:50:03 pm
  • I like C++
Re: PA:PA 174 at US 11/PA 533 Recenter (plus US 11 generalization)
« Reply #2 on: March 01, 2016, 02:27:14 pm »
11/533/174 intersection fixed in all three files.
I've opted to leave PA US11 PA581_W as is.
https://github.com/TravelMapping/HighwayData/pull/459
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca