News:

Thanks to everyone for the feedback on what errors you encountered from the forum database changes made in Fall 2023. Let us know if you discover anymore.

Main Menu

Google Maps just fucking SUCKS now

Started by agentsteel53, February 26, 2014, 03:26:58 PM

Previous topic - Next topic

anyone else having an insane amount of trouble with the new Google Maps?

instant browser crash
10 (3.5%)
loads fine, then crashes the browser when attempting to do anything at all
23 (8%)
not quite terrible, but still worse
127 (44.4%)
I am indifferent
63 (22%)
I actually like the new Google Maps
63 (22%)

Total Members Voted: 286

MNHighwayMan

Quote from: 20160805 on March 10, 2019, 07:29:54 AM
Quote from: bm7 on December 27, 2018, 06:33:28 PM
The user-submitted 360 images are starting to really irritate me. It seems that when going into street view, Google Maps prioritizes them over normal street view imagery which means it often takes multiple attempts to get into street view in areas where people have submitted pictures. Or even worse, when people tried to make their own 'street view' with their awful phone camera, which means entire roads are overlapping with user images.
This has been driving me crazy for probably years now.

This so much. Especially frustrating when I see something in Google's images, then move forward to get a better look and it switches to user bullshit, and the thing isn't there anymore.


Michael

Quote from: MNHighwayMan on March 10, 2019, 04:39:50 PM
Quote from: 20160805 on March 10, 2019, 07:29:54 AM
Quote from: bm7 on December 27, 2018, 06:33:28 PM
The user-submitted 360 images are starting to really irritate me. It seems that when going into street view, Google Maps prioritizes them over normal street view imagery which means it often takes multiple attempts to get into street view in areas where people have submitted pictures. Or even worse, when people tried to make their own 'street view' with their awful phone camera, which means entire roads are overlapping with user images.
This has been driving me crazy for probably years now.

This so much. Especially frustrating when I see something in Google's images, then move forward to get a better look and it switches to user bullshit, and the thing isn't there anymore.

Try using the arrow keys instead of clicking.  If I'm looking at a Street View image that doesn't quite line up with the road (usually older images and/or multi-lane roads), it jumps to one that does line up.  Using the arrow keys forces the road you're on and the date to stay the same.




I just came across something actually good in Google Maps that was in classic Google Maps, but wasn't in new Maps at first.  In classic Maps, you could drop Pegman pointing in a specific direction.  For example, if you wanted to face east on a north-south road, you'd drop Pegman off to the right.  I never got this to work in new Maps, but just now noticed it works again!  New Maps used to default to looking north, and if you re-entered Street View, it would face the last direction you were looking.  For a while now, I've been ending up in what I thought was a random direction, but I just realized it was working the old way again!  My only complaints are that the green circle under Pegman doesn't point the way he's "looking", and it's harder to get the direction just right than it was in classic Maps.

ipeters61

Quote from: 20160805 on March 10, 2019, 07:29:54 AM
Quote from: bm7 on December 27, 2018, 06:33:28 PM
The user-submitted 360 images are starting to really irritate me. It seems that when going into street view, Google Maps prioritizes them over normal street view imagery which means it often takes multiple attempts to get into street view in areas where people have submitted pictures. Or even worse, when people tried to make their own 'street view' with their awful phone camera, which means entire roads are overlapping with user images.
This has been driving me crazy for probably years now.
Some guy decided to cover The Circle in Georgetown DE with his own "street view" images and now it's practically impossible to navigate there in actual Street View.
Disclaimer: Opinions expressed on my posts on the AARoads Forum are my own and do not represent official positions of my employer.
Instagram | Clinched Map

Rothman

Please note: All comments here represent my own personal opinion and do not reflect the official position(s) of NYSDOT.

ipeters61

Quote from: Rothman on April 03, 2019, 10:51:29 AM
See the Garden State Parkway address:

https://goo.gl/maps/Vb2XuYPZnwo
I've seen that on a few expressways when getting directions.

Speaking of that, here's a neighborhood where the streets show up in Cyrillic characters.  It's in Delaware.  https://goo.gl/maps/7ACDyQxyRsz
Disclaimer: Opinions expressed on my posts on the AARoads Forum are my own and do not represent official positions of my employer.
Instagram | Clinched Map

Rothman

Quote from: ipeters61 on April 03, 2019, 11:48:21 AM
Quote from: Rothman on April 03, 2019, 10:51:29 AM
See the Garden State Parkway address:

https://goo.gl/maps/Vb2XuYPZnwo
I've seen that on a few expressways when getting directions.

Speaking of that, here's a neighborhood where the streets show up in Cyrillic characters.  It's in Delaware.  https://goo.gl/maps/7ACDyQxyRsz
That is truly bizarre since it looks like regular English on the map.
Please note: All comments here represent my own personal opinion and do not reflect the official position(s) of NYSDOT.

jakeroot

Finally experience a legit, maddening issue.

For some reason, I cannot leave the path of a street view vehicle. If I'm clicking along a road, I am only able to advance (on-screen clicking) in the direction that the camera car proceeds. So, if I'm clicking down a major road, and the street view vehicle turns right, I am not able to click forward along the main road to follow the route of another street view vehicle. Instead, I can only click right. And so on, and on, etc.

Because the system seems to only recognize the existence of that single street view vehicle, I also cannot access historical street view imagery (as they are routes taken by other street view vehicles). I can still click around on the map in the bottom left, but I am, again, forced to follow the route of that vehicle, and there's still no historic imagery available.

I've been able to repeat the issue on several browsers on Windows 10-1803 (Chrome, Firefox, and Edge), as well as on my iMac, running Mojave 10.14.4 (Chrome and Safari). I'm going to assume that some of you might be experiencing a similar issue as well, then?

hotdogPi

Clinched

Traveled, plus
US 13, 44, 50
MA 22, 40, 107, 109, 117, 119, 126, 141, 159
NH 27, 111A(E); CA 133; NY 366; GA 42, 140; FL A1A, 7; CT 32; VT 2A, 5A; PA 3, 51, 60, QC 162, 165, 263; 🇬🇧A100, A3211, A3213, A3215, A4222; 🇫🇷95 D316

US 89

Yep, started having the exact same issue last night. It's continuing through today and it's pissing me off. I'm running macOS/Chrome.

jakeroot

Quote from: 1 on May 13, 2019, 06:44:51 PM
No problem here.

What's your system?

Quote from: US 89 on May 13, 2019, 06:46:00 PM
Yep, started having the exact same issue last night. It's continuing through today and it's pissing me off. I'm running macOS/Chrome.

Good to know I'm not alone.

jakeroot

I would like to comment, additionally, that I'm not seeing the issue along every road. Just, quite a few of them.

hotdogPi

Quote from: jakeroot on May 13, 2019, 06:53:32 PM
Quote from: 1 on May 13, 2019, 06:44:51 PM
No problem here.
What's your system?

Mac OS 10.13.6, Safari 12.0.3. Normal both in a regular web browser (logged in to Google) and in private browsing.
Clinched

Traveled, plus
US 13, 44, 50
MA 22, 40, 107, 109, 117, 119, 126, 141, 159
NH 27, 111A(E); CA 133; NY 366; GA 42, 140; FL A1A, 7; CT 32; VT 2A, 5A; PA 3, 51, 60, QC 162, 165, 263; 🇬🇧A100, A3211, A3213, A3215, A4222; 🇫🇷95 D316

ipeters61

Was trying to use Street View when at work today, does part of this issue involve a very "slow" movement along the road? (like you can't go very far on one click?)
Disclaimer: Opinions expressed on my posts on the AARoads Forum are my own and do not represent official positions of my employer.
Instagram | Clinched Map

hotdogPi

Quote from: ipeters61 on May 13, 2019, 07:00:40 PM
Was trying to use Street View when at work today, does part of this issue involve a very "slow" movement along the road? (like you can't go very far on one click?)

That happens to me for 2007—2009 imagery, which seems to be a different issue.
Clinched

Traveled, plus
US 13, 44, 50
MA 22, 40, 107, 109, 117, 119, 126, 141, 159
NH 27, 111A(E); CA 133; NY 366; GA 42, 140; FL A1A, 7; CT 32; VT 2A, 5A; PA 3, 51, 60, QC 162, 165, 263; 🇬🇧A100, A3211, A3213, A3215, A4222; 🇫🇷95 D316

jakeroot

Quote from: ipeters61 on May 13, 2019, 07:00:40 PM
Was trying to use Street View when at work today, does part of this issue involve a very "slow" movement along the road? (like you can't go very far on one click?)

In those sections where I am stuck on a single "track" (most roads from what I can tell), yes the movement is quite slow. I can't go more than a few metres in a single go, unless I get really lucky, or there's a gap in the images available from that "track", forcing me to either go backwards, or really far forwards.

Quote from: 1 on May 13, 2019, 06:59:31 PM
Quote from: jakeroot on May 13, 2019, 06:53:32 PM
Quote from: 1 on May 13, 2019, 06:44:51 PM
No problem here.
What's your system?

Mac OS 10.13.6, Safari 12.0.3. Normal both in a regular web browser (logged in to Google) and in private browsing.

Interesting.

Check out this street view link, and see if you can get unstuck from the August 2018 "track": https://goo.gl/maps/V8USbNrmYvEdzaaq9

I am personally unable (in the link above) to go anywhere other than between Lenora and 8th. I cannot click into the intersection.

hotdogPi

Quote from: jakeroot on May 13, 2019, 07:47:24 PM

I am personally unable (in the link above) to go anywhere other than between Lenora and 8th. I cannot click into the intersection.

Same here. Northeastern MA is fine, though.
Clinched

Traveled, plus
US 13, 44, 50
MA 22, 40, 107, 109, 117, 119, 126, 141, 159
NH 27, 111A(E); CA 133; NY 366; GA 42, 140; FL A1A, 7; CT 32; VT 2A, 5A; PA 3, 51, 60, QC 162, 165, 263; 🇬🇧A100, A3211, A3213, A3215, A4222; 🇫🇷95 D316

Eth

Quote from: jakeroot on May 13, 2019, 07:47:24 PM
Quote from: ipeters61 on May 13, 2019, 07:00:40 PM
Was trying to use Street View when at work today, does part of this issue involve a very "slow" movement along the road? (like you can't go very far on one click?)

In those sections where I am stuck on a single "track" (most roads from what I can tell), yes the movement is quite slow. I can't go more than a few metres in a single go, unless I get really lucky, or there's a gap in the images available from that "track", forcing me to either go backwards, or really far forwards.

Quote from: 1 on May 13, 2019, 06:59:31 PM
Quote from: jakeroot on May 13, 2019, 06:53:32 PM
Quote from: 1 on May 13, 2019, 06:44:51 PM
No problem here.
What's your system?

Mac OS 10.13.6, Safari 12.0.3. Normal both in a regular web browser (logged in to Google) and in private browsing.

Interesting.

Check out this street view link, and see if you can get unstuck from the August 2018 "track": https://goo.gl/maps/V8USbNrmYvEdzaaq9

I am personally unable (in the link above) to go anywhere other than between Lenora and 8th. I cannot click into the intersection.

I see the same thing (and also, if I go out to the map and drop down onto Westlake, I can't access Lenora/8th from there). macOS 10.14.4, Chrome 73.

jakeroot

Quote from: 1 on May 13, 2019, 07:53:10 PM
Quote from: jakeroot on May 13, 2019, 07:47:24 PM

I am personally unable (in the link above) to go anywhere other than between Lenora and 8th. I cannot click into the intersection.

Same here. Northeastern MA is fine, though.

As is much of Vancouver. A bunch of the Seattle area is all screwed up though. Apparently other parts of the US as well. Weird how this error is so regional.

Quote from: Eth on May 13, 2019, 08:30:51 PM
I see the same thing (and also, if I go out to the map and drop down onto Westlake, I can't access Lenora/8th from there). macOS 10.14.4, Chrome 73.

Thanks for the info. Looks like a relatively major issue (in the areas that it affects).

hotdogPi

I found an area with the problem in Cambridge MA. It might be an urban/rural split, not a geographical split.
Clinched

Traveled, plus
US 13, 44, 50
MA 22, 40, 107, 109, 117, 119, 126, 141, 159
NH 27, 111A(E); CA 133; NY 366; GA 42, 140; FL A1A, 7; CT 32; VT 2A, 5A; PA 3, 51, 60, QC 162, 165, 263; 🇬🇧A100, A3211, A3213, A3215, A4222; 🇫🇷95 D316

Ben114

Quote from: Eth on May 13, 2019, 08:30:51 PM
Quote from: jakeroot on May 13, 2019, 07:47:24 PM
Quote from: ipeters61 on May 13, 2019, 07:00:40 PM
Was trying to use Street View when at work today, does part of this issue involve a very "slow" movement along the road? (like you can't go very far on one click?)

In those sections where I am stuck on a single "track" (most roads from what I can tell), yes the movement is quite slow. I can't go more than a few metres in a single go, unless I get really lucky, or there's a gap in the images available from that "track", forcing me to either go backwards, or really far forwards.

Quote from: 1 on May 13, 2019, 06:59:31 PM
Quote from: jakeroot on May 13, 2019, 06:53:32 PM
Quote from: 1 on May 13, 2019, 06:44:51 PM
No problem here.
What's your system?

Mac OS 10.13.6, Safari 12.0.3. Normal both in a regular web browser (logged in to Google) and in private browsing.

Interesting.

Check out this street view link, and see if you can get unstuck from the August 2018 "track": https://goo.gl/maps/V8USbNrmYvEdzaaq9

I am personally unable (in the link above) to go anywhere other than between Lenora and 8th. I cannot click into the intersection.

I see the same thing (and also, if I go out to the map and drop down onto Westlake, I can't access Lenora/8th from there). macOS 10.14.4, Chrome 73.
Works with me. Running Chrome OS 73 with Google Chrome 74 (not sure about web browser version)

kphoger

Quote from: 1 on May 13, 2019, 07:53:10 PM

Quote from: jakeroot on May 13, 2019, 07:47:24 PM
I am personally unable (in the link above) to go anywhere other than between Lenora and 8th. I cannot click into the intersection.

Same here. Northeastern MA is fine, though.

Hmmm...  I just started noticing the issue yesterday, and I've been looking at Boston these days.
Keep right except to pass.  Yes.  You.
Visit scenic Orleans County, NY!
Male pronouns, please.

Quote from: Philip K. DickIf you can control the meaning of words, you can control the people who must use them.

ipeters61

Quote from: 1 on May 13, 2019, 08:44:10 PM
I found an area with the problem in Cambridge MA. It might be an urban/rural split, not a geographical split.
Dover DE has the same issue.
Disclaimer: Opinions expressed on my posts on the AARoads Forum are my own and do not represent official positions of my employer.
Instagram | Clinched Map

Roadsguy

I notice this issue sometimes, but not other times it works. It seems to work or not work on the same roads every time, though I have no idea what pattern there'd be.
Mileage-based exit numbering implies the existence of mileage-cringe exit numbering.

roadman65

I miss the color contrasts as now Google maps don't have much to differentiate the streets from the areas around them.  My HP notebook has everything white including the areas off the streets.

It maybe my pc, but it is an issue I hate with Google maps.
Every day is a winding road, you just got to get used to it.

Sheryl Crowe

ipeters61

Quote from: roadman65 on May 14, 2019, 10:40:28 AM
I miss the color contrasts as now Google maps don't have much to differentiate the streets from the areas around them.  My HP notebook has everything white including the areas off the streets.

It maybe my pc, but it is an issue I hate with Google maps.
Looking at the monitor I'm using right now (Dell P2217H), when I set contrast to about 90%, then everything is white on the map.  Having it at 75% makes it totally usable.

Is there anything you can change in the graphics card settings?  I really hate how a lot of laptop screens are these days...
Disclaimer: Opinions expressed on my posts on the AARoads Forum are my own and do not represent official positions of my employer.
Instagram | Clinched Map



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.