Author Topic: PA: possible new routes in York and Lancaster areas  (Read 1831 times)

0 Members and 1 Guest are viewing this topic.

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 808
  • Last Login:Yesterday at 06:23:21 pm
PA: possible new routes in York and Lancaster areas
« on: June 18, 2016, 10:13:57 am »
Discovered these while cleaning up my clinched lists and looking over my GPS tracks.  I've found a possible route in the York area, and a possible route extension in the Lancaster area, both of which need further investigation.

The possible new route is "PA 892".  Apple maps (which appears on my GPS tracking app) has it beginning at I-83 Exit 10, briefly goes west on North St to intersect PA 214, then turns north on Main St, crossing Lake Williams and PA 182 (along South George St), then ends where BUS-83 meets South George St.  Google Maps shows the northern part of this as "PA 892", but Bing Maps and OSM do not show it.  I have not checked photo sites or GMSV.

The possible route extension is PA 722.  Apple maps shows it crossing PA 272, going south along Bushong Rd to Quarry Rd to end at PA 23.  Google Maps does not show this, nor does Bing Maps (though Bing Maps doesn't show PA 722 along Oregon Rd either) or OSM.  So it's likely that this one doesn't exist or is a former alignment that Apple hasn't updated.

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1179
  • Last Login:Today at 06:09:47 am
    • Co-curator Virginia Highways Project
Re: PA: possible new routes in York and Lancaster areas
« Reply #1 on: June 18, 2016, 11:06:03 am »
Latest GMSV for anywhere along either of these is in late 2015 (I-83 and PA 23 respectively).  Neither shows these new routes.

PennDOT RMS files from Dec 2015 also do not show these.

I am unable to find anywhere something like the Virginia CTB for Pennsylvania to see if something just happened...

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3105
  • Last Login:Today at 07:05:01 am
Re: PA: possible new routes in York and Lancaster areas
« Reply #2 on: June 18, 2016, 09:12:05 pm »
As far as I know, these routes do not exist.  The only route changes I can think of since I moved to PA are PA 441 in Columbia and US 202 Business (the portion of US 202 near Doylestown bypassed by the parkway was approved by AASHTO but had not been signed, I actually did get to see a portion of this get signed back in January)



-Note that having worked for PennDOT for seven months, I have not found out where route changes are documented.

-Mark AKA 74/171FAN

Offline dave1693

  • Full Member
  • ***
  • Posts: 185
  • Last Login:November 21, 2023, 11:28:54 pm
Re: PA: possible new routes in York and Lancaster areas
« Reply #3 on: July 25, 2016, 02:50:31 am »
Confirmed on 24 July 2016 that US 202 Business has been completely signed. I traveled the entire length from US202 in Montgomeryville to PA611 just west of Doylestown -- there is an "End North Business US202" sign at the west end of the overpass that takes State St over PA611. Apparently Doylestown itself didn't care to have a US Business route running through the center of town.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:April 07, 2024, 11:18:57 pm
  • I like C++
Re: PA: possible new routes in York and Lancaster areas
« Reply #4 on: July 08, 2017, 12:05:57 pm »
I looked at the PENNDOT city/borough/township and county maps (both type 10 & type 3); no evidence of 892 or an extended 722 in any of these. The type 10 York county map was dated 2017. Edit: Nothing on pahighways.com either.
« Last Edit: July 09, 2017, 01:54:54 am by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:April 01, 2024, 02:37:22 am
Re: PA: possible new routes in York and Lancaster areas
« Reply #5 on: July 08, 2017, 03:46:14 pm »
It's probably just an error with Apple Maps. I guess that it is still full of errors...