Scenic map not matching OpenStreetMap

#1 · 03.07.2026, 15:52

I just found a weird map issue where the map in Scenic does not match OpenStreetMap. The issue is in Pennsylvania, near the vicinity of 39°46'18.4"N 78°44'56.6"W. I'm trying to create a route that follows PA 96 (Hyndman Rd) from the north to the south. Scenic shows PA 96 ending just south of Stairway Drive before it reaches Windy Lane:

But PA 96 is not a new road, and has been correct in OpenStreetMap for, well, forever. It continues southward past Windy Lane and beyond in OpenStreetMap:

I've run across map errors in Scenic before that were attributable to OpenStreetMap errors, and successfully corrected them in OpenStreetMap. But I'm stumped on this one because Scenic is simply not matching the OpenStreetMap map.

Any ideas or help is much appreciated.

--Tom

#2 · 06.07.2026, 11:41

About a month ago, this road was given the tag highway=secondary. This is what Scenic needs to make it show up. OSM shows real up to date data. However Scenic’s map provider takes an extract every 1 to 2 months. My guess is in their latest extract, this tag did not exist yet. It should show up with the next map update.

Here’s a the link to OSM edit history of this road.

https://www.openstreetmap.org/way/19597153/history https://www.openstreetmap.org/way/133680011/history#map=18/45.353318/-79.348342&layers=D

As you can see, in version 14 the highway=secondary tag did not exist yet. It was only added in version 15 a month ago.

Hope that explains.

Best regards,

Guido

Tom in NH has reacted to this post.

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

#3 · 08.07.2026, 05:30

Thank you so much for the detailed reply, Guido. That does explain it perfectly!

—Tom