We all know that even a mapmaker can make errors. I have been noticing some erroneous things in Google Maps and I'd like to share them. If you find errors on Google Maps and such, feel free to tell them here. I have found some, and I'd like to share them.
These are from Google Maps.
Lexington-Fayette's location is off, as it is out of the city, but near it. I (think) that it is also too small of a city to have such a big dot on the map.
Wrong Location for the Name:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=37.971809,-84.433365&spn=0.235461,0.441513&z=11 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=37.971809,-84.433365&spn=0.235461,0.441513&z=11)
A bigger dot than Louisville?:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=38.182069,-84.589233&spn=1.8782,3.532104&z=8 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=38.182069,-84.589233&spn=1.8782,3.532104&z=8)
Maine and Nova Scotia, according to Google Maps, is a national border, not an international border. (This is supposed to be a international water border.)
http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.768119,-69.598389&spn=0.215697,0.441513&z=11 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.768119,-69.598389&spn=0.215697,0.441513&z=11)
Feel free to share yours!
~City
(let's open it up to paper too :D -ms)
Don't get me started with Google Maps and errors. I don't have enough paper for a list.
Consider this to start: BC 3B is cosigned with BC 3 for BC 3's entire length.
All the provincial route markers Google used got switched to trapezoids for a spell, marking no visual distinction with secondary highways at all (very bad for making files for the Clinched Highways site).
Decommissioned highways are a mainstay. We'll know it's really bad when US 6 returns to Long Beach.
The Google Maps symbology. (Must... not... rant...)
Oftimes map overlay on Satellite view is off; particularly bad in the higher latitudes.
I liked that they included the PA routes that were decommissioned after WWII, as it helped me with their histories.
Oftentimes I see US Highways marked with state highway markers, a CIRCLE FOR EVERY STATE X(
There are too many errors in Google Maps to find them all, but here are some of the ones that I know of in western Maryland (most of them are minor, but meh)...
MD 956 is shown as MD 9.
Zihlman, MD, is shown as "Zihmah."
Eckhart Mines is shown as being a mile or two west of its correct location
Burning Mines Road is shown as going to Dan's Rock (the road was washed out in a flood decades ago and never rebuilt)
It shows a ghost road paralleling MD 638.
It shows MD 36 forking and going two different directions in eastern Frostburg.
An amusing side-effect of one error is that if you type in "Nothing", the first suggestion is "Frostburg, Maryland"
Google Maps often signs US Routes as State Routes, and vice versa. Also, Business, Alternate etc. are often just shown as US Routes.
I found another one.
Google Maps claims that Interstate 99 has one carriageway between US-322 until it ends at US-220. :pan:
Only MapQuest shows that portion as complete. The same has happened with the new US 15 freeway. Ironically, while Google does not have that on maps, it does have it on street view, resulting in micro sections of street view that don't seem to correspond to anything that are actually the freeway.
NY458 between its western terminus at NY11B and the St. Lawrence-Franklin county line is shown as NY11B...although "State Rte 458" is shown as the route name.
Also, my address is shown as being on the wrong side of the road! :D
If it's okay 2 include map errors from the good ol' fashioned folding paper road maps, here's 1. I recall seeing a 1964 Rand McNally Michigan road map showing M-131 starting at US-31 by Petoskey and going up to Cross Village, then turning east and returning to US-31 in Levering. The error is that M-131 only went as far as Cross Village. :coffee:
Quote from: Tom on August 12, 2009, 07:48:27 PM
If it's okay 2 include map errors from the good ol' fashioned folding paper road maps, here's 1. I recall seeing a 1964 Rand McNally Michigan road map showing M-131 starting at US-31 by Petoskey and going up to Cross Village, then turning east and returning to US-31 in Levering. The error is that M-131 only went as far as Cross Village. :coffee:
That'd be ok here.
Need not mention the phantom freeway bypass under construction forever in the Rand McNally atlas.
AAA maps for NY has a bunch of strango errors:
NY 31C still marked (decommissioned 2003)
NY 99 still marked (decommissioned 1996)
NY 132A still marked (decommissioned 1972)
NY 194 still marked (decommissioned 1980)
There were more :|
VA-167's evidently still alive on LaSalle Ave in Hampton, VA according to my 2010 Rand McNally. In fact it even shows it extending down Chesapeake Ave, which I doubt it ever did, considering that that is just a little street with no markings or even an actual curb.
Plus it tends to show a lot of 4-lane divided highways as 2-lane, is missing a lot of recent bypasses (primarily US-17 in NE NC), and even shows US-17 in VA still using the old alignment along the Dismal Swamp Canal.
Here is a crazy one. On US 20 in Sturbridge, MA (near I-84's east end), there are US 29 shields!
http://maps.google.com/maps/mm?ie=UTF8&hl=en&ll=42.123883,-72.053061&spn=0.030557,0.076818&t=h&z=14 (http://maps.google.com/maps/mm?ie=UTF8&hl=en&ll=42.123883,-72.053061&spn=0.030557,0.076818&t=h&z=14)
Google maps also tends to sign the hidden designations for routes with hidden designations. They also have a huge problem with signing US routes as state routes. Oh and in Pennsylvania, the minor SR xxxx routes are signed.
Not a true error, but the final couple of miles of New Hampshire's Spaulding Turnpike/NH 16 super-2 is signed as a surface road, when it should be a freeway:
http://maps.google.com/maps/mm?ie=UTF8&hl=en&ll=43.307317,-70.980949&spn=0.059959,0.153637&t=h&z=13 (http://maps.google.com/maps/mm?ie=UTF8&hl=en&ll=43.307317,-70.980949&spn=0.059959,0.153637&t=h&z=13)
QuoteVA-167's evidently still alive on LaSalle Ave in Hampton, VA according to my 2010 Rand McNally. In fact it even shows it extending down Chesapeake Ave, which I doubt it ever did, considering that that is just a little street with no markings or even an actual curb.
VA 167 is even still shown on the VDOT map as of the 2008-2010 edition :-o
I think I found this error on the 2010 Large Scale Rand McNally Road Atlas.
US 501 here to the right of the picture should've been US 158. US 501 runs north-south from Durham into Virginia.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi26.tinypic.com%2F2ugh4bc.jpg&hash=f114f3b7a89ca2e09de3acb48dc8050e7fe5508a)
Fairly sure that US 501 icon should be US 158 (the one west of US 29 is correct, anyway).
QuoteFairly sure that US 501 icon should be US 158 (the one west of US 29 is correct, anyway).
Since even paper maps are created digitally these days, it could be a cut and paste error. i.e. They copied a US-501 shield and forgot to change the number.
Yeah that's definitely 158. I've even been down that way somewhat recently with that same atlas and never even noticed that. :-|
Apparently there's an NJ 55 bypass of Freehold in the 09 Rand atlas.
The American Maps South Hampton Roads atlas has VA 337 ALT on a segment of VA 239 from US 17 to VA 337 in Portsmouth.
American Map also has secondary routes in various independent cities and in Henrico County, which don't actually have them. Virginia independent cities not named Suffolk do not have SRs, nor do Arlington or Henrico Counties (though Henrico did once have them on paper, and Nuckols Rd was once erroneously signed as SR 695 at I-295 early in the 2000s). Interestingly, they correctly don't show SRs in Arlington County.
The Greater Richmond maps have SR 627 (Meadowbridge Rd), SR 683 (Forest Hill Ave), and SR 686 (Jahnke Rd) within the city limits; and SR 625 (Greenwood Rd), 627 (Richmond-Henrico Tnpk), and 650 (River Rd) in Henrico County. This isn't unique to just Richmond, but Richmond is probably the most convenient example. I sent an email to them about it, but the errors were not corrected in the 2009 editions of some of the maps.
I know that the VA 337 ALT and some of the SRs in independent cities go back at least to the 2003 edition of the South Hampton Roads one, as I've throughly examined all of it over these years. Though I wasn't sure that the VA 337 ALT one was an error, as that whole routing confuses me.
QuoteVA-167's evidently still alive on LaSalle Ave in Hampton, VA according to my 2010 Rand McNally. In fact it even shows it extending down Chesapeake Ave, which I doubt it ever did, considering that that is just a little street with no markings or even an actual curb.
Yes it did. VA 167 was extended west along Chesapeake Ave (at the time called the Monitor-Merrimac Memorial Hwy) out to Indian River (near Powhatan Pkwy) ca. 1940, then to the Newport News line ca. 1944, then finally along 16th St to Jefferson Ave ca. 1950 (later, in 1958, continuing north along Jefferson Ave to VA 143 at 28th St).
QuoteThe American Maps South Hampton Roads atlas has VA 337 ALT on a segment of VA 239 from US 17 to VA 337 in Portsmouth.
Probably an offshoot of the "VA 337" error along that segment of VA 239 on the ADC Maps (ADC and American Map are owned by the same parent company).
The official Michigan Transportation Map has shown County Highway H-16, a highway that does not and never has existed, in 1983, 1984, and every year since 1992. It's actually National Forest Highway 16.
Rand McNally had M-179 marked as M-79 for a couple years. It almost makes more sense, but it's not true.
Google Earth should really do something about the FM and RM roads in Texas by the way. You have to zoom in very far to read the number (written as a street name).
I noticed in the 2009 RM that the Fond du Lac WI bypass was never drawn, even though through this year the part east of US 41 was completed (for a few years)
I just got the new Colorado DOT map, and the NW Pkwy is for some reason now listed as part of 470, which it never has been in previous editions
US 27 never goes north of Fort Wayne (it ends at Indiana Route 3 and I-69)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi31.tinypic.com%2Fix61ra.jpg&hash=bfdf269a3df69b5259b35f7d34f19b96253966a5)
Rand McNally 2010 Large Scale Atlas
I was looking at Google Maps at the site of the future I-68/Mon-Fayette Expressway interchange, and noticed this little gem (in case anyone isn't familiar with it, US 48 is the former designation of I-68, which was changed in 1991. The northbound road on the map is CR 857, which runs parallel to the Mon-Fayette Expressway):
http://maps.google.com/?ie=UTF8&ll=39.670744,-79.849255&spn=0.011248,0.019269&z=16 (http://maps.google.com/?ie=UTF8&ll=39.670744,-79.849255&spn=0.011248,0.019269&z=16)
the last time I was there (2006), I saw the END 27 shield posted on Coldwater Road (which is now Indiana state highway 327) at exit 112 as seen on the map ... and then, past it but visible from the spot of the END shield ... a 27 reassurance marker! :pan:
US 27 was truncated in 2001 according to wikipedia, so there might be some old signs around. It used to run all the way up north in Michigan.
QuoteUS 27 was truncated in 2001 according to wikipedia, so there might be some old signs around. It used to run all the way up north in Michigan.
It still should, IMO. How US 127 got priority in Michigan over US 27 is beyond me. :hmmm:
I just so happen to notice in the 2009 RM Road Atlas the phantom Nashua, NH bypass is not under construction anymore - it's not shown at all. :crazy:
QuoteI just so happen to notice in the 2009 RM Road Atlas the phantom Nashua, NH bypass is not under construction anymore - it's not shown at all.
Was it ever under construction in the first place? What was the deal with that?
probably RcM making a name for themselves.
Quote from: Chris on September 13, 2009, 09:50:25 AM
US 27 never goes north of Fort Wayne (it ends at Indiana Route 3 and I-69)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi31.tinypic.com%2Fix61ra.jpg&hash=bfdf269a3df69b5259b35f7d34f19b96253966a5)
Rand McNally 2010 Large Scale Atlas
At least they're consistent, the regular 2010 atlas has the same error.
Google maps don't show in Quebec, the bypass of Danville PQ-255, St-Felicien (PQ-169) and the A-50 extensions from Lachute to Greenville and from Masson to Thurso.
Quote from: njroadhorse on September 13, 2009, 02:21:42 PM
QuoteI just so happen to notice in the 2009 RM Road Atlas the phantom Nashua, NH bypass is not under construction anymore - it's not shown at all.
Was it ever under construction in the first place? What was the deal with that?
It's like the U.C. roads shown in atlases in the 1960's and 1970's. It was close enough to going through that they assumed it would. Then the economy dictated that non-essential road projects get dropped, and there was never enough need for this road in the first place. Probably never coming back, either.
Quote from: mightyace on September 13, 2009, 03:18:26 PM
At least they're consistent, the regular 2010 atlas has the same error.
It's in the '08 edition as well.
Quote from: agentsteel53 on September 13, 2009, 11:52:30 AM
the last time I was there (2006), I saw the END 27 shield posted on Coldwater Road (which is now Indiana state highway 327) at exit 112 as seen on the map ... and then, past it but visible from the spot of the END shield ... a 27 reassurance marker! :pan:
SR 327 doesn't even begin until you get to the intersection with SR 205 just south of Garrett. The portion from there south to I-69 has been under local jurisdiction for quite sometime.
Pick the real 97! (http://maps.google.com/?ie=UTF8&ll=47.729972,-120.179443&spn=0.105303,0.264187&z=13)
Quote from: DBrim on September 14, 2009, 12:10:27 PM
Pick the real 97! (http://maps.google.com/?ie=UTF8&ll=47.729972,-120.179443&spn=0.105303,0.264187&z=13)
lemme guess, the one that
is labeled both 97 and 97A. I forget which side of the river 97 is on.
QuotePick the real 97!
In a similar vein, Pick the real 77H! (http://maps.google.com/?ie=UTF8&ll=35.243376,-97.429161&spn=0.031965,0.077162&z=14)
Google does that all the time. hence their issue. This one seems more obvious - but pick the real US 51 http://maps.google.com/?ie=UTF8&ll=44.934547,-89.616508&spn=0.07826,0.154324&z=13 (http://maps.google.com/?ie=UTF8&ll=44.934547,-89.616508&spn=0.07826,0.154324&z=13)
US-66 lives on!
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi188.photobucket.com%2Falbums%2Fz194%2Fdeathtopumpkins%2Fdf1ccd9e.jpg&hash=4c1d59a843ab94445efcd0212649369318795b3d)
It's definitely eating away at your battery :-D
At work, there is a 1982 map of Richmond that DPW made; it's substantially lower in quality than the VDOT map of the time. The DPW map was hand-drawn (compared to VDOT maps, which haven't been for decades), and had a lot of incorrect route shields (US 95, US 195, US 64, US 33 where VA 33 is, and US 150). If I didn't work in a hospital, I'd take my camera and take pictures.
Most notably, though, the map does show VA 418 on Monument Avenue, and 1982 was the first year of VA 418 being on it. The map does not show VA 416 or VA 417, which also existed at the time.
QuoteGoogle does that all the time. hence their issue. This one seems more obvious - but pick the real US 51
The part I left out of my post is that neither of them are 77H (and the US 77 shown there isn't US 77). The western "77H" was decommissioned years ago, and relatively recently the eastern "77H" became US 77.
There's a Clare County (Mich.) road map from the 1990's that still shows old M-61 designated as M-61 along with the current M-61. :coffee:
I just fired up Google Earth only to notice that there is no longer any mention of I-264 on the Virginia Beach-Norfolk Expy (which is shown as the "Norfolk Virginia Beach Expressway") east of I-64, but rather that it has reverted back to VA-44.
EDIT: And SR-615 is back as well... Oceana Blvd. is labeled "State Route 615" with no mention of Oceana Blvd.
EDIT2: And several other secondary routes in Virginia Beach, such as 632 on Great Neck Rd.
Quote from: deathtopumpkins on October 24, 2009, 12:42:32 PM
I just fired up Google Earth only to notice that there is no longer any mention of I-264 on the Virginia Beach-Norfolk Expy (which is shown as the "Norfolk Virginia Beach Expressway") east of I-64, but rather that it has reverted back to VA-44.
EDIT: And SR-615 is back as well... Oceana Blvd. is labeled "State Route 615" with no mention of Oceana Blvd.
EDIT2: And several other secondary routes in Virginia Beach, such as 632 on Great Neck Rd.
At least they don't do what American Map/ADC does and call Sandbridge Rd and Sandpiper Rd SR 629...
I also noticed that I-264/VA 44 go right to US 60...even on 21st and 22nd Streets, which aren't numbered (or freeway, for that matter)! Pacific Ave is labeled with a normal US 60 shield, but "US 60 BUS" in all caps. At least it shows the correct endpoint (the loop at the end of Atlantic Ave). VA 164 is also not a freeway, apparently (neither are VA 895, VA 150, or the freeway segment of VA 199), but VA 76 and VA 288 are...
In Richmond, US 60 has a strange routing that I don't think ever existed in real life - E. Broad St along the old pre-2004 routing, past 25th and on one-way alignments on 17th and 18th (all of 18th and part of 17th are US 360) to Main, and then to the Manchester Bridge as normal.
Google Earth is likely suffering the same problems Google Maps is suffering from when Google switched to a map database that had lots of errors.
This may be an old thread, but I still have to bring up the error; Google not only incorrectly places Wassaic Metro-North commuter railroad station north of the actual station itself, but north of the Wassaic Metro-North Yard.
https://maps.google.com/?ll=41.819496,-73.562651&spn=0.026642,0.038581&t=h&z=15
I could try to get them to correct their error, but I forgot how I did this in the past.
This is the most epic fail ever:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi45.tinypic.com%2Fbff61h.jpg&hash=adb93175e1f1c498a8c5aead99a0aab6c5a38d5a)
On the ADAC Deutschland (Germany) KompactAtlas, but the same mistake is in a ton other maps, even in OSM!
Quote from: CNGL-Leudimin on March 20, 2013, 03:48:25 PM
This is the most epic fail ever:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi45.tinypic.com%2Fbff61h.jpg&hash=adb93175e1f1c498a8c5aead99a0aab6c5a38d5a)
On the ADAC Deutschland (Germany) KompactAtlas, but the same mistake is in a ton other maps, even in OSM!
Things only funny to Europeans...
Quote from: Steve on March 20, 2013, 11:38:46 PMThings only funny to Europeans...
Well, actually is not a mistake either :). It's something related to the Bielefeld Conspiracy (http://en.wikipedia.org/wiki/Bielefeld_Conspiracy), which claims this German city doesn't exist.
This thread should not have been bumped.
Quote from: D-Dey65 on March 20, 2013, 02:34:27 PM
This may be an old thread, but I still have to bring up the error; Google not only incorrectly places Wassaic Metro-North commuter railroad station north of the actual station itself, but north of the Wassaic Metro-North Yard.
https://maps.google.com/?ll=41.819496,-73.562651&spn=0.026642,0.038581&t=h&z=15
I could try to get them to correct their error, but I forgot how I did this in the past.
That's why we have the Incorrect Highways Marked on Google Maps thread. :P
Quote from: Roadsguy on March 22, 2013, 08:31:30 AM
That's why we have the Incorrect Highways Marked on Google Maps thread. :P
I couldn't find that, though/ Luckily, I did today;
https://www.aaroads.com/forum/index.php?topic=2001.0
I saw on my Facebook News Feed last night that Central NY is getting a Costco, and I found this map (http://www.cameronllc.com/wp-content/uploads/Aerial_1115121.jpg) (warning: 6900 pixel wide image) on the developer's web page. I had no idea that US 5 went through CNY. At least they have the correct AADTs.