News:

Thanks to everyone for the feedback on what errors you encountered at https://www.aaroads.com/forum/index.php?topic=33904.0
Corrected several already and appreciate your patience as we work through the rest.

Main Menu

Incorrect highways marked on Google Maps

Started by Riverside Frwy, November 08, 2009, 09:56:04 PM

Previous topic - Next topic

rickmastfan67

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


HighwayMaster

#326
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

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

http://g.co/maps/a92ku
Life is too short not to have Tim Hortons donuts.

InterstateNG

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?
I demand an apology.

Alps


F350


HighwayMaster

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.
Life is too short not to have Tim Hortons donuts.

Bickendan

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.

rickmastfan67

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.

NE2

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.
pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

vtk

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.
Wait, it's all Ohio? Always has been.

HighwayMaster

Not a road, but I don't remember Norway, ME as being this big:

http://g.co/maps/4zmav
Life is too short not to have Tim Hortons donuts.

NE2

pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

Bickendan

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.

MDRoads

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.

PurdueBill

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.

MDRoads

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.

PurdueBill

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.

rickmastfan67

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:

mukade

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.

roadfro

^ It appears someone is blindly following the Wikipedia naming policies for state-detail articles of US routes...
Roadfro - AARoads Pacific Southwest moderator since 2010, Nevada roadgeek since 1983.

mcdonaat

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.

hbelkins

Zoom in to US 20 in Michigan City, Ind., and see what you find.


Government would be tolerable if not for politicians and bureaucrats.

NE2

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?
pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

Central Avenue

Is the entirety of US 20 marked as "in Illinois"/"in Nebraska" now? I noticed the same thing in Toledo...
Routewitches. These children of the moving road gather strength from travel . . . Rather than controlling the road, routewitches choose to work with it, borrowing its strength and using it to make bargains with entities both living and dead. -- Seanan McGuire, Sparrow Hill Road

roadfro

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

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".
Roadfro - AARoads Pacific Southwest moderator since 2010, Nevada roadgeek since 1983.



Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.