Earlier this evening when I drove up US 71 on my way back home to Kansas City from Bridal Cave at the Lake of the Ozarks, I thought about something I remember having seen on Google Maps: namely, at some point after I-49 was designated along the US 71 freeway in Missouri south of the Grandview Triangle (the I-435/I-470 interchange), Google Maps also labeled the exits along the stretch in KC north of the Triangle (Bruce R. Watkins Drive) as if they continued the I-49 exit numbers, even though they aren't actually numbered in real life.
That made me wonder: throughout the country, are there any freeways, or sections of freeways, that are labeled on Google Maps as though the exits were numbered, even though the exit numbers aren't posted on the actual signs? I'm sure there's at least a handful of those "phantom exit numbers" on Google Maps.
Quote from: KCRoadFan on December 26, 2023, 11:31:03 PM
Earlier this evening when I drove up US 71 on my way back home to Kansas City from Bridal Cave at the Lake of the Ozarks, I thought about something I remember having seen on Google Maps: namely, at some point after I-49 was designated along the US 71 freeway in Missouri south of the Grandview Triangle (the I-435/I-470 interchange), Google Maps also labeled the exits along the stretch in KC north of the Triangle (Bruce R. Watkins Drive) as if they continued the I-49 exit numbers, even though they aren't actually numbered in real life.
That made me wonder: throughout the country, are there any freeways, or sections of freeways, that are labeled on Google Maps as though the exits were numbered, even though the exit numbers aren't posted on the actual signs? I'm sure there's at least a handful of those "phantom exit numbers" on Google Maps.
This may be common in California. CalTrans has designated every CASR- US- and I- freeway exit in the state, but not all of the are posted, and, it may be that contracts to do so haven't even been let.
Google Maps shows the exit on US 95 at Mercury northwest of Indian Springs, NV as exit 136. This exit number is not signed in the field, as it's a single interchange along divided highway to the south, with the highway transitioning to two-lane just to the north. I think the number is correct based on historical statewide mileage of US 95, but as far as I'm aware this number does not appear on any NDOT documentation.
I've seen Google Maps sometimes confuse the speed limit on one of the yellow Advisory signs as an exit number.
For a while, in GPS mode in Google Maps, it would show Exit 60 on I-295 North in NJ as Route 60 instead (the routes are NJ 29 & I-295).
There was a "Shopping Center" exit along I-80 in Tannersville, Pennsylvania at one point. It may have been the 611/33 interchange.
Not really a "phantom exit number", but more of an "erroneous exit number". The HOV left exit to Logan Airport and South Station (which is now open to all vehicles) on I-93 North in Boston after Exit 16 (Old Exit 20) is erroneously labelled as Exit 17 or 20 (https://www.google.com/maps/@42.3362207,-71.0648863,18.73z?entry=ttu) on Google Maps (may have to zoom in to see both erroneous numbers), even though that exit has never received a number prior to the numbering, nor has it been assigned one once the mile based exit numbers were in place.
Quote from: roadman on April 25, 2021, 05:56:46 PM
Quote from: fwydriver405 on April 25, 2021, 01:22:55 PM
However, on Google Maps:
- I noticed that the former HOV left exit NB to the airport and South Station after new exit 16 (old exit 20) is labelled as "exit 17 (https://www.google.com/maps/@42.3359891,-71.064698,18.12z)". The last time I checked, there was no mention of that exit ever receiving a number at all.
The left HOV/South Station exit on I-93 north has never had an exit number, nor will it receive one under this project. Google is in error here.
Copyright traps?
Mike