AARoads Forum

National Boards => General Highway Talk => Topic started by: Riverside Frwy on November 08, 2009, 09:56:04 PM

Title: Incorrect highways marked on Google Maps
Post by: Riverside Frwy on November 08, 2009, 09:56:04 PM
Why is the South Bay Expressway (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=San+Diego,+CA&sll=32.715329,-117.157255&sspn=0.320058,0.701752&ie=UTF8&hq=&hnear=San+Diego,+California&ll=32.625786,-116.950493&spn=0.160189,0.350876&z=12) colored street yellow?That entire segment of California State Route 125 is built to freeway standards.Sure the shoulders are a little narrow on the bridges, but come on.Just shows that Google heard it's was called the "South Bay expressway", so they assumed it was an actual expressway.Then they just set it to yellow without knowing anything about that stretch of freeway.
Title: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on November 08, 2009, 09:57:40 PM
Most short or non-interstate freeways are now shown as arterials. Just another consequence of Google using its own data now.
Title: Incorrect highways marked on Google Maps
Post by: Alps on November 11, 2009, 07:17:13 PM
Quote from: deathtopumpkins on November 08, 2009, 09:57:40 PM
Most short or non-interstate freeways are now shown as arterials. Just another consequence of Google using its own data now.
Even Interstates.  I-895 (NY) is labeled "I-895" with no shield and no orange color.
Title: Incorrect highways marked on Google Maps
Post by: PAHighways on November 11, 2009, 09:05:40 PM
Quote from: deathtopumpkins on November 08, 2009, 09:57:40 PMMost short or non-interstate freeways are now shown as arterials. Just another consequence of Google using its own data now.

PA Turnpike 576 fits both criteria since it is yellow and marked "Pennsylvania 576 Turnpike," meanwhile PA Turnpike 43 is orange and marked with a 43 in a circle.
Title: Incorrect highways marked on Google Maps
Post by: algorerhythms on November 14, 2009, 09:14:49 PM
Apparently they fixed several of the errors I reported, though they rerouted US-77 onto Rock Creek Rd. instead of Tecumseh Rd.
Title: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on November 15, 2009, 10:30:37 PM
I-46 is still there.
Title: Incorrect highways marked on Google Maps
Post by: CL on November 16, 2009, 06:47:23 PM
Yep, it turns out so far around 70 percent of the errors I reported in the Salt Lake City area have been corrected by Google Maps after about a month or so. While most were corrected the way they were supposed to, others were poorly executed (some street names were only halfway corrected, other street additions were done without a name, and their interpretation of Legacy Pkwy says it all).
Title: Incorrect highways marked on Google Maps
Post by: agentsteel53 on November 16, 2009, 06:49:04 PM
I can't even find the Legacy Parkway!  Is it the one labeled Enterprise Blvd?
Title: Incorrect highways marked on Google Maps
Post by: CL on November 16, 2009, 07:04:41 PM
Yep. Also note the lack of an SR symbol, or how it's colored yellow as a regular road, or how it looks like something from Open Street Map (this is especially obvious at the northern terminus of Legacy Pkwy). Overall, a poor job they've done. And I have no idea where in the world they got Enterprise Blvd
Title: Incorrect highways marked on Google Maps
Post by: City on November 16, 2009, 09:56:32 PM
Google Maps is at it again by marking major corridors in Chile as US Routes. (http://maps.google.com/maps?hl=en&ie=UTF8&ll=-33.513919,-70.488281&spn=2.015113,3.532104&z=8)  :crazy: Although Chile's shields are similar to the US national highway shield,  they need to be colored properly to pass my approval as being the right shield design.

And in Bolivia... (http://maps.google.com/maps?hl=en&ie=UTF8&ll=-17.66496,-63.094482&spn=2.302885,3.532104&z=8)

And in Colombia... (http://maps.google.com/maps?hl=en&ie=UTF8&ll=4.696879,-73.806152&spn=2.408699,3.532104&z=8)

And (vaguely) in Peru... (http://maps.google.com/maps?hl=en&ie=UTF8&ll=-11.765192,-75.975952&spn=2.366054,3.532104&z=8)

Oh, and here's a bonus; Costa Rica has US and circle shields! (http://maps.google.com/maps?hl=en&ie=UTF8&ll=10.309515,-84.193726&spn=2.377806,3.532104&z=8)  :pan:

Add Honduras to that list... (http://maps.google.com/maps?hl=en&ie=UTF8&ll=13.33083,-87.113342&spn=1.175914,1.766052&z=9)

...alongside El Salvador... (http://maps.google.com/maps?hl=en&ie=UTF8&ll=13.736717,-88.838196&spn=1.17391,1.766052&z=9)

Yes, even Guatemala! (http://maps.google.com/maps?hl=en&ie=UTF8&ll=14.822681,-90.401001&spn=2.336409,3.532104&z=8)

There's probably more, but I'll save them for later.

Why can't they just take a few quick seconds to photoshop the right shield designs?  :banghead:
Title: Incorrect highways marked on Google Maps
Post by: City on November 17, 2009, 09:06:11 PM
Today, I have found yet another error. Have you ever heard of Hilo, AR? (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.394759,-92.263184&spn=4.035413,7.064209&z=7)

At first, there was a dot here, but there was no name assigned to it. Now, it is named Hilo.

:banghead:

Anyways, here are some more shots of it.

http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.36265,-92.27417&spn=1.009336,1.766052&z=9 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.36265,-92.27417&spn=1.009336,1.766052&z=9)

http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.361503,-92.275543&spn=0.252339,0.441513&z=11 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.361503,-92.275543&spn=0.252339,0.441513&z=11)

http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.361861,-92.272882&spn=0.031542,0.055189&z=14 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.361861,-92.272882&spn=0.031542,0.055189&z=14)

EDIT: I have another one for you all... US-1265! (http://maps.google.com/maps?hl=en&ie=UTF8&ll=35.199342,-82.435741&spn=0.06172,0.110378&z=13)  :pan:

I reported these errors to Google, so hopefully they'll be fixed.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on November 18, 2009, 12:33:47 AM
Quote from: City on November 17, 2009, 09:06:11 PM
EDIT: I have another one for you all... US-1265! (http://maps.google.com/maps?hl=en&ie=UTF8&ll=35.199342,-82.435741&spn=0.06172,0.110378&z=13)  :pan:

I can top that.  Say hello to US-1441 (http://maps.google.com/?ie=UTF8&ll=35.083043,-80.933232&spn=0.025742,0.055747&z=15). lol.

And yes, I've already reported it.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on November 18, 2009, 10:39:36 AM
And I present to you, U.S. 1200, U.S. 1710, U.S. 1800, and U.S. 1875 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=40.132691,-87.559319&spn=0.152768,0.282898&z=12)!
Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on November 18, 2009, 08:30:27 PM
That might be the greatest multiplex ever right there.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on November 18, 2009, 08:52:24 PM
Quote from: SyntheticDreamer on November 18, 2009, 08:30:27 PM
That might be the greatest multiplex ever right there.

if greatness is determined by the product of all route numbers, then yes, quite likely.
Title: Re: Incorrect highways marked on Google Maps
Post by: City on November 18, 2009, 09:07:50 PM
I present you... Interstate 6! (and in the most ironic of places) (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.630281,-78.950114&spn=0.003931,0.006899&z=17)

And US-17... (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.633639,-78.947303&spn=0.00393,0.006899&z=17) well, they were close to it, but instead insisted on labeling 17th St. as US-17. (need pan smiley, here!)
Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on November 18, 2009, 09:12:46 PM
Quote from: City on November 18, 2009, 09:07:50 PM
I present you... Interstate 6! (and in the most ironic of places) (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.630281,-78.950114&spn=0.003931,0.006899&z=17)

Okay, forget I-46 and I-341, that takes the cake.
Title: Re: Incorrect highways marked on Google Maps
Post by: Hellfighter on November 18, 2009, 11:51:42 PM
Quote from: SyntheticDreamer on November 18, 2009, 09:12:46 PM
Quote from: City on November 18, 2009, 09:07:50 PM
I present you... Interstate 6! (and in the most ironic of places) (http://maps.google.com/maps?hl=en&ie=UTF8&ll=33.630281,-78.950114&spn=0.003931,0.006899&z=17)

Okay, forget I-46 and I-341, that takes the cake.

WTF!!!! 
Title: Re: Incorrect highways marked on Google Maps
Post by: Duke87 on November 25, 2009, 01:18:47 AM
So, apparently, the Cross County Parkway is now also the Cross County Mall. (http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=40.925718,-73.813394&spn=0.001937,0.004823&t=h&z=18) Who knew?
Title: Re: Incorrect highways marked on Google Maps
Post by: njroadhorse on November 27, 2009, 01:43:11 PM
So, now US 701 is secretly mutliplexed all the way to Mount Pleasant, SC along US 17, and takes two different routes near Sullivan's Island!
http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Mount+Pleasant,+SC&sll=37.0625,-95.677068&sspn=48.50801,78.837891&ie=UTF8&hq=&hnear=Mount+Pleasant,+Charleston,+South+Carolina&ll=32.808558,-79.866657&spn=0.050642,0.07699&t=h&z=14 (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Mount+Pleasant,+SC&sll=37.0625,-95.677068&sspn=48.50801,78.837891&ie=UTF8&hq=&hnear=Mount+Pleasant,+Charleston,+South+Carolina&ll=32.808558,-79.866657&spn=0.050642,0.07699&t=h&z=14)
Title: Re: Incorrect highways marked on Google Maps
Post by: City on November 27, 2009, 02:24:44 PM
Quote from: Duke87 on November 25, 2009, 01:18:47 AM
So, apparently, the Cross County Parkway is now also the Cross County Mall. (http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=40.925718,-73.813394&spn=0.001937,0.004823&t=h&z=18) Who knew?

Umm... then where is the food court and all the stores? :pan:


--

Yes, there are towns in the middle of the Great Lakes!

Chatham-Kent and Dutton/Dunwich (http://maps.google.com/maps?hl=en&ie=UTF8&ll=42.246819,-81.452637&spn=0.894594,1.766052&z=9)
Kettle Point 44 and Lambton Shores (http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.295199,-81.89209&spn=0.879579,1.766052&z=9)
Huron-Kinloss and Ashfield-Colborne-Wawanosh (http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.996766,-81.68335&spn=0.869366,1.766052&z=9)

Don't get me started on any more. There are too many to count.
Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on November 27, 2009, 06:48:02 PM
Quote from: City on November 27, 2009, 02:24:44 PM
Quote from: Duke87 on November 25, 2009, 01:18:47 AM
So, apparently, the Cross County Parkway is now also the Cross County Mall. (http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=40.925718,-73.813394&spn=0.001937,0.004823&t=h&z=18) Who knew?

Umm... then where is the food court and all the stores? :pan:


--

Yes, there are towns in the middle of the Great Lakes!

Chatham-Kent and Dutton/Dunwich (http://maps.google.com/maps?hl=en&ie=UTF8&ll=42.246819,-81.452637&spn=0.894594,1.766052&z=9)
Kettle Point 44 and Lambton Shores (http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.295199,-81.89209&spn=0.879579,1.766052&z=9)
Huron-Kinloss and Ashfield-Colborne-Wawanosh (http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.996766,-81.68335&spn=0.869366,1.766052&z=9)

Don't get me started on any more. There are too many to count.

If it were an isolated incident I'd suggest that Google has found the Lost Continent of Atlantis.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on November 28, 2009, 11:05:23 AM
U.S. 36 multiplexes with U.S. 600 and 2200. (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=terre+haute,+in&sll=37.0625,-95.677068&sspn=52.505328,78.662109&ie=UTF8&hq=&hnear=Terre+Haute,+Vigo,+Indiana&ll=39.809591,-87.52327&spn=0.200964,0.43808&z=12)

Further north, U.S. 136 joins with U.S. 1200, U.S. 1710, U.S. 1800, and U.S. 1875! (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=terre+haute,+in&sll=37.0625,-95.677068&sspn=52.505328,78.662109&ie=UTF8&hq=&hnear=Terre+Haute,+Vigo,+Indiana&ll=40.116152,-87.535286&spn=0.200065,0.43808&z=12)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on November 28, 2009, 06:26:22 PM
Google has been posting "Future" Interstates on the maps for awhile.  So, it's really not incorrect since they do have "Future I-269 Corridor" signs along that highway.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on November 28, 2009, 07:12:08 PM
this may be useful, but only depending on how close to a function I-269 the road is.

there is a "future I-69 corridor" sign posted on US-82 in Arkansas, corresponding to a future road that will cross 82.  As of 2008, when I was there, the trees have not even been cleared. 
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 28, 2009, 07:58:09 PM
Especially since these routes aren't marked as future.  There's nothing to distinguish them from a route that actually exists!
Title: Re: Incorrect highways marked on Google Maps
Post by: froggie on November 28, 2009, 09:51:31 PM
Quotethis may be useful, but only depending on how close to a function I-269 the road is.

The road in question is full freeway, with the stretch west of I-40 having been completed for several years.  I don't recall if that stretch is Interstate-grade, but the segment south of I-40 most likely is.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on November 28, 2009, 10:15:56 PM
Quote from: froggie on November 28, 2009, 09:51:31 PM

The road in question is full freeway, with the stretch west of I-40 having been completed for several years.  I don't recall if that stretch is Interstate-grade, but the segment south of I-40 most likely is.


the average driver will not care if an on-ramp has a turning radius one foot too tight ... labeling it I-269 on Google maps is fine.

if I-278 through the Bronx is interstate-grade, anything is.
Title: Re: Incorrect highways marked on Google Maps
Post by: froggie on November 29, 2009, 07:40:11 AM
Quotethe average driver will not care if an on-ramp has a turning radius one foot too tight

The average driver may not.  But FHWA will.  And they're footing most of the bill.

Your I-278 example doesn't really compare since it was an older route that was grandfathered in.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 29, 2009, 10:40:25 AM
Quote from: froggie on November 29, 2009, 07:40:11 AM

Your I-278 example doesn't really compare since it was an older route that was grandfathered in.

So why can't the grandfathering happen to NY 17 (which is mostly freeway except for two portions with at-grade intersections)?
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on November 29, 2009, 11:53:14 AM
Quote from: froggie on November 29, 2009, 07:40:11 AM
The average driver may not.  But FHWA will.  And they're footing most of the bill.

Your I-278 example doesn't really compare since it was an older route that was grandfathered in.


I-278 isn't just below standard - it is significantly below standard.  It is a disgrace to the system.  I say we kick that one out and use those oh-so-precious chargeable miles on something like I-269 which, at the very least, has more than one lane.
Title: Re: Incorrect highways marked on Google Maps
Post by: froggie on November 30, 2009, 07:57:20 AM
QuoteSo why can't the grandfathering happen to NY 17 (which is mostly freeway except for two portions with at-grade intersections)?

Because, unlike I-278, NY 17 didn't exist as it does today when the Interstate system was created.


QuoteI-278 isn't just below standard - it is significantly below standard.  It is a disgrace to the system.  I say we kick that one out and use those oh-so-precious chargeable miles on something like I-269 which, at the very least, has more than one lane.

Agree that it's significantly below standard.  Disagree that it's a disgrace....it's still very much a major part of the system.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 30, 2009, 06:09:41 PM
So grandfathering only counts for routes that were being incorporated into the original system?  Looks like a huge double standard to me.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on November 30, 2009, 06:48:45 PM
yep, sounds like political grift all the way.

idealism: "yay! let's make a great system of roads that will be completely at-grade separated, with at least two lanes in each direction!  It will be so delightful and there'll be dancing bears and world peace!"

reality: "psst, you want me to vote on your pork bill, Congressman?  how about you let us sign US-30 through Breezewood with the red, white, and blue shields."
Title: Re: Incorrect highways marked on Google Maps
Post by: SSOWorld on November 30, 2009, 06:54:17 PM
As long as you put "To" above it, that will be fine</traditionalist politician>
Title: Re: Incorrect highways marked on Google Maps
Post by: andytom on December 01, 2009, 04:54:36 PM
Quote from: deanej on November 30, 2009, 06:09:41 PM
So grandfathering only counts for routes that were being incorporated into the original system?

For routes not yet in the system, yes.  Once the system is established, grandfathering only applies to routes already in the system when standards change.  Routes not already in the system have to follow the rules to get in.

Quote from: deanej on November 30, 2009, 06:09:41 PM
Looks like a huge double standard to me.

Not at all.  At the time the system was established, I-278 was close to, if not up to, the current interstate standard at the time.  NY 17 was nowhere close.

--Andy
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 01, 2009, 05:05:28 PM
As far as I'm concerned, existing routes should be forced to update to the new standards; otherwise there is little point to updating the standards (as the system is considered "complete").

I've never been on the Quickway, but as far as I can tell, aside from the at-grade portions, any non-standard sections are just nitpicking with the standards.  It looks just fine on a map.
Title: Re: Incorrect highways marked on Google Maps
Post by: andytom on December 01, 2009, 05:32:41 PM
Quote from: deanej on December 01, 2009, 05:05:28 PM
As far as I'm concerned, existing routes should be forced to update to the new standards; otherwise there is little point to updating the standards (as the system is considered "complete").

Mm hmm.  So, who's gonna cough up the money to do that each time?  The point of the standard is that you have something to build to and that every mile of the current system was up to an interstate standard at some point.  If every mile had to be upgraded to standard when the new standard came out, the whole system would be under construction in perpetuity and never be 'complete'.

Quote from: deanej
I've never been on the Quickway, but as far as I can tell, aside from the at-grade portions, any non-standard sections are just nitpicking with the standards.  It looks just fine on a map.

So, from that line on the map, you can tell that:

You can get your truck underneath the bridges,

You can get your truck around the curves at speed,

You can get your truck up and down the hills safely,

You have a suitable place to park your truck if it stops running.

--Andy
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on December 01, 2009, 06:37:22 PM
Quote from: andytom on December 01, 2009, 04:54:36 PM

Not at all.  At the time the system was established, I-278 was close to, if not up to, the current interstate standard at the time.  NY 17 was nowhere close.

Absolutely not.  I-278 was barely all freeway, and one section is a parkway that doesn't allow trucks.  It was let in with numerous exceptions - and many routes nowadays also allow exceptions as well.  It's part of the application process.

Quote from: andytom on December 01, 2009, 05:32:41 PM
Quote from: deanej on December 01, 2009, 05:05:28 PM

I've never been on the Quickway, but as far as I can tell, aside from the at-grade portions, any non-standard sections are just nitpicking with the standards.  It looks just fine on a map.

So, from that line on the map, you can tell that:

You can get your truck underneath the bridges,

You can get your truck around the curves at speed,

You can get your truck up and down the hills safely,

You have a suitable place to park your truck if it stops running.

--Andy


Hey Andy, can you tell all those things about the current Interstates either or, for that matter, ANY other line on a map?  That's the reason design exceptions are allowed.  It's a question of what's reasonable to require vs. what costs too much money for the incremental increase toward standards.  I've driven NY 17 end to end, and east of Binghamton, other than the at-grades there's precious little that really gets in the way.  I believe there are exceptions for things like shoulder width and possibly a curve radius or two already approved - meaning I-86 won't be up to Interstate standards (technically) when it's designated fully.  Again, all part of the game.
Title: Re: Incorrect highways marked on Google Maps
Post by: SSOWorld on December 01, 2009, 07:49:11 PM
I-39 is a good example of one - it had low bridges over 10 miles of its northern end.  (still does in places - but replacements are underway.)

I've ran into several interstates that had low bridges - like I-90 in Coeur d'Alene ID.
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on December 01, 2009, 08:22:00 PM
Quote from: agentsteel53 on November 30, 2009, 06:48:45 PMreality: "psst, you want me to vote on your pork bill, Congressman?  how about you let us sign US-30 through Breezewood with the red, white, and blue shields."

In reality, 70 is not signed through Breezewood.
Title: Re: Incorrect highways marked on Google Maps
Post by: andytom on December 02, 2009, 04:57:16 PM
Quote from: AlpsROADS on December 01, 2009, 06:37:22 PM
Quote from: andytom

Not at all.  At the time the system was established, I-278 was close to, if not up to, the current interstate standard at the time.  NY 17 was nowhere close.

Absolutely not.  I-278 was barely all freeway, and one section is a parkway that doesn't allow trucks.  It was let in with numerous exceptions - and many routes nowadays also allow exceptions as well.  It's part of the application process.

Of course I know about exceptions.  Except in a few locations, these are usually few and far between and usually don't break the rules by much.  The point of my statement was that, at the time that the system was established, the barely freeway that became I-278 was a lot closer to the initial interstate standard than the undivided hwy that was most of NY-17.  Even in 1970, more than half of NY-17 was still undivided.


Quote from: AlpsROADS
Quote from: andytom
Quote from: deanej

I've never been on the Quickway, but as far as I can tell, aside from the at-grade portions, any non-standard sections are just nitpicking with the standards.  It looks just fine on a map.

So, from that line on the map, you can tell that:

You can get your truck underneath the bridges,

You can get your truck around the curves at speed,

You can get your truck up and down the hills safely,

You have a suitable place to park your truck if it stops running.

--Andy


Hey Andy, can you tell all those things about the current Interstates either or, for that matter, ANY other line on a map?  That's the reason design exceptions are allowed.  It's a question of what's reasonable to require vs. what costs too much money for the incremental increase toward standards.  I've driven NY 17 end to end, and east of Binghamton, other than the at-grades there's precious little that really gets in the way.  I believe there are exceptions for things like shoulder width and possibly a curve radius or two already approved - meaning I-86 won't be up to Interstate standards (technically) when it's designated fully.  Again, all part of the game.

Concerning the line on the map, you make my point for me.  The line only specifies the classification (freeway, divided, paved, unparved).  The shield on that line provides more information.  If it's an Interstate shield, you know that it was built, with a few exceptions, to a standard.  Nowdays, if it's a US hwy shield, that also has to meet certain standards for a change of alignment or extension to be approved.

--Andy
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr_Northside on December 03, 2009, 09:37:49 AM
Quote from: PAHighways on December 01, 2009, 08:22:00 PM
Quote from: agentsteel53 on November 30, 2009, 06:48:45 PMreality: "psst, you want me to vote on your pork bill, Congressman?  how about you let us sign US-30 through Breezewood with the red, white, and blue shields."

In reality, 70 is not signed through Breezewood.

With I-70 in PA, I'm not sure what is a more egregious example of making exceptions.... Breezewood, with a (relatively) brief section (being technically signed or not notwithstanding) of surface highway, a quirk of PennDOT & the Tpk not building it properly and local interests opposed to "fixing" the situation...
OR
The section between New Stanton & Washngton, PA... it's "limited access", but woefully substandard... not for a brief section, but for almost 40 miles.
I'm not sure what's worse.
(Some of the sections of Turnpike that haven't been rebuilt yet aren't all that great either...)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 09, 2009, 08:42:56 PM
I didn't know that I-86 was designated past Elmira yet... :spin:

http://maps.google.com/maps?ie=UTF8&hl=en&hq=&hnear=Rochester,+Monroe,+New+York&ll=42.027874,-76.660538&spn=0.310621,0.724411&z=11
Title: Re: Incorrect highways marked on Google Maps
Post by: mgk920 on December 10, 2009, 08:11:05 PM
Another:

For a nice 'promotion' of a gravel-surfaced local road, zoom in on Rapelje, MT on their map (it's a little bit northwest of Billings, MT).

:cool:

(That area is middle-of-nowhere solitude central, BTW.)

Mike
Title: Re: Incorrect highways marked on Google Maps
Post by: Fcexpress80 on December 17, 2009, 08:26:46 PM
Interesting note:  Google EARTH is jumping the gun by labling Alaska's highways with the as yet to be officially posted Interstate designations, A-1, A-2, A-3, and A-4.  While this would make sense where these highways meet Interstate highway standards, mainly in the Anchorage area and somewhat in the Fairbanks area; the two lane undivided rural roads should not be labeled as such, in my opinion.
Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on December 18, 2009, 12:11:28 AM
Quote from: Fcexpress80 on December 17, 2009, 08:26:46 PM
Interesting note:  Google EARTH is jumping the gun by labling Alaska's highways with the as yet to be officially posted Interstate designations, A-1, A-2, A-3, and A-4.  While this would make sense where these highways meet Interstate highway standards, mainly in the Anchorage area and somewhat in the Fairbanks area; the two lane undivided rural roads should not be labeled as such, in my opinion.

Those designations officially exist; they just are not signed and are, as far as I am aware, not required to meet interstate standards (basically, the routes get federal funding but are not necessarily freeways). Therefore, Google Maps/Earth labeling them as such is not an error.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on December 18, 2009, 12:47:09 AM
Quote from: SyntheticDreamer on December 18, 2009, 12:11:28 AM


Those designations officially exist; they just are not signed and are, as far as I am aware, not required to meet interstate standards (basically, the routes get federal funding but are not necessarily freeways). Therefore, Google Maps/Earth labeling them as such is not an error.

they will be signposted in the field?
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on December 18, 2009, 12:47:32 AM
Quote from: SyntheticDreamer on December 18, 2009, 12:11:28 AM
Those designations officially exist; they just are not signed and are, as far as I am aware, not required to meet interstate standards (basically, the routes get federal funding but are not necessarily freeways). Therefore, Google Maps/Earth labeling them as such is not an error.

Yes, but as the designations are not signed, they shouldn't be shown on the maps as they can confuse people.  (Like I-595 in Maryland or the numerous "secret" routes coincident with US Routes here in the South)
Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on December 18, 2009, 01:20:06 AM
Okay, I suppose it both is and isn't an error in that case. :p
Title: Re: Incorrect highways marked on Google Maps
Post by: froggie on December 18, 2009, 07:03:22 AM
As long as they got the designations correct, it's not an error, period.  That said, whether or not to label them, when they're not signed as such in the field plus the confusion factor that mightyace noted, is debatable...
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on December 18, 2009, 07:42:00 PM
Quote from: froggie on December 18, 2009, 07:03:22 AM
As long as they got the designations correct, it's not an error, period.  That said, whether or not to label them, when they're not signed as such in the field plus the confusion factor that mightyace noted, is debatable...

True, but I'm definitely against showing them for another reason.  I now have a Motorola Droid phone using the Google Android platform.  It has a GPS navigation function in with the Droid version of Google maps.  I tested it on a recent trip around this area and the directions told be to turn on the hidden highway instead of the signed one.  :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on February 06, 2010, 09:44:48 PM
Trying to get from Tulsa to Independence, KS? Better take US-3300 (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=independence+KS&sll=37.0625,-95.677068&sspn=41.767874,93.076172&ie=UTF8&hq=&hnear=Independence,+Montgomery,+Kansas&ll=37.187126,-95.774002&spn=0.041164,0.090895&z=14).
Title: Re: Incorrect highways marked on Google Maps
Post by: xonhulu on February 06, 2010, 10:42:39 PM
Quote from: Scott5114 on February 06, 2010, 09:44:48 PM
Trying to get from Tulsa to Independence, KS? Better take US-3300 (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=independence+KS&sll=37.0625,-95.677068&sspn=41.767874,93.076172&ie=UTF8&hq=&hnear=Independence,+Montgomery,+Kansas&ll=37.187126,-95.774002&spn=0.041164,0.090895&z=14).

The 33rd branch route of US 0?  It is near US 400.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on February 15, 2010, 02:23:22 PM
As if South Boulevard did not have enough highways sharing its pavement, U.S. 43 (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=montgomery,+al&sll=37.0625,-95.677068&sspn=43.443045,93.076172&ie=UTF8&hq=&hnear=Montgomery,+Alabama&ll=32.367493,-86.285934&spn=0.181818,0.494385&z=12) now joins the fold!
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on February 15, 2010, 04:59:30 PM
Good to see another I-264 pop up, but this is an odd spot

http://maps.google.com/?ie=UTF8&ll=31.655062,-93.824379&spn=0.01295,0.027874&z=16
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on February 16, 2010, 02:23:28 PM
^^ That's worse than I-99! :)
Title: Re: Incorrect highways marked on Google Maps
Post by: okroads on February 16, 2010, 04:44:46 PM
Here is U.S. 2556 in the Rio Grande Valley:
http://maps.google.com/?ie=UTF8&ll=26.17824,-97.803898&spn=0.093048,0.132008&z=13
Title: Re: Incorrect highways marked on Google Maps
Post by: Ian on February 17, 2010, 09:52:22 PM
US 666 lives on...
http://maps.google.com/maps?ie=UTF8&hl=en&ll=34.098301,-109.23852&spn=0.034542,0.076818&t=h&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on February 17, 2010, 09:56:37 PM
In that case, so does US-187

http://maps.google.com/maps?ie=UTF8&hl=en&ll=41.792561,-109.331474&spn=0.102899,0.338173&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: CL on February 18, 2010, 07:54:55 PM
Eastbound Center Street turns into a freeway alignment for a block.

http://maps.google.com/?ie=UTF8&hq=&hnear=Salt+Lake+City,+Salt+Lake,+Utah&ll=40.233707,-111.665951&spn=0.004529,0.009645&z=17
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on February 18, 2010, 10:09:32 PM
http://maps.google.com/maps?hl=en&ie=UTF8&ll=42.953643,-76.980214&spn=0.007758,0.013797&z=16

Since when was NY 318 extended onto interchange 42?
Title: Re: Incorrect highways marked on Google Maps
Post by: Duke87 on May 08, 2010, 10:58:13 AM
Okay, I know Pennsylvania loves to name towns weird things like "Moon", "Pillow", or "Bird in Hand", but this is taking it to a whole new level (http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=40.979898,-75.301151&spn=0.062205,0.154324&z=13).
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg98.imageshack.us%2Fimg98%2F2697%2Fgooglemapspaarabic.png&hash=1bfc12d100f9767acef0d89b8cf07c9e50ed93fd)

Random Arabic! :spin:
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on May 08, 2010, 12:12:14 PM
well, you know how those Amish are with their strange hobbies in the absence of electricity,  "learn Arabic" is just a few notches higher than "churn butter", apparently.
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on May 08, 2010, 12:17:55 PM
On that note- this popped up north of Laramie a while ago (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=laramie+wy&sll=37.0625,-95.677068&sspn=28.196369,86.572266&ie=UTF8&hq=&hnear=Laramie,+Albany,+Wyoming&ll=41.435777,-105.56488&spn=0.103985,0.338173&z=12). The Japanese is Japanese for "Wyoming" which is interesting because about a month ago Google showed a small community called "Wyoming" in the same spot. I have no idea what the town Test- Wrong Locality is all about

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.davidjcorcoran.com%2Fgooglelaramie.jpg&hash=be7387b76fa29db4ee4702cdfa537fdae189b320)
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on May 08, 2010, 12:23:44 PM
Quote from: corco on May 08, 2010, 12:17:55 PMTest- Wrong Locality

site of a battle between the US Army and the Wrong Locality Sioux in 1886.
Title: Re: Incorrect highways marked on Google Maps
Post by: Duke87 on May 12, 2010, 11:40:02 PM
Rhode Island is also in on the new Arabic trend (http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=41.589513,-71.653862&spn=0.122996,0.308647&z=12):
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg684.imageshack.us%2Fimg684%2F2166%2Fgooglemapsriarabic.png&hash=ca84511dba3fc42f2eb75232c5d00fc6d9fb19df)

And then there's this (http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=41.206039,-73.02269&spn=0.249514,0.617294&z=11):
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg513.imageshack.us%2Fimg513%2F5802%2Fmilfordcitybalance.png&hash=cc86c8a22f7019344345808058c9b8ab9f5afee2)

The city of Milford, CT is indeed at that location, but I've never heard it referred to as "Milford City". The "(balance)" part makes no sense whatsoever.
Title: Re: Incorrect highways marked on Google Maps
Post by: jdb1234 on August 17, 2010, 10:33:39 PM
i was looking at Louisville, KY and since when did US 7 and US 50 get extended to Kentucky?
Title: Re: Incorrect highways marked on Google Maps
Post by: mapman on August 18, 2010, 12:46:11 AM
Quote from: Duke87 on May 12, 2010, 11:40:02 PM
The city of Milford, CT is indeed at that location, but I've never heard it referred to as "Milford City". The "(balance)" part makes no sense whatsoever.

"Milford" refers to the central portion of Milford, CT, while "Milford City (balance)" refers to the balance, or rest, of Milford.  See, simple!    :sombrero:

Now, excuse me while I head to bed, or, as Google calls it, "House (balance)." 
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on August 18, 2010, 06:42:25 AM
"(balance)" usually refers to a sort of fiction invented to make Census figures come out more useful, especially in the case of consolidated city-counties. Here's the Wikipedia entry on "balances" (http://en.wikipedia.org/wiki/Consolidated_city-county#Balances). Pretty much how the equation works is "Balance + population of any cities independent of the consolidated government = county population total".

Not sure what that has to do with Milford, but the article section above gives several examples of (balance)s.
Title: Re: Incorrect highways marked on Google Maps
Post by: NWI_Irish96 on August 18, 2010, 08:12:40 AM
US 150 is apparently also secretly US 7 for its entire length.



Title: Re: Incorrect highways marked on Google Maps
Post by: huskeroadgeek on August 18, 2010, 04:18:24 PM
Quote from: Scott5114 on August 18, 2010, 06:42:25 AM
"(balance)" usually refers to a sort of fiction invented to make Census figures come out more useful, especially in the case of consolidated city-counties. Here's the Wikipedia entry on "balances" (http://en.wikipedia.org/wiki/Consolidated_city-county#Balances). Pretty much how the equation works is "Balance + population of any cities independent of the consolidated government = county population total".

Not sure what that has to do with Milford, but the article section above gives several examples of (balance)s.
I think what it has to do with here is Connecticut's town structure, which is the primary method of local government. The state is divided into 169 towns that in many cases don't correspond to what we would think of as cities in most states. Instead of having cities with corporate limits surrounded by unincorporated areas, every piece of land in the state is under the jurisdiction of a town-there are no unincorporated areas. A town is more like one main city with other smaller towns put together in one single governmental unit. So I think here it is distinguishing between the main part of Milford and the "balance" is the rest of the town which is part of the town of Milford(officially called a city-a distinction which makes no difference in this case), but not part of the central city.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on August 18, 2010, 10:01:24 PM
Google's rendition of ME 92 bugged me up good.  92 EB doesn't turn left to get back to 1 - it goes all the way down the peninsula and ends at a dirt driveway with little warning.  Not the best way to spend a frantic night of driving...
Title: Re: Incorrect highways marked on Google Maps
Post by: TheStranger on August 18, 2010, 10:28:49 PM
Google Maps's view of the harbor area in Los Angeles shows Route 47 as making an odd left turn onto Anaheim Street to reach Alameda Street, instead of correctly simply continuing straight on Henry Ford Avenue to reach Alameda:

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Henry+Ford+Ave+%26+E+Anaheim+St,+Long+Beach,+CA&sll=33.780681,-118.23864&sspn=0.019012,0.027595&ie=UTF8&hq=&hnear=E+Anaheim+St+%26+N+Henry+Ford+Ave,+Los+Angeles,+California+90744&z=16
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on August 20, 2010, 03:01:01 AM
Quote from: cabiness42 on August 18, 2010, 08:12:40 AM
US 150 is apparently also secretly US 7 for its entire length.


It appears that U.S. 7 makes its way westward via the Bel Air and Hickory Business Loops (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Aberdeen,+MD&sll=39.581028,-78.845441&sspn=0.021003,0.052142&g=Bel+Air,+MD&ie=UTF8&hq=&hnear=Aberdeen,+Harford,+Maryland&ll=39.543764,-76.339531&spn=0.084058,0.208569&z=13) of U.S. 1 in Maryland!
Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on October 20, 2010, 08:42:28 PM
Next time I'm in Illinois, I need to see about clinching US 1275, US 1360, and US 1250 (scroll left) (http://maps.google.com/?ie=UTF8&ll=39.110183,-88.57285&spn=0.01988,0.045447&z=15).
Title: Re: Incorrect highways marked on Google Maps
Post by: TheStranger on October 25, 2010, 07:59:53 PM
I wouldn't call it incorrect, but the unsigned I-305 in Sacramento is now being marked on Google Maps!

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=95819&sll=37.0625,-95.677068&sspn=47.215051,78.662109&ie=UTF8&hq=&hnear=Sacramento,+California+95819&ll=38.568435,-121.473684&spn=0.045835,0.076818&z=14&layer=t
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on October 25, 2010, 08:21:13 PM
Quote from: TheStranger on October 25, 2010, 07:59:53 PM
I wouldn't call it incorrect, but the unsigned I-305 in Sacramento is now being marked on Google Maps!

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=95819&sll=37.0625,-95.677068&sspn=47.215051,78.662109&ie=UTF8&hq=&hnear=Sacramento,+California+95819&ll=38.568435,-121.473684&spn=0.045835,0.076818&z=14&layer=t

That and Google should get off their asses and post Business Interstates with the Green Shields instead of the normal one...............
Title: Re: Incorrect highways marked on Google Maps
Post by: exit322 on October 25, 2010, 08:48:26 PM
Quote from: rickmastfan67 on October 25, 2010, 08:21:13 PM
That and Google should get off their asses and post Business Interstates with the Green Shields instead of the normal one...............

I contend they should get ON their asses to do this.  It's far easier, I've found, to use the computer sitting down.  :-D

But yeah, the technology is there to make the shields on maps look like what they'll look like in the wild - and you don't even have to change the circles for every state, people!
Title: Re: Incorrect highways marked on Google Maps
Post by: CL on October 25, 2010, 09:06:09 PM
I-15 through Salt Lake City (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Salt+Lake+City+UT&sll=37.0625,-95.677068&sspn=38.365962,79.013672&ie=UTF8&hq=&hnear=Salt+Lake+City,+Salt+Lake,+Utah&ll=40.699642,-111.898069&spn=0.035919,0.077162&z=14) (actually, looks like the entire length of freeway (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Butte+MT&sll=45.663966,-112.456055&sspn=2.119123,4.938354&ie=UTF8&hq=&hnear=Butte,+Silver+Bow,+Montana&ll=45.991058,-112.533646&spn=0.032917,0.077162&z=14), and here too (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=St+George+UT&sll=45.991058,-112.533646&sspn=0.032917,0.077162&ie=UTF8&hq=&hnear=St+George,+Washington,+Utah&ll=37.100577,-113.565416&spn=0.018894,0.038581&z=15)) has been designated the Barstow and Mojave Freeway. This just appeared in the last week I believe.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on January 14, 2011, 08:23:50 PM
Next time I visit Ypsilanti, MI, I need to clinch "; U.S. 12":

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Flh3.ggpht.com%2F_AXtC_YsMww4%2FTTDzziE8mxI%2FAAAAAAAAA3s%2FY3tcoxm5drY%2Fs800%2Fmidriverror.jpg&hash=c185d4a110e8bfeec33f907fdf24926db6e314b7)

Title: Re: Incorrect highways marked on Google Maps
Post by: WillWeaverRVA on January 14, 2011, 08:38:00 PM
Quote from: MDOTFanFB on January 14, 2011, 08:23:50 PM
Next time I visit Ypsilanti, MI, I need to clinch "; U.S. 12":

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Flh3.ggpht.com%2F_AXtC_YsMww4%2FTTDzziE8mxI%2FAAAAAAAAA3s%2FY3tcoxm5drY%2Fs800%2Fmidriverror.jpg&hash=c185d4a110e8bfeec33f907fdf24926db6e314b7)



Which site is that? That doesn't look like Google Maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 14, 2011, 08:52:36 PM
Given the semicolon, I'd guess it's something based on OpenStreetMap data (OSM uses a semicolon for overlaps). But there's no ref tag, only a relation with slightly-strange network=US:US:BUSINESS ref=BUS US 12, so maybe not. Anyway, maps have errors.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on January 14, 2011, 09:06:04 PM
Looks like MapQuest based on OSM data.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on January 14, 2011, 10:12:09 PM
Quote from: SyntheticDreamer on January 14, 2011, 08:38:00 PM
Which site is that? That doesn't look like Google Maps.

http://mdotnetpublic.state.mi.us/drive/ (http://mdotnetpublic.state.mi.us/drive/)

Right now I am watching a live cam of M-39 south at 8 Mile Road (M-102) waitng for the overpass to be torn down. RIP overpass (196x-2011)
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on January 14, 2011, 10:32:35 PM
Quote from: rickmastfan67 on October 25, 2010, 08:21:13 PMThat and Google should get off their asses and post Business Interstates with the Green Shields instead of the normal one...............

And post banners, period.  Heaven help the person relying on Google Maps and trying to figure out why a route splits into parallel alignments with the same number (http://maps.google.com/?ie=UTF8&ll=38.390783,-78.24244&spn=0.013488,0.0262&z=16).
Title: Re: Incorrect highways marked on Google Maps
Post by: rawmustard on January 15, 2011, 08:02:51 AM
Quote from: MDOTFanFB on January 14, 2011, 10:12:09 PM
http://mdotnetpublic.state.mi.us/drive/

Right now I am watching a live cam of M-39 south at 8 Mile Road (M-102) waitng for the overpass to be torn down. RIP overpass (196x-2011)

Maybe MDOT will make a time-lapse video of the demolition from that feed considering it has posted demolitions of other overpasses to its YouTube channel (http://www.youtube.com/user/MichiganDOT).
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek Adam on January 25, 2011, 04:50:13 PM
http://maps.google.com/maps?q=Millburn+NJ&oe=utf-8&client=firefox-a&ie=UTF8&hq=&hnear=Millburn,+Essex,+New+Jersey&gl=us&ll=40.740364,-74.302769&spn=0.092865,0.154324&z=13

CR 527 got a promotion in Millburn.
Title: Re: Incorrect highways marked on Google Maps
Post by: Revive 755 on January 25, 2011, 05:12:59 PM
I'm seeing a new I-136 in Nebraska, Missouri, and Illinois today:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=39.88445,-94.130859&spn=6.372267,21.09375&z=7 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=39.88445,-94.130859&spn=6.372267,21.09375&z=7)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on January 25, 2011, 05:37:31 PM
Quote from: Revive 755 on January 25, 2011, 05:12:59 PM
I'm seeing a new I-136 in Nebraska, Missouri, and Illinois today:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=39.88445,-94.130859&spn=6.372267,21.09375&z=7 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=39.88445,-94.130859&spn=6.372267,21.09375&z=7)

And I've also seen that US-52 in the entire US has been decommisioned by Google at the same time.  Only has the text of "US-52" along any part of it's alignment except in one very small area of NC just outside of Mt. Airy.  That and the Darlington, SC Business route.
Title: Re: Incorrect highways marked on Google Maps
Post by: US71 on January 25, 2011, 05:53:59 PM
There's a US 1120 near Muldrow, OK
http://maps.google.com/maps?client=opera&q=muldrow,+OK&oe=utf-8&ie=UTF8&hq=&hnear=Muldrow,+Sequoyah,+Oklahoma&gl=us&ll=35.387231,-94.551601&spn=0.083409,0.132351&z=13
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on January 31, 2011, 04:30:28 PM
Alright, who had modified M-17 to run along the Wisconsin border? http://maps.google.com/maps?hl=en&ie=UTF8&ll=46.079408,-88.946857&spn=0,0.02738&z=16&layer=c&cbll=46.079362,-88.946748&panoid=JHzSruqePhDOKjZSzPv6dA&cbp=12,117.62,,0,6.76 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=46.079408,-88.946857&spn=0,0.02738&z=16&layer=c&cbll=46.079362,-88.946748&panoid=JHzSruqePhDOKjZSzPv6dA&cbp=12,117.62,,0,6.76)

If you click back twice, notice that it shows the correct WI 17.

Just found out that Google has re-restructed M-108 after it has been decomissioned for over a month! http://maps.google.com/maps?hl=en&ie=UTF8&ll=45.784105,-84.731852&spn=0.005671,0.01369&z=17 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=45.784105,-84.731852&spn=0.005671,0.01369&z=17)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 31, 2011, 09:48:58 PM
Oh no! A map is a month out of date!
Title: Re: Incorrect highways marked on Google Maps
Post by: bulldog1979 on February 01, 2011, 05:57:20 AM
Quote from: MDOTFanFB on January 31, 2011, 04:30:28 PM
Just found out that Google has re-restructed M-108 after it has been decomissioned for over a month! http://maps.google.com/maps?hl=en&ie=UTF8&ll=45.784105,-84.731852&spn=0.005671,0.01369&z=17 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=45.784105,-84.731852&spn=0.005671,0.01369&z=17)

Not only that, but they extended it down old US 31. Don't worry, I've already filed an error report, and notified them of the exact jurisdictional transfer date.
Title: Re: Incorrect highways marked on Google Maps
Post by: froggie on February 01, 2011, 08:14:12 AM
QuoteAnd I've also seen that US-52 in the entire US has been decommisioned by Google at the same time.

Not entirely.  Still shown "shielded" in Minnesota and Iowa.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on February 01, 2011, 02:15:29 PM
Take a look at this:
http://goo.gl/maps/DNez

To the best of my knowledge, this road configuration never existed (and never will); here's another: http://goo.gl/maps/ksMm
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 02, 2011, 05:12:35 PM
Quote from: froggie on February 01, 2011, 08:14:12 AM
QuoteAnd I've also seen that US-52 in the entire US has been decommisioned by Google at the same time.

Not entirely.  Still shown "shielded" in Minnesota and Iowa.

Anyways, Google responded to my report on this and they said I was "right".  Well, of course I was right. :spin:  Hopefully it will not take them 2 months to get it fixed. lol.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on February 02, 2011, 10:51:23 PM
Quote from: Roadgeek_Adam on January 25, 2011, 04:50:13 PM
http://maps.google.com/maps?q=Millburn+NJ&oe=utf-8&client=firefox-a&ie=UTF8&hq=&hnear=Millburn,+Essex,+New+Jersey&gl=us&ll=40.740364,-74.302769&spn=0.092865,0.154324&z=13

CR 527 got a promotion in Millburn.

That's quite the promotion!  I remember a while ago (not sure how long ago, could be quite some time), they had all the 500-series routes (and I think a few regular county routes too) marked with the state route symbol.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on February 03, 2011, 07:39:39 PM
Quote from: Kacie Jane on February 02, 2011, 10:51:23 PM
Quote from: Roadgeek_Adam on January 25, 2011, 04:50:13 PM
http://maps.google.com/maps?q=Millburn+NJ&oe=utf-8&client=firefox-a&ie=UTF8&hq=&hnear=Millburn,+Essex,+New+Jersey&gl=us&ll=40.740364,-74.302769&spn=0.092865,0.154324&z=13

CR 527 got a promotion in Millburn.

That's quite the promotion!  I remember a while ago (not sure how long ago, could be quite some time), they had all the 500-series routes (and I think a few regular county routes too) marked with the state route symbol.
Actually yes, it's been years since I recall that. Early NJ maps (1960s) would show the 5xx in the same symbol as state highways, sometimes. Other maps would show them in blue vs. the standard black squares.
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on February 14, 2011, 09:00:34 PM
http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.081113,-77.493739&spn=0.016613,0.027595&z=15

Dang it, Google, why did you have to go and break NY 31? I don't think it has anything to do with construction, as NYSDOT's site doesn't mention any construction on NY 31 around there. Also, it's still possible to route driving directions to use the "broken" part, like here: http://maps.google.com/maps?f=d&source=s_d&saddr=NY-31+W%2FPalmyra+Rd%2FPittsford+Palmyra+Rd&daddr=NY-31+W%2FPalmyra+Rd%2FPittsford+Palmyra+Rd&geocode=FQRUkQIdprFh-w%3BFdZjkQIdqH1h-w&hl=en&mra=dme&mrcr=0&mrsp=1&sz=15&sll=43.078104,-77.486444&sspn=0.016614,0.027595&ie=UTF8&z=15
Title: Re: Incorrect highways marked on Google Maps
Post by: cu2010 on February 14, 2011, 09:22:28 PM
Quote from: deanej on February 01, 2011, 02:15:29 PM
To the best of my knowledge, this road configuration never existed (and never will); here's another: http://goo.gl/maps/ksMm

The map is correct. The overhead image is an old shot; that entire intersection was reconstructed along with the new border station a few years back. 37 is no longer divided through there, and the circle replaced with the configuration shown in the map.
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on February 14, 2011, 09:24:26 PM
Quote from: WNYroadgeek on February 14, 2011, 09:00:34 PM
http://maps.google.com/maps?hl=en&ie=UTF8&ll=43.081113,-77.493739&spn=0.016613,0.027595&z=15

Dang it, Google, why did you have to go and break NY 31? I don't think it has anything to do with construction, as NYSDOT's site doesn't mention any construction on NY 31 around there. Also, it's still possible to route driving directions to use the "broken" part, like here: http://maps.google.com/maps?f=d&source=s_d&saddr=NY-31+W%2FPalmyra+Rd%2FPittsford+Palmyra+Rd&daddr=NY-31+W%2FPalmyra+Rd%2FPittsford+Palmyra+Rd&geocode=FQRUkQIdprFh-w%3BFdZjkQIdqH1h-w&hl=en&mra=dme&mrcr=0&mrsp=1&sz=15&sll=43.078104,-77.486444&sspn=0.016614,0.027595&ie=UTF8&z=15

Huh, you can view Street View of the "missing" section, too.

That's weird.

(edited to add quote, so people know what I'm talking about)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 14, 2011, 10:33:23 PM
Quote from: cu2010 on February 14, 2011, 09:22:28 PM
Quote from: deanej on February 01, 2011, 02:15:29 PM
To the best of my knowledge, this road configuration never existed (and never will); here's another: http://goo.gl/maps/ksMm

The map is correct. The overhead image is an old shot; that entire intersection was reconstructed along with the new border station a few years back. 37 is no longer divided through there, and the circle replaced with the configuration shown in the map.

http://mapq.st/g2lYg3
Title: Re: Incorrect highways marked on Google Maps
Post by: cu2010 on February 14, 2011, 10:48:47 PM
Quote from: NE2 on February 14, 2011, 10:33:23 PM
http://mapq.st/g2lYg3

Aah, there we go.

Yes, that is the current configuration. I liked the old one better, but there was no room for the new border station in that configuration...
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 14, 2011, 10:59:50 PM
Thanks to MapQuest allowing tracing of their Open Aerial tiles, which includes that imagery (I think it's NAIP), OSM now has the new layout: http://www.openstreetmap.org/?lat=44.98106&lon=-74.73719&zoom=16&layers=M
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on February 15, 2011, 12:30:26 PM
Quote from: cu2010 on February 14, 2011, 10:48:47 PM
Quote from: NE2 on February 14, 2011, 10:33:23 PM
http://mapq.st/g2lYg3

Aah, there we go.

Yes, that is the current configuration. I liked the old one better, but there was no room for the new border station in that configuration...
The Google one is still wrong, but at least it's not as bad (according to Google, the left turn from NY 37 east to the bridge cannot be made).

I'm sure the US and Canada are going to regret reconfiguring all these border stations once Obama's new border policy (http://www.ottawacitizen.com/business/Harper+Obama+agree+integrate+border/4225641/story.html) goes through.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bigmikelakers on February 21, 2011, 02:37:21 AM
I wouldn't considered this to be a highway marked incorrectly but, google maps has Interstate 15 labeled as the Mojave/Barstow Freeway as far north as the Utah stateline. To my knowledge, the Barstow Freeway section of I-15 is from the I-10 jct in Ontario to I-40 in Barstow. The Mojave freeway stretch of I-15 is from I-40 to the Nevada stateline.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on February 21, 2011, 11:38:45 AM
I just noticed that Google put NY 598 in Syracuse on Teall Ave instead of Midler Ave.
Title: Re: Incorrect highways marked on Google Maps
Post by: CL on February 21, 2011, 11:55:25 AM
Quote from: Bigmikelakers on February 21, 2011, 02:37:21 AM
I wouldn't considered this to be a highway marked incorrectly but, google maps has Interstate 15 labeled as the Mojave/Barstow Freeway as far north as the Utah stateline. To my knowledge, the Barstow Freeway section of I-15 is from the I-10 jct in Ontario to I-40 in Barstow. The Mojave freeway stretch of I-15 is from I-40 to the Nevada stateline.

They used to have it designated as such all the way up to the Canadian border, and I guess they only cut it back to Arizona after I reported their error. Typical.
Title: Re: Incorrect highways marked on Google Maps
Post by: DeaconG on February 21, 2011, 05:06:35 PM
Why is Augusta, GA listed as "Augusta-Richmond County?" :confused:

Gee, if you're gonna go that route why don't we just add "Jacksonville-Duval County" while we're at it?

I hope I didn't give anyone at Google any ideas... :spin:
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael in Philly on February 23, 2011, 02:31:00 PM
Just discovered US 202 in King of Prussia, Pa., is marked as 202 and 206....
Title: Re: Incorrect highways marked on Google Maps
Post by: dfilpus on February 23, 2011, 03:57:01 PM
Quote from: DeaconG on February 21, 2011, 05:06:35 PM
Why is Augusta, GA listed as "Augusta-Richmond County?" :confused:

Gee, if you're gonna go that route why don't we just add "Jacksonville-Duval County" while we're at it?

I hope I didn't give anyone at Google any ideas... :spin:
Well, Augusta-Richmond County is an official name of the consolidated city/county. It is used on the city website.
Jacksonville does not use Jacksonville-Duval County as an official name.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on February 23, 2011, 04:03:26 PM
Quote from: dfilpus on February 23, 2011, 03:57:01 PM

Well, Augusta-Richmond County is an official name of the consolidated city/county. It is used on the city website.
Jacksonville does not use Jacksonville-Duval County as an official name.

and here in Southern California we have a city called El Pueblo de Nuestra Señora la Reina de los Ángeles del Río de Porciúncula, but there's no way in Hell anyone would put that on a sign!
Title: Re: Incorrect highways marked on Google Maps
Post by: Rover_0 on February 23, 2011, 07:05:33 PM
Also caught a US-9 and earler US-16 in Yuma, AZ.  I think that I remember a US-7 concurrent with US-93 in Nevada somewhere.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on February 24, 2011, 12:16:23 AM
Quote from: Michael in Philly on February 23, 2011, 02:31:00 PM
Just discovered US 202 in King of Prussia, Pa., is marked as 202 and 206....

All of 202 south of NY 59 is marked US 202/206. Another golden nugget from Google Maps along with US 527. :roll:
Title: Re: Incorrect highways marked on Google Maps
Post by: Bigmikelakers on February 24, 2011, 01:29:34 AM
Quote from: CL on February 21, 2011, 11:55:25 AM
Quote from: Bigmikelakers on February 21, 2011, 02:37:21 AM
I wouldn't considered this to be a highway marked incorrectly but, google maps has Interstate 15 labeled as the Mojave/Barstow Freeway as far north as the Utah stateline. To my knowledge, the Barstow Freeway section of I-15 is from the I-10 jct in Ontario to I-40 in Barstow. The Mojave freeway stretch of I-15 is from I-40 to the Nevada stateline.


They used to have it designated as such all the way up to the Canadian border, and I guess they only cut it back to Arizona after I reported their error. Typical.

Ahhh, I found another one. Interstate 10 is labeled Redlands Freeway from the 215 interchange to the Arizona stateline. I never heard of the Redlands Freeway being used in any map or anything else before. New to me.
Title: Re: Incorrect highways marked on Google Maps
Post by: Dr Frankenstein on February 24, 2011, 11:32:56 AM
In the past I remember seeing QC-335 in Montréal signed with an Ontario secondary highway shield... but it's no longer the case today.

But right now, the issue is that the exit number for exit 73 on A-40 is shown as "QC-335" instead of "73".
http://maps.google.ca/?ll=45.553632,-73.62373
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael in Philly on February 24, 2011, 11:44:07 AM
Quote from: Bigmikelakers on February 24, 2011, 01:29:34 AM
Quote from: CL on February 21, 2011, 11:55:25 AM
Quote from: Bigmikelakers on February 21, 2011, 02:37:21 AM
I wouldn't considered this to be a highway marked incorrectly but, google maps has Interstate 15 labeled as the Mojave/Barstow Freeway as far north as the Utah stateline. To my knowledge, the Barstow Freeway section of I-15 is from the I-10 jct in Ontario to I-40 in Barstow. The Mojave freeway stretch of I-15 is from I-40 to the Nevada stateline.


They used to have it designated as such all the way up to the Canadian border, and I guess they only cut it back to Arizona after I reported their error. Typical.

Ahhh, I found another one. Interstate 10 is labeled Redlands Freeway from the 215 interchange to the Arizona stateline. I never heard of the Redlands Freeway being used in any map or anything else before. New to me.


Actually, I have seen the Redlands Freeway designation on some commercial map or other.  Wouldn't have expected it to go all the way to Arizona, though.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadfro on February 26, 2011, 02:12:27 PM
Quote from: Rover_0 on February 23, 2011, 07:05:33 PM
I think that I remember a US-7 concurrent with US-93 in Nevada somewhere.

Google Maps must've pulled some source that made reference to the pre-1976 Nevada highway numbers. I don't remember if that error was marked as US 7 or SR 7...

Before 1976, SR 7 was legislatively designated concurrent with US 93 between I-15 and Ely.
Title: Re: Incorrect highways marked on Google Maps
Post by: kurumi on February 26, 2011, 04:31:16 PM
Quote from: Mr. Matté on February 24, 2011, 12:16:23 AM
Quote from: Michael in Philly on February 23, 2011, 02:31:00 PM
Just discovered US 202 in King of Prussia, Pa., is marked as 202 and 206....

All of 202 south of NY 59 is marked US 202/206. Another golden nugget from Google Maps along with US 527. :roll:

US 206 also overlaps with 202 from Simsbury, CT to Jaffrey, NH. This is turning into quite a preponderance of evidence that a longer US 206 really exists. :-/
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 26, 2011, 06:25:23 PM
They seem to have applied many things to the entire route rather than just a portion. For example all of US 64 is the Knightdale Bypass. Most likely they use something like OSM's relations (http://www.openstreetmap.org/browse/relation/421777) to store both numbers and names, and they suck worse than OSM at maintaining them properly.
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael in Philly on February 28, 2011, 11:32:51 AM
So I guess the moral of all this is that paper maps aren't obsolete yet.  Which works for me.  Unfortunately, if enough of the public aren't aware of this, map publishers may still, um, stop publishing maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: Rover_0 on February 28, 2011, 02:52:34 PM
US-9 Near Yuma, Arizona (http://maps.google.com/?ie=UTF8&ll=32.699308,-114.56646&spn=0.013669,0.027874&t=h&z=16")
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on February 28, 2011, 04:30:20 PM
I was looking around in Street View, and noticed that NY 38 north of Auburn is labeled as "State Saint Road" (http://maps.google.com/?ie=UTF8&ll=42.954348,-76.579889&spn=0,0.002642&t=h&z=19&layer=c&cbll=42.954344,-76.579888&panoid=Sr1QfdEdTCxKnDR_Q_Wkaw&cbp=12,349.95,,0,5).  It's actually State Street Road.  I'm guessing that Google converted the "St" in the abbreviation of State St. Rd. to "saint" instead of "street".
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael in Philly on February 28, 2011, 04:54:50 PM
Quote from: Michael on February 28, 2011, 04:30:20 PM
I was looking around in Street View, and noticed that NY 38 north of Auburn is labeled as "State Saint Road" (http://maps.google.com/?ie=UTF8&ll=42.954348,-76.579889&spn=0,0.002642&t=h&z=19&layer=c&cbll=42.954344,-76.579888&panoid=Sr1QfdEdTCxKnDR_Q_Wkaw&cbp=12,349.95,,0,5).  It's actually State Street Road.  I'm guessing that Google converted the "St" in the abbreviation of State St. Rd. to "saint" instead of "street".

[visits Google Maps with some trepidation]...
[comes back relieved]
At least they got Street Road and State Road, which intersect each other in suburban Philadelphia, right....
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on March 07, 2011, 11:24:26 AM
I was getting directions in Syracuse for a friend, and Google Maps wouldn't route me along Erie Blvd. over West St. Here's (http://maps.google.com/maps?f=d&source=s_d&saddr=Unknown+road&daddr=Erie+Blvd+W&hl=en&geocode=FUzkkAIdAuJ1-w%3BFczmkAIdGu11-w&mra=dme&mrsp=1&sz=17&sll=43.050435,-76.159093&sspn=0.006335,0.013937&ie=UTF8&t=h&z=17) a map link.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 07, 2011, 05:07:48 PM
It appears that bridge was closed for a while (until November 2010): http://www.syracuse.com/news/index.ssf/2010/11/erie_boulevard_west_bridge_ope.html
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on March 07, 2011, 08:34:00 PM
Quote from: NE2 on March 07, 2011, 05:07:48 PM
It appears that bridge was closed for a while (until November 2010): http://www.syracuse.com/news/index.ssf/2010/11/erie_boulevard_west_bridge_ope.html

And perhaps Google forgot all about that.
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on March 08, 2011, 12:17:07 AM
Quote from: NE2 on March 07, 2011, 05:07:48 PM
It appears that bridge was closed for a while (until November 2010): http://www.syracuse.com/news/index.ssf/2010/11/erie_boulevard_west_bridge_ope.html

I thought of that, but I never realized it was closed for 8 months.  Besides, I wouldn't think that Google Maps would have construction data in its base maps.  Street view shows the segment just fine.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfilpus on March 08, 2011, 09:04:51 AM
Quote from: Michael on March 08, 2011, 12:17:07 AM
Quote from: NE2 on March 07, 2011, 05:07:48 PM
It appears that bridge was closed for a while (until November 2010): http://www.syracuse.com/news/index.ssf/2010/11/erie_boulevard_west_bridge_ope.html

I thought of that, but I never realized it was closed for 8 months.  Besides, I wouldn't think that Google Maps would have construction data in its base maps.  Street view shows the segment just fine.
Google maps does include major construction closures in its maps. Notice that the street in question is gray, rather than yellow. When I-40 was closed through the Great Smokies from rock slides, you could't route that way.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 08, 2011, 01:55:35 PM
Sadly Google does put construction data in it's maps.  Often this means that the maps are wrong for years after when it would have been more correct to leave well enough alone.
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on March 10, 2011, 12:31:33 AM
^^^

I know.  Locally, the unfinished stubs of TN 840 are in there.

I went out Dickson way on Saturday to take the newly opened stretch of 840 for the first time.  Google maps still only has the stubs on each end.  That did make the GPS wig out a little less when I drove the stretch.  However, that stretch of road opened nearly five months ago!
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 10, 2011, 05:55:27 AM
Quote from: mightyace on March 10, 2011, 12:31:33 AM
^^^

I know.  Locally, the unfinished stubs of TN 840 are in there.

I went out Dickson way on Saturday to take the newly opened stretch of 840 for the first time.  Google maps still only has the stubs on each end.  That did make the GPS wig out a little less when I drove the stretch.  However, that stretch of road opened nearly five months ago!

Use OSM then. lol.  It's been in there almost since it was opened. ;)  But I do see Google's attempting to add it, but it looks horrible as of right now because they have a giant gap in it. :ded:
http://maps.google.com/?ie=UTF8&ll=35.918389,-87.156086&spn=0.052689,0.111494&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on March 10, 2011, 02:55:52 PM
Disconnected roads in Washington, D.C., which strangely enough are still routable:

http://maps.google.com/maps?hl=en&ie=UTF8&ll=38.892828,-77.038262&spn=0.003144,0.006845&z=18 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=38.892828,-77.038262&spn=0.003144,0.006845&z=18)
Title: Re: Incorrect highways marked on Google Maps
Post by: DeaconG on March 10, 2011, 05:56:43 PM
I thought the Pocahontas Parkway in Richmond was freeway grade...apparently Google doesn't think so...
Title: Re: Incorrect highways marked on Google Maps
Post by: DeaconG on March 10, 2011, 05:59:28 PM
And while I'm at it, the John Land Apopka Expressway is freeway grade-I rode on it three weeks ago-and IT'S not marked either!

At least they figured out that the Fort Bend Parkway in Houston is freeway grade-they finally marked it right...
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 10, 2011, 06:57:18 PM
Yeah, Google is pretty bad at not marking short freeways as such.

Not that OSM is any better when a local gets it in their mind that something isn't built well enough to be marked as a freeway and reverts attempts to correct it (see Seattle (http://www.openstreetmap.org/?lat=47.6009&lon=-122.3122&zoom=13&layers=M))...
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 10, 2011, 07:52:00 PM
Quote from: NE2 on March 10, 2011, 06:57:18 PM
Yeah, Google is pretty bad at not marking short freeways as such.

Oh, I know the feeling.  I've been having fights with them over Business I-376.  They finally now have it as an expressway, but they forgot to leave a small section in yellow for the short at-grade section.
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on March 11, 2011, 05:23:10 PM
I've given up all hope on getting them to do that right. I can name a handful of incorrectly shown freeways here in Hampton Roads alone (e.g., 164, Suffolk Bypass).
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on March 15, 2011, 03:45:30 PM
Quote from: rickmastfan67 on March 10, 2011, 05:55:27 AM
Quote from: mightyace on March 10, 2011, 12:31:33 AM
^^^

I know.  Locally, the unfinished stubs of TN 840 are in there.

I went out Dickson way on Saturday to take the newly opened stretch of 840 for the first time.  Google maps still only has the stubs on each end.  That did make the GPS wig out a little less when I drove the stretch.  However, that stretch of road opened nearly five months ago!

Use OSM then. lol.  It's been in there almost since it was opened. ;)  But I do see Google's attempting to add it, but it looks horrible as of right now because they have a giant gap in it. :ded:
http://maps.google.com/?ie=UTF8&ll=35.918389,-87.156086&spn=0.052689,0.111494&z=14

They've put more in since I took that ride to Dickson on the 6th but, as you say, it still has a gap!
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on March 15, 2011, 09:42:56 PM
Quote from: Revive 755 on January 25, 2011, 05:12:59 PM
I'm seeing a new I-136 in Nebraska, Missouri, and Illinois today:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=39.88445,-94.130859&spn=6.372267,21.09375&z=7 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=39.88445,-94.130859&spn=6.372267,21.09375&z=7)

Not completely, still named "U.S. 136" in Street View.

Got another one. This mountain road near Cuddebackville, NY becomes a freeway for a few bends:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=41.504592,-74.657936&spn=0.02404,0.05476&z=15 (http://maps.google.com/maps?hl=en&ie=UTF8&ll=41.504592,-74.657936&spn=0.02404,0.05476&z=15)
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on March 26, 2011, 06:31:48 PM
http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Green+River,+UT,+United+States&aq=0&sll=37.713159,-99.874649&sspn=0.240092,0.438766&ie=UTF8&hq=&hnear=Green+River,+Emery,+Utah,+United+States&ll=38.986767,-110.24025&spn=0.058976,0.109692&z=13 (http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Green+River,+UT,+United+States&aq=0&sll=37.713159,-99.874649&sspn=0.240092,0.438766&ie=UTF8&hq=&hnear=Green+River,+Emery,+Utah,+United+States&ll=38.986767,-110.24025&spn=0.058976,0.109692&z=13)
Here, US 6/191 is named 'State Route 191'.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 26, 2011, 06:52:04 PM
So? http://le.utah.gov/~code/TITLE72/htm/72_04_012500.htm
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on March 27, 2011, 05:27:02 AM
CO 789 is still marked with CO 13.
http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Rifle,+CO,+United+States&aq=0&sll=43.418889,-106.369801&sspn=0.055111,0.109692&doflg=ptm&ie=UTF8&hq=&hnear=Rifle,+Garfield,+Colorado,+United+States&ll=39.710356,-107.782745&spn=0.466951,0.877533&z=10 (http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Rifle,+CO,+United+States&aq=0&sll=43.418889,-106.369801&sspn=0.055111,0.109692&doflg=ptm&ie=UTF8&hq=&hnear=Rifle,+Garfield,+Colorado,+United+States&ll=39.710356,-107.782745&spn=0.466951,0.877533&z=10)
Title: Re: Incorrect highways marked on Google Maps
Post by: Ian on March 28, 2011, 07:33:45 PM
Random limited access road line branching off of MA 146 south of Worcester:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=42.165566,-71.691284&spn=0.071507,0.154324&t=h&z=13
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on March 31, 2011, 11:24:38 PM
Looks like Google fixed some of the problems here: US 527 through Central Jersey no longer exists, nor does the extremely long US 202/206 concurrency through Pennsylvania and Delaware. In addition, the random freeway just one post above is gone.

Unfortunately, I-136 is still listed in all its grade-unseparated glory.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on March 31, 2011, 11:37:18 PM
Quote from: PennDOTFan on March 28, 2011, 07:33:45 PM
Random limited access road line branching off of MA 146 south of Worcester:
http://maps.google.com/maps?hl=en&ie=UTF8&ll=42.165566,-71.691284&spn=0.071507,0.154324&t=h&z=13
Well, 146 ought to be a freeway, so they're still not perfect. They reconnected 138 to 79 in Fall River, though.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on April 07, 2011, 03:02:41 AM
Here, US 180 has been de-moted to AZ 180. (Well, there IS an AZ 180A)
http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Holbrook,+AZ,+United+States&aq=0&sll=-25.335448,135.745076&sspn=34.69083,56.162109&ie=UTF8&hq=&hnear=Holbrook,+Navajo,+Arizona,+United+States&ll=34.891563,-110.104637&spn=0.12447,0.350189&z=12 (http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Holbrook,+AZ,+United+States&aq=0&sll=-25.335448,135.745076&sspn=34.69083,56.162109&ie=UTF8&hq=&hnear=Holbrook,+Navajo,+Arizona,+United+States&ll=34.891563,-110.104637&spn=0.12447,0.350189&z=12)
In fact, I believe the WHOLE of US 180 has been demoted to a state route. And, also the ghost of US 666 still lurks in Eagar, AZ. Speak of the devil...
http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Eagar,+AZ,+United+States&aq=0&sll=34.091336,-109.092865&sspn=0.502679,1.400757&ie=UTF8&hq=&hnear=Eagar,+Apache,+Arizona,+United+States&ll=34.097733,-109.237061&spn=0.06283,0.109692&z=13 (http://maps.google.com.au/maps?f=q&source=s_q&hl=en&geocode=&q=Eagar,+AZ,+United+States&aq=0&sll=34.091336,-109.092865&sspn=0.502679,1.400757&ie=UTF8&hq=&hnear=Eagar,+Apache,+Arizona,+United+States&ll=34.097733,-109.237061&spn=0.06283,0.109692&z=13)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 07, 2011, 11:04:13 PM
US-641 just got extended by Google:
http://maps.google.com/maps?ie=UTF8&ll=37.694552,-87.87672&spn=0.049511,0.111494&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: Dr Frankenstein on April 08, 2011, 01:19:12 AM
http://maps.google.ca/?ll=45.369514,-73.567028&z=13

The A-30 section through St-Constant was finally added, 4 months after its scheduled opening and about as long after my bug report, HOWEVER:
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on April 08, 2011, 09:43:31 AM
In other news, MD 200 finally shows up, but check out the interchange with MD 97 in google maps!
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on April 08, 2011, 04:57:51 PM
I don't know whether this is new or I just haven't been paying attention.  Saturn Parkway (TN 396) is shown as a yellow road (surface/arterial) rather than a freeway.

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Spring+Hill,+TN&aq=1&sll=39.118225,-77.075787&sspn=0.011121,0.027466&ie=UTF8&hq=&hnear=Spring+Hill,+Maury,+Tennessee&ll=35.741079,-86.921597&spn=0.046537,0.109863&t=h&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on April 08, 2011, 06:20:58 PM
Quote from: deanej on April 08, 2011, 09:43:31 AM
In other news, MD 200 finally shows up, but check out the interchange with MD 97 in google maps!

Not only that, but most of the eastbound carriageway is missing!
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on April 09, 2011, 09:45:31 PM
Why is US 209 between PA 33 and I-80 near Stroudsburg, PA shown as a freeway when it has three at grade intersections on it?
Why is US 301 north of Fayetteville, NC shown as an arterial when it is a freeway?  Matter of fact it was I-95 until the Fayetteville Bypass was completed in 84 and was still then shown as an arterrial.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 09, 2011, 09:52:47 PM
Quote from: roadman65 on April 09, 2011, 09:45:31 PM
Matter of fact it was I-95 until the Fayetteville Bypass was completed in 84 and was still then shown as an arterrial.
Google Maps wasn't around in 1984...?
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on April 09, 2011, 09:57:41 PM
Quote from: NE2 on April 09, 2011, 09:52:47 PM
Quote from: roadman65 on April 09, 2011, 09:45:31 PM
Matter of fact it was I-95 until the Fayetteville Bypass was completed in 84 and was still then shown as an arterrial.
Google Maps wasn't around in 1984...?
Well other maps were and they were like Google.

Fixed quote. (https://www.aaroads.com/forum/index.php?topic=4000.0) - rmf67
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on April 18, 2011, 04:28:22 PM
I was looking up NY 598 in Syracuse (http://maps.google.com/maps?ie=UTF8&ll=43.067132,-76.109076&spn=0.032982,0.084543&z=14) and noticed that it's marked on Teall Ave when it should be marked on Midler Ave.
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on April 19, 2011, 12:54:20 PM
Quote from: mightyace on March 10, 2011, 12:31:33 AM
I know.  Locally, the unfinished stubs of TN 840 are in there.

I went out Dickson way on Saturday to take the newly opened stretch of 840 for the first time.  Google maps still only has the stubs on each end.  That did make the GPS wig out a little less when I drove the stretch.  However, that stretch of road opened nearly five months ago!

I went back on the road on Saturday to get some photos and noticed that Google maps has added that stretch of 840 to the maps.  Not surprisingly, the satellite/aerial maps still show it under construction with gaps.
Title: Re: Incorrect highways marked on Google Maps
Post by: Hot Rod Hootenanny on April 19, 2011, 04:21:13 PM
Quote from: mightyace on April 19, 2011, 12:54:20 PM
Quote from: mightyace on March 10, 2011, 12:31:33 AM
I know.  Locally, the unfinished stubs of TN 840 are in there.

I went out Dickson way on Saturday to take the newly opened stretch of 840 for the first time.  Google maps still only has the stubs on each end.  That did make the GPS wig out a little less when I drove the stretch.  However, that stretch of road opened nearly five months ago!

I went back on the road on Saturday to get some photos and noticed that Google maps has added that stretch of 840 to the maps.  Not surprisingly, the satellite/aerial maps still show it under construction with gaps.
If you're on google earth, you can see the date for when the satellite image was taken.
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on April 19, 2011, 06:19:30 PM
^^^

In this case that would only do me any good if Google Earth had newer imaging than Google Maps.  i.e. I want newer images on 840 not older.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 19, 2011, 06:30:25 PM
NAIP has 2010 imagery for Williamson County: http://datagateway.nrcs.usda.gov/GDGOrder.aspx
Title: Re: Incorrect highways marked on Google Maps
Post by: Duke87 on May 17, 2011, 07:57:05 PM
Apparently MTQ has found its way to Portland...
http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=45.530944,-122.657204&spn=0.02844,0.062742&z=14


(permanent screenshot) (http://img27.imageshack.us/img27/9784/googlemapsqc366portland.png)
Title: Re: Incorrect highways marked on Google Maps
Post by: Zmapper on May 17, 2011, 08:04:31 PM
Maybe Google wants America to become part of Quebec.  :-P
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on May 17, 2011, 08:37:54 PM
Quote from: Duke87 on May 17, 2011, 07:57:05 PM
Apparently MTQ has found its way to Portland...
http://maps.google.com/?ie=UTF8&hq=&hnear=New+York&ll=45.530944,-122.657204&spn=0.02844,0.062742&z=14


(permanent screenshot) (http://img27.imageshack.us/img27/9784/googlemapsqc366portland.png)

It also showed up in Nebreska.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zmapper on May 17, 2011, 09:10:54 PM
I think I found the problem.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ffarm3.static.flickr.com%2F2008%2F5732205088_44df41e1b4_b.jpg&hash=6d763c971ff27fbaad61fcdd5dc08b561d2bee2e)

Flickr: http://www.flickr.com/photos/52377790@N03/5732205088/sizes/l/in/photostream/

MOD NOTE: Can you please merge the posts in the Google Map Maker thread about Quebec Route 366 with this thread? Thank you in advance.
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on May 17, 2011, 10:24:04 PM
I didn't realize I was on Quebec Route 366 today.
Title: Re: Incorrect highways marked on Google Maps
Post by: ftballfan on May 17, 2011, 10:29:28 PM
Quebec Route 366 = US-30
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on May 17, 2011, 10:42:33 PM
That'd be the [actual] route I was on.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on May 22, 2011, 10:35:42 PM
I have seen somewhere that FL A1A was marked as FL 1A.
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on June 02, 2011, 06:47:43 PM
Ready to have your mind blown? Check I-84

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=mountain+home+id&aq=&sll=37.0625,-95.677068&sspn=35.957999,86.572266&ie=UTF8&hq=&hnear=Mountain+Home,+Elmore,+Idaho&ll=43.143082,-115.698738&spn=0.129511,0.338173&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 02, 2011, 07:09:07 PM
All I see is Quebec Route 366, which has already been mentioned here and elsewhere.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zmapper on June 02, 2011, 07:12:33 PM
What about the underwater subdivision on the south side of I-84/Quebec 366 and between N 10th and N 18th?
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on June 03, 2011, 12:37:54 AM
http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Jamestown,+NY&aq=0&sll=37.0625,-95.677068&sspn=36.642161,56.513672&ie=UTF8&hq=&hnear=Jamestown,+Chautauqua,+New+York&ll=42.051268,-79.184475&spn=0.016794,0.027595&z=15

What's this "US 940" you speak of, Google?

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Jamestown,+NY&aq=0&sll=37.0625,-95.677068&sspn=36.642161,56.513672&ie=UTF8&hq=&hnear=Jamestown,+Chautauqua,+New+York&ll=42.115511,-76.816063&spn=0.016777,0.027595&z=15

NY 14 isn't routed that way, Google!

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Ashford,+NY&aq=0&sll=42.301246,-78.655415&sspn=0.033455,0.055189&ie=UTF8&hq=&hnear=Ashford,+New+York&ll=42.427828,-78.632412&spn=0.033388,0.055189&z=14

Way to sign Cattaraugus CR 86 as a state route, Google!

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Ashford,+NY&aq=0&sll=42.301246,-78.655415&sspn=0.033455,0.055189&ie=UTF8&hq=&hnear=Ashford,+New+York&ll=42.006958,-76.57093&spn=0.134443,0.220757&z=12

I-86 isn't signed here yet, Google!
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on June 03, 2011, 06:10:57 AM
Quote from: WNYroadgeek on June 03, 2011, 12:37:54 AMhttp://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Ashford,+NY&aq=0&sll=42.301246,-78.655415&sspn=0.033455,0.055189&ie=UTF8&hq=&hnear=Ashford,+New+York&ll=42.006958,-76.57093&spn=0.134443,0.220757&z=12

I-86 isn't signed here yet, Google!
Isn't it signed as Future I-86? In which case that's not a huge problem, given that's still red and blue shields.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on June 11, 2011, 11:25:06 AM
Not G. Maps, but G. Earth. On I-79 and some on-ramps just south of the Ohio River, a "wall of spikes" line the roads:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg861.imageshack.us%2Fimg861%2F8492%2Fi79error1.jpg&hash=10e7bc92f934926e2bb23dee4f541d6ec4a2db2a)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg90.imageshack.us%2Fimg90%2F485%2Fi79error2.jpg&hash=4ef7fa46eea19117f50264b995174ffde1e3740e)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on June 11, 2011, 02:05:15 PM
Terrain height and roads in the imagery don't mix.
Title: Re: Incorrect highways marked on Google Maps
Post by: TwinsMetsFan on June 13, 2011, 10:45:07 PM
Quote from: WNYroadgeek on June 03, 2011, 12:37:54 AM
What's this "US 940" you speak of, Google?
Google also marks that segment as "County Road 940", but I have no clue why that caused US route markers to appear. As for CR 940, that part of US 62 was internally designated as CR 940 when it was maintained by Chautauqua County during the 1970s, but the number hasn't existed since 1980 when ownership of this piece of US 62 was transferred to the state. I can't say I'm surprised that Google's data still has it, considering it has many references to routes that were eliminated in or around 1980 (such as NY 239, NY 358, and until recently NY 422 and NY 288).
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on June 15, 2011, 09:42:07 AM
Quote from: Mr. Matté on June 11, 2011, 11:25:06 AM
Not G. Maps, but G. Earth. On I-79 and some on-ramps just south of the Ohio River, a "wall of spikes" line the roads:
The PA-51 overpass sunk as well. Me> :pan: <Google

Quote from: ftballfan on May 17, 2011, 10:29:28 PM
Quebec Route 366 = US-30
I-136 was close, but this takes the cake.
Title: Re: Incorrect highways marked on Google Maps
Post by: Rover_0 on June 15, 2011, 05:40:35 PM
Well, we also have US-131 in Utah, near Strawberry Reservior:

http://maps.google.com/?ie=UTF8&ll=40.182414,-111.176834&spn=0.089443,0.154324&z=13 (http://maps.google.com/?ie=UTF8&ll=40.182414,-111.176834&spn=0.089443,0.154324&z=13)
Title: Re: Incorrect highways marked on Google Maps
Post by: TwinsMetsFan on June 16, 2011, 07:41:04 PM
Apologies if this one's been mentioned already, but I found a strange error during some down time earlier. In Remsen, New York, there's a road (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=remsen,+ny&aq=&sll=37.0625,-95.677068&sspn=48.77566,114.169922&ie=UTF8&hq=&hnear=Remsen,+Oneida,+New+York&ll=43.326348,-75.185323&spn=0.01102,0.027874&z=16) marked as NY 28B - a designation that hasn't existed in almost 50 years. As if that wasn't enough, the road in question doesn't exist (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=remsen,+ny&aq=&sll=37.0625,-95.677068&sspn=48.77566,114.169922&ie=UTF8&hq=&hnear=Remsen,+Oneida,+New+York&t=h&ll=43.32581,-75.183762&spn=0.002755,0.006968&z=18).
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on June 18, 2011, 12:27:56 AM
And I love how it intersects "Newyork 920V"  :-/
Title: Re: Incorrect highways marked on Google Maps
Post by: Icodec on June 21, 2011, 04:04:13 PM
US-136 is marked as Interstate 136 and colored yellow. This really gets on my nerves. I realize that it is an "interstate," but why can't just mark it with a US-route shield? Ughhhh.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on June 21, 2011, 05:29:39 PM
The I-136 thing has been fixed for a few weeks. Did you try clearing your browser's cache?

The QC 366/US 30 problem still exists.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on June 27, 2011, 01:24:45 PM
Quote from: mightyace on April 19, 2011, 06:19:30 PM
In this case that would only do me any good if Google Earth had newer imaging than Google Maps.  i.e. I want newer images on 840 not older.

Often it does.  Google Maps' default "satellite" layer consists of what Google considers to be the "best" imagery available, which isn't always the newest.  This can happen if newer imagery is of relatively low resolution, or sometimes for no apparent reason at all.  Until 2008 or 2009, Google's default imagery for Columbus was some unattributed source from 2004, even though 1ft OSIP 2007 imagery was available from 2007.  By the time they incorporated OSIP into the default imagery layer, the 2009 USDA Farm Service Agency (NAIP?) imagery had become available in Google Earth.
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on June 29, 2011, 07:31:41 PM
Quote from: Mr. Matté on June 21, 2011, 05:29:39 PMThe QC 366/US 30 problem still exists.

I just got an e-mail today from someone who used Google for directions, and wondered why it said "Quebec Route."  They thought it might be a misinterpretation of quadrant route.  It has even fooled my local paper, who gave the address of a restaurant in Ligonier as "2727 Quebec Route 366 (http://calendar.triblive.com/ligonier-pa/venues/show/5745586-cocomos-down-under)."

It must be taking them a long time to get the fixes online, because while I was told my elimination of PA 66 between New Stanton and Greensburg was approved, it still shows it multiplexed with US 119.
Title: Re: Incorrect highways marked on Google Maps
Post by: rawmustard on June 30, 2011, 11:54:11 AM
Quote from: PAHighways on June 29, 2011, 07:31:41 PM
I just got an e-mail today from someone who used Google for directions, and wondered why it said "Quebec Route."
I wonder if it's the same person who reported on this story (http://philadelphia.cbslocal.com/2011/06/30/route-30-incorrectly-labeled-quebec-route-366-by-google-maps/). :hmmm:
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on June 30, 2011, 12:31:38 PM
Quote from: rawmustard on June 30, 2011, 11:54:11 AM
Quote from: PAHighways on June 29, 2011, 07:31:41 PM
I just got an e-mail today from someone who used Google for directions, and wondered why it said "Quebec Route."
I wonder if it's the same person who reported on this story (http://philadelphia.cbslocal.com/2011/06/30/route-30-incorrectly-labeled-quebec-route-366-by-google-maps/). :hmmm:

One in the same.

During the interview, he asked me if Google Map Maker has a system of checks and balances, so I relayed my experiences as well as others mentioned in this thread.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 30, 2011, 01:05:42 PM
"I believe there was one incident where someone had marked the entire United States as a military reserve. That's one of the dangers with having too many cooks in the kitchen."

This was on OpenStreetMap, and was reverted in about two hours.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 30, 2011, 01:14:44 PM
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi55.tinypic.com%2Fj14vo9.png&hash=dc128e1867934d6b4b6005f27603e4ed5198ab6a)
:sombrero:
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on June 30, 2011, 02:01:21 PM
Quote from: NE2 on June 30, 2011, 01:05:42 PM
too many cocks in the kitchen.

that sums up the internet in general.
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on June 30, 2011, 02:20:13 PM
Quote from: NE2 on June 30, 2011, 01:05:42 PM
"I believe there was one incident where someone had marked the entire United States as a military reserve. That's one of the dangers with having too many cooks in the kitchen."

This was on OpenStreetMap, and was reverted in about two hours.

I mentioned the site in our conversation, to show that there are other similar sites with similar issues.  I guess he got confused and thought I was speaking of Google Maps as well.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 01, 2011, 07:21:47 AM
Quote from: PAHighways on June 30, 2011, 02:20:13 PM
Quote from: NE2 on June 30, 2011, 01:05:42 PM
"I believe there was one incident where someone had marked the entire United States as a military reserve. That's one of the dangers with having too many cooks in the kitchen.”

This was on OpenStreetMap, and was reverted in about two hours.

I mentioned the site in our conversation, to show that there are other similar sites with similar issues.  I guess he got confused and thought I was speaking of Google Maps as well.

You should let him know that Google's reviewers don't know what a freeway is. lol. (in reference to I-381 in VA)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 01, 2011, 09:54:17 AM
Quote from: rickmastfan67 on July 01, 2011, 07:21:47 AM
You should let him know that Google's reviewers don't know what a freeway is. lol. (in reference to I-381 in VA)
And OSM's editors do? (Alaskan Way Viaduct)
Title: Re: Incorrect highways marked on Google Maps
Post by: PAHighways on July 01, 2011, 12:02:17 PM
Quote from: rickmastfan67 on July 01, 2011, 07:21:47 AMYou should let him know that Google's reviewers don't know what a freeway is. lol. (in reference to I-381 in VA)

I mentioned that as well.
Title: Re: Incorrect highways marked on Google Maps
Post by: texaskdog on July 01, 2011, 02:02:36 PM
I email them all the time about how it is physically impossible to go the routes they suggest and they email me back thanking me and telling me I'm right, and then they don't change it.
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on July 01, 2011, 05:30:21 PM
I think I've basically given up on Google Maps. Gonna be using OSM as much as possible from now on...
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 01, 2011, 10:21:05 PM
All I can say here is "WTF?!?!?!?"

http://maps.google.com/maps?ll=38.48026,-81.924523&spn=0.006417,0.013894&z=17
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 01, 2011, 10:38:03 PM
Somethiing got deleted; happens in OSM too. And US 35 certainly isn't a freeway north of there.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 01, 2011, 10:40:00 PM
Another wierd thing.  While in the "main" map of Google, they show the TN/VA border in the correct place.  Yet in Map Maker, they show it around Broad Street in Bristol.

Normal: http://maps.google.com/?ie=UTF8&ll=36.595495,-82.182541&spn=0.012869,0.027874&z=16
MapMaker: http://www.google.com/mapmaker?ll=36.595495,-82.182541&spn=0.012869,0.027874&t=m&z=16&source=gm_el

Quote from: NE2 on July 01, 2011, 10:38:03 PM
Somethiing got deleted; happens in OSM too. And US 35 certainly isn't a freeway north of there.

Did you notice the wrong dirrection highway as well?
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on July 04, 2011, 03:35:53 PM
And the solution to "Quebec Route 366" was to delete the US-30 shields, so now there's text for "US-30" and "Quebec Route 366" although now it looks like you have to zoom in a bit further to see Route 366

Ugh
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on July 04, 2011, 06:12:04 PM
There's a district in West London called "White City", but it appears on google maps as "White Stadt", which suggests they used the German wikipedia co-ordinates and ignored the English ones.

They had some French and Welsh names appearing around London, but sorted those (no map maker in the UK yet).
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on July 11, 2011, 12:21:26 PM
If you thought Quebec Route 366 was bad...

http://www.nj.com/business/index.ssf/2011/07/google_map_brings_recreation-s.html
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on July 11, 2011, 02:00:20 PM
Quote from: Mr. Matté on July 11, 2011, 12:21:26 PM
If you thought Quebec Route 366 was bad...

http://www.nj.com/business/index.ssf/2011/07/google_map_brings_recreation-s.html

It sounds to me like Google gives directions the way it does because this shared driveway appears on Google Maps and is the closest road to the lake or the geographic center of the lake.  If Google simply removes the driveway from its map data (I don't think it should be there in the first place if it's a driveway for a few private residences) then the problem should go away.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on July 12, 2011, 12:35:52 PM
This is Google we're talking about.  I wouldn't be surprised if the only way this eventually gets resolved is if she sues them.  It's not like Google cares about their data.  She could try using mapmaker first, though.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on July 12, 2011, 03:31:23 PM
Quote from: deanej on July 12, 2011, 12:35:52 PM
...She could try using mapmaker first, though.

*Archie Bunker laugh*

I tried and someone else tried deleting the roads, and surprise surprise, edits denied by people with bad grammar/spelling.
Title: Re: Incorrect highways marked on Google Maps
Post by: ftballfan on July 13, 2011, 08:34:19 AM
I just found this in Michigan (M-394): http://maps.google.com/maps?hl=en&ll=41.867771,-85.877037&spn=0.111471,0.449066&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on July 18, 2011, 05:17:21 PM
This isn't a road, but this is just too funny to pass up:

http://maps.google.com/?ll=42.424803,-71.793766&spn=0.009757,0.027466&z=16 (http://maps.google.com/?ll=42.424803,-71.793766&spn=0.009757,0.027466&z=16)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on July 19, 2011, 12:11:57 PM
At this point I'm wondering if we should close this thread and start a "Correct highways marked on Google Maps" thread.  :)
Title: Re: Incorrect highways marked on Google Maps
Post by: 1995hoo on July 19, 2011, 12:41:50 PM
Quebec Route 366 appears to be fixed.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 12, 2011, 12:07:03 AM
US-119 is now shown as a "Freeway" in West Virigina...

http://maps.google.com/?ie=UTF8&ll=37.927951,-82.09053&spn=0.407834,0.891953&z=11
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on August 12, 2011, 12:28:16 AM
As are Corridor D (SR 32) across Ohio, Corridor H, way too much of US 23 north of Columbus, the San Jose area expressways, the entire southern approach to the CBBT, NJ 17, just to name a few... I was hoping I-180 Wyoming would be marked as a freeway, but no dice :)
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on August 12, 2011, 12:29:20 AM
It seems that a lot of expressways are being shown as freeways now.  Sometimes, only one direction of the roadway has been upgraded, which smacks of MapMaker mischief.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 26, 2011, 02:50:49 AM
Quote from: Scott5114 on February 06, 2010, 09:44:48 PM
Trying to get from Tulsa to Independence, KS? Better take US-3300 (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=independence+KS&sll=37.0625,-95.677068&sspn=41.767874,93.076172&ie=UTF8&hq=&hnear=Independence,+Montgomery,+Kansas&ll=37.187126,-95.774002&spn=0.041164,0.090895&z=14).

ROTFL, this one is still posted in Google Maps. hahahahaha.
Title: Re: Incorrect highways marked on Google Maps
Post by: jdb1234 on September 01, 2011, 04:50:30 AM
Apparently AL 42 is now multiplexed with US 31 in Montgomery:

http://www.google.com/maps?hl=en&ll=32.318981,-86.343141&spn=0.018532,0.027122&z=15&vpsrc=6 (http://www.google.com/maps?hl=en&ll=32.318981,-86.343141&spn=0.018532,0.027122&z=15&vpsrc=6)
Title: Re: Incorrect highways marked on Google Maps
Post by: texaskdog on September 01, 2011, 08:28:05 AM
Still funny when they email you and tell you you are right about a correction and that they will change it soon, and it never gets changed.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on September 01, 2011, 03:24:59 PM
Quote from: texaskdog on September 01, 2011, 08:28:05 AM
Still funny when they email you and tell you you are right about a correction and that they will change it soon, and it never gets changed.

It is funny sometimes, but it's also annoying other times.  For one, they still can't get the I-10/I-95 interchange in Jacksonville correct.  Then still need to fix NB I-95 at that interchange....
http://maps.google.com/?ie=UTF8&ll=30.321665,-81.681762&spn=0.006964,0.013937&z=17&vpsrc=6
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on September 02, 2011, 10:30:36 AM
I've pretty much given up on Google at this point.  There's no way it will ever be accurate.

They should have just stuck with Navteq.  When they switched to TeleAtlas, that's when all the problems began.
Title: Re: Incorrect highways marked on Google Maps
Post by: Brandon on September 05, 2011, 11:00:57 PM
And the directions for Google Maps are getting worse, IMHO.  Google Maps failed to recognize a section of I-94 near Albion, MI, instead sending the user off onto frontage roads and other roads for about 10 miles.
Title: Re: Incorrect highways marked on Google Maps
Post by: jdb1234 on September 15, 2011, 09:58:17 PM
Apparently US 20 now has a long multiplex with US 26.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on September 16, 2011, 05:00:19 AM
Outside of Idaho?

OR 224 is marked as a freeway between OR 99E and OR 213.
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael in Philly on September 16, 2011, 10:30:12 AM
Quote from: english si on July 04, 2011, 06:12:04 PM
There's a district in West London called "White City", but it appears on google maps as "White Stadt", which suggests they used the German wikipedia co-ordinates and ignored the English ones.

They had some French and Welsh names appearing around London, but sorted those (no map maker in the UK yet).

Another European/linguistic example:

They seem to have largely fixed it, but for a long time street names, landmarks and so on in Brussels appeared in Dutch only.  (For those who don't know the Belgian situation, roughly half the country has Dutch as its official language, the other half French, and a bit in the east German...  linguistic politics is highly sensitive - one example that the rest of Europe finds baffling and annoying is the treatment of place names on: in a Dutch-speaking area, for example, a non-Dutch-speaking city that has a Dutch name different from its name in its own language needs to be signed in Dutch only, so people navigating through Belgium by city names need to know two names for lots of places...  Anyhow, Brussels, the capital, is officially bilingual but predominantly French-speaking.  If I were in charge of Google maps, I'd label everything in Brussels in both languages, but most maps for tourists show street names and such only in French; using only the Dutch names is not very helpful.)
Title: Re: Incorrect highways marked on Google Maps
Post by: OCGuy81 on September 16, 2011, 10:36:25 AM
Interesting little note on Google Maps.

If you zoom in on Disneyland, specifically Disney's California Adventure, the trail that encircles the park actually shows up on Google Maps as CA-49.  It's funny, because there ARE CA-49 novelty shields as you walk the park, and I guess someone at Google took it literally.

They also show CA-66 where "Cars" Land is under construction.

I'm unsure how to post Google Map images, but it's worth checking out if you're interested in Google errors.
Title: Re: Incorrect highways marked on Google Maps
Post by: 1995hoo on September 16, 2011, 10:51:51 AM
Quote from: OCGuy81 on September 16, 2011, 10:36:25 AM
....

I'm unsure how to post Google Map images, but it's worth checking out if you're interested in Google errors.

Zoom in on where you want, then click the little chain-link icon above and to the right of the map window. It lets you copy and paste a link. If you want to post an actual image, you'd have to take a screenshot, save it as an image, then upload that image to somewhere. It's usually more trouble than it's worth unless you want to compare an outdated Google Street View image (which may change if they update it) to a current photo. But if you want to do it, on a PC you hit <Shift>-<PrtScr> to take the screenshot, then load a picture program (MS Paint works fine), cut out the area you want and copy it into a new image, save that, then upload the resulting file to a photo-sharing site like Photobucket, then copy and paste the URL for the image (Photobucket will give you a link that already contains the "IMG" tags needed on this forum).
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on September 18, 2011, 12:05:22 AM
Google just recently broke the Liberty Bridge going both dirrections here in Pittsburgh..... :pan:

http://g.co/maps/rgvsm
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on September 23, 2011, 07:21:27 PM
...while Google thinks all but one of the ramps at the I-94/Telegraph Road (U.S. 24) interchange in Taylor, MI is under construction:

http://g.co/maps/5868p

Try making a route that uses one of those ramps and the directions tell you to use another exit nearby. For example, if you try to route from I-94 east to Telegraph south, you would have to get off at Pelham Road (exit 204), then backtrack on Van Born Road!
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on October 03, 2011, 12:07:24 PM
Quote from: jdb1234 on September 15, 2011, 09:58:17 PM
Apparently US 20 now has a long multiplex with US 26.

I was going to post about this one.  It looks like the whole length of US 20 is also US 26.

On a side note, why does US 20 go 70 miles north and back south instead of staying on it's duplex US 26 in western Wyoming?
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on October 07, 2011, 06:18:38 AM
I-381 in VA is now back to being a "National Highway" again instead of a Freeway......
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on October 21, 2011, 04:33:25 AM
US-50 has now been posted in Louisville, KY...
http://g.co/maps/hr3sk
Title: Re: Incorrect highways marked on Google Maps
Post by: TheStranger on October 26, 2011, 02:55:10 PM
Why is US 29 in Greensboro continually marked as a conventional street on Google Maps (not even the odd expressway marking of half-conventional road/half-freeway that Google has used lately) when it is clearly a freeway?  Even some of the overpasses are mistakenly shown as intersections.



Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on October 26, 2011, 03:47:07 PM
Quote from: TheStranger on October 26, 2011, 02:55:10 PM
Why is US 29 in Greensboro continually marked as a conventional street on Google Maps (not even the odd expressway marking of half-conventional road/half-freeway that Google has used lately) when it is clearly a freeway?  Even some of the overpasses are mistakenly shown as intersections.


These are the same people that think Interstate 381 is a surface road. Take away the cartographer from the equation and that is what you get.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on November 02, 2011, 09:17:18 PM
NJ 124 in Springfield, NJ is marked NJ 82 at its intersection with Mountain Avenue.  NJ 82 ends 1/2 mile east of that intersection.
Title: Re: Incorrect highways marked on Google Maps
Post by: DeaconG on November 04, 2011, 01:31:20 AM
They finally posted the Pennyrile Parkway extension to I-24...
Title: Re: Incorrect highways marked on Google Maps
Post by: Jim on November 04, 2011, 02:56:57 PM
I've gotten a flurry of responses to errors I reported months ago, all in the last couple days..  And all were fixed.

Title: Re: Incorrect highways marked on Google Maps
Post by: pianocello on November 04, 2011, 04:11:18 PM
Evidently the RIRO intersections with neighborhood streets are close enough to interchanges to call the Kingery Hwy (IL-83) in the western suburbs a freeway.
Title: Re: Incorrect highways marked on Google Maps
Post by: Brandon on November 04, 2011, 10:20:42 PM
Quote from: pianocello on November 04, 2011, 04:11:18 PM
Evidently the RIRO intersections with neighborhood streets are close enough to interchanges to call the Kingery Hwy (IL-83) in the western suburbs a freeway.

Parts of it are a freeway.  Between 63rd St and 22nd St, it is a freeway with a few RIROs in addition.  It also becomes freeway between 16th St and the WalMart entrance.

For that matter, Roosevelt Rd (IL-38) is a freeway from just west of IL-83 to I-294.
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on November 16, 2011, 06:50:11 PM
Apparently US-62 and US-180 now have an even longer concurrency- from the Texas Panhandle all the way to the Ohio/Pennsylvania line..

http://g.co/maps/he796
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on November 22, 2011, 03:08:10 PM
What the heck?  US-30 is no longer signed as a Québec autoroute for its entirety?  Such a shame!

I can't remember where right now, but I've seen Google try to fit a whole highway NAME inside a route shield before, I think somewhere in México (for example, trying to fit "Villahermosa - Frontera") inside a little route marker.

It's nice to see that Guatemala City now has more than just surface streets.  For the longest time, there were no yellow or orange roads, just white.

Wow, Google seems to have corrected all the goofs I can think of off the top of my head.  Even some new ones I thought popped up ended up being correct–more correct than it used to be, even.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 22, 2011, 04:40:41 PM
Orange doesn't mean freeway in Latin America.  Don't know what does.  It's very confusing.
Title: Re: Incorrect highways marked on Google Maps
Post by: SSOWorld on November 27, 2011, 11:37:15 AM
http://maps.google.com/?ll=45.130227,-89.123497&spn=0.18384,0.528374&hnear=Fox+Ridge+Rd,+Platteville,+Grant,+Wisconsin+53818&t=h&z=12&vpsrc=6

In this link, WIS 64 is also labeled as 5 and a 1700 and 11500 are also shown.  so funny since these are actually a street name (5th ave) or address grid numbers :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on November 27, 2011, 09:13:49 PM
Not really marked, per se, but it's CHEMUNG County, Google, not Chautauqua!: http://maps.google.com/maps?saddr=I-86+W&daddr=Exit+52A&hl=en&ll=42.161272,-76.835922&spn=0.004589,0.006899&sll=42.161884,-76.836469&sspn=0.004589,0.006899&geocode=FZtPgwId951r-w%3BFfJTgwIdwZRr-w&vpsrc=6&mra=dme&mrsp=1&sz=17&t=m&z=17
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on December 06, 2011, 09:33:00 AM
It's not a highway, but apparently SeaTac airport is now "Aeroport internacional de Seattle-Tacoma" complete with an accent on the e. What is it with Google messing up languages lately?
Title: Re: Incorrect highways marked on Google Maps
Post by: stormwatch7721 on December 07, 2011, 09:20:25 PM
Google Maps has U.S. Route 62 paired with U.S. Route !80 in Ohio.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 07, 2011, 11:22:49 PM
Quote from: stormwatch7721 on December 07, 2011, 09:20:25 PM
Google Maps has U.S. Route 62 paired with U.S. Route !80 in Ohio.

Quote from: corco on November 16, 2011, 06:50:11 PM
Apparently US-62 and US-180 now have an even longer concurrency- from the Texas Panhandle all the way to the Ohio/Pennsylvania line..

http://g.co/maps/he796
Title: Re: Incorrect highways marked on Google Maps
Post by: stormwatch7721 on December 07, 2011, 11:38:36 PM
Oh I didn't see that. My bad. Sorry for going Off-Topic.
Title: Re: Incorrect highways marked on Google Maps
Post by: rawmustard on December 08, 2011, 10:22:12 AM
I guess with the updated shield images, M-37 became US-37.  :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on December 08, 2011, 07:19:00 PM
Quote from: rawmustard on December 08, 2011, 10:22:12 AM
I guess with the updated shield images, M-37 became US-37.  :-D

I'd have thought that as they were updating the shield images, it would've been a good opportunity to finally display bannered routes properly.  Google apparently disagreed.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 08, 2011, 08:26:20 PM
Quote from: Eth on December 08, 2011, 07:19:00 PM
Quote from: rawmustard on December 08, 2011, 10:22:12 AM
I guess with the updated shield images, M-37 became US-37.  :-D

I'd have thought that as they were updating the shield images, it would've been a good opportunity to finally display bannered routes properly.  Google apparently disagreed.

Yeah, and they still show Business Interstates as normal Interstates...
http://g.co/maps/9y54p
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on December 08, 2011, 09:24:20 PM
Another highway that has semi-phantom status is I-65 between Peytonsville Rd. (TN-248) and TN-96.  It shows up fine on the map but Google refuses to route you on that stretch.

Now, that stretch is under construction to widen it from 4 lanes to 8.  So, maybe some yahoo at Google though it was closed!

Also, where future the TN 840 interchange with Carters Creek Pike (TN-246) will be, the new alignment of 246 through the interchange is shown, however, it doesn't quite connect at the north end.  Also, the old alignment is still shown even though parts of it are under tons of dirt!

http://maps.google.com/?ll=35.81449,-86.98245&spn=0.011554,0.021136&t=h&z=16&vpsrc=6
Title: Re: Incorrect highways marked on Google Maps
Post by: ftballfan on December 11, 2011, 02:17:38 PM
Quote from: rawmustard on December 08, 2011, 10:22:12 AM
I guess with the updated shield images, M-37 became US-37.  :-D
It would, however, fit in the grid to some extent.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 11, 2011, 05:17:20 PM
Quote from: mightyace on December 08, 2011, 09:24:20 PM
So, maybe some yahoo at Google though it was closed!

Sorry, this made me giggle. :)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 11, 2011, 05:40:58 PM
And in their office they have the machine that goes bing.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on December 13, 2011, 08:19:20 PM
Yes, it cost over three-quarters of a million pounds!
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 13, 2011, 10:48:23 PM
Well, this isn't totally about highways, but I didn't know the Pentagon was recently turned into a shopping mall! :spin:

http://g.co/maps/qebpv

Look at all the businesses that seem to have stores in the Pentagon! :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 13, 2011, 11:26:26 PM
Quote from: rickmastfan67 on December 13, 2011, 10:48:23 PM
Look at all the businesses that seem to have stores in the Pentagon! :pan:
I can't confirm all of those places, but at least some are correct: http://pentagon.osd.mil/concessions.html
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 14, 2011, 09:11:06 PM
Quote from: NE2 on December 13, 2011, 11:26:26 PM
Quote from: rickmastfan67 on December 13, 2011, 10:48:23 PM
Look at all the businesses that seem to have stores in the Pentagon! :pan:
I can't confirm all of those places, but at least some are correct: http://pentagon.osd.mil/concessions.html

Hmmm, you learn something new every day!
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 15, 2011, 05:36:53 PM
Florida's Turnpike is completely missing at low zooms. Must be overreliance on networks (Interstate/US).
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 18, 2011, 01:25:57 AM
Google's extended I-290 in IL above I-90 along IL-53.
http://g.co/maps/3qgus
Title: Re: Incorrect highways marked on Google Maps
Post by: KEVIN_224 on December 18, 2011, 12:43:53 PM
On a semi-related note: The software which WVIT-TV (NBC) channel 30 of New Britain, CT (Hartford/New Haven market) uses is funny. If you zoom their weather radar enough, Connecticut Route 11 between its start in Colchester southward to Salem, CT will show up as both state route 11 and Interstate 11! Weird! :D
Title: Re: Incorrect highways marked on Google Maps
Post by: Revive 755 on December 26, 2011, 10:51:21 PM
Google's having problems with mixing MO 364 and MO 94 tonight:
http://maps.google.com/maps?ll=38.88502,-90.244617&spn=0.112911,0.264187&t=m&z=13&vpsrc=6 (http://maps.google.com/maps?ll=38.88502,-90.244617&spn=0.112911,0.264187&t=m&z=13&vpsrc=6)
http://maps.google.com/maps?ll=38.600774,-91.917114&spn=0.453443,1.056747&t=m&z=11&vpsrc=6 (http://maps.google.com/maps?ll=38.600774,-91.917114&spn=0.453443,1.056747&t=m&z=11&vpsrc=6)
Title: Re: Incorrect highways marked on Google Maps
Post by: DeaconG on December 27, 2011, 03:42:32 AM
Quote from: NE2 on December 15, 2011, 05:36:53 PM
Florida's Turnpike is completely missing at low zooms. Must be overreliance on networks (Interstate/US).

So is the Suncoast Parkway-Veterans shows up, though...
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 30, 2011, 03:53:50 AM
Here's a funny one.  See if you can figure out what's wrong here. lol. ;)
http://g.co/maps/4sq9r
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on December 30, 2011, 04:42:54 AM
I shouldn't find that as amusing as I do.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 30, 2011, 05:20:13 PM
Reminds me of TIGER's conversion of County Road into Cord or Creek.
Title: Re: Incorrect highways marked on Google Maps
Post by: Stephane Dumas on January 04, 2012, 10:53:38 AM
Since when US-37 is commissioned in Northern Michigan? ;)
http://maps.google.com/?ll=44.584599,-85.503159&spn=0.379004,0.617294&t=m&z=11&vpsrc=6
Title: Re: Incorrect highways marked on Google Maps
Post by: Ian on January 04, 2012, 09:01:35 PM
Apparently there is now an MD 7J in White Marsh, MD...
http://maps.google.com/maps?hl=en&ll=39.371995,-76.430511&spn=0.155261,0.308647&t=h&z=12&vpsrc=6
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on January 04, 2012, 09:46:35 PM
According to Wikipedia -- which I'll trust in this instance since a) it's cited, and b) it jives with what little I know about Maryland's system -- 7J does exist as an unsigned reference route type deal, although Google is slightly off on it's location.  It's the road to the ramp highlighted here.
http://maps.google.com/maps?saddr=Unknown+road&daddr=Unknown+road&hl=en&sll=39.376092,-76.436262&sspn=0.008841,0.021136&geocode=FcrQWAId_plx-w%3BFcbKWAIdPqBx-w&vpsrc=0&mra=me&mrsp=1,0&sz=16&t=h&z=16
Title: Re: Incorrect highways marked on Google Maps
Post by: Ian on January 05, 2012, 05:23:32 PM
Quote from: Kacie Jane on January 04, 2012, 09:46:35 PM
According to Wikipedia -- which I'll trust in this instance since a) it's cited, and b) it jives with what little I know about Maryland's system -- 7J does exist as an unsigned reference route type deal, although Google is slightly off on it's location.  It's the road to the ramp highlighted here.
http://maps.google.com/maps?saddr=Unknown+road&daddr=Unknown+road&hl=en&sll=39.376092,-76.436262&sspn=0.008841,0.021136&geocode=FcrQWAId_plx-w%3BFcbKWAIdPqBx-w&vpsrc=0&mra=me&mrsp=1,0&sz=16&t=h&z=16

Huh. Now this I did not know. Thanks for that piece of info!
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on January 10, 2012, 08:53:02 AM
Here's something crazy.  Google thinks that the Elevated Toll Lanes of I-95 in Miami are the mainline lanes at Exit #12.... :banghead:

http://g.co/maps/u6pk4
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on January 17, 2012, 02:49:01 PM
Apparently there is a Business I-35E in Pearsall, Texas–but, to be fair, I-35E is only 266 miles away.   :eyebrow:
http://maps.google.com/maps?hl=en&ll=28.898189,-99.081917&spn=0.110911,0.153637&t=p&z=13&vpsrc=6 (http://maps.google.com/maps?hl=en&ll=28.898189,-99.081917&spn=0.110911,0.153637&t=p&z=13&vpsrc=6)
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on January 17, 2012, 02:51:33 PM
And then there's Interstate 35C Business in Cotulla, just down the road....  :crazy:
http://maps.google.com/maps?hl=en&ll=28.438242,-99.235682&spn=0.027699,0.038409&t=p&z=15&vpsrc=6 (http://maps.google.com/maps?hl=en&ll=28.438242,-99.235682&spn=0.027699,0.038409&t=p&z=15&vpsrc=6)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 17, 2012, 03:39:37 PM
That's TXDOT's method of identifying their business routes. Here's 35-H (and SH 46-C):
(//www.aaroads.com/shields/img/TX/TX19790351i1.jpg) (//www.aaroads.com/shields/show.php?image=TX19790351)
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on January 17, 2012, 03:46:47 PM
Quote from: NE2 on January 17, 2012, 03:39:37 PM
That's TXDOT's method of identifying their business routes. Here's 35-H (and SH 46-C):

does the general motoring public ever pay attention to the business route letter?  I have not ever heard of someone saying "take business IH-35F" but I am not all that often in Texas. 
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 17, 2012, 03:53:39 PM
Quote from: agentsteel53 on January 17, 2012, 03:46:47 PM
does the general motoring public ever pay attention to the business route letter?
Very doubtful. But it's not really an error on Google's part, just a quirk.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on January 17, 2012, 03:56:58 PM
Quote from: NE2 on January 17, 2012, 03:53:39 PM

Very doubtful. But it's not really an error on Google's part, just a quirk.

I would disagree with you.  I've never considered the serial letter to be part of the route's numerical designation.  therefore, I think that google should show the route as it is colloquially known - especially in the case of Texas, where there is a legitimate I-35E, as well as the fifth business loop of I-35.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on January 17, 2012, 03:58:16 PM
If it were simply Google using the official suffix, then that's not consistent either.  Business I-35 through Dilley is signed correctly, no suffix.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on January 17, 2012, 06:07:04 PM
Google does three different things on three consecutive business routes. Is anyone surprised?
Title: Re: Incorrect highways marked on Google Maps
Post by: sandwalk on January 17, 2012, 11:51:57 PM
Not a highway.  But apparently Southwestern Vermont Medical Center is in north central Ohio. :D

http://maps.google.com/maps?q=willard+ohio&ll=41.051201,-82.718039&spn=0.037347,0.055189&hnear=Willard,+Huron,+Ohio&gl=us&t=m&z=14&vpsrc=6
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on January 18, 2012, 06:44:08 AM
Quote from: sandwalk on January 17, 2012, 11:51:57 PM
Not a highway.  But apparently Southwestern Vermont Medical Center is in north central Ohio. :D

http://maps.google.com/maps?q=willard+ohio&ll=41.051201,-82.718039&spn=0.037347,0.055189&hnear=Willard,+Huron,+Ohio&gl=us&t=m&z=14&vpsrc=6

I wonder if that's a result of bad geocoding, or a mistake by a foreign MapMaker user.

Bad geocoding results in a lot of POIs with addresses like "XXX Private Drive #YYY, South Point, OH" to be placed on a short residential street (with one house) called Private Dr in a neighborhood called Westpoint, over a hundred miles north in Franklin County.
Title: Re: Incorrect highways marked on Google Maps
Post by: Stephane Dumas on January 22, 2012, 11:53:54 AM
Not an highway but they're still reference to Detroit Olympia arena, former home of the Red Wings and the Pistons who was closed in 1980 and demolished in 1986.
http://maps.google.com/maps?q=42.353458,-83.100978&ll=42.352966,-83.099889&spn=0.003072,0.004823&num=1&vpsrc=0&t=m&z=18
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on January 22, 2012, 06:05:35 PM
The Google Street view shows NJ 109 over the Atlantic Intracoastal Waterway  in Lower, NJ as the Garden State Parkway.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on January 22, 2012, 06:30:13 PM
Quote from: agentsteel53 on January 17, 2012, 03:46:47 PM
Quote from: NE2 on January 17, 2012, 03:39:37 PM
That's TXDOT's method of identifying their business routes. Here's 35-H (and SH 46-C):

does the general motoring public ever pay attention to the business route letter?  I have not ever heard of someone saying "take business IH-35F" but I am not all that often in Texas. 

Mapsco (now defunct of course), which was supposed to be the authority in Texas road maps, did not know why the national atlas they put a cover on used suffixes on the BL shields in Texas. I pointed them out to their president and it was the first he had heard of them. So the answer should be "absolutely not".
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on January 28, 2012, 02:27:03 PM
Apparently, the small town of Waverly, Minnesota, has a two- or three-block section of State Highway 61 running right through its downtown.  I really would have expected more of the Minnesota highway department; note the distinct lack of route signage, center line, etc.  Also note that the "rest" of State Highway 61 exists as the would-be extension of I-35 from Duluth to Grand Portage.

http://maps.google.com/maps?hl=en&ll=45.068015,-93.965962&spn=0.011548,0.019205&t=m&z=16 (http://maps.google.com/maps?hl=en&ll=45.068015,-93.965962&spn=0.011548,0.019205&t=m&z=16)
Title: Re: Incorrect highways marked on Google Maps
Post by: US71 on February 02, 2012, 10:28:07 AM
Has anyone had problems submitting map corrections to Google? I have submitted 4, only to be told my submissions aren't valid.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 02, 2012, 12:09:46 PM
Quote from: US71 on February 02, 2012, 10:28:07 AM
Has anyone had problems submitting map corrections to Google? I have submitted 4, only to be told my submissions aren't valid.


Not here, but I haven't submitted many lately.
Title: Re: Incorrect highways marked on Google Maps
Post by: sandwalk on February 03, 2012, 12:04:49 PM
Quote from: vtk on January 18, 2012, 06:44:08 AM
Quote from: sandwalk on January 17, 2012, 11:51:57 PM
Not a highway.  But apparently Southwestern Vermont Medical Center is in north central Ohio. :D

http://maps.google.com/maps?q=willard+ohio&ll=41.051201,-82.718039&spn=0.037347,0.055189&hnear=Willard,+Huron,+Ohio&gl=us&t=m&z=14&vpsrc=6

I wonder if that's a result of bad geocoding, or a mistake by a foreign MapMaker user.

Bad geocoding results in a lot of POIs with addresses like "XXX Private Drive #YYY, South Point, OH" to be placed on a short residential street (with one house) called Private Dr in a neighborhood called Westpoint, over a hundred miles north in Franklin County.

Makes sense.  However, that location is indeed a hospital (Mercy Hospital of Willard).
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on February 08, 2012, 10:48:45 PM
And now Google has US 20 mutiplexed with US 20A for the entirety of the latter's routing, even though US 20's actual routing is still there!: http://g.co/maps/fqpfz
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on February 10, 2012, 02:06:00 PM
Quote from: WNYroadgeek on February 08, 2012, 10:48:45 PM
And now Google has US 20 mutiplexed with US 20A for the entirety of the latter's routing, even though US 20's actual routing is still there!: http://g.co/maps/fqpfz

I'm guessing the reason for this is their inability to show bannered routes, and for some reason they have this labeled as both US 20A and US 20 Alt.  Doesn't make it okay by any stretch of the imagination; in fact, it's a mistake layered on top of a mistake.

Similarly, in Niagara Falls, they have three consecutive blocks labelled as US 62. http://g.co/maps/3pqs3 (The two-way street should be 62 Business, formerly NY 62A.)
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on February 15, 2012, 02:06:57 PM
Someone must have went into MapMaker and added in the aisle numbers at a Home Depot near DC: http://g.co/maps/bmqs9 (http://g.co/maps/bmqs9)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 15, 2012, 03:29:01 PM
Quote from: HighwayMaster on February 15, 2012, 02:06:57 PM
Someone must have went into MapMaker and added in the aisle numbers at a Home Depot near DC: http://g.co/maps/bmqs9 (http://g.co/maps/bmqs9)
As footways, most likely. Nothing incorrect about that, just micromapping.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on February 16, 2012, 01:58:31 AM
Quote from: HighwayMaster on February 15, 2012, 02:06:57 PM
Someone must have went into MapMaker and added in the aisle numbers at a Home Depot near DC: http://g.co/maps/bmqs9 (http://g.co/maps/bmqs9)

Sure that's not related to Google's new Indoor Maps?
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on February 16, 2012, 12:46:23 PM
Wow..... I was just calculating mileage between fuel and meal stops for a trip to Minnesota tomorrow, and.....apparently the whole town of Ankeny, Iowa, no longer exists.  All the businesses it suggests have an Ankeny address, but I am unable to map the town itself, and the label 'Ankeny' is no longer on the map.  Poor guys.....
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on February 16, 2012, 01:33:54 PM
Quote from: NE2 on February 15, 2012, 03:29:01 PM
Quote from: HighwayMaster on February 15, 2012, 02:06:57 PM
Someone must have went into MapMaker and added in the aisle numbers at a Home Depot near DC: http://g.co/maps/bmqs9 (http://g.co/maps/bmqs9)
As footways, most likely. Nothing incorrect about that, just micromapping.

Who could possibly have the inclination to walk through the Home Depot with a GPS taking notes though? Or even to draw a map of the store layout with aisle numbers to fastidiously draw back up when they got home? It would almost have to be a bored geo-geek employee... if anyone else tried doing that they'd surely be asked not to...
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 16, 2012, 03:22:29 PM
Quote from: Scott5114 on February 16, 2012, 01:33:54 PM
Who could possibly have the inclination to walk through the Home Depot with a GPS taking notes though?
Er, GPS doesn't work indoors...
Title: Re: Incorrect highways marked on Google Maps
Post by: bsmart on February 17, 2012, 10:54:33 PM
Just a thought - It used to be the norm that reference books (dictionaries, atlases, etc) purposely put some false information in so that they could prove copyright infringement if necessary. ADC book maps usually had a few roads that could be said to be 'planned' or 'future' that were marked as existing that I believe fell into this category.  Could it be that Google is doing the same but all of us being able to discuss it in realtime makes it more obvious?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 17, 2012, 11:25:51 PM
Quote from: bsmart on February 17, 2012, 10:54:33 PM
Just a thought - It used to be the norm that reference books (dictionaries, atlases, etc) purposely put some false information in so that they could prove copyright infringement if necessary. ADC book maps usually had a few roads that could be said to be 'planned' or 'future' that were marked as existing that I believe fell into this category.  Could it be that Google is doing the same but all of us being able to discuss it in realtime makes it more obvious?
Quote from: Hanlon's Razor
Never attribute to malice that which can be adequately explained by stupidity.
Title: Re: Incorrect highways marked on Google Maps
Post by: bigboi00069 on February 17, 2012, 11:36:17 PM
Google maps shows US 41 continuing north along US 1 in Miami until I-395. It has terminated at US 1 (1.5 miles south of 395) since the mid 90s.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 18, 2012, 12:16:06 AM
Quote from: bigboi00069 on February 17, 2012, 11:36:17 PM
Google maps shows US 41 continuing north along US 1 in Miami until I-395. It has terminated at US 1 (1.5 miles south of 395) since the mid 90s.

Actually, US-41 officially still mutliplexes with US-1 and FL-A1A to end over at Washington Ave.  FDOT never submitted a request to the AASHTO to decommission that part of US-41.  Heck, even in their GIS data, they still show US-41 continuing over to Washington Ave.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 24, 2012, 06:36:01 AM
It's a TIGER error, but still amusing: http://maps.google.com/maps?q=%22loop%20closure%22
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 26, 2012, 01:15:31 AM
Here's a recent screw-up by Google.  Say bye-bye to US-17 and say hello to US-17B!

http://g.co/maps/fz2hf
Title: Re: Incorrect highways marked on Google Maps
Post by: US71 on February 26, 2012, 10:25:15 AM
I reported 4 errors yesterday. Let's see how they respond.

UPDATE: They accepted 3, but asked for more info on the fourth.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on February 26, 2012, 02:00:42 PM
Google just started claiming that I-81 north of NY 12 is not a freeway.  Before that, they claimed that ON 137 on Hill Island was.  Can't they understand that a route can be a freeway in the US and a two lane road in Canada?
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 05, 2012, 08:51:18 AM
Here's a good one that I just spotted.

http://g.co/maps/2bvbk

There's been a new alignment of the WB lanes of the PA Turnpike (I-76/I-70) heading towards the Allegheny Mountain Tunnel since at least July '09, however, Google shows the old alignment for the WB lanes.  Heck, they even have StreetView of the new alignment shown in the correct place, yet they show the old road on the map.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 05, 2012, 11:27:33 AM
My guess is that it's because the satellite imagery is outdated; the reviewers seem to think the imagery is gospel even when it's ancient.  I guess the concept of roads being re-aligned is foreign to them.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on March 05, 2012, 11:54:25 AM
I added a bike trail in MapMaker once, and the reviewer commented something like "the geometry doesn't match aerialv imagery; I've fixed this".  I didn't notice any change in my geometry, but I wonder what the reviewer thought he saw – the imagery was at least a year older than the earliest  construction work on the bike path. (I derived my geometry from a GPS trace i'd taken.)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 06, 2012, 02:26:34 AM
Quote from: deanej on March 05, 2012, 11:27:33 AM
My guess is that it's because the satellite imagery is outdated; the reviewers seem to think the imagery is gospel even when it's ancient.  I guess the concept of roads being re-aligned is foreign to them.

Well, I just recently tested out the directions in that area and they use the new alignment.  So, it seems the tiles just haven't been updated yet.
Title: ¿¿I-585 Atlanta??
Post by: Eisenhower on March 14, 2012, 01:26:37 AM
According to Google Maps, GA 400 is now officially "I-585" between I-85 and I-285 (unconfirmed).

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fdl.dropbox.com%2Fu%2F21890345%2Faaroads%2Fi585atl.png&hash=86de8abaf07010c17a1d369dc678b7297a3ad969)
Title: Re: ¿¿I-585 Atlanta??
Post by: NE2 on March 14, 2012, 01:33:24 AM
Whoa. Someone got that past the censors.
Title: Re: ¿¿I-585 Atlanta??
Post by: rickmastfan67 on March 14, 2012, 01:53:15 AM
Quote from: NE2 on March 14, 2012, 01:33:24 AM
Whoa. Someone got that past the censors.

It hasn't made it into the directions yet.  Let's see how long it will stay on the map without one of us reporting it. LOL.
Title: Re: ¿¿I-585 Atlanta??
Post by: Mr. Matté on March 14, 2012, 01:25:24 PM
Quote from: rickmastfan67 on March 14, 2012, 01:53:15 AM
It hasn't made it into the directions yet.  Let's see how long it will stay on the map without one of us reporting it. LOL.

Well, if one of us reports it, then it probably gets the ol' "Please kindly undo this edit" from the know-nothings at Google.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on March 14, 2012, 06:15:17 PM
That is a great error, I hope it stays as long as possible.  :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on March 14, 2012, 06:48:15 PM
What if they know something we don't...
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 15, 2012, 11:47:39 AM
Quote from: Steve on March 14, 2012, 06:48:15 PM
What if they know something we don't...

Since when has Google ever been ahead of the game? LOL.

Anyways, here's a quick link (http://g.co/maps/ygp8v) to it so we can all keep tabs on this phantom Interstate. :bigass:
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on March 15, 2012, 01:11:25 PM
Someone needs to contact GDOT and see if they have made any requests to FHWA and/or AASHTO.
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on March 15, 2012, 06:19:14 PM
Quote from: Mr. Matté on March 14, 2012, 01:25:24 PM
Quote from: rickmastfan67 on March 14, 2012, 01:53:15 AM
It hasn't made it into the directions yet.  Let's see how long it will stay on the map without one of us reporting it. LOL.

Well, if one of us reports it, then it probably gets the ol' "Please kindly undo this edit" from the know-nothings at Google.

Out of curiosity: what happens if you don't comply with their request to "undo this edit"?
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 16, 2012, 10:13:36 PM
Quote from: Scott5114 on March 15, 2012, 06:19:14 PM
Quote from: Mr. Matté on March 14, 2012, 01:25:24 PM
Quote from: rickmastfan67 on March 14, 2012, 01:53:15 AM
It hasn't made it into the directions yet.  Let's see how long it will stay on the map without one of us reporting it. LOL.

Well, if one of us reports it, then it probably gets the ol' "Please kindly undo this edit" from the know-nothings at Google.

Out of curiosity: what happens if you don't comply with their request to "undo this edit"?

They keep harassing you to do it until they eventually do it themselves after about a month, maybe month and a half.  That's the experience I encountered with that whole "I-381 is NOT a Freeway" mentality I experienced last year till then finally got it correct.
Title: Re: Incorrect highways marked on Google Maps
Post by: Brian556 on March 17, 2012, 12:54:33 AM
In Tennessee. US 31A is marked as "US 31" I used street view to check the signs, they all say "31A".
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 17, 2012, 12:59:27 AM
Quote from: Brian556 on March 17, 2012, 12:54:33 AM
In Tennessee. US 31A is marked as "US 31" I used street view to check the signs, they all say "31A".
Yes, we know that Google borks banners (even fake ones).
Title: Re: Incorrect highways marked on Google Maps
Post by: Stephane Dumas on March 17, 2012, 09:25:42 AM
Quote from: Alex on March 14, 2012, 06:15:17 PM
That is a great error, I hope it stays as long as possible.  :-D

Now if they could mark again the unsigned roads like NJ-444 (Garden State Parkway) or FL-91 (FL Tpk). ;)

Would be interesting if Google Maps showed the Queen Elizabeth Way marked as QEW just like in the MapArt and Rand-McNally road maps like for example in this MapArt map.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1268.photobucket.com%2Falbums%2Fjj563%2Fsd-100%2Fmap_oakville.jpg&hash=7ffea17fe282bcaa5102b59eb982a1e28e912e25)
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on March 17, 2012, 12:08:25 PM
Quote from: Stephane Dumas on March 17, 2012, 09:25:42 AMNow if they could mark again the unsigned roads like NJ-444 (Garden State Parkway) or FL-91 (FL Tpk). ;)

They do mark some of them.  See, for instance, the GA 403 shield on I-85 in the I-585 error link above.
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on March 17, 2012, 04:47:32 PM
They also show Kentucky's parkways with their hidden 9000-series inventory numbers.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 20, 2012, 09:56:25 PM
Booo, the I-585 error in Atlanta is now gone. :(

Who here reported it?
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on March 21, 2012, 12:19:57 AM
Google broke NY 21: http://g.co/maps/wz6m7

You can still route directions on the broken part, though: http://g.co/maps/fs727
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on March 21, 2012, 11:21:34 AM
Oh, I hate broken highways.  Google broke Mexican federal highway 40 between Saltillo and Torreón.  Apparently half of this divided highway just doesn't exist for a little bit.  Getting directions doesn't work either, and would involve driving on roads that can barely be called paved anymore.
http://g.co/maps/u7b5d (http://g.co/maps/u7b5d)
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on March 21, 2012, 11:27:54 AM
Quote from: kphoger on March 21, 2012, 11:21:34 AM
Oh, I hate broken highways.  Google broke Mexican federal highway 40 between Saltillo and Torreón.  Apparently half of this divided highway just doesn't exist for a little bit.  Getting directions doesn't work either, and would involve driving on roads that can barely be called paved anymore.
http://g.co/maps/u7b5d (http://g.co/maps/u7b5d)

if I saw those directions, I'd assume "oh, the road isn't actually broken" and mentally eliminate that small kink.

from the satellite image, it looks like the road is in good shape... if it turns out to be broken in real life, I suppose I'd ask the locals what to do.

in related news: that is an awesome salt flat.  I must go there.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on March 21, 2012, 11:43:56 AM
Quote from: agentsteel53 on March 21, 2012, 11:27:54 AM
Quote from: kphoger on March 21, 2012, 11:21:34 AM
Oh, I hate broken highways.  Google broke Mexican federal highway 40 between Saltillo and Torreón.  Apparently half of this divided highway just doesn't exist for a little bit.  Getting directions doesn't work either, and would involve driving on roads that can barely be called paved anymore.
http://g.co/maps/u7b5d (http://g.co/maps/u7b5d)

if I saw those directions, I'd assume "oh, the road isn't actually broken" and mentally eliminate that small kink.

from the satellite image, it looks like the road is in good shape... if it turns out to be broken in real life, I suppose I'd ask the locals what to do.

in related news: that is an awesome salt flat.  I must go there.

Yes, one would naturally assume the highway still continued, especially if there were no warning signs advising otherwise.  However, it makes calculating accurate distances on Google maps difficult, because eastbound and westbound lanes separate and have different lenghts along there.

As far as the road being in good condition.... Satellite imagery of the area is old:  it hasn't been updated since I first starting viewing the area in 2008.  I have not personally driven that stretch of highway, but I have been within 32 miles as recently as March of last year, and I think I would have heard about some natural disaster wiping out the primary east-west highway in north-central México if something like that had indeed happened.  For example, you might just suspect there to be a thread in the Mexican highway threads on SkyscraperCity.  So, yeah, the road is still there.

Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 11, 2012, 05:03:33 AM
I didn't know that the US Highway network now started to have "named" highways in addition to numbered ones....

http://g.co/maps/d4va9
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on April 16, 2012, 05:31:33 PM
This one editor has added many interesting roads, including the part of I-70 in Balto never built:

http://www.google.com/mapmaker?gw=66&ptab=1&uid=204116578521277253534 (http://www.google.com/mapmaker?gw=66&uid=204116578521277253534)

BTW, U.S. Route 30 "in Nebraska" is in Ohio. It probably is that from Astoria to Atlantic City.

http://g.co/maps/a92ku (http://g.co/maps/a92ku)
Title: Re: Incorrect highways marked on Google Maps
Post by: InterstateNG on April 16, 2012, 06:02:23 PM
Quote from: HighwayMaster on April 16, 2012, 05:39:04 PM
Bad news about I-585 in Atlanta: It's gone.

As reported a month ago:

Quote from: rickmastfan67 on March 20, 2012, 09:56:25 PM
Booo, the I-585 error in Atlanta is now gone. :(

Who here reported it?
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on April 16, 2012, 06:26:49 PM
http://maps.google.com/?ll=42.46317,-90.49593&spn=0.036028,0.085487&t=m&z=14

So US 20 in Nebraska is now multiplexed with US 20 in Illinois.
Title: Re: Incorrect highways marked on Google Maps
Post by: F350 on April 16, 2012, 07:34:44 PM
And another...

http://g.co/maps/bqeb7
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on April 16, 2012, 07:59:28 PM
Quote from: Steve on April 16, 2012, 06:26:49 PM
http://maps.google.com/?ll=42.46317,-90.49593&spn=0.036028,0.085487&t=m&z=14

So US 20 in Nebraska is now multiplexed with US 20 in Illinois.
Quote from: F350 on April 16, 2012, 07:34:44 PM
And another...

http://g.co/maps/bqeb7

Uh-oh. I see a theme happening. We had better not see "U.S. Route [number] in [state]" on every US route.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on April 16, 2012, 09:39:38 PM
I think I see the problem.
QuoteNames can be changed by editing the corresponding route from the "Edit" menu for this segment.
To edit the route name, select the Edit entire route option in the segment dropdown. When you edit the route name, multiple segments may be affected, even if the segments are not visible.

Stupid, Google, stupid.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 17, 2012, 01:32:05 AM
Quote from: Bickendan on April 16, 2012, 09:39:38 PM
I think I see the problem.
QuoteNames can be changed by editing the corresponding route from the "Edit" menu for this segment.
To edit the route name, select the Edit entire route option in the segment dropdown. When you edit the route name, multiple segments may be affected, even if the segments are not visible.

Stupid, Google, stupid.

Kinda like OSM's relations. Except in OSM, the relation names normally don't get rendered.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 17, 2012, 01:37:37 AM
Quote from: rickmastfan67 on April 17, 2012, 01:32:05 AM
Kinda like OSM's relations. Except in OSM, the relation names normally don't get rendered.
If I'm not mistaken, Google has only one name/ref field for relations, and you're supposed to put e.g. "Florida 50" in there. Perhaps people are trying to get fancy here and create state-by-state relations for U.S. Routes without support for such.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on April 17, 2012, 10:04:02 AM
As far as I  know, Google MapMaker doesn't provide a means to change which road segments are or are not part of a "relation", except for adding brand-new roads to it ("extend such-and-such road" when drawing a new segment). It seems this must be done by someone with more advanced tools. Then again, I haven't messed with it much since before they "improved" the MapMaker interface.
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on April 19, 2012, 06:37:58 PM
Not a road, but I don't remember Norway, ME as being this big:

http://g.co/maps/4zmav (http://g.co/maps/4zmav)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 19, 2012, 07:11:12 PM
Quote from: HighwayMaster on April 19, 2012, 06:37:58 PM
Not a road, but I don't remember Norway, ME as being this big:

http://g.co/maps/4zmav (http://g.co/maps/4zmav)
Huh?
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on April 19, 2012, 08:19:23 PM
Took me a second, but Norway, Maine has a bigger city locator dot and text than Portland, Maine does. You'd think, at that zoom level, that Norway was the biggest city in Maine.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDRoads on April 22, 2012, 01:55:14 PM
I noticed over the last week or so that the entire length of US 1 is named "W City Ave," as if it was accidentally named on the relation level.
Title: Re: Incorrect highways marked on Google Maps
Post by: PurdueBill on April 22, 2012, 02:38:35 PM
If Google doesn't straighten out stuff like this (especially things like all of US 1 being City Ave) really fast, then what do they expect people to think of their product?  As it is, it looks like Google Maps is very, very unreliable if anyone can go and vandalize it basically.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDRoads on April 22, 2012, 03:30:35 PM
It is properly named as such in part of Philadelphia; someone must have named the entire route accidentally, not just the piece he was working on.
Title: Re: Incorrect highways marked on Google Maps
Post by: PurdueBill on April 22, 2012, 03:33:49 PM
Quote from: MDRoads on April 22, 2012, 03:30:35 PM
It is properly named as such in part of Philadelphia; someone must have named the entire route accidentally, not just the piece he was working on.

Yep, that is probably where it is from (with honkers behind Dave Roberts's weather forecast and all), but Google has to make it so that these things don't perpetuate instantly to the whole route.

Amazingly, this afternoon as part of some family tree research I am helping my family with, I was looking for some things in Rockland, Maine and was mapping on Google--what do you know......US 1A in Rockland, Maine has even been hit as W City Ave--even both streets of a pair of one-ways!  At some zoom levels, that name is shown and not the correct street name!  Bravo, Google!  Sigh.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 22, 2012, 05:54:17 PM
I honestly dare somebody to attempt to add Interstate shields to the entire distance of US-1, US-17, and US-90 and see if it gets past the idiots who approve changes at Google. :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: mukade on April 22, 2012, 06:44:31 PM
Quote from: HighwayMaster on April 16, 2012, 07:59:28 PM
Quote from: Steve on April 16, 2012, 06:26:49 PM
http://maps.google.com/?ll=42.46317,-90.49593&spn=0.036028,0.085487&t=m&z=14

So US 20 in Nebraska is now multiplexed with US 20 in Illinois.
Quote from: F350 on April 16, 2012, 07:34:44 PM
And another...

http://g.co/maps/bqeb7

Uh-oh. I see a theme happening. We had better not see "U.S. Route [number] in [state]" on every US route.

Many/most US highways in Indiana are now US route xx in [state]. US 20, US 24, and US 30 are three that I checked.

A couple of interesting things. If you look at US 20 around South Bend, eastbound is in Nebraska and westbound is in Illinois. It seems like Nebraska and Illinois are important states in this new system of naming highways for Google. Another interesting thing is that the road/highway name appears over and over - much more so that real road names.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadfro on April 23, 2012, 03:32:21 AM
^ It appears someone is blindly following the Wikipedia naming policies for state-detail articles of US routes...
Title: Re: Incorrect highways marked on Google Maps
Post by: mcdonaat on April 23, 2012, 05:49:22 AM
In small road geek news, Google removed the shields for US 84 for about a month. Contacted em, and they said conflicting interests prevented them from readding the shields. checked back, and they added the shields. US 165 between Monroe and Sterlington (both in LA) is a broken route.
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on April 23, 2012, 07:18:38 PM
Zoom in to US 20 in Michigan City, Ind., and see what you find.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 23, 2012, 07:46:34 PM
Quote from: hbelkins on April 23, 2012, 07:18:38 PM
Zoom in to US 20 in Michigan City, Ind., and see what you find.
Elks Lodge?
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on April 23, 2012, 07:47:01 PM
Is the entirety of US 20 marked as "in Illinois"/"in Nebraska" now? I noticed the same thing in Toledo...
Title: Re: Incorrect highways marked on Google Maps
Post by: roadfro on April 23, 2012, 09:42:34 PM
Quote from: roadfro on April 23, 2012, 03:32:21 AM
^ It appears someone is blindly following the Wikipedia naming policies for state-detail articles of US routes...

More evidence of this: Spanish Fork, Utah (http://g.co/maps/kcjf8)

Roads around the junction of US 6 & US 89 show as street names "U.S. Route 89 in Arizona", "U.S. Route 6 in California", and the most egregious "U.S. 6 in Rhode Island".
Title: Re: Incorrect highways marked on Google Maps
Post by: PurdueBill on April 23, 2012, 11:25:48 PM
Quote from: mcdonaat on April 23, 2012, 05:49:22 AM
In small road geek news, Google removed the shields for US 84 for about a month. Contacted em, and they said conflicting interests prevented them from readding the shields. checked back, and they added the shields. US 165 between Monroe and Sterlington (both in LA) is a broken route.

I wonder what "conflicting interests" could possibly mean....either the road is US 84 or it's not!  It's not a matter of opinion or taste.

US 1A in Thomaston and Rockland, Maine is still W. City Ave, I see.....my submission of a report probably will have not done anything.  If they are getting reports of every instance of a misnamed US highway right now, they will be swamped forever.  Whoever at Google came up with allowing that kind of change to be made without an easy revert shouldn't be with Google much longer.....
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 23, 2012, 11:54:06 PM
Quote from: mcdonaat on April 23, 2012, 05:49:22 AM
In small road geek news, Google removed the shields for US 84 for about a month. Contacted em, and they said conflicting interests prevented them from readding the shields. checked back, and they added the shields. US 165 between Monroe and Sterlington (both in LA) is a broken route.

US-19W lost it's shields in NC and TN. I sent them a report and they only re-added the shields back in NC (only 2 total showing up at the same locations in all zooms).....

Google is f'ed up bad I'd say.
Title: Re: Incorrect highways marked on Google Maps
Post by: PurdueBill on April 24, 2012, 10:17:34 PM
US 1 has still lost all of its shields; it's W City Ave its whole length right now.  Useless......
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on April 24, 2012, 10:44:53 PM
Where does the "City Ave" name come from, and how can Google Maps get rid of ALL of US 1?
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on April 24, 2012, 10:49:49 PM
Quote from: tdindy88 on April 24, 2012, 10:44:53 PM
Where does the "City Ave" name come from, and how can Google Maps get rid of ALL of US 1?

Likely Philadelphia, where U.S. 1 straddles the city line along City Avenue.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 26, 2012, 03:33:24 AM
Quote from: tdindy88 on April 24, 2012, 10:44:53 PM
Where does the "City Ave" name come from, and how can Google Maps get rid of ALL of US 1?

It's easy when the reviewers @ Google don't have the faintest idea what they are doing.  Thus, the stupidest things get past them with ease.
Title: Re: Incorrect highways marked on Google Maps
Post by: mightyace on April 26, 2012, 06:43:22 PM
And yet, they turned down my changes for setting the speed limit to what it really is on a local road.
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on April 27, 2012, 12:32:51 AM
Another day, another road broken by Google. This time I-490 west: http://g.co/maps/6zvaf
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 27, 2012, 12:41:16 AM
Quote from: WNYroadgeek on April 27, 2012, 12:32:51 AM
Another day, another road broken by Google. This time I-490 west: http://g.co/maps/6zvaf

However, the directions are broken there, yet....
Title: Re: Incorrect highways marked on Google Maps
Post by: mcdonaat on April 27, 2012, 04:37:28 AM
Quote from: WNYroadgeek on April 27, 2012, 12:32:51 AM
Another day, another road broken by Google. This time I-490 west: http://g.co/maps/6zvaf
I think Google has a reserve of highways that they use... corrected a piece of US Highway 165 north of where I live, only to find two identical sections about a mile south were removed.
Title: Re: Incorrect highways marked on Google Maps
Post by: Morriswa on April 27, 2012, 06:41:40 AM
I don't know if it has been mentioned yet, but US 41/US 76/SR 2/SR 3 in Ringgold, GA (near Chattanooga, TN) is labeled as "U.S. Route 41 in Illinois".

http://g.co/maps/jdsny (http://g.co/maps/jdsny)

I'm about to report it.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 27, 2012, 07:18:08 AM
Quote from: Morriswa on April 27, 2012, 06:41:40 AM
I don't know if it has been mentioned yet,
:banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 27, 2012, 09:56:04 AM
Quote from: Morriswa on April 27, 2012, 06:41:40 AM
I don't know if it has been mentioned yet, but US 41/US 76/SR 2/SR 3 in Ringgold, GA (near Chattanooga, TN) is labeled as "U.S. Route 41 in Illinois".

http://g.co/maps/jdsny (http://g.co/maps/jdsny)

I'm about to report it.

While that one in particular wasn't mentioned on the last page, people were well aware of things like this happening on several other US Highways already.
Title: Re: Incorrect highways marked on Google Maps
Post by: Morriswa on April 27, 2012, 03:20:33 PM
Yes, I know.
Title: Re: Incorrect highways marked on Google Maps
Post by: Takumi on April 28, 2012, 11:38:15 AM
First Colonial Road in Virginia Beach is shown as SR 615 (with a circle) and VA 408 (written out "State Route 408"). It is currently neither. (Can't post the link because I'm on my phone.) There are several other instances of the old Princess Anne County secondary route numbers in Virginia Beach as well.
Title: Re: Incorrect highways marked on Google Maps
Post by: D-Dey65 on April 29, 2012, 10:25:35 AM
Quote from: Morriswa on April 27, 2012, 06:41:40 AM
I don't know if it has been mentioned yet, but US 41/US 76/SR 2/SR 3 in Ringgold, GA (near Chattanooga, TN) is labeled as "U.S. Route 41 in Illinois".

http://g.co/maps/jdsny (http://g.co/maps/jdsny)

I'm about to report it.
For some reason Google's coverage of US 41 in Florida contains the blatantly incorrect street name "US Route 41 in Illinois."

While you're at it, you can report that. I'll bet they made the same mistake in Georgia too.





Title: Re: Incorrect highways marked on Google Maps
Post by: bulldog1979 on April 29, 2012, 10:46:32 AM
Quote from: D-Dey65 on April 29, 2012, 10:25:35 AM
Quote from: Morriswa on April 27, 2012, 06:41:40 AM
I don't know if it has been mentioned yet, but US 41/US 76/SR 2/SR 3 in Ringgold, GA (near Chattanooga, TN) is labeled as "U.S. Route 41 in Illinois".

http://g.co/maps/jdsny (http://g.co/maps/jdsny)

I'm about to report it.
For some reason Google's coverage of US 41 in Florida contains the blatantly incorrect street name "US Route 41 in Illinois."

While you're at it, you can report that. I'll bet they made the same mistake in Georgia too.

The entire length of US 41 is labeled as "in Illinois"... all the way up to Copper Harbor, Michigan. US 2 is "in Idaho", so when I was plotting something the other day, I could have followed the combination of "U.S. Route 2 in Idaho", "U.S. Route 41 in Illinois" and "Michigan 35" (they can't seem to get that corrected to just M-35 either).
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on April 29, 2012, 12:03:08 PM
I think it's been mentioned further up, but it seems that every U.S. highway that goes through Indiana that also goes through Illinois, that doesn't have a name of its own (U.S. 40 = National Road, which is still mentioned) is called US Route XX in Illinois. I just wasn't sure if this mistake was made to other segments of highway in other states.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on April 29, 2012, 02:34:55 PM
What's really bad is that the eastern US 2 is also labeled "US 2 in Idaho".
Title: Re: Incorrect highways marked on Google Maps
Post by: SSOWorld on April 29, 2012, 07:42:33 PM
Quote from: D-Dey65 on April 29, 2012, 10:25:35 AM
Quote from: Morriswa on April 27, 2012, 06:41:40 AM
I don't know if it has been mentioned yet, but US 41/US 76/SR 2/SR 3 in Ringgold, GA (near Chattanooga, TN) is labeled as "U.S. Route 41 in Illinois".

http://g.co/maps/jdsny (http://g.co/maps/jdsny)

I'm about to report it.
For some reason Google's coverage of US 41 in Florida contains the blatantly incorrect street name "US Route 41 in Illinois."

While you're at it, you can report that. I'll bet they made the same mistake in Georgia too.

and this - http://g.co/maps/3ct8v
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on April 30, 2012, 08:56:27 PM
Probably any given US Route that passes through Illinois has that error as seen in this shot from KC along the I-70/US 40/US 24 multiplex.
http://g.co/maps/urpx9 (http://g.co/maps/urpx9)
Title: Re: Incorrect highways marked on Google Maps
Post by: Hot Rod Hootenanny on May 02, 2012, 10:02:43 PM
Over on one of the Lincoln Highway Facebook groups we've had the following discussion today...

QuoteMichael Engle
In google maps, if you type in Dalton, Oh you get "US Route 30 in Nebraska" on the map.
Like.Unlike ·  ·Unfollow Post.Follow Post · Monday at 9:52pm

Sandor Gulyas
That's just the tip of the iceburg when it comes to google map errors.
www.aaroads.com/forum/index.php?topic=2001.0
Monday at 10:01pm · LikeUnlike · .

Michael Engle
and US 24 between Toledo and Fort Wayne is known as US Rt 24 in Illinois.
Monday at 10:05pm · LikeUnlike.

Gary Gilmore
Have you reported these problems to Google?
Yesterday at 3:00pm · LikeUnlike.

Michael Engle
nope. i kind of like the mistakes. it makes it more intersting
22 hours ago · LikeUnlike.

Sandor Gulyas
Gary, others have reported the "errors" to google (see link above to examples of over 200 noted errors over 3 years) and have evidently been given run-arounds over the validitity of their concern.
11 hours ago · LikeUnlike.

Gary Gilmore
Dunno. Every correction I've reported has be handled within a month.
8 hours ago · LikeUnlike.

Sem C. Sutter
I've sent them corrections that they handled efficiently and politely
2 hours ago · LikeUnlike.

Jeff Kitsko
I've sent in corrections and have gotten e-mails saying they were approved, but I have yet to see any of them published. However, I seem to see more errors each time I go to Google Maps.
17 minutes ago · LikeUnlike.

Gary Gilmore
To be fair, it's a mammoth job they've got there.
4 minutes ago · LikeUnlike.

Jeff Kitsko
I understand, but somehow it seems more errors than corrections are getting through. For example, I saw US 22 is now designated as an expressway between Pittsburgh and Altoona.

Gary Gilmore
Is it scheduled to be improved to expressway levels? Myself, as long as the road is in the right place, I'm smart enough to figure out that there's an error, and deal with it. By and large, Google Maps is pretty darn good, free, and will get you from point A to point B. (I also use it in conjunction with my TomTom, so one of them is bound to be right.)
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on May 03, 2012, 11:17:18 AM
Is this the part where we're supposed to collectively facepalm?
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on May 03, 2012, 04:17:40 PM
Quote from: national highway 1 on April 30, 2012, 08:56:27 PM
Probably any given US Route that passes through Illinois has that error as seen in this shot from KC along the I-70/US 40/US 24 multiplex.
http://g.co/maps/urpx9 (http://g.co/maps/urpx9)

Not here!
http://g.co/maps/v3caf (http://g.co/maps/v3caf)
Title: Re: Incorrect highways marked on Google Maps
Post by: Brian556 on May 03, 2012, 08:57:00 PM
All of US 67 in Texas has recently been tagged "US Route 67 in Illinois" WTF?
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1209.photobucket.com%2Falbums%2Fcc395%2FBrian5561%2F67illinois.png&hash=b6d180181fc3caec0b5351e3743d710661c50438)

Gifco Rd near Midlothian, TX has mysteriously been tagged " State Hwy 2"
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1209.photobucket.com%2Falbums%2Fcc395%2FBrian5561%2Fstatehwy2error.png&hash=1ec07c64b505ce860fe8dce33655e1714b38e44c)
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 03, 2012, 09:01:26 PM
The next person who brings up a "U.S. Route X in XXXX" error will be viciously and repeatedly slapped in the face with a fish.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on May 03, 2012, 09:18:54 PM
Quote from: Kacie Jane on May 03, 2012, 09:01:26 PM
The next person who brings up a "U.S. Route X in XXXX" error will be viciously and repeatedly slapped in the face with a fish.

Agreed.  We all know about this happening.  No need to keep telling us. lol.  Just report it to Google (if you want to) and leave it at that. ;)  Save this thread for the really crazy ones that aren't the "U.S. Route X in XXXX" error. LOL. :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on May 03, 2012, 10:32:04 PM
US 66 has been reinstated!
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on May 03, 2012, 10:34:04 PM
Quote from: corco on May 03, 2012, 10:32:04 PM
US 66 has been reinstated!

ROTFL!!! If you didn't believe that the Google Mods are idiots, this proves it!!
http://g.co/maps/7qra5
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on May 03, 2012, 10:46:34 PM
are we sure the 66 isn't intentional?
Title: Re: Incorrect highways marked on Google Maps
Post by: mukade on May 03, 2012, 10:48:54 PM
Quote from: corco on May 03, 2012, 10:32:04 PM
US 66 has been reinstated!

Everyone knows that should be US 66 in Illinois.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 03, 2012, 11:39:03 PM
Quote from: agentsteel53 on May 03, 2012, 10:46:34 PM
are we sure the 66 isn't intentional?

Well, it's certainly intentional on someone's part, it didn't just show up by mere accident.  That doesn't make it correct.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on May 03, 2012, 11:47:52 PM
Quote from: Kacie Jane on May 03, 2012, 11:39:03 PM
Well, it's certainly intentional on someone's part, it didn't just show up by mere accident.  That doesn't make it correct.
I don't mind it too much, but I wish they'd use something like a brown or gray shield, and also label the old alignment.  any idiot can drive US-66 by taking I-40, 44, etc.
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on May 03, 2012, 11:52:52 PM
So US 66 is back. If it hasn't happened yet, this is Google Maps' "jump the shark" moment.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on May 04, 2012, 01:56:27 AM
Google Maps: Used by the cast of Happy Days.
Title: Re: Incorrect highways marked on Google Maps
Post by: mcdonaat on May 04, 2012, 09:39:12 AM
Quote from: Scott5114 on May 03, 2012, 11:52:52 PM
So US 66 is back. If it hasn't happened yet, this is Google Maps' "jump the shark" moment.
Nobody should report it :P
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 04, 2012, 05:50:10 PM
Quote from: agentsteel53 on May 03, 2012, 11:47:52 PM
Quote from: Kacie Jane on May 03, 2012, 11:39:03 PM
Well, it's certainly intentional on someone's part, it didn't just show up by mere accident.  That doesn't make it correct.
I don't mind it too much, but I wish they'd use something like a brown or gray shield, and also label the old alignment.  any idiot can drive US-66 by taking I-40, 44, etc.

I find it ironic that your post starts with the words, "I don't mind it too much", and then you state exactly why I do mind it.  I have no problem with RMcN's treatment of Route 66.  It doesn't specify it as old or historic, but it does separate it from present day routes, and it labels an alignment that people would actually be interested in following for its historical significance, rather than simply labelling a corridor.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on May 05, 2012, 10:46:43 AM
So I tried changing all of US 40 to "U.S. Route 40 in New Jersey" (because there's "Too much bias for the Midwest for misnamed U.S. Routes. (US 30 in Nebraska, US 67 in Illinois, etc.)"). This is the response I got:

QuoteReason: Good information changed for the worse
Comments: That routes identified by state name have spread across the country is a bug that will soon be fixed. Let's not give Google one more bug to sort through.

I don't think these naming issues are bugs though...
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on May 05, 2012, 03:43:13 PM
Maybe it is, though attempting to change the whole name of the route to another state isn't. At least they're 'aware' of it and claim they'll fix it soon. Prediction: The US route error will be fixed, only for a similar issue for the Interstates, E-Routes or (more subtly) for the Rocky/Prairie TCH...
Title: Re: Incorrect highways marked on Google Maps
Post by: sr641 on May 07, 2012, 06:26:15 AM
indiana 641 is labeled as yellow and it shows indiana 63 ending at hulman  street rather than at the exit with us 41 in terre haute
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 10, 2012, 05:14:11 PM
Apparently, Mexican federal highway 95(D) goes by number on one side, and goes by name on the other.
Also notice the English tag 'Toll road' versus the Spanish tag 'Vía de peaje' (a term not really used in México).
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2FPeaje.png&hash=a0f8b5537127353dc62a0ab60dea5985696bfb64)
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on May 10, 2012, 05:24:57 PM
Why can't GM use the reddish notation for toll roads that is used in Europe for the US and Canada instead of just using "(Toll road)"?
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on May 11, 2012, 01:01:05 AM
For that matter, why do Japan and the British Isles get a different symbology from the rest of the world?
(With that said, the Japan/British symbology looks cleaner than the rest of the worlds x.x)
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 11, 2012, 10:58:03 AM
I also like how nearly every federal or state highway in México is drawn with an orange line, whereas only freeways are orange in the States.  Zoom out, and it looks like the U.S. has a pathetic road system compared to our southern neighbors.  :crazy:
Title: Re: Incorrect highways marked on Google Maps
Post by: txstateends on May 11, 2012, 04:00:12 PM
I looked at the US 66 "redesignation", and the OK 4-route overlap is back: http://g.co/maps/2tz82

Meanwhile, another "blanket" labeling, along US 62 (which I first noticed several days ago), "Brownfield Hwy.", has apparently been removed.  I've checked several spots, none of which listed the naming--which should only label the part between Lubbock and Brownfield, TX.
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on May 11, 2012, 05:42:57 PM
Quote from: mukade on May 03, 2012, 10:48:54 PM
Quote from: corco on May 03, 2012, 10:32:04 PM
US 66 has been reinstated!

Everyone knows that should be US 66 in Illinois.

I literally LOL'd.




Here's (http://maps.google.com/?ll=42.928942,-76.599104&spn=0.001699,0.003484&t=m&z=19) something a little different than the "US X In _____" error.  It's two "US X In _____" errors on the same road!

P.S.: Kacie, please don't slap me with a fish!
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 11, 2012, 06:43:47 PM
Quote from: Michael on May 11, 2012, 05:42:57 PM
Here's (http://maps.google.com/?ll=42.928942,-76.599104&spn=0.001699,0.003484&t=m&z=19) something a little different than the "US X In _____" error.  It's two "US X In _____" errors on the same road!

P.S.: Kacie, please don't slap me with a fish!

I'll concede that it is quite amusing to have each direction labeled as being in a different state.

Nevertheless, here, have a herring...
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.sideshowtoy.com%2Fmas_assets%2Flarge%2F3717R.jpg&hash=64cacf4d2a1e2e34ecd64d8a7a2346bb211f6ac9)
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on May 11, 2012, 09:48:41 PM
Perhaps the median runs down the state line.  :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: Morriswa on May 11, 2012, 11:10:21 PM
Kacie Jane, what is that picture?
Title: Re: Incorrect highways marked on Google Maps
Post by: ftballfan on May 11, 2012, 11:15:47 PM
M-394 in Cass County is still on the map.
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on May 11, 2012, 11:20:21 PM
Quote from: Bickendan on May 11, 2012, 01:01:05 AM
For that matter, why do Japan and the British Isles get a different symbology from the rest of the world?
(With that said, the Japan/British symbology looks cleaner than the rest of the worlds x.x)

Symbology in the British isles is much more standardized than in America. Every British map I've seen uses blue lines for the motorways, green lines for the A roads... it would probably not do much for their UK market share if they did their own thing.
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on May 12, 2012, 07:20:08 AM
^^ there's a few exceptions to that (and green lines are primary routes, not A roads) - Michelin being the biggest one (and older mapping being similar in using line thickness to designate primary/trunk routes)

Typically you get this:
Motorways: Blue - signed with blue signs
Primary Routes: Green - signed with green signs
National Secondary roads (RoI): dotted green lines (OS Ireland)/red/green (Google) - signed with green signs
Other A Roads: Red/orange (Google) - signed with white signs
B Roads: Brown (OS)/yellow - signed with white signs
Other roads: yellow & white (OS)/white

Google's recent changes have caused all sorts of annoyance, with blue being used for non-motorway roads, roads being given colour by importance and quality, rather than A-B-other (many B roads show in red, some in white. Ditto unclassified roads. A roads shown in yellow). This adds to the existing ignorance of convention on motorway ramps (which as they are motorway, are normally showed in blue) - they even show full on motorway spurs as red or green. Most of the blatant ones have been corrected following SABRE's complaints (and one or two took a couple of goes to do).
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on May 12, 2012, 10:44:23 AM
Quote from: english si on May 12, 2012, 07:20:08 AM
Most of the blatant ones have been corrected following SABRE's complaints (and one or two took a couple of goes to do).

Good on SABRE for fighting the good fight–you've seen the reception most AARoads members have had.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 12, 2012, 12:57:16 PM
Quote from: Morriswa on May 11, 2012, 11:10:21 PM
Kacie Jane, what is that picture?

Ni!
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 12, 2012, 05:20:04 PM
After seeing this thread linked in the RMcN thread, I clicked some of the links on Page 1 just for shits and giggles.

I think most of the more idiotic errors have been fixed, but sure enough, you can still find U.S. 2200 (http://g.co/maps/2qspd) in Illinois, 2 1/2 years after it was first posted here.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on May 12, 2012, 05:42:00 PM
Quote from: Scott5114 on May 11, 2012, 11:20:21 PM
Symbology in the British isles is much more standardized than in America. Every British map I've seen uses blue lines for the motorways, green lines for the A roads...
I think green is actually reserved for the "primary route network", which is the set of roads on which signs have a green background.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on May 12, 2012, 10:03:25 PM
Yes, they are supposed to form a grid of the primary A Road network across Great Britain.
Title: Re: Incorrect highways marked on Google Maps
Post by: connroadgeek on May 12, 2012, 10:17:17 PM
U.S. 6 in the Hartford CT area is mislabeled as "U.S. Route 6 in Nevada" and "U.S. Route 6 in Illinois."
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 12, 2012, 10:33:22 PM
Title: Re: Incorrect highways marked on Google Maps
Post by: ibagli on May 13, 2012, 12:55:13 AM
A township road in rural Ohio now has an Interstate 177 shield (http://maps.google.com/maps?hl=en&ll=40.25097,-83.601065&spn=0.033212,0.084543&sll=40.249726,-83.60939&sspn=0.033213,0.084543&t=m&z=14). (And as a companion to the US-xx in yy issues, much of US-62 in Ohio and probably elsewhere has been labeled "Brownfield Highway.")
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on May 13, 2012, 12:22:28 PM
Quote from: ibagli on May 13, 2012, 12:55:13 AM
A township road in rural Ohio now has an Interstate 177 shield (http://maps.google.com/maps?hl=en&ll=40.25097,-83.601065&spn=0.033212,0.084543&sll=40.249726,-83.60939&sspn=0.033213,0.084543&t=m&z=14). (And as a companion to the US-xx in yy issues, much of US-62 in Ohio and probably elsewhere has been labeled "Brownfield Highway.")
Not anymore. BTW, there was one time when US-62 was shown multiplexed with US-180 from El Paso to Niagara.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on May 19, 2012, 08:23:05 PM
US 20 at where it crosses I-81 in LaFayette, NY is marked "US 20 in Illinois" for some reason.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on May 19, 2012, 08:35:00 PM
:bangfuckinhead:
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on May 19, 2012, 10:00:46 PM
Quote from: roadman65 on May 19, 2012, 08:23:05 PM
US 20 at where it crosses I-81 in LaFayette, NY is marked "US 20 in Illinois" for some reason.

-

Quote from: Kacie Jane on May 03, 2012, 09:01:26 PM
The next person who brings up a "U.S. Route X in XXXX" error will be viciously and repeatedly slapped in the face with a fish.



lol. :)
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 20, 2012, 12:06:37 AM
Okay, seriously.  :banghead: :banghead: :banghead:

When I first posted my "response" to connroadgeek -- note my post was edited -- I just posted a picture of some salmon.  Then I went to the Google and cued up the fish slapping dance so that I could build up to it and use it later.  Then I realized, "No, that's stupid."  I prayed that it wouldn't be necessary, that people would be intelligent, and there wouldn't be the opportunity to "build up to it".  Now sadly, I've come to realize that this is the Internet, and the Internet is populated primarily by idiots (not unlike the real world).

In all seriousness, this is a discussion board.  You can not hope to jump into a middle of a discussion, repeat things we've already discussed (repeatedly), and expect us not to think you asshole or idiot.  The past conversation is here for you to read.  I realize that 17 pages is a lot -- maybe you don't have to read them all; on other sites where this issue has come up, the consensus seemed to be that you should familiarize yourself with at least the last 2 pages before you jump into a conversation.  Otherwise, you're just being rude.

So no more fish-slapping.  I have a very particular set of skills; skills I have acquired over a very long career. Skills that make me a nightmare for people like you. If you stop posting about U.S. X in XXXX errors now, that'll be the end of it. I will not look for you, I will not pursue you. But if you don't, I will look for you, I will find you, and I will kill you.

Okay, not really.  But seriously.  Everyone.  Stop.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on May 20, 2012, 01:36:13 AM
The point of me stating that US 20 in Illinois was in line with the topic!  Lafayette, NY is not in Illinois, obviously.  So therefore, it is a mistake.  However, if it did say US 20 in New York or whatever city, county, or jurisdiction that the place is in, it would not be a mistake and I, for sure, would have not posted it.

If you want to get upset over posts, why not get worried over someone against Google patronizing an establishment in Breezewood.  That makes no sense unless we took an oath to Boycot the town's businesses, which we did not.  Yet. it appears that one person stated that Google should not be at a business operating in Breezewood.  Another got mad and answered him and asking if the poster is mad at him cause he patronized Broezwood.

Some of us take things to seriously here.  As far as being rude, what about the other roadman66 posting  a thread wondering why there are missing gaps in the interstate numbering grid, but he did not ask it that way.  Instead he asked like an idiot  " How come there is no interstate 1,2, 3...32,33, 34 etc.?"  Then he used an icon  of the curious face instead of asking in detail which if he did not.  That was rude there.  If he had posted by asking the question in detail it would have not been rude.

Two other users made fun of his thread and the moderator stepped in there, and he stated that we should not poke fun and answer the damned question.  He was right in that matter, but roadman66 was rude in the way he asked his question and with that ethanman8675309 or whatever his name is bugging everyone already, it caused that reaction to it.

Nonetheless, I did not get angry myself and tell him off, but did later jump in and say that if no one pointed out his question sounding dumb he would asked about the letter routes in NY in the same fashion. 

Anyway, back to my point.  It was valid and it was in regards to what this post is about. Yes, I got anxious when I first joined and I quickly learned how to use this forum.  Granted, I still sometimes leave out parts of sentences that cause my point to get lost, but I responded back that I made a mistake.  If I offended anyone here, I am sorry, tut US 20 is not in the US state that the map there said it was at the place and that is incorrectly marked on the google map in my opinion!
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on May 20, 2012, 01:44:09 AM
(talking as a normal user and not an Admin here)
Well, I just have to admit that some people are getting annoyed about people mentioning that error again, and again.  In fact, US-20 was one of the first ones to be reported here (https://www.aaroads.com/forum/index.php?topic=2001.msg143777#msg143777).

So, I just decided to redo the fish video again to lighten up the thread.  Come on, that video is hilarious. :bigass:
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on May 20, 2012, 01:54:57 AM
Quote from: rickmastfan67 on May 20, 2012, 01:44:09 AM
(talking as a normal user and not an Admin here)
Well, I just have to admit that some people are getting annoyed about people mentioning that error again, and again.  In fact, US-20 was one of the first ones to be reported here (https://www.aaroads.com/forum/index.php?topic=2001.msg143777#msg143777).

So, I just decided to redo the fish video again to lighten up the thread.  Come on, that video is hilarious. :bigass:

Yeah it was, I am not mad at that or anyone.  I just wanted to know how that was a mistake.  I should have read it more carefully, before I posted.  I was on google before and saw it and thought it was a good idea.  My ignorance led me to believe that no one else would have posted that fact already ( you have to admit the odds are well against it). 

Kacie Jane's post caused a reaction to me and I did want her to know that I knew what we were talking about.  Sometimes, it is hard to go through the posts when it is over a page long.  Sometimes, you can read them and still miss one.  I have done that and then some others have as well.  I posted once something and later on another user posted the same as me.  I even posted the wrong word and NE 2 corrected me that 42 and 24 are NOT recipricals!  Now, I know that it is a word used for fractions being reversed between numerator and denominater.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on May 20, 2012, 10:37:32 AM
Quote from: roadman65 on May 20, 2012, 01:36:13 AM
The point of me stating that US 20 in Illinois was in line with the topic!  Lafayette, NY is not in Illinois, obviously.  So therefore, it is a mistake.  However, if it did say US 20 in New York or whatever city, county, or jurisdiction that the place is in, it would not be a mistake and I, for sure, would have not posted it.
That type of error happens so often in Google Maps these days that it just goes without saying.

QuoteIf you want to get upset over posts, why not get worried over someone against Google patronizing an establishment in Breezewood.  That makes no sense unless we took an oath to Boycot the town's businesses, which we did not.  Yet. it appears that one person stated that Google should not be at a business operating in Breezewood.  Another got mad and answered him and asking if the poster is mad at him cause he patronized Broezwood.
First, it was mostly sarcastic.  Second, you do realize that those businesses have been using their bought out politicians to prevent PA from fixing a major deficiency in the road infrastructure of the area (namely, I-70 traveling on surface streets; it's both annoying and unsafe for travelers, all because a few businesses don't want to adapt to changing surroundings)?  As a roadgeek, I can't say I like them very much.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 20, 2012, 05:33:10 PM
I apologize if I came off as too harsh, but I honestly think that after over a month -- four pages of discussion -- it was time for someone to explain exactly why people are getting annoyed and slapping each other with fishes.  And roadman65, I think you still somewhat missed my point.

I was calling you rude for one reason, and one reason only.  It was not for your poor grammar (which has vastly improved), or for posting off-topic (because it was certainly on-topic).  It was for reposting something that has already been mentioned multiple times on each of the past four pages.

Quote from: roadman65 on May 20, 2012, 01:54:57 AMMy ignorance led me to believe that no one else would have posted that fact already ( you have to admit the odds are well against it).

I'll admit that the odds would be well against it, IF that were the only place this error had occurred.  But it's not, and we've spent the past month talking about how several different U.S. highways are mislabeled for their entire length.

Quote from: roadman65 on May 20, 2012, 01:54:57 AM
Sometimes, it is hard to go through the posts when it is over a page long.  Sometimes, you can read them and still miss one.

Yes, and I acknowledged that.  I'm not saying that you have to read all 17 pages before you post in this thread.  If someone repeats something someone said once ten pages ago, that's fine.  But you didn't even have to go back two pages like I suggest... just four posts above you connroadgeek posted about U.S. 6 being mislabelled, and I responded with an amusing video of two men slapping each other with fish.  That should have been a clue that something is amiss.

Just read a page or two so that you know what you're responding to, that's all I ask.
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on May 21, 2012, 01:03:05 AM
If this thread causes so much indigestion, why don't the mods lock it?

I've seen topics locked for much less.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on May 21, 2012, 07:27:59 AM
It may be worth starting fresh on a new thread, provided that it's made clear U.S. X in XXXX mentions are banned from the get-go.  (Unless, God forbid, Google actually fixes them.)

Or I could just remove the stick from my ass, either way.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 21, 2012, 10:32:28 AM
I think it's in the Bible to remove the stick from your own ass before slapping your brother with a fish.  I'm not sure exactly, but Jesus might have used different words.

probably Aramaic ones....
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on May 21, 2012, 01:56:57 PM
At this point, posting "US X is labeled US X in <state>" is the same thing as saying water is wet.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on May 21, 2012, 02:55:00 PM
Quote from: deanej on May 21, 2012, 01:56:57 PM
At this point, posting "US X is labeled US X in <state>" is the same thing as saying water is wet.

I have added a news item mentioning it at the top of the forum. Hopefully this helps with the issue...
Title: Re: Incorrect highways marked on Google Maps
Post by: sr641 on May 21, 2012, 05:27:37 PM
US 41 in Indiana is labeled as US 41 in Illinois.
Title: Re: Incorrect highways marked on Google Maps
Post by: InterstateNG on May 21, 2012, 05:38:18 PM
Keep trollin trollin trollin.

Dipshit.
Title: Re: Incorrect highways marked on Google Maps
Post by: sr641 on May 21, 2012, 05:41:19 PM
Quote from: InterstateNG on May 21, 2012, 05:38:18 PM
Keep trollin trollin trollin.

Dipshit.

How am I trolling. I just put a google maP ERROR.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on May 21, 2012, 06:51:12 PM
Quote from: sr641 on May 21, 2012, 05:41:19 PM
Quote from: InterstateNG on May 21, 2012, 05:38:18 PM
Keep trollin trollin trollin.

Dipshit.

How am I trolling. I just put a google maP ERROR.

It has been specifically written in several posts above about this particular WELL-KNOWN error.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on May 21, 2012, 09:21:26 PM
Next person to post about US X in Y, unless it's explicitly sexual, will have his or her name changed to "sr642".
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on May 21, 2012, 09:50:29 PM
KY 2565 is the old routing of US 23 through Louisa between KY 32 in town and US 23 south of town.

Driving down US 23 yesterday, and tracking my trip with the EveryTrail app for iDevices (which uses Google maps) I noticed that 2565 is co-signed with 23 well south of Louisa into Johnson County.

Title: Re: Incorrect highways marked on Google Maps
Post by: Stephane Dumas on June 03, 2012, 06:29:59 PM
I already mentionned it in the past, Google maps corrected it once but they "recomissioned" again US-66.
http://goo.gl/maps/tcPV
Title: Re: Incorrect highways marked on Google Maps
Post by: kendancy66 on June 03, 2012, 06:53:22 PM
Quote from: Stephane Dumas on June 03, 2012, 06:29:59 PM
I already mentionned it in the past, Google maps corrected it once but they "recomissioned" again US-66.
http://goo.gl/maps/tcPV

That is a mistake I can live with.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 03, 2012, 06:54:19 PM
holy crap u.s. route 47 in alaska is in florida
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on June 03, 2012, 07:04:53 PM
zomg where
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 03, 2012, 07:49:51 PM
in quebec yo
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on June 03, 2012, 09:02:51 PM
I do not know if this was mentioned, but US 71 is listed on both old and new alignments north of Pineville, MO.  According to street view, the old road is signed as Business US 71.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on June 03, 2012, 09:11:45 PM
Don't know if that specific one has been mentioned, but it is a known error -- not one that's been discussed ad nauseum in this thread though.  Google has trouble with bannered routes, namely that they don't show banners at all.

My favorite example (that I'm sure I have posted in this thread before) is Niagara Falls, NY (http://goo.gl/maps/KmS1), where three consecutive streets are labelled US 62.  Ferry and Walnut (the one-way pair) are US 62 mainline, Pine should be US 62 Business.

My second favorite is anywhere where there's a surface street labelled with a red, white, and blue Interstate shield (that's supposed to be a green one).
Title: Re: Incorrect highways marked on Google Maps
Post by: Stephane Dumas on June 03, 2012, 09:31:18 PM
Quote from: kendancy66 on June 03, 2012, 06:53:22 PM
Quote from: Stephane Dumas on June 03, 2012, 06:29:59 PM
I already mentionned it in the past, Google maps corrected it once but they "recomissioned" again US-66.
http://goo.gl/maps/tcPV

That is a mistake I can live with.

Maybe, we should encourage them to make other good mistakes like marking WS-99, OR-99 and CA-99 as US-99. ;)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on June 04, 2012, 05:28:59 AM
Quote from: Kacie Jane on June 03, 2012, 09:11:45 PM
My second favorite is anywhere where there's a surface street labelled with a red, white, and blue Interstate shield (that's supposed to be a green one).

Google's been doing that from the start of having maps on their site.  It seems like they don't care about fixing it.
Title: Re: Incorrect highways marked on Google Maps
Post by: pianocello on June 04, 2012, 09:58:35 AM
That kind of business interstate signage isn't that big a deal, IMO, since you can easily tell it's not the mainline. What is a problem is when the business route is a freeway, like green 80 in CA or green 40 in NC.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on June 04, 2012, 11:37:38 AM
Or I-376 through Moon, PA.
Title: Re: Incorrect highways marked on Google Maps
Post by: BigMattFromTexas on June 04, 2012, 08:04:37 PM
I apparently live in Illinois... Haha. Pretty close.. :-D
I actually used to think Google Maps was superior to the others.. But this is just like... childish..
BigMatt
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on June 05, 2012, 04:54:29 PM
Brace yourself for a 4dus shield...US 1700 in Illinois? (https://maps.google.com/?ll=40.744136,-88.125114&spn=0.158928,0.308647&t=m&z=12)

(I know, it's very obviously county road 1700 along US Route 24, sumthinerother.)
Title: Re: Incorrect highways marked on Google Maps
Post by: Takumi on June 05, 2012, 05:11:05 PM
VA 162 is still shown on its pre-1994 routing when it still went through Williamsburg.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on June 05, 2012, 11:57:20 PM
Quote from: deanej on June 04, 2012, 11:37:38 AM
Or I-376 through Moon, PA.
I see nothing wrong with these at-grades. (https://maps.google.com/maps?q=Moon+Township,+Carnot-Moon,+PA&hl=en&ll=40.499895,-80.220355&spn=0.002321,0.005252&sll=37.0625,-95.677068&sspn=39.507908,86.044922&oq=moon,+&hnear=Carnot-Moon,+Moon,+Allegheny,+Pennsylvania&t=m&z=18)
Title: Re: Incorrect highways marked on Google Maps
Post by: Dr Frankenstein on June 08, 2012, 08:32:02 PM
NY 987F (Sprain Brook Parkway) is signed all of a sudden.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on June 08, 2012, 09:38:55 PM
Quote from: Dr Frankenstein on June 08, 2012, 08:32:02 PM
NY 987F (Sprain Brook Parkway) is signed all of a sudden.
Related but unrelated: NJDOT map is based on their GIS work (which I love, rather than contracting out to a mapping company), and that means every state highway has at least one shield. Including NY's reference routes.
Title: Re: Incorrect highways marked on Google Maps
Post by: mjb2002 on June 09, 2012, 03:34:13 PM
I just got a long standing error corrected on Thursday: In Aiken County, the name of US 78 on Google Maps kept showing up as Charleston Augusta Road when it is Charleston Highway between Windsor and Aiken.

I am going around the CSRA, using paper maps and Bing maps to assist me, in correcting the other naming errors in Earth.
Title: Re: Incorrect highways marked on Google Maps
Post by: tidecat on June 10, 2012, 08:32:25 PM
Not so much an error as it is a case of outdated information:

If you drag the little orange person to the 400 Block of W 2nd Street in Owensboro, Kentucky, the Executive Inn Rivermont can be seen in street view, even though Google's aerial map of Owensboro reflects that the hotel has been demolished.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on June 10, 2012, 09:49:06 PM
Quote from: tidecat on June 10, 2012, 08:32:25 PM
If you drag the little orange person

His name is Pegman.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on June 10, 2012, 10:29:29 PM
Quote from: vtk on June 10, 2012, 09:49:06 PM
Quote from: tidecat on June 10, 2012, 08:32:25 PM
If you drag the little orange person

His name is Pegman.

Nope, he's The Little Yellow Man. Because my boss insists.
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on June 13, 2012, 10:21:42 AM
8th Avenue in SF between Kirkham and Lawton is marked as a freeway. At least that's what I saw on my iPhone.

EDIT: 8th Avenue has been fixed, however the same bug has now hit 6th Avenue between Balboa and Cabrillo.
Title: Re: Incorrect highways marked on Google Maps
Post by: doorknob60 on June 19, 2012, 12:25:47 AM
There's a gap in US 97 south of Bend: https://maps.google.com/?ll=43.888446,-121.381202&spn=0.013408,0.033023&t=v&z=16
To be fair, they just recently (completed within the past few months) changed this section of highway from a 2 lane to a 4 lane divided freeway, and Google Maps seems to have leftovers from both on there :P

Also, zoom out a little and look what it calls the highway: "US Route 97 in California", though obviously this is in Oregon :P https://maps.google.com/?ll=43.909281,-121.368724&spn=0.107223,0.264187&t=v&z=13

Even worse, this also happens in Washington between Yakima and the Oregon border: https://maps.google.com/?ll=46.010147,-120.597878&spn=0.206734,0.528374&t=v&z=12


Okay apparently that is a very common bug and not worth pointing out, but the first one still counts.
Title: Re: Incorrect highways marked on Google Maps
Post by: Hot Rod Hootenanny on June 19, 2012, 03:12:39 PM
So who here is Blake Stephens?
http://www.contracostatimes.com/business/ci_20874345/hayward-man-makes-sure-details-google-maps-are-accurate (http://www.contracostatimes.com/business/ci_20874345/hayward-man-makes-sure-details-google-maps-are-accurate)
Title: Re: Incorrect highways marked on Google Maps
Post by: txstateends on June 20, 2012, 10:39:09 AM
Are any of the US # in SomeOtherPlace label errors any closer to going away yet?
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on June 21, 2012, 02:29:53 AM
Quote from: txstateends on June 20, 2012, 10:39:09 AM
Are any of the US # in SomeOtherPlace label errors any closer to going away yet?

Not that I'm aware of. lol.
Title: Re: Incorrect highways marked on Google Maps
Post by: rawmustard on June 21, 2012, 09:01:52 AM
Apparently LSD between McCormick Place and Jackson Park now runs over the water (https://maps.google.com/maps?hl=en&ll=41.82263,-87.590046&spn=0.091466,0.123081&sll=41.648288,-87.608585&sspn=0.091714,0.123081&t=m&z=13). :paranoid:
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on June 21, 2012, 12:37:10 PM
stray US-68 and state 68 shields at the junction of MN-60 and US-63.

http://goo.gl/maps/OEqV
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on June 21, 2012, 06:56:54 PM
Quote from: rickmastfan67 on June 21, 2012, 02:29:53 AM
Quote from: txstateends on June 20, 2012, 10:39:09 AM
Are any of the US # in SomeOtherPlace label errors any closer to going away yet?

Not that I'm aware of. lol.

I'm waiting for a "US 97 in California" to show up in British Columbia...

Fixed quote. (https://www.aaroads.com/forum/index.php?topic=4000.0) - rmf67
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 21, 2012, 07:18:29 PM
Also: Q-366: U-30 in Quebec?
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on June 23, 2012, 02:48:07 AM
Apparently US 10 has been resurrected in Montana:
http://goo.gl/maps/WFbd (http://goo.gl/maps/WFbd)
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on June 23, 2012, 07:10:33 AM
The A487 has recently moved to a new bypass of Porthmadog, with the old road called A4971.

Guess what google did...
http://goo.gl/maps/h8iu


...yes they labelled the whole A487 as A4971 (except the Porthmadog bypass, of course), though parts are also labelled correctly as A487.
Title: Re: Incorrect highways marked on Google Maps
Post by: sandwalk on June 23, 2012, 11:52:54 AM
Quote from: rawmustard on June 21, 2012, 09:01:52 AM
Apparently LSD between McCormick Place and Jackson Park now runs over the water (https://maps.google.com/maps?hl=en&ll=41.82263,-87.590046&spn=0.091466,0.123081&sll=41.648288,-87.608585&sspn=0.091714,0.123081&t=m&z=13). :paranoid:

Wow.  I LOLed when I look at this!
Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on July 02, 2012, 09:32:08 AM
I really wished that Google Maps included some sort of graphic to label bannered US routes.  No, US 72 doesn't go through both Athens, AL and Decatur, AL (http://goo.gl/maps/Yd5W). Even if it takes going at it Arkansas-style and labeling the business route US xxB or Tennessee-style with US xxA for alternate routes (e.g. US 41A in Tennessee (https://maps.google.com/?ll=35.251227,-86.020203&spn=0.462604,0.891953&t=h&z=11)).
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on July 02, 2012, 10:19:46 AM
Sheesh, where to begin?

First of all, FYI: there's a "freeway" priority (line type), and an "expressway" priority that are both (stupidly) shown the same color. So "freeways" with intersections (usually) aren't.

Expressways (freeways) shown yellow:

-http://maps.google.com/?ll=40.112624,-74.88131&spn=0.010076,0.013797&t=m&z=16 (http://maps.google.com/?ll=40.112624,-74.88131&spn=0.010076,0.013797&t=m&z=16) (there's a "freeway ends" sign on these "ramps," so yeah)
-http://maps.google.com/?ll=39.897687,-75.199571&spn=0.020216,0.027595&t=m&z=15 (http://maps.google.com/?ll=39.897687,-75.199571&spn=0.020216,0.027595&t=m&z=15) (the whole Platt Bridge up to 26th St.)
-http://maps.google.com/?ll=40.105846,-75.344367&spn=0.020154,0.027595&t=m&z=15 (http://maps.google.com/?ll=40.105846,-75.344367&spn=0.020154,0.027595&t=m&z=15) (202 from Dekalb St. to Main St.)
-http://maps.google.com/?ll=39.956267,-76.763191&spn=0.040396,0.055189&t=m&z=14 (http://maps.google.com/?ll=39.956267,-76.763191&spn=0.040396,0.055189&t=m&z=14) (30 from 462 to Kenneth Rd; the sad part is that they were right about it for a while)
-http://maps.google.com/?ll=39.931393,-76.691608&spn=0.040411,0.055189&t=m&z=14 (http://maps.google.com/?ll=39.931393,-76.691608&spn=0.040411,0.055189&t=m&z=14) (Bus. 83 from George St. to 83)
-http://maps.google.com/?ll=40.257521,-76.888504&spn=0.040218,0.055189&t=m&z=14 (http://maps.google.com/?ll=40.257521,-76.888504&spn=0.040218,0.055189&t=m&z=14) (the Taylor Bridge from 21st St. to Front St.)
-http://maps.google.com/?ll=40.255343,-76.810634&spn=0.010055,0.013797&t=m&z=16 (http://maps.google.com/?ll=40.255343,-76.810634&spn=0.010055,0.013797&t=m&z=16) (Eisen. Blvd/322 from Paxton St. up to 83)
-http://maps.google.com/?ll=40.262695,-76.691523&spn=0.040215,0.055189&t=m&z=14 (http://maps.google.com/?ll=40.262695,-76.691523&spn=0.040215,0.055189&t=m&z=14) (part 322, part 422 from Bridge Rd. to Lucy Ave.)

More soon... ;)

(BTW, if you think Google is bad, wait'll you see a map at the Independence Mall visitors' center in Philly! It makes you go :banghead:,  :-D, and :eyebrow: all at the same time!)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 02, 2012, 11:51:54 AM
I don't see the problem with many of those, and the others are arguably borderline.

In particular, I see nothing at all wrong with I-95 at PA 413 and the Platt Bridge.
Title: Re: Incorrect highways marked on Google Maps
Post by: mukade on July 02, 2012, 11:02:02 PM
When did Google Maps fix the problem of the US highways in Illinois, Nebraska, Idaho, etc. from other states? I don't see these in Indiana at least.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 03, 2012, 08:55:48 AM
Holy crap, I think the master programmers at Google finally fixed it.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on July 04, 2012, 01:03:49 AM
Title: Re: Incorrect highways marked on Google Maps
Post by: mcdonaat on July 04, 2012, 01:10:45 AM
How about this... Google Maps can take the old, decomissioned routes, and turn them into an alternate color US shield, to designate the roads as historic. I would even suggest the California cutout style for historic routes, since CalTrans pretty much wiped the idea of a U.S. route off the map. It would be awesome for people following the old routes, and those who are looking for a good road won't be sent off the Interstate in search of US 66 or something.
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on July 04, 2012, 06:46:55 AM
Quote from: mcdonaat on July 04, 2012, 01:10:45 AM
How about this... Google Maps can take the old, decomissioned routes, and turn them into an alternate color US shield, to designate the roads as historic. I would even suggest the California cutout style for historic routes, since CalTrans pretty much wiped the idea of a U.S. route off the map. It would be awesome for people following the old routes, and those who are looking for a good road won't be sent off the Interstate in search of US 66 or something.

That would probably confuse the hell out of the masses, who really don't care what route US 270 used to take before the interstate was built. The only old highway most people give a thought to tracing is US 66...I imagine most people don't even realize there ARE other old highways.

Besides, how would you decide what the One True Routing of the old highway was? Or would you mark all possible old alignments (boy, talk about confusing). What would you do if a bridge was taken out on the old alignment, or if it was discontinuous because the freeway took over part of it?

The more I think about it the more I think a specialized Roadgeek Atlas is a great idea...but it probably wouldn't be marketable. It'd have to be a not-for-profit labor-of-love thing.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on July 05, 2012, 04:27:46 AM
US 10 in Fargo, ND is listed as I-94.   I do not know if someone else brought that up already or not.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on July 06, 2012, 09:42:35 AM
Quote from: Scott5114 on July 04, 2012, 06:46:55 AM
The more I think about it the more I think a specialized Roadgeek Atlas is a great idea...but it probably wouldn't be marketable. It'd have to be a not-for-profit labor-of-love thing.

Sort of an Open Street Map, although in some cases, perhaps "Closed Street Map" would be an apt description. :P
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on July 11, 2012, 08:32:59 PM
Quote from: roadman65 on July 05, 2012, 04:27:46 AM
US 10 in Fargo, ND is listed as I-94.   I do not know if someone else brought that up already or not.
Business loop? That happens.
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on July 13, 2012, 02:29:16 PM
I don't know how to explain how this happened.

http://goo.gl/maps/g3MF (http://goo.gl/maps/g3MF)
http://goo.gl/maps/fDXY (http://goo.gl/maps/fDXY)
Title: Re: Incorrect highways marked on Google Maps
Post by: 707 on July 16, 2012, 08:31:58 PM
I guess this is considered "incorrect", but it's funny at the same time. US 66 is shown as an active highway along many areas of I-40, but the shields do not appear on actual segments of old US 66, nor does US 66 officially exist anymore. I'm guessing Google did this to let people know where US 66 was if one wants to take a road trip.
Title: Re: Incorrect highways marked on Google Maps
Post by: txstateends on July 18, 2012, 12:09:32 PM
Quote from: HighwayMaster on July 13, 2012, 02:29:16 PM
I don't know how to explain how this happened.

http://goo.gl/maps/g3MF (http://goo.gl/maps/g3MF)
http://goo.gl/maps/fDXY (http://goo.gl/maps/fDXY)

I've been noticing 'Hwy 77' and 'Rte 77' along with the 77 shields on the Dallas-area maps for weeks now.  If there is the possibility of a shield graphic for a road, why would you also want to have multiple textual versions of the same labeling??  >ugh<, overkill!!
Title: Re: Incorrect highways marked on Google Maps
Post by: CL on July 25, 2012, 11:04:16 AM
The entirety of US-89 has been demoted to state route status. Yay.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on July 25, 2012, 03:09:02 PM
Quote from: CL on July 25, 2012, 11:04:16 AM
The entirety of US-89 has been demoted to state route status. Yay.

Maybe someone read one of the threads on here saying how there's no such thing as a federal route, and decided to change US-89 to a state route to accurately reflect that.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on August 07, 2012, 03:10:12 PM
Apparently now Business Interstate 83 in York has been redesignated Interstate 83B. :eyebrow:

When I used Map Maker (I've since learned that they never listen any more that way than through Report a Problem.), I noticed that a business tag in the route number changes the form of number, but not the shield graphic. This may or may not be Bus. 83B or just 83B.

Why they can't just recolor the shield green is beyond me...
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on August 07, 2012, 09:02:33 PM
I guess showing business routes with a "B" suffix is better than not showing them at all, but the best solution would be to put "BUS." above the shield. You know, like every other map ever.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 07, 2012, 09:58:14 PM
Map Maker is a joke.  OSM's editing software is 10x easier to use.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on August 09, 2012, 10:06:21 AM
I know, I use it. Now all OSM needs is satellite view outside of the editor... :nod:
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on August 09, 2012, 01:25:48 PM
I wouldn't hold your breath. Satellite/aerial data is mostly copyrighted, and OSM aims to build a map free of any copyright encumbrances. They might be able to get public domain USGS data but it probably wouldn't be as high quality as Google or Bing's. The satellite map in the editor is used under license from Bing, but they probably want to keep that restricted to the editors. The general public can look at it on their site.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on August 13, 2012, 03:40:41 PM
http://maps.google.com/?ll=40.450343,-78.567352&spn=0.15179,0.338173&t=m&z=12 (http://maps.google.com/?ll=40.450343,-78.567352&spn=0.15179,0.338173&t=m&z=12)

Google has hit an all-time low at problem-fixing. For a long time, US 22 was entirely labeled as an "expressway," from I-376 all the way to where it becomes a freeway. (Who knows, it may have been internally an expressway all the way to I-99!) They have since "fixed" this and labeled the whole thing yellow (national highway?), with the occasional patch of expressway. Not to mention that the I-99 connector that was incorrectly entirely shown as a ramp is still shown as freeway-colored ramps. :banghead:

Also, they added but didn't remove at the former south end of the PA 88 expressway in Brownsville. :eyebrow:

http://maps.google.com/?ll=40.018265,-79.940429&spn=0.009548,0.021136&t=m&z=16

(As if their setup made any sense even when it wasn't extended yet...)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on August 14, 2012, 04:08:58 PM
That seems to happen somewhat often; I blame the poor editing interface.  They usually get cleaned up, but not always.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on August 15, 2012, 10:06:22 AM
Quote from: deanej on August 14, 2012, 04:08:58 PM
That seems to happen somewhat often

Yeah, whenever they base something on a construction satellite view, it never ends well. Just look at WV 43 at I-68.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on August 21, 2012, 11:05:10 AM
Large parts of US 209 in PA are labeled as Interstate 209. :banghead:

http://maps.google.com/?ll=40.723844,-76.002731&spn=0.302341,0.676346&t=m&z=11 (http://maps.google.com/?ll=40.723844,-76.002731&spn=0.302341,0.676346&t=m&z=11)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 22, 2012, 07:33:31 AM
Quote from: Roadsguy on August 21, 2012, 11:05:10 AM
Large parts of US 209 in PA are labeled as Interstate 209. :banghead:

http://maps.google.com/?ll=40.723844,-76.002731&spn=0.302341,0.676346&t=m&z=11 (http://maps.google.com/?ll=40.723844,-76.002731&spn=0.302341,0.676346&t=m&z=11)

Isn't the first time that type of error has popped up in Google land.  At one time, the entire length of US-136 was re-branded as I-136.  It was talked about somewhere in this thread if you want to "go back in time" for a bit Roadsguy. ;)
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on August 22, 2012, 10:55:53 AM
I read the whole thread once, before I joined. These errors make up a good chunk of what I laugh at. :) (Not really...)
Title: Re: Incorrect highways marked on Google Maps
Post by: sandwalk on August 27, 2012, 01:36:37 PM
Not a highway, but apparently Lake Erie is now called 'Quarry.'

https://maps.google.com/maps?q=lake+erie&hl=en&ll=41.892055,-81.164246&spn=1.245117,1.766052&safe=off&hnear=Lake+Erie&gl=us&t=m&z=9
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on August 29, 2012, 08:47:11 PM
US-41 in Miami is shown to head north for several blocks on US-1 after its SW 7th St terminus.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 30, 2012, 05:48:14 AM
Quote from: agentsteel53 on August 29, 2012, 08:47:11 PM
US-41 in Miami is shown to head north for several blocks on US-1 after its SW 7th St terminus.

It may not be posted in the field, but Google has it correct here. :wow:  FDOT still considers US-41 heading up US-1 to FL-A1A to continue over to the beaches.  Just look at their GIS files.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on August 30, 2012, 12:37:40 PM
quick, somebody alert Dale Sanderson!
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on August 30, 2012, 01:12:29 PM
Dale goes mostly by signage, which consistently ends US 41 at US 1.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on August 31, 2012, 07:19:00 PM
Signage ends CR 529 twice in NJ as you head north. It's not 100% reliable. Then again, states aren't 100% reliable either - just ask the omitted NJ 62 and included NJ 524 back in earlier Straight Line Diagrams.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on September 01, 2012, 08:07:37 PM
Not really an error, but they show US 1 on the Overseas Highway in Florida multiplexing FL 5, even all the way up to Jacksonville. This is technically correct, since 5 is the secret number for US 1 through there.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on September 11, 2012, 01:03:12 AM
SR 5 is the "secret number" for US 1 throughout most of (but not all of) Florida. It is indeed SR5/US1 throughout The Keys.

A notable exception is from Lantana Boulevard to Southern Boulevard in Palm Beach County; there's a defacto FL 5 (Olive Boulevard) and a separate US 1 (Dixie Highway) which is secretly FL 805, as they run parallel to each other.

(Example (https://maps.google.com/maps?q=26.582778,-80.0575&ll=26.616692,-80.052395&spn=0.020411,0.077162&t=h&z=14&layer=c&cbll=26.616718,-80.05239&panoid=gzFDkChaj2ppU0_aMlYPaw&cbp=11,0.19,,0,-0.66).)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on September 11, 2012, 01:46:08 AM
Hey mods, you can remove this from the news at the top of the forum:
QuoteBefore posting about the Google Maps "U.S. XX in XXXX" state error, please note that it is already common knowledge among board members.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on September 11, 2012, 01:57:08 AM
Quote from: NE2 on September 11, 2012, 01:46:08 AM
Hey mods, you can remove this from the news at the top of the forum:
QuoteBefore posting about the Google Maps "U.S. XX in XXXX" state error, please note that it is already common knowledge among board members.

Done.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on September 11, 2012, 04:43:14 PM
What the heck is with highway segments simply disappearing from Google Maps??  How does this happen?

A section of recently constructed freeway in Saltillo has apparently vanished:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fsaltillo.png&hash=289632506e256cde2ebcf35a376c08f0074e904e)
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on September 11, 2012, 04:48:36 PM
that looks like there is an interchange there.

was the new interchange in place before the vanishing?

if not, then I suspect that the folks at google are busy replacing the data, and apparently deleted the old interchange before putting in the new one.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on September 11, 2012, 05:04:29 PM
Yes, the whole stretch through there was upgraded to a freeway within the last year or so.  It was a fully opened freeway when I drove it in June, and had been long enough for me to be able to watch someone else's YouTube of it in advance of going down there.

But replacing data doesn't explain other examples I've seen where a totally rural stretch of highway simply disappears for a while.  These occurrences make Get directions difficult.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on September 11, 2012, 08:47:57 PM
I've run into situations where I load a city block, and I see restaurants pop into view and then disappear. I feel like there are two layers of data getting loaded right now.
Title: Re: Incorrect highways marked on Google Maps
Post by: Ian on September 11, 2012, 08:56:18 PM
Looks like I-6 exists in Maine now...
http://goo.gl/maps/nBlLH
Title: Re: Incorrect highways marked on Google Maps
Post by: algorerhythms on September 15, 2012, 12:53:13 PM
It appears as though Oklahoma has a new U.S. highway: US 65, which runs concurrent with US 62 between Kickapoo Casino east of OKC (http://goo.gl/maps/c9jXs) and Newcastle Gaming Center south of OKC (http://goo.gl/maps/ybwZj).
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on September 15, 2012, 09:46:36 PM
Penrith, NSW
http://goo.gl/maps/zw0Fq (http://goo.gl/maps/zw0Fq)
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on September 15, 2012, 10:05:52 PM
Quote from: national highway 1 on September 15, 2012, 09:46:36 PM
Penrith, NSW
http://goo.gl/maps/zw0Fq (http://goo.gl/maps/zw0Fq)

Very weird.  I just saw a street name at work called Penrith today, and wondered where the name came from.  It was in Arkansas.
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on September 16, 2012, 03:22:09 AM
Bizarrely, you can still route directions over the nonexistent bridge. (http://goo.gl/maps/kS2Pd)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on September 16, 2012, 12:03:13 PM
The funniest thing about that is - "Is something missing?  Edit in Google Map Maker".

I guess Google Map Maker can now make changes to how the roads are in RL.  Quite an unorthodox solution to all the spam/inaccurate map edits.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on September 17, 2012, 03:33:04 AM
Quote from: kphoger on September 15, 2012, 10:05:52 PM
Quote from: national highway 1 on September 15, 2012, 09:46:36 PM
Penrith, NSW
http://goo.gl/maps/zw0Fq (http://goo.gl/maps/zw0Fq)

Very weird.  I just saw a street name at work called Penrith today, and wondered where the name came from.  It was in Arkansas.
Actually the original Penrith came from a place in Cumbria in the UK:
http://goo.gl/maps/nME0h (http://goo.gl/maps/nME0h)
Title: Re: Incorrect highways marked on Google Maps
Post by: Super Mateo on September 17, 2012, 07:01:39 PM
It looks like the majority of US 52 isn't labeled in northern IL.  The only mentions of it are in Dixon and Bourbonnais.
Title: Re: Incorrect highways marked on Google Maps
Post by: mukade on September 17, 2012, 07:11:23 PM
It loses its way in Indiana west of Lafayette and stays lost in Illinois. It also disappears from Indianapolis to Cincinnati. Around Indianapolis, it has the wrong routing around I-465, but that is nothing new.
Title: Re: Incorrect highways marked on Google Maps
Post by: doorknob60 on September 18, 2012, 01:35:36 AM
Minor error, but still an error. Ever since ITD finished the Karcher interchange (I-84 at Midland Blvd, Exit 33) in Nampa (been built since late 2006 from what I can tell, almost 6 years), SH-55 has been rerouted from Northside/Nampa Blvd and Nampa-Caldwell Blvd to the much more direct access on Midland. Google Maps still shows the old alignment. https://maps.google.com/maps?hl=en&ll=43.598792,-116.585712&spn=0.03456,0.078964&t=m&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on September 18, 2012, 02:01:02 PM
Quote from: national highway 1 on September 17, 2012, 03:33:04 AM
Quote from: kphoger on September 15, 2012, 10:05:52 PM
Quote from: national highway 1 on September 15, 2012, 09:46:36 PM
Penrith, NSW
http://goo.gl/maps/zw0Fq (http://goo.gl/maps/zw0Fq)

Very weird.  I just saw a street name at work called Penrith today, and wondered where the name came from.  It was in Arkansas.
Actually the original Penrith came from a place in Cumbria in the UK:
http://goo.gl/maps/nME0h (http://goo.gl/maps/nME0h)

That makes sense.  Many of the street names in that area of Arkansas come from Britain.
Title: 880 in a specific part of Fremont appears to be southbound only
Post by: bootmii on September 18, 2012, 04:02:22 PM
The NB lane disappears for a little bit around here:

http://goo.gl/maps/bfL3U
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on September 18, 2012, 04:44:24 PM
This is becoming the next "Route X in Y state that's really in Z state" error.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on September 18, 2012, 06:55:06 PM
If this counts, apparently, Street View no longer recognizes Ohio or Alaska  :pan:, as seen in this example (look in the upper left, specifically in the box with "Interstate 280"): http://goo.gl/maps/jyckm (http://goo.gl/maps/jyckm)
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on October 08, 2012, 05:20:54 PM
Google Maps is despicable
Title: Re: Incorrect highways marked on Google Maps
Post by: SSOWorld on October 08, 2012, 05:36:18 PM
Quote from: Roadgeek2500 on October 08, 2012, 05:20:54 PM
Google Maps is despicable
Care to elaborate?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 08, 2012, 05:42:19 PM
Probably paid by Apple to come here and post that.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on October 08, 2012, 06:07:47 PM
Quote from: Roadgeek2500 on October 08, 2012, 05:20:54 PM
Google Maps is despicable

great first post.  go back to hiding under your bridge.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on October 08, 2012, 07:13:37 PM
Quote from: agentsteel53 on October 08, 2012, 06:07:47 PM
Quote from: Roadgeek2500 on October 08, 2012, 05:20:54 PM
Google Maps is despicable

great first post.  go back to hiding under your bridge.
but Google Maps shows the bridge as out
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on October 08, 2012, 09:26:12 PM
Quote from: Steve on October 08, 2012, 07:13:37 PM
Quote from: agentsteel53 on October 08, 2012, 06:07:47 PM
Quote from: Roadgeek2500 on October 08, 2012, 05:20:54 PM
Google Maps is despicable

great first post.  go back to hiding under your bridge.
but Google Maps shows the bridge as out
Still better than Apple.  Wouldn't want the bridge to melt on top of you.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on October 08, 2012, 09:37:03 PM
There are some situations with Google Maps that do tend to piss me off sometimes. For one, google map maker gives you basically no freedom. As a roadgeek it gets annoying, cause you can't make an edit finalized into the actual maps.google.com until it goes through a whole approval process. For example, I tried to make this segment of US 209 http://goo.gl/maps/VYAAG a National Highway instead of an Expressway, as there is a signalized intersection right there. The response given is simply along the lines of 'this does not meet our guidelines, undo the edit'
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on October 08, 2012, 09:53:24 PM
Quote from: NE2 on October 08, 2012, 05:42:19 PM
Probably paid by Apple to come here and post that.

Can't remember the identities of those involved, but once upon a time, someone in M.T.R. accused someone else of being paid by the Heritage Foundation to post there.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 08, 2012, 10:41:18 PM
Quote from: hbelkins on October 08, 2012, 09:53:24 PM
Quote from: NE2 on October 08, 2012, 05:42:19 PM
Probably paid by Apple to come here and post that.

Can't remember the identities of those involved, but once upon a time, someone in M.T.R. accused someone else of being paid by the Heritage Foundation to post there.

Can't remember the identities of those involved, but once upon a time, someone in M.T.R. accused pooing of being uncool.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on October 09, 2012, 09:14:39 AM
Quote from: Some_Person on October 08, 2012, 09:37:03 PM
National Highway instead of an Expressway, as there is a signalized intersection right there

After my fairly short experience with Map Maker, I learned that Google follows the non-Northeastern US in having expressways called freeways, and expressways being pretty much the same thing, but with the occasional intersection (i.e. non-freeway US 15 from Frederick, MD to Harrisburg, PA, except for around Dillsburg) but no driveways.

So yeah, it's technically correct. The dumb part is that Google has no separate line color for freeways and expressways. :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on October 09, 2012, 06:29:30 PM
Quote from: Roadsguy on October 09, 2012, 09:14:39 AM
Quote from: Some_Person on October 08, 2012, 09:37:03 PM
National Highway instead of an Expressway, as there is a signalized intersection right there
The dumb part is that Google has no separate line color for freeways and expressways. :banghead:
I agree, same with any other major road, as you can have US Route 1 outside of Raleigh be colored yellow be looking like this http://goo.gl/maps/AC3gq, while you can also have a road like this http://goo.gl/maps/dGtBg sharing the same color.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on October 09, 2012, 07:04:56 PM
The yellow is Minor Artery, Major Artery, or National Highway.

Not as important a distinction as freeway/not-freeway is.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on October 09, 2012, 07:25:05 PM
Quote from: Roadsguy on October 09, 2012, 07:04:56 PM
The yellow is Minor Artery, Major Artery, or National Highway.

Not as important a distinction as freeway/not-freeway is.
I'm aware, and although the example I posted is a rather big distinction as well, you do have a point. Which leads me to wonder how and why there are random examples of this in some cities: http://goo.gl/maps/2rFl3
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 09, 2012, 07:40:42 PM
Someone makes an error, someone else corrects it and misses a piece. Happens in OSM too, but there are no hoops to jump through before correcting it.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on October 10, 2012, 12:52:58 PM
Well... I'm only 12

EDIT and I know what your all talking about
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on October 10, 2012, 09:14:59 PM
Quote from: Roadgeek2500 on October 10, 2012, 12:52:58 PM
Well... I'm only 12

The process goes like this:

1) Make a statement
2) Give a reason (or reasons) to back up your statement,
3) Include a real-life example (or examples) with some factual proof.

Make sure it's all wrapped up in one post, and that's called communicating via a message board on the Internet.

If you can't do that, at least be witty and/or ironic about it (don't take lessons form me in that respect). Ta da!
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on October 11, 2012, 12:46:28 AM
Also: Children under age 13 should have their parents monitoring their usage. It's common sense from a parenting perspective.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on October 11, 2012, 04:46:23 PM
Thanks for the advice. Oh and Steve, big fan. Now back on topic
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on October 12, 2012, 05:37:06 PM
It appears that not only U.S. 27 is now back in Michigan after 10 years, it appears it's now again on it's pre-I-69 alignment:
http://goo.gl/maps/ELVGj (http://goo.gl/maps/ELVGj)
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on October 12, 2012, 08:49:57 PM
Quote from: MDOTFanFB on October 12, 2012, 05:37:06 PM
It appears that not only U.S. 27 is now back in Michigan after 10 years, it appears it's now again on it's pre-I-69 alignment:
http://goo.gl/maps/ELVGj (http://goo.gl/maps/ELVGj)

I love how they simultaneously have it labeled as US 27 and Old US 27.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on October 12, 2012, 09:07:08 PM
Quote from: Central Avenue on October 12, 2012, 08:49:57 PM
Quote from: MDOTFanFB on October 12, 2012, 05:37:06 PM
It appears that not only U.S. 27 is now back in Michigan after 10 years, it appears it's now again on it's pre-I-69 alignment:
http://goo.gl/maps/ELVGj (http://goo.gl/maps/ELVGj)

I love how they simultaneously have it labeled as US 27 and Old US 27.

It looks like I've discovered another U.S. 27 in Michigan, this time in Alma: http://goo.gl/maps/VTbPl (http://goo.gl/maps/VTbPl)

Could this be a temporary hurrah for people who missed U.S. 27?
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on October 12, 2012, 09:34:05 PM
U.S. 27.  The poor man's Route 66.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on October 13, 2012, 07:38:02 PM
https://maps.google.com/maps?q=Century+City,+Los+Angeles,+CA&hl=en&ll=34.040498,-118.454504&spn=0.018101,0.042272&sll=27.698638,-83.804601&sspn=9.892242,21.643066&oq=century+ci&t=h&hnear=Century+City,+Los+Angeles,+California&z=15

Speaking of US 66, is it making a comeback? 
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on October 13, 2012, 07:55:03 PM
Quote from: roadman65 on October 13, 2012, 07:38:02 PM
https://maps.google.com/maps?q=Century+City,+Los+Angeles,+CA&hl=en&ll=34.040498,-118.454504&spn=0.018101,0.042272&sll=27.698638,-83.804601&sspn=9.892242,21.643066&oq=century+ci&t=h&hnear=Century+City,+Los+Angeles,+California&z=15

Speaking of US 66, is it making a comeback? 

Quote from: 707 on July 16, 2012, 08:31:58 PM
I guess this is considered "incorrect", but it's funny at the same time. US 66 is shown as an active highway along many areas of I-40, but the shields do not appear on actual segments of old US 66, nor does US 66 officially exist anymore. I'm guessing Google did this to let people know where US 66 was if one wants to take a road trip.

Quote from: Stephane Dumas on June 03, 2012, 06:29:59 PM
I already mentionned it in the past, Google maps corrected it once but they "recomissioned" again US-66.
http://goo.gl/maps/tcPV

Quote from: corco on May 03, 2012, 10:32:04 PM
US 66 has been reinstated!

Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on October 13, 2012, 08:00:11 PM
So US 66 is a double mistake?  You are right it is funny, considering that part of the old Mother Road is far off from being a business route to an interstate it follows like in the other states.  Also, I believe this is the first part of US 66 to be truncated as old 1970 maps show it ending in Pasedena.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 13, 2012, 08:11:23 PM
haha funny
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on October 13, 2012, 08:21:50 PM
Here is one even funnier. I-35E in Pearsall, TX.
https://maps.google.com/maps?q=Laredo,+TX&hl=en&ll=28.887819,-99.098654&spn=0.038552,0.084543&sll=27.698638,-83.804601&sspn=9.892242,21.643066&oq=Lar&hnear=Laredo,+Webb,+Texas&t=m&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 13, 2012, 08:28:08 PM
OH MY GOD SO FUNNY
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on October 13, 2012, 08:29:33 PM
Quote from: kphoger on January 17, 2012, 02:49:01 PM
Apparently there is a Business I-35E in Pearsall, Texas–but, to be fair, I-35E is only 266 miles away.   :eyebrow:
http://maps.google.com/maps?hl=en&ll=28.898189,-99.081917&spn=0.110911,0.153637&t=p&z=13&vpsrc=6 (http://maps.google.com/maps?hl=en&ll=28.898189,-99.081917&spn=0.110911,0.153637&t=p&z=13&vpsrc=6)

Quote from: NE2 on January 17, 2012, 03:39:37 PM
That's TXDOT's method of identifying their business routes. Here's 35-H (and SH 46-C):
(//www.aaroads.com/shields/img/TX/TX19790351i1.jpg) (//www.aaroads.com/shields/show.php?image=TX19790351)
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on October 14, 2012, 08:49:27 AM
I even mentioned that very thing farther upthread.  (too lazy to look now)
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on October 14, 2012, 11:18:19 AM
kphoger, look closely at my last post (i.e. the one where I point that out to roadman by quoting your post from January).
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on October 14, 2012, 12:02:26 PM
Quote from: kphoger on October 14, 2012, 08:49:27 AM
I even mentioned that very thing farther upthread.  (too lazy to look now)
Hey at 22 pages it is very easy to miss something.  Only NE2's posts I do not miss seeing all of his posts, because  of the fact  that he needs so much attention  from society that he makes his posts stand out above all the rest.  It could be as many pages as the dictionary, and you could not miss any of what he has to say.

Nonetheless, who ever posted it, no matter how many times, it is still interesting to see that kind of error.   I have seen mainline I-94 signed in Bismark along its business routing, but this one with an "E" suffix is super strange occurrence.


Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on October 14, 2012, 01:57:42 PM
Quote from: mukade on July 02, 2012, 11:02:02 PM
When did Google Maps fix the problem of the US highways in Illinois, Nebraska, Idaho, etc. from other states? I don't see these in Indiana at least.

Not quite, since U.S. 50 west of Lake Tahoe, CA, is (still) listed as, ironically enough, "U.S. Route 50 in California"!  :pan:  :spin:
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on October 15, 2012, 12:37:45 PM
Quote from: Kacie Jane on October 14, 2012, 11:18:19 AM
kphoger, look closely at my last post (i.e. the one where I point that out to roadman by quoting your post from January).

Wow, I didn't realize I was that lazy!   :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: pianocello on October 15, 2012, 08:58:43 PM
Quote from: MDOTFanFB on October 12, 2012, 09:07:08 PM
It looks like I've discovered another U.S. 27 in Michigan, this time in Alma: http://goo.gl/maps/VTbPl (http://goo.gl/maps/VTbPl)
Interesting. I saw US-27 in Apple maps as well, except it was in Mt. Pleasant.

Quote
Could this be a temporary hurrah for people who missed U.S. 27?
:clap:
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on October 28, 2012, 07:14:27 AM
In Lewes, DE there is a section of US 9 that is marked as 'Road 23.'  Then it also shows the part of King's Highway that deviates from US 9 and leads into Downtown Lewes as 'US 9.' 

Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on October 29, 2012, 03:38:30 PM
The Ben Franklin Bridge in Philly is now not shown as a freeway. :banghead: :banghead:

I have officially given up on Google Maps. (Now how do I link to a point on Bing?)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 29, 2012, 03:51:47 PM
Quote from: Roadsguy on October 29, 2012, 03:38:30 PM
The Ben Franklin Bridge in Philly is now not shown as a freeway. :banghead: :banghead:
It's borderline. ftp://ftp.dot.state.pa.us/public/pdf/BPR_pdf_files/Maps/Statewide/OTM/2012/web_philly_enlg.pdf
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on October 29, 2012, 07:00:27 PM
I think the bridge itself can be called a freeway, now that they put in the movable barrier - I wouldn't have said that pre-barrier. But it definitely ends on the PA side either way, so between there and the tollbooth is an academic exercise.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on October 31, 2012, 11:23:03 AM
Quote from: MDOTFanFB on September 18, 2012, 06:55:06 PM
If this counts, apparently, Street View no longer recognizes Ohio or Alaska  :pan:, as seen in this example (look in the upper left, specifically in the box with "Interstate 280"): http://goo.gl/maps/jyckm (http://goo.gl/maps/jyckm)

Well, it looks like Ohio and Alaska are no longer the only states that are omitted on Street View addresses (a.k.a. the "(address) (street name) (suffix), (city), United States" bug)!  :pan:

New York State no longer exists... (http://goo.gl/maps/1bfZY)

Neither does Illinois... (http://goo.gl/maps/2XuGe)

Nor North Carolina... (http://goo.gl/maps/66a0Z)

Not even Kentucky exists any more... (http://goo.gl/maps/idzyt)

Nor Missouri... (http://goo.gl/maps/ipjxj)

Nor Arizona... (http://goo.gl/maps/e8e8C)

Even Google's home state of California gets bitten by the "no state on Street View address" bug! (http://goo.gl/maps/OzaT0)  :banghead:

Why are states disappearing all of a sudden from addresses on Street View? A potential attack by Alanland?
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on October 31, 2012, 01:06:39 PM
They also seem to give the "address" with no regard to which of several names on the road is actually used for making an address.  For example, in downtown Columbus, it will say "96 U.S. 40", when it should say "96 W Broad St", or at least "96 W U.S. 40".  Just another example of why the directional prefix should (in a majority of address systems, including all in central Ohio) be considered part of the address, not part of the street name.
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on November 01, 2012, 02:06:29 AM
Quote from: vtk on October 31, 2012, 01:06:39 PM
They also seem to give the "address" with no regard to which of several names on the road is actually used for making an address.  For example, in downtown Columbus, it will say "96 U.S. 40", when it should say "96 W Broad St", or at least "96 W U.S. 40".  Just another example of why the directional prefix should (in a majority of address systems, including all in central Ohio) be considered part of the address, not part of the street name.

I've noticed that as well.

One of the most egregious examples was a few months back, when they had nearly all of US 40, at least in Ohio, labeled as "Victory Highway" regardless of any of its local names.

Now they seem to have it, as you noted, as "U.S. 40", which is marginally better since one could at least find references to US 40 in real-life signage...
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 02, 2012, 12:43:13 AM
Oops, I seem to have screwed up Google Maps' rendering of the George Washington Bridge interchange. I sent them a report that Exit 1 from the lower lever to the Henry Hudson Parkway was incorrectly shown diverging to the right instead of the left...now they're updated it to show the ramp on the left, but from the upper level instead!

http://goo.gl/maps/3gq1d

My fault, sorry!   :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on November 03, 2012, 10:12:42 AM
For once, Google maps has done something GOOD. it actually shows you your house and the exact development you are in when you are zoomed in real close  :wow:

[Image redacted. Probably not a good idea to show the entire world the exact city and street you live on, dude! -S.]
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 03, 2012, 12:09:20 PM
Only for some cities.
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on November 03, 2012, 06:37:09 PM
This is both correct and incorrect: The GSP in Jersey is NJ-444, but in New York, it's NY-982L, not NY-444

http://goo.gl/maps/xPSzV
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 04, 2012, 10:52:37 AM
Yet another... (http://goo.gl/maps/e5k9I)
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on November 04, 2012, 11:09:24 AM
Quote from: Roadsguy on November 04, 2012, 10:52:37 AM
Yet another... (http://goo.gl/maps/e5k9I)
"4 lanes, 55.00 mph speed, Two way traffic, Paved road, Expressway" How does that even get approved...

I found another case of a back road being shown as an expressway, and I edited it back to normal, and of course I get the "This edit does not meet our guidelines.." automated response. I wish Map Maker was as simple and easy as OpenStreetMap. Some of the editors at Map Maker who have the ability to approve these edits don't even know as much as half the people on this forum.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on November 06, 2012, 07:55:27 PM
Look at this, the DE/PA borders In Google maps and MapMaker are over 1mi. apart.   :banghead: :banghead:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1294.photobucket.com%2Falbums%2Fb619%2Fkherm2000%2FDEBorderMapsSouth.png&hash=cfa9d0b9dee3b9efa1289479d0b9e962bca108cf)
Google Maps (I'm pretty sure this is the correct one)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1294.photobucket.com%2Falbums%2Fb619%2Fkherm2000%2FDEBorderMapMakerNorth.png&hash=2844a498dbd097edec087bb70dc7b4715e795fdc)
Google MapMaker


Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on November 06, 2012, 10:20:23 PM
Interstate 376 Business is colored orange for its entire length even though there are clearly a few at grade intersections: http://goo.gl/maps/GZBYh

This section of US 22 is colored yellow when it is a freeway here: http://goo.gl/maps/5E6sd

This mile or two long segment of US 209 is a freeway, and is labelled as such on most official maps, but from experience in Map Maker, Google refuses to give it expressway or freeway status  http://goo.gl/maps/TtQCj
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 07, 2012, 07:29:55 AM
Quote from: Some_Person on November 06, 2012, 10:20:23 PM
Interstate 376 Business is colored orange for its entire length even though there are clearly a few at grade intersections: http://goo.gl/maps/GZBYh

That's because it's an expressway, not all freeway. (I believe it was once supposed to be all upgraded though...) Since you use Map Maker, did you check to see if it was freeway or expressway, or if ALL of it was wrongly shown as expressway?
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on November 07, 2012, 06:10:19 PM
Quote from: Roadgeek2500 on November 06, 2012, 07:55:27 PM
Look at this, the DE/PA borders In Google maps and MapMaker are over 1mi. apart.   :banghead: :banghead:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1294.photobucket.com%2Falbums%2Fb619%2Fkherm2000%2FDEBorderMapMakerNorth.png&hash=2844a498dbd097edec087bb70dc7b4715e795fdc)
Google MapMaker



Delaware needs all the land it can get.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on November 10, 2012, 08:30:36 AM
Quote from: Steve on November 07, 2012, 06:10:19 PM
Quote from: Roadgeek2500 on November 06, 2012, 07:55:27 PM
Look at this, the DE/PA borders In Google maps and MapMaker are over 1mi. apart.   :banghead: :banghead:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1294.photobucket.com%2Falbums%2Fb619%2Fkherm2000%2FDEBorderMapMakerNorth.png&hash=2844a498dbd097edec087bb70dc7b4715e795fdc)
Google MapMaker



Delaware needs all the land it can get.

Yeah, so much that it needs PA 491 in DE  :spin:
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on November 10, 2012, 03:59:44 PM
Quote from: Roadgeek2500 on November 10, 2012, 08:30:36 AM
Quote from: Steve on November 07, 2012, 06:10:19 PM
Quote from: Roadgeek2500 on November 06, 2012, 07:55:27 PM
Look at this, the DE/PA borders In Google maps and MapMaker are over 1mi. apart.   :banghead: :banghead:



Delaware needs all the land it can get.

Yeah, so much that it needs PA 491 in DE  :spin:
There's a DE 491. It's just really short. (Eastern end of 491 at 92 dips into DE.)
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on November 10, 2012, 06:53:49 PM
I was looking at the Alaskan Way Viaduct area today for some reason, and slowly came to the realization that there don't seem to be any SR 99 shields to be seen anywhere in Washington.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on November 12, 2012, 09:47:32 PM
Does the state of Montana have a US 210? I say no. But we do have 2, 12, 20, 87, 89, 93, 191, 212, 287 and 310. I don't see how Google Earth has a US 210 in Montana. That just doesn't make sense.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 17, 2012, 10:15:01 AM
http://goo.gl/maps/RkvAz (http://goo.gl/maps/RkvAz) :eyebrow:
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on November 18, 2012, 05:23:19 AM
Quote from: Roadsguy on November 17, 2012, 10:15:01 AM
http://goo.gl/maps/RkvAz (http://goo.gl/maps/RkvAz) :eyebrow:

AFAICT that's just Google's dumbass practice of not posting any sort of banners or green shields on Business routes.

Stupid, but not necessarily incorrect (you'll notice that if you get directions, it does indeed refer to it as "US 13 BUS").
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 18, 2012, 09:04:03 AM
No, I mean the entire bypass isn't shown as a freeway. :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on November 18, 2012, 10:37:12 AM
Google's completely screwed that up everywhere. There are countless non-freeways shown in orange, and countless freeways shown in yellow.

Here's an example: http://goo.gl/maps/fhYAB Binghamton, NY
-NY 201 on the left is a full freeway all the way from NY 17/I-86 down to NY 434, yet Google shows it as yellow.
-NY 363/7 on the right, however, has a signalized intersection just south of NY 17/I-86, and another one about a mile north of it, yet Google shows it as orange.
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 18, 2012, 01:25:06 PM
Quote from: deathtopumpkins on November 18, 2012, 10:37:12 AM
Google's completely screwed that up everywhere. There are countless non-freeways shown in orange, and countless freeways shown in yellow.

There is no map legend for Google that I'm aware of...is it known whether the symbols do in fact represent freeways vs. non-freeways? I mean that would make sense, but...
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on November 18, 2012, 01:27:53 PM
Quote from: Roadsguy on November 18, 2012, 09:04:03 AM
No, I mean the entire bypass isn't shown as a freeway. :pan:

Pfft, I didn't even zoom in far enough to notice those were grade-separated interchanges. Derp!  :spin:
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 18, 2012, 01:30:11 PM
Quote from: empirestate on November 18, 2012, 01:25:06 PM
Quote from: deathtopumpkins on November 18, 2012, 10:37:12 AM
Google's completely screwed that up everywhere. There are countless non-freeways shown in orange, and countless freeways shown in yellow.

There is no map legend for Google that I'm aware of...is it known whether the symbols do in fact represent freeways vs. non-freeways? I mean that would make sense, but...

It's assumed so in the US and Canada, though in places like Mexico they're truly random.  The Mexican data has no means of differentiating freeways and non-freeways.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 18, 2012, 06:18:27 PM
Google has "expressway" and "freeway." The same color is used for both, though, which is dumb and confusing.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on November 18, 2012, 06:30:16 PM
Quote from: Roadsguy on November 18, 2012, 06:18:27 PM
Google has "expressway" and "freeway." The same color is used for both, though, which is dumb and confusing.

I thought they just had "expressway", which was meant to be used for what MUTCD calls freeways, and more recently was applied also to what MUTCD calls expressways due to Map Maker contributors and moderators being dumb.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on November 18, 2012, 08:05:44 PM
Quote from: vtk on November 18, 2012, 06:30:16 PM
Quote from: Roadsguy on November 18, 2012, 06:18:27 PM
Google has "expressway" and "freeway." The same color is used for both, though, which is dumb and confusing.

I thought they just had "expressway", which was meant to be used for what MUTCD calls freeways, and more recently was applied also to what MUTCD calls expressways due to Map Maker contributors and moderators being dumb.
If Map Maker was more similar to OSMs editing system then Google would be the best mapping site there is. Or at least, they could just have everyone on this forum given editing privileges. Half the moderators on Map Maker know barely as much as we all do. Plus, I don't think 3 colors is enough to define all the different roads on Google Maps
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 18, 2012, 08:18:20 PM
Quote from: Some_Person on November 18, 2012, 08:05:44 PM
Plus, I don't think 3 colors is enough to define all the different roads on Google Maps

One principle I've always struggled with from a cartographic standpoint is: should the symbol used indicate a road's class (US, state, Interstate...) or its function (arterial, freeway, expressway and similar descriptors) or its physical characteristics (paved, unimproved, multi-lane...) or what?

Some maps, like the current USGS digital topos, use different symbols for Interstate, US, and state highways. Besides not always giving much of an idea what a road's really like (many state highways are freeways and of much higher quality than some backcountry two-lane US route), you could argue it's redundant because the shield symbol already tells you that.

Probably most maps try to depict roads according to their importance: primary, secondary, tertiary...or sometimes arterial, collector, local and so on. Freeways are pretty universally set off from other roads visually. But as we see at OSM, agreeing on a consistent and widely-applied symbology is harder than you'd think, partly because importance is relative. If a two-lane asphalt (or even gravel) highway is the only road for dozens of miles around, you'd say it's pretty darn primary. But a physically identical road in a suburban area would hardly register as important at all.

And how do you treat a road that every inch a freeway, except for one isolated place where maybe there's a grade crossing? You wouldn't downgrade the symbology for the whole road, but you'd also want to accurately convey the anomaly.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on November 18, 2012, 08:31:50 PM
Quote from: empirestate on November 18, 2012, 08:18:20 PM
Some maps, like the current USGS digital topos, use different symbols for Interstate, US, and state highways.

That annoys the crap out of me, particularly when older versions of the map differentiated based on other characteristics.  USGS Topos and DeLorme Atlas & Gazetteers are both like that.  The problem is a switch to a digital roads dataset that knows nothing of a road's characteristics, but only its designation.  The new USGS topos actually have a roads layer derived from a commercial data provider, and that layer retains copyright status as a result. :angry:
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 18, 2012, 08:57:17 PM
From my brief time in Map Maker, before I gave up on it, I could tell:

Orange:
-Freeway
-Expressway

Yellow:
-National Highway (pretty much only US routes...)
-Major Artery
-Minor Artery

White:
-I forget if it was "minor road" or whatever...
-Terminal road (slightly narrower, usually used for no-outlets)
-Some other really narrow thing

Ramps were assigned by "segment usage," not "priority." I still haven't quite figured out how to make a ramp into a non-ramp. It never seemed to work. :/
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on November 18, 2012, 09:52:16 PM
Quote from: Roadsguy on November 18, 2012, 08:57:17 PM
Ramps were assigned by "segment usage," not "priority." I still haven't quite figured out how to make a ramp into a non-ramp. It never seemed to work. :/

I'm glad I'm not the only one who can't figure that out :-P like for example, here: http://goo.gl/maps/zThVX where PA 309 branches off I-78, those shouldn't be ramps, as it's the entire freeway that comes off the interstate, so it should be more like this example: http://goo.gl/maps/E0Qwk

Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on November 19, 2012, 07:14:50 AM
This is why I much, much preferred the Thomas Brothers symbology.
They broke it down by road type -- Freeways and their ramps (thick red, thin red)
Highways/west-coast expressways (with at grade crossings) (thick tan, thin tan)
Arteries and their ramps (if they have interchanges) (thick green, thin green)
Collectors/secondary arteries (bold black line)
Local streets (thin grey line)
Unpaved (dashed grey line)

What's so difficult about adopting a theme like this for the online maps? Google maps would be excellent if it differentiated between road classes, so errors like OR 224 being shown as a freeway wouldn't exist (and it falls under the freeway category because its name is the Milwaukie Expressway).
OSM does a much better job, but it's not great either, because highways will shift colors for sometimes indiscernible reasons -- US 26 through Portland's a great example. It's a red line through Southeast Portland, shifts to tan east of I-205 all the way to the junction with Burnside Rd and the Mt Hood Highway, where it becomes green until the city limits of Sandy, where it goes red again. Why? Is it denoting maintenance divisions? I couldn't care less about that; I'd refer to an ODOT map if I needed that information. Is it a lane distribution? Then the portion through downtown Gresham is wrong, as it's four lanes, like the portion between the river and I-205. Is it a speed limit indication? Again, then it's wrong: From memory, Powell is 40 over the Ross Island Bridge, 35 from OR 99E all the way to about 122nd Ave, 40 from there to 182nd, back to 35 to Eastman, 30 to the Mt Hood, 55 to Sandy and down to 35 in Sandy itself.
Since non-highways also share the same colors, it muddies the water even further. Ok, green lines are the big, non-freeway highways maybe. Wait. N Greeley Ave and N Going St are green as well.

It's this type of thing that keeps a map from being excellent -- it's either simplifying too much and then falling prey to an archaic editing system with a bad review process (Google) or it's conveying too much information which would better fit a foreign system (OSM, which I believe fits the European road classification model better than the American one).
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 19, 2012, 12:31:58 PM
Quote from: Bickendan on November 19, 2012, 07:14:50 AM
This is why I much, much preferred the Thomas Brothers symbology.
They broke it down by road type -- Freeways and their ramps (thick red, thin red)
Highways/west-coast expressways (with at grade crossings) (thick tan, thin tan)
Arteries and their ramps (if they have interchanges) (thick green, thin green)
Collectors/secondary arteries (bold black line)
Local streets (thin grey line)
Unpaved (dashed grey line)

What's so difficult about adopting a theme like this for the online maps?

Couple reasons occur to me...

-This symbology works great in Thomas Bros. territory, but how do you apply it around the world? How would you show the Dalton Highway, for example? As a dashed gray line for unpaved road, or a thick green one for major artery? What about other countries where almost none of even the most major roads are improved?

-Functional classification isn't consistent with route designation in the U.S., but you still want to show some correlation for those actually trying to follow a route through an area. There should ideally be a symbological way to show the path of a US highway, for example, along different city streets that aren't otherwise physically distinguishable.

-Do you depict a road according to its design, or what traffic it actually handles? If a small road is choked with traffic, does it get the arterial symbol? Or does it get the minor road symbol, to emphasize that it isn't at all the right level of road for the traffic it carries?
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on November 19, 2012, 03:58:29 PM
Quote from: empirestate on November 19, 2012, 12:31:58 PM
Quote from: Bickendan on November 19, 2012, 07:14:50 AM
This is why I much, much preferred the Thomas Brothers symbology.
They broke it down by road type -- Freeways and their ramps (thick red, thin red)
Highways/west-coast expressways (with at grade crossings) (thick tan, thin tan)
Arteries and their ramps (if they have interchanges) (thick green, thin green)
Collectors/secondary arteries (bold black line)
Local streets (thin grey line)
Unpaved (dashed grey line)

What's so difficult about adopting a theme like this for the online maps?

Couple reasons occur to me...

-This symbology works great in Thomas Bros. territory, but how do you apply it around the world? How would you show the Dalton Highway, for example? As a dashed gray line for unpaved road, or a thick green one for major artery? What about other countries where almost none of even the most major roads are improved?
If using a strict TB scheme, the Dalton (and similar highways in Yukon/NWT, like the Dempster) would be tan, to show that they are highways. That's how they handled OR 27 in the PNW atlas, which does have unpaved sections, if memory serves. A solution to note that it is unpaved would be in the highway label: DALTON HIGHWAY (UNIMPROVED [or] UNPAVED), with its route marker [AK 11].
What would be needed is an additional color for unpaved highways (unpaved arteries could use a dashed, uncased green line, for example, though that could clash with green marked areas, like forests, parks and golf courses). Another problem, one that I imagine RMN tried to solve, is colorblind people. Of course, RMN's symbology is fairly garish.

Quote-Functional classification isn't consistent with route designation in the U.S., but you still want to show some correlation for those actually trying to follow a route through an area. There should ideally be a symbological way to show the path of a US highway, for example, along different city streets that aren't otherwise physically distinguishable.
If I'm reading this correctly, this goes along my point about US 26 through Portland and Gresham. That tan line from I-405 and SW Broadway all the way out through Gresham would tell me exactly where it goes (even TB [ok, RMN] screws this up, but that's really ODOT's fault for failing to precisely define how US 26 gets through downtown and then telling AASHTO: Market/Clay and Naito, per AASHTO? I-405, Broadway/5th/Sheridan, 3rd, Arthur, Kelly/Naito per ODOT?)

Quote-Do you depict a road according to its design, or what traffic it actually handles? If a small road is choked with traffic, does it get the arterial symbol? Or does it get the minor road symbol, to emphasize that it isn't at all the right level of road for the traffic it carries?
Artery. SE Division St springs straight to mind. From 7th to 60th, it carries a lot more traffic than it was designed to; it's also a straight shot from Gresham to Portland for commuters, running from SE 3rd to 317th out past Gresham. I see that green line, I know to keep a bigger eye out for traffic when walking/riding a bike/etc.
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 19, 2012, 09:22:18 PM
Quote from: Bickendan on November 19, 2012, 03:58:29 PM
Quote-Do you depict a road according to its design, or what traffic it actually handles? If a small road is choked with traffic, does it get the arterial symbol? Or does it get the minor road symbol, to emphasize that it isn't at all the right level of road for the traffic it carries?
Artery. SE Division St springs straight to mind. From 7th to 60th, it carries a lot more traffic than it was designed to; it's also a straight shot from Gresham to Portland for commuters, running from SE 3rd to 317th out past Gresham. I see that green line, I know to keep a bigger eye out for traffic when walking/riding a bike/etc.

OK, that's all fair...but what if I'm using the map to find the best route through, assuming that the map will show me the roads that I can expect to use without issues of congestion...or, if no such route exists, to show me that instead?

In other words, it comes down to the fact that maps should show what they're designed to show, and there's no catch-all answer for that. If I make a map explicitly of Interstate, US and state highway systems, then by golly I had better use symbology that reflects those distinctions! But if my map is supposed to be for effective motor travel, I probably should use symbols based on functional class instead. And you've mentioned walking, biking, etc.–maps can be separately designed for those uses as well.

The challenge, then, is what to do with online mapping, which ambitiously tries to be an all-in-one solution. Many, if not most, people may use them primarily for navigation, but there are other ways they are frequently used as well. As a result, different providers have different levels of success. I use Google for the most up-to-date aerial imagery, MapQuest for the most up-to-date map date, and Bing if I want, for example, to see all of the counties successfully labeled at a single zoom level. I use OSM, on the other hand, to look at areas where I want human interpretation to have been applied. Where it has been, it's most accurate of all, and where it hasn't, that's fairly evident from the map's appearance. Then again, I'm a much more advanced map user than the average Joe...
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on November 20, 2012, 09:50:59 AM
Quote from: empirestate on November 19, 2012, 09:22:18 PM
what if I'm...assuming that the map will show me the roads that I can expect to use without issues of congestion...?

But who reads a map with that assumption in mind?  Aside from the freeway/surface route and single/dual carriageway distinctions, what congestion issues does one really expect a map to convey?  Ratio of number of lanes to traffic counts?  Stoplight timings?  Speed limits?

Yeah, that kind of stuff might be useful on a map, but I don't think people (OK, more than seven people) really think that's...
Quote from: empirestate on November 19, 2012, 09:22:18 PM
what they're designed to show
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 20, 2012, 12:28:15 PM
Quote from: kphoger on November 20, 2012, 09:50:59 AM
Quote from: empirestate on November 19, 2012, 09:22:18 PM
what if I'm...assuming that the map will show me the roads that I can expect to use without issues of congestion...?

But who reads a map with that assumption in mind?

Why, travelers using the map, of course.

Quote from: kphoger on November 20, 2012, 09:50:59 AM
Aside from the freeway/surface route and single/dual carriageway distinctions, what congestion issues does one really expect a map to convey?  Ratio of number of lanes to traffic counts?  Stoplight timings?  Speed limits?

No, think more broadly: mountains, cities, that sort of thing. If I'm reading a map and I see a big fat line in a bold color running through an otherwise blank area, I'll assume my passage there will be relatively easy. Now, if a dot or a blob with a city name appears along that line, I now assume some kind of settlement. Perhaps the road I'm on barrels through that town with essentially no interruption, but perhaps instead it gets funneled down a single street that's far too narrow. Yet it's the only way through, and many people pass through this town, so it's completely choked with traffic, and it may take me an hour or so to traverse this little town. I think it's a fair assumption that a map of reasonable detail will somehow show which of those cases is more likely.

So as for specific highway symbology, would you retain the bold, fat line symbol on that road as it passes through that town, to show that it carries all of the traffic through–i.e., is the artery? Or do you switch to a skinny little line to show that the way through town is along a skinny little street, hoping the reader will infer that the trip from big fat line through skinny line and back to big fat line will add some time to the journey?

Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on November 20, 2012, 06:43:42 PM
Quote from: empirestate on November 19, 2012, 09:22:18 PM
But if my map is supposed to be for effective motor travel, I probably should use symbols based on functional class instead.

When editing OSM I try to use a sort of polished HFCS-style system. HFCS itself is a bit too messy to use on a finished map; classifications are not always moved after major realignments, and sometimes begin or end at arbitrary places.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on November 20, 2012, 09:15:36 PM
Quote from: empirestate on November 20, 2012, 12:28:15 PM
If I'm reading a map and I see a big fat line in a bold color running through an otherwise blank area, I'll assume my passage there will be relatively easy. Now, if a dot or a blob with a city name appears along that line, I now assume some kind of settlement. Perhaps the road I'm on barrels through that town with essentially no interruption, but perhaps instead it gets funneled down a single street that's far too narrow. Yet it's the only way through, and many people pass through this town, so it's completely choked with traffic, and it may take me an hour or so to traverse this little town. I think it's a fair assumption that a map of reasonable detail will somehow show which of those cases is more likely.

So as for specific highway symbology, would you retain the bold, fat line symbol on that road as it passes through that town, to show that it carries all of the traffic through—i.e., is the artery? Or do you switch to a skinny little line to show that the way through town is along a skinny little street, hoping the reader will infer that the trip from big fat line through skinny line and back to big fat line will add some time to the journey?

Neither, since the black dot covers the town and obliterates the red line in that location.  Fat lines should denote trunk highways, and skinny ones should denote feeder highways.
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on November 20, 2012, 11:18:51 PM
Quote from: kphoger on November 20, 2012, 09:15:36 PM
Quote from: empirestate on November 20, 2012, 12:28:15 PM
So as for specific highway symbology, would you retain the bold, fat line symbol on that road as it passes through that town, to show that it carries all of the traffic through—i.e., is the artery? Or do you switch to a skinny little line to show that the way through town is along a skinny little street, hoping the reader will infer that the trip from big fat line through skinny line and back to big fat line will add some time to the journey?

Neither, since the black dot covers the town and obliterates the red line in that location.  Fat lines should denote trunk highways, and skinny ones should denote feeder highways.

OK, fine...  :rolleyes: Suppose it's a really long stretch of narrow highway, like through a mountain range, if that helps.

Or don't suppose anything...bottom line is, do the classes "trunk", "arterial" and so forth refer to the traffic a highway carries, or that which it's designed to carry, or capable of carrying, even though the actual amount is much more or less? I'm speaking from a cartographic standpoint, not an engineering one.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on November 20, 2012, 11:54:55 PM
I'd say it's more recursive than that. If you have two parallel routes connecting nearby points, and one is clearly a better route to take, that one should be a higher clasification. Classifications should end at logical points (usually towns or major intersections). So if a six-lane highway becomes a two-lane main street, it should keep the same classification *unless there is a bypass*. This, of course, ignores classifications based on physical characteristics (OSM's trunk, sometimes; Google's expressway; paper maps' divided highway). My personal rendering preference would be the way I've seen some paper maps do it: color indicates importance and thickness/number of lines indicates width. This is trivial at low zooms, where one doesn't have to deal with one-way pairs (the occasional super-wide median looks a bit ugly, but whatever).

So for the example of a four-lane going to two through a mountain range:
       ^ ^
===-----===
        ^
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on November 21, 2012, 07:28:56 AM
Is that I-93 in ASCII? ;)
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on November 21, 2012, 01:57:18 PM
Quote from: empirestate on November 20, 2012, 11:18:51 PM
do the classes "trunk", "arterial" and so forth refer to the traffic a highway carries, or that which it's designed to carry, or capable of carrying, even though the actual amount is much more or less? I'm speaking from a cartographic standpoint, not an engineering one.

'Trunk', 'arterial', etc. should refer to the route's importance in the overall road network.  That is, the main highway people take from City A to City B should be considered a trunk route; highways feeding that one from smaller communities and alternate routes should be considered secondary.  The amount of traffic that a trunk route is designed to carry, as well as what it actually carries, will vary by geographical location; IMO, that shouldn't affect how it is rendered on a map.
Title: Re: Incorrect highways marked on Google Maps
Post by: myosh_tino on November 21, 2012, 03:35:54 PM
Quote from: NE2 on November 20, 2012, 11:54:55 PM
So for the example of a four-lane going to two through a mountain range:
       ^ ^
===-----===
        ^
Looks like that road is under construction!  ;-)
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on November 25, 2012, 10:45:11 PM
This section of US 202 in New Jersey has always been shown as a freeway, but now it's colored yellow http://goo.gl/maps/AksH9

Also, I believe I've seen this on this thread or at least forum somewhere before, http://goo.gl/maps/JR7nd I-6 is showing up in Maine
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 26, 2012, 08:29:27 AM
Quote from: Some_Person on November 25, 2012, 10:45:11 PM
This section of US 202 in New Jersey has always been shown as a freeway, but now it's colored yellow http://goo.gl/maps/AksH9

:banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: Takumi on November 26, 2012, 10:21:57 AM
Part of NC 11 Business near Aulander (http://m.google.com/u/m/BreVnW) is labeled NC 350, which hasn't existed for over 30 years. (http://www.vahighways.com/ncannex/route-log/nc350.html) Pardon the phone screenshot quality.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fphotos-c.ak.fbcdn.net%2Fhphotos-ak-snc7%2F481715_4904384368689_2002455642_n.jpg&hash=30a573e805333a779b531d60d5383d4947274e0d)
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on November 26, 2012, 05:01:11 PM
Quote from: Roadsguy on November 26, 2012, 08:29:27 AM
Quote from: Some_Person on November 25, 2012, 10:45:11 PM
This section of US 202 in New Jersey has always been shown as a freeway, but now it's colored yellow http://goo.gl/maps/AksH9

:banghead:
Someone must have decided it's not a freeway because "I drive on 202 and it has lights." Not thinking about where the lights end.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on November 26, 2012, 05:47:43 PM
Quote from: Takumi on November 26, 2012, 10:21:57 AM
Part of NC 11 Business near Aulander (http://m.google.com/u/m/BreVnW) is labeled NC 350, which hasn't existed for over 30 years. (http://www.vahighways.com/ncannex/route-log/nc350.html)
That's from TIGER (and Google's decision to display all the TIGER alternate names): http://www.openstreetmap.org/browse/way/16609941
Title: Re: Incorrect highways marked on Google Maps
Post by: Dr Frankenstein on November 28, 2012, 10:35:38 AM
And now Autoroutes 10, 35 and 55 have entirely gone shield-less.

And an inexplicable, isolated stretch of A-30 popped up in the middle of Beauharnois, 3 weeks from opening.

Damn, I hate clueless MapMaker editors.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 28, 2012, 11:13:49 AM
The entire eastern half of I-140 in Wilmington, NC isn't shown as a freeway. As if to justify this, all shields on the entire thing are gone. :eyebrow:
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on November 28, 2012, 11:40:06 AM
Quote from: Dr Frankenstein on November 28, 2012, 10:35:38 AM
And now Autoroutes 10, 35 and 55 have entirely gone shield-less.

And an inexplicable, isolated stretch of A-30 popped up in the middle of Beauharnois, 3 weeks from opening.

Damn, I hate clueless MapMaker editors.
Part of I-781 popped up too, though it's shown as "Iraqi Freedom Drive" (they added the SPUI).
Title: Re: Incorrect highways marked on Google Maps
Post by: bob7374 on November 28, 2012, 12:32:20 PM
Quote from: Roadsguy on November 28, 2012, 11:13:49 AM
The entire eastern half of I-140 in Wilmington, NC isn't shown as a freeway. As if to justify this, all shields on the entire thing are gone. :eyebrow:
According to NCDOT the eastern half of the Wilmington Bypass is only US 17, not I-140. It is a freeway though, so you would think it would show up as one. Elsewhere in NC, now that I-73 officially runs along all of US 220 South of Greensboro, they've removed all I-73 shields from Asheboro north. They do have I-74 shields along US 220 as far north as US 311, or as one shield to the east of the exit reads, I-311.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on November 28, 2012, 05:25:02 PM
Can we just amend the US roadgeek constitution and ban all use of Google Maps? :bigass:
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on November 28, 2012, 07:44:31 PM
Quote from: Roadsguy on November 28, 2012, 05:25:02 PM
Can we just amend the US roadgeek constitution and ban all use of Google Maps? :bigass:
I think they should just give us the right to edit Google Maps just as much as we can edit OpenStreetMap, anyone who's smart enough to discover and use Map Maker efficiently shouldn't have to wait for a long process just to get their edit (sometimes :-/) approved.

Although, based on how my experiences with Map Maker have been, your idea seems easier and better :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on November 28, 2012, 09:29:11 PM
I think Google Maps should only be editable by members of AARoads who have at least 100 posts and have been here at least 7 days. (That gives admins enough time to cut off clueless users.)
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on November 29, 2012, 12:44:48 PM
Maybe AARoads could start a new server using OSM's toolchain and we could have our own roadgeeky map dataset.

...yes, I know how absurd that sounds.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on November 30, 2012, 06:30:35 PM
Quote from: vtk on November 29, 2012, 12:44:48 PM
Maybe AARoads could start a new server using OSM's toolchain and we could have our own roadgeeky map dataset.

...yes, I know how absurd that sounds.
OSM is basically just that. Unlike Google Maps, the OSM editors actually know what they're doing.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on November 30, 2012, 07:20:53 PM
Quote from: Steve on November 30, 2012, 06:30:35 PM
Quote from: vtk on November 29, 2012, 12:44:48 PM
Maybe AARoads could start a new server using OSM's toolchain and we could have our own roadgeeky map dataset.

...yes, I know how absurd that sounds.
OSM is basically just that. Unlike Google Maps, the OSM editors actually know what they're doing.
...which is exactly why duplicating that effort is so absurd.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 01, 2012, 09:39:54 AM
Quote from: Steve on November 30, 2012, 06:30:35 PM
Unlike Google Maps, the OSM editors actually know what they're doing.
Usually. But it's not worth forking just so the Alaskan Way Viaduct can be a freeway.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on December 01, 2012, 09:47:01 AM
Why exactly isn't it shown as one?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 01, 2012, 09:52:39 AM
Quote from: Roadsguy on December 01, 2012, 09:47:01 AM
Why exactly isn't it shown as one?
Because a local decided it's not one, due to:
"Low speed limits (35 mph on Spokane Street Viaduct, 50/40 mph on Alaskan Way Viaduct vs. I-5 60mph)
No shoulders
dangerous onramps
narrow lanes"
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on December 01, 2012, 10:18:15 AM
Well, we all know it's one of the most substandard freeways ever. Hence the planned demolition. :P
Title: Re: Incorrect highways marked on Google Maps
Post by: jp the roadgeek on December 04, 2012, 05:16:57 PM
Don't know if anyone has noticed, but Maine apparently has started signing the new rooftop highway as Interstate 6.  Still a 2 lane road though :)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 04, 2012, 10:41:43 PM
Say hello to I-311. (http://goo.gl/maps/4rWlM)
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 04, 2012, 11:45:22 PM
Quote from: rickmastfan67 on December 04, 2012, 10:41:43 PM
Say hello to I-311. (http://goo.gl/maps/4rWlM)

Well, to be fair, it is an Interstate highway, and it is numbered 311. :(
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 06, 2012, 05:31:05 AM
Quote from: Kacie Jane on December 04, 2012, 11:45:22 PM
Quote from: rickmastfan67 on December 04, 2012, 10:41:43 PM
Say hello to I-311. (http://goo.gl/maps/4rWlM)

Well, to be fair, it is an Interstate highway, and it is numbered 311. :(

Well, that was fast.  It's already been fixed!
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on December 06, 2012, 01:34:52 PM
Quote from: rickmastfan67 on December 06, 2012, 05:31:05 AM
Quote from: Kacie Jane on December 04, 2012, 11:45:22 PM
Quote from: rickmastfan67 on December 04, 2012, 10:41:43 PM
Say hello to I-311. (http://goo.gl/maps/4rWlM)

Well, to be fair, it is an Interstate highway, and it is numbered 311. :(

Well, that was fast.  It's already been fixed!

I-311? Did Google mistake that to be US 311? I don't even know if US 311 is even ready to be upgraded to Interstate status.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 06, 2012, 02:09:12 PM
Quote from: Billy F 1988 on December 06, 2012, 01:34:52 PM
Quote from: rickmastfan67 on December 06, 2012, 05:31:05 AM
Quote from: Kacie Jane on December 04, 2012, 11:45:22 PM
Quote from: rickmastfan67 on December 04, 2012, 10:41:43 PM
Say hello to I-311. (http://goo.gl/maps/4rWlM)

Well, to be fair, it is an Interstate highway, and it is numbered 311. :(

Well, that was fast.  It's already been fixed!

I-311? Did Google mistake that to be US 311? I don't even know if US 311 is even ready to be upgraded to Interstate status.

Sometimes it helps to click the link where it's given, so you can see that yes, it was supposed to be US 311, but yes, the section in question was already an Interstate (it's a multiplex of I-74/US 311).

Then again, sometimes it helps for me to read my own signature, but I put it there knowing I wouldn't.

On a lighter note, enjoy these US 1993 shields in the same area: http://goo.gl/maps/O1rYd
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on December 08, 2012, 08:15:51 PM
http://goo.gl/maps/QWxjA (http://goo.gl/maps/QWxjA) :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 08, 2012, 09:19:50 PM
Quote from: Roadsguy on December 08, 2012, 08:15:51 PM
http://goo.gl/maps/QWxjA (http://goo.gl/maps/QWxjA) :pan:

And to boot, it really looks like Google took it directly from OSM (the alignment that is)!! :-o :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 08, 2012, 09:29:01 PM
Quote from: rickmastfan67 on December 08, 2012, 09:19:50 PM
Quote from: Roadsguy on December 08, 2012, 08:15:51 PM
http://goo.gl/maps/QWxjA (http://goo.gl/maps/QWxjA) :pan:

And to boot, it really looks like Google took it directly from OSM (the alignment that is)!! :-o :pan:

Evidence? Do they both have the alignment wrong in the same way?
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 08, 2012, 09:35:03 PM
Quote from: NE2 on December 08, 2012, 09:29:01 PM
Quote from: rickmastfan67 on December 08, 2012, 09:19:50 PM
Quote from: Roadsguy on December 08, 2012, 08:15:51 PM
http://goo.gl/maps/QWxjA (http://goo.gl/maps/QWxjA) :pan:

And to boot, it really looks like Google took it directly from OSM (the alignment that is)!! :-o :pan:

Evidence? Do they both have the alignment wrong in the same way?

Well, my evidence is using the CHM browser that allows me to compare different imagery sources.  Since we don't have I-781 in our browser yet, use I-81's (http://cmap.m-plex.com/hb/hwymap.php?r=ny.i081&sys=usai&rg=all) file.  Hit Exit #48 and then zoom into the new alignment of I-781.  It's pretty might identical on Google to OSM's.  Just switch between the "Mapnik" and "Map" layers.  This is especially fishy since Google doesn't even have Sat imagery yet for that area showing the highway under-construction (Bing does), and I don't think they could have had any StreetView cars up there already to get a trace.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 08, 2012, 09:51:04 PM
I don't buy it. There's definitely some difference, especially west of NY 37, where Google better matches the bridges visible on the Bing and NAIP (MQ Open) aerials than OSM. It seems that whoever added it to Google simply used a different aerial photo.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 08, 2012, 09:56:26 PM
Quote from: NE2 on December 08, 2012, 09:51:04 PM
I don't buy it. There's definitely some difference, especially west of NY 37, where Google better matches the bridges visible on the Bing and NAIP (MQ Open) aerials than OSM. It seems that whoever added it to Google simply used a different aerial photo.

Maybe you're right about somebody somehow using the NAIP imagery to trace it into Google.  Just seemed a tad phishy to me.
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on December 08, 2012, 10:55:24 PM
Also, it's not designated as an interstate, and it's not marked as I-781.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 08, 2012, 11:03:28 PM
Quote from: WNYroadgeek on December 08, 2012, 10:55:24 PM
Also, it's not designated as an interstate, and it's not marked as I-781.

I only said that the "alignment" was possibly taken from OSM.
Quote from: rickmastfan67 on December 08, 2012, 09:19:50 PM
And to boot, it really looks like Google took it directly from OSM (the alignment that is)!! :-o :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 09, 2012, 12:30:45 PM
Leave it to Google to do something like this wrong.  Their logic is probably along the lines of "there are no interchanges between I-81 and US 11 so it's not a freeway".  To top it off, NY 342 is marked as the more heavily traveled road, as evidenced when you zoom out (this seems to be a common problem, actually, and is still an issue with I-69).
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 09, 2012, 03:17:34 PM
Quote from: deanej on December 09, 2012, 12:30:45 PM
To top it off, NY 342 is marked as the more heavily traveled road, as evidenced when you zoom out (this seems to be a common problem, actually, and is still an issue with I-69).
It's also an issue with Interstates vs. other freeways. Look ma, no Turnpike! http://maps.google.com/maps?hl=en&ll=28.396233,-80.848389&spn=4.406221,8.453979&gl=us&t=m&z=8

PS: How did this get I-465 shields? http://maps.google.com/maps?hl=en&ll=35.514051,-79.784153&spn=0.003982,0.008256&gl=us&t=m&z=18
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on December 09, 2012, 05:56:38 PM
Quote from: NE2 on December 09, 2012, 03:17:34 PM
Quote from: deanej on December 09, 2012, 12:30:45 PM
To top it off, NY 342 is marked as the more heavily traveled road, as evidenced when you zoom out (this seems to be a common problem, actually, and is still an issue with I-69).
It's also an issue with Interstates vs. other freeways. Look ma, no Turnpike! http://maps.google.com/maps?hl=en&ll=28.396233,-80.848389&spn=4.406221,8.453979&gl=us&t=m&z=8

PS: How did this get I-465 shields? http://maps.google.com/maps?hl=en&ll=35.514051,-79.784153&spn=0.003982,0.008256&gl=us&t=m&z=18
I-465 was briefly extended along the entirety of I-74 because people are stupid and Google doesn't review user contributions very well. So when that was retracted, I guess this remained because no one caught the initial error that the service area roadways were labeled as Interstates. Why I wish OSM would implement route directions, so that I don't have to ever use Google Maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on December 09, 2012, 06:00:45 PM
Quote from: NE2 on December 09, 2012, 03:17:34 PM
Quote from: deanej on December 09, 2012, 12:30:45 PM
To top it off, NY 342 is marked as the more heavily traveled road, as evidenced when you zoom out (this seems to be a common problem, actually, and is still an issue with I-69).
It's also an issue with Interstates vs. other freeways. Look ma, no Turnpike! http://maps.google.com/maps?hl=en&ll=28.396233,-80.848389&spn=4.406221,8.453979&gl=us&t=m&z=8
It's a weird problem too; click on that link and zoom in once towards Orlando. You'll see the state route freeways become visible, and some segments of freeway northwest of Orlando, that don't become fully visible until you zoom in once more. I wish Google maps had a filter we could use, like a checkmarked type box that we can use so we can only see certain roads and all that. In my opinion, it'd be pretty cool to zoom into somewhere like New York City and have a filter that only shows freeways, or only Interstates, stuff like that. It doesn't seem like it'd be a hard thing to implement.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 09, 2012, 06:04:27 PM
Quote from: Steve on December 09, 2012, 05:56:38 PM
Why I wish OSM would implement route directions, so that I don't have to ever use Google Maps.
http://map.project-osrm.org/ is pretty decent, though I still prefer the Goog for ease of use (since I can usually spot errors).
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on December 09, 2012, 07:37:32 PM
Quote from: Steve on December 09, 2012, 05:56:38 PM
Quote from: NE2 on December 09, 2012, 03:17:34 PM
Quote from: deanej on December 09, 2012, 12:30:45 PM
To top it off, NY 342 is marked as the more heavily traveled road, as evidenced when you zoom out (this seems to be a common problem, actually, and is still an issue with I-69).
It's also an issue with Interstates vs. other freeways. Look ma, no Turnpike! http://maps.google.com/maps?hl=en&ll=28.396233,-80.848389&spn=4.406221,8.453979&gl=us&t=m&z=8

PS: How did this get I-465 shields? http://maps.google.com/maps?hl=en&ll=35.514051,-79.784153&spn=0.003982,0.008256&gl=us&t=m&z=18
Why I wish OSM would implement route directions, so that I don't have to ever use Google Maps.

I would barely touch Google or Bing if OSM had satellite view. I'd only touch the other two for street view or birds-eye, but all we need is a pipe to get them both added to OSM. :cool:
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on December 09, 2012, 08:31:25 PM
Quote from: NE2 on December 09, 2012, 06:04:27 PM
Quote from: Steve on December 09, 2012, 05:56:38 PM
Why I wish OSM would implement route directions, so that I don't have to ever use Google Maps.
http://map.project-osrm.org/ is pretty decent, though I still prefer the Goog for ease of use (since I can usually spot errors).
I tested that out. It's a good starting concept but needs some UI work (for example, to let you know it's processing - which it does often but not always). Some of the routes are wonky and it doesn't always take your rerouting very kindly. If OSRM is going to be what happens with OSM, I'll wait until it gets out of functional beta.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 10, 2012, 11:25:24 AM
The view from the Highway Browser from CHM is nice, allowing the user to use ANY mapping service (that isn't mobile only), including street view.  Now all they need is a way to access that view outside of the Highway Browser and driving directions.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on December 15, 2012, 12:17:26 PM
Should this portion of US 9 bythe Raritan river in New Jersey be labelled as freeway? http://goo.gl/maps/hpvji It's marked as a motorway on OSM and it does have a few interchanges in this segment, so I don't see why it isn't.
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on December 15, 2012, 11:59:48 PM
Quote from: Some_Person on December 15, 2012, 12:17:26 PM
Should this portion of US 9 bythe Raritan river in New Jersey be labelled as freeway? http://goo.gl/maps/hpvji It's marked as a motorway on OSM and it does have a few interchanges in this segment, so I don't see why it isn't.

To the letter, that's probably fair. However, from a cartographic standpoint, there's an argument to be made for visually distinguishing US 9, not a freeway overall, from the adjacent GSP, which is a freeway for most of its length. One of the hallmarks of superior mapmaking is exactly this kind of digesting and interpreting facts so that they are most meaningful to the user. Digital mapping services are notorious for anomalies produced by overly-strict application of parameters (labeling "BR" as "Branch" when it's supposed to mean "Business Route", for example). In this case of course, it's not wrong to say that US 9 is briefly a freeway, but it's perhaps not the most effective way to convey the nature of the road for navigation purposes.

If I were mapping the area, I'd indicate that there were interchanges along US 9, but I'd depict the road itself with a symbol distinct from the one I used for freeways.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 16, 2012, 12:31:45 AM
Quote from: empirestate on December 15, 2012, 11:59:48 PM
However, from a cartographic standpoint, there's an argument to be made for visually distinguishing US 9, not a freeway overall, from the adjacent GSP, which is a freeway for most of its length.
When you try to do this sort of on-the-fly visual distinction, it doesn't always work. What would you do if US 9 were an Interstate (such as an x95 from the Turnpike to South Amboy)? See also: I-90 and I-790/NY 49.

By the way, in both of these cases, coloring toll roads differently would work (if the GSP didn't have one-way tolling): http://www.openstreetmap.org/?lat=40.51668&lon=-74.29869&zoom=16&layers=Q http://www.openstreetmap.org/?lat=43.12111&lon=-75.22352&zoom=15&layers=Q
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on December 16, 2012, 11:44:36 AM
Quote from: NE2 on December 16, 2012, 12:31:45 AM
Quote from: empirestate on December 15, 2012, 11:59:48 PM
However, from a cartographic standpoint, there's an argument to be made for visually distinguishing US 9, not a freeway overall, from the adjacent GSP, which is a freeway for most of its length.
When you try to do this sort of on-the-fly visual distinction, it doesn't always work. What would you do if US 9 were an Interstate (such as an x95 from the Turnpike to South Amboy)? See also: I-90 and I-790/NY 49.

I'd use the same symbology and put an Interstate shield on it, unless I was making a map that specifically showed highway designation classes. For a similar example, would you show a US route as a heavier highway symbol when it meanders through congested city streets, or would you use a symbol like other similar streets on the area? An official highway map would probably set off the designated US route by symbology, but one intended for general navigation purpose might not, relying instead only on the shield symbol to denote the designation.

For the I-790 example, it depends somewhat on scale and the level of detail being shown. Some maps try to show the dual carriageway situation, but others set off I-790 as a separate, parallel roadway. Certainly I-790 is a weird enough highway that it present problems for cartographic display. I-180 in Wyoming is another...I'm sure nobody here would expect to see it labeled as a freeway, but we would expect to see it shown as an Interstate.

Quote from: NE2 on December 16, 2012, 12:31:45 AM
By the way, in both of these cases, coloring toll roads differently would work (if the GSP didn't have o
ne-way tolling): http://www.openstreetmap.org/?lat=40.51668&lon=-74.29869&zoom=16&layers=Q http://www.openstreetmap.org/?lat=43.12111&lon=-75.22352&zoom=15&layers=Q

Yes, both the GSP and the Thruway are different enough from US 9 and I-790 that they should be shown differently regardless, but I'd say that's true even if they were not toll roads.

Also, there is the ongoing struggle of whether and how to show one-way tolling, or barrier-based systems with lots of free segments. Many maps just show a road as toll overall, even though there are many routes along them that won't require any payment. That leaves something to be desired in terms of completeness, but graphically showing every case where there is or isn't a payment required can be visually confusing and may be impossible in certain cases. That's one place where digital routing can help, since it can show whether or not a toll will be paid on any given routing.
Title: Re: Incorrect highways marked on Google Maps
Post by: US71 on December 16, 2012, 07:28:18 PM
FWIW, I've been looking at Google Maps along the I-49 Corridor in Missouri: it looks as if all the upgraded interchanges have been incorporated into the map, though not all labelled.

UPDATE: there are some 49 shields along 71, including along Bruce Watkins Parkway. Still, I've found half a dozen glitches without even trying including a road that shows on satellite view south of Neosho, but not on the maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: StogieGuy7 on December 18, 2012, 11:37:54 AM
I'm too lazy to pick through all 26 pages of this thread, but am still compelled to ask whether anyone has noticed Maine's new Interstate 6?   

Plowing through the backcountry of Maine is a sleek new interstate highway who's designation was plucked from a project somewhere in Florida that could-have-been.....  https://maps.google.com/?ll=45.612116,-69.690399&spn=0.389535,0.617294&t=h&z=11 (https://maps.google.com/?ll=45.612116,-69.690399&spn=0.389535,0.617294&t=h&z=11)
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 18, 2012, 04:02:59 PM
Quote from: StogieGuy7 on December 18, 2012, 11:37:54 AM
I'm too lazy to pick through all 26 pages of this thread, but am still compelled to ask whether anyone has noticed Maine's new Interstate 6?

If you're too lazy to pick through all 26 pages, can you at least go back one page next time?

Quote from: jp the roadgeek on December 04, 2012, 05:16:57 PM
Don't know if anyone has noticed, but Maine apparently has started signing the new rooftop highway as Interstate 6.  Still a 2 lane road though :)
Title: Re: Incorrect highways marked on Google Maps
Post by: myosh_tino on December 18, 2012, 06:09:49 PM
Someone thought it was a good idea to route El Camino Real onto I-880 between Coleman Ave and US 101 and on US 101 from I-880 south to Gilroy!  :banghead: :banghead: :banghead:

http://www.google.com/maps?ll=37.341093,-121.884384&spn=0.075199,0.110378&t=m&z=13
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 18, 2012, 06:57:19 PM
Doing some minor research, it doesn't look like this is in any way inaccurate.  However, unlike how it is for SR 82, it's just an alternate (historical) name that doesn't need to be included on maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: StogieGuy7 on December 19, 2012, 09:46:12 AM
Quote from: Kacie Jane on December 18, 2012, 04:02:59 PM
If you're too lazy to pick through all 26 pages, can you at least go back one page next time?


Well, excuuuuuuuuuuuse me!   :rolleyes:
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on December 19, 2012, 11:08:46 AM
Quote from: StogieGuy7 on December 19, 2012, 09:46:12 AM
Quote from: Kacie Jane on December 18, 2012, 04:02:59 PM
If you're too lazy to pick through all 26 pages, can you at least go back one page next time?


Well, excuuuuuuuuuuuse me!   :rolleyes:

I think that was a reasonable request.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 19, 2012, 12:42:28 PM
While 26 pages is naturally unreasonable, I think one is.  I knew we had that one posted before but I didn't remember it was that close!
Title: Re: Incorrect highways marked on Google Maps
Post by: cpzilliacus on December 19, 2012, 02:09:39 PM
Quote from: PennDOTFan on September 11, 2012, 08:56:18 PM
Looks like I-6 exists in Maine now...
http://goo.gl/maps/nBlLH

Yup.  Runs all the way across the state from U.S. 201 (PQ 173) to Vanceboro (NB 4).

Must be part of the conspiracy to get that east-west toll road built across Maine.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 19, 2012, 11:23:45 PM
Quote from: kphoger on December 19, 2012, 11:08:46 AM
Quote from: StogieGuy7 on December 19, 2012, 09:46:12 AM
Quote from: Kacie Jane on December 18, 2012, 04:02:59 PM
If you're too lazy to pick through all 26 pages, can you at least go back one page next time?


Well, excuuuuuuuuuuuse me!   :rolleyes:

I think that was a reasonable request.

It was a reasonable request in my eyes.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on December 21, 2012, 08:31:00 PM
Now the NJ turnpike is now labeled in 3 ways.
1 NJTP
2 NJ Turnpike
3 New Jersey Turnpike
:banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on December 22, 2012, 03:28:23 PM
Lots of things wrong with this
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1294.photobucket.com%2Falbums%2Fb619%2Fkherm2000%2F83b.png&hash=7897ccded1a63e759b0c312e1332d5a587f56705)
1. Before I-83B meets George St. the expressway should be orange
2. I-83B should end at George St.
3. Does I-83B even exist?
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 22, 2012, 04:17:16 PM
Quote from: Roadgeek2500 on December 22, 2012, 03:28:23 PM
3. Does I-83B even exist?

It's better than the alternative (signing it as just I-83, since Google can't figure out how to do banners).
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on December 22, 2012, 06:01:46 PM
Oh does it mean Business I-83, I didn't think of that  :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on December 28, 2012, 02:26:30 PM
Looks like I-70 found its way into NC http://goo.gl/maps/HzjiF

Also, while talking about NC, here's something that Google has that actually seems like a good thing: http://goo.gl/maps/zQ8Ac a lot of numbered routes are indicated here, in areas like PA, 4 digit or more numbered-routes are rarely given shields
Title: Re: Incorrect highways marked on Google Maps
Post by: BrianP on December 28, 2012, 03:19:46 PM
Quote from: Some_Person on December 28, 2012, 02:26:30 PM
Looks like I-70 found its way into NC http://goo.gl/maps/HzjiF

Also, while talking about NC, here's something that Google has that actually seems like a good thing: http://goo.gl/maps/zQ8Ac a lot of numbered routes are indicated here, in areas like PA, 4 digit or more numbered-routes are rarely given shields
So did I-465:
https://maps.google.com/maps?hl=en&ll=35.498133,-79.732933&spn=0.290132,0.528374&t=m&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on December 28, 2012, 04:30:32 PM
Quote from: BrianP on December 28, 2012, 03:19:46 PM
Quote from: Some_Person on December 28, 2012, 02:26:30 PM
Looks like I-70 found its way into NC http://goo.gl/maps/HzjiF

Also, while talking about NC, here's something that Google has that actually seems like a good thing: http://goo.gl/maps/zQ8Ac a lot of numbered routes are indicated here, in areas like PA, 4 digit or more numbered-routes are rarely given shields
So did I-465:
https://maps.google.com/maps?hl=en&ll=35.498133,-79.732933&spn=0.290132,0.528374&t=m&z=12

Zoom in towards the 465 shield. You'll start randomly seeing shields off to the left side of the road! :eyebrow:

Actually, that's a visitor's center, I think. :pan: Still wrong, though.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on December 28, 2012, 08:52:56 PM
It looks like Interstate 14 found its way onto some back roads in SC: http://goo.gl/maps/dKTRu
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 28, 2012, 10:37:40 PM
Somehow "State Road S-14-556" from TIGER became I-14...
Title: Re: Incorrect highways marked on Google Maps
Post by: swbrotha100 on December 29, 2012, 06:26:33 PM
Google shows I-515 in Nevada extended to where US 95 splits from US 93 near Boulder City. If you didn't know any better, the map gives one the impression that the freeway portion of US 93 is longer than it currently is.

On a side note, I was hoping that the Boulder City bypass would have been at least started by now, if only to see how far south (east) the I-515 designation would go, and if it would make it across the Hoover Dam Bypass into Arizona.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadfro on December 29, 2012, 06:46:11 PM
Quote from: swbrotha100 on December 29, 2012, 06:26:33 PM
Google shows I-515 in Nevada extended to where US 95 splits from US 93 near Boulder City. If you didn't know any better, the map gives one the impression that the freeway portion of US 93 is longer than it currently is.

On a side note, I was hoping that the Boulder City bypass would have been at least started by now, if only to see how far south (east) the I-515 designation would go, and if it would make it across the Hoover Dam Bypass into Arizona.

Not necessarily an egregious error...it's only 2.5 miles longer than it should be, but it does carry the I-515 designation past a SB access road intersection and the signal at Railroad Pass Casino.

I was also hoping that the Boulder City Bypass would have started construction on phase 1 by now. I think that was NDOT's original goal to have something ready to go during this calendar year. However, the potential to toll the bypass (as being studied by NDOT & RTC) and/or make it part of future I-11 may have altered the timeline.

The Boulder City Bypass won't carry the I-515 designation past the future US 93/US 95 interchange. Future I-11 would fill the need to carry an interstate highway across the Hoover Dam bridge into Arizona (eventually supplanting I-515).
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on December 29, 2012, 07:13:48 PM
FL 404 shouldn't be colored orange here; it starts off at a signalized diamond interchange and has some signalized intersections before turning into a freeway at the interchange with US 1: http://goo.gl/maps/FipnN
Title: Re: Incorrect highways marked on Google Maps
Post by: KEK Inc. on December 30, 2012, 01:41:06 AM
Quote from: myosh_tino on December 18, 2012, 06:09:49 PM
Someone thought it was a good idea to route El Camino Real onto I-880 between Coleman Ave and US 101 and on US 101 from I-880 south to Gilroy!  :banghead: :banghead: :banghead:

http://www.google.com/maps?ll=37.341093,-121.884384&spn=0.075199,0.110378&t=m&z=13

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2Fc%2Fcc%2FEl_Camino_Real_California_2.JPG&hash=e0ef33c24f525f129ce4346eddd17a0dc16b88b7)

I've seen these bad boys on US-101 south of Bernal Rd.  I'm not sure if Caltrans declared I-880 and US-101 between I-880 and Bernal Rd. to be part of the new historic route.

Technically, the historic road doesn't really follow any current highway.  If anything, it should take CA-17 south to Santa Cruz.

http://upload.wikimedia.org/wikipedia/commons/2/21/1920_Alta_California_mission_trail.jpg
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on December 31, 2012, 08:05:11 AM
Quote from: Some_Person on December 28, 2012, 02:26:30 PM
Looks like I-70 found its way into NC http://goo.gl/maps/HzjiF

It seems to appear randomly along US-70 in NC. And at first glance the I-74 and US-74 thing looks like an error.

I-510 near New Orleans is drawn in yellow :banghead:: http://goo.gl/maps/5XKVY

Edit: WTF??? I've found I-70 in OK and TX too!
Title: Re: Incorrect highways marked on Google Maps
Post by: ftballfan on December 31, 2012, 03:02:01 PM
US-10 (the Farwell Bypass) west of US-127 in MI is drawn as a divided highway despite being a fully access controlled freeway (and has been one since it was built in the 1970s) from US-127 to west of M-115.

Then, Kingery and Roosevelt are drawn as full freeways despite only being expressways.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on January 01, 2013, 12:12:30 AM
They probably are expressways. Google uses the same color for expressways and freeways, which is confusing.

Recently they've been "cracking down" on yellow expressways, and also short freeways, and even long but "disconnected" ones. :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on January 01, 2013, 05:32:11 PM
Preserving old route alignments (such as PA 100, which, until 2003, went south of West Chester to connect to DE 100) is good, but the old PA 100 alignment is far from "historic." :pan:

http://goo.gl/maps/AROx7 (http://goo.gl/maps/AROx7)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on January 07, 2013, 10:47:45 PM
Fictional cities.  They happen in Google too!

http://tools.geofabrik.de/mc/?mt0=mapnik&mt1=googlemapmaker&lon=-75.13136&lat=3.44456&zoom=15

Wonder if this will ever make it into the main map.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on January 12, 2013, 10:33:04 PM
Should we just consider it common sense now that Google Maps doesn't seem to like labeling freeway segments on State or US highways with the orange color anymore?

NJ 18: http://goo.gl/maps/OnTbR
US 202 in NJ: http://goo.gl/maps/WEZke
US 209 in PA: http://goo.gl/maps/mSmhg
US 222 Kutztown Bypass: http://goo.gl/maps/xJwqN

There's countless other examples, personally I think Google Maps should give every member of this forum some rights to edit the maps and approve the edit all in one step
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on January 12, 2013, 10:40:58 PM
But then we'd have things like I-366 in VA, with a bit of preferential routing because of its 85 MPH speed limit.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on January 13, 2013, 09:13:22 AM
This thread would die if we weren't allowed to post the latest in Google's mass-demotion of short, disconnected freeways.

Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on January 13, 2013, 12:00:42 PM
Here are some screw-ups that I have noticed recently with Google Maps:

- The proposed I-66 has been posted on Google Maps in KY: http://goo.gl/maps/w71Jv, http://goo.gl/maps/DU08f, http://goo.gl/maps/J8fvX, and http://goo.gl/maps/TH51W
- The Audubon Pkwy between Henderson, KY and Owensboro, KY is now I-369: http://goo.gl/maps/gzFmw
- I-310 and I-510 have been decommissioned and turned to arterials in New Orleans: http://goo.gl/maps/W2TVJ and http://goo.gl/maps/d1kJZ
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on January 26, 2013, 01:36:11 AM
Quote from: codyg1985 on January 13, 2013, 12:00:42 PM
Here are some screw-ups that I have noticed recently with Google Maps:

- The Audubon Pkwy between Henderson, KY and Owensboro, KY is now I-369: http://goo.gl/maps/gzFmw

And the fun thing about that one is that it still might not become I-369, and instead might become another I-X69.  That number isn't even set in stone yet.
Title: Re: Incorrect highways marked on Google Maps
Post by: Jim on January 26, 2013, 04:04:33 PM
Quote from: PennDOTFan on September 11, 2012, 08:56:18 PM
Looks like I-6 exists in Maine now...
http://goo.gl/maps/nBlLH

I, and I am sure many others, reported this to Google back when it was first noticed.  I got a message today saying it's not going to be fixed soon because:

Quote from: GoogleEmailReplythe problem you reported isn't easy for us to fix at this time
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 31, 2013, 11:12:05 PM
http://maps.google.com/maps?hl=en&ll=4.696839,-74.055233&spn=0.002438,0.004128&gl=us&t=m&z=19
Autopista ~[0x01]55?
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on February 01, 2013, 02:44:51 PM
Quote from: NE2 on January 31, 2013, 11:12:05 PM
http://maps.google.com/maps?hl=en&ll=4.696839,-74.055233&spn=0.002438,0.004128&gl=us&t=m&z=19
Autopista ~[0x01]55?

The tilde is logic shorthand for not.  So Google Maps is just letting you know that the highway is not numbered [0x01]55–which is correct.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on February 01, 2013, 02:57:11 PM
Quote from: kphoger on February 01, 2013, 02:44:51 PM
Quote from: NE2 on January 31, 2013, 11:12:05 PM
http://maps.google.com/maps?hl=en&ll=4.696839,-74.055233&spn=0.002438,0.004128&gl=us&t=m&z=19
Autopista ~[0x01]55?

The tilde is logic shorthand for not.  So Google Maps is just letting you know that the highway is not numbered [0x01]55–which is correct.

Every answer just opens more questions.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on February 01, 2013, 03:18:20 PM
Quote from: kphoger on February 01, 2013, 02:44:51 PM
Quote from: NE2 on January 31, 2013, 11:12:05 PM
http://maps.google.com/maps?hl=en&ll=4.696839,-74.055233&spn=0.002438,0.004128&gl=us&t=m&z=19
Autopista ~[0x01]55?

The tilde is logic shorthand for not.  So Google Maps is just letting you know that the highway is not numbered [0x01]55–which is correct.

...thus, it's really a limited-unlimited-access freeway in Alanland.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on February 02, 2013, 05:40:29 PM
If posting errors from outside the US is allowed, then Google must erase the A-23 designation from Spanish A-22 now: https://maps.google.es/maps?ll=41.999305,-0.041885&spn=0.284738,0.617294&t=m&z=11
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on February 02, 2013, 09:28:49 PM
Step into the wayback machine, as Google Maps presents GA 229, which was decommissioned in 1982:
https://maps.google.com/?ll=33.47899,-83.684235&spn=0.442713,0.529404&t=h&z=11
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on February 03, 2013, 08:30:14 AM
Quote from: CNGL-Leudimin on February 02, 2013, 05:40:29 PM
... Google must...

:-D  Yeah, right!
Title: Re: Incorrect highways marked on Google Maps
Post by: jp the roadgeek on February 03, 2013, 11:30:54 AM
Quote from: CNGL-Leudimin on December 31, 2012, 08:05:11 AM
Quote from: Some_Person on December 28, 2012, 02:26:30 PM
Looks like I-70 found its way into NC http://goo.gl/maps/HzjiF

It seems to appear randomly along US-70 in NC. And at first glance the I-74 and US-74 thing looks like an error.

I-510 near New Orleans is drawn in yellow :banghead:: http://goo.gl/maps/5XKVY

Edit: WTF??? I've found I-70 in OK and TX too!

And Arkansas
Title: Re: Incorrect highways marked on Google Maps
Post by: webfil on February 03, 2013, 05:19:54 PM
Quote from: CNGL-Leudimin on December 31, 2012, 08:05:11 AM
Quote from: Some_Person on December 28, 2012, 02:26:30 PM
Looks like I-70 found its way into NC http://goo.gl/maps/HzjiF
I-510 near New Orleans is drawn in yellow :banghead:: http://goo.gl/maps/5XKVY

There seem to be an issue about Google's standards on what is a freeway a what is not.

Moderators and Google Reviewers keep contributors from giving short freeways and freeway sections of typically non-freeway road their right classification.

Autoroute Dufferin-Montmorency (A-440 and A-40) in Québec City (http://goo.gl/maps/z7tVy) has one intersection, though it is not even marked as an expressway, but a "primary route" despite being a freeway on the rest of its course. Some Google Reviewer locked it after an edit war and the route is no longer editable.

Autoroute Papineau (A-19) freeway (http://goo.gl/maps/YW0Id) section in Laval has an edit war also undergoing, as it is not marked as a freeway.

Short A-730, A-930 (south shore Montréal) (http://goo.gl/maps/vJdTR) and A-85 (eastern Québec) (http://goo.gl/maps/n6AN1) freeways have been recently marked as freeway, although I would not be surprised that some moderator would rank them down in short term.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on February 03, 2013, 05:45:23 PM
And much of QC 185 has also been marked as a freeway despite being two lane road.  At least it's not an inverse of what it's supposed to be now.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on February 04, 2013, 12:48:01 AM
The new FL 451 is still marked as FL 429 despite the new FL 429 is marked as it should.
http://maps.google.com/maps?q=Apopka,+FL&hl=en&ll=28.655043,-81.53512&spn=0.032161,0.055189&sll=27.698638,-83.804601&sspn=8.300816,14.128418&oq=apo&hnear=Apopka,+Orange,+Florida&t=m&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 04, 2013, 08:01:02 PM
Quote from: roadman65 on February 04, 2013, 12:48:01 AM
The new FL 451 is still marked as FL 429 despite the new FL 429 is marked as it should.
http://maps.google.com/maps?q=Apopka,+FL&hl=en&ll=28.655043,-81.53512&spn=0.032161,0.055189&sll=27.698638,-83.804601&sspn=8.300816,14.128418&oq=apo&hnear=Apopka,+Orange,+Florida&t=m&z=14

I love how they think that a bridge is a tunnel (http://goo.gl/maps/m7YjC). #FAIL
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 05, 2013, 03:58:00 AM
Quote from: rickmastfan67 on February 04, 2013, 08:01:02 PM
I love how they think that a bridge is a tunnel (http://goo.gl/maps/m7YjC). #FAIL
I think they actually forgot to change those bridges from proposed.

And just to the south, check out exit 30.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex on February 06, 2013, 01:14:22 PM
Google maps shows all of S.C. 16 in Columbia as S.C. 40.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 06, 2013, 01:53:30 PM
Quote from: Alex on February 06, 2013, 01:14:22 PM
Google maps shows all of S.C. 16 in Columbia as S.C. 40.
Most likely because it was several S-40-* routes.
Title: Re: Incorrect highways marked on Google Maps
Post by: Duke87 on February 07, 2013, 10:37:31 PM
Colorado's 470 Tollway has been promoted to an interstate:
https://maps.google.com/?ll=39.827654,-104.741077&spn=0.068816,0.123253&t=m&z=13

I approve of this error.
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on February 08, 2013, 05:15:09 AM
A subtle one, but the entire length of Morse Road in Franklin and Licking Counties, Ohio is labeled "Morse Crossing". (http://goo.gl/maps/vlXpG)

"Morse Crossing" is actually the name of a different street that, er, crosses Morse Road. (http://goo.gl/maps/Hz4FG)
Title: Re: Incorrect highways marked on Google Maps
Post by: CTInterstate on February 09, 2013, 07:18:43 PM
The freeway sction of US 6 in WIllmantic is marked as yellow.... :confused:
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on February 09, 2013, 07:56:52 PM
Quote from: CTInterstate on February 09, 2013, 07:18:43 PM
The freeway sction of US 6 in WIllmantic is marked as yellow.... :confused:
Probably they are waiting for I-366.
Title: Re: Incorrect highways marked on Google Maps
Post by: ilvny on February 11, 2013, 12:46:49 PM
I'm not sure if this has already been mentioned, but Route 1 in Philadelphia is labeled with two street names.

For example, Route 1 is listed as Roosevelt Blvd and Lincoln Hwy in Philadelphia, when it should only say Roosevelt Blvd.  Lincoln Hwy is the Bucks County portion of Route 1 up to Business Route 1.  The "Lincoln Highway" name continues on Business Route 1.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on February 12, 2013, 07:57:53 AM
Proof of Google being crazy: they use the most loosely-defined "technical" name for things in addition to the posted name (The general US 1 corridor from US 30 to New York is part of Lincoln Highway.), but demote freeways left and right when a caveman could tell they're wrong. :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on February 12, 2013, 09:47:50 PM
Hmm, here's a new one for me: http://goo.gl/maps/fhuYu
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on February 12, 2013, 09:55:59 PM
A random kentucky state route? The error isn't obvious to me.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on February 12, 2013, 09:56:14 PM
Quote from: Steve on February 12, 2013, 09:47:50 PM
Hmm, here's a new one for me: http://goo.gl/maps/fhuYu

Erroneous road sign alert!  This (http://goo.gl/maps/689iF) should have a US shield!
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on February 12, 2013, 10:00:59 PM
Quote from: ilvny on February 11, 2013, 12:46:49 PM
I'm not sure if this has already been mentioned, but Route 1 in Philadelphia is labeled with two street names.

For example, Route 1 is listed as Roosevelt Blvd and Lincoln Hwy in Philadelphia, when it should only say Roosevelt Blvd.  Lincoln Hwy is the Bucks County portion of Route 1 up to Business Route 1.  The "Lincoln Highway" name continues on Business Route 1.
Princeton Avenue in Trenton, NJ is listed also as Lincoln Highway.  That may be the old US 1 through town that was the original Lincoln Highway, but its not is officially designated name now.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on February 12, 2013, 10:37:44 PM
Quote from: vtk on February 12, 2013, 09:55:59 PM
A random kentucky state route? The error isn't obvious to me.
Is it not a US 1602 to you? I didn't know there was even a 402.
Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on February 13, 2013, 07:10:13 AM
Well now most of I-74 is multiplexed with I-465 on Google Maps, except for a few sections in NC.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on February 13, 2013, 07:43:11 AM
Quote from: Steve on February 12, 2013, 10:37:44 PM
Quote from: vtk on February 12, 2013, 09:55:59 PM
A random kentucky state route? The error isn't obvious to me.
Is it not a US 1602 to you? I didn't know there was even a 402.

All I saw when I clicked the link was a marker for one result of searching "KY 1123, KY".

https://www.aaroads.com/forum/index.php?topic=5716.0
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on February 14, 2013, 12:37:16 AM
Quote from: vtk on February 13, 2013, 07:43:11 AM
Quote from: Steve on February 12, 2013, 10:37:44 PM
Quote from: vtk on February 12, 2013, 09:55:59 PM
A random kentucky state route? The error isn't obvious to me.
Is it not a US 1602 to you? I didn't know there was even a 402.

All I saw when I clicked the link was a marker for one result of searching "KY 1123, KY".

https://www.aaroads.com/forum/index.php?topic=5716.0
Yeah, good point, I forgot. Shame on me.

http://goo.gl/maps/beHba
Title: Re: Incorrect highways marked on Google Maps
Post by: amroad17 on February 14, 2013, 01:52:10 AM
It's just the beginning of a "new" US 2 spur route extending from Ashland, WI to Ashland, KY.  The "new" route would be extended east via new terrain to an interchange with I-64 west of Morehead, KY (built like the AA Highway).  It would be co-signed with I-64 to exit 185 where the "new" route would head into Ashland along current KY 180 and US 60.  US 60 would be co-signed on I-64 from exit 181 to exit 191 where it would head north on US 23 to its current point east to Huntington, WV.  This "routing" would take many years to accomplish, but this "new" US highway has to start somewhere. ;-) :D

Besides, since there is only a US 202 and US 302, why not have a US 1602--it would be rather unique.

If someone cares to "expound" on this in fictional highways...
Title: Re: Incorrect highways marked on Google Maps
Post by: iowahighways on February 24, 2013, 12:59:08 PM
Since when did I-465 multiplex with I-74... in Iowa? http://goo.gl/maps/55fEk

Not only that, the city of Bettendorf has disappeared from the map.
Title: Re: Incorrect highways marked on Google Maps
Post by: Big John on February 24, 2013, 01:17:51 PM
Quote from: iowahighways on February 24, 2013, 12:59:08 PM
Since when did I-465 multiplex with I-74... in Iowa? http://goo.gl/maps/55fEk

And throughout all of the western I-74 to Cincinnati
Title: Re: Incorrect highways marked on Google Maps
Post by: pianocello on February 24, 2013, 02:11:43 PM
Quote from: iowahighways on February 24, 2013, 12:59:08 PM
Not only that, the city of Bettendorf has disappeared from the map.

Meh. Bettendorf isn't all that important anyway.
[/regional bias]
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on February 25, 2013, 10:14:09 AM
Quote from: iowahighways on February 24, 2013, 12:59:08 PM
Since when did I-465 multiplex with I-74... in Iowa? http://goo.gl/maps/55fEk

I-465 seems to have also met up with Interstates 73 and 74 in North Carolina (https://maps.google.com/?ll=35.687976,-79.806747&spn=0.248733,0.441513&t=m&z=11).
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on February 25, 2013, 07:45:14 PM
Quote from: pianocello on February 24, 2013, 02:11:43 PM
Quote from: iowahighways on February 24, 2013, 12:59:08 PM
Not only that, the city of Bettendorf has disappeared from the map.

Meh. Bettendorf isn't all that important anyway.
[/regional bias]
You forgot the [regional bias] opening tag, there. Also, East Moline loves you.
Title: Re: Incorrect highways marked on Google Maps
Post by: Grzrd on February 25, 2013, 10:05:47 PM
The grading and structures project in Union City, TN (http://maps.google.com/maps?q=Union+City,+TN&hl=en&ll=36.450837,-89.070797&spn=0.03666,0.076818&sll=36.445245,-89.058781&sspn=0.053509,0.076818&oq=union+city+tn&t=h&hnear=Union+City,+Obion,+Tennessee&z=14) is now I-69.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on February 26, 2013, 07:52:35 AM
I-14 on random surface streets in Georgia. (http://goo.gl/maps/VXXrM) EDIT: South Carolina, oops. :P
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on February 26, 2013, 10:20:07 AM
Quote from: Steve on February 12, 2013, 09:47:50 PM
Hmm, here's a new one for me: http://goo.gl/maps/fhuYu

Heh. I was just through there earlier this month.

Here's another one from Kentucky I found:

http://goo.gl/maps/Uil4u

KY 67 appears on the four-digit route that is the old routing of US 23.
Title: Re: Incorrect highways marked on Google Maps
Post by: kharvey10 on February 26, 2013, 10:37:19 AM
https://maps.google.com/maps?q=normal,+il&oe=utf-8&client=firefox-a&hnear=Normal,+McLean,+Illinois&gl=us&t=h&z=12

Very easy to spot the mistake
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on February 26, 2013, 12:34:10 PM
Quote from: kharvey10 on February 26, 2013, 10:37:19 AM
https://maps.google.com/maps?q=normal,+il&oe=utf-8&client=firefox-a&hnear=Normal,+McLean,+Illinois&gl=us&t=h&z=12

Very easy to spot the mistake

what, no I-465 in North Carolina?  it's along every other segment of I-74 now - except for the ring road around Indianapolis, where it is correct.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on February 26, 2013, 03:48:54 PM
Quote from: Roadsguy on February 26, 2013, 07:52:35 AM
I-14 on random surface streets in Georgia. (http://goo.gl/maps/VXXrM)
South Carolina. Somehow S-14-* became I-14.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on February 26, 2013, 05:24:32 PM
The I-70 thing is still there, all over US-70.

Say hi to I-11 (https://maps.google.es/maps?ll=34.590824,-113.480873&spn=0.170992,0.308647&t=m&z=12). Another future has gone wrong :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on February 27, 2013, 08:30:19 AM
Quote from: NE2 on February 26, 2013, 03:48:54 PM
Quote from: Roadsguy on February 26, 2013, 07:52:35 AM
I-14 on random surface streets in Georgia. (http://goo.gl/maps/VXXrM)
South Carolina. Somehow S-14-* became I-14.

Oops... I was following I-95 up to see where the 3dis were, and I never noticed the SC border. :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: KEK Inc. on February 27, 2013, 09:06:27 AM
Quote from: CNGL-Leudimin on February 26, 2013, 05:24:32 PM
The I-70 thing is still there, all over US-70.

Say hi to I-11 (https://maps.google.es/maps?ll=34.590824,-113.480873&spn=0.170992,0.308647&t=m&z=12). Another future has gone wrong :banghead:

Hey, maybe Google wants AZ and NV to make an I-11.  :P  Google has jumped the gun on some, including I-305 in Sacramento.  (I think they removed that.) 

At least I-11 is in serious talks.
Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on February 28, 2013, 07:48:14 AM
A small part of US 75 just north of I-45's terminus in Dallas is now I-345 (http://goo.gl/maps/GTJeG).
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on February 28, 2013, 08:27:22 AM
Quote from: codyg1985 on February 28, 2013, 07:48:14 AM
A small part of US 75 just north of I-45's terminus in Dallas is now I-345 (http://goo.gl/maps/GTJeG).
That's correct. I-345 isn't signed, but it is there on paper :nod:
Title: Re: Incorrect highways marked on Google Maps
Post by: OCGuy81 on February 28, 2013, 08:58:07 AM
Apologies if this made it on here already, but I saw signs on a recent trip to Portland that I thought were incorrect, and it appears Google thinks the same.

OR-99W and OR-10 go all the way into downtown Portland?  It was my understanding 99W ended at the I-5 interchange a bit further south, and OR-10 ended further south as well (at the intersection with Barbur, IIRC)

http://goo.gl/maps/4mSO3 (http://goo.gl/maps/4mSO3)
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on March 01, 2013, 02:31:35 AM
That's ODOT not being clear about OR 10 and 99W.
At this point, I'm not sure ODOT knows where the two highways end. On one hand, OR 99W ends at I-5(294). On another, according to signs in the field, ODOT maps, wherever you see it, it ends at US 26 with OR 10... which ends at OR 99W at the northern end of SW Capitol Highway...

Also, US 26 either follows I-405, SW Broadway/Sheridan, 3rd, Arthur, Kelly/Naito (per signs and ODOT) or Market/Clay, Naito (and Kelly) per AASHTO.

Can't blame Google for this one. You can blame them for OR 224 being marked as a freeway along the Milwaukie Expressway, however...
Title: Re: Incorrect highways marked on Google Maps
Post by: OCGuy81 on March 01, 2013, 09:52:41 AM
Thanks Bickendan.  That whole area is a complete mess!  I wanted to follow US 26 through Portland after taking my kids to the zoo.  From 405, it's a very confusing route to the Ross Island Bridge with all the turns.  Managed to do okay, but yikes! Even looking at aeiral images makes one scratch their head!
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on March 01, 2013, 07:07:52 PM
I-90B. What the hell? Since when did Montana have an "I-90B"? Did Google mean to have that as I-90 Bus or I-90 "Bypass"?
http://goo.gl/maps/d2bMl

And who could forget the infamous "US 210" (Which is Secondary Route 210)?
http://goo.gl/maps/MK2bL
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 02, 2013, 01:00:21 AM
Quote from: Billy F 1988 on March 01, 2013, 07:07:52 PM
I-90B. What the hell? Since when did Montana have an "I-90B"? Did Google mean to have that as I-90 Bus or I-90 "Bypass"?
http://goo.gl/maps/d2bMl

That's Google's half-ass way to identify a "Business" Interstate.  Why couldn't they just use the Green Shield....
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on March 02, 2013, 02:50:47 AM
Figures. Lazy bums at Screw-gle can't even get half their shit right. I say Screw-gle because they're mainly a bunch of rookie geeks who can't tell the difference between an Interstate and a Business Route from the holes in their you-know-whats!  :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 02, 2013, 03:40:05 AM
Ooh ooh! I know what! Their hands?
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on March 02, 2013, 03:47:02 AM
Probably. Or their goats!  :sombrero:
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on March 02, 2013, 05:04:00 AM
Quote from: OCGuy81 on March 01, 2013, 09:52:41 AM
Thanks Bickendan.  That whole area is a complete mess!  I wanted to follow US 26 through Portland after taking my kids to the zoo.  From 405, it's a very confusing route to the Ross Island Bridge with all the turns.  Managed to do okay, but yikes! Even looking at aeiral images makes one scratch their head!

It's the result of the southern portion of I-405 destroying the street grid of south downtown Portland when the freeway was built. Once you've gone through there a few times, the layout makes sense and works fairly well (well, when it isn't gridlocked during rush hour, lol) for what it is.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on March 02, 2013, 09:16:26 AM
Quote from: rickmastfan67 on March 02, 2013, 01:00:21 AM
Quote from: Billy F 1988 on March 01, 2013, 07:07:52 PM
I-90B. What the hell? Since when did Montana have an "I-90B"? Did Google mean to have that as I-90 Bus or I-90 "Bypass"?
http://goo.gl/maps/d2bMl

That's Google's half-ass way to identify a "Business" Interstate.

Better than their no-assed way of identifying a business Interstate or any other bannered route most of the time...
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on March 14, 2013, 08:21:50 PM
I've noticed 2 highways in Pennsylvania that suffered the orange-to-yellow color transformation;
PA 248(Which although was marked a freeway from US 209 to PA 873, it's really only a freeway from 873 to Club Road): http://goo.gl/maps/2FE8m

US 209 from PA 33 to I-80:http://goo.gl/maps/fFsts
Due to the fact that there's no interchanges and there's even a signaled intersection, I'd agree with this change. I've read tons of mixed opinions on the status of this segment of 209.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on March 14, 2013, 11:39:47 PM
Quote from: Some_Person on March 14, 2013, 08:21:50 PM

US 209 from PA 33 to I-80:http://goo.gl/maps/fFsts
Due to the fact that there's no interchanges and there's even a signaled intersection, I'd agree with this change. I've read tons of mixed opinions on the status of this segment of 209.
There can't be mixed opinions. It has a signal, ergo it is not a freeway.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 15, 2013, 12:02:37 AM
The new SR 429 alignment is freeway northbound but surface southbound: http://maps.google.com/maps?hl=en&ll=28.666002,-81.542802&spn=0.034342,0.066047&gl=us&t=m&z=15
And a random piece of the Turnpike still disappears when you zoom out: http://maps.google.com/maps?hl=en&ll=28.567638,-81.309814&spn=2.199826,4.22699&gl=us&t=m&z=9
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on March 15, 2013, 08:31:15 AM
Quote from: Steve on March 14, 2013, 11:39:47 PM
Quote from: Some_Person on March 14, 2013, 08:21:50 PM

US 209 from PA 33 to I-80:http://goo.gl/maps/fFsts
Due to the fact that there's no interchanges and there's even a signaled intersection, I'd agree with this change. I've read tons of mixed opinions on the status of this segment of 209.
There can't be mixed opinions. It has a signal, ergo it is not a freeway.

It's "expressway," and it was marked as that along with the PA 248 example last time I used Map Maker (long since given up on it). I have no idea why they demoted it, since it's one of the best examples of "expressway" in the state (like US 222 near Allentown), which calls freeways "expressways" all the time, along with most if not all of the northeast.
Title: Re: Incorrect highways marked on Google Maps
Post by: JMoses24 on March 15, 2013, 09:07:51 AM
Quote from: codyg1985 on February 13, 2013, 07:10:13 AM
Well now most of I-74 is multiplexed with I-465 on Google Maps, except for a few sections in NC.

As of this morning, it's STILL that way from near Harrison, Ohio to the Quad Cities of IL/IA. It's supposed to be multiplexed with I-465 only along the Indianapolis beltway. Once it's off there, it's supposed to be on its own. It isn't apparently multiplexed with 465 anywhere from the I-275 loop in Cincinnati to where the western segment of 74 terminates, nor once it takes the turn west onto I-280 in the Quad Cities. I can't find how to remove those shields though, or I'd have done it.
Title: Re: Incorrect highways marked on Google Maps
Post by: A.J. Bertin on March 15, 2013, 11:14:45 AM
Quote from: JMoses24 on March 15, 2013, 09:07:51 AM
Quote from: codyg1985 on February 13, 2013, 07:10:13 AM
Well now most of I-74 is multiplexed with I-465 on Google Maps, except for a few sections in NC.

As of this morning, it's STILL that way from near Harrison, Ohio to the Quad Cities of IL/IA. It's supposed to be multiplexed with I-465 only along the Indianapolis beltway. Once it's off there, it's supposed to be on its own. It isn't apparently multiplexed with 465 anywhere from the I-275 loop in Cincinnati to where the western segment of 74 terminates, nor once it takes the turn west onto I-280 in the Quad Cities. I can't find how to remove those shields though, or I'd have done it.
Quote from: JMoses24 on March 15, 2013, 09:07:51 AM
Quote from: codyg1985 on February 13, 2013, 07:10:13 AM
Well now most of I-74 is multiplexed with I-465 on Google Maps, except for a few sections in NC.

As of this morning, it's STILL that way from near Harrison, Ohio to the Quad Cities of IL/IA. It's supposed to be multiplexed with I-465 only along the Indianapolis beltway. Once it's off there, it's supposed to be on its own. It isn't apparently multiplexed with 465 anywhere from the I-275 loop in Cincinnati to where the western segment of 74 terminates, nor once it takes the turn west onto I-280 in the Quad Cities. I can't find how to remove those shields though, or I'd have done it.

A week or two ago I reported this error through Google Maps. The following day I received a note from them saying that they are unable to process the correction right now. Sounds like it's some technical error that the folks at Google can't quite figure out. LOL
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 15, 2013, 11:55:09 AM
US 11 is shown as not existing from Morely-Potsdam Rd to the Potsdam village line on most zoom levels.  Never thought I'd see one so close to college.

Quote from: Steve on March 14, 2013, 11:39:47 PM
Quote from: Some_Person on March 14, 2013, 08:21:50 PM

US 209 from PA 33 to I-80:http://goo.gl/maps/fFsts
Due to the fact that there's no interchanges and there's even a signaled intersection, I'd agree with this change. I've read tons of mixed opinions on the status of this segment of 209.
There can't be mixed opinions. It has a signal, ergo it is not a freeway.
My take is that if there's one lone light on what is otherwise a freeway, then it's a freeway on either side of the light, but not at the light.  No way to show that on a map though.  Since there's also a RIRO on each side near PA 33 this example is just one of those things that's really hard to classify, acting both like a freeway and an expressway.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on March 18, 2013, 07:40:14 PM
Quote from: vdeane on March 15, 2013, 11:55:09 AM
My take is that if there's one lone light on what is otherwise a freeway, then it's a freeway on either side of the light
In that case, 5th Ave. in Manhattan is an expressway everywhere except at traffic lights.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 18, 2013, 10:40:16 PM
There's the "otherwise a freeway" part - limited access, overpasses, etc. - in between two stoplights would likely be "not a freeway".  I'm thinking of stuff like NY 204.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on March 21, 2013, 10:12:29 PM
not a highway, but I just noticed that the Northwest Angle in Minnesota has been renamed to "Jake's Northwest Angle".

I had nothing to do with this, but I'll take it!
Title: Re: Incorrect highways marked on Google Maps
Post by: Bruce on March 22, 2013, 02:30:23 AM
Introducing...Washington State Route 38560. http://goo.gl/maps/lznzl
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on March 22, 2013, 05:01:55 PM
Quote from: agentsteel53 on March 21, 2013, 10:12:29 PM
not a highway, but I just noticed that the Northwest Angle in Minnesota has been renamed to "Jake's Northwest Angle".

It's an actual name of a lodge there, a website for it even exists (http://www.jakesnorthwestangle.com).
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 22, 2013, 07:59:57 PM
Columbia has some new cities surrounding it: Northeast Arcadia Lakes, East & Southern, and West Metro. Northwest Columbia is slightly less major.
http://maps.google.com/maps?hl=en&ll=34.00071,-81.034814&spn=1.03831,2.113495&gl=us&t=m&z=10
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on March 22, 2013, 08:35:48 PM
On that note, Edmonton and Calgary have been divided into quadrants

http://goo.gl/maps/tUZPb

And I don't know what a "West Valley" is, but apparently it's more important than Garden City
http://goo.gl/maps/4851l

Oooo- and look at the city of Northeast Denver
http://goo.gl/maps/sCKKr

Memphis is toast
http://goo.gl/maps/z0Az1

I really don't understand how such a cutting edge, top of the line company can allow updates like this to go live.

It looks like they uploaded a neighborhood layer but failed...Tucson is divided into its wards instead of the official neighborhoods...nobody knows what ward they're in (upside: they do now!) http://goo.gl/maps/defQq
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on March 22, 2013, 08:43:44 PM
I've noticed it for a while that the townships within Indianapolis (Marion County) are referenced in the same way, even though they are all a part of the city itself. Granted in Indy, if you don't live in a neighborhood that is commonly refered to by a name, you are refered by your township's name. It may be like that elsewhere too, but looking at that Memphis example....I could have sworn there was a large city in that part of the state that went by the name of a former Egyptian community.
Title: Re: Incorrect highways marked on Google Maps
Post by: iowahighways on March 23, 2013, 12:28:45 PM
Looks like there are some newly-resurrected highways (http://goo.gl/maps/pqAMh) near Cedar Rapids: IA 94 appears despite being decommissioned in 2003. But that's not all: IA 149 is marked in Fairfax even though it hasn't gone through there since 1985, as US 151 superseded it upon its extension to I-80. And then there's IA 84 near the airport, which hasn't been a state highway since 1980.

It's not limited to Cedar Rapids, either: IA 401 has not gone through Johnston since 1990, but here it is (http://goo.gl/maps/E2YbK).
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on March 23, 2013, 07:12:13 PM
Google's now posting all the SRs in Pennsylvania in their own shields, both the signed routes and the quadrant routes.

Example: https://maps.google.com/maps?hl=en&ll=40.661629,-75.696831&spn=0.213036,0.445976&t=m&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: hbelkins on March 23, 2013, 08:57:05 PM
Mentioned this as an aside in another thread, but it bears repeating.

Google has I-69 marked on the Pennyrile Parkway north of the WK Parkway, and also has I-66 marked on the WK east of the Pennyrile. The public information officer from the two westernmost highway districts submitted the error report to Google. They replied with some off-the-wall excuse.

Pretty bad when they won't accept a correction from a highway department official.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on March 24, 2013, 08:09:07 AM
Welcome to the city of Northwest Philadelphia. (http://goo.gl/maps/CLR0u)
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on March 24, 2013, 03:37:35 PM
I do not know if someone brought this up or not, as there are many pages here now, but US 70 Business through Smithfield, NC is shown as mainline US 70.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadfro on March 24, 2013, 08:22:22 PM
Quote from: roadman65 on March 24, 2013, 03:37:35 PM
I do not know if someone brought this up or not, as there are many pages here now, but US 70 Business through Smithfield, NC is shown as mainline US 70.

That's not incorrect, it's a limitation in the way Google Maps displays route markers--they do not show any banners on their maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on March 24, 2013, 08:30:13 PM
Quote from: roadfro on March 24, 2013, 08:22:22 PM
Quote from: roadman65 on March 24, 2013, 03:37:35 PM
I do not know if someone brought this up or not, as there are many pages here now, but US 70 Business through Smithfield, NC is shown as mainline US 70.

That's not incorrect, it's a limitation in the way Google Maps displays route markers--they do not show any banners on their maps.
Interesting.  That is unusual, as it can throw a stranger off looking at it.

Anyway, I did find another as I was going through my old stomping ground.  That is NJ 124 in Irvington, NJ along Springfield Avenue.  NJ 124 ends at the city border on Springfield Avenue and turns to an Essex County Route at that particular point.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on March 24, 2013, 10:14:40 PM
Quote from: roadfro on March 24, 2013, 08:22:22 PM
Quote from: roadman65 on March 24, 2013, 03:37:35 PM
I do not know if someone brought this up or not, as there are many pages here now, but US 70 Business through Smithfield, NC is shown as mainline US 70.

That's not incorrect, it's a limitation in the way Google Maps displays route markers--they do not show any banners on their maps.
It becomes more than a little problematic when the bannered route is of similar quality to the main route, and I'm trying to plan my way through an area for the first time. Oh, yeah, and all the completely misplaced/misrouted routes, there are those, too.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on March 25, 2013, 04:57:06 AM
Try MapQuest's OSM rendering: http://www.openstreetmap.org/?lat=35.5106&lon=-78.2916&zoom=14&layers=Q
Title: Re: Incorrect highways marked on Google Maps
Post by: dfilpus on March 25, 2013, 10:43:15 AM
Quote from: NE2 on March 25, 2013, 04:57:06 AM
Try MapQuest's OSM rendering: http://www.openstreetmap.org/?lat=35.5106&lon=-78.2916&zoom=14&layers=Q
Of course, that rendering shows a US 70 Alt shield on the intersection of US 70 mainline and US 70 Alt, making it look like US 70 is US 70 Alt. If you zoom out, the shield shifts onto US 70 Alt, but as you zoom in, it stays at the intersection.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 25, 2013, 11:20:10 AM
Take a look at NJ Turnpike exit 8... I really don't know what to say...
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on March 25, 2013, 05:13:15 PM
Quote from: vdeane on March 25, 2013, 11:20:10 AM
Take a look at NJ Turnpike exit 8... I really don't know what to say...

http://goo.gl/maps/pJxK1

I didn't think it'd be that bad... how do Google editors let this stuff happen, when they reject even legit and correct edits? :banghead:

I wish the editor was similar to OSM so we could just jump in and get it all fixed without a whole process.
Title: Re: Incorrect highways marked on Google Maps
Post by: JMoses24 on March 25, 2013, 06:56:48 PM
Quote from: A.J. Bertin on March 15, 2013, 11:14:45 AM
Quote from: JMoses24 on March 15, 2013, 09:07:51 AM
Quote from: codyg1985 on February 13, 2013, 07:10:13 AM
Well now most of I-74 is multiplexed with I-465 on Google Maps, except for a few sections in NC.

As of this morning, it's STILL that way from near Harrison, Ohio to the Quad Cities of IL/IA. It's supposed to be multiplexed with I-465 only along the Indianapolis beltway. Once it's off there, it's supposed to be on its own. It isn't apparently multiplexed with 465 anywhere from the I-275 loop in Cincinnati to where the western segment of 74 terminates, nor once it takes the turn west onto I-280 in the Quad Cities. I can't find how to remove those shields though, or I'd have done it.
A week or two ago I reported this error through Google Maps. The following day I received a note from them saying that they are unable to process the correction right now. Sounds like it's some technical error that the folks at Google can't quite figure out. LOL

As of tonight (6:56 PM EDT), this error has now finally been fixed.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 25, 2013, 10:16:56 PM
Quote from: dfilpus on March 25, 2013, 10:43:15 AM
Quote from: NE2 on March 25, 2013, 04:57:06 AM
Try MapQuest's OSM rendering: http://www.openstreetmap.org/?lat=35.5106&lon=-78.2916&zoom=14&layers=Q
Of course, that rendering shows a US 70 Alt shield on the intersection of US 70 mainline and US 70 Alt, making it look like US 70 is US 70 Alt. If you zoom out, the shield shifts onto US 70 Alt, but as you zoom in, it stays at the intersection.

That's because of the highway "way" being split there.
http://www.openstreetmap.org/browse/way/15121388

Because of that way being so "small", the shield shows up in the middle of the intersection.  An unfortunate flaw in Mapnik/Mapquest.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 28, 2013, 02:03:45 AM
Seems US-331 has been upgraded for it's entire length to "I-331"..... :banghead:
http://goo.gl/maps/zlr1c

Seriously, I want to know how these stupid edits happen.  Does Google employ monkey's as mods?
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on March 28, 2013, 06:32:34 PM
Quote from: rickmastfan67 on March 28, 2013, 02:03:45 AM
Seems US-331 has been upgraded for it's entire length to "I-331"..... :banghead:
http://goo.gl/maps/zlr1c

Seriously, I want to know how these stupid edits happen.  Does Google employ monkey's as mods?
They happen for the same reason you pluralized a noun with an apostrophe.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on March 28, 2013, 06:38:53 PM
As of 6:38 PM EDT on March 28, 2013, Google Street View has started to recognize Illinois' existence again, but New York State, Kentucky, Ohio and Missouri still don't exist on Street View.  :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: kharvey10 on March 28, 2013, 06:46:17 PM
IL 160 in Southern Illinois is marked as IL 100 but only in Clinton County

If you zoom in far enough, various unmarked routes are marked as state routes as well in St. Clair County.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on March 28, 2013, 08:36:24 PM
If Google is making that many errors within certain days, they really need to rethink how they do the entire world atlas, not just the U.S.

I mean, a US 210 in Montana, an I-90B, a turnpike exit error, and now this I-331 and IL 100. Like I've said before, they must have hired rookie road geeks who make these shitty ass maps like they're from third grade or something! Jesus! Is Google really that stupid?  :eyebrow:
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on March 29, 2013, 09:47:54 AM
In Alma, MI, the US 127 Business route is still marked as "US 27" while its counterpart in St. Louis, MI is marked as US 127B.

I mention the latter to prove that the former was definitely overlooked or the simple fact that Michigan does not log both business routes as the same because of the unique situation here of having two business loops at the same place.  Nonetheless, it has not been US 27 in decades and the newer freeway was changed to US 127 just over 10 years ago.
Title: Re: Incorrect highways marked on Google Maps
Post by: DTComposer on March 29, 2013, 10:25:38 AM
Quote from: corco on March 22, 2013, 08:35:48 PM
On that note, Edmonton and Calgary have been divided into quadrants

http://goo.gl/maps/tUZPb

And I don't know what a "West Valley" is, but apparently it's more important than Garden City
http://goo.gl/maps/4851l

Oooo- and look at the city of Northeast Denver
http://goo.gl/maps/sCKKr

Memphis is toast
http://goo.gl/maps/z0Az1

I really don't understand how such a cutting edge, top of the line company can allow updates like this to go live.

It looks like they uploaded a neighborhood layer but failed...Tucson is divided into its wards instead of the official neighborhoods...nobody knows what ward they're in (upside: they do now!) http://goo.gl/maps/defQq

Also in Los Angeles...it's like the San Fernando Valley actually got to secede...

https://maps.google.com/maps?hl=en&ll=34.052659,-118.24585&spn=2.698662,4.295654&gl=us&t=m&z=8
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 29, 2013, 11:44:29 AM
Quote from: Billy F 1988 on March 28, 2013, 08:36:24 PM
If Google is making that many errors within certain days, they really need to rethink how they do the entire world atlas, not just the U.S.

I mean, a US 210 in Montana, an I-90B, a turnpike exit error, and now this I-331 and IL 100. Like I've said before, they must have hired rookie road geeks who make these shitty ass maps like they're from third grade or something! Jesus! Is Google really that stupid?  :eyebrow:
The just employ moderators from Nicaragua who pretend to be people from India pretending to be Americans.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on March 30, 2013, 01:08:36 PM
Quote from: kharvey10 on March 28, 2013, 06:46:17 PM
If you zoom in far enough, various unmarked routes are marked as state routes as well in St. Clair County.

Those are state highways.  Technically, they are federal aid secondary state routes (or various similar designations), which is why they're labelled "FAS xxx" on Google Maps; you can read more information on them here (http://www.n9jig.com/trivia.html).  Though they don't have proper route shields, they are also technically signed by number in the field on mile markers like this (http://www.billburmaster.com/rmsandw/illinois/images/il910mile080.jpg) (the one linked is for MM-0.80 on FAS-910 (Old IL-121 south of Tremont) in Tazewell County.  Of course, I'm sure Google would still rather the labels hadn't ended up on their map.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bamaroadgeek on March 31, 2013, 04:45:27 PM
Welcome to the city of Walnut Grove-Shelby Farms PD, Tennessee....
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on April 01, 2013, 06:32:39 AM
US 250 near Fairmont WV has been upgraded to I-250 (https://maps.google.es/maps?ll=39.472245,-80.136337&spn=0.073411,0.154324&t=m&z=13)
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on April 01, 2013, 01:28:58 PM
In the words of Chad Knaus (racing crew chief): GOT TO BE FUCKIN' KIDDING ME! GOT TO BE FUCKING KIDDING ME!

Appologies for the language, but seriously, Google is so stupid now. This is unreal, people!
Title: Re: Incorrect highways marked on Google Maps
Post by: BrianP on April 01, 2013, 04:22:37 PM
Quote from: CNGL-Leudimin on April 01, 2013, 06:32:39 AM
US 250 near Fairmont WV has been upgraded to I-250 (https://maps.google.es/maps?ll=39.472245,-80.136337&spn=0.073411,0.154324&t=m&z=13)
I saw that today.  It stretches from Charolettesville VA to Uhrichsville OH.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on April 01, 2013, 08:45:43 PM
Quote from: CNGL-Leudimin on April 01, 2013, 06:32:39 AM
US 250 near Fairmont WV has been upgraded to I-250 (https://maps.google.es/maps?ll=39.472245,-80.136337&spn=0.073411,0.154324&t=m&z=13)
To avoid the embarrassment of being an April Fool, Google will now have to create an I-50 as well. I recommend converting US 6, the northern terminus of 250.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on April 01, 2013, 10:32:42 PM
This freeway segment of PA 309 is all messed up with some yellow segments: https://maps.google.com/maps?hl=en&ll=40.348899,-75.256691&spn=0.129256,0.308304&t=m&z=12

And upon zooming out, you'll notice that PA 309 from PA 378 to the bottom part of that freeway segment is all chopped up. I wonder what causes it to display this way: http://goo.gl/maps/L13In

With that second error, that's definitely not the only place where that happens. Some examples:

NJ Turnpike: http://goo.gl/maps/uAIqO
GSP: http://goo.gl/maps/6JqHU
http://goo.gl/maps/6JqHU (SE of Mahwah)

It all seems to only display that way at that same zoom level.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on April 02, 2013, 12:48:08 AM
Quote from: Some_Person on April 01, 2013, 10:32:42 PM
GSP: http://goo.gl/maps/6JqHU
http://goo.gl/maps/6JqHU (SE of Mahwah)

Palisades Parkway too.  Here's a better link for the SE of Mahwah one. http://goo.gl/maps/IgIAy (You copypastaed the same link twice.)
Title: Re: Incorrect highways marked on Google Maps
Post by: HighwayMaster on April 06, 2013, 03:30:00 PM
2 suburbs of Columbia, SC, West Metro and Northeast Arcadia Lakes, are shown as bigger than Columbia itself.
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on April 06, 2013, 05:32:51 PM
Not an incorrect highway, exactly, but Google has moved US 98 in Canal Point, FL onto the nearby railroad tracks: https://maps.google.com/?ll=26.857717,-80.635765&spn=0.001625,0.00327&t=m&z=19
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 06, 2013, 05:49:02 PM
Quote from: deathtopumpkins on April 06, 2013, 05:32:51 PM
Not an incorrect highway, exactly, but Google has moved US 98 in Canal Point, FL onto the nearby railroad tracks: https://maps.google.com/?ll=26.857717,-80.635765&spn=0.001625,0.00327&t=m&z=19
Nice. (Un)fortunately it won't route along the tracks.
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on April 07, 2013, 05:26:23 PM
I just had to explain to my father why I-369 is not signed in Kentucky, at least I'm pretty sure it isn't or else I'd see it mentioned here. We'll be taking a trip next month to...oh what's that town...oh yeah Walnut Grove-Shelby Farms PD, Tennessee.
Title: Re: Incorrect highways marked on Google Maps
Post by: Central Avenue on April 08, 2013, 12:14:21 AM
And in a reversal of the US 98 error above: N. County Line Road near Centerburg, Ohio marked as "Conrail Railroad" (http://goo.gl/maps/NIGLv)
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on April 08, 2013, 11:08:07 AM
Quote from: Central Avenue on April 08, 2013, 12:14:21 AM
And in a reversal of the US 98 error above: N. County Line Road near Centerburg, Ohio marked as "Conrail Railroad" (http://goo.gl/maps/NIGLv)

Ooh, not only is that not a railroad, its not even the right railroad! Conrail was merged into CSX and NS in 1999 and now only exists as a terminal railroad subsidiary in 3 cities.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on April 08, 2013, 04:08:47 PM
Quote from: deathtopumpkins on April 08, 2013, 11:08:07 AM
Quote from: Central Avenue on April 08, 2013, 12:14:21 AM
And in a reversal of the US 98 error above: N. County Line Road near Centerburg, Ohio marked as "Conrail Railroad" (http://goo.gl/maps/NIGLv)

Ooh, not only is that not a railroad, its not even the right railroad! Conrail was merged into CSX and NS in 1999 and now only exists as a terminal railroad subsidiary in 3 cities.

He he he....let's "correct" IL-37 to say Illinois Central.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on April 08, 2013, 07:18:44 PM
Quote from: deathtopumpkins on April 06, 2013, 05:32:51 PM
Not an incorrect highway, exactly, but Google has moved US 98 in Canal Point, FL onto the nearby railroad tracks: https://maps.google.com/?ll=26.857717,-80.635765&spn=0.001625,0.00327&t=m&z=19
And this is why whenever I want to clinch any highway with a routing that's not dead-straight, I go to people's websites to confirm.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on April 08, 2013, 10:25:15 PM
Quote from: deathtopumpkins on April 06, 2013, 05:32:51 PM
Not an incorrect highway, exactly, but Google has moved US 98 in Canal Point, FL onto the nearby railroad tracks: https://maps.google.com/?ll=26.857717,-80.635765&spn=0.001625,0.00327&t=m&z=19

It also shows US 98 along Old Conner Highway, which is only FL 700, and has been that way since around 2008-09.
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on April 09, 2013, 01:52:52 AM
Quote from: formulanone on April 08, 2013, 10:25:15 PM
Quote from: deathtopumpkins on April 06, 2013, 05:32:51 PM
Not an incorrect highway, exactly, but Google has moved US 98 in Canal Point, FL onto the nearby railroad tracks: https://maps.google.com/?ll=26.857717,-80.635765&spn=0.001625,0.00327&t=m&z=19

It also shows US 98 along Old Conner Highway, which is only FL 700, and has been that way since around 2008-09.

Yeah the routings of everything are really messed up around there. I've found that Florida as a whole is horribly riddled with errors on Google, but the area around Lake Okeechobee is particularly screwed up, and very difficult to figure out due to a bunch of changes in recent years, and a general lack of either roadgeek site coverage or actual usable streetview imagery.
I do believe I've gotten everything correct though:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F7GGILaa.png&hash=faf34c2c7173c5eded1f55d25b9c89974c763d22)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 09, 2013, 03:11:16 AM
SR 812 is a recent addition, going west from "Runyon" to SR 715 as part of a truck bypass of Belle Glade.

You also left out CR 700 (and of course left SR 717 and SR 880 unmarked, though the latter is actually signed as CR 880).

Also note that SR 15 is signed through Belle Glade to SR 880 (which used to be where SR 80 left the current route).
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on April 09, 2013, 12:01:00 PM
Quote from: deathtopumpkins on April 09, 2013, 01:52:52 AM
... the area around Lake Okeechobee is particularly screwed up, and very difficult to figure out due to a bunch of changes in recent years, and a general lack of either roadgeek site coverage or actual usable streetview imagery.

For an area with a population of around ten thousand people, there's been an unusual number of detail changes in numbering within that region during the past 25 years.

In the background you can see where SR 15 starts:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.formulanone.org%2Froads%2FCR880%2FCR880sign-BG.jpg&hash=93f842b2ea78412582ad25b51cf0c0121987f2fc)

(I think we'd also determined that this CR 880 shield should technically be an SR 880 shield, at least for about a mile or so, and then be a county-route shield again.)

And here's the SR 812 sign (there's an un-related CR 812 near Lake Worth and Lantana, same county, different location).

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.formulanone.org%2Froads%2FSR715%2FSR812sign.jpg&hash=3838029083a2373bb822d8a8229d60a752d7fa8f)
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on April 09, 2013, 02:07:12 PM
Quote from: NE2 on April 09, 2013, 03:11:16 AM
SR 812 is a recent addition, going west from "Runyon" to SR 715 as part of a truck bypass of Belle Glade.

Just added this. Is it new construction or the existing road going west from the intersection of US 441 and US 98?

QuoteYou also left out CR 700 (and of course left SR 717 and SR 880 unmarked, though the latter is actually signed as CR 880).

Yeah, the fact that part of 880 is an SR is indicated by the portion of it with a thicker line, I just figured it would be redundant to include a second shield, especially since the majority of people can't even distinguish between the different shield types anyway. Where are 700 and 717 though? It's been a while since I did the bulk of my research in that area.

QuoteAlso note that SR 15 is signed through Belle Glade to SR 880 (which used to be where SR 80 left the current route).

Added an SR 15 shield.

Thank you very much for the corrections, and thank you formulanone for the photographic evidence!
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 09, 2013, 04:08:35 PM
Quote from: deathtopumpkins on April 09, 2013, 02:07:12 PM
Just added this. Is it new construction or the existing road going west from the intersection of US 441 and US 98?
The existing road.

Quote from: deathtopumpkins on April 09, 2013, 02:07:12 PM
Where are 700 and 717 though? It's been a while since I did the bulk of my research in that area.
CR 700 continues SR 700 southeast to CR 880. It's the old main road before SR 80 was realigned off CR 880.

SR 717 is the diagonal state road in Belle Glade, running from SR 715 to SR 880/CR 880.

Also SR 80 is consistently signed along US 27 and US 98-441.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on April 18, 2013, 09:48:17 PM
Leave It to Google! :banghead:
http://goo.gl/maps/AmLh8 (http://goo.gl/maps/AmLh8) Just east from the GSP interchange

Edit: Just miles west on the ACE  http://goo.gl/maps/KDbN7 (http://goo.gl/maps/KDbN7)
Now, an underpass is considered a tunnel  :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on April 18, 2013, 10:22:23 PM
Quote from: Roadgeek2500 on April 18, 2013, 09:48:17 PM
Leave It to Google! :banghead:
http://goo.gl/maps/AmLh8 (http://goo.gl/maps/AmLh8) Just east from the GSP interchange
"Freeway Entrance: Emergency Stopping Only"
"Road Ends 1/4 Mile" :sombrero:
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on April 19, 2013, 11:35:29 AM
Quote from: Roadgeek2500 on April 18, 2013, 09:48:17 PM
Leave It to Google! :banghead:
http://goo.gl/maps/AmLh8 (http://goo.gl/maps/AmLh8) Just east from the GSP interchange
Those have been popping up everywhere.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 26, 2013, 12:23:42 PM
Routing gap in US 65: http://maps.google.com/maps?saddr=U.S.+165+N%2FUS-65+N&daddr=U.S.+165+N%2FUS-65+N&hl=en&ll=33.710061,-91.461182&spn=0.260463,0.528374&sll=33.72591,-91.447642&sspn=0.016276,0.033023&geocode=FaRIAgIdE6aM-g%3BFcChAgIdJIeM-g&gl=us&mra=dme&mrsp=1&sz=16&t=m&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on April 26, 2013, 12:27:29 PM
Quote from: NE2 on April 26, 2013, 12:23:42 PM
Routing gap in US 65: http://maps.google.com/maps?saddr=U.S.+165+N%2FUS-65+N&daddr=U.S.+165+N%2FUS-65+N&hl=en&ll=33.710061,-91.461182&spn=0.260463,0.528374&sll=33.72591,-91.447642&sspn=0.016276,0.033023&geocode=FaRIAgIdE6aM-g%3BFcChAgIdJIeM-g&gl=us&mra=dme&mrsp=1&sz=16&t=m&z=12

There's an irony there.  Where above, there's an odd break in the line on the map, but it would still route you correctly on the freeway in question.  But here, the map looks fine, but it won't route you that way (and still doesn't even route you on the shortest alternate).
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on April 26, 2013, 05:33:09 PM
Bahaha. Some idiot deleted the new piece of SR 429: http://maps.google.com/maps?ll=28.66747,-81.52997&spn=0.068682,0.132093&gl=us&t=m&z=14
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on April 26, 2013, 06:16:15 PM
I'm thinking there's a chance Google might start signing county highways with shields. I just noticed in Google Earth, county highways are displayed with a rectangular shield; while not like the signed pentagons, it is in-line with other mapping services like paper maps and Bing.

But of course, it's Google so they fuck it up badly:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F83h3Gsn.jpg&hash=aa4e7df3488cf1372cdeb7d97b133e90588ffe98)
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on April 26, 2013, 08:32:14 PM
That's Google for you. Complain to them about incorrect highways, they ain't gonna do shit about it. They'll just go "fuck you, that's what we have it as" and shun you. They may as well be messed up goats from Alanland who think it's "Analland". What a bunch of dipshits! Go to he...er...um Alanland, or whatever that place is called, Google! Or should I say SCREWGLE?!
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on April 26, 2013, 11:20:44 PM
Quote from: NE2 on April 26, 2013, 05:33:09 PM
Bahaha. Some idiot deleted the new piece of SR 429: http://maps.google.com/maps?ll=28.66747,-81.52997&spn=0.068682,0.132093&gl=us&t=m&z=14

It's not deleted, but it's been marked as "planned" again.  Just zoom in to the closer zooms and it shows up again.
http://goo.gl/maps/hhpTD
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on April 27, 2013, 09:17:54 AM
Apple Maps has begun to how county pentagons in some areas. I noticed some in Central Florida, and Indiana, when tinkering with an iPad recently (Edit: Alabama, too). Oddly, I didn't think Indiana signed their county routes...at least, the Shield Gallery doesn't have any, nor have I seen one there.



Google's gotta keep up, I suppose.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on April 28, 2013, 02:45:44 AM
This one's not just Google -- EVERY online mapping service has this one wrong. In Google's favor, they've got it less wrong. Surprisingly.

http://goo.gl/maps/OYJgs
"SW Zoo Rd" is really SW Knights Blvd. There are no signs from US 26 referring to Knights or any other street name, just a directional sign toward the Oregon Zoo, Childrens' Museum and Washington Park in general. OpenStreetMap goes with this particular error, and it's somewhat understandable.

However, in the park itself, there are zero street signs pointing to an existence of a "SE Zoo Rd". The posted maps in the park do show SW Knights Blvd.

I mentioned Google (and OSM) have this 'less wrong' than the others.
Rand McNally (and by extension, the last edition of the Portland Thomas Guide, RIP), Bing, Yahoo and MapQuest (non-OSM) all show this as 'SW Canyon Rd'. Canyon Rd is actually the freeway.
Thomas Guides 2007 and before agree with Washington Park's posted maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on April 28, 2013, 05:46:56 AM
Quote from: formulanone on April 27, 2013, 09:17:54 AM
Apple Maps has begun to how county pentagons in some areas. I noticed some in Central Florida, and Indiana, when tinkering with an iPad recently. Oddly, I didn't think Indiana signed their county routes...at least, the Shield Gallery doesn't have any, nor have I seen one there.

Google's gotta keep up, I suppose.

I've seen three pentagon shields in Indiana my whole life. County roads are usually marked on regular street shields. I get a kick at seeing maps using a square or pentagon to represent county highway numbers (County Road 100 North for instance) when they are nothing more than road names.
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on April 30, 2013, 09:27:53 PM
Apparently Google thinks NY 20C still exists: http://goo.gl/maps/NsscN

EDIT: And apparently they didn't get the memo that NYSDOT decommissioned NY 360 last year: http://goo.gl/maps/42OuK
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on May 04, 2013, 03:37:29 PM
Once Again the Media Byp. (US 1) has been Downgraded to "yellow" http://goo.gl/maps/kHlGa (http://goo.gl/maps/kHlGa)
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on May 04, 2013, 04:48:47 PM
Thanks for pointing that out.  I've gone ahead and corrected Zoo Rd.  I can't seem to fix the number of lanes, but will hopefully find someone who can.  All you need to do to correct it is to use Google Mapmaker.

I'll take a look at some of the other bad information and work on correcting it.

I did notice the other day that FL-5 is labeled from Mainland Florida to Key West, along with US-1 and A1A (which just shows up as 1A).  Can anyone confirm or deny the existence of FL-5 over that route, so I can correct it.

Quote from: Bickendan on April 28, 2013, 02:45:44 AM
This one's not just Google -- EVERY online mapping service has this one wrong. In Google's favor, they've got it less wrong. Surprisingly.

http://goo.gl/maps/OYJgs
"SW Zoo Rd" is really SW Knights Blvd. There are no signs from US 26 referring to Knights or any other street name, just a directional sign toward the Oregon Zoo, Childrens' Museum and Washington Park in general. OpenStreetMap goes with this particular error, and it's somewhat understandable.

However, in the park itself, there are zero street signs pointing to an existence of a "SE Zoo Rd". The posted maps in the park do show SW Knights Blvd.

I mentioned Google (and OSM) have this 'less wrong' than the others.
Rand McNally (and by extension, the last edition of the Portland Thomas Guide, RIP), Bing, Yahoo and MapQuest (non-OSM) all show this as 'SW Canyon Rd'. Canyon Rd is actually the freeway.
Thomas Guides 2007 and before agree with Washington Park's posted maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on May 04, 2013, 05:00:07 PM
Quote from: Roadgeek2500 on May 04, 2013, 03:37:29 PM
Once Again the Media Byp. (US 1) has been Downgraded to "yellow" http://goo.gl/maps/kHlGa (http://goo.gl/maps/kHlGa)

The Google Map(maker) moderators don't like roads that change types.  They are very often converting Freeways and Expressways back to National Highway (Yellow), and it takes a lot of work for us to keep them correct.  I've been spending over a year keeping the new IN-25 Expressway as an Expressway.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on May 04, 2013, 06:17:42 PM
Quote from: TEG24601 on May 04, 2013, 04:48:47 PM
I did notice the other day that FL-5 is labeled from Mainland Florida to Key West, along with US-1 and A1A (which just shows up as 1A).  Can anyone confirm or deny the existence of FL-5 over that route, so I can correct it.
Bahaha. Every fucking map, even most local printed maps, shows these "hidden" routes. Good luck removing them. (As for SR 5, it exists from Key West to Georgia but is only signed on Olive Avenue-Federal Highway in Lake Worth-West Palm, ending at Belvedere.)
Title: Re: Incorrect highways marked on Google Maps
Post by: Michael on May 04, 2013, 09:05:58 PM
This post isn't about a highway, but a set of directions.

I took a day trip to our church camp with some friends on July 3rd last summer (I meant to post this on July 4th, but I'm just getting to it now, ten months later :banghead:), and the one driving got her directions from Google Maps.  Here's (http://maps.google.com/maps?saddr=Unknown+road&daddr=Cma+Camp&hl=en&ll=43.176805,-76.006245&spn=0.687998,1.454315&sll=43.29388,-75.464391&sspn=0.000671,0.00142&geocode=FcgLkQIdjsxv-w%3BFSudlAIdYoGA-w&t=m&mra=me&mrsp=1,0&sz=20&z=10) an overview of the trip.  Last fall (November I believe), Google changed it's routing algorithm, and the old routing looked like this current alternate routing option (http://maps.google.com/maps?saddr=Unknown+road&daddr=43.1521703,-75.6917326+to:Access+Rd&hl=en&sll=43.29388,-75.464391&sspn=0.000671,0.00142&geocode=FcgLkQIdjsxv-w%3BFSpzkgIdLAl9-ylvG65In3XZiTEaiwQC2pF-LQ%3BFQydlAIdZIGA-w&t=m&mra=me&mrsp=1,0&sz=20&z=10&via=1).  The problem is near Canastota and Rome.  The correct routing is to stay on the Thruway until exit 33, then take NY 365 to Rome (http://maps.google.com/maps?saddr=Unknown+road&daddr=Cma+Camp&hl=en&ll=43.16963,-75.572891&spn=0.344043,0.727158&sll=43.29388,-75.464391&sspn=0.000671,0.00142&geocode=FcgLkQIdjsxv-w%3BFSudlAIdYoGA-w&t=m&mra=me&mrsp=1,0&sz=20&z=11).  The old algorithm had you get off at exit 34 (NY 13) and literally sent you zigzagging across Oneida County (http://maps.google.com/maps?saddr=Unknown+road&daddr=43.0999457,-75.7478847+to:Cma+Camp&hl=en&ll=43.16963,-75.572891&spn=0.344043,0.727158&sll=43.29388,-75.464391&sspn=0.000671,0.00142&geocode=FcgLkQIdjsxv-w%3BFSmnkQId1C18-ylx3s9lup3ZiTEaV56VqkXKVg%3BFSudlAIdYoGA-w&t=m&mra=me&mrsp=1,0&sz=20&z=11&via=1).  My friend who was driving got confused at this intersection (http://maps.google.com/maps?saddr=Unknown+road&daddr=43.0999457,-75.7478847+to:Cma+Camp&hl=en&ll=43.229498,-75.49356&spn=0.001343,0.00284&sll=43.29388,-75.464391&sspn=0.000671,0.00142&geocode=FcgLkQIdjsxv-w%3BFSmnkQId1C18-ylx3s9lup3ZiTEaV56VqkXKVg%3BFSudlAIdYoGA-w&t=m&mra=me&mrsp=1,0&sz=20&z=19&via=1) when she was looking for a sign for Rome-Taburg Road that was mentioned in the directions, but the intersection only had signs for NY 46, NY 49, and NY 69.  My other friend opened Google Maps on her iPhone, gave it to me and asked if I could make any sense of the map.  I'd looked up the area on Google Maps before we left, and I knew that turning left would be taking us away from where we wanted to be, so I had her turn right to get to NY 26.  This gave me some more things to add to the You Know You're A Roadgeek If... thread (https://www.aaroads.com/forum/index.php?topic=1113.msg219498#msg219498), and inspired me to create a thread about when being a roadgeek has been helpful (https://www.aaroads.com/forum/index.php?topic=9398.0).

On the way home, we took NY 365, but with a slight variation.  We took James Street between Downtown Rome and NY 365 (http://maps.google.com/maps?saddr=Cma+Camp&daddr=Unknown+road&hl=en&ll=43.203987,-75.45393&spn=0.042981,0.090895&sll=43.186154,-75.456505&sspn=0.171975,0.363579&geocode=FSudlAIdYoGA-w%3BFcgLkQIdjsxv-w&mra=prev&t=m&z=14) instead of staying on NY 26 (http://maps.google.com/maps?saddr=Cma+Camp&daddr=43.1978671,-75.4526958+to:Unknown+road&hl=en&sll=43.203987,-75.45393&sspn=0.042981,0.090895&geocode=FSudlAIdYoGA-w%3BFaslkwId6a6A-ylnR3MYdBPZiTEJdKozOyEwyQ%3BFcgLkQIdjsxv-w&mra=dpe&mrsp=1&sz=14&via=1&t=m&z=14).  Using James Street is .8 miles and one minute shorter, but the only problem with using James Street in the default routing on Google Maps is a 9 foot high railroad tunnel.

I don't understand why Google picked the longer routing by default with the old algorithm.  The option of taking I-81 north to NY 69 in Oswego County is about 12 miles and 20 minutes longer than either of the routings above, yet was an option with the old algorithm and still is with the new algorithm.

Here's (https://www.aaroads.com/forum/index.php?topic=1487.msg219496#msg219496) a link to a trip report I posted in the New York thread on the Northeast board.




I posted earlier in this thread about two separate "US Route in ____" errors on the same road (https://www.aaroads.com/forum/index.php?topic=2001.msg148324#msg148324), but I beat that record by finding three separate "US Route in ____" errors on US 6 west of the Bear Mountain Bridge last spring, but never posted it.  Fortunately, they were fixed by July when I took the trip I wrote about above.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 06, 2013, 01:50:13 PM
Quote from: TEG24601 on May 04, 2013, 05:00:07 PM
The Google Map(maker) moderators don't like roads that change types

Says you!  Start here (http://goo.gl/maps/VgeVg) and scroll south for a while.  It's all freeway, so I'm not sure why different halves change color every few millimeters.
Title: Re: Incorrect highways marked on Google Maps
Post by: swbrotha100 on May 06, 2013, 07:46:58 PM
I-49 is cosigned with AR 549 south of Texarkana.
Title: Re: Incorrect highways marked on Google Maps
Post by: Some_Person on May 06, 2013, 08:00:52 PM
Quote from: kphoger on May 06, 2013, 01:50:13 PM
Quote from: TEG24601 on May 04, 2013, 05:00:07 PM
The Google Map(maker) moderators don't like roads that change types

Says you!  Start here (http://goo.gl/maps/VgeVg) and scroll south for a while.  It's all freeway, so I'm not sure why different halves change color every few millimeters.

That problem seems to exist nearly everywhere there's a freeway:
http://goo.gl/maps/AXp7a
http://goo.gl/maps/CkCJM

This is another error that I often question though:
http://goo.gl/maps/Hcep0 - Notice PA 33 and US 22 near Easton and I-78, they're rendered poorly and dont appear at points, and this error only seems to happen in satellite mode. Also, for some reason, the freeway portion of PA 378 doesn't show up whatsoever on that link, even though other state highway-freeways are shown.
Title: Re: Incorrect highways marked on Google Maps
Post by: jp the roadgeek on May 13, 2013, 10:36:46 AM
Apparently, Google Maps now indicates that a new section of CT 9 is open.  No, not a northern extension to CT 4 or a Long Island Sound bridge, but as a section of Minor Hill Rd. in Roxbury about 30 miles from the closest stretch of the real CT 9.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on May 17, 2013, 07:48:46 PM
Surprise! I-580 now ends at the California border :bigass:

http://goo.gl/maps/bylO3




Quote from: swbrotha100 on May 06, 2013, 07:46:58 PM
I-49 is cosigned with AR 549 south of Texarkana.
I have absolutely no problem with this :nod:
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 21, 2013, 08:17:32 PM
You want proof that all they do is draw lines over their own satellite imagery?  Here it is.

This is obviously in the process of being upgraded from a three-way at-grade intersection to a four-way cloverleaf:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fmexsat1_zpsdbf4f547.png&hash=68d46fc43101d3524d62c9dd218bc6a1e7830e07)

And so the Goog gives us this quite unuseful map:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fmexsat2_zps600014dd.png&hash=4f4c7d5df30e380082377086e5d726d1d3d7b600)

Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on May 21, 2013, 08:21:52 PM
Quote from: kphoger on May 21, 2013, 08:17:32 PM
You want proof that all they do is draw lines over their own satellite imagery?  Here it is.

This is obviously in the process of being upgraded from a three-way at-grade intersection to a four-way cloverleaf:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fmexsat1_zpsdbf4f547.png&hash=68d46fc43101d3524d62c9dd218bc6a1e7830e07)

And so the Goog gives us this quite unuseful map:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fmexsat2_zps600014dd.png&hash=4f4c7d5df30e380082377086e5d726d1d3d7b600)
Now that's just... Sad... :wow:
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on May 22, 2013, 08:42:56 AM
Quote from: Molandfreak on May 17, 2013, 07:48:46 PM
Surprise! I-580 now ends at the California border :bigass:

http://goo.gl/maps/bylO3

And it cannot continue further because there is another I-580 in CA :sombrero:.

Recently I saw yet another Google Maps mistake, but I forgot where it was.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 22, 2013, 11:13:20 AM
Quote from: CNGL-Leudimin on May 22, 2013, 08:42:56 AM
Recently I saw yet another Google Maps mistake, but I forgot where it was.

It was Virginia.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on May 22, 2013, 12:36:21 PM
where is 580 intended to end? 

would it be too much of a fudge to have that last mile or two in CA be also signed as "California I-580"?
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on May 22, 2013, 01:44:21 PM
Quote from: agentsteel53 on May 22, 2013, 12:36:21 PM
where is 580 intended to end? 

would it be too much of a fudge to have that last mile or two in CA be also signed as "California I-580"?
I-580 doesn't go anywhere north of I-80.

Since I-580's purpose in Nevada is only to give Carson City an interstate, it wouldn't make much sense to continue it north.

AASHTO would have a fit if California wanted to sign another 580, but then again that would be kind of hypocritical if Iowa had numbered their two I-280s and 380s as planned.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on May 22, 2013, 01:45:45 PM
Quote from: Molandfreak on May 22, 2013, 01:44:21 PMIowa had their two I-280s and 380s as planned.

really?  this was a plan?  I've never heard of this, but it seems logical... there are lots of interstates with the same number located closer together.  I-295s of various flavor come to mind.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on May 22, 2013, 01:47:51 PM
I-235 was originally planned as I-380, and I-680 was originally planned as I-280 and I-80N.
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on May 22, 2013, 09:48:14 PM
In Google's defense, both of these routes (https://maps.google.com/?ll=33.806618,-117.919929&spn=0.003312,0.005622&t=m&z=18) are indeed signed.
Title: Re: Incorrect highways marked on Google Maps
Post by: myosh_tino on May 23, 2013, 03:00:28 PM
Quote from: Eth on May 22, 2013, 09:48:14 PM
In Google's defense, both of these routes (https://maps.google.com/?ll=33.806618,-117.919929&spn=0.003312,0.005622&t=m&z=18) are indeed signed.
If you zoom out two levels you'll see two routes... US 66 and SR-49.  I suspect US 66 is part of Cars Land at Disney's California Adventure.  Route 49 probably pays homage to CA-49 which runs right through the heart of California's gold country.  I seem to recall seeing a CA-49 route shield at Disney's California Adventure during my last visit back in 2008.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on May 23, 2013, 03:16:46 PM
http://goo.gl/maps/SCFwH Sweet! :sombrero:
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on May 23, 2013, 05:33:05 PM
Quote from: myosh_tino on May 23, 2013, 03:00:28 PM
Quote from: Eth on May 22, 2013, 09:48:14 PM
In Google's defense, both of these routes (https://maps.google.com/?ll=33.806618,-117.919929&spn=0.003312,0.005622&t=m&z=18) are indeed signed.
If you zoom out two levels you'll see two routes... US 66 and SR-49.  I suspect US 66 is part of Cars Land at Disney's California Adventure.  Route 49 probably pays homage to CA-49 which runs right through the heart of California's gold country.  I seem to recall seeing a CA-49 route shield at Disney's California Adventure during my last visit back in 2008.

Indeed, that's precisely what I was referring to. I saw those firsthand when I was there on Tuesday. Rather amusing that Google gave them the full treatment.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on May 23, 2013, 08:34:04 PM
Quote from: Eth on May 23, 2013, 05:33:05 PM
Quote from: myosh_tino on May 23, 2013, 03:00:28 PMIf you zoom out two levels you'll see two routes... US 66 and SR-49.  I suspect US 66 is part of Cars Land at Disney's California Adventure.  Route 49 probably pays homage to CA-49 which runs right through the heart of California's gold country.  I seem to recall seeing a CA-49 route shield at Disney's California Adventure during my last visit back in 2008.

Indeed, that's precisely what I was referring to. I saw those firsthand when I was there on Tuesday. Rather amusing that Google gave them the full treatment.

So...who's up for suggesting US 498 to Google for a small part of Animal Kingdom?

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ffarm1.staticflickr.com%2F119%2F307349622_0969989d7f_z.jpg&hash=32a48585cdfd5d430b27479f017cd90528d3dc5a)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on May 23, 2013, 09:26:46 PM
Better: I-95 (appears to be accurate early spec with NEW YORK) on what's obviously a surface street in Hollywood Studios.
http://www.flickr.com/photos/adamontheroad/6300481797/
(And an embossed cutout CALIFORNIA US 66.)
Title: Re: Incorrect highways marked on Google Maps
Post by: sbeaver44 on May 27, 2013, 03:26:16 PM
Anyone else experiencing Google Maps' refusal to route over I-94/Bishop Ford Freeway in Chicago?  Even if I try to drag the route onto I-94 it avoids it... is there some closure that, even though I have tried to research, I should be aware of?
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on May 27, 2013, 04:01:54 PM
Quote from: sbeaver44 on May 27, 2013, 03:26:16 PM
Anyone else experiencing Google Maps' refusal to route over I-94/Bishop Ford Freeway in Chicago?  Even if I try to drag the route onto I-94 it avoids it... is there some closure that, even though I have tried to research, I should be aware of?

It appears that I-94 on Google Maps is "broken" between Sibley and I-57.  No obvious reason that I can tell, though.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on May 27, 2013, 09:55:37 PM
Silliest fake city name I've come across: http://maps.google.com/maps?ll=32.939107,-80.039005&spn=0.131389,0.264187&gl=us&t=m&z=13
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on May 28, 2013, 12:44:46 AM
Wouldn't surprise me if that's what all the local realtors call it.  Still, seems like it could be shortened. Maybe: Nocha O'Marclar.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on May 28, 2013, 01:15:30 AM
Quote from: vtk on May 28, 2013, 12:44:46 AM
Wouldn't surprise me if that's what all the local realtors call it.
Probably chicken and egg - some realtor database has it and Google imported that. Or maybe the Goog was first.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on May 28, 2013, 10:25:04 PM
Look for Northeast and Southwest Rural West Ashley to appear.

Why are these little outposts suddenly becoming so prominent, in the eyes of Goofle?
Title: Re: Incorrect highways marked on Google Maps
Post by: rebel049 on May 30, 2013, 06:41:48 PM
After having many attempts to have Google correct obvious errors falling on deaf ears I wan't to thank all of you for confirming that it just isn't happening to me. After seeing this post being on 34 pages, I decided to read through all of the responses, and again, I want to thank all of you for the best laugh I have had in a long time for sharing your crazy findings and awesome humor.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on May 31, 2013, 03:29:04 AM
Quote from: Eth on May 23, 2013, 05:33:05 PM
Quote from: myosh_tino on May 23, 2013, 03:00:28 PM
Quote from: Eth on May 22, 2013, 09:48:14 PM
In Google's defense, both of these routes (https://maps.google.com/?ll=33.806618,-117.919929&spn=0.003312,0.005622&t=m&z=18) are indeed signed.
If you zoom out two levels you'll see two routes... US 66 and SR-49.  I suspect US 66 is part of Cars Land at Disney's California Adventure.  Route 49 probably pays homage to CA-49 which runs right through the heart of California's gold country.  I seem to recall seeing a CA-49 route shield at Disney's California Adventure during my last visit back in 2008.

Indeed, that's precisely what I was referring to. I saw those firsthand when I was there on Tuesday. Rather amusing that Google gave them the full treatment.

This isn't the first time that this has been brought up.

Quote from: OCGuy81 on September 16, 2011, 10:36:25 AM
Interesting little note on Google Maps.

If you zoom in on Disneyland, specifically Disney's California Adventure, the trail that encircles the park actually shows up on Google Maps as CA-49.  It's funny, because there ARE CA-49 novelty shields as you walk the park, and I guess someone at Google took it literally.

They also show CA-66 where "Cars" Land is under construction.

I'm unsure how to post Google Map images, but it's worth checking out if you're interested in Google errors.
Title: Re: Incorrect highways marked on Google Maps
Post by: flowmotion on June 04, 2013, 12:54:49 AM
The San Francisco-Oakland Bay Bridge's primary label is now "Lincoln Hwy", and the secondary label is "Dwight D. Eisenhower Hwy". Thanks a lot, roadgeeks.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on June 04, 2013, 01:06:39 AM
Oh, my God, Google! How can they fuck that up?! Man, I hate Google Maps so much! It's so discouraging to me having to see all these errors being made by Google, I just want it to burn! If Google is making this many errors on an occasional basis, they really should just kill the Google Maps service, redo it, and do it right the first time so that we wouldn't have to keep documenting these erroneous entires Google keeps on inputting!
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on June 04, 2013, 08:06:57 AM
Judging by the "new Google Maps" thread, re-doing the service will only make things worse...
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on June 04, 2013, 01:02:02 PM
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fts3.mm.bing.net%2Fth%3Fid%3DH.5038744925505726%26amp%3Bpid%3D1.7&hash=7f7589c0772ccd69e4d87498d7882a8869af5f3b)
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on June 05, 2013, 09:36:57 AM
When was that strip and what's the context?
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on June 05, 2013, 10:37:11 AM
The copyright looks like 2009, but I'm not entirely sure.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fgeauxgirl.files.wordpress.com%2F2010%2F02%2Fimage001.png&hash=da106d127f324646cb295ca64c4880949325d34b)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fgeauxgirl.files.wordpress.com%2F2010%2F02%2Fimage002.png&hash=7009acfc0e8b925dc82d60a72d7beb58303f89d9)
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on June 05, 2013, 01:59:09 PM
Pearls Before Swine - United Features Syndicate (date pretty much is '09)

Anyways, moving back to the topic at hand, I just am so discouraged by these errors that Google makes on their maps so much. Mapquest is about the only thing close to reliable, same with Bing and Yahoo.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on June 05, 2013, 04:49:09 PM
Quote from: Billy F 1988 on June 05, 2013, 01:59:09 PM
Mapquest is about the only thing close to reliable, same with Bing and Yahoo.

I had abandoned Mapquest and Yahoo quite a while ago, though I do sometimes use Bing Maps.  Since you said that, I did a quick glance at all three again, and I still find all three of them falling short of Google, despite the latter's mistakes.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on June 05, 2013, 07:36:17 PM
Quote from: kphoger on June 05, 2013, 04:49:09 PM
Quote from: Billy F 1988 on June 05, 2013, 01:59:09 PM
Mapquest is about the only thing close to reliable, same with Bing and Yahoo.

I had abandoned Mapquest and Yahoo quite a while ago, though I do sometimes use Bing Maps.  Since you said that, I did a quick glance at all three again, and I still find all three of them falling short of Google, despite the latter's mistakes.

Yeah. Mapquest, Bing and Yahoo do have their shortcomings, but certainly don't input silly labels like "Northwest Rural West Ashley" and things like that and they do have shortcomings using the appropriate route markers. Yes, the three fall short behind the Goog, it's just that Google makes a lot of mistakes while mistakes by Yahoo, Bing, and Mapquest aren't as prominent, but that doesn't mean all are mistake-free, per se. And not all are 100% accurate.
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on June 05, 2013, 09:58:42 PM
There's one particular road in México that's shown on three out of those four mapping programs.  Google is the only one that doesn't show it.  The road does not exist in real life.  This is the kind of thing Google is pretty good at.  The others seem to get their information all from the same place.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on June 09, 2013, 05:43:54 PM
Quote from: formulanone on May 23, 2013, 08:34:04 PM
So...who's up for suggesting US 498 to Google for a small part of Animal Kingdom?

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ffarm1.staticflickr.com%2F119%2F307349622_0969989d7f_z.jpg&hash=32a48585cdfd5d430b27479f017cd90528d3dc5a)
What's the logo at the bottom? Looks like crossed swords.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on June 09, 2013, 06:32:04 PM
Those are swords but are implied to be as shovels.
Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on June 09, 2013, 06:35:56 PM
Google Maps shows TN 110 as continuing south (https://www.google.com/maps/preview#!data=!1m4!1m3!1d20363!2d-86.869205!3d34.9830498) into Alabama along AL 53 to end at I-65. Of course, this isn't the case.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on June 10, 2013, 02:27:54 PM
Quote from: Steve on June 09, 2013, 05:43:54 PM
What's the logo at the bottom? Looks like crossed swords.

It's a "Diggs County" logo, with crossed shovels. The California Division of Public Works used a pick axe and a shovel in the same spot. There's also a "re-purposed" shield nearby...you can see where embossed 498 once appeared, but it's painted over.

Looking at the shield gallery, it looks like Disney did their homework.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 10, 2013, 03:41:50 PM
Quote from: formulanone on June 10, 2013, 02:27:54 PM
Looking at the shield gallery, it looks like Disney did their homework.
Usually :bigass:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.themeparkreview.com%2Fforum%2Ffiles%2Fdsc01429.jpg&hash=d9bf08e6ed192698fa531f0def72b5a31ad8c354)
Title: Re: Incorrect highways marked on Google Maps
Post by: 1995hoo on June 10, 2013, 04:36:43 PM
I noted today that Google Maps shows I-66 shields from Somerset to Paducah. Those aren't actually posted out there yet, are they?
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on June 10, 2013, 05:32:54 PM
Not so much an incorrect highway, but I noticed when driving home from Maine a few days ago that Google refuses to route you over several stretches of US 1 in New Hampshire. First was US 1 Bypass over the Long Bridge, which I presume they never updated after it reopened recently, and then another stretch of US 1 just south of where the Bypass merges (essentially right by the restaurant where the Portsmouth meet was held). When driving on it, the Navigation app on my phone freaked out and displayed a combination "We couldn't find a route" and a constant rerouting to nearby roads.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on June 10, 2013, 05:40:53 PM
Quote from: deathtopumpkins on June 10, 2013, 05:32:54 PM
Not so much an incorrect highway, but I noticed when driving home from Maine a few days ago that Google refuses to route you over several stretches of US 1 in New Hampshire. First was US 1 Bypass over the Long Bridge, which I presume they never updated after it reopened recently, and then another stretch of US 1 just south of where the Bypass merges (essentially right by the restaurant where the Portsmouth meet was held). When driving on it, the Navigation app on my phone freaked out and displayed a combination "We couldn't find a route" and a constant rerouting to nearby roads.

similarly, there is a segment of CA-67 near my house that - at least as of several months ago - could not be routed over.  I have no idea why the glitch; the road has been unmodified for years.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on June 10, 2013, 06:08:16 PM
Quote from: 1995hoo on June 10, 2013, 04:36:43 PM
I noted today that Google Maps shows I-66 shields from Somerset to Paducah. Those aren't actually posted out there yet, are they?

Pretty sure that's in their database as "Future I-66" and they still haven't figured out how to display bannered routes properly.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on June 10, 2013, 06:16:55 PM
Quote from: NE2 on June 10, 2013, 03:41:50 PM
Quote from: formulanone on June 10, 2013, 02:27:54 PM
Looking at the shield gallery, it looks like Disney did their homework.
Usually :bigass:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.themeparkreview.com%2Fforum%2Ffiles%2Fdsc01429.jpg&hash=d9bf08e6ed192698fa531f0def72b5a31ad8c354)

Unfortunately, that shield (along with all the other shields and signs) are gone, as of my trip in January 2013. They remodeled the Test Track with more GM money to make it look more futuristic, and less rustic. :( Would like to know where it wound up, though...usually, Disney has a penchant for saving all their old crap.

Is that a I-405 shield off to the side?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 10, 2013, 06:26:46 PM
Quote from: formulanone on June 10, 2013, 06:16:55 PM
Is that a I-405 shield off to the side?
Yep, neutered. Found another photo:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi244.photobucket.com%2Falbums%2Fgg8%2Fwdwmemories%2F2TE%2Fepcot-test-track-picture-020.jpg&hash=fb60579b27fd5eba49423c55383b776a100cd47a)
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on June 10, 2013, 06:36:44 PM
There were some I-405 shields in Hilliard, Ohio for several months a few years ago.  A driving school called "Drive 405" or something like that popped up in a strip mall.  Their logo included a neutered Interstate 405 shield, which was drawn with something like Tahoma in print ads.  But on the signage above the storefront, they had a pattern-accurate, retroreflective I-405 shield mounted. 

Would have been funny to see that show up on Google Maps somehow.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on June 23, 2013, 08:29:31 AM
Now, there is a part of the PA/DE state line that has completely vanished  http://goo.gl/maps/bCZJ4 (http://goo.gl/maps/bCZJ4)   :confused:
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on June 23, 2013, 09:56:50 AM
DE is DE; PA is PA.  But also, PA is DE, and DE is PA.  All four of these are true.  Clearly, the states have been annexed by Alanland.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on June 23, 2013, 04:10:45 PM
Quote from: codyg1985 on June 09, 2013, 06:35:56 PM
Google Maps shows TN 110 as continuing south (https://www.google.com/maps/preview#!data=!1m4!1m3!1d20363!2d-86.869205!3d34.9830498) into Alabama along AL 53 to end at I-65. Of course, this isn't the case.

As someone attempting to fix this issue, is there a designation for the road that is a continuation of TN 110 to AL 53?  Does AL 53 really travel south on that poor road along the railroad, and not down 251?

BTW - I a member of Google Mapmaker, the people who actually fix these sort of issues, so feel free to send me a message with errors, so I can try to correct them.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on June 23, 2013, 04:39:04 PM
Jones Avenue is the signed truck route/through route to I-65. SR 53 however uses 6th to Ardmore.
http://aldotgis.dot.state.al.us/GeneralHighwayPDF/co42.pdf
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on June 23, 2013, 04:47:27 PM
Quote from: kphoger on May 21, 2013, 08:17:32 PM
You want proof that all they do is draw lines over their own satellite imagery?  Here it is.

This is obviously in the process of being upgraded from a three-way at-grade intersection to a four-way cloverleaf:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fmexsat1_zpsdbf4f547.png&hash=68d46fc43101d3524d62c9dd218bc6a1e7830e07)

And so the Goog gives us this quite unuseful map:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1092.photobucket.com%2Falbums%2Fi410%2Fkphoger%2Fmexsat2_zps600014dd.png&hash=4f4c7d5df30e380082377086e5d726d1d3d7b600)

Unfortunately, that was likely done by bots.  Google uses many bots to update information all the time.  It is actually a pain the the ass for those of us who try to keep our local areas up-to-date and correct.  Some bots trace over the satellite imagery, others, pull information from hundreds of sources for road names, business names and locations, but some of the sources are 10, 15, 20, up to 50 years old, and no one bothers to tell the bots to compare the information between sources before publishing, so suddenly, you will have businesses appear that hadn't existed in your lifetime, or road names revert to those prior to a county or citywide renaming of streets for emergency services, or even revert highway names and locations to those that were in existence in 1960... even if the road bed doesn't even exist in that area anymore.  It is a constant struggle, and while the bots are helpful to get things started, they are a pain in the ass when they change items you have been working meticulously on for weeks and months, or when a Google Moderator denies a change of yours because it doesn't match their information, because they never bothered to look up the business or check another source, just the bot or their existing database.  Hell, I've been struggling just to get the Hoosier Heartland Highway labeled since before it opened, and they are still trying to revert it.

Then again, especially in Indiana, I refuse to remove routes that used to travel through cities, simply because INDOT decided to make them discontinuous to save money.  INDOT actually removed SR 25 and 26, along with other from Lafayette and West Lafayette in order to save money, but without them on Google Maps, most people would get lost in those cities, because they don't know their way around otherwise.
Title: Re: Incorrect highways marked on Google Maps
Post by: Avalanchez71 on June 23, 2013, 10:22:25 PM
It appears that Google still has the old US 11 through Athens, TN marked as US 11.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on June 23, 2013, 11:04:39 PM
Why doesn't Google get rid of the bots?  As it stands now, they're worse than useless.  No wonder their data is so bad.  Bots?  Data over 10 years old?  It's as if they're TRYING to make their maps bad!

Not that it wasn't obvious that quality was not a concern when they switched from NavTeq to TeleAtlas way back when.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on June 24, 2013, 01:20:29 PM
Quote from: vdeane on June 23, 2013, 11:04:39 PM
Why doesn't Google get rid of the bots?  As it stands now, they're worse than useless.  No wonder their data is so bad.  Bots?  Data over 10 years old?  It's as if they're TRYING to make their maps bad!

Not that it wasn't obvious that quality was not a concern when they switched from NavTeq to TeleAtlas way back when.

This is one of those questions we as GMM Reviewers keep asking.  It is especially bad when a Google Employee trusts the bot over that of someone who lives in the area.  It will take approval by 5-10 reviewers to override an Employee or even some Bots.

Then again, the system is good in other ways, like who shorting after the I-5 Bridge Collapse in Washington, I removed the bridge to prevent traffic routing.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on June 24, 2013, 07:40:07 PM
On the other hand, I also HATE the way Google marks roads as not existing when they're merely closed.  What if you're using the map for planning a trip for after the road re-opens, or just finding out where a route goes for the heck of it?  Google will often delete a road immediately but take months to put it back.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on June 24, 2013, 08:40:47 PM
Quote from: vdeane on June 24, 2013, 07:40:07 PM
On the other hand, I also HATE the way Google marks roads as not existing when they're merely closed.  What if you're using the map for planning a trip for after the road re-opens, or just finding out where a route goes for the heck of it?  Google will often delete a road immediately but take months to put it back.
One of the more annoying "features" of Google is the random missing bits of roads that you can't see until you try to route over them. I've had turn penalties that mysteriously disappear when you double back to an area on a circuitous routing, tiny gravel roads faster than the straight routes they parallel, and 2-hour detours for some nonexistent break in the only road that goes through an area. Considering that I try to time my days to fill daylight, an extra 10-15 minutes here and there can mean the difference between seeing extra bridges, scenic views, etc., or burning straight through.
Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on June 24, 2013, 08:44:13 PM
Quote from: TEG24601 on June 23, 2013, 04:10:45 PM
Quote from: codyg1985 on June 09, 2013, 06:35:56 PM
Google Maps shows TN 110 as continuing south (https://www.google.com/maps/preview#!data=!1m4!1m3!1d20363!2d-86.869205!3d34.9830498) into Alabama along AL 53 to end at I-65. Of course, this isn't the case.

As someone attempting to fix this issue, is there a designation for the road that is a continuation of TN 110 to AL 53?  Does AL 53 really travel south on that poor road along the railroad, and not down 251?

BTW - I a member of Google Mapmaker, the people who actually fix these sort of issues, so feel free to send me a message with errors, so I can try to correct them.

AL 53 does indeed travel west along 6th street from AL 251's northern terminus before turning south (but signed north) along the road next to the railroad before going under the railroad via a one-way tunnel controlled with a traffic signal. There is nothing in the field that I can see that indicates that TN 110 is signed past its southern terminus with AL 53/TN 7. TN 7 officially ends about a 1/4 mile to the east of TN 110 at the Giles/Lincoln County line, all multiplexed with AL 53.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on June 24, 2013, 11:20:06 PM
Quote from: codyg1985 on June 24, 2013, 08:44:13 PM
Quote from: TEG24601 on June 23, 2013, 04:10:45 PM
Quote from: codyg1985 on June 09, 2013, 06:35:56 PM
Google Maps shows TN 110 as continuing south (https://www.google.com/maps/preview#!data=!1m4!1m3!1d20363!2d-86.869205!3d34.9830498) into Alabama along AL 53 to end at I-65. Of course, this isn't the case.

As someone attempting to fix this issue, is there a designation for the road that is a continuation of TN 110 to AL 53?  Does AL 53 really travel south on that poor road along the railroad, and not down 251?

BTW - I a member of Google Mapmaker, the people who actually fix these sort of issues, so feel free to send me a message with errors, so I can try to correct them.

AL 53 does indeed travel west along 6th street from AL 251's northern terminus before turning south (but signed north) along the road next to the railroad before going under the railroad via a one-way tunnel controlled with a traffic signal. There is nothing in the field that I can see that indicates that TN 110 is signed past its southern terminus with AL 53/TN 7. TN 7 officially ends about a 1/4 mile to the east of TN 110 at the Giles/Lincoln County line, all multiplexed with AL 53.

It should be fixed now.  I've already reported the error in the state line, and am working out the Truck route from TN-7 to AL-53.  That should be taken care of shortly.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 07, 2013, 10:39:40 AM
Not quite an error on Google Maps, but: http://www.google.com/search?q=springfield+mo+county
Title: Re: Incorrect highways marked on Google Maps
Post by: codyg1985 on July 10, 2013, 08:24:06 AM
I-49 in MO is now labeled as I-49B.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 10, 2013, 08:29:45 AM
Quote from: codyg1985 on July 10, 2013, 08:24:06 AM
I-49 in MO is now labeled as I-49B.
Directions have been labeling it "I49Bus" for quite some time. The shields are new.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on July 10, 2013, 05:01:12 PM
Quote from: codyg1985 on July 10, 2013, 08:24:06 AM
I-49 in MO is now labeled as I-49B.
Most likely, its actually referring to a business loop of 49, probably correct.  Same case with the I-196B in Michigan.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 10, 2013, 05:14:30 PM
Quote from: Molandfreak on July 10, 2013, 05:01:12 PM
Quote from: codyg1985 on July 10, 2013, 08:24:06 AM
I-49 in MO is now labeled as I-49B.
Most likely, I didn't look at the Goog.
PS: they seem to have rolled out the new style as default.
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on July 10, 2013, 05:17:16 PM
Every single classified road in the UK is the wrong colour.

Though it's more that it is vomit-inducing, eye-hurting cartography.

And that's the least-worst New Maps change coming - at least it is still usable at the moment, even if your eyes hurt.
Quote from: Molandfreak on July 10, 2013, 05:01:12 PM
Quote from: codyg1985 on July 10, 2013, 08:24:06 AM
I-49 in MO is now labeled as I-49B.
Most likely, its actually referring to a business loop of 49, probably correct.  Same case with the I-196B in Michigan.
No, the whole lot. Plus the business loops.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on July 10, 2013, 06:50:26 PM
Quote from: english si on July 10, 2013, 05:17:16 PM
Every single classified road in the UK is the wrong colour.
You mean the correct color. No "u." Amerika uber alles!
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on July 10, 2013, 08:51:30 PM
The new style makes me want to throw up.  Worse, it's unusable.  Everything that isn't a freeway or a major arterial looks like a minor road.  The only good thing about it is they finally stopped calling every road in Mexico a freeway.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on July 11, 2013, 07:47:29 AM
It is even worse in Spain, where expressways (autovías) are marked as regular roads :banghead:.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 11, 2013, 10:57:21 AM
A piece of Florida's Turnpike STILL disappears when you zoom out: https://maps.google.com/maps?hl=en&ll=28.652031,-81.702576&spn=1.85341,3.628235&gl=us&t=m&z=9
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on July 11, 2013, 04:04:56 PM
Quote from: NE2 on July 10, 2013, 05:14:30 PM
Quote from: Molandfreak on July 10, 2013, 05:01:12 PM
Quote from: codyg1985 on July 10, 2013, 08:24:06 AM
I-49 in MO is now labeled as I-49B.
Most likely, I didn't look at the Goog.
PS: they seem to have rolled out the new style as default.
PS: I'm on vacation in Denmark and I don't have any non-mobile devices on me so I couldn't accurately look at the full version of google maps. GMAB.
Title: Re: Incorrect highways marked on Google Maps
Post by: exit322 on July 11, 2013, 04:34:00 PM
Quote from: NE2 on June 10, 2013, 06:26:46 PM
Quote from: formulanone on June 10, 2013, 06:16:55 PM
Is that a I-405 shield off to the side?
Yep, neutered. Found another photo:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi244.photobucket.com%2Falbums%2Fgg8%2Fwdwmemories%2F2TE%2Fepcot-test-track-picture-020.jpg&hash=fb60579b27fd5eba49423c55383b776a100cd47a)

Don't give them any ideas.
Title: Re: Incorrect highways marked on Google Maps
Post by: exit322 on July 11, 2013, 04:36:32 PM
Quote from: vdeane on June 23, 2013, 09:56:50 AM
DE is DE; PA is PA.  But also, PA is DE, and DE is PA.  All four of these are true.  Clearly, the states have been annexed by Alanland.

Oblast boundaries are subject to change with and without notice.

https://www.aaroads.com/forum/index.php?topic=7720.275
Title: Re: Incorrect highways marked on Google Maps
Post by: Thing 342 on July 12, 2013, 11:46:13 AM
The Seward Hwy and Minnesota Dr freeways south of Anchorage are still shown as regular arterials.
Title: Re: Incorrect highways marked on Google Maps
Post by: Avalanchez71 on July 12, 2013, 08:46:43 PM
https://www.google.com/maps?q=wallace,+id&hl=en&ll=47.477536,-115.934515&spn=0.025438,0.066047&sll=35.830521,-85.978599&sspn=3.88749,8.453979&hnear=Wallace,+Shoshone,+Idaho&t=m&z=15 (https://www.google.com/maps?q=wallace,+id&hl=en&ll=47.477536,-115.934515&spn=0.025438,0.066047&sll=35.830521,-85.978599&sspn=3.88749,8.453979&hnear=Wallace,+Shoshone,+Idaho&t=m&z=15)

Hey look US 10 in Wallace, ID has been recommissioned.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on July 12, 2013, 11:44:06 PM
That's to imply, in my opinion, the original route as such, not as I-90 Business. A lot of Wallace residents do tend to call that Highway 10. Heck, Missoula does that, too, because West Broadway Street and Secondary 474 are known as Highway 10 West because US 10 ran through until 1986. I guess the Googs decided to put it there for "historic" purposes.

Oh, and get this, too. Google marks a stretch of I-90 in Missoula from Exits 96 to 104 as "E Railroad Ave" and why that is puzzles me.
https://www.google.com/maps?hl=en&ll=46.903134,-114.046326&spn=0.134408,0.338173&sll=47.477536,-115.934515&sspn=0.01662,0.042272&t=m&z=12
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on July 13, 2013, 12:16:07 AM
Quote from: Billy F 1988 on July 12, 2013, 11:44:06 PM
That's to imply, in my opinion, the original route as such, not as I-90 Business. A lot of Wallace residents do tend to call that Highway 10. Heck, Missoula does that, too, because West Broadway Street and Secondary 474 are known as Highway 10 West because US 10 ran through until 1986. I guess the Googs decided to put it there for "historic" purposes.

Oh, and get this, too. Google marks a stretch of I-90 in Missoula from Exits 96 to 104 as "E Railroad Ave" and why that is puzzles me.
https://www.google.com/maps?hl=en&ll=46.903134,-114.046326&spn=0.134408,0.338173&sll=47.477536,-115.934515&sspn=0.01662,0.042272&t=m&z=12

You are correct.  The road in MapMaker is listed as "I-90 Business" Official/Obscure with "Old US 10" as Local/Primary.  I hate seeing it that way, but when I try to correct it, someone from the local area reverts it, so I don't fight it much anymore.
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on July 22, 2013, 07:25:31 PM
Not a highway, but according to google, the Scottish island of Jura (https://www.google.com/maps?q=Isle+of+Jura&hl=en&ll=55.903806,-5.940857&spn=0.617419,1.234589&sll=55.9492,-5.862579&sspn=0.616696,1.234589&oq=Isle+of+Jura&hnear=Isle+of+Jura,+United+Kingdom&t=m&z=10) sunk a good few weeks ago. They have formally apologised, but still haven't rectified it, despite the outline still being in their data.
Title: Re: Incorrect highways marked on Google Maps
Post by: Avalanchez71 on July 22, 2013, 10:28:10 PM
Quote from: Billy F 1988 on July 12, 2013, 11:44:06 PM
That's to imply, in my opinion, the original route as such, not as I-90 Business. A lot of Wallace residents do tend to call that Highway 10. Heck, Missoula does that, too, because West Broadway Street and Secondary 474 are known as Highway 10 West because US 10 ran through until 1986. I guess the Googs decided to put it there for "historic" purposes.

Oh, and get this, too. Google marks a stretch of I-90 in Missoula from Exits 96 to 104 as "E Railroad Ave" and why that is puzzles me.
https://www.google.com/maps?hl=en&ll=46.903134,-114.046326&spn=0.134408,0.338173&sll=47.477536,-115.934515&sspn=0.01662,0.042272&t=m&z=12
It looks like if you follow SR 200 east from there it keeps the E Railroad Ave moniker.  Is that correct?
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on July 23, 2013, 02:13:24 PM
^ And when you keep following SR-200 to US-89, it turns into E. Railroad Ave, And when you follow US-89 to I-15, That also turns into E. Railroad Ave.
Title: Re: Incorrect highways marked on Google Maps
Post by: Avalanchez71 on July 23, 2013, 04:20:42 PM
I followed E Railroad Ave through the state.
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on July 23, 2013, 05:56:50 PM
Interesting.  :hmmm:
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on July 26, 2013, 09:41:55 PM
There are now two I-580s in California. http://goo.gl/maps/bIYiv
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on July 26, 2013, 10:28:19 PM
Quote from: Molandfreak on July 26, 2013, 09:41:55 PM
There are now two I-580s in California. http://goo.gl/maps/bIYiv

Fixed.  Either an idiot remapped US 395, not knowing what they were doing, or a bot.  Either way, it is being fixed.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on July 26, 2013, 10:31:53 PM
Quote from: TEG24601 on July 26, 2013, 10:28:19 PM
Quote from: Molandfreak on July 26, 2013, 09:41:55 PM
There are now two I-580s in California. http://goo.gl/maps/bIYiv

Fixed.  Either an idiot remapped US 395, not knowing what they were doing, or a bot.  Either way, it is being fixed.
Good!
Title: Re: Incorrect highways marked on Google Maps
Post by: wxfree on July 27, 2013, 12:03:12 AM
It isn't an incorrect marking exactly, but a lack of marking that bothers me.  For some time now Google has been leaving off road names for numbered roads that don't get a highway number marker.  Numbered county roads and Farm-to-Market roads are often not labelled.  In Texas Farm-to-Market roads are "on system" and maintained as a lower class of state highways, and most of them are not identified at all on the maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on July 27, 2013, 01:12:26 AM
Quote from: wxfree on July 27, 2013, 12:03:12 AM
It isn't an incorrect marking exactly, but a lack of marking that bothers me.  For some time now Google has been leaving off road names for numbered roads that don't get a highway number marker.  Numbered county roads and Farm-to-Market roads are often not labelled.  In Texas Farm-to-Market roads are "on system" and maintained as a lower class of state highways, and most of them are not identified at all on the maps.
Yeah the lack of some highway systems appearing on google maps has always bothered me. I also don't know why they don't mark county lines. But I guess you can't please everyone.
Title: Re: Incorrect highways marked on Google Maps
Post by: jwolfer on July 30, 2013, 01:13:01 PM
Florida SR A1A is marked as SR 1A
Title: Re: Incorrect highways marked on Google Maps
Post by: deathtopumpkins on July 30, 2013, 05:46:44 PM
Now, not only does Google mark the TCH with the words "Route Transcanadienne" sticking out of a TCH shield, but there are also a few "Quebec Route 138" Quebec route shields: http://goo.gl/maps/V7lPI
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on July 30, 2013, 10:17:38 PM
Alberta 35 now extends into the Northwest Territories. http://goo.gl/maps/b9BUo
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on July 30, 2013, 10:57:48 PM
For the first time, Google is using square shields for county routes. Finally, you can tell them apart from state routes! Now, what have they done in Missouri, Virginia... West Virginia...
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on July 30, 2013, 11:18:19 PM
To be fair, most printed maps I've seen group "county" and "state secondary" together in the legend, so using a square for those routes in those states wouldn't be incorrect.  Putting "State Route C" in said square, however... (http://goo.gl/maps/A3InZ)
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on July 30, 2013, 11:22:32 PM
I think WV is just TIGER data sucking particular ass wrt fractional routes. Here's an overlap of CR 63 and CR 6/3: http://maps.google.com/maps?ll=38.435018,-81.419184&spn=0.012925,0.028346&gl=us&t=m&z=16
TIGER has both on different portions: http://www.openstreetmap.org/browse/way/15574288 http://www.openstreetmap.org/browse/way/15578989

As for Virginia, most TIGER counties (correctly) use State Route x, but some have County Route x.
Title: Re: Incorrect highways marked on Google Maps
Post by: wxfree on July 31, 2013, 12:38:15 AM
Quote from: Steve on July 30, 2013, 10:57:48 PM
For the first time, Google is using square shields for county routes. Finally, you can tell them apart from state routes! Now, what have they done in Missouri, Virginia... West Virginia...

It's an improvement over leaving them unlabelled, but the county roads look the same as the Farm-to-Market roads, which are the "state secondary routes" in Texas.  I remember them before being labelled in text, as "County Road 123" and "Farm-To-Market 1234."  I liked that and saw no reason to change it.  Still, compared with leaving them unlabelled, I prefer the rectangle markers; I can at least find what I'm looking for.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on August 09, 2013, 10:07:17 PM
Maine State Route 6 used to be Interstate 6. (It has been fixed after I reported the error.) However, NH 124 still goes into Massachusetts according to Google Maps - and ends at a random place (if it would continue, it would make sense to end at MA 119, but NH 124 actually ends at the border.) NH 122 goes a tiny bit into Massachusetts, according to Google Maps, and it ends at a tiny road! You can see the "122" on this tiny road!
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on August 10, 2013, 07:29:49 AM
Quote from: 1 on August 09, 2013, 10:07:17 PM
Maine State Route 6 used to be Interstate 6. (It has been fixed after I reported the error.) However, NH 124 still goes into Massachusetts according to Google Maps - and ends at a random place (if it would continue, it would make sense to end at MA 119, but NH 124 actually ends at the border.) NH 122 goes a tiny bit into Massachusetts, according to Google Maps, and it ends at a tiny road! You can see the "122" on this tiny road!

On a similar note, it appears that Holmes (FL) CR 171 continues into Alabama concurrent with AL 103 up to Hodges Rd (the first intersection after the state line). Similarly, Geneva (AL) CR 49 continues into Florida concurrent with Holmes CR 173 to the first intersection after the state line.

I'm gonna go out on a limb and guess that this is probably a widespread phenomenon.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on August 13, 2013, 09:12:25 PM
Now, one half of the Commodore Barry Bridge is orange and the other half is yellow   
https://www.google.com/maps?ll=39.833676,-75.375236&spn=0.003946,0.00839&t=m&dg=opt&z=17 (https://www.google.com/maps?ll=39.833676,-75.375236&spn=0.003946,0.00839&t=m&dg=opt&z=17)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 14, 2013, 12:56:19 AM
I-695 in DC (http://goo.gl/maps/2hvhk) is missing it's shields.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on August 19, 2013, 05:49:16 PM
Quote from: rickmastfan67 on August 14, 2013, 12:56:19 AM
I-695 in DC (http://goo.gl/maps/2hvhk) is missing it's shields.


The new rendering engine is playing havoc with roads like I-695, because it is too close to other roads, so it isn't sure where exactly to put them.



Quote from: deathtopumpkins on July 30, 2013, 05:46:44 PM
Now, not only does Google mark the TCH with the words "Route Transcanadienne" sticking out of a TCH shield, but there are also a few "Quebec Route 138" Quebec route shields: http://goo.gl/maps/V7lPI (http://goo.gl/maps/V7lPI)


The new engine is also auto-translating names (as the route is only labeled in English), likely due to a request by the Quebec government, and they haven't quite worked the bugs out for displaying.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on August 19, 2013, 09:53:13 PM
Quote from: TEG24601 on August 19, 2013, 05:49:16 PM
Quote from: rickmastfan67 on August 14, 2013, 12:56:19 AM
I-695 in DC (http://goo.gl/maps/2hvhk) is missing it's shields.


The new rendering engine is playing havoc with roads like I-695, because it is too close to other roads, so it isn't sure where exactly to put them.

I don't think that's the case here.  Even on the lowest zoom level where I-695 is mostly the only road in view, no shields are shown there.  Compared with I-395 nearby, has several on the same zoom level.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on August 27, 2013, 04:43:01 PM
Quote from: rickmastfan67 on August 19, 2013, 09:53:13 PM
Quote from: TEG24601 on August 19, 2013, 05:49:16 PM
Quote from: rickmastfan67 on August 14, 2013, 12:56:19 AM
I-695 in DC (http://goo.gl/maps/2hvhk) is missing it's shields.


The new rendering engine is playing havoc with roads like I-695, because it is too close to other roads, so it isn't sure where exactly to put them.

I don't think that's the case here.  Even on the lowest zoom level where I-695 is mostly the only road in view, no shields are shown there.  Compared with I-395 nearby, has several on the same zoom level.


However, when I look to edit the road, the road says "Interstate 695", so I'm still blaming it on the new engine.
Title: Re: Incorrect highways marked on Google Maps
Post by: MDOTFanFB on September 02, 2013, 05:44:53 PM
In Detroit, a very short section of Forest Avenue east of Woodward Avenue is now marked as a freeway. (http://goo.gl/maps/xAwFJ)

Scratch that. As of today, it is no longer a freeway, it has reverted back to the minor street it's supposed to be marked as.
Title: Re: Incorrect highways marked on Google Maps
Post by: Alex4897 on September 02, 2013, 09:24:50 PM
Google decided to label a southern Delaware back road as US Rte. 277.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fs23.postimg.org%2Fufnyhj14n%2Fderp.jpg&hash=84e7fd4c9b22bf8fae9e1e2540c1d2e0d85dd674) (http://postimg.org/image/ufnyhj14n/)
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on September 02, 2013, 10:48:25 PM
Quote from: wxfree on July 31, 2013, 12:38:15 AM
Quote from: Steve on July 30, 2013, 10:57:48 PM
For the first time, Google is using square shields for county routes. Finally, you can tell them apart from state routes! Now, what have they done in Missouri, Virginia... West Virginia...

It's an improvement over leaving them unlabelled, but the county roads look the same as the Farm-to-Market roads, which are the "state secondary routes" in Texas.  I remember them before being labelled in text, as "County Road 123" and "Farm-To-Market 1234."  I liked that and saw no reason to change it.  Still, compared with leaving them unlabelled, I prefer the rectangle markers; I can at least find what I'm looking for.

I too liked the all-text labeling of county roads and even FM routes in Texas.  Now that they're labelled the same, though, you have no idea whether you should expect to see a route shield, a small green sign, or neither one at all.

On the other hand......we now get to see 1111 in a route shield (Sierra Blanca, TX)!
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on September 05, 2013, 02:16:58 PM
Henries rejoice. There's now a freeway across Yosemite: http://maps.google.com/maps?hl=en&ll=37.770715,-119.42276&spn=0.834773,1.814117&t=m&z=10
Title: Re: Incorrect highways marked on Google Maps
Post by: Scott5114 on September 05, 2013, 11:50:55 PM
Quote from: Alex4897 on September 02, 2013, 09:24:50 PM
Google decided to label a southern Delaware back road as US Rte. 277.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fs23.postimg.org%2Fufnyhj14n%2Fderp.jpg&hash=84e7fd4c9b22bf8fae9e1e2540c1d2e0d85dd674) (http://postimg.org/image/ufnyhj14n/)

Too bad it's not in northern Delaware...then they could get away with saying they mixed up Newcastle, OK with New Castle, DE :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: kphoger on September 06, 2013, 03:31:42 PM
Quote from: NE2 on September 05, 2013, 02:16:58 PM
Henries rejoice. There's now a freeway across Yosemite: http://maps.google.com/maps?hl=en&ll=37.770715,-119.42276&spn=0.834773,1.814117&t=m&z=10

Oh, that Henry... (http://3.bp.blogspot.com/_QldSl87l2JM/TGe-HIGlH2I/AAAAAAAAB3c/SvZmvAlqnYA/s400/Oh_Henry_bar.jpg)
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on September 09, 2013, 03:21:51 PM
Google just recently extended US-70S in TN from it's Eastern end @ US-70 in Sparta all the up TN-111 to US-70N in Cookeville.
http://goo.gl/maps/RR6IN
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 09, 2013, 04:01:03 PM
If Google Maps was accurate:

New warning sign on MA 24 South towards exit 17:

"Warning: If using 10mi/20km scale, exit at exit 17 or you will fall off!"
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on September 09, 2013, 09:48:21 PM
Quote from: 1 on September 09, 2013, 04:01:03 PM
If Google Maps was accurate:

New warning sign on MA 24 South towards exit 17:

"Warning: If using 10mi/20km scale, exit at exit 17 or you will fall off!"
"Or switch to Satellite View"
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 11, 2013, 03:24:41 PM
Colombia has US routes.
Ecuador has Interstates.

Proof: http://goo.gl/maps/QRWy6
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on September 11, 2013, 03:38:27 PM
Americanizing foreign highways, no?
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on September 11, 2013, 03:42:23 PM
I've seen some maps using the same marker for Quebec Autoroutes as US Interstates...
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on September 11, 2013, 03:52:06 PM
yep, going the lazy route and substituting in a symbol which is "close enough".
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 11, 2013, 04:45:06 PM
Bolivia and Chile have US routes too.
Title: Re: Incorrect highways marked on Google Maps
Post by: Thing 342 on September 11, 2013, 05:36:45 PM
Apparently Alaska Route 9 got an extension: https://maps.google.com/?ll=64.071899,-141.091919&spn=0.2615,1.056747&t=m&z=11
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on September 11, 2013, 05:55:02 PM
Nova Scotia has U.S. Routes.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 11, 2013, 06:00:53 PM
Quote from: Thing 342 on September 11, 2013, 05:36:45 PM
Apparently Alaska Route 9 got an extension: https://maps.google.com/?ll=64.071899,-141.091919&spn=0.2615,1.056747&t=m&z=11

And it leads directly into Dawson, at a river. It must be Dawson's Creek (the show).


Also, check here (http://goo.gl/maps/A8qV2).
Route 253 in Quebec extends into New Hampshire, and there seems to be erroneous County Route 1 and County Route 9.

Route 253 has a completely different form in Canada within 150 feet of the border.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 11, 2013, 06:02:18 PM
Quote from: NE2 on September 11, 2013, 05:55:02 PM
Nova Scotia has U.S. Routes.

Nova Scotia seems to have words in routes that make it not fit, but I don't see US routes there.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on September 11, 2013, 06:10:11 PM
Quote from: 1 on September 11, 2013, 06:02:18 PM
Quote from: NE2 on September 11, 2013, 05:55:02 PM
Nova Scotia has U.S. Routes.

Nova Scotia seems to have words in routes that make it not fit, but I don't see US routes there.
holy crap http://en.wikipedia.org/wiki/Nova_Scotia_Trunk_2
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 11, 2013, 08:10:12 PM
This place (http://goo.gl/maps/Nx4SQ) in Nova Scotia has a 4-way concurrency between these four US routes:

4
Hwy 4
Trunk 4
Nova Scotia Trunk 4
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on September 12, 2013, 07:27:09 AM
Quote from: 1 on September 11, 2013, 03:24:41 PM
Colombia has US routes.
Ecuador has Interstates.

Proof: http://goo.gl/maps/QRWy6

Ecuador actually has "Interstates", as far as I can tell you :sombrero:. They use the same shield for their routes.
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on September 12, 2013, 12:11:05 PM
yep, '70 spec neutered, with ECUADOR in the crown.  both narrow and wide versions exist. 

I wonder if they ever used '57 or '61 spec neutered.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on September 13, 2013, 04:25:43 AM
Quote from: 1 on September 11, 2013, 03:24:41 PM
Ecuador has Interstates.
New South Wales Freeway Routes (http://www.ozroads.com.au/NSW/RouteNumbering/Freeway%20Routes/freewayroutes.htm)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.ozroads.com.au%2FNSW%2FRouteNumbering%2FFreeway%2520Routes%2F01.JPG&hash=9adad64eb2c42b480ee147399117898721f20cf1)
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadgeek2500 on September 15, 2013, 05:03:21 PM
Google got the drawings of this waterway in Cape May, NJ pretty far off

http://goo.gl/maps/qaPCv (http://goo.gl/maps/qaPCv)
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on September 15, 2013, 10:19:03 PM
Quote from: 1 on September 11, 2013, 08:10:12 PM
This place (http://goo.gl/maps/Nx4SQ) in Nova Scotia has a 4-way concurrency between these four US routes:

4
Hwy 4
Trunk 4
Nova Scotia Trunk 4


The Nova Scotia Trunk Route System uses a symbol nearly identical to the US Routes, therefor the Symbol is correct, if the duplication is not.
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on September 16, 2013, 12:22:52 AM
Quote from: TEG24601 on September 15, 2013, 10:19:03 PM
The Nova Scotia Trunk Route System uses a symbol nearly identical to the US Routes, therefor the Symbol is correct, if the duplication is not.
Uhh. The same information is literally found in the post before that.
Quote from: NE2 on September 11, 2013, 06:10:11 PM
holy crap http://en.wikipedia.org/wiki/Nova_Scotia_Trunk_2
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on September 19, 2013, 01:16:21 AM
They're jumping the gun on interstates again: http://goo.gl/maps/f3Wer
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 19, 2013, 06:36:56 AM
Quote from: Molandfreak on September 19, 2013, 01:16:21 AM
They're jumping the gun on interstates again: http://goo.gl/maps/f3Wer

They have already jumped the gun on future I-86, but now they're doing I-99!
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on September 19, 2013, 09:41:39 AM
Quote from: 1 on September 19, 2013, 06:36:56 AM
Quote from: Molandfreak on September 19, 2013, 01:16:21 AM
They're jumping the gun on interstates again: http://goo.gl/maps/f3Wer

They have already jumped the gun on future I-86, but now they're doing I-99!
I believe 86 is correct in that situation; 99 was the real point. ;-)
Title: Re: Incorrect highways marked on Google Maps
Post by: english si on September 19, 2013, 10:17:10 AM
Future Interstates are signed with blue and red shields. The question is merely a "how well?". Given that many tile mapping services struggle with bannered routes, especially Google, I can understand signing the future interstates if they are signed with more than the very occasional sign.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 19, 2013, 04:46:40 PM
MA 7 (400 feet long): http://goo.gl/maps/ETkxD

Random freeway: http://goo.gl/maps/NA5sc

36 should be 26: http://goo.gl/maps/3sRKH

Not actually 85: http://goo.gl/maps/JVZjU
Title: Re: Incorrect highways marked on Google Maps
Post by: Molandfreak on September 19, 2013, 05:02:47 PM
Quote from: english si on September 19, 2013, 10:17:10 AM
Future Interstates are signed with blue and red shields. The question is merely a "how well?". Given that many tile mapping services struggle with bannered routes, especially Google, I can understand signing the future interstates if they are signed with more than the very occasional sign.
If that's true, why don't they just jump the gun on surface street sections of future 99, 69, 11, 72, 22?, and 49, as well as "future" 66, 73, and 74?
Title: Re: Incorrect highways marked on Google Maps
Post by: briantroutman on September 19, 2013, 05:35:35 PM
Quote from: 1 on September 19, 2013, 06:36:56 AM
Quote from: Molandfreak on September 19, 2013, 01:16:21 AM
They're jumping the gun on interstates again: http://goo.gl/maps/f3Wer

They have already jumped the gun on future I-86, but now they're doing I-99!

I was going to post this but I've been beaten to it. From what I have seen, Google posts I-99 for the Williamsport to Corning section only–but not the Williamsport to I-80 stretch or the overlap with I-80 near Bellefonte and Lamar.

But the section they do have signed (Williamsport to Corning) is the only of the three "Future 99" sections that is signed. Makes me wonder how they're acquiring this data.

Quote from: english si on September 19, 2013, 10:17:10 AM
The question is merely a "how well?"...

As far as I've seen, none of the Future 99 shields is freestanding; all are ground-mounted on rectangular "FUTURE 99 CORRIDOR" assemblies. They're not signed very consistently–at best a single assembly after more significant interchanges with nothing ever on overhead guides, trailblazers, or entrance ramp signs.
Title: Re: Incorrect highways marked on Google Maps
Post by: TEG24601 on September 19, 2013, 05:41:46 PM
Remember, most of the Data comes from Local Governments, GIS, and users.  So perhaps someone is trying to be 'smart' by marking it early.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on September 19, 2013, 08:31:02 PM
I have NEVER seen anything other than the ground-mounted rectangular assemblies for future interstates; do actual banners for them even exist at all?  If they did, you'd think NY would use them rather than covering up the I-86 shields in Orange County.

The only error they have with I-86 that I can see is that they haven't marked it between Elmira and the Tioga County line yet, but that's a very recent addition (NYSDOT just got FHWA approval to sign it this week).
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on September 19, 2013, 08:49:07 PM
Quote from: vdeane on September 19, 2013, 08:31:02 PM
I have NEVER seen anything other than the ground-mounted rectangular assemblies for future interstates; do actual banners for them even exist at all?  If they did, you'd think NY would use them rather than covering up the I-86 shields in Orange County.
NC uses a couple in-between options:
(//www.aaroads.com/shields/img/NC/NC19882953i1.jpg)(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fpeople.duke.edu%2F%7Ermalme%2Frockby04.jpg&hash=7518479b14151a327383e5c5d7b3b54d5e76d9da)
Obvious drawback: the shield needs to be patched or replaced. I don't know if AASHTO would allow the former with a real Interstate shield.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on September 19, 2013, 09:00:10 PM
I think I saw the latter in a graphic somewhere.  Maybe I'll make a future I-99 shield for my website now, given that that style is actually used somewhere.
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on September 21, 2013, 09:39:52 PM
Hey Google, NY 36 goes nowhere near Whitney Point: http://goo.gl/maps/xV6pP

(Could be a typo for NY 26, which does run there)
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on September 22, 2013, 05:30:58 PM
Google Maps still thinks US 66 exists in California.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on September 24, 2013, 06:48:19 PM
I for one, am glad it's listed. If Rand McNally still cares, why not...
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on October 01, 2013, 11:33:50 PM
...and NY 41 goes nowhere near Almond (should be 21): http://goo.gl/maps/6bSos
Title: Re: Incorrect highways marked on Google Maps: Negative route number
Post by: hotdogPi on October 06, 2013, 05:04:11 PM
Negative route number: Route -157!

http://goo.gl/maps/eUhmq

Lowest route number ever?
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on October 14, 2013, 03:20:18 PM
Interstate 1D:

http://goo.gl/maps/0Hp2w

How many 1D fans would like that?
Title: Re: Incorrect highways marked on Google Maps
Post by: agentsteel53 on October 14, 2013, 03:24:00 PM
how many 1D fans are there?
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on October 14, 2013, 03:37:26 PM
That might have happened because Google put the border a little too far south, leaving that portion of 1D in the "US".
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on October 14, 2013, 04:22:31 PM
Quote from: agentsteel53 on October 14, 2013, 03:24:00 PM
how many 1D fans are there?

Plenty.  Whether or not there's any overlap with the membership of this board -- or even any overlap with the sort of people who would notice that error -- is another matter entirely.
Title: Re: Incorrect highways marked on Google Maps
Post by: D-Dey65 on October 24, 2013, 01:12:04 PM
I found two recently;

In Southwest and South Philadelphia, there are some street that are listed as Pennsylvania State Route 3021. I never saw that anywhere on my trip on the Route 36 Trolley in 2011.

In Coram, New York, the connecting street between NY 112 at Mill Road and NY 25 at Old Middle Country Road is incorrectly named "Grand Smith Road." For as long as I can remember it has been "Grant Smith Road."

:-o :confused:
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on October 24, 2013, 09:00:25 PM
Quote from: D-Dey65 on October 24, 2013, 01:12:04 PM
In Southwest and South Philadelphia, there are some street that are listed as Pennsylvania State Route 3021. I never saw that anywhere on my trip on the Route 36 Trolley in 2011.

That's because 4-diigit routes in PA are hidden (not given normal shields) and are only shown on the little white mileage signs for state highways. (Example (http://goo.gl/maps/nujpW))

You can also see more info on how the 4-ditgit routes are assigned here (http://www.pahighways.com/state/).
Title: Re: Incorrect highways marked on Google Maps
Post by: PColumbus73 on October 28, 2013, 11:24:13 AM
US 701 has been relabeled as '701B' through its entire route
Title: Re: Incorrect highways marked on Google Maps
Post by: D-Dey65 on October 30, 2013, 11:27:15 AM
Quote from: rickmastfan67 on October 24, 2013, 09:00:25 PM
You can also see more info on how the 4-ditgit routes are assigned here (http://www.pahighways.com/state/).
"This page can't be displayed."

:-(

Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on October 30, 2013, 07:05:41 PM
Quote from: D-Dey65 on October 30, 2013, 11:27:15 AM
Quote from: rickmastfan67 on October 24, 2013, 09:00:25 PM
You can also see more info on how the 4-ditgit routes are assigned here (http://www.pahighways.com/state/).
"This page can't be displayed."

:-(

Just tested that link, working fine here. :/
Title: Re: Incorrect highways marked on Google Maps
Post by: D-Dey65 on November 02, 2013, 01:43:22 AM
Quote from: rickmastfan67 on October 30, 2013, 07:05:41 PM
Just tested that link, working fine here. :/
Okay, now I see it. I don't know why it wouldn't turn up before.

:confused:
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on November 02, 2013, 07:32:49 AM
MI-28 has been downgraded to "County Route M-28".
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on November 20, 2013, 11:41:02 PM
QuoteThen Google Maps was like, "turn right on Malcolm Ten Boulevard" and I knew there were no black engineers working there
http://twitter.com/alliebland/statuses/402990270402543616
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 10, 2013, 09:26:47 PM
Happened to notice this only because I have a grandfather that used to live here. The private road (http://goo.gl/maps/CZM9A) between Pinehurst Avenue and Cabrini Boulevard in Upper Manhattan is marked as one-way the wrong direction.  (If you look at the street view of the north end, you can see a black-on-white text sign reading "One Way Do Not Enter".)
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on December 11, 2013, 02:21:32 PM
Not a highway, but the name of Las Vegas is shown completely outside of the city limit (i.e., at The Strip). However, searching for Las Vegas still brings up and highlights the city boundary, as well as the name label outside of it!
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on December 11, 2013, 05:09:54 PM
Which direction does  this  (http://goo.gl/maps/Y8IJg) road go?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 11, 2013, 05:19:35 PM
Quote from: 1 on December 11, 2013, 05:09:54 PM
Which direction does  this  (http://goo.gl/maps/Y8IJg) road go?
It's probably two roads drawn on top of each other.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 11, 2013, 06:03:07 PM
Quote from: NE2 on December 11, 2013, 05:19:35 PM
Quote from: 1 on December 11, 2013, 05:09:54 PM
Which direction does  this  (http://goo.gl/maps/Y8IJg) road go?
It's probably two roads drawn on top of each other.

Given that it's a freeway on-ramp that clearly only goes one direction, that doesn't make it any less incorrect.

(Looks like the interchange was reconstructed, and when they drew in the new ramp, they forgot to change the direction of the old pavement.)
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on January 04, 2014, 03:15:49 PM
NJ 24 is back west of Morristown: http://goo.gl/maps/Rj9gX
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 04, 2014, 11:43:57 PM
That's correct, innit? Or have they actually removed the signs?
Title: Re: Incorrect highways marked on Google Maps
Post by: Alps on January 05, 2014, 12:54:45 AM
Quote from: NE2 on January 04, 2014, 11:43:57 PM
That's correct, innit? Or have they actually removed the signs?
Signs are gone gone goneski. Even when there were more of them, they were mostly along 510.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on January 07, 2014, 09:32:42 PM
OK Google, what happened to MA 109 inside 128?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 14, 2014, 12:47:25 AM
Not a highway, but nice spam: http://maps.google.com/maps?ll=28.206434,-82.289684&spn=0.001926,0.003543&gl=us&t=m&z=19
Title: Re: Incorrect highways marked on Google Maps
Post by: DAL764 on January 16, 2014, 05:59:22 AM
Google has already brought I-685 to Alabama. Sign is (barely) seen on the under construction Southern Beltway, with the I-685 sign positioned right under the AL-108 sign. Never mind that the beltway isn't even connected to any road yet, IIRC the plan is also to put I-685 on the existing I-85 west of the interchange and move I-85 onto the Beltway for potential westward extension.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on January 23, 2014, 10:06:36 PM
 190 feet of Google's US 26 (https://maps.google.com/maps?ll=43.43949,-112.103291&spn=0.004004,0.005944&t=m&z=17)

The problem is that the US 26 marker is visible from further away.

This error is not expected to last forever.




Found 1 mile away from the "Exit 113" discussion of "Department of Redundancy Department"
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 23, 2014, 10:31:16 PM
Quote from: 1 on January 23, 2014, 10:06:36 PM
190 feet of Google's US 26 (https://maps.google.com/maps?ll=43.43949,-112.103291&spn=0.004004,0.005944&t=m&z=17)
That used to be US 26. They probably tried to move it but being the Goog cocked it up.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 12, 2014, 04:19:29 AM
Google now thinks that US-19 Truck here in Pittsburgh is 'US-19 Bypass'. :banghead:

http://goo.gl/maps/4y3su
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on March 01, 2014, 07:28:08 PM
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fmaps.googleapis.com%2Fmaps%2Fapi%2Fstaticmap%3Fcenter%3D44.645758%2C-72.834206%26amp%3Bzoom%3D13%26amp%3Bsize%3D400x400%26amp%3Bsensor%3Dfalse&hash=ecd046f1b5f5e3832dfd1150e459c25870b4da32)

Grand Army of the Republic Highway? This is the intersection of VT 15 and VT 108, not US 6!

Note: A road does exist behind the town name. That is not an error.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 01, 2014, 07:39:12 PM
That's actually right.  VT 15 is indeed called the Grand Army of the Republic Highway.
Title: Re: Incorrect highways marked on Google Maps
Post by: Roadsguy on March 21, 2014, 10:04:06 AM
Quote from: rickmastfan67 on February 12, 2014, 04:19:29 AM
Google now thinks that US-19 Truck here in Pittsburgh is 'US-19 Bypass'. :banghead:

http://goo.gl/maps/4y3su

Yes, all truck routes seem to be rendered as bypass. At least actual bannered routes is a start...
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on March 21, 2014, 10:37:57 AM
Part of US 60 in Louisville, KY is signed along the wrong streets.  It is basically signed along the home stretches of both US 31E and US 31W into each other, but in one place it deviates from US 31W.
https://www.google.com/maps/place/Louisville,+KY/@38.2287794,-85.7858591,15z/data=!4m2!3m1!1s0x88690b1ab35bd511:0xd4d3b4282071fd32 

Where US 60 is on Dixie Highway just east of US 31W is not.  US 60 is concurrent with US 31W.
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on May 22, 2014, 05:30:06 PM
Apparently Google somehow thought NYSDOT decided to sign NY N. Main St through Manchester: http://goo.gl/maps/9ycFK

Google also thinks that NY 19A doesn't exist and there's two NY 19's between Gainesville and Fillmore: http://goo.gl/maps/gT1bD (and this appears to be an isolated issue; US 20A, NY 15A, NY 33A, NY 31F, etc. are all displayed correctly)
Title: Re: Incorrect highways marked on Google Maps
Post by: Thing 342 on May 23, 2014, 05:42:38 PM
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg.tapatalk.com%2Fd%2F14%2F05%2F24%2Fupesusev.jpg&hash=3de52cd30efc7a377ae1335f0b0844f7768df7d0)I-1 in Bristol, VA/TN?
Title: Re: Incorrect highways marked on Google Maps
Post by: Legodinodoctor on June 21, 2014, 01:04:06 PM
Quote from: Thing 342 on May 23, 2014, 05:42:38 PM
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg.tapatalk.com%2Fd%2F14%2F05%2F24%2Fupesusev.jpg&hash=3de52cd30efc7a377ae1335f0b0844f7768df7d0)I-1 in Bristol, VA/TN?
I'm Suprised that There's an interstate 1, and this is nearing 1,000 Posts  :ded:
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on July 26, 2014, 11:34:49 PM
Way to go, Google, YOU JUST DESTROYED PART OF I-86!: http://goo.gl/maps/S56jn
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on July 26, 2014, 11:59:14 PM
Quote from: WNYroadgeek on July 26, 2014, 11:34:49 PM
Way to go, Google, YOU JUST DESTROYED PART OF I-86!: http://goo.gl/maps/S56jn

According to DOT and Google Traffic, that section is currently closed to traffic and has been since the end of May. Detour is along old NY 17. Google takes stuff off the map if it's a medium to long term closure. There are a few ramps missing in Binghamton (Exit 4) and downtown Columbus, OH (I-71/I-670) for the same reason.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 27, 2014, 12:01:39 AM
Quote from: WNYroadgeek on July 26, 2014, 11:34:49 PM
Way to go, Google, YOU JUST DESTROYED PART OF I-86!: http://goo.gl/maps/S56jn

It's still there.  Just have to zoom in.  However, it's flagged as this: "Construction Status: Closed for maintenance".  No idea why.  But happened on July 21st.
Title: Re: Incorrect highways marked on Google Maps
Post by: cu2010 on July 27, 2014, 07:47:51 AM
That section of I-86 is currently closed for major reconstruction...much needed, as the concrete pavement on that segment was in really rough shape, to the point where your ass could start aching after driving over it.

Traffic is currently being detoured along NY417/Business US219.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on July 27, 2014, 05:32:03 PM
I wonder why they didn't do lane shifts/closures.  Well, it's R5...
Title: Re: Incorrect highways marked on Google Maps
Post by: KEVIN_224 on July 27, 2014, 05:51:35 PM
http://goo.gl/maps/DcES3

This is with Newark, DE near the Maryland border. The road northeast from the state line up to Christiana Parkway was changed from DE Route 2 to DE Route 279 last fall.

I was on that stretch this past June 17th. There was a DE Route 279 shield soon after the state line, but my picture doesn't show it.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FQtZFV6F.jpg&hash=92485a8b1cf622b7dd81efc38b935fac339615ee)
Title: Re: Incorrect highways marked on Google Maps
Post by: cu2010 on July 27, 2014, 06:51:06 PM
Quote from: vdeane on July 27, 2014, 05:32:03 PM
I wonder why they didn't do lane shifts/closures.  Well, it's R5...

Environmental concerns, allegedly. Apparently with the close proximity of the Allegheny River to the project site (there are a few sections that practically hug the side of the river), they were forced to outright close the entire highway.

Typical NY PR nonsense. More than likely the real reason is "because everyone in Albany is on crack". :pan:
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 27, 2014, 08:39:33 PM
Quote from: cu2010 on July 27, 2014, 06:51:06 PM
Quote from: vdeane on July 27, 2014, 05:32:03 PM
I wonder why they didn't do lane shifts/closures.  Well, it's R5...

Environmental concerns, allegedly. Apparently with the close proximity of the Allegheny River to the project site (there are a few sections that practically hug the side of the river), they were forced to outright close the entire highway.

Typical NY PR nonsense. More than likely the real reason is "because everyone in Albany is on crack". :pan:

Is there a PR release on this that you can link me to? Need to update OSM and want to have the PR to back up the edit.
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on July 27, 2014, 09:02:53 PM
Quote from: cu2010 on July 27, 2014, 06:51:06 PM
Quote from: vdeane on July 27, 2014, 05:32:03 PM
I wonder why they didn't do lane shifts/closures.  Well, it's R5...

Environmental concerns, allegedly. Apparently with the close proximity of the Allegheny River to the project site (there are a few sections that practically hug the side of the river), they were forced to outright close the entire highway.

Typical NY PR nonsense. More than likely the real reason is "because everyone in Albany is on crack". :pan:

I'd like to think that it's because they're trying to limit the amount of time spent doing construction on Seneca land. The road is in pretty crappy shape and they might be doing a full rebuild on both sides, including foundation work (which it certainly needs). With how narrow the ROW is, there really isn't space for anything off of the shoulder. For much of it, one side is the river and the other is a state park.

But, as was mentioned, this is R5. They've been closing down an entire side of NY 33 in Buffalo every night for a month for the mill and fill project. For the NY 400 overlay, they ground up the paint and restriped the road at least three separate times before doing the overlay. Project started in May, half of the overlay zone still isn't done. The I-290 bridge replacement project supposedly started two months ago and they just installed temporary traffic lights for the ramp closures. I would have just done a lane shift, but it's not like old NY 17 can't handle the relatively small amount of traffic that goes through there (except in Salamanca, which is a mess).
Title: Re: Incorrect highways marked on Google Maps
Post by: cu2010 on July 27, 2014, 09:26:29 PM
Quote from: rickmastfan67 on July 27, 2014, 08:39:33 PM
Is there a PR release on this that you can link me to? Need to update OSM and want to have the PR to back up the edit.

https://www.dot.ny.gov/news/press-releases/2014/2014-05-02
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 27, 2014, 10:44:12 PM
Quote from: cu2010 on July 27, 2014, 09:26:29 PM
Quote from: rickmastfan67 on July 27, 2014, 08:39:33 PM
Is there a PR release on this that you can link me to? Need to update OSM and want to have the PR to back up the edit.

https://www.dot.ny.gov/news/press-releases/2014/2014-05-02

Thanks!  Now have updated OSM in Changeset #24394677 (https://www.openstreetmap.org/changeset/24394677).  Also have created a note on OSM so that you or anybody else can let everybody know when it might re-open so that OSM can be updated and have I-86 tags updated to allow it to be routed on once again. - https://www.openstreetmap.org/note/207176
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on October 19, 2014, 03:40:29 PM
Well, I hate to break the news to this particular thread, but the Googs now appear to have marked Continental Drive south of Butte as "route 375" and Montana Highway 2 with a "quasai concurrency" of "route 393". Those don't exist in Butte. And those "routes" per se, are Secondary route numbers that are farther east than they appear to be "according" to Google. Yeah. Just because you think MT 2 is "concurrent" with SR 393 doesn't mean anything to me at all. And Continental Drive is a local artery that connects with I-90 and MT 2 and should not warrant a Secondary designation based on the low traffic volume there.

Want proof of my find? Click the link to validate this discovery: https://www.google.com/maps/@45.957493,-112.4578503,12z
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on October 19, 2014, 05:40:51 PM
393 looks like someone made an honest mistake at some point in the past, because 393 does continue south from that point, and 2 is poorly signed north of there. 375 appears to be a historical relic, as I did find references to a highway 375 in some random newspaper articles from the 60s, and also there are arrowhead 375 signs along highway 2 at the southern intersection in street view. Not in the road log now though. Both fixed now, so that should be updated on Maps soon.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on October 21, 2014, 12:51:28 PM
US 1-9 Truck is now US 1-9 Bipass :bigass:
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on October 21, 2014, 12:54:55 PM
Several ramps on the New Jersey Turnpike are marked with white instead of their usual colors. (See Exits 3 and 5) Strangely, this doesn't happen for exit 8A, where NJ 32 is also marked in white on Google Maps, but the ramps are their normal colors.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on October 21, 2014, 07:37:17 PM
Quote from: NE2 on October 21, 2014, 12:51:28 PM
US 1-9 Truck is now US 1-9 Bipass :bigass:

Same with US-19 Truck here in Pittsburgh.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on October 22, 2014, 01:54:24 AM
Quote from: rickmastfan67 on October 21, 2014, 07:37:17 PM
Quote from: NE2 on October 21, 2014, 12:51:28 PM
US 1-9 Truck is now US 1-9 Bipass :bigass:

Same with US-19 Truck here in Pittsburgh.
They're correctly named as Truck. Google uses the BYP banner because...who knows. Probably easier than doing proper support for bannered routes. US routes only get a few (ALT, BUS, BYP), while state routes get none.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on November 29, 2014, 02:27:52 PM
Not exactly a highway, but a city street in Newark, NJ (and Irvington, NJ) that is supposed to be Sanford Avenue.
https://www.google.com/maps/place/Irvington,+NJ/@40.7330949,-74.2376248,17z/data=!4m2!3m1!1s0x89c3acc433f2e4d1:0x50cac0d62e5a555f

In fact Essex County made the same mistake (I wonder if these two are connected) on CR 603 in Irvington on the overhead street signs at the intersection there.  http://www.alpsroads.net/roads/nj/essex/ Scroll down to the lower part.
Title: Re: Incorrect highways marked on Google Maps
Post by: mrsman on November 30, 2014, 07:41:53 AM
I don't know if anyone else mentioned this before, but I hate when GM uses names that might be technically correct, but aren't really used regularly.

For example, I-10 is the Christopher Columbus Transcontinental Highway, and there is ONE (and only one) sign stating that in Santa Monica, CA, but nobody uses that.  It's known as  either I-10, or the Santa Monica Freeway.

Many places where US 30 is technically Lincoln Highway, but it might be know on the street signs as being "Main Street", yet Main Street is not shown on the map.  And when you are driving the road, only Main Street shows up, not Lincoln Highway.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on November 30, 2014, 07:55:46 AM
Quote from: dfwmapper on October 22, 2014, 01:54:24 AM
Quote from: rickmastfan67 on October 21, 2014, 07:37:17 PM
Quote from: NE2 on October 21, 2014, 12:51:28 PM
US 1-9 Truck is now US 1-9 Bipass :bigass:

Same with US-19 Truck here in Pittsburgh.
They're correctly named as Truck. Google uses the BYP banner because...who knows. Probably easier than doing proper support for bannered routes. US routes only get a few (ALT, BUS, BYP), while state routes get none.
Not familiar with Pittsburgh, but seeing that given the two choices, US 1/9 Truck is clearly more of a business route than a bypass, there's nothing correct about that banner.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 01, 2014, 06:40:42 AM
Quote from: roadman65 on November 29, 2014, 02:27:52 PM
Not exactly a highway, but a city street in Newark, NJ (and Irvington, NJ) that is supposed to be Sanford Avenue.
https://www.google.com/maps/place/Irvington,+NJ/@40.7330949,-74.2376248,17z/data=!4m2!3m1!1s0x89c3acc433f2e4d1:0x50cac0d62e5a555f
Fixed
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on December 03, 2014, 10:37:15 PM
I know that the extension of PA Turnpike 576 is underway, but I didn't think it was open..... :banghead:

http://goo.gl/maps/wGtKt
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 04, 2014, 10:53:48 AM
There's apparently a bug in Maps causing roads that are marked as Planned/Started to be visible.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 04, 2014, 11:09:50 AM
Quote from: dfwmapper on December 04, 2014, 10:53:48 AM
There's apparently a bug in Maps causing roads that are marked as Planned/Started to be visible.
But only some? http://maps.google.com/maps?ll=34.963552,-89.640723&spn=0.006269,0.012392&t=m&z=17
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 04, 2014, 11:12:15 AM
It's different in Map vs. Satellite view as well.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on December 04, 2014, 12:01:05 PM
Quote from: mrsman on November 30, 2014, 07:41:53 AM
I don't know if anyone else mentioned this before, but I hate when GM uses names that might be technically correct, but aren't really used regularly.

For example, I-10 is the Christopher Columbus Transcontinental Highway, and there is ONE (and only one) sign stating that in Santa Monica, CA, but nobody uses that.  It's known as  either I-10, or the Santa Monica Freeway.

Many places where US 30 is technically Lincoln Highway, but it might be know on the street signs as being "Main Street", yet Main Street is not shown on the map.  And when you are driving the road, only Main Street shows up, not Lincoln Highway.
At some point, GM showed US 30 in Oregon as the Lincoln Highway.
Not quite, Goog.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 04, 2014, 12:04:28 PM
Quote from: Bickendan on December 04, 2014, 12:01:05 PM
At some point, GM showed US 30 in Oregon as Quebec Route 366.
Not quite, Goog.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 04, 2014, 12:15:01 PM
Good help is hard to find. It's especially hard when your pool of talent is more suited to answering phones for AOL.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on December 04, 2014, 01:13:49 PM
Quote from: NE2 on December 04, 2014, 12:04:28 PM
Quote from: Bickendan on December 04, 2014, 12:01:05 PM
At some point, GM showed US 30 in Oregon as Quebec Route 366.
Not quite, Goog.
I remember that! :lol:
Title: Re: Incorrect highways marked on Google Maps
Post by: mrsman on December 05, 2014, 10:12:17 AM
Quote from: Kacie Jane on November 30, 2014, 07:55:46 AM
Quote from: dfwmapper on October 22, 2014, 01:54:24 AM
Quote from: rickmastfan67 on October 21, 2014, 07:37:17 PM
Quote from: NE2 on October 21, 2014, 12:51:28 PM
US 1-9 Truck is now US 1-9 Bipass :bigass:

Same with US-19 Truck here in Pittsburgh.
They're correctly named as Truck. Google uses the BYP banner because...who knows. Probably easier than doing proper support for bannered routes. US routes only get a few (ALT, BUS, BYP), while state routes get none.
Not familiar with Pittsburgh, but seeing that given the two choices, US 1/9 Truck is clearly more of a business route than a bypass, there's nothing correct about that banner.

US 1/9 Truck is a business routing, but truck makes more sense because the regular 1/9 prohibits certain heavy trucks on the Pulaski Skyway.  Truck 1/9 provides a truck friendly toll free route between Newark and the Holland Tunnel.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on December 05, 2014, 10:30:05 AM
Quote from: NE2 on December 04, 2014, 12:04:28 PM
Quote from: Bickendan on December 04, 2014, 12:01:05 PM
At some point, GM showed US 30 in Oregon as Quebec Route 366.
Not quite, Goog.

[Empty post]

Not only US 30 in OR, but the entire lenght of US 30 was marked as Quebec Route 366.

Or all those 'US [Insert number here] in [Insert state here]'.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on December 05, 2014, 10:35:36 AM
Quote from: CNGL-Leudimin on December 05, 2014, 10:30:05 AM
Not only US 30 in OR, but the entire lenght of US 30 was marked as Quebec Route 366.

Is it bad that I just can't take that particular route number seriously, no matter where it is?

Quote from: mrsman on December 05, 2014, 10:12:17 AM
US 1/9 Truck is a business routing, but truck makes more sense because the regular 1/9 prohibits certain heavy trucks on the Pulaski Skyway.  Truck 1/9 provides a truck friendly toll free route between Newark and the Holland Tunnel.

Actually, I don't even think it's marked as 1/9 in the first place - all I see are US 9 shields on the TRUCK 1/9 section.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on December 05, 2014, 11:16:12 AM
Quote from: mrsman on December 05, 2014, 10:12:17 AM
Quote from: Kacie Jane on November 30, 2014, 07:55:46 AM
Quote from: dfwmapper on October 22, 2014, 01:54:24 AM
Quote from: rickmastfan67 on October 21, 2014, 07:37:17 PM
Quote from: NE2 on October 21, 2014, 12:51:28 PM
US 1-9 Truck is now US 1-9 Bipass :bigass:

Same with US-19 Truck here in Pittsburgh.
They're correctly named as Truck. Google uses the BYP banner because...who knows. Probably easier than doing proper support for bannered routes. US routes only get a few (ALT, BUS, BYP), while state routes get none.
Not familiar with Pittsburgh, but seeing that given the two choices, US 1/9 Truck is clearly more of a business route than a bypass, there's nothing correct about that banner.

US 1/9 Truck is a business routing, but truck makes more sense because the regular 1/9 prohibits certain heavy trucks on the Pulaski Skyway.  Truck 1/9 provides a truck friendly toll free route between Newark and the Holland Tunnel.

I didn't mean that it should be signed as Business in real life.  Just that if Google is going to insist on a choice between only Business or Bypass, Business would have been clearly better in this case, so the BYP banner is especially wrong.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 05, 2014, 11:39:40 AM
The problem is that too many states sign TRUCK along the best through route when they should be using BYPASS or no banner on the bypass and BUSINESS on the in-town route. The Goog using BYP as the banner for routes signed as TRUCK conveys the correct idea most of the time, just not in this one oddball case where it's a truck route not because it's the best route, but because of restrictions on what would otherwise be the best route.
Title: Re: Incorrect highways marked on Google Maps
Post by: mrsman on December 07, 2014, 07:21:52 AM
Quote from: dfwmapper on December 05, 2014, 11:39:40 AM
The problem is that too many states sign TRUCK along the best through route when they should be using BYPASS or no banner on the bypass and BUSINESS on the in-town route. The Goog using BYP as the banner for routes signed as TRUCK conveys the correct idea most of the time, just not in this one oddball case where it's a truck route not because it's the best route, but because of restrictions on what would otherwise be the best route.

And to some degree, I'm willing to give a little benefit of the doubt to Google because TRUCK 1/9 is unusual in this regard.  Only locals would know that TRUCK 1/9 is not a conventional bypass.  Plus, there may not be an indication for TRUCK routes in their system, so they used Bypass instead.  And right now, while there are closures to the Pulaski Skyway in the northbound direction, the term bypass actually makes perfect sense.

And in my opinion, I'd prefer signing the through route without any banners at all, then having the through route known as a bypass.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 08, 2014, 03:06:31 PM
US 281 through Falfurrias isn't toll, is it?
Title: Re: Incorrect highways marked on Google Maps
Post by: Grzrd on December 08, 2014, 03:17:01 PM
Quote from: NE2 on December 08, 2014, 03:06:31 PM
US 281 through Falfurrias isn't toll, is it?

I have March, 2014 email correspondence from TxDOT stating that it would not be tolled:

https://www.aaroads.com/forum/index.php?topic=3624.msg297433;topicseen#msg297433

Previously, a 2011 Alliance for I-69 Texas article (linked in above-linked post) had reported that it would be tolled.

IIRC Oscar drove it right after it opened.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 09, 2014, 05:07:22 PM
Holy shit. Some idiot (or do they have a program automatically running through the exits?) interpreted this as exit 15:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FHfvh8bL.png&hash=9a283ef3ea37a3d5cef9b5642f35f84ff96da655) (http://maps.google.com/maps?ll=40.177857,-74.906974&spn=0.011689,0.024784&t=m&z=16&layer=c&cbll=40.177964,-74.906865&panoid=wVo8rii-jAwuLLTnvKJ2MQ&cbp=12,251.8,,0,7.35)
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on December 09, 2014, 05:13:55 PM
You'd think that whoever (or whatever) made that mistake would've noticed the lack of exit numbers on that stretch of US 1 anyway.
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on December 10, 2014, 04:29:48 PM
I do believe Google has a rather aggressive strategy of algorithmically extracting map data from Street View imagery.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on December 11, 2014, 02:52:35 AM
Some idiot made sure the Google path didn't follow the actual road on satellite.
http://goo.gl/jc4co0 (http://goo.gl/jc4co0)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 11, 2014, 12:53:33 PM
I've seen it a few times, though nothing compares to how far off the map and satellite data is in China.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on December 11, 2014, 02:31:08 PM
Apparently, Interstate 4 is now in Alaska.

http://goo.gl/maps/J2ePO

Yes, I know it's supposed to be Interstate A4, and it doesn't seem to be signed, but it should be marked on Maps as such.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on December 11, 2014, 02:37:06 PM
Quote from: SignGeek101 on December 11, 2014, 02:31:08 PM
Apparently, Interstate 4 is now in Alaska.

http://goo.gl/maps/J2ePO

Yes, I know it's supposed to be Interstate A4, and it doesn't seem to be signed, but it should be marked on Maps as such.

Still better than former I-6 in Maine (now ME 6).
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 11, 2014, 04:26:56 PM
Quote from: SignGeek101 on December 11, 2014, 02:31:08 PM
Yes, I know it's supposed to be Interstate A4, and it doesn't seem to be signed, but it should be marked on Maps as such.
No, it shouldn't be marked at all. It helps no one.
Title: Re: Incorrect highways marked on Google Maps
Post by: sbeaver44 on December 11, 2014, 05:40:15 PM
Quote from: dfwmapper on December 04, 2014, 10:53:48 AM
There's apparently a bug in Maps causing roads that are marked as Planned/Started to be visible.

Yeah, I saw this with I-11 today and was like...did I miss something?
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on December 11, 2014, 06:17:26 PM
Quote from: NE2 on December 11, 2014, 04:26:56 PM
Quote from: SignGeek101 on December 11, 2014, 02:31:08 PM
Yes, I know it's supposed to be Interstate A4, and it doesn't seem to be signed, but it should be marked on Maps as such.
No, it shouldn't be marked at all. It helps no one.

As if what GMaps marked by mistake don't help anyhow for any route at all.
Title: Re: Incorrect highways marked on Google Maps
Post by: roadfro on December 16, 2014, 04:45:45 PM
Quote from: sbeaver44 on December 11, 2014, 05:40:15 PM
Quote from: dfwmapper on December 04, 2014, 10:53:48 AM
There's apparently a bug in Maps causing roads that are marked as Planned/Started to be visible.

Yeah, I saw this with I-11 today and was like...did I miss something?

Yeah, I saw this recently with I-11 south of Boulder City, NV. Not marked "future" or anything... I was thinking, "they haven't even put phase 1 out to bid yet".
Title: Re: Incorrect highways marked on Google Maps
Post by: adventurernumber1 on December 16, 2014, 06:13:19 PM
Earlier today I saw this on Google Maps looking at Alaska:
:rofl:

(https://farm8.staticflickr.com/7486/15853016457_23bd2a2a17.jpg)
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on December 16, 2014, 06:26:09 PM
Not digging back to see if this has been mentioned already, but I-238 gains an orphaned sibling: I-134.

At least this one's on the correct side of I-40...
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 16, 2014, 06:28:32 PM
Quote from: Bickendan on December 16, 2014, 06:26:09 PM
Not digging back to see if this has been mentioned already, but I-238 gains an orphaned sibling: I-134.

At least this one's on the correct side of I-40...
Where?
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on December 16, 2014, 06:42:09 PM
The Ventura Freeway.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 16, 2014, 06:54:23 PM
Quote from: Bickendan on December 16, 2014, 06:42:09 PM
The Ventura Freeway.
:pan: not some newbie who screwed that up either. Some of the decisions those people make just baffle me. Hopefully the fix will be approved soon.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 16, 2014, 10:31:16 PM
lolwut (http://maps.google.com/maps?ll=34.762275,-100.138321&spn=0.050557,0.099134&t=m&z=14)
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 16, 2014, 11:05:28 PM
Quote from: dfwmapper on December 16, 2014, 06:54:23 PM
Quote from: Bickendan on December 16, 2014, 06:42:09 PM
The Ventura Freeway.
:pan: not some newbie who screwed that up either. Some of the decisions those people make just baffle me. Hopefully the fix will be approved soon.
This is fixed, BTW. I can't fix I-238, you'll have to get CalTrans and the FHWA to do that.
Quote from: NE2 on December 16, 2014, 10:31:16 PM
lolwut (http://maps.google.com/maps?ll=34.762275,-100.138321&spn=0.050557,0.099134&t=m&z=14)
County Road SC. Someone should spam up the map with the 49 other state abbreviations and see what happens.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on December 16, 2014, 11:30:37 PM
http://goo.gl/maps/HXKIo

Minor, but should be US Route 3 not state route 3
Title: Re: Incorrect highways marked on Google Maps
Post by: jakeroot on December 20, 2014, 01:54:29 AM
^^ I know in Washington, for example, US 2 is considered State Route 2 (http://apps.leg.wa.gov/rcw/default.aspx?cite=47.17.005), Interstate 5 is State Route 5 (http://apps.leg.wa.gov/rcw/default.aspx?cite=47.17.020), Interstate 90 is State Route 90 (http://app.leg.wa.gov/rcw/default.aspx?cite=47.17.140), and so on. You can probably guess that we don't sign the same number for multiple types of roadways. I'm wondering if maybe New Hampshire does the same thing, and Google is just using overly specific legal speak on their maps?
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 20, 2014, 02:02:04 AM
No, someone just fucked up. Happens all the time. It's fixed now internally, but this particular type of change takes a long time to show up on the map for some reason.
Title: Re: Incorrect highways marked on Google Maps
Post by: jakeroot on December 20, 2014, 02:10:57 AM
Quote from: dfwmapper on December 20, 2014, 02:02:04 AM
No, someone just fucked up. Happens all the time. It's fixed now internally, but this particular type of change takes a long time to show up on the map for some reason.

I've seen weeks between Google telling me they fixed something and it actually showing up. The smaller fixes (like missing roundabouts or slip lanes) are usually pretty quick, but I bet a big fuck-up like this could take quite a long time to update, since there are many, many more "sectors" to update (if that makes any sense).
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 20, 2014, 02:43:50 AM
The fix only required changing a single object, the U.S. 3 route. The name was added as an alternate to that, which is completely wrong as NH doesn't have a state route 3, and MA's state route 3 is a continuation from the southern terminus of US 3. Even if there was a co-signed state route (a la Georgia) it would need to be added as a completely separate route. Adding, removing, or modifying names on an existing route is just very slow for some reason. It would be faster to update the map by creating a completely new U.S. 3 route and adding it to all the appropriate road segments, but a change like that would never get approved.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on December 20, 2014, 10:47:45 AM
I saw these county road mistakes (http://goo.gl/maps/kbFSU) on Google Maps. The only counties in New Jersey that actually break away from the 5xx and 6xx/7xx route numbering system is Bergen County and Monmouth County.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 20, 2014, 03:36:50 PM
Quote from: Zeffy on December 20, 2014, 10:47:45 AM
I saw these county road mistakes (http://goo.gl/maps/kbFSU) on Google Maps. The only counties in New Jersey that actually break away from the 5xx and 6xx/7xx route numbering system is Bergen County and Monmouth County.
Removed 5 and 6, extended 629 down to 567, and added 667. Any I missed?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 20, 2014, 05:42:34 PM
Quote from: Zeffy on December 20, 2014, 10:47:45 AM
I saw these county road mistakes (http://goo.gl/maps/kbFSU) on Google Maps. The only counties in New Jersey that actually break away from the 5xx and 6xx/7xx route numbering system is Bergen County and Monmouth County.
And Ocean.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 20, 2014, 08:05:02 PM
http://www.fbctra.com/roads/grand-parkway-toll-road.html
QuoteMotorist[sic] may still use the Grand Parkway and avoid paying tolls by exiting prior to the tolled overpasses.
The Goog shows it all as a toll road.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on December 20, 2014, 08:12:47 PM
Quote from: NE2 on December 20, 2014, 08:05:02 PM
http://www.fbctra.com/roads/grand-parkway-toll-road.html
QuoteMotorist[sic] may still use the Grand Parkway and avoid paying tolls by exiting prior to the tolled overpasses.
The Goog shows it all as a toll road.

It also shows the Thruway between I-88 and I-87 north as a toll road (I seem to remember that you pay $0.00 when doing that).
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on December 20, 2014, 08:20:08 PM
Quote from: 1 on December 20, 2014, 08:12:47 PM
It also shows the Thruway between I-88 and I-87 north as a toll road (I seem to remember that you pay $0.00 when doing that).

Yes, but if you pass through that stretch you still get charged for that mileage.
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on December 20, 2014, 08:44:18 PM
Quote from: empirestate on December 20, 2014, 08:20:08 PM
Quote from: 1 on December 20, 2014, 08:12:47 PM
It also shows the Thruway between I-88 and I-87 north as a toll road (I seem to remember that you pay $0.00 when doing that).

Yes, but if you pass through that stretch you still get charged for that mileage.

Agree. Not an error. Only free if you're going between I-88 and Exit 24 or either I-890 exit. IIRC, this was part of the deal when the freeway alternate to NY 7 was canceled.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 20, 2014, 09:12:17 PM
It is an error to show a toll on I-90 east of I-88. Think about it this way: if you tell the Goog to avoid tolls in going from Binghamton to Albany, you want it to route you along the Thruway.

If you pass over a segment marked toll, you pay a toll. So two of the four ramps at I-890 west should be marked as toll, since you have to pay to go between exit 24 and I-890, but if you stay on and exit at I-88 you don't have to pay.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on December 21, 2014, 07:37:10 PM
Quote from: NE2 on December 20, 2014, 09:12:17 PM
It is an error to show a toll on I-90 east of I-88. Think about it this way: if you tell the Goog to avoid tolls in going from Binghamton to Albany, you want it to route you along the Thruway.

If you pass over a segment marked toll, you pay a toll. So two of the four ramps at I-890 west should be marked as toll, since you have to pay to go between exit 24 and I-890, but if you stay on and exit at I-88 you don't have to pay.
If you get on at exit 26 and exit at exit 25 (basically taking the Thruway between both ends of I-890), you pay a toll, but your scheme would show that as free (no tolls between 26 and 25A either).  If you're passing through and want to pay no toll on that stretch, you'd have to exit at 24, U turn, exit again at 25A, U turn again, and then do the same thing one more time at 26.  Everyone else on that segment continues to pay the toll as if no deal existed there - traffic coming from the west doesn't pay the same toll at 24 as it does at 25A, for example, even if it would have used I-88 had it been built.
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on December 21, 2014, 11:11:03 PM
Quote from: vdeane on December 21, 2014, 07:37:10 PM
Quote from: NE2 on December 20, 2014, 09:12:17 PM
It is an error to show a toll on I-90 east of I-88. Think about it this way: if you tell the Goog to avoid tolls in going from Binghamton to Albany, you want it to route you along the Thruway.

If you pass over a segment marked toll, you pay a toll. So two of the four ramps at I-890 west should be marked as toll, since you have to pay to go between exit 24 and I-890, but if you stay on and exit at I-88 you don't have to pay.
If you get on at exit 26 and exit at exit 25 (basically taking the Thruway between both ends of I-890), you pay a toll, but your scheme would show that as free (no tolls between 26 and 25A either).
Nope. The mainline between the I-88 ramps would still be toll.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on December 24, 2014, 06:15:40 AM
http://goo.gl/maps/3Cnnd (http://goo.gl/maps/3Cnnd)
Stray I-15 shield in Nogales, AZ, should be a MX 15 shield, and should not be shown on the American side of the border.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on December 24, 2014, 07:19:41 AM
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F8PDEWzZ.jpg&hash=9e0396534dacdcbad804d8ce7ddcf6c549f48ec8)

In GE, a state highway that hasn't appeared in over 60 years appears here, but it's not in MapMaker so I don't know where the heck they're getting their data.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on December 24, 2014, 03:33:35 PM
I'm not sure if this has been mentioned, but CR 382 in Gulf County, FL (just north of Port St. Joe) is marked as SR 382.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 24, 2014, 06:10:38 PM
Quote from: freebrickproductions on December 24, 2014, 03:33:35 PM
I'm not sure if this has been mentioned, but CR 382 in Gulf County, FL (just north of Port St. Joe) is marked as SR 382.
Fixed.
Title: Re: Incorrect highways marked on Google Maps
Post by: lordsutch on December 25, 2014, 05:06:41 PM
Non-existent or long-dead GA 361 is marked on several roads around Macon (Hartley Bridge, Bass, Tucker, Fulton Mill).

GA 11 is marked on its old alignment (Houston Road) rather than its "new" one (Industrial Highway and Hawkinsville Road, multiplexed with GA 49 and US 41).
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on December 26, 2014, 07:37:26 PM
Quote from: lordsutch on December 25, 2014, 05:06:41 PM
Non-existent or long-dead GA 361 is marked on several roads around Macon (Hartley Bridge, Bass, Tucker, Fulton Mill).

See also nearby GA 148 east of Bolingbroke, which has been gone for about 50 years. Scrolling north a bit, you'll also find GA 221, which shuffled off this mortal coil back in the 1980s.
Title: Re: Incorrect highways marked on Google Maps
Post by: Ga293 on December 27, 2014, 07:09:47 AM
A few more dead Georgia SR's still with shields on Google:


A whole stew of errors here. (https://maps.google.com/maps?ll=34.912118,-85.227642&spn=0.128239,0.264187&t=h&z=13)
Title: Re: Incorrect highways marked on Google Maps
Post by: adventurernumber1 on January 15, 2015, 08:18:15 PM
This is US 19/US 129 just south of US 64/US 74 in NC. This road heads south to Blairsville, GA so this has to be wrong. I've also come upon this typo several times the past few months. Not the hugest error in town but I hope to try to help Google Maps be as accurate as possible  :sombrero:

(https://farm8.staticflickr.com/7479/16289597385_bd1db7a92e.jpg)

EDIT: Also, I just noticed this as well, in that same pic. It is literally right next to the GA line, but GA 11 doesn't extend into NC  :-P
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on January 19, 2015, 10:43:56 PM
Someone deleted a section of CA 1 in Marin County
http://goo.gl/maps/89QhY (http://goo.gl/maps/89QhY)
Title: Re: Incorrect highways marked on Google Maps
Post by: myosh_tino on January 19, 2015, 11:37:01 PM
Quote from: national highway 1 on January 19, 2015, 10:43:56 PM
Someone deleted a section of CA 1 in Marin County
http://goo.gl/maps/89QhY (http://goo.gl/maps/89QhY)

Actually, the big storms that hit California in December washed out portions of CA-1 between Muir Woods and Muir Beach which forced Caltrans to close that stretch of highway which is roughly what was deleted on Google Maps.  According to news reports, the road is going to remain closed until March at the earliest.

http://sanfrancisco.cbslocal.com/2014/12/11/highway-1-from-muir-beach-to-muir-woods-closed-due-to-road-collapse-marin-county-storm/
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 19, 2015, 11:42:42 PM
And if I'm planning a trip in June, I'm fucked. Thanks, Goog!
Title: Re: Incorrect highways marked on Google Maps
Post by: myosh_tino on January 20, 2015, 01:38:37 AM
Quote from: NE2 on January 19, 2015, 11:42:42 PM
And if I'm planning a trip in June, I'm fucked. Thanks, Goog!

Any recommendation on how Google Maps should handle temporary closures?
Title: Re: Incorrect highways marked on Google Maps
Post by: NE2 on January 20, 2015, 01:58:32 AM
Quote from: myosh_tino on January 20, 2015, 01:38:37 AM
Quote from: NE2 on January 19, 2015, 11:42:42 PM
And if I'm planning a trip in June, I'm fucked. Thanks, Goog!

Any recommendation on how Google Maps should handle temporary closures?

Same way they handle winter closures. Say 'this road might be closed'.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on March 19, 2015, 10:47:46 AM
In Spring City, TN, TN 68 is shown going down the wrong road.
It needs to be going along this road (https://maps.google.com/maps?q=35.68822,-84.867332&num=1&t=h&z=15) rather than through the  downtown.
Title: Re: Incorrect highways marked on Google Maps
Post by: slorydn1 on March 19, 2015, 12:34:10 PM
US-17 Business in New Bern NC is incorrectly shown to be signed all the way through town on MLK Jr Blvd, Neuse Blvd, Broad St, and then a right turn along East Front St across the bridge to the US-17/US-70 interchange at the Neuse River Bridge. It actually terminates at the interchange with the US-17/US-70 freeway just east of the mall on MLK Jr Blvd.

The portion east of this interchange along the alignment that I typed above used to be US-70 Business before the new US-17 freeway was opened west of New Bern a few years ago, I am not sure why NCDOT decided to drop it.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 19, 2015, 03:55:00 PM
Quote from: freebrickproductions on March 19, 2015, 10:47:46 AM
In Spring City, TN, TN 68 is shown going down the wrong road.
It needs to be going along this road (https://maps.google.com/maps?q=35.68822,-84.867332&num=1&t=h&z=15) rather than through the  downtown.
Quote from: slorydn1 on March 19, 2015, 12:34:10 PM
US-17 Business in New Bern NC is incorrectly shown to be signed all the way through town on MLK Jr Blvd, Neuse Blvd, Broad St, and then a right turn along East Front St across the bridge to the US-17/US-70 interchange at the Neuse River Bridge. It actually terminates at the interchange with the US-17/US-70 freeway just east of the mall on MLK Jr Blvd.

The portion east of this interchange along the alignment that I typed above used to be US-70 Business before the new US-17 freeway was opened west of New Bern a few years ago, I am not sure why NCDOT decided to drop it.
Both fixed, though it may take some time to update.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on March 21, 2015, 05:18:15 PM
CT 4 is marked as "CT-4" in the county route rectangle, when it's a state route.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 23, 2015, 12:44:28 AM
Fixed now.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on March 24, 2015, 10:11:59 PM
Somebody downgraded I-676 in Camden and Philadelphia to a non-freeway road. That's technically true, but only for certain parts of it. The entire road in Camden is a freeway, and the bridge should be one too.

https://www.google.com/maps/@39.9569859,-75.1319161,14z
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on March 24, 2015, 11:00:21 PM
Quote from: Zeffy on March 24, 2015, 10:11:59 PM
Somebody downgraded I-676 in Camden and Philadelphia to a non-freeway road. That's technically true, but only for certain parts of it. The entire road in Camden is a freeway, and the bridge should be one too.

https://www.google.com/maps/@39.9569859,-75.1319161,14z

Good luck in trying to get that fixed.  I-381 says hi. (http://goo.gl/maps/q0Cn9)
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 24, 2015, 11:09:18 PM
I'll see if I can get I-676 fixed.

The set of overgrown ramps that somehow got an Interstate designation is fine the way it is.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on March 24, 2015, 11:16:49 PM
Quote from: dfwmapper on March 24, 2015, 11:09:18 PM
The set of overgrown ramps that somehow got an Interstate designation is fine the way it is.

Not really sure why it couldn't just be VA 381 for the entirety...
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on March 24, 2015, 11:19:47 PM
Quote from: Zeffy on March 24, 2015, 11:16:49 PM
Quote from: dfwmapper on March 24, 2015, 11:09:18 PM
The set of overgrown ramps that somehow got an Interstate designation is fine the way it is.

Not really sure why it couldn't just be VA 381 for the entirety...

Agree. It's worse than I-790 and it might just be below I-587. At least the latter doesn't consist of an interchange and its ramps.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 25, 2015, 02:12:36 AM
I-676 is fixed, should be updated on the map within a couple hours.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 25, 2015, 07:46:47 PM
I-81 on Wellesley Island is also marked as not a freeway.  I'm guessing that Google can't conceive of the fact that ON 137 on Hill Island is a non-freeway but I-81 on Wellesley Island is a freeway, since no matter what they classify it at a given time, they're both always classified the same.  Always.  They probably don't like the fact that both spans of the Thousand Islands Bridge are two lanes undivided as well.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 25, 2015, 08:11:23 PM
It's the two lane undivided parts that do it in. I've tried to get other super 2's like the eastern part of the Mountain Parkway in Kentucky and Loop 49 around Tyler, TX, marked as freeways, but they almost always get denied, or if they do get approved, someone comes back later and undoes the change.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on March 25, 2015, 08:35:11 PM
They didn't seem to be an issue for the first year of the current map style when both were marked as freeways.  At the very least they could mark the stuff that is actually ON Wellesley Island as a freeway.  As it is, the freeway color in Google Maps is completely useless (especially since it's used in many countries on roads that aren't even limited access; if my apartment was in Africa, the parking lot would be colored freeway orange on Google Maps, I'm sure of it).
Title: Re: Incorrect highways marked on Google Maps
Post by: Thing 342 on March 26, 2015, 08:36:08 AM
VA-199 is marked as a freeway for its entire length, as opposed to just the sections between 64 and SR-621 and VA-5 and I-64.
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on March 26, 2015, 12:15:09 PM
Mapquest this time, the shot below was used by the Star-Ledger to report on a pedestrian death in Toms River, NJ:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fmedia.nj.com%2Focean_impact%2Fphoto%2Ftoms-river-fatal-crash-locator-8d20b6a98fbedc95.png&hash=05a72532e6244872a75066deb948d7b081e0b24c)
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on March 26, 2015, 12:27:57 PM
I sincerely hope that no one actually thought CR 549 was an Interstate.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on March 26, 2015, 12:30:31 PM
Quote from: Mr. Matté on March 26, 2015, 12:15:09 PM
Mapquest this time, the shot below was used by the Star-Ledger to report on a pedestrian death in Toms River, NJ:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fmedia.nj.com%2Focean_impact%2Fphoto%2Ftoms-river-fatal-crash-locator-8d20b6a98fbedc95.png&hash=05a72532e6244872a75066deb948d7b081e0b24c)
Can't say I've seen many Spur Interstate outside of Baltimore...

Just checked this one on OSM/MQ. MQ tiles show square marker Spur 549 and OSM tiles show (549 Spur).

MQ.com is showing the I-shield, so something's causing it to read the Spur tag as an Interstate; there was a Spur I-524 in the vicinity.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 26, 2015, 06:36:14 PM
Quote from: Thing 342 on March 26, 2015, 08:36:08 AM
VA-199 is marked as a freeway for its entire length, as opposed to just the sections between 64 and SR-621 and VA-5 and I-64.
Yeah that's wrong. Looks like it would make a good expressway though, see what I can do about that.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bruce on March 30, 2015, 08:43:51 PM
U.S. Route 99 is back, at least from Everett to Blaine and in Tacoma.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Ft7IJpjn.png&hash=faf385c9f8212039798a2b7b9034e8efa03a2d0c)
Title: Re: Incorrect highways marked on Google Maps
Post by: jakeroot on March 30, 2015, 08:55:12 PM
Quote from: Bruce on March 30, 2015, 08:43:51 PM
U.S. Route 99 is back, at least from Everett to Blaine and in Tacoma.

Does the routing match up with the original alignment (where the freeway didn't replace the original road)? Interested because I don't think 99 ever followed South Tacoma Way.

EDIT: Some of the addresses even show up as "xxxx U.S. 99". :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: Bruce on March 30, 2015, 09:02:43 PM
Quote from: jakeroot on March 30, 2015, 08:55:12 PM
Quote from: Bruce on March 30, 2015, 08:43:51 PM
U.S. Route 99 is back, at least from Everett to Blaine and in Tacoma.

Does the routing match up with the original alignment (where the freeway didn't replace the original road)? Interested because I don't think 99 ever followed South Tacoma Way.

EDIT: Some of the addresses even show up as "xxxx U.S. 99". :-D

Not sure about Tacoma, but it generally follows the last non-expressway sections of U.S. Route 99. The real oddity is on the Pioneer Highway between Arlington and Stanwood, which US 99 was moved from in the 1930s, though it was a state highway until 1991.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on March 31, 2015, 12:00:21 AM
Quote from: jakeroot on March 30, 2015, 08:55:12 PM
Quote from: Bruce on March 30, 2015, 08:43:51 PM
U.S. Route 99 is back, at least from Everett to Blaine and in Tacoma.

Does the routing match up with the original alignment (where the freeway didn't replace the original road)? Interested because I don't think 99 ever followed South Tacoma Way.

EDIT: Some of the addresses even show up as "xxxx U.S. 99". :-D

99 absolutely followed South Tacoma Way. This is the first time I've seen Google put shields on it, but last year when I lived a few blocks off of it, out would occasionally tell me to turn right on "South Tacoma Way/U.S. 99" when using navigation on my phone.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bruce on March 31, 2015, 12:31:23 AM
The only section of highway in Washington state that has any right to call itself US 99 is the viaduct, solely because of the shield on Columbia Street's on ramp.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on March 31, 2015, 04:25:54 AM
Somehow "Historic U.S. 99" lost the Historic part and gained the flag that puts a shield on the map. :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on April 08, 2015, 04:31:13 PM
Not a highway, but click anywhere in the North Pacific Ocean (Only works on the new Maps)...
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on April 08, 2015, 04:34:00 PM
Quote from: CNGL-Leudimin on April 08, 2015, 04:31:13 PM
Not a highway, but click anywhere in the North Pacific Ocean (Only works on the new Maps)...
...I can't even come up with a snarky remark about this :/
Title: Re: Incorrect highways marked on Google Maps
Post by: Big John on April 08, 2015, 05:03:25 PM
Quote from: CNGL-Leudimin on April 08, 2015, 04:31:13 PM
Not a highway, but click anywhere in the North Pacific Ocean (Only works on the new Maps)...
And most of the North Atlantic Ocean is listed as Ireland.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on April 08, 2015, 07:44:19 PM
US Route 96 is listed as TX 96...well, throughout its entire pointless existence (https://www.google.com/maps/@30.2881896,-94.1267035,11z).
Title: Re: Incorrect highways marked on Google Maps
Post by: DeaconG on April 09, 2015, 05:39:20 PM
Quote from: Big John on April 08, 2015, 05:03:25 PM
Quote from: CNGL-Leudimin on April 08, 2015, 04:31:13 PM
Not a highway, but click anywhere in the North Pacific Ocean (Only works on the new Maps)...
And most of the North Atlantic Ocean is listed as Ireland.

North Pacific too.

Who knew Ireland was located between Asia and North America as well?

Weird...
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on April 10, 2015, 01:20:52 AM
Quote from: formulanone on April 08, 2015, 07:44:19 PM
US Route 96 is listed as TX 96...well, throughout its entire pointless existence (https://www.google.com/maps/@30.2881896,-94.1267035,11z).
That's fixed now. No idea how that one got fucked up, whatever change was made was hidden.
Title: Re: Incorrect highways marked on Google Maps
Post by: Big John on April 10, 2015, 09:57:14 PM
IL 75 is incorrectly marked as rte 67 from I-39/90 to Wisconsin state line, becoming WI 67 there.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on April 11, 2015, 10:18:17 AM
Quote from: dfwmapper on April 10, 2015, 01:20:52 AM
Quote from: formulanone on April 08, 2015, 07:44:19 PM
US Route 96 is listed as TX 96...well, throughout its entire pointless existence (https://www.google.com/maps/@30.2881896,-94.1267035,11z).

That's fixed now. No idea how that one got fucked up, whatever change was made was hidden.

Yup, seems correct now - Buna and Center will be happy again.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on April 15, 2015, 11:37:09 PM
Should RI 146 be marked as a freeway north of the RI 99 interchange? It looks like it's more of an expressway, especially as how there are RIROs and traffic signals.
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on May 03, 2015, 02:43:57 PM
A1A, in its entirety, is currently showing up as FL 2.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on May 03, 2015, 09:33:30 PM
It actually has 6 names on the route that used to be Florida A1A: Nathan Lester Highway 1, Nathan Lester Highway 2, Nathan Lester Highway 3, Nathan Lester Highway 4, Nathan Lester Highway 5, and Nathan Lester Highway 6. I don't even know how that happens. Google recently changed the way their chimps make edits, so there's no way to even know which stupid motherfucker made that change.
Title: Re: Incorrect highways marked on Google Maps
Post by: Highway63 on May 04, 2015, 07:16:16 PM
Serious "WTF" with the Avenue of the Saints going on:

In Missouri, northbound (but not southbound) of US 61 between I-64 and MO 27 is marked as freeway (orange) instead of expressway.

The entirety of the four-lane Avenue of the Saints (US 218 then US 18) between IA 57/58 and US 65 is marked as freeway but only certain bypasses are freeway segments. The rest has at-grade intersections.

In Mount Pleasant, northbound US 218 between exits 42 and 45 is marked as freeway but nothing else.

-IA 27/58 is marked as freeway through Cedar Falls. There are stoplights at Greenhill Road and south (so the "Freeway" only applies to University Avenue to US 218, or starting at Greenhill Road itself northward)
-US 218 is marked as freeway between San Marnan Drive and downtown Waterloo. It is not.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on May 04, 2015, 07:30:14 PM
None of those are marked as freeway, they're all expressway. Both freeway and expressway render in the same orange color on Maps. When they were approved as expressways, the reviewers who approved them were lazy and didn't make the change for the opposite direction. Maybe they'll get fixed someday.
Title: Re: Incorrect highways marked on Google Maps
Post by: Highway63 on May 04, 2015, 07:38:24 PM
Really? Huh. It was my experience/thinking that only fully controlled access roads got the orange, and expressways stayed yellow. (And now I'm looking and the same thing has happened to US 151 in Wisconsin.)

It just looks and feels wrong to me to treat freeways and expressways the same, I guess.
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on May 04, 2015, 07:46:37 PM
Quote from: Jeff Morrison on May 04, 2015, 07:38:24 PM
Really? Huh. It was my experience/thinking that only fully controlled access roads got the orange, and expressways stayed yellow. (And now I'm looking and the same thing has happened to US 151 in Wisconsin.)

It just looks and feels wrong to me to treat freeways and expressways the same, I guess.

OpenStreetMap gives them different colors, although green also applies to very important 2-lane roads that effectively work as Interstates (such as US 11 north of I-781).
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on May 04, 2015, 07:58:25 PM
Originally, expressways were orange. Then, they made them the same yellow as regional/national highways. Now they're back to orange. There are a lot of dumb things about the way Maps currently renders. Arteries being in white when they used to be pale yellow and easy to distinguish from white local/terminal roads. Using the California spec US shield when the rest of the country doesn't. Expressways not getting their own color. Ramps sometimes rendering in pale orange and sometimes in white.
Title: Re: Incorrect highways marked on Google Maps
Post by: mrsman on May 05, 2015, 02:45:38 PM
If I were designing Google maps, I would have white and yellow for all at-grade roads.  Freeways would be red.  Freeways that are toll would be green.


What they do now simply doesn't work.  Yellow and orange are too close.  And I can barely tell when a road is toll, what is it darker black outlines along the road?
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on May 05, 2015, 02:59:59 PM
Quote from: mrsman on May 05, 2015, 02:45:38 PM
If I were designing Google maps, I would have white and yellow for all at-grade roads.  Freeways would be red.  Freeways that are toll would be green.


What they do now simply doesn't work.  Yellow and orange are too close.  And I can barely tell when a road is toll, what is it darker black outlines along the road?

"Expressways" have switched back and forth between freeway color and primary road color at least 3 times. One example is MA 2 between exits 14 [middle of nowhere] and 40 [I-495] (this segment is a full freeway except for exits 27-32). Other examples include undivided surface roads outside of the United States.

Toll roads have darker black outlines once you zoom in enough. For me, the scale must read "2000ft/500m" or less, but the scale changes depending on latitude.
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on May 05, 2015, 04:17:49 PM
Quote from: mrsman on May 05, 2015, 02:45:38 PM
If I were designing Google maps, I would have white and yellow for all at-grade roads.  Freeways would be red.  Freeways that are toll would be green.


What they do now simply doesn't work.  Yellow and orange are too close.  And I can barely tell when a road is toll, what is it darker black outlines along the road?

Thomas Bros had it the best.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.silverlake.org%2Fimages%2Fgif%2Fslmap.gif&hash=c012d4965751d8a5abe111414286ef2b0638976f)

My personal variation is to make at-grade highways green and arteries purple. For online maps, color-blind friendly options could be toggled with a button.
Title: Re: Incorrect highways marked on Google Maps
Post by: jakeroot on May 05, 2015, 04:18:13 PM
Quote from: mrsman on May 05, 2015, 02:45:38 PM
If I were designing Google maps, I would have white and yellow for all at-grade roads.  Freeways would be red.  Freeways that are toll would be green....What they do now simply doesn't work. Yellow and orange are too close.

Cartography is an art. You can't just throw down contrasting colors and call it good. I get your point (any sane person would) but there's more to it than just red/blue/green/yellow.

Right now, Google is doing quite a good job, IMO. They should make better use of the yellow color (I believe there are more arterial roads than what are presently shown) but they are on the right track. The only other color variation that I like is the UK's colors, which are blue freeways, green arterial roads, and orange secondary roads (and white tertiary roads).

As for toll roads, I don't think mapping them is too important, beyond text along the roadway (e.g. "M6 TOLL"). Then again, that's just my opinion.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on May 05, 2015, 04:40:30 PM
Quote from: jakeroot on May 05, 2015, 04:18:13 PM
Quote from: mrsman on May 05, 2015, 02:45:38 PM
If I were designing Google maps, I would have white and yellow for all at-grade roads.  Freeways would be red.  Freeways that are toll would be green....What they do now simply doesn't work. Yellow and orange are too close.

Cartography is an art. You can't just throw down contrasting colors and call it good. I get your point (any sane person would) but there's more to it than just red/blue/green/yellow.

Right now, Google is doing quite a good job, IMO. They should make better use of the yellow color (I believe there are more arterial roads than what are presently shown) but they are on the right track. The only other color variation that I like is the UK's colors, which are blue freeways, green arterial roads, and orange secondary roads (and white tertiary roads).

As for toll roads, I don't think mapping them is too important, beyond text along the roadway (e.g. "M6 TOLL"). Then again, that's just my opinion.

Google Mapmaker has yellow (normal Google Maps has orange, but not yellow) on many roads. In the United States, the current orange roads are generally reserved for expressways and US routes in some states (Massachusetts), and used on more roads in others (New York).

google.com/mapmaker (http://google.com/mapmaker)

(Note: Google Mapmaker is closer to Classic than it is to the new version, so you will be fine.)
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on May 05, 2015, 09:18:19 PM
Quote from: mrsman on May 05, 2015, 02:45:38 PM
If I were designing Google maps, I would have white and yellow for all at-grade roads.  Freeways would be red.  Freeways that are toll would be green.


What they do now simply doesn't work.  Yellow and orange are too close.  And I can barely tell when a road is toll, what is it darker black outlines along the road?
Sounds like MapWorks... they use red for freeways, green for toll freeways, pink for state/US routes, yellow/orange for country routes and other arterials, and white for local roads.  IMO they're the king of cartography.

Example: http://www.mapworksinc.com/product-p/796.htm
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on May 05, 2015, 11:22:12 PM
In general, online mapping services don't show what is/isn't a toll road. Mapquest is one of the very few that does. IMO, they give the most accurate directions and travel times, but that's another thing. Bing uses blue-green for toll roads, but nobody uses them (and I don't like how they treat surface roads as a single color with only a few exceptions).
Title: Re: Incorrect highways marked on Google Maps
Post by: empirestate on May 06, 2015, 12:17:45 AM
Quote from: vdeane on May 05, 2015, 09:18:19 PM
Sounds like MapWorks... they use red for freeways, green for toll freeways, pink for state/US routes, yellow/orange for country routes and other arterials, and white for local roads.  IMO they're the king of cartography.

Example: http://www.mapworksinc.com/product-p/796.htm

They've always been good, and I had a full range of their pre-digital offerings. Not the all-time best cartography firm out of Rochester–remember ActionMaps?–but certainly the top of the current game. They always managed to beat out Jimapco for visual style.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on May 17, 2015, 01:26:03 AM
I don't know how long this has been the case, but ON 407 should have a circle shield, and has a standard provincial highway shield. A nitpick, but incorrect nonetheless.

http://goo.gl/maps/8vC8s
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on May 17, 2015, 02:06:59 AM
Google doesn't attempt to match the design of state/provincial highway shields, other than some provinces getting white pentagons, some getting blue, and some random green ones in Quebec. As a primary highway, the pentagon is correct for 407, even if it doesn't happen to be operated by the province.
Title: Re: Incorrect highways marked on Google Maps
Post by: corco on May 17, 2015, 02:21:40 AM
If memory serves, 407 actually did have a circle shield for several years- evidently they changed it back. Agreed that it's not wrong to have it be a pentagon, but I think it was at one point a circle shield on Google Maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on June 08, 2015, 07:56:46 AM
Not an erroneous highway, but knowing where Google is from, I'm not surprised North Korea appears as 북한 (Bukhan) instead of 조선 (Joseon).
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on June 08, 2015, 03:29:09 PM
Not a highway, but for some reason, Flint Road/Corsbie Street in Decatur isn't marked with a line showing the street, even though it exists and is open (as of a couple weeks ago). This error has been around for at least a month, I think.
https://maps.google.com/maps/myplaces?ll=34.575373,-86.973039&spn=0.002814,0.004128&t=h&z=19
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on June 09, 2015, 01:29:42 AM
I saw IL-000 somewhere in Google Maps. It was one of those insanely high US highway number links.
Title: Re: Incorrect highways marked on Google Maps
Post by: Haeleus on June 12, 2015, 10:51:08 AM
Caught this by chance while checking out the Dalton Highway, looks like the oil pipeline counts as an interstate now :-P.
https://www.google.ca/maps/@65.7355593,-149.2949026,12z

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FHc8A3r0.png&hash=4562c01952f94cf1140dc30aec36d0bd867c0415)
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on June 12, 2015, 11:08:18 AM
Quote from: Haeleus on June 12, 2015, 10:51:08 AM
Caught this by chance while checking out the Dalton Highway, looks like the oil pipeline counts as an interstate now :-P.
https://www.google.ca/maps/@65.7355593,-149.2949026,12z

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FHc8A3r0.png&hash=4562c01952f94cf1140dc30aec36d0bd867c0415)

I got a little confused, but if you look in streetview, that interstate is indeed a pipeline and not a road.  :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: SSOWorld on June 13, 2015, 11:08:24 AM
Not highway #, but highway type
Baja California State Route - though both are nationally drawn in Mexico, they DO have different shield designs

https://www.google.com/maps/@32.3859251,-115.4285603,10z
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on June 13, 2015, 11:48:32 AM
https://www.google.com/maps/mms?ll=43.904579,-80.88389&spn=0.004553,0.010568&t=m&z=17

87 should be a county shield.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on June 13, 2015, 04:42:25 PM
Quote from: SSOWorld on June 13, 2015, 11:08:24 AM
Not highway #, but highway type
Baja California State Route - though both are nationally drawn in Mexico, they DO have different shield designs

https://www.google.com/maps/@32.3859251,-115.4285603,10z
Does any state highway in Mexico have the other shield design? Baja California 2 is flagged as a state route, while MX 2D is flagged as a federal route, so the data appears to be correct. Google may just not have an icon for the other shield design.
Title: Re: Incorrect highways marked on Google Maps
Post by: kurumi on June 26, 2015, 10:26:07 PM
Here's a 2012 bug thread (https://code.google.com/p/google-mapmaker/issues/detail?id=2695) discussing the "US <number> in <distant state>" bug.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on June 26, 2015, 11:03:20 PM
Quote from: kurumi on June 26, 2015, 10:26:07 PM
Here's a 2012 bug thread (https://code.google.com/p/google-mapmaker/issues/detail?id=2695) discussing the "US <number> in <distant state>" bug.

Man, that brings back all the fun laughing @ Google over that. :)
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on July 02, 2015, 01:02:33 PM
According to Google, US 3 turns into MA 3 in Burlington at I-95/MA 128. (The actual place where it switches is approximately ten miles south.)
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on July 07, 2015, 11:08:19 AM
Google maps thinks NY-198 is limited access, even at the light
https://www.google.ca/maps/@42.930473,-78.8730078,15z

The shortest freeway in the world! It also has driveways and dead-ends  :-D :-D :-D :-D
https://www.google.ca/maps/@32.5729358,-84.9096923,18z
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on July 19, 2015, 06:19:52 PM
Google says 1000 Islands Parkway bordering the St. Lawrence is Highway 2. It was Highway 2S at one time, but that was gone by 1970.

https://www.google.ca/maps/@44.3538172,-76.0559224,13z?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on July 19, 2015, 06:31:53 PM
Google doesn't know that Cline Avenue is being demolished currently and isn't currently being replaced. Hopefully it doesn't try to direct drivers into the closed road-  :no:

https://www.google.ca/maps/@41.6514452,-87.46643,16.14z

Google also thinks that I-290 after the Shit Circle Interchange is actually I-290.

https://www.google.ca/maps/@41.8757235,-87.6407927,17.45z

Google also thinks Keystone Avenue in Caramel, Indiana is limited access.

https://www.google.ca/maps/@39.9218653,-86.1116853,16.01z

And last but not least we have the US 31 freeway in Westfield, Indiana between E 181st Street and E 196th street being fully limited access.

https://www.google.ca/maps/@40.0616568,-86.1294482,15.14z
Title: Re: Incorrect highways marked on Google Maps
Post by: vtk on July 20, 2015, 11:20:42 AM
In Columbus, Google seems to think OH 3 follows Broad St between 3rd/4th and Cleveland Ave; in reality, it follows Spring/Long.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on July 20, 2015, 11:29:15 AM
Google Maps seems to think that the Humelsine Parkway is fully limited access and while parts are not all of it is.
https://www.google.ca/maps/@37.2585783,-76.7175679,14.92z
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on July 20, 2015, 12:31:08 PM
Quote from: iBallasticwolf2 on July 20, 2015, 11:29:15 AM
Google Maps seems to think that the Humelsine Parkway is fully limited access and while parts are not all of it is.
https://www.google.ca/maps/@37.2585783,-76.7175679,14.92z
Both expressways and freeways show up in orange currently. Humelsine Parkway, Keystone, US 31, and NY 198 all qualify as expressways and are marked as such.
Title: Re: Incorrect highways marked on Google Maps
Post by: US71 on July 20, 2015, 01:04:03 PM
I've seen incorrect highways on weather radar, such as I-71 and I-271 in Arkansas.
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on July 20, 2015, 03:18:32 PM
Oops Google, this is Penhar Drive! Not Penhar Street!

https://www.google.com/maps/place/Penhar+St,+Harrisburg,+PA+17111/@40.2497864,-76.801988,16z/data=!4m2!3m1!1s0x89c8bf6d554f68c1:0x6bde2ff64877d999

No google, if a road gets a center stripe, does not mean it is a divided highway!

https://www.google.com/maps/place/Penhar+St,+Harrisburg,+PA+17111/@40.2489009,-76.8057822,19z/data=!4m2!3m1!1s0x89c8bf6d554f68c1:0x6bde2ff64877d999

That isn't Paxton Street, it's an offramp!

https://www.google.com/maps/place/Penhar+St,+Harrisburg,+PA+17111/@40.2546683,-76.8251915,18z/data=!4m2!3m1!1s0x89c8bf6d554f68c1:0x6bde2ff64877d999


Despite the links looking the same, they are actually different. Trust me.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on July 20, 2015, 03:30:44 PM
Quote from: noelbotevera on July 20, 2015, 03:18:32 PM
Despite the links looking the same, they are actually different. Trust me.

The links don't look the same. I can easily see that the coordinates (approximately 40°N, 77°W) are different for each link.
Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on July 20, 2015, 05:41:56 PM
Quote from: noelbotevera on July 20, 2015, 03:18:32 PM
No google, if a road gets a center stripe, does not mean it is a divided highway!

https://www.google.com/maps/place/Penhar+St,+Harrisburg,+PA+17111/@40.2489009,-76.8057822,19z/data=!4m2!3m1!1s0x89c8bf6d554f68c1:0x6bde2ff64877d999
That's actually a Google policy.  I presume that's because it's illegal to turn left across the stripe in at least a few jurisdictions (including California).
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on July 20, 2015, 06:05:22 PM
It's actually against Google's policy, which indicates that divided roads should only be mapped as separate one-way roads when the division is for an extended distance. For something short like that, there's a separate 'Divider' attribute that can be set on the road that will prevent directions from telling people to turn left across it. But, several years back, Google hired a team of monkeys who went around and split instances like that, and it's all but impossible to get them fixed (and currently impossible to do anything, since Map Maker is disabled until sometime in August).
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on July 20, 2015, 06:06:52 PM
Quote from: dfwmapper on July 20, 2015, 06:05:22 PM(and currently impossible to do anything, since Map Maker is disabled until sometime in August).

I thought it was "temporarily" disabled forever. Is it actually coming back?
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on July 20, 2015, 06:13:19 PM
Yes, they announced a few days ago that it's coming back in early August, and also that they're planning to shift primary review duties to the community with only certain things needing review by them (no specifics provided on where the dividing line will be).
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on July 20, 2015, 06:37:34 PM
Quote from: dfwmapper on July 20, 2015, 06:13:19 PM
Yes, they announced a few days ago that it's coming back in early August, and also that they're planning to shift primary review duties to the community with only certain things needing review by them (no specifics provided on where the dividing line will be).

Maybe Google found out about Roadgeeks and want to rely on them now.  :bigass:
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on July 21, 2015, 11:42:26 AM
Another error from Google:

https://www.google.ca/maps/@44.6333575,-81.1311251,17z?hl=en

Hwy 70 was decommissioned in 1997. It no longer exists. Shouldn't be in a map that was made years later.
Title: Re: Incorrect highways marked on Google Maps
Post by: Highway63 on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on July 26, 2015, 03:00:13 AM
Quote from: Jeff Morrison on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.

Bet this is another one of those 'India Mods Strike Again'.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on July 27, 2015, 12:43:21 PM
A second Interstate 45?
https://www.google.ca/maps/@31.7657528,-106.4498422,18.14z
Apparently so!
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on July 27, 2015, 01:00:24 PM
Quote from: rickmastfan67 on July 26, 2015, 03:00:13 AM
Quote from: Jeff Morrison on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.

Bet this is another one of those 'India Mods Strike Again'.
Yep. Google disabled editing of rivers by mappers on January 29, and the change was made on January 30. In the default font Google uses, a lowercase l looks like an uppercase I, so if you're a dumbass from the wrong side of the world and don't know basic US geography and state names, you might fuck that up.
Quote from: iBallasticwolf2 on July 27, 2015, 12:43:21 PM
A second Interstate 45?
https://www.google.ca/maps/@31.7657528,-106.4498422,18.14z
Apparently so!
The Federal Highway 45 name was extended north over the bridge into the US. Mexico's Federal Highways have the same classification internally as Interstates, and the icon is automatic based on the classification+country. It's now on my list of stuff to fix once Map Maker reopens.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on July 27, 2015, 01:05:28 PM

Quote from: iBallasticwolf2 on July 27, 2015, 12:43:21 PM
A second Interstate 45?
https://www.google.ca/maps/@31.7657528,-106.4498422,18.14z
Apparently so!
The Federal Highway 45 name was extended north over the bridge into the US. Mexico's Federal Highways have the same classification internally as Interstates, and the icon is automatic based on the classification+country. It's now on my list of stuff to fix once Map Maker reopens.
[/quote]

That makes sense. It seems to even show a I-45 shield on the Mexico Side of the bridge.
https://www.google.ca/maps/@31.7640953,-106.451138,19.67z
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on July 27, 2015, 01:16:45 PM
It's not actually the physical location of the segment, it's the country in the address associated with the segment, which may not match the actual location, and is not pleasant to try and fix. The segment of northbound lanes immediately south of the border has a Texas address, and the segment of southbound lanes immediately north of the border has a Chihuahua address.
Title: Re: Incorrect highways marked on Google Maps
Post by: Pete from Boston on July 28, 2015, 07:35:57 PM
Not highways, but there's a systemic failure to map Martha's Vineyard roads properly.  Countless private dirt roads that are little more than driveways (many marked "no trespassing") are drawn equal to local public through streets.  Worst overall results I've had from using Google Maps in quite a while.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on July 28, 2015, 08:00:19 PM
Driveways get into a very gray area in the map rules. Driveways that serve 3 or more houses are explicitly permitted on the map, as are driveways that are useful in navigation if a destination is well back from the main road and directions get the location wrong (usually when the driveway curves or slants so the house isn't aligned to where the driveway meets the road). There is a public/private attribute that can be set to Private for roads inside gated communities or with posted "no trespassing" signs, and that changes the rendering so the road is gray instead of white. But, it's rarely set correctly for posted but ungated roads because of the difficulty in identifying the signs in street view. It's easy enough to fix specific ones (once MM is reopened), but it looks like street view in that area is pretty old so being able to systematically identify them without actually being there might be difficult.
Title: Re: Incorrect highways marked on Google Maps
Post by: formulanone on July 28, 2015, 08:04:57 PM
Quote from: Jeff Morrison on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.

We bought a wooden puzzle set for our children which included a map of the US. Iowa was also spelled "Lowa".

(https://farm1.staticflickr.com/487/20114131009_d4b3c42505_h.jpg) (https://flic.kr/p/wDqboe)
Mysterious America Puzzle (https://flic.kr/p/wDqboe) by formulanone (https://www.flickr.com/photos/formulanone/), on Flickr
Title: Incorrect highways marked on Google Maps
Post by: Pete from Boston on August 05, 2015, 08:31:26 PM
Quote from: formulanone on July 28, 2015, 08:04:57 PM
Quote from: Jeff Morrison on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.

We bought a wooden puzzle set for our children which included a map of the US. Iowa was also spelled "Lowa".

(https://farm1.staticflickr.com/487/20114131009_d4b3c42505_h.jpg) (https://flic.kr/p/wDqboe)
Mysterious America Puzzle (https://flic.kr/p/wDqboe) by formulanone (https://www.flickr.com/photos/formulanone/), on Flickr

The shapes of those states are making me queasy, never mind their approach to the four-color map problem.  We were not consulted up here as to whether we even wanted Connecticut or Rhode Island.

I am grateful, though, for them shortening my trip to New York.  I always did wish Boston was where Hartford is.

Also, what state is Maui part of?
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on August 05, 2015, 08:35:54 PM
Trenton is now where Newark is. Great. The state shape for New Jersey as a whole is fucking vomit-inducing too.
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on August 05, 2015, 08:40:53 PM
Quote from: Pete from Boston on August 05, 2015, 08:31:26 PM
Also, what state is Maui part of?

I believe it's a part of the state of "Hawaii Islands." Now back to shaking my head at that puzzle.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on August 05, 2015, 08:42:42 PM
Quote from: Pete from Boston on August 05, 2015, 08:31:26 PM
Quote from: formulanone on July 28, 2015, 08:04:57 PM
Quote from: Jeff Morrison on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.

We bought a wooden puzzle set for our children which included a map of the US. Iowa was also spelled "Lowa".

(https://farm1.staticflickr.com/487/20114131009_d4b3c42505_h.jpg) (https://flic.kr/p/wDqboe)
Mysterious America Puzzle (https://flic.kr/p/wDqboe) by formulanone (https://www.flickr.com/photos/formulanone/), on Flickr

The shapes of those states are making me queasy, never mind their approach to the four-color map problem.  We were not consulted up here as to whether we even wanted Connecticut or Rhode Island.

Also, what state is Maui part of?

I could have put up with this at first but when they spelt Cincinnati wrong (They spelled it Cincinanti) that was the last straw. Also Topeka is south of Kansas City now. Also the Maryland and Delaware borders are REALLY screwed up. They used that cow insert 5 times and the Ohio River is so straight it made Kentucky smaller. Also it seems Toas, NM is large enough to display on this map even though it is smaller than 10,000 people.
Title: Re: Incorrect highways marked on Google Maps
Post by: Big John on August 05, 2015, 08:54:17 PM
^^ Add Winsconsin

And the I in Iowa is in Sait Lake City\

And don't go to Indianpous or Dailas
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on August 05, 2015, 08:57:49 PM
Not mentioned yet:

1. Massachusetts touches Maine.
2. Idano. Does it mean "I don't know"?
3. Dailas.
4. Reno, Carson City, and Las Vegas are all capitals.
5. Minneapous. Indianapous is the same.
6. Harrisburg and Philadelphia are the same city.
7. New Hamshire, no P.
Title: Re: Incorrect highways marked on Google Maps
Post by: Pete from Boston on August 05, 2015, 09:28:43 PM
Quote from: 1 on August 05, 2015, 08:57:49 PM
4. Reno, Carsom City, and Las Vegas are all capitals.

FTFY
Title: Re: Incorrect highways marked on Google Maps
Post by: Bruce on August 05, 2015, 11:16:53 PM
Seattle seems to be tucked right under Mount Baker. Olympia has decided to move onto the Olympic Peninsula and into the Olympic Mountains.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on August 06, 2015, 05:04:15 AM
Quote from: CNGL-Leudimin on June 08, 2015, 07:56:46 AM
Not an erroneous highway, but knowing where Google is from, I'm not surprised North Korea appears as 북한 (Bukhan) instead of 조선 (Joseon).

I can't believe they have corrected this one, it now appears as 조선 민주주의 인민공화국 (Joseon Minjujueui Inmin Gonghwaguk, lit. DPR Korea).

Also, look what Google came up with when I searched 'Chinese Taipei' (i.e. Taiwan): https://www.google.es/maps/place/China+Taipei/@39.5685408,-104.902878,17z/data=!3m1!4b1!4m2!3m1!1s0x876c84382c3edfc1:0xa66ad458898ef3
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on August 06, 2015, 01:16:35 PM
Quote from: CNGL-Leudimin on August 06, 2015, 05:04:15 AM
Quote from: CNGL-Leudimin on June 08, 2015, 07:56:46 AM
Not an erroneous highway, but knowing where Google is from, I'm not surprised North Korea appears as 북한 (Bukhan) instead of 조선 (Joseon).

I can't believe they have corrected this one, it now appears as 조선 민주주의 인민공화국 (Joseon Minjujueui Inmin Gonghwaguk, lit. DPR Korea).

Also, look what Google came up with when I searched 'Chinese Taipei' (i.e. Taiwan): https://www.google.es/maps/place/China+Taipei/@39.5685408,-104.902878,17z/data=!3m1!4b1!4m2!3m1!1s0x876c84382c3edfc1:0xa66ad458898ef3
Well, time to go to Colorado. Clearly that's where Taiwan is, right!? (sarcasm)
Title: Re: Incorrect highways marked on Google Maps
Post by: Pete from Boston on August 07, 2015, 10:31:41 AM
Quote from: noelbotevera on August 06, 2015, 01:16:35 PM
Quote from: CNGL-Leudimin on August 06, 2015, 05:04:15 AM
Quote from: CNGL-Leudimin on June 08, 2015, 07:56:46 AM
Not an erroneous highway, but knowing where Google is from, I'm not surprised North Korea appears as 북한 (Bukhan) instead of 조선 (Joseon).

I can't believe they have corrected this one, it now appears as 조선 민주주의 인민공화국 (Joseon Minjujueui Inmin Gonghwaguk, lit. DPR Korea).

Also, look what Google came up with when I searched 'Chinese Taipei' (i.e. Taiwan): https://www.google.es/maps/place/China+Taipei/@39.5685408,-104.902878,17z/data=!3m1!4b1!4m2!3m1!1s0x876c84382c3edfc1:0xa66ad458898ef3
Well, time to go to Colorado. Clearly that's where Taiwan is, right!? (sarcasm)

In fairness, Chinese Taipei is not a geographic name, but rather a political compromise of nomenclature solely within the activities of the International Olympic Committee.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on August 07, 2015, 09:42:11 PM
Quote from: iBallasticwolf2 on August 05, 2015, 08:42:42 PM
Quote from: Pete from Boston on August 05, 2015, 08:31:26 PM
Quote from: formulanone on July 28, 2015, 08:04:57 PM
Quote from: Jeff Morrison on July 26, 2015, 12:44:26 AM
Not a highway error, but the Iowa River is marked as the Lowa River from Steamboat Rock to Albion.

We bought a wooden puzzle set for our children which included a map of the US. Iowa was also spelled "Lowa".

(https://farm1.staticflickr.com/487/20114131009_d4b3c42505_h.jpg) (https://flic.kr/p/wDqboe)
Mysterious America Puzzle (https://flic.kr/p/wDqboe) by formulanone (https://www.flickr.com/photos/formulanone/), on Flickr

The shapes of those states are making me queasy, never mind their approach to the four-color map problem.  We were not consulted up here as to whether we even wanted Connecticut or Rhode Island.

Also, what state is Maui part of?

I could have put up with this at first but when they spelt Cincinnati wrong (They spelled it Cincinanti) that was the last straw. Also Topeka is south of Kansas City now. Also the Maryland and Delaware borders are REALLY screwed up. They used that cow insert 5 times and the Ohio River is so straight it made Kentucky smaller. Also it seems Toas, NM is large enough to display on this map even though it is smaller than 10,000 people.
I'm pretty sure Alabama ain't supposed to look like that and that Tallahassee, FL is supposed to be a bit farther to the east.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on August 10, 2015, 10:17:47 AM
https://www.google.ca/maps/@43.9736002,-78.8954793,15z?hl=en

Hold on Google, this freeway isn't supposed to open until the end of the year (if not later).
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on August 10, 2015, 08:26:58 PM
Map Maker has partially reopened (Bangladesh, Brazil, Canada, India, Philippines and Ukraine only for now). Thousand Islands Parkway is now fixed, county road 78 has been fixed for a while, and the 407 freeway is pending.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on August 10, 2015, 08:40:14 PM
https://www.google.com/maps/@39.5518666,-76.09782,15.75z

This, I believe, should be MD 7, however, I can't actually confirm that, since all my maps I have don't have any insets for Havre De Grace (understandably, it's a pretty small town). Google says 7A, but this shield says otherwise. OSM also confirms that this should probably be MD 7.
Title: Re: Incorrect highways marked on Google Maps
Post by: Kacie Jane on August 11, 2015, 03:27:44 PM
https://en.m.wikipedia.org/wiki/Maryland_Route_7

7A is technically correct, but yes, any map that's not intended for internal MDSHA use should label it as 7.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on August 22, 2015, 03:13:53 PM
Google Maps shows three disconnected segments of Houston's Grand Parkway which in this case isn't open yet.
https://www.google.ca/maps/@30.0546446,-95.4827749,11.91z
Title: Re: Incorrect highways marked on Google Maps
Post by: Bruce on September 11, 2015, 06:22:48 PM
MT 3 is marked as a highway in one direction:

https://www.google.com/maps/place/45%C2%B046'33.1%22N+108%C2%B029'52.2%22W/@45.77587,-108.497837,17z/data=!3m1!4b1!4m2!3m1!1s0x0:0x0

I call it a "Vatican stripe (https://en.wikipedia.org/wiki/Flag_of_Vatican_City)".
Title: Re: Incorrect highways marked on Google Maps
Post by: Billy F 1988 on September 12, 2015, 03:07:09 AM
Wait, what?! Just the southbound lane of MT 3 is marked from 1st Ave S to the I-90 interchange at Exit 450?! That's just effed up. Both the northbound and southbound lanes should be marked.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on September 12, 2015, 06:16:55 PM
The selection tool in Map Maker only allows for selecting a single continuous path. If the road splits into separate one-way segments, those pieces have to be submitted as separate edits. If you submit one big edit for one direction of road (say, MT 3 from US 12 to I-90) and a bunch of smaller edits for the opposite-direction one way parts, Google's reviewers will often deny the smaller pieces, because they apparently don't notice that there's a big edit that the smaller ones go along with. So, the edits usually just get submitted as the one big one, then the reviewers do cleanup afterwards. Sometimes they don't do the cleanup part though, and this is what happens.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on September 12, 2015, 08:09:55 PM
Here's the Almond Street Freeway in Poplar Bluff, Missouri.
https://www.google.ca/maps/@36.754649,-90.3888583,19.98z


Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on September 12, 2015, 08:15:55 PM
Not an incorrect highway, but an incorrect waterway in South Jersey.  The Bass River is marked as Mullica River in Bass River Township.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on September 12, 2015, 08:25:04 PM
Quote from: iBallasticwolf2 on September 12, 2015, 08:09:55 PM
Here's the Almond Street Freeway in Poplar Bluff, Missouri.
https://www.google.ca/maps/@36.754649,-90.3888583,19.98z

That's got to be the shortest freeway I've ever seen. It's apparent speed limit of 65 mph (according to Google Mapmaker) means you could clinch it quickly :sombrero:

It's already been edited though and should be fixed soon.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on September 13, 2015, 04:27:55 PM
Apparently, Michigan's borders have changed.

https://www.google.ca/maps/place/Michigan,+USA/@45.8201084,-84.776133,6z/data=!4m2!3m1!1s0x4d4caa3dc7ca0411:0x97dd48597a62c9b3?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on September 13, 2015, 05:28:33 PM
Quote from: SignGeek101 on September 13, 2015, 04:27:55 PM
Apparently, Michigan's borders have changed.

https://www.google.ca/maps/place/Michigan,+USA/@45.8201084,-84.776133,6z/data=!4m2!3m1!1s0x4d4caa3dc7ca0411:0x97dd48597a62c9b3?hl=en
It reminds me of this.

https://www.thrillist.com/travel/nation/can-you-draw-all-50-us-states

It seems Google failed to draw Michigan and now Indiana and Ohio can now annex a ton of land. Bye Lansing, Grand Rapids, etc.
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on September 13, 2015, 06:17:25 PM
Quote from: SignGeek101 on September 13, 2015, 04:27:55 PM
Apparently, Michigan's borders have changed.

https://www.google.ca/maps/place/Michigan,+USA/@45.8201084,-84.776133,6z/data=!4m2!3m1!1s0x4d4caa3dc7ca0411:0x97dd48597a62c9b3?hl=en

And Indiana and Illinois and Wisconsin and Maryland and Georgia and Alabama and Mississippi and...
Title: Re: Incorrect highways marked on Google Maps
Post by: Mr. Matté on September 13, 2015, 06:18:49 PM
Quote from: noelbotevera on September 13, 2015, 05:28:33 PM
Quote from: SignGeek101 on September 13, 2015, 04:27:55 PM
Apparently, Michigan's borders have changed.

https://www.google.ca/maps/place/Michigan,+USA/@45.8201084,-84.776133,6z/data=!4m2!3m1!1s0x4d4caa3dc7ca0411:0x97dd48597a62c9b3?hl=en
It reminds me of this.

https://www.thrillist.com/travel/nation/can-you-draw-all-50-us-states

It seems Google failed to draw Michigan and now Indiana and Ohio can now annex a ton of land. Bye Lansing, Grand Rapids, etc.

At least SNL's David Paterson got most of his wish and now New Jersey is just a rhombus in Salem and Cumberland counties. (https://www.google.com/maps/place/New+Jersey/@39.5139291,-75.1544272,11z/data=!3m1!4b1!4m2!3m1!1s0x89c0fb959e00409f:0x2cd27b07f83f6d8d)
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on September 13, 2015, 06:24:23 PM
Quote from: Eth on September 13, 2015, 06:17:25 PM
Quote from: SignGeek101 on September 13, 2015, 04:27:55 PM
Apparently, Michigan's borders have changed.

https://www.google.ca/maps/place/Michigan,+USA/@45.8201084,-84.776133,6z/data=!4m2!3m1!1s0x4d4caa3dc7ca0411:0x97dd48597a62c9b3?hl=en

And Indiana and Illinois and Wisconsin and Maryland and Georgia and Alabama and Mississippi and...

Didn't notice that those ones were messed up as well. Some of the Canadian provinces have been messed up as well. Wonder what is wrong with Google.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on September 13, 2015, 06:54:06 PM
Quote from: Mr. Matté on September 13, 2015, 06:18:49 PM
At least SNL's David Paterson got most of his wish and now New Jersey is just a rhombus in Salem and Cumberland counties. (https://www.google.com/maps/place/New+Jersey/@39.5139291,-75.1544272,11z/data=!3m1!4b1!4m2!3m1!1s0x89c0fb959e00409f:0x2cd27b07f83f6d8d)

Considering most of New York (including New York City) was annexed by an unknown entity, as well as Connecticut, Massachusetts, Maryland, Virginia, North Carolina, and South Carolina, while Pennsylvania remains intact, I can only theorize that those bastards are behind all this.
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on September 13, 2015, 07:46:41 PM
Quote from: Zeffy on September 13, 2015, 06:54:06 PM
Quote from: Mr. Matté on September 13, 2015, 06:18:49 PM
At least SNL's David Paterson got most of his wish and now New Jersey is just a rhombus in Salem and Cumberland counties. (https://www.google.com/maps/place/New+Jersey/@39.5139291,-75.1544272,11z/data=!3m1!4b1!4m2!3m1!1s0x89c0fb959e00409f:0x2cd27b07f83f6d8d)

Considering most of New York (including New York City) was annexed by an unknown entity, as well as Connecticut, Massachusetts, Maryland, Virginia, North Carolina, and South Carolina, while Pennsylvania remains intact, I can only theorize that those bastards are behind all this.
https://www.google.com/maps/place/Illinois/@39.7240067,-88.519017,7.51z/data=!4m2!3m1!1s0x880b2d386f6e2619:0x7f15825064115956
https://www.google.com/maps/place/Iowa/@41.5689288,-92.4778205,9z/data=!3m1!4b1!4m2!3m1!1s0x87ee5e6ff1f86019:0xc6ef634a57c759d9
https://www.google.com/maps/place/Michigan/@45.281572,-86.4900002,7z/data=!3m1!4b1!4m2!3m1!1s0x4d4caa3dc7ca0411:0x97dd48597a62c9b3
https://www.google.com/maps/place/Wisconsin/@44.8054455,-89.8267049,7z/data=!3m1!4b1!4m2!3m1!1s0x52a8f40f9384e3af:0xf2d5d5b8f88649d6
https://www.google.com/maps/place/Nebraska/@41.8254517,-99.5641229,8z/data=!3m1!4b1!4m2!3m1!1s0x87938dc8b50cfced:0xa127900c0ff30ac4
https://www.google.com/maps/place/Georgia/@32.8303069,-83.3887494,8z/data=!3m1!4b1!4m2!3m1!1s0x88f136c51d5f8157:0x6684bc10ec4f10e7
https://www.google.com/maps/place/Alabama/@33.1841361,-86.6165368,8z/data=!3m1!4b1!4m2!3m1!1s0x88867f341f4bfe75:0x5e55343553c8cce9
https://www.google.com/maps/place/Mississippi/@33.2425005,-89.2338725,8z/data=!3m1!4b1!4m2!3m1!1s0x862832e4e44ad419:0x620d177fe9dca6da
https://www.google.com/maps/place/Louisiana/@30.7820504,-91.7407524,8z/data=!3m1!4b1!4m2!3m1!1s0x8620a454b2118265:0xc955f73281e54703
https://www.google.com/maps/place/Arizona/@35.1100543,-112.0464871,8z/data=!3m1!4b1!4m2!3m1!1s0x872b08ebcb4c186b:0x423927b17fc1cd71
https://www.google.com/maps/place/California/@38.9785987,-122.206726,7z/data=!3m1!4b1!4m2!3m1!1s0x808fb9fe5f285e3d:0x8b5109a227086f55
https://www.google.com/maps/place/Idaho/@44.7450016,-114.1675485,7z/data=!3m1!4b1!4m2!3m1!1s0x5358ffa885e499e9:0xd06b300515f78758
https://www.google.com/maps/place/Oklahoma/@35.4513023,-95.9103149,8z/data=!3m1!4b1!4m2!3m1!1s0x87ac3911b1ac4f9d:0x5d1ccf33400aea48
https://www.google.com/maps/place/Florida/@26.527387,-83.9892645,6z/data=!3m1!4b1!4m2!3m1!1s0x88c1766591562abf:0xf72e13d35bc74ed0
I think that is all that is off.
I've also noticed some cities and states lost their vectors and are only displayed as place markers.
https://www.google.com/maps/place/West+Virginia/@38.2591803,-80.8925607,8.14z/data=!4m2!3m1!1s0x884a54a5d4cb0945:0xbb00c768decd3a43
https://www.google.com/maps/place/New+York,+NY/@40.6870755,-73.9789944,11z/data=!4m2!3m1!1s0x89c24fa5d33f083b:0xc80b8f06e177fe62
https://www.google.com/maps/place/Cincinnati,+OH/@39.13634,-84.5404014,12z/data=!3m1!4b1!4m2!3m1!1s0x884051b1de3821f9:0x69fb7e8be4c09317
https://www.google.com/maps/place/Florence,+KY/@38.9812919,-84.6588739,13z/data=!3m1!4b1!4m2!3m1!1s0x8841c64fb0230f03:0x4cf0ed5f518f0d26
EDIT: I believe all cities have lost their vectors.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on September 14, 2015, 08:24:45 AM
I see Michigan's outline correctly.
Quote from: iBallasticwolf2 on September 12, 2015, 08:09:55 PM
Here's the Almond Street Freeway in Poplar Bluff, Missouri.
https://www.google.ca/maps/@36.754649,-90.3888583,19.98z

This has happened in Spain, too. After two random streets of two different villages in Soria province were turned into expressways, it's now the turn for a freeway that 'splits' off A-23 near Villanueva de Gállego (North of Zaragoza): https://www.google.es/maps/@41.7791321,-0.8332269,14z
Title: Re: Incorrect highways marked on Google Maps
Post by: TravelingBethelite on September 14, 2015, 10:04:10 AM
Spot the error  :biggrin:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FspzPxSZ.png&hash=9cae5c878a8315522b616ee2e1699eb1cd619357)
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on September 14, 2015, 11:24:48 AM
Are the borders still messed up?
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on September 14, 2015, 03:49:01 PM
Quote from: freebrickproductions on September 14, 2015, 11:24:48 AM
Are the borders still messed up?
Nope. They must've got fixed when I was in school, I checked a link to make sure. (I come home at around 3:20 PM ET)
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on September 14, 2015, 05:23:09 PM
Quote from: noelbotevera on September 14, 2015, 03:49:01 PM
Quote from: freebrickproductions on September 14, 2015, 11:24:48 AM
Are the borders still messed up?
Nope. They must've got fixed when I was in school, I checked a link to make sure. (I come home at around 3:20 PM ET)
Every city and state also got its vectors back so it isn't just shown as a place marker.
Title: Re: Incorrect highways marked on Google Maps
Post by: PaulRAnderson on September 14, 2015, 06:46:10 PM
Quote from: TravelingBethelite on September 14, 2015, 10:04:10 AM
Spot the error  :biggrin:

It's still there on Google Maps like that.  US Route 6 mysteriously changes to Connecticut Route 6 and then back again!

It's bad enough the sign makers make this mistake often enough.  How does a mistake like this get into an online map?

Paul
Title: Re: Incorrect highways marked on Google Maps
Post by: TravelingBethelite on September 14, 2015, 07:19:14 PM
Quote from: PaulRAnderson on September 14, 2015, 06:46:10 PM
Quote from: TravelingBethelite on September 14, 2015, 10:04:10 AM
Spot the error  :biggrin:

It's still there on Google Maps like that.  US Route 6 mysteriously changes to Connecticut Route 6 and then back again!

It's bad enough the sign makers make this mistake often enough.  How does a mistake like this get into an online map?

Paul
Re:
https://www.google.com/maps/@41.3960854,-73.3749441,3a,75y,71.61h,58.9t/data=!3m6!1e1!3m4!1sIsQOatvYXQDNJiV4NcpHrQ!2e0!7i13312!8i6656!6m1!1e1 (https://www.google.com/maps/@41.3960854,-73.3749441,3a,75y,71.61h,58.9t/data=!3m6!1e1!3m4!1sIsQOatvYXQDNJiV4NcpHrQ!2e0!7i13312!8i6656!6m1!1e1)
https://www.google.com/maps/@41.3924336,-73.3983709,3a,75y,353.94h,67.37t/data=!3m6!1e1!3m4!1sUOkzNBCTnRNfTlKk7QOMtg!2e0!7i13312!8i6656!6m1!1e1 (https://www.google.com/maps/@41.3924336,-73.3983709,3a,75y,353.94h,67.37t/data=!3m6!1e1!3m4!1sUOkzNBCTnRNfTlKk7QOMtg!2e0!7i13312!8i6656!6m1!1e1)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FGXPrei3.jpg&hash=e9ad067048aca60f9038cdd8e3079c7e01b49695)
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on September 16, 2015, 05:18:33 PM
This road is still shown going across the tracks here, despite the crossing over the center railroad line appearing to have been closed (look at satellite view):
https://www.google.com/maps/place/6567+Township+Rd+9,+Delta,+OH+43515/@41.5647055,-84.0375656,191m/data=!3m2!1e3!4b1!4m2!3m1!1s0x883c446077327bdd:0xc6a7f19779d1ede2
Title: Re: Incorrect highways marked on Google Maps
Post by: jakeroot on September 16, 2015, 05:33:19 PM
Quote from: freebrickproductions on September 16, 2015, 05:18:33 PM
This road is still shown going across the tracks here, despite the crossing over the center railroad line appearing to have been closed (look at satellite view):
https://www.google.com/maps/place/6567+Township+Rd+9,+Delta,+OH+43515/@41.5647055,-84.0375656,191m/data=!3m2!1e3!4b1!4m2!3m1!1s0x883c446077327bdd:0xc6a7f19779d1ede2

It looks more like it's closed to through traffic, not necessarily all traffic. It has the correct "faint line" marking that Google sometimes uses for private roads. Unless there's something on the ground that indicates full, permanent closure, I think it's correct as marked.
Title: Re: Incorrect highways marked on Google Maps
Post by: Zeffy on September 16, 2015, 07:44:14 PM
Not sure it's really incorrect, but there's a random '61' appended to this street in Mt Vernon, NY:

https://www.google.com/maps/@40.898342,-73.8367113,18.42z
Title: Re: Incorrect highways marked on Google Maps
Post by: TravelingBethelite on September 16, 2015, 07:55:15 PM
There's a lot of Google Maps "signage" of Business US 60's in southern Missouri, which do not exist according to AASHTO and MODOT, aka real life. Here's 1: https://www.google.com/maps/@37.1544888,-92.7766914,16z (https://www.google.com/maps/@37.1544888,-92.7766914,16z)
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on September 18, 2015, 02:45:51 PM
In a similar manner how US 30 was labelled Quebec route 366 (i.e. QC 366), or all those US [insert number here] in [insert a state the US route goes through other than the current one here], Spanish A-4 between Madrid and Seville (But not the section in the Cadiz bay area) is now labelled as 'Ronda Urbana Norte'.

Also, several numbering changes that took place last year in my region still don't show up in Google Maps.
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on September 29, 2015, 04:14:23 AM
Business US 127 in Alma, MI is marked BUS US 27
https://goo.gl/1ofgBF (https://goo.gl/1ofgBF).
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on September 29, 2015, 07:52:55 AM
Quote from: national highway 1 on September 29, 2015, 04:14:23 AM
Business US 127 in Alma, MI is marked BUS US 27
https://goo.gl/1ofgBF (https://goo.gl/1ofgBF).
Hey! US 27's back!
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on September 30, 2015, 11:45:32 PM
Uh, Google... what happened to Letchworth State Park?!?!: https://www.google.com/maps/@42.6601925,-77.9536101,12z?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on October 04, 2015, 09:06:23 PM
This street right here is Auburn Avenue, not Sewanee Road.

EDIT: Forgot the link, lol. :pan:
https://www.google.com/maps/place/34%C2%B042'59.6%22N+86%C2%B035'09.0%22W/@34.7165786,-86.5859737,148m/data=!3m1!1e3!4m2!3m1!1s0x0:0x0?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on December 18, 2015, 10:39:59 AM
Never knew that AL 2 goes into Bridgeport, AL along AL 277, despite it being an unsigned reference route for US 72.
https://www.google.com/maps/@34.9583305,-85.7330028,14z/data=!3m1!1e3
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on December 18, 2015, 12:03:27 PM
Fixed (once it propagates).
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on January 11, 2016, 02:20:14 PM
AL 2 stays on US 72 through Athens, AL, though Google shows AL 2 taking a route that isn't part of US 72:
https://www.google.com/maps/@34.7972031,-86.9939951,15z/data=!3m1!1e3
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on January 22, 2016, 07:33:01 PM
Fixed.
Title: Re: Incorrect highways marked on Google Maps
Post by: JustDrive on February 19, 2016, 12:10:51 AM
The portion of Interstate 5 between Basilone Road and CA 905 in San Diego County is incorrectly marked as a toll road

https://www.google.com/maps/place/1600+N+Coast+Hwy,+Oceanside,+CA+92054/@33.2096715,-117.3868595,20z/data=!4m2!3m1!1s0x80dc6fb6756dd479:0x4fab5bdbadf0d7d
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on February 19, 2016, 07:29:45 AM
Not a highway, but I've noticed some sections of the Appalachian trail are missing, most notably in Vermont.
Title: Re: Incorrect highways marked on Google Maps
Post by: odditude on February 19, 2016, 08:49:38 AM
Quadrant routes are being marked in Pennsylvania, which is murder for navigation as they're not signed for public consumption.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on February 19, 2016, 11:14:53 AM
ALT US 72 should only go down I-565, not Madison Boulevard:
https://www.google.com/maps/@34.6883244,-86.7304949,14z/data=!3m1!1e3
However, there are a few ALT. US 72 shields posted along Madison Boulevard from back when the road was AL 20.
Title: Re: Incorrect highways marked on Google Maps
Post by: theFXexpert on February 19, 2016, 12:01:12 PM
FL 636 near Wauchula got mislabeled as FL 650.

https://www.google.com/maps/@27.546982,-81.7327665,12.75z?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on February 21, 2016, 06:12:15 PM
Quote from: odditude on February 19, 2016, 08:49:38 AM
Quadrant routes are being marked in Pennsylvania, which is murder for navigation as they're not signed for public consumption.

That problem has been at least recently fixed in OSM.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on February 29, 2016, 11:07:00 AM
"Dr. Martin Luther King Jr. Lane" should be "Martin Luther King Jr. Highway":
https://www.google.com/maps/@34.8063873,-86.646405,14z/data=!3m1!1e3
Also, AL 255 goes all the way to where Bob Wade Lane goes from four lanes divided to two lanes.
https://www.google.com/maps/@34.8245932,-86.6242327,3a,66.8y,229.77h,84.23t/data=!3m4!1e1!3m2!1stfscNInGp8pq6upKrxeyNg!2e0
Title: Re: Incorrect highways marked on Google Maps
Post by: national highway 1 on March 01, 2016, 12:02:27 AM
https://www.google.com.au/maps/@35.1954118,-111.767688,10.46z (https://www.google.com.au/maps/@35.1954118,-111.767688,10.46z)
Now Flagstaff is now in the middle of a humongous national park.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on March 16, 2016, 06:48:10 PM
The roads on the map haven't been updated here yet, even though they have the new road alignments on Satellite view:
https://www.google.com/maps/@34.743119,-86.5936718,786m/data=!3m1!1e3?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: tdindy88 on March 16, 2016, 06:59:00 PM
Quote from: national highway 1 on March 01, 2016, 12:02:27 AM
https://www.google.com.au/maps/@35.1954118,-111.767688,10.46z (https://www.google.com.au/maps/@35.1954118,-111.767688,10.46z)
Now Flagstaff is now in the middle of a humongous national park.

That's a national forest and a quick look around at the rest of Google Maps and a list of national forests in Arizona indicates that is correct. This probably explains why on some road maps national parks and national forests/grasslands are shown with slightly different shades of green to differentiate the two.
Title: Re: Incorrect highways marked on Google Maps
Post by: Rothman on March 17, 2016, 12:55:58 AM
Quote from: national highway 1 on March 01, 2016, 12:02:27 AM
https://www.google.com.au/maps/@35.1954118,-111.767688,10.46z (https://www.google.com.au/maps/@35.1954118,-111.767688,10.46z)
Now Flagstaff is now in the middle of a humongous national park.

Yeah, using the same color for BLM, NPS and USFS managed units is stupid.

Title: Re: Incorrect highways marked on Google Maps
Post by: myosh_tino on April 27, 2016, 06:59:12 PM
Apparently I-11 is now open southeast of Boulder City.

https://goo.gl/maps/J95pnmk4eUG2

Too bad it doesn't connect to anything.  :pan: :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on May 10, 2016, 10:11:02 PM
Quote from: freebrickproductions on February 19, 2016, 11:14:53 AM
ALT US 72 should only go down I-565, not Madison Boulevard:
Quote from: theFXexpert on February 19, 2016, 12:01:12 PM
FL 636 near Wauchula got mislabeled as FL 650.
Quote from: freebrickproductions on February 29, 2016, 11:07:00 AM
"Dr. Martin Luther King Jr. Lane" should be "Martin Luther King Jr. Highway":
Also, AL 255 goes all the way to where Bob Wade Lane goes from four lanes divided to two lanes.
Quote from: freebrickproductions on March 16, 2016, 06:48:10 PM
The roads on the map haven't been updated here yet, even though they have the new road alignments on Satellite view:
Fixed, or they will be once the map updates. Someone already got I-11.
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on May 12, 2016, 11:41:51 AM
And now the entire Appalachian Trail (except for the section between Mount Washington and NH 16 in New Hampshire) has been renamed South River Fire Road.
Title: Re: Incorrect highways marked on Google Maps
Post by: Rothman on May 12, 2016, 12:22:27 PM
Quote from: CNGL-Leudimin on May 12, 2016, 11:41:51 AM
And now the entire Appalachian Trail (except for the section between Mount Washington and NH 16 in New Hampshire) has been renamed South River Fire Road.

I recently had to contact them about the Sheltowee Trace National Recreation Trail that wasn't even 4WD accessible in central KY that they had marked as a road.  Of course, the route they gave me had me going down it; glad I caught it before heading off.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on May 12, 2016, 12:39:44 PM
Davis Circle has been extended to the traffic circle on Monroe Street, and Dr. Joseph E. Lowery Boulevard has been opened between Governors Drive (US 431) and Pelham Avenue:
https://www.google.com/maps/@34.721981,-86.5863386,17z/data=!3m1!1e3?hl=en
Davis Circle's extension is here:
https://www.google.com/maps/@34.7235361,-86.5893347,19z/data=!3m1!1e3?hl=en
Dr. Joseph E. Lowery Boulevard was built here:
https://www.google.com/maps/@34.7214781,-86.5854052,18z/data=!3m1!1e3?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on May 13, 2016, 05:59:37 PM
Quote from: Rothman on May 12, 2016, 12:22:27 PMI recently had to contact them about the Sheltowee Trace National Recreation Trail that wasn't even 4WD accessible in central KY that they had marked as a road.  Of course, the route they gave me had me going down it; glad I caught it before heading off.

Heck, last month I did a trail running race that went through a trail Google Maps has marked as a road. However 'South River Fire Road' is still marked as a trail.
Title: Re: Incorrect highways marked on Google Maps
Post by: mrsman on May 22, 2016, 08:03:19 AM
My biggest pet peeve with regard to Google Maps is when they use a highway name or number that is technically correct, but completely unused locally.

For example, the use of "lincoln highway" through many towns along US 30, even though it may be known locally (and on signs posted) as "Main Street"

Title: Re: Incorrect highways marked on Google Maps
Post by: vdeane on May 22, 2016, 01:57:48 PM
Google has marked at least one NYS reference route as well... and I'm not talking about the four that are actually signed.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on May 22, 2016, 02:06:36 PM
Quote from: vdeane on May 22, 2016, 01:57:48 PM
Google has marked at least one NYS reference route as well... and I'm not talking about the four that are actually signed.

I've found 912M and 914V (the first is the Berkshire Connector).
Title: Re: Incorrect highways marked on Google Maps
Post by: cl94 on May 22, 2016, 09:54:13 PM
Quote from: 1 on May 22, 2016, 02:06:36 PM
Quote from: vdeane on May 22, 2016, 01:57:48 PM
Google has marked at least one NYS reference route as well... and I'm not talking about the four that are actually signed.

I've found 912M and 914V (the first is the Berkshire Connector).

They've signed many more than two. 911E and 912Q in Warren County are signed prominently on Google Maps, for example.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on May 23, 2016, 11:11:54 AM
Google also has all of the county routes here in Alabama marked, even the ones that aren't signed!
Title: Re: Incorrect highways marked on Google Maps
Post by: LM117 on May 23, 2016, 06:00:13 PM
Google still has US-117 following the I-795/US-264 concurrency to I-95 in Wilson, NC despite US-117 being returned to it's 2-lane alignment between Goldsboro and Wilson years ago.  :pan: US-117 shows up on I-795/US-264 only when zoomed in close, though.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on May 31, 2016, 07:44:06 PM
College Street in Cherokee, AL was closed at the Norfolk Southern grade crossing recently, but it's still marked as open on Google Maps:
https://www.google.com/maps/@34.756263,-87.9736739,19.45z?hl=en
Title: Re: Incorrect highways marked on Google Maps
Post by: Avalanchez71 on June 03, 2016, 01:04:48 PM
Google shows a secondary state road in NC as state road "NORTH CAROLINA" off of US 70 out by Beaufort.
Title: Re: Incorrect highways marked on Google Maps
Post by: US71 on June 05, 2016, 09:43:43 PM
It's not Google, but I've seen a few TV weather maps show I-271 in Oklahoma ;)
Title: Re: Incorrect highways marked on Google Maps
Post by: Bickendan on June 08, 2016, 09:58:04 PM
OR 170 has made an appearance on google maps, despite having been turned back over 20 years ago...
Title: Re: Incorrect highways marked on Google Maps
Post by: bootmii on July 20, 2016, 02:54:35 PM
Colma Blvd is apparently 500 County. :-D
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on August 01, 2016, 12:18:29 AM
Looks like Google didn't get the memo that the eastern half of the Inner Loop was permanently closed a year and a half ago: https://goo.gl/maps/jkmuWQHLKq22
Title: Re: Incorrect highways marked on Google Maps
Post by: CtrlAltDel on August 01, 2016, 12:24:23 AM
It bothers me that the old Elgin-O'Hare Expressway is now marked as "Illinois Route 390." It is Illinois Route 390, but it's marked with words instead of a 390 in a circle.
Title: Re: Incorrect highways marked on Google Maps
Post by: dfwmapper on August 01, 2016, 12:49:34 AM
Working on Rochester. Some genius put it back on the map after it had already been deleted. It should only take 10 or 15 tries to get it deleted again.

IL 390 is stuck like that because Google sucks at fixing bugs on Map Maker, in this case the one that prevents numbered highway names from being created or modified. 390 has been reported and requested to be fixed directly by Google (they use a separate system that is apparently less buggy), but nothing has come of it. :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on August 01, 2016, 02:19:43 PM
Apparently, the ON 417 extension is now open. Even if it was, Google marks it as ON 17, it's not marked as a freeway (as it should), and the loops at Campbell drive are done terribly.  :banghead:

https://goo.gl/maps/zL5QcErLqs62
Title: Re: Incorrect highways marked on Google Maps
Post by: iBallasticwolf2 on April 13, 2017, 09:55:25 PM
Seeing I-69 marked on roads in Tennessee, even if they are surface roads.
https://www.google.ca/maps/@35.1953456,-90.026293,14.96z
https://www.google.ca/maps/@36.0576136,-89.3685167,14.53z
Title: Re: Incorrect highways marked on Google Maps
Post by: Max Rockatansky on April 23, 2017, 08:26:30 PM
For some reason Google has CA 145 terminating at the north end of Millerton Lake rather than CA 41:

https://www.google.com/maps/@37.0188957,-119.6775379,15z?hl=en

East of the CA 145 terminus the road is called Road 145 which what I'm thinking is causing the map error.
Title: Re: Incorrect highways marked on Google Maps
Post by: JMoses24 on May 19, 2017, 09:08:35 PM
Apparently, SR 265 in Indiana is now marked as SR 841 as well (but I've seen no such signage to that effect).
Title: Re: Incorrect highways marked on Google Maps
Post by: Max Rockatansky on May 19, 2017, 09:20:18 PM
State road 4a is still listed as a state highway on Little Torch Key.  County routes are still listed on Geiger, Boca Chica, Sugarloaf, and Boot Key.
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on June 01, 2017, 04:53:35 PM
Google, this is the United States. (https://www.google.com/maps/@30.3241415,-97.6760119,17z)
Title: Re: Incorrect highways marked on Google Maps
Post by: jakeroot on June 01, 2017, 05:45:27 PM
Quote from: noelbotevera on June 01, 2017, 04:53:35 PM
Google, this is the United States. (https://www.google.com/maps/@30.3241415,-97.6760119,17z)

Hahaha that's actually pretty good!
Title: Re: Incorrect highways marked on Google Maps
Post by: CNGL-Leudimin on June 01, 2017, 06:07:08 PM
Quote from: noelbotevera on June 01, 2017, 04:53:35 PM
Google, this is the United States. (https://www.google.com/maps/@30.3241415,-97.6760119,17z)

Google, this is Spain (https://www.google.es/maps/@42.3428056,0.2649749,16z).
Title: Re: Incorrect highways marked on Google Maps
Post by: ilpt4u on June 01, 2017, 07:46:08 PM
Quote from: noelbotevera on June 01, 2017, 04:53:35 PM
Google, this is the United States. (https://www.google.com/maps/@30.3241415,-97.6760119,17z)
I'm not the only person who noticed that today...

https://goo.gl/maps/GjmnaRfZLbJ2

"Ruta de Illinois 13" better be pronounced "trece"
Title: Re: Incorrect highways marked on Google Maps
Post by: noelbotevera on June 01, 2017, 08:34:18 PM
Ladies and gentlemen (and goats), I present to you the highest exit number in existence!

EXIT TWO THOUSAND, TWO HUNDRED, TWENTY TWO! (https://www.google.com/maps/@30.308019,-97.7128821,16z)
Title: Re: Incorrect highways marked on Google Maps
Post by: Max Rockatansky on June 01, 2017, 10:07:35 PM
Quote from: noelbotevera on June 01, 2017, 08:34:18 PM
Ladies and gentlemen (and goats), I present to you the highest exit number in existence!

EXIT TWO THOUSAND, TWO HUNDRED, TWENTY TWO! (https://www.google.com/maps/@30.308019,-97.7128821,16z)

Ironic considering how the exits are for real with I-10 in Texas.
Title: Re: Incorrect highways marked on Google Maps
Post by: rickmastfan67 on June 01, 2017, 10:27:13 PM
Quote from: noelbotevera on June 01, 2017, 08:34:18 PM
Ladies and gentlemen (and goats), I present to you the highest exit number in existence!

EXIT TWO THOUSAND, TWO HUNDRED, TWENTY TWO! (https://www.google.com/maps/@30.308019,-97.7128821,16z)

Even the routing engine says "Head northeast on N Interstate 35 Frontage Rd toward Exit 2222 W". lol.
Title: Re: Incorrect highways marked on Google Maps
Post by: texaskdog on June 01, 2017, 10:54:51 PM
Quote from: rickmastfan67 on June 01, 2017, 10:27:13 PM
Quote from: noelbotevera on June 01, 2017, 08:34:18 PM
Ladies and gentlemen (and goats), I present to you the highest exit number in existence!

EXIT TWO THOUSAND, TWO HUNDRED, TWENTY TWO! (https://www.google.com/maps/@30.308019,-97.7128821,16z)

Even the routing engine says "Head northeast on N Interstate 35 Frontage Rd toward Exit 2222 W". lol.

Well it is Ranch Road 2222!
Title: Re: Incorrect highways marked on Google Maps
Post by: Eth on June 02, 2017, 02:03:49 PM
Quote from: texaskdog on June 01, 2017, 10:54:51 PM
Quote from: rickmastfan67 on June 01, 2017, 10:27:13 PM
Quote from: noelbotevera on June 01, 2017, 08:34:18 PM
Ladies and gentlemen (and goats), I present to you the highest exit number in existence!

EXIT TWO THOUSAND, TWO HUNDRED, TWENTY TWO! (https://www.google.com/maps/@30.308019,-97.7128821,16z)

Even the routing engine says "Head northeast on N Interstate 35 Frontage Rd toward Exit 2222 W". lol.

Well it is Ranch Road 2222!

Something similar happens around the FL 826/FL 836 interchange (https://www.google.com/maps/@25.775981,-80.3260061,14z) in Miami.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on June 21, 2017, 09:54:24 PM
US Routes (and a US State Route) in Canada?
https://www.google.com/maps/@46.0740965,-60.321503,43372m/data=!3m1!1e3

Even more here:
https://www.google.com/maps/@45.0952779,-63.7588896,187188m/data=!3m1!1e3
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on June 21, 2017, 09:58:28 PM
Quote from: freebrickproductions on June 21, 2017, 09:54:24 PM
US Routes (and a US State Route) in Canada?
https://www.google.com/maps/@46.0740965,-60.321503,43372m/data=!3m1!1e3

Even more here:
https://www.google.com/maps/@45.0952779,-63.7588896,187188m/data=!3m1!1e3

Nova Scotia has US route lookalikes. It's not an error.
Title: Re: Incorrect highways marked on Google Maps
Post by: SignGeek101 on June 21, 2017, 10:24:23 PM
Quote from: 1 on June 21, 2017, 09:58:28 PM
Quote from: freebrickproductions on June 21, 2017, 09:54:24 PM
US Routes (and a US State Route) in Canada?
https://www.google.com/maps/@46.0740965,-60.321503,43372m/data=!3m1!1e3

Even more here:
https://www.google.com/maps/@45.0952779,-63.7588896,187188m/data=!3m1!1e3

Nova Scotia has US route lookalikes. It's not an error.

I believe there are other countries (too lazy to look right now) that also use the US Route shield on Google Maps. Obviously, they're not actual US Routes, but have similar looking shields.
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on June 22, 2017, 12:41:44 AM
Quote from: SignGeek101 on June 21, 2017, 10:24:23 PM
Quote from: 1 on June 21, 2017, 09:58:28 PM
Quote from: freebrickproductions on June 21, 2017, 09:54:24 PM
US Routes (and a US State Route) in Canada?
https://www.google.com/maps/@46.0740965,-60.321503,43372m/data=!3m1!1e3

Even more here:
https://www.google.com/maps/@45.0952779,-63.7588896,187188m/data=!3m1!1e3

Nova Scotia has US route lookalikes. It's not an error.

I believe there are other countries (too lazy to look right now) that also use the US Route shield on Google Maps. Obviously, they're not actual US Routes, but have similar looking shields.
Huh. Are they actually signed though? I did some looking (even at junctions) and never found any.
Title: Re: Incorrect highways marked on Google Maps
Post by: Jim on June 22, 2017, 08:01:59 AM
Quote from: freebrickproductions on June 22, 2017, 12:41:44 AM
Huh. Are they actually signed though? I did some looking (even at junctions) and never found any.

I've only been just across the border into NS at Amherst, but saw these routes signed.  This one on August 8, 2014.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.teresco.org%2Fpics%2Fsigns%2F20140808%2Fns2northtotc104.jpg&hash=4da7406678b02d06334a931ef7425e08277771d5)
Title: Re: Incorrect highways marked on Google Maps
Post by: freebrickproductions on June 22, 2017, 04:19:32 PM
Quote from: Jim on June 22, 2017, 08:01:59 AM
Quote from: freebrickproductions on June 22, 2017, 12:41:44 AM
Huh. Are they actually signed though? I did some looking (even at junctions) and never found any.

I've only been just across the border into NS at Amherst, but saw these routes signed.  This one on August 8, 2014.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.teresco.org%2Fpics%2Fsigns%2F20140808%2Fns2northtotc104.jpg&hash=4da7406678b02d06334a931ef7425e08277771d5)
Wow! That's rather interesting. Love how they use the older US shield design!
Title: Re: Incorrect highways marked on Google Maps
Post by: epzik8 on June 25, 2017, 09:47:00 AM
They have South Carolina Route 22 marked on a little cul-de-sac in the Barefoot Resort area of North Myrtle Beach, South Carolina. I found that because I'm staying in a Barefoot condo right now on vacation and Google Maps is using the location from my phone.
Title: Re: Incorrect highways marked on Google Maps
Post by: D-Dey65 on August 25, 2017, 06:07:40 PM
Did anyone catch Aqueduct Road in White Plains, NY as being part of NY 124 between NY 100 and NY 119? Well Google Maps thinks it is.

Title: Re: Incorrect highways marked on Google Maps
Post by: roadman65 on October 29, 2017, 04:17:18 PM
ttps://www.google.com/maps/place/Tampa,+FL/@28.004851,-82.5023568,15z/data=!4m5!3m4!1s0x88c2b782b3b9d1e1:0xa75f1389af96b463!8m2!3d27.950575!4d-82.4571776

Found this one where US 92 is on Dale Mabry Highway in Tampa north of where it departs on Hillsborough Avenue.  US 92 is only on Dale Mabry between Gandy Blvd. in South Tampa and Hillsborough Avenue just north of Raymond James Stadium.
Title: Re: Incorrect highways marked on Google Maps
Post by: hotdogPi on March 17, 2018, 09:14:53 AM
This one is on the Google Maps app instead of the website, and the error is spoken instead of written:

"Robert East Lee Boulevard" at Stone Mountain in Georgia, due to E being pronounced as East regardless of context. Now I'm wondering about Washington DC's lettered streets.
Title: Re: Incorrect highways marked on Google Maps
Post by: mrcmc888 on March 22, 2018, 12:29:27 PM
Google Maps is still marking Main Street/Delaware Avenue in Newark, DE as being part of DE-2 despite it having been truncated to DE-72 for about 5 years.

Something tells me DelDOT is using Google to find out where their own roads are, because a brand new set of DE-2 markers just went up on Main about two months ago... :banghead:
Title: Re: Incorrect highways marked on Google Maps
Post by: briantroutman on August 02, 2018, 04:07:23 PM
Forgive me for not being entirely up-to-date on Google Maps and the editing process. From what I understand, the ability to make edits and corrections to Google Maps has been locked down to a much smaller group than before–small enough to the point that no one on these boards can do so. (And therefore, this is the reason why the Google Maps Edit Request thread was allowed to die.) Is that correct?

I just noticed that the entirety of US 15 is named "U.S. Hwy 15/501" –even in places 500 miles away from the US 501 overlap, and even on sections that overlap with other routes, like US 11, 29, and 340. Even in places where lingo like "U.S. Highway"  is alien.

This seems to be a common issue–a name which applies only to a short section somehow being pasted over the entire length. I recall Google having labeled I-80 as "Christopher Columbus Highway"  from coast to coast at one point, despite it not being designated as such in many states...it certainly isn't designated under that name in Pennsylvania. Does the Google Maps editing interface that makes it too easy to accidentally click "apply to all"  or something like that?

And since Google Maps is now apparently closed to outside editors, is there any way to flag something that's incorrect?
Title: Re: Incorrect highways marked on Google Maps
Post by: WNYroadgeek on August 12, 2018, 03:45:38 PM
Google, I'm pretty sure this isn't California: https://goo.gl/maps/13JBjw4Ad6T2

Quote from: briantroutman on August 02, 2018, 04:07:23 PMAnd since Google Maps is now apparently closed to outside editors, is there any way to flag something that's incorrect?

From what I can see:

-Main Menu (three liens at the top left)
-Send feedback
-Log in to Google Account (if not already)
-Wrong information
-Click on the affected road