AARoads Forum

National Boards => General Highway Talk => Topic started by: agentsteel53 on February 26, 2014, 03:26:58 PM

Poll
Question: anyone else having an insane amount of trouble with the new Google Maps?
Option 1: instant browser crash votes: 10
Option 2: loads fine, then crashes the browser when attempting to do anything at all votes: 23
Option 3: not quite terrible, but still worse votes: 127
Option 4: I am indifferent votes: 63
Option 5: I actually like the new Google Maps votes: 63
Title: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 03:26:58 PM
well, shit.

it's gone from a tool that I rely on several times a day, to something for which I have had to erase the memorized auto-complete URL in my browser's address bar, lest I prefer to not absentmindedly crash my browser.

what the high holy fuck ever prompted Google to release this pile of shit?

it's like going from a car that reliably transports you to point B, to Ace Rothstein's Cadillac.
Title: Re: Google Maps just fucking SUCKS now
Post by: bassoon1986 on February 26, 2014, 03:30:57 PM
So far it has been enjoyable for me. It seemed a little slow at first, but I actually like the small map that I can directly click on when I'm in Streetview and get thrown from an overpass.
Title: Re: Google Maps just fucking SUCKS now
Post by: corco on February 26, 2014, 03:31:08 PM
maps.google.ca is where it's at now.

Yeah, they took the best tool for roadgeeking and made it useless.
Title: Re: Google Maps just fucking SUCKS now
Post by: Truvelo on February 26, 2014, 03:34:27 PM
There is an option to go back to the old layout
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on February 26, 2014, 03:34:36 PM
I have not experienced a browser crash with it, but in general I have found it to be slower than it used to be and I've switched to using Bing Maps until I hear it's been resolved. Bing's aerial images are considerably older than Google's, however.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 26, 2014, 03:35:31 PM
I am not seeing the "new" things except business/bypass/truck routes and some hidden designations (NY 912M, NJ 444).
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 26, 2014, 03:36:41 PM
agentsteel53, does google.com/mapmaker (http://google.com/mapmaker) still work without crashing?
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 03:37:35 PM
Quote from: Truvelo on February 26, 2014, 03:34:27 PM
There is an option to go back to the old layout

can you give me a direct link?  I cannot open the new page and let it load long enough to show all the bells, whistles, and gongs.

as far as hidden designations, and new truck routes, and what have you... again, I physically cannot get that far.  it gulps down about one gigabyte of RAM in 10-15 seconds, which makes Flickr look like an Atari 2600.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 26, 2014, 03:39:02 PM
Quote from: 1 on February 26, 2014, 03:35:31 PM
I am not seeing the "new" things except business/bypass/truck routes and some hidden designations (NY 912M, NJ 444).
Same here. I've never been autoswitched to the new style; who knows why.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 26, 2014, 03:42:54 PM
I'm still on old Google Maps and until they force me to switch I'm not changing it.

@jake: Try this link, maybe it'll work? I just almost made Firefox crash doing this. https://www.google.com/maps?t=m&ll=40.07304,-74.724323&z=8&output=classic&dg=opt
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 03:51:13 PM
Quote from: Zeffy on February 26, 2014, 03:42:54 PM
I'm still on old Google Maps and until they force me to switch I'm not changing it.

@jake: Try this link, maybe it'll work? I just almost made Firefox crash doing this. https://www.google.com/maps?t=m&ll=40.07304,-74.724323&z=8&output=classic&dg=opt

awesome!!  thank you.  it looks like "output=classic" is the relevant piece of code there.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 26, 2014, 03:56:40 PM
I use maps.google.es, still with the old maps. Until they force me to use the new maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 26, 2014, 03:57:46 PM
The poll is a 5-way tie!
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 03:59:24 PM
Quote from: 1 on February 26, 2014, 03:57:46 PM
The poll is a 5-way tie!

"crashes for 40% of users" is really, really not the experience Google should be promoting.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 26, 2014, 04:01:52 PM
No problem. I'm not sure what the new Google Maps' problem is, but here's a fun fact: Memory usage of Firefox with Google Maps open and NO OTHER TABS:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1300.photobucket.com%2Falbums%2Fag88%2FZeffyboy%2FNewGoogleMaps_memusage_zpsa961b45d.png&hash=f30288c291c71a3ec9ad2b6bfe6f07e644bb4a1f)

604 MB!!!! THAT'S A SINGLE TAB!

Mine doesn't crash started crashing cause why the fuck not, but here's what usually ends up happening:
* It's always slow (always)
* City and town names disappear. Route shields disappear. All I fucking see is lines. And no matter what I do, until I refresh the page and rape my memory more, it won't fix itself.
* I get frustrated in Street View because it's so clunky
* FIREFOX HAS STOPPED RESPONDING
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on February 26, 2014, 04:03:17 PM
Quote from: agentsteel53 on February 26, 2014, 03:26:58 PM
well, shit.

it's gone from a tool that I rely on several times a day, to something for which I have had to erase the memorized auto-complete URL in my browser's address bar, lest I prefer to not absentmindedly crash my browser.

what the high holy fuck ever prompted Google to release this pile of shit?

it's like going from a car that reliably transports you to point B, to Ace Rothstein's Cadillac.

So it has extra plating under the driver's seat saving your life in a car bombing?

Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on February 26, 2014, 04:05:08 PM
BTW,

THE NEW GOOGLE MAPS INTERFACE SUCKS MONKEY BALLS!  :verymad: :thumbdown:

Hence why I switched back to the old interface.  That, and I couldn't figure out how to link from the new interface.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 26, 2014, 04:07:24 PM
Quote from: Brandon on February 26, 2014, 04:05:08 PM
Hence why I switched back to the old interface.  That, and I couldn't figure out how to link from the new interface.

You copy and paste your URL bar. Did they mention they don't have a short URL feature? Because I looked around every button on that piece of crap and didn't find it.

If they ever force me to switch, I'm going to Bing. Seriously.
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 04:21:07 PM
Quote from: Brandon on February 26, 2014, 04:03:17 PM
So it has extra plating under the driver's seat saving your life in a car bombing?

ha, given how much RAM it takes, it had better.

I couldn't think of a more easily recognizable meme for "car bomb" than the scene in Casino.

I'm not one of those "it's new; therefore it must suck" luddites.  I actually enjoy the Westside Parkway in Bakersfield.  but I think "crashes without fail" should not be the hot new design trend of 2014.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on February 26, 2014, 04:28:32 PM
Quote from: agentsteel53 on February 26, 2014, 04:21:07 PM
Quote from: Brandon on February 26, 2014, 04:03:17 PM
So it has extra plating under the driver's seat saving your life in a car bombing?

ha, given how much RAM it takes, it had better.

I couldn't think of a more easily recognizable meme for "car bomb" than the scene in Casino.

I'm not one of those "it's new; therefore it must suck" luddites.  I actually enjoy the Westside Parkway in Bakersfield.  but I think "crashes without fail" should not be the hot new design trend of 2014.

Nor I, but the new interface is obviously a case of "amateur night".
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 05:02:23 PM
Quote from: Brandon on February 26, 2014, 04:28:32 PM
Nor I, but the new interface is obviously a case of "amateur night".

I don't even know if the interface is good or not.

MS Office 2007 (or is it 2010?  the new one.) is "amateur night".  (seriously, you broke "save as", you weirdos.)  the new Google Maps is the "shoot your customers when they walk into the dealership" level of marketing.
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on February 26, 2014, 05:07:38 PM
It's just like Flickr - they took a wonderful tool and made it into a fucking piece of shit.  I didn't mind paying for Flickr Pro and I didn't want to be switched to the buggy new interface.  Why do internet companies think they have to constantly change their products when there is nothing wrong with them in the first place?  Facebook, I'm looking at you.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brian556 on February 26, 2014, 05:15:33 PM
quote from Bugo:
QuoteIt's just like Flickr - they took a wonderful tool and made it into a fucking piece of shit.  I didn't mind paying for Flickr Pro and I didn't want to be switched to the buggy new interface.  Why do internet companies think they have to constantly change their products when there is nothing wrong with them in the first place?  Facebook, I'm looking at you.

Amen. If it ain't broke don't fix it.

This is just like those girls that change their hair color for no reason. They have a perfectly good hair color, and change it to something that looks like shit on them.

Also all these websites that were redesigned for tablet devices. They are now horrible, and have a lot less information. weather.com, nbcnews.com,ect
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on February 26, 2014, 05:42:02 PM
Quote from: bugo on February 26, 2014, 05:07:38 PM
It's just like Flickr - they took a wonderful tool and made it into a fucking piece of shit.  I didn't mind paying for Flickr Pro and I didn't want to be switched to the buggy new interface.  Why do internet companies think they have to constantly change their products when there is nothing wrong with them in the first place?  Facebook, I'm looking at you.
Its called progress!  Things must change if it gets a few years old, whether broken or not.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 26, 2014, 06:13:15 PM
Quote from: Brian556 on February 26, 2014, 05:15:33 PM
This is just like those girls that change their hair color for no reason. They have a perfectly good hair color, and change it to something that looks like shit on them.
Only if those new colors give you a headache. Otherwise who gives a fuck?
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 06:14:56 PM
Quote from: NE2 on February 26, 2014, 06:13:15 PM
Quote from: Brian556 on February 26, 2014, 05:15:33 PM
This is just like those girls that change their hair color for no reason. They have a perfectly good hair color, and change it to something that looks like shit on them.
Only if those new colors give you a headache. Otherwise who gives a fuck?

"looks like shit" and "gives a headache" are two entirely different classes of color.

that, or Brian really needs to go see a doctor.
Title: Re: Google Maps just fucking SUCKS now
Post by: on_wisconsin on February 26, 2014, 06:34:46 PM
No stability issues whatsoever here, BUT they got rid of the 45° aerial imagery, a nice feature (a Bird's Eye fighter) they had only added about a year ago. Because of that fact it tended to have the most up to date views as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 06:49:04 PM
Quote from: on_wisconsin on February 26, 2014, 06:34:46 PMa Bird's Eye fighter

I would love to have one of those.  I'm always constantly under attack by frozen peas.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr_Northside on February 26, 2014, 07:01:01 PM
I use it for work, and it's pretty unusable right now. 
Horrible.

I've been using Bing the last couple of days since.
Title: Re: Google Maps just fucking SUCKS now
Post by: SSOWorld on February 26, 2014, 07:04:54 PM
Never had major problems in Firefox.  Google Chrome, however, MAJOR FUCKING HANGUPS running any Google Maps!!! One would think google's own software would run it best...
Title: Re: Google Maps just fucking SUCKS now
Post by: Molandfreak on February 26, 2014, 07:32:26 PM
Where's the option for people who just hate how it looks/runs and don't have any browser trouble?

https://www.aaroads.com/forum/index.php?topic=11696.0

I don't want to know what the fastest mode of transportation is to get somewhere. I just want my goddamn driving directions, which google maps used to be about.
Title: Re: Google Maps just fucking SUCKS now
Post by: Molandfreak on February 26, 2014, 07:41:06 PM
Quote from: roadman65 on February 26, 2014, 05:42:02 PM
Quote from: bugo on February 26, 2014, 05:07:38 PM
It's just like Flickr - they took a wonderful tool and made it into a fucking piece of shit.  I didn't mind paying for Flickr Pro and I didn't want to be switched to the buggy new interface.  Why do internet companies think they have to constantly change their products when there is nothing wrong with them in the first place?  Facebook, I'm looking at you.
Its called progress!  Things must change if it gets a few years old, whether broken or not.
Screw progress if it inconveniences the user. I didn't ask for this lightbox crap in new flickr, and I didn't ask for non-driving directions to be a priority in google maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 26, 2014, 07:46:49 PM
Quote from: Molandfreak on February 26, 2014, 07:41:06 PM
Screw progress if it inconveniences the user. I didn't ask for this lightbox crap in new flickr, and I didn't ask for non-driving directions to be a priority in google maps.

lightbox is inscrutably hieroglyphic.  it took me quite a while to figure out that the standard right-click-and-save had been replaced by "..."

that's worse than VCR level of intuitive.

but hey, at least Flickr takes about a minute and a half to crash.  that's way better than Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: Thing 342 on February 26, 2014, 08:02:17 PM
Quote from: Zeffy on February 26, 2014, 04:01:52 PM
No problem. I'm not sure what the new Google Maps' problem is, but here's a fun fact: Memory usage of Firefox with Google Maps open and NO OTHER TABS:

604 MB!!!! THAT'S A SINGLE TAB!

Mine doesn't crash, but here's what usually ends up happening:
* It's always slow (always)
* City and town names disappear. Route shields disappear. All I fucking see is lines. And no matter what I do, until I refresh the page and rape my memory more, it won't fix itself.
* I get frustrated in Street View because it's so clunky

To be fair, Firefox is a notorious memory hog. Loading the new maps in Chrome took up just 80MB.
Title: Re: Google Maps just fucking SUCKS now
Post by: dgolub on February 26, 2014, 08:03:32 PM
I haven't had stalls or freezes, but I still like the old version better.
Title: Re: Google Maps just fucking SUCKS now
Post by: iwishiwascanadian on February 26, 2014, 08:36:19 PM
Has anyone switched back and taken the survey?
Title: Re: Google Maps just fucking SUCKS now
Post by: Alex on February 26, 2014, 09:15:46 PM
Not a big fan of the new Google maps either. Fortunately Internet Exploder still loads the old Google Maps for me, and I almost exclusively use that for Google Maps as it is.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 26, 2014, 09:22:10 PM
Quote from: Alex on February 26, 2014, 09:15:46 PM
Internet Exploder

BOOM!


Has anyone other than me and NE2 not autoswitched? (Maybe it's because we were both logged in at the time of the change.)
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 26, 2014, 09:31:32 PM
Quote from: 1 on February 26, 2014, 09:22:10 PM
Has anyone other than me and NE2 not autoswitched? (Maybe it's because we were both logged in at the time of the change.)
I never log into the Goog unless I need to edit my route log or mark a video as spam.

It's not the browser - I just loaded IE and it too has the old style. Maybe it's the OS (XP)?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 26, 2014, 09:35:37 PM
Quote from: NE2 on February 26, 2014, 09:31:32 PM
Quote from: 1 on February 26, 2014, 09:22:10 PM
Has anyone other than me and NE2 not autoswitched? (Maybe it's because we were both logged in at the time of the change.)
I never log into the Goog unless I need to edit my route log or mark a video as spam.

It's not the browser - I just loaded IE and it too has the old style. Maybe it's the OS (XP)?

Mac 10.6.8.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on February 26, 2014, 09:37:06 PM
Quote from: agentsteel53 on February 26, 2014, 03:37:35 PM
as far as hidden designations, and new truck routes, and what have you... again, I physically cannot get that far.  it gulps down about one gigabyte of RAM in 10-15 seconds, which makes Flickr look like an Atari 2600.

That is...interesting, certainly.

No problems on my end - for what it's worth, as of this writing, the new Google Maps, Twitter, and this AARoads forum thread (all in Chrome) are combining to use a mere 174 MB of RAM.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 26, 2014, 10:09:18 PM
I didn't auto-switch either.  Still on the old one, and still will be no matter how much they prompt me (though my old Google account I did switch for testing purposes).  In my case, I suspect that Linux/ATI not getting along with WebGL has something to do with not switching.  Any attempt to use the new version forces me onto the "lite" version.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 26, 2014, 10:26:07 PM
Hmmm. Everyone who's not getting switched go here: http://get.webgl.org/
I receive
QuoteHmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.

Does WebGL have a point other than making a computer slow EMACS-style?
Title: Re: Google Maps just fucking SUCKS now
Post by: ET21 on February 26, 2014, 10:49:04 PM
I had to look up about 50 cities to do a weather METAR coding map (METAR is coded weather data), and I had no issues whatsoever with it this afternoon.
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on February 26, 2014, 10:49:31 PM
Quote from: roadman65 on February 26, 2014, 05:42:02 PM
Quote from: bugo on February 26, 2014, 05:07:38 PM
It's just like Flickr - they took a wonderful tool and made it into a fucking piece of shit.  I didn't mind paying for Flickr Pro and I didn't want to be switched to the buggy new interface.  Why do internet companies think they have to constantly change their products when there is nothing wrong with them in the first place?  Facebook, I'm looking at you.
Its called progress!  Things must change if it gets a few years old, whether broken or not.

Hi Steve Gum!

(steveg1988)
Title: Re: Google Maps just fucking SUCKS now
Post by: bandit957 on February 26, 2014, 10:57:27 PM
You folks do realize you can switch back to "classic" Google Maps. I already did.
Title: Re: Google Maps just fucking SUCKS now
Post by: KEVIN_224 on February 26, 2014, 11:16:16 PM
they had me switched to the new version last week. I was able to switch back to the old version as mentioned above and it's fine. I use Mozilla Firefox here, in case that matters. :)
Title: Re: Google Maps just fucking SUCKS now
Post by: SteveG1988 on February 26, 2014, 11:21:46 PM
Switching back to the old version is easy, the new one sucks on my laptop, mostly due to lag issues
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on February 26, 2014, 11:41:47 PM
Quote from: iwishiwascanadian on February 26, 2014, 08:36:19 PM
Has anyone switched back and taken the survey?

I did!  I told them the new interface sucks big time and everything is slow as hell.  What used to take a single click now takes multiple clicks and getting the map to redraw because I panned or zoomed is painfully slow.  Will it make a difference?  Probably not.  I don't think Google gives a flying f*&k about those of us using traditional computers.  :angry:
Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on February 26, 2014, 11:50:30 PM
Not being able to remove labels (and street lines) on aerial view is annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on February 26, 2014, 11:55:04 PM
The new one kinda worked ok for me.  However, StreetView wouldn't work at all in the new version when using Firefox.  So, I'm back to the old one and staying there till I'm forced permanently to switch to the new one.
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on February 27, 2014, 12:08:11 AM
I want no part of that new damn Google Maps.

Had to print out directions to get somewhere, tried to figure out how to print the map...and couldn't find it at first, it used to be a print icon in the upper left hand corner.  So I go to the help and it says "use CTRL-P" to print.

Do WHAT now?

Excuse me, you just wasted a good ten-fifteen minutes of my time trying to figure out how to print out one of your map locations and you didn't even bother to put it on a menu or a control like the old version?

Worse, when it did print the map it didn't print it at the zoom level I selected, it printed it at the zoom level IT wanted.

Screw you, give me back my old Google Maps!  Got the old version back on my machine now and it works just fine, does what the hell I want it to.

(When I went to their help and read the comments on their print function, I wasn't the only one who wasn't happy with that turn of events, a lot of people were pissed, to say the least!)
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on February 27, 2014, 06:50:41 AM
Worked well two days ago, just spent a few extra moments figuring out Street View (the back arrow is a little more "intuitive" than zooming out multiple times), and trying to make those incessant menus (at the top left) stop dropping down when I'm nowhere near them.

Yesterday was sluggish, out of focus, occasionally crashed. Yup, 400-500MB of memory in a single tab. Unacceptable in a Chrome browser, on a laptop with plenty of memory and processing power.

I've had "output=classic" bookmarked since I opted for the trial version a few months back, and had enough after a few days. It still works fine, naturally...eventually, the day will probably come when it no longer understands that in the URL.

I'm hoping the Android app won't change any time soon. I need that in case of a travel emergency (or in case of a need to wander, either one).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 27, 2014, 10:45:47 AM
Quote from: NE2 on February 26, 2014, 10:26:07 PM
Hmmm. Everyone who's not getting switched go here: http://get.webgl.org/
I receive
QuoteHmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.

Does WebGL have a point other than making a computer slow EMACS-style?
Bringing video game quality hardware accelerated graphics to web browsers
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on February 27, 2014, 10:51:11 AM
Quote from: vdeane on February 27, 2014, 10:45:47 AM
Quote from: NE2 on February 26, 2014, 10:26:07 PM
Hmmm. Everyone who's not getting switched go here: http://get.webgl.org/
I receive
QuoteHmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.

Does WebGL have a point other than making a computer slow EMACS-style?
Bringing video game quality hardware accelerated graphics to web browsers

Why do I need that to view static web pages?  I'm not playing games online.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on February 27, 2014, 10:53:15 AM
As an aside, I'm getting damn sick and tired of web designers thinking they need to add all sorts of Flash and Shockwave shit to their pages just so we can view them.  They do nothing to enhance the viewing experience and do everything to crash.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on February 27, 2014, 11:01:26 AM
Quote from: Brandon on February 27, 2014, 10:53:15 AMAs an aside, I'm getting damn sick and tired of web designers thinking they need to add all sorts of Flash and Shockwave shit to their pages just so we can view them.  They do nothing to enhance the viewing experience and do everything to crash.

I hear you.  Flash also complicates automation.  I currently can't set up auto-download for Oregon DOT's electronic plans site (which fortunately is the only such site that now uses Flash) since it relies on binary postdata and the tools I use work well with ASCII postdata only.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on February 27, 2014, 11:16:30 AM
Quote from: Brandon on February 27, 2014, 10:53:15 AM
As an aside, I'm getting damn sick and tired of web designers thinking they need to add all sorts of Flash and Shockwave shit to their pages just so we can view them.  They do nothing to enhance the viewing experience and do everything to crash.

Flash can be especially annoying if you want to view a site on an iOS device but the site developer hasn't created a compatible version. For some reason iOS devices will not run Flash objects (YouTube has a separate non-Flash version for such devices).
Title: Re: Google Maps just fucking SUCKS now
Post by: dmr37 on February 27, 2014, 11:35:04 AM
I'm so mad I'm going to say F**k multiple times! And sh*t too!
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on February 27, 2014, 11:47:17 AM
I hate the new street view. It wont let me drag the guy onto the road anymore. Then it freezes on my computer. I have to search for everything. THe new Google Maps is way worse than the old version. BRING THE OLD VERSION BACK!!!
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 27, 2014, 12:11:14 PM
So I experienced that browser crashing on Firefox that everyone referred to...

I have a gaming laptop, and there is no reason that when Firefox hangs because of Google Maps, I have to watch as my computer slows down to a crawl until Firefox decides to end the process itself, because the task manager refuses to open.  :thumbdown:
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 27, 2014, 12:18:06 PM
so we are at 8/38 users report a crash before the ability to do anything useful.

that's still more than a quarter, which I believe is a significant enough minority to deem it a user-experience failure.

(unless people like crashing?  in which case I may have a Windows 95 install disc somewhere.)
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on February 27, 2014, 12:20:32 PM
Quote from: US 41 on February 27, 2014, 11:47:17 AM
I hate the new street view. It wont let me drag the guy onto the road anymore. Then it freezes on my computer. I have to search for everything. THe new Google Maps is way worse than the old version. BRING THE OLD VERSION BACK!!!

I don't necessarily mind not being able to drag the guy. Instead you click on him and then you just click on the road where you want to see the Street View image. That seems more straightforward than dragging (especially if I'm using my touchpad rather than the mouse!).

Don't mean to start a threadjack, but since there's been some discussion of browsers, this seems as good a place as any to raise the browser issue. I've used Firefox for years. There's no question it can sometimes be a bit of a memory hog and that its tendency to slow down seemingly at random, followed by the title bar briefly saying "Not Responding" (it goes away if you wait it out), can be damn annoying. (I have not yet downloaded Firefox 27 despite the browser's repeated pleas that I do so.) I hear people talk about Google Chrome as the main alternative. Can someone address what advantages and disadvantages it may have compared with Firefox? Certainly you hear a lot in the media about privacy issues with respect to Google in general, so I wonder to what extent Chrome might suffer from the same. I do not have an Android-based phone or tablet, so any advantages relating to that particular issue wouldn't be relevant. I run various Flash- and ad-blocking Firefox plugins and extensions and I'd want to be able to do something similar in any other browser I might try (in particular, I hate the way ESPN tries to force-load loud video when you open their site).

Thanks in advance. Moderators, if you think this belongs in "Off-Topic" obviously it's your call to move it; I simply thought it fit in with some of the discussion earlier in this thread, especially after someone suggested using Chrome.




Quote from: Zeffy on February 27, 2014, 12:11:14 PM
So I experienced that browser crashing on Firefox that everyone referred to...

I have a gaming laptop, and there is no reason that when Firefox hangs because of Google Maps, I have to watch as my computer slows down to a crawl until Firefox decides to end the process itself, because the task manager refuses to open.  :thumbdown:

My PC has been slow in general today. I'm trying to write a chapter of a publication I'm working on and it frustrates me to no end when there's a few-second delay after I hit a key before the character appears. Almost impossible to type that way. I think I'll run virus and malware scans when I break for lunch. I've only tried to run Google Maps once so far (in response to the post from US 41 quoted above), although presently I have open Firefox with five browser tabs, three MS Word windows, Mozilla Thunderbird for e-mail, iTunes, and two file manager windows. I have 16 GB of RAM and a 2.9-GHz quad-core processor, but some days I just want to hurl the thing out the window.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 27, 2014, 12:29:30 PM
Even with all the hate for Internet Explorer, I will say that the newest version is not as bad as people think. In fact, I like it. A lot. Also, it has old Google Maps saved into whatever preferences Google uses so I don't have to worry about the impending browser crashes.

Chrome? Yeah I like it, but the new Google Maps is a steaming pile of shit on Chrome for me. Firefox can't take the fail anymore and quits. IE enjoys the old Google Maps, and so do I.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on February 27, 2014, 12:35:44 PM
The following just appeared on Twitter from the Washington Post's lead transportation reporter:

Quote
Robert Thomson ‏@RT_Thomson 3m

Happy I just figured out how to restore Classic version of Google Maps. Had issues with Directions & other commonly used tools.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on February 27, 2014, 12:52:27 PM
Quote from: agentsteel53 on February 27, 2014, 12:18:06 PM
so we are at 8/38 users report a crash before the ability to do anything useful.

that's still more than a quarter, which I believe is a significant enough minority to deem it a user-experience failure.

(unless people like crashing?  in which case I may have a Windows 95 install disc somewhere.)

Even if the New And Improved Google Maps doesn't crash (which it did not for me on Firefox), it is still a steaming pile of rat dung.  So that makes 29/39 right now who either don't like it, or it crashes for them.  That's over 74%!  It is distinctly a user-experience failure.
Title: Re: Google Maps just fucking SUCKS now
Post by: BrianP on February 27, 2014, 01:30:54 PM
Hey all

The best thing to do for crashing problems would be to update your video card drivers if they are not the latest version.  In general WebGL crashes are from faulty drivers.  They even list up to date drivers as a system requirement for the new maps:
https://support.google.com/maps/answer/3096703?ctx=c2n_req1

Also Firefox blocks the use of some drivers that are known to be faulty to avoid crashes.  So in that case you don't get hardware acceleration so it will be slower.  But I would guess they can't stay on top of every bad video card/driver combination.  Updating the drivers is the most you can there as well.  Well besides getting a new video card. 

I also hate that streetview uses flash.  But I haven't used the new version so I haven't voted in the poll.  I still get the old version in Firefox.  I guess that since in general i'm not signed into Google (no GMail).  But from what I've seen on the web the new version does not use Flash. :D

Also only IE 11 has WebGL so older versions of IE can only use the old version of Google maps. So the old version shouldn't be going anywhere anytime soon.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on February 27, 2014, 02:47:32 PM
The AARoads Forum, specifically this thread, earns a mention in the Washington Post!

Map rage: Navigating Google's revised way-finding system (http://www.washingtonpost.com/blogs/dr-gridlock/wp/2014/02/27/map-rage-navigating-googles-revised-way-finding-system/) by Robert Thomson (Dr. Gridlock)

QuoteIt wasn't broken, Google. Why did you have to fix it?

The last time I wrote about Google Maps was to praise the way-finding system, comparing it favorably to Apple's much-derided mapping system.

That was then. This is now: The version of Google Maps now showing up on my desktop PC is fuzzy and slow. And those are its best qualities.

....

This isn't just an old guy grumble. Our frequent commenter 1995hoo pointed out a conversation about the maps on the AARoads forum (https://www.aaroads.com/forum/index.php?topic=11718.0). The commenter included a warning about the language I would encounter there from travelers who are reacting as I did.

....


I had sent him a tweet, in reply to his prior one that I quoted earlier in this thread, suggesting he check out this thread.
Title: Re: Google Maps just fucking SUCKS now
Post by: SSOWorld on February 27, 2014, 07:56:05 PM
Those that get computers with 16 GB Of RAM don't need it unless they get 64-bit compatible programs.  Most applications use only 3.2 GB being 32-bit apps
Title: Re: Google Maps just fucking SUCKS now
Post by: SSOWorld on February 27, 2014, 07:57:38 PM
Those that get computers with 16 GB Of RAM don't need it unless they get 64-bit compatible programs.  Most applications use only 3.2 GB being 32-bit apps  :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: KEK Inc. on February 27, 2014, 08:16:19 PM
I wouldn't mind the new one if they didn't move the legend and controls to the opposite corner.  It's very frustrating. 

I have a decent graphics card to run it and enough RAM for it not to crash, but I really don't like the flipped interface.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on February 27, 2014, 09:33:32 PM
It works fine for me. I use Firefox in Linux with an Nvidia GPU. When it first came out, it was painfully slow, but now the performance for everything but street view is as good as the classic maps. Not perfect, but usable. In Chrome, it's silky smooth (even street view). The new interface has a few annoying quirks, but overall both are equally fine for me.

For you people with crashes: are you still running freaking XP or something? Either way, update your GPU drivers, because it's likely WebGL causing it to fail.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 27, 2014, 10:17:38 PM
I have the latest version of my graphic drivers for both my integrated and dedicated video cards. The new Google Maps causes more frustration than I can deal with honestly.
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on February 27, 2014, 10:30:51 PM
I haven't had any crashes or other failures of the program, although they did remove some helpful things. No more date of image in street view. No more linking directly to street view. No more maintaining directions when entering street view. These are annoyances but not deal breakers for me. I haven't switched back since I know I won't be able to do that permanently, and I'm not the type to fight a fight I know I can't win.


As for the question of "why fix it if it ain't broke?", it seems to me that the new interface is designed to be more readily usable by people on touch screen devices (which explains why they did away with right clicking). Given the growing number of users that are working with tablets rather than traditional PCs, this is not a trivial matter and I do not fault Google for seeking to address it. It sounds, at least, like the current release addresses a lot of issues which were brought up during the beta stage... although it obviously is still far from perfect.

The crashing is obviously the biggest problem, although if it is a driver issue as has been suggested, then that is not something Google can fix on their end short of opting to not use WebGL.
Title: Re: Google Maps just fucking SUCKS now
Post by: english si on February 27, 2014, 11:26:08 PM
Quote from: Duke87 on June 11, 1970, 02:59:42 AMAs for the question of "why fix it if it ain't broke?", it seems to me that the new interface is designed to be more readily usable by people on touch screen devices (which explains why they did away with right clicking). Given the growing number of users that are working with tablets rather than traditional PCs, this is not a trivial matter and I do not fault Google for seeking to address it. It sounds, at least, like the current release addresses a lot of issues which were brought up during the beta stage... although it obviously is still far from perfect.
1) this wasn't a fix (though this travesty is a lot better than the beta,which was nearly stop using the plethora of Google products that I use bad...) 'Tisn't don't fix if it ain't broke, but don't break if its fine!

2) tablets/phones/etc are easy to deal with. As Google's rival's once said "there's an app for that". OK, I avoid using the bundled Google Maps apps (Maps and Navigation) on this android tablet as they have the annoying habit of showing me where I am,not where the person who posted the link wanted me to see*. And what ever happened to m.website.alan redirects for mobile devices?

*I set my location on classic maps, once it forced me to have one, to UK as I rarely need a map of where I am and I can zoom in easily. New maps, even with vague location data seems to zoom much further in, meaning that my first action when forced to switch is typically going to be a zoom out, followed by a zoom in, rather than just a zoom in. If I do need something in my area, I can use the search facility. If I'm browsing, or don't want to have to fight new maps when going into street view, then I don't/won't use search terms.
Title: Re: Google Maps just fucking SUCKS now
Post by: SD Mapman on February 28, 2014, 12:34:14 AM
I don't know. Works fine for me...
What I like about the new version is the 3d satellite images they have in some places (Rapid City, SD to name one). It's mesmerizing.
Title: Re: Google Maps just fucking SUCKS now
Post by: cpzilliacus on February 28, 2014, 07:17:52 AM
Quote from: 1995hoo on February 27, 2014, 02:47:32 PM
The AARoads Forum, specifically this thread, earns a mention in the Washington Post!

Map rage: Navigating Google's revised way-finding system (http://www.washingtonpost.com/blogs/dr-gridlock/wp/2014/02/27/map-rage-navigating-googles-revised-way-finding-system/) by Robert Thomson (Dr. Gridlock)

Nicely done!
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on February 28, 2014, 11:44:49 AM
Wow I thought I was the only one! I'm very angry that they removed the distance measurement tool! I used that all the time! I also don't understand why google still hasnt put county boundaries on the maps (townships would be nice too)! Also mapmaker has always been complete shit!

GT-N5110

Title: Re: Google Maps just fucking SUCKS now
Post by: jbnv on February 28, 2014, 12:03:01 PM
I'm not a fan of Google Maps to begin with, because Google. I avoid using Google products for several reasons--their politics, their collecting of data, their cooperation with tyrannical governments, etc. I actually returned a Nest thermostat without installing it because Google bought Nest. However, nobody else has Street View, and Google's app is simply better than Mapquest's in several ways. Sigh.

Now as for the new version, I find it to be slower. Street View is more of a pain to work with, and doesn't provide the zoom any more. Also, I can't find the link generator.
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on February 28, 2014, 01:11:50 PM
So after resetting my default to the classic Google Maps, I filled out the survey as well.

Today, I received this in my email:
Quote
Hello,

Growing up, directions were simple–in my hometown of Lawrence, Kansas, the roads conveniently run north to south and east to west (and there's only one hill to block the view). For more than a decade, my team and I have been working to make it just as easy for you to see the world and get where you're going.

I'd like to thank you for trying out the new Google Maps and helping us make it better. With your great feedback, now it's even easier to decide where to go, how to get there, and what to explore in the area (with Pegman's help if needed). Now we're ready for the rest of the world to try it out.

Even though the new Google Maps has launched, we're just getting started. There will be some things we don't get quite right, so please continue to let us know how we're doing. I look forward to mapping together for many more years to come.

–Brian McClendon, VP of Google Maps

I wonder if it was triggered by the Washington Post article. If not, Google's form email is very slow in sending, as I filled out the survey a few weeks ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on February 28, 2014, 01:18:43 PM
Quote from: Duke87 on February 27, 2014, 10:30:51 PM
As for the question of "why fix it if it ain't broke?", it seems to me that the new interface is designed to be more readily usable by people on touch screen devices (which explains why they did away with right clicking). Given the growing number of users that are working with tablets rather than traditional PCs, this is not a trivial matter and I do not fault Google for seeking to address it.

Your argument doesn't make any sense!  Tablet users (both Android and iOS) have their OWN Google Maps App that are either pre-installed (Android) or can be downloaded from the app store (iOS).

For the most part, the only people going to maps.google.com using a web browser are traditional PC users who are not using a touch interface unless you're running Windows 8 which seems to be a total flop and accounts for maybe 10% of all traditional computer users.  If the change was prompted because of Windows 8, then I'll fault both Google AND Microsoft!  :angry:
Title: Re: Google Maps just fucking SUCKS now
Post by: agentsteel53 on February 28, 2014, 01:31:15 PM
well, I sure as shit didn't get a form email.  apparently my writing "hey, you guys are cocks" on some random forum isn't enough to get their attention.
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on February 28, 2014, 01:35:24 PM
They really need a customer service hotline.

GT-N5110

Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 28, 2014, 02:00:03 PM
Quote from: DaBigE on February 28, 2014, 01:11:50 PM
So after resetting my default to the classic Google Maps, I filled out the survey as well.

Today, I received this in my email:
Quote
Hello,

Growing up, directions were simple–in my hometown of Lawrence, Kansas, the roads conveniently run north to south and east to west (and there's only one hill to block the view). For more than a decade, my team and I have been working to make it just as easy for you to see the world and get where you're going.

I'd like to thank you for trying out the new Google Maps and helping us make it better. With your great feedback, now it's even easier to decide where to go, how to get there, and what to explore in the area (with Pegman's help if needed). Now we're ready for the rest of the world to try it out.

Even though the new Google Maps has launched, we're just getting started. There will be some things we don't get quite right, so please continue to let us know how we're doing. I look forward to mapping together for many more years to come.

–Brian McClendon, VP of Google Maps

I wonder if it was triggered by the Washington Post article. If not, Google's form email is very slow in sending, as I filled out the survey a few weeks ago.

I never filled out a survey, yet I got this email as well. Maybe I should go fill one out...
Quote from: myosh_tino on February 28, 2014, 01:18:43 PM

For the most part, the only people going to maps.google.com using a web browser are traditional PC users who are not using a touch interface unless you're running Windows 8 which seems to be a total flop and accounts for maybe 10% of all traditional computer users.  If the change was prompted because of Windows 8, then I'll fault both Google AND Microsoft!  :angry:

Where do people get the hate for Windows 8? I never disliked it, even before 8.1. I have had virtually no issues with Windows 8/8.1.
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on March 04, 2014, 01:49:32 PM
My biggest complaint is with the mobile app. My android phone was forced to update, and that included Google Maps.

The problem I have with the setup is this: If you get a routing, and then follow the routing, you can't drop a pin somewhere on the map. That means you have to X out of the routing, which usually takes you back to where you started or zoom out all the way. This is decidedly inconvenient.

The improvements are nice. But this one thing makes it a horrible.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on March 04, 2014, 03:13:27 PM
One thing, though, I noticed that if you drag the yellow man down to the map for Street View you MUST hit the target!  If you miss the blue line, the map will suddenly zoom out.
Title: Re: Google Maps just fucking SUCKS now
Post by: wphiii on March 04, 2014, 05:28:00 PM
No slowdown issues for me, but some pretty irritating things going on that I've found so far:

- Toggling "modes" (to terrain, traffic, etc) erases anything that's been pinpointed as a result of a previous search.
- You can't get directions while in terrain mode (or enter terrain mode while a directions route is being displayed).
- The drop-down list of things you've recently searched for/directions you've recently asked for seems to be gone completely. I learned this the hard way when I thought I was just temporarily "turning off" a pretty complicated set of directions, only to realize that there didn't appear to be a way to turn them back on.
- Forcing me to see what flickr accounts and panoramas are nearby whenever I enter street view is pretty annoying.
- I swear there are way fewer directions segments + manual alterations to routes permitted in this new version.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on March 04, 2014, 05:48:36 PM
Windows 8 discussion split to https://www.aaroads.com/forum/index.php?topic=11761.0 .
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on March 04, 2014, 08:44:10 PM
Quote from: Zeffy on February 28, 2014, 02:00:03 PM
Quote from: DaBigE on February 28, 2014, 01:11:50 PM
So after resetting my default to the classic Google Maps, I filled out the survey as well.

Today, I received this in my email:
Quote
Hello,

Growing up, directions were simple–in my hometown of Lawrence, Kansas, the roads conveniently run north to south and east to west (and there's only one hill to block the view). For more than a decade, my team and I have been working to make it just as easy for you to see the world and get where you're going.

I'd like to thank you for trying out the new Google Maps and helping us make it better. With your great feedback, now it's even easier to decide where to go, how to get there, and what to explore in the area (with Pegman's help if needed). Now we're ready for the rest of the world to try it out.

Even though the new Google Maps has launched, we're just getting started. There will be some things we don't get quite right, so please continue to let us know how we're doing. I look forward to mapping together for many more years to come.

–Brian McClendon, VP of Google Maps

I wonder if it was triggered by the Washington Post article. If not, Google's form email is very slow in sending, as I filled out the survey a few weeks ago.

I never filled out a survey, yet I got this email as well. Maybe I should go fill one out...
Quote from: myosh_tino on February 28, 2014, 01:18:43 PM

For the most part, the only people going to maps.google.com using a web browser are traditional PC users who are not using a touch interface unless you're running Windows 8 which seems to be a total flop and accounts for maybe 10% of all traditional computer users.  If the change was prompted because of Windows 8, then I'll fault both Google AND Microsoft!  :angry:

Where do people get the hate for Windows 8? I never disliked it, even before 8.1. I have had virtually no issues with Windows 8/8.1.

The same reason everyone hated ME and Vista:  because they suck.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on March 05, 2014, 12:18:40 AM
Quote from: agentsteel53 on February 27, 2014, 12:18:06 PM
(unless people like crashing?  in which case I may have a Windows 95 install disc somewhere.)

I'll see yer Windows 95 and raise you Windows ME...
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on March 05, 2014, 08:13:58 AM
I never had much issue with ME, it just didn't seem to do much that 98 couldn't do, except crash somewhat less (perhaps I was the lucky one). XP make it seem a lot more archaic, that's pretty much a given...
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on March 12, 2014, 04:17:57 PM
I never had very many problems with Vista, but I am happier with Windows 7. My wife's laptop runs Vista and it's starting to get very slow, but it's also seven years old this May.

Returning to Google Maps: Earlier this afternoon I downloaded (and am using as I type this post) a 64-bit browser called Waterfox, which is based on the current version of Firefox. I did some research before downloading and found generally positive reviews. So far it is considerably faster than Firefox for most browsing and I have not encountered the annoying problem where Firefox just randomly freezes up and says "(Not Responding)" for a minute or two, then resumes working. I find the new Google Maps to be faster in 64-bit Waterfox than it is in 32-bit Firefox, but it's still not as fast as the old Google Maps was in 32-bit Firefox (and I have not yet tried using the old interface in the 64-bit browser).
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on March 13, 2014, 01:41:49 AM
Occasionally I do have performance problems with it (usually in Firefox, but still usable in most cases; it usually (but not always) works better on Chrome though), but can the old Google Maps do this? (Actually, all 6 of these screenshots were taken in Firefox, so it still gets the job done)

Link to album (6 1080p images): http://imgur.com/a/XXCwf#0

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F6SzSnHC.jpg&hash=a8455663828607f4e9416f970f716746d6a84cfa)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FgyUDz7T.jpg&hash=21a77ff19bddf6d96059d4a8c69964c530b12989)

I don't want to embed any more in here but you get the point, pretty cool feature how it manages to make everything into 3D (even individual trees!) and add proper textures to everything, I was shocked when I found out how to do this! Oh, just click the tilt view button twice near the bottom right while in Earth mode.


(I realize the desktop Google Earth client might be able to do this now; it was never this good in the past though, but I haven't used it in at least a year due to bugginess).
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 13, 2014, 02:10:33 AM
Quote from: doorknob60 on March 13, 2014, 01:41:49 AM
Occasionally I do have performance problems with it (usually in Firefox, but still usable in most cases; it usually (but not always) works better on Chrome though), but can the old Google Maps do this?
So it's a whore that looks great but can't perform.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on March 13, 2014, 04:36:53 PM
I think the old maps had something called the "Google Earth Plugin" that could do something like that.  You had to install it separately though.
Title: Re: Google Maps just fucking SUCKS now
Post by: Occidental Tourist on March 13, 2014, 06:39:29 PM
Quote from: roadman65 on March 04, 2014, 03:13:27 PM
One thing, though, I noticed that if you drag the yellow man down to the map for Street View you MUST hit the target!  If you miss the blue line, the map will suddenly zoom out.

And good luck trying to follow a road for any distance on Street View.  The old version had set arrows in the pavement to advance or retreat on a route.  The new version does not.  Go over a complex viaduct in the new version and you'll find yourself in an underpass with no way out and no way to advance.  Here's a good example:  Try to cross the Zakim Bunker Hill Memorial Bridge on Street View (https://www.google.com/maps/place/North+Point+Park/@42.371379,-71.066735,3a,75y,128.95h,87.27t/data=!3m4!1e1!3m2!1sz1UZs3sOmbn7kPaRE6uy2A!2e0!4m7!1m4!3m3!1s0x89e3652d0d3d311b:0x787cbf240162e8a0!2sBoston,+MA!3b1!3m1!1s0x0:0xdce6ae09ee27ad73).  I dare you.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on March 13, 2014, 07:08:02 PM
Quote from: Occidental Tourist on March 13, 2014, 06:39:29 PM
Quote from: roadman65 on March 04, 2014, 03:13:27 PM
One thing, though, I noticed that if you drag the yellow man down to the map for Street View you MUST hit the target!  If you miss the blue line, the map will suddenly zoom out.

And good luck trying to follow a road for any distance on Street View.  The old version had set arrows in the pavement to advance or retreat on a route.  The new version does not.  Go over a complex viaduct in the new version and you'll find yourself in an underpass with no way out and no way to advance.  Here's a good example:  Try to cross the Zakim Bunker Hill Memorial Bridge on Street View (https://www.google.com/maps/place/North+Point+Park/@42.371379,-71.066735,3a,75y,128.95h,87.27t/data=!3m4!1e1!3m2!1sz1UZs3sOmbn7kPaRE6uy2A!2e0!4m7!1m4!3m3!1s0x89e3652d0d3d311b:0x787cbf240162e8a0!2sBoston,+MA!3b1!3m1!1s0x0:0xdce6ae09ee27ad73).  I dare you.

Click the overpass when  that happens. Sometimes you'll return.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on March 14, 2014, 12:38:18 AM
Quote from: vdeane on March 13, 2014, 04:36:53 PM
I think the old maps had something called the "Google Earth Plugin" that could do something like that.  You had to install it separately though.

Never worked on Linux though, so irrelevant to me. Either way, it's not so much the fact that it's in the browser that was impressive (although it is impressive), but the fact that every single building and even tree is now rendered in 3D. It was not like this before, even in the standalone Earth application (last time I checked). Plus. the draw distance is incredible.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brian556 on March 14, 2014, 12:50:02 AM
Quote from NE2:
QuoteSo it's a whore that looks great but can't perform

With whores it's usually the other way around. Just bring a paper bag and enjoy the ride.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on March 14, 2014, 12:34:24 PM
Okay, so I decided to see if Google Maps new version has gotten any better. So, I made a new private window in Firefox, closed my one populated with tabs (to increase performance), and set out to the Google Maps homepage. It asked if I wanted to try the new maps, I gulped and clicked yes. After waiting for a browser crash, nothing happened - I carefully zoomed in - expecting to take 20sec or more to load the area of New Jersey I was looking over - to my surprise - it loaded fast. About two seconds. Impressed, I toggled Earth view and flew on over to Trenton and tilted the view. Apparently, Trenton is a flat place where buildings don't use a Z axis:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1300.photobucket.com%2Falbums%2Fag88%2FZeffyboy%2FNewGoogleMaps-Trenton_zpsb20931ae.png&hash=5befb0353d94bff4d68ed32c04151d0b6cf85082)
Yay, Trenton is flat. Thanks Google for showing how great the capital really isn't!

So, disappointed with Trenton, I went to a slightly worse place on the Delaware River: Camden. I thought that if Trenton was flat, then Camden would be even worse! Annnnnd I was wrong:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1300.photobucket.com%2Falbums%2Fag88%2FZeffyboy%2FSigns%2FNewGoogleMaps-Camden_zps87eb2d47.png&hash=724e1e3a90662f02b2c2efa24082ff64d5e56508)
I guess Camden is doing better than Trenton nowadays. Well then.

So, continuing to see which cities Google Maps favored, I went to the bigger players in New Jersey: Newark. I can say that I honestly expected to see 3d buildings, so when I did, I wasn't left pissed:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1300.photobucket.com%2Falbums%2Fag88%2FZeffyboy%2FSigns%2FNewGoogleMaps-Newark_zpsc3bc7a58.png&hash=75c3c9bed5412d2b2a84b9a0320b9437fbe16441)
One of the more urban areas in New Jersey, with plenty of city like buildings. Still wouldn't live there.

Finally before I ended my tour 3d building hunting, I flew to the only place in New Jersey where you can find real skyscrapers: Jersey City. I flew down to the coast near the Hudson River, and was delighted to see the pretty buildings lining the waterfront in downtown Jersey City:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1300.photobucket.com%2Falbums%2Fag88%2FZeffyboy%2FSigns%2FNewGoogleMaps-JC_zps84f4e312.png&hash=a50719468a90a2e386d9f192506791e4fc3f4666)
Yay Skyscrapers! Wait, look in the background. It's Manhattan. Reminds me of the Super Bowl Program that featured Manhattan while leaving a small view of Jersey City in the background.

So, apparently, Google Maps did something right, because the new version hasn't done anything stupid yet. Or maybe it's the ridiculous amount of tabs I have open in my main Firefox window. Although when I did this same thing before with the private window, it was just as bad as if I did have my tabs open. Even with these improvements, I'm still going to continue using old maps. The 3d views and such is cool, but, meh, I don't feel like closing tabs and opening a private window just to use Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on March 14, 2014, 03:30:52 PM
Quote from: doorknob60 on March 14, 2014, 12:38:18 AM
Quote from: vdeane on March 13, 2014, 04:36:53 PM
I think the old maps had something called the "Google Earth Plugin" that could do something like that.  You had to install it separately though.

Never worked on Linux though, so irrelevant to me. Either way, it's not so much the fact that it's in the browser that was impressive (although it is impressive), but the fact that every single building and even tree is now rendered in 3D. It was not like this before, even in the standalone Earth application (last time I checked). Plus. the draw distance is incredible.
Unfortunately, most Linux users can't use the new 3D Earth View either due to the crappy video drivers inherent to the platform.  Even ATI's proprietary drivers won't do WebGL on Linux, so it's a moot point.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on March 14, 2014, 03:35:31 PM
Quote from: vdeane on March 14, 2014, 03:30:52 PM
Quote from: doorknob60 on March 14, 2014, 12:38:18 AM
Quote from: vdeane on March 13, 2014, 04:36:53 PM
I think the old maps had something called the "Google Earth Plugin" that could do something like that.  You had to install it separately though.

Never worked on Linux though, so irrelevant to me. Either way, it's not so much the fact that it's in the browser that was impressive (although it is impressive), but the fact that every single building and even tree is now rendered in 3D. It was not like this before, even in the standalone Earth application (last time I checked). Plus. the draw distance is incredible.
Unfortunately, most Linux users can't use the new 3D Earth View either due to the crappy video drivers inherent to the platform.  Even ATI's proprietary drivers won't do WebGL on Linux, so it's a moot point.

Yeah I haven't tried it on my laptop with AMD graphics, but it works great with the Nvidia proprietary drivers. I'll try it on my laptop sometime and report back.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on March 14, 2014, 03:54:44 PM
I've heard the Nvidia/Linux situation has improved a lot in the past couple years.  Too bad AMD/ATI is so ubiquitous these days.  I'll have to see what happens with my laptop and a live CD the next time I'm bored and can switch the ATI card for the built-in Intel one in BIOS.  My next desktop will probably have integrated graphics just to avoid the situation.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on March 20, 2014, 04:45:54 PM
I just tried it out on my laptop, running Ubuntu 12.04. It has a Radeon HD 6520G GPU. I'm using the open source (default drivers, not the proprietary Catalyst ones. In both Firefox and Chrome, it defaulted to Lite mode and worked. I forced WebGL on Firefox, and it seems to work fine (albeit slow, but the hardware isn't exactly fast). On Chrome, it wouldn't let me activate WebGL (my GPU may be blacklisted by Chrome, there might be a way to fix that), but I got no browser crashes, and Maps still works in both by default.

EDIT: I enabled the ignore GPU blacklist flag in Chrome in about:flags, and then the WebGL version worked, and at a very usable framerate (probably in the 20-30 range, even in Earth 3D).
Title: Re: Google Maps just fucking SUCKS now
Post by: Alex on March 21, 2014, 12:49:54 AM
So my IE now prompts me to try the new google maps and to login with a google account while also not providing any option for the classic maps. I use IE with cookies turned off and prefer it as my map browser while using Chrome for everything else. Talk about a PITA.
Title: Re: Google Maps just fucking SUCKS now
Post by: BrianP on March 21, 2014, 10:39:24 AM
Quote from: Alex on March 21, 2014, 12:49:54 AM
So my IE now prompts me to try the new google maps and to login with a google account while also not providing any option for the classic maps. I use IE with cookies turned off and prefer it as my map browser while using Chrome for everything else. Talk about a PITA.
Yeah I hit that last night in Firefox.  And no google I don't want to login.  Let me use the maps - I don't care which version just let me use something.   :angry:
Title: Re: Google Maps just fucking SUCKS now
Post by: algorerhythms on March 23, 2014, 05:51:21 PM
Apparently the new Google Maps allows you to zoom in on a city by clicking its name, and it shows you the city limits when it zooms in. So I tried it on a few cities and stumbled on this (https://www.google.com/maps/place/Owasso,+OK/@36.292856,-95.8048779,12z/data=!3m1!4b1!4m2!3m1!1s0x87b6effc128d6983:0xa1a8eef11b4b92b0). I'm wondering whether this is a Google Maps slipup, or if Owasso actually did annex a bunch of roads in the surrounding area, but none of the land attached to the roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on March 23, 2014, 06:20:40 PM
Quote from: algorerhythms on March 23, 2014, 05:51:21 PMApparently the new Google Maps allows you to zoom in on a city by clicking its name, and it shows you the city limits when it zooms in. So I tried it on a few cities and stumbled on this (https://www.google.com/maps/place/Owasso,+OK/@36.292856,-95.8048779,12z/data=!3m1!4b1!4m2!3m1!1s0x87b6effc128d6983:0xa1a8eef11b4b92b0). I'm wondering whether this is a Google Maps slipup, or if Owasso actually did annex a bunch of roads in the surrounding area, but none of the land attached to the roads.

This isn't a new feature--the old Google Maps showed you jurisdictional boundaries (states, counties, cities) too.  What Google Maps shows for Owasso is a classic deployment of the encircling-annexation tactic (which gained notoriety in Arizona when it was used by several municipalities in the Phoenix area to carve out parcels of rural land which their neighbors would then not be able to annex).
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 23, 2014, 06:49:20 PM
Houston may be the largest city to do this. Peep it.
Title: Re: Google Maps just fucking SUCKS now
Post by: algorerhythms on March 23, 2014, 06:54:16 PM
Maybe I'm not thinking it through well enough, but if they don't want other cities to annex the land, couldn't they just annex it themselves first? And I'm guessing the cities aren't allowed to have non-contiguous sections.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 23, 2014, 07:04:16 PM
Property owners usually have to agree to be annexed.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on March 24, 2014, 09:38:04 AM
Quote from: J N Winkler on March 23, 2014, 06:20:40 PM
Quote from: algorerhythms on March 23, 2014, 05:51:21 PMApparently the new Google Maps allows you to zoom in on a city by clicking its name, and it shows you the city limits when it zooms in. So I tried it on a few cities and stumbled on this (https://www.google.com/maps/place/Owasso,+OK/@36.292856,-95.8048779,12z/data=!3m1!4b1!4m2!3m1!1s0x87b6effc128d6983:0xa1a8eef11b4b92b0). I'm wondering whether this is a Google Maps slipup, or if Owasso actually did annex a bunch of roads in the surrounding area, but none of the land attached to the roads.

This isn't a new feature--the old Google Maps showed you jurisdictional boundaries (states, counties, cities) too.  What Google Maps shows for Owasso is a classic deployment of the encircling-annexation tactic (which gained notoriety in Arizona when it was used by several municipalities in the Phoenix area to carve out parcels of rural land which their neighbors would then not be able to annex).

Which is considered challengeable in Illinois.  Municipalities have tried this in Illinois only to be shot down by their neighbors in court.  So now the tactic is to annex the road plus properties along the road to be annexed, even if it remains agricultural for the foreseeable future.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on March 24, 2014, 09:43:39 AM
Quote from: NE2 on March 23, 2014, 07:04:16 PM
Property owners usually have to agree to be annexed.

In most cases, yes.  Some states allow for forcible annexation of smaller properties.  Illinois does, as well as a few other interesting ways of annexation:

http://www.ilga.gov/legislation/ilcs/fulltext.asp?DocName=006500050K7-1-1
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on March 24, 2014, 10:49:03 AM
Quote from: Brandon on March 24, 2014, 09:38:04 AMWhich is considered challengeable in Illinois.  Municipalities have tried this in Illinois only to be shot down by their neighbors in court.  So now the tactic is to annex the road plus properties along the road to be annexed, even if it remains agricultural for the foreseeable future.

It doesn't work in Arizona anymore either, since the annexation statutes were reformed to curb the worst abuses.  (My reference is Carol E. Heim, Border Wars:  Tax Revenues, Annexation, and Urban Growth in Phoenix, published by the UMass Amherst economics department as a working paper.)  What I have called "encircling annexation" is also called "strip annexation" when the purpose is to isolate an area of unincorporated land--a "county island"--so that neighboring municipalities cannot annex it.  In 1980, Arizona banned strip annexation by imposing a minimum width requirement of 200 feet (exclusive of highway width) and requiring that the annexed area be no more than twice as long as it was wide.  In 1986, it also required the consent of half of the landowners in the annexed area, not just a group of such landowners representing half the assessed property value, and it also required a public hearing to be held.  The 1980 measure came after a number of annexations in the 1970's created county islands ranging in size up to 86 square miles.

But, as we all know, annexation law varies from state to state.  As long as abuses are not too flagrant, many states refrain from restricting annexation in order to keep the number of municipalities in a given area down, and thus limit the opportunities for coordination failures in land-use planning.  The Phoenix area has only 24 incorporated municipalities, for example, while Chicago has 265.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 24, 2014, 11:59:35 AM
Does Kansas allow you to annex only a highway ROW? Would I be able to create a town, annex all of a state highway, and force KDOT to turn over maintenance to me?
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on March 24, 2014, 01:10:08 PM
Quote from: NE2 on March 24, 2014, 11:59:35 AMDoes Kansas allow you to annex only a highway ROW? Would I be able to create a town, annex all of a state highway, and force KDOT to turn over maintenance to me?

I haven't done a detailed study of what statutes and court rulings allow in terms of annexation in Kansas.  However, there is abundant precedent for annexing land other than a highway right-of-way (US 54 and 119th Street West near west Wichita being cases in point), and there is apparently precedent for noncontiguous land (e.g. the proposed Furley landfill site) being annexed if it is to be used for a defined municipal purpose.

In regard to your last question:

*  You can create a town if you have the necessary number of people (300, basically) for at least a third-class city.

*  Whether you can annex a state highway depends on whether strip annexation is allowed under Kansas law.  I don't know if it is, but a casual inspection of the Kansas City area (where one would expect competitive annexation to be at its fiercest) turns up no examples of it.  The closest approximations are pene-enclaves belonging to Overland Park where the isthmus connection is the width of a street.  I don't know if strip annexation Arizona-style has been tried in Kansas.

*  If you annex a state highway, I am not sure you can force KDOT to relinquish it, though I think you remove the ability of the KDOT secretary to exercise certain powers which he or she enjoys in respect of state highways but not city connecting links, including the power to relocate to a new alignment.  Again, I am not sure annexation for this purpose has been tried.

Edit:  It appears that strip annexation is not generally allowed under Kansas law owing to certain perimeter requirements under KSA § 12-520 (http://kansasstatutes.lesterama.org/Chapter_12/Article_5/12-520.html):

*  Annexation of up to 21 acres allowed if two-thirds of the boundary line of the annexed land adjoins the city boundary.

*  Annexation of up to 21 acres allowed if it will make the city boundary "straight and harmonious" (the precise opposite of the usual result of strip annexation).

Annexation can be involuntary (Kansas is one of a handful of states that permits this), with no area limit, as long as the annexed land is contiguous with the city and is platted.  However, a separate provision bans annexation of highway right-of-way unless the land on one or both sides of the highway is already part of the city.

Annexation can also be reversed if residents of the annexed land feel the city has not provided adequate public services--an issue that has surfaced in Sedgwick County (http://www.kansas.com/2011/05/12/1845734/lawmakers-limit-cities-annexation.html).

However, there is a catch:  per KSA § 12-521 (http://kansasstatutes.lesterama.org/Chapter_12/Article_5/#12-521), a city can annex outside the parameters of KSA § 12-520 if it files plans for the services it intends to provide in the annexed land and gets the approval of the county commissioners.  So, in principle, strip annexation can happen if a city can get buy-in from the county, but I don't think this happens often (if at all) since it is difficult to imagine circumstances under which it is in a county's interest to allow municipalities in its area to fight border wars with each other.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on March 24, 2014, 02:11:06 PM
Quote from: J N Winkler on March 24, 2014, 10:49:03 AM
But, as we all know, annexation law varies from state to state.  As long as abuses are not too flagrant, many states refrain from restricting annexation in order to keep the number of municipalities in a given area down, and thus limit the opportunities for coordination failures in land-use planning.  The Phoenix area has only 24 incorporated municipalities, for example, while Chicago has 265.

Part of that is that incorporation as a village (governmental type) is relatively easy in Illinois in addition to fairly easy annexation.  So you get a mixture of municipal sizes with some far more aggressive than others.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on March 24, 2014, 02:14:35 PM
Duncan is another Oklahoma city with similar annexation patterns to Owasso. It appears non-contiguous annexing is allowed, because Duncan has annexed several lakes east of town with no connection to the main city.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 24, 2014, 02:41:25 PM
Quote from: Scott5114 on March 24, 2014, 02:14:35 PM
Duncan is another Oklahoma city with similar annexation patterns to Owasso.
What the hell line do those follow? Underground water pipes?

Quote from: Scott5114 on March 24, 2014, 02:14:35 PM
It appears non-contiguous annexing is allowed, because Duncan has annexed several lakes east of town with no connection to the main city.
This appears to be the annexation of the lakes: http://www.tax.ok.gov/boundary/Duncan%20Sec%2015.pdf

Current law (effective 1978 at the latest) bans noncontiguous annexation:
QuoteThe municipal governing body by ordinance may add to the municipality territory adjacent or contiguous to its corporate limits and increase or diminish the corporate limits as the governing body deems desirable for the benefit of the municipality.
This may mean that strip annexation is illegal: http://www.ofblegalfoundation.org/past/item.aspx?archive=0&page=8381.htm&id=8381

PS: I love the Oknoname reservoirs.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on March 24, 2014, 03:46:27 PM
Quote from: NE2 on March 24, 2014, 02:41:25 PMCurrent law (effective 1978 at the latest) bans noncontiguous annexation:

QuoteThe municipal governing body by ordinance may add to the municipality territory adjacent or contiguous to its corporate limits and increase or diminish the corporate limits as the governing body deems desirable for the benefit of the municipality.

This may mean that strip annexation is illegal: http://www.ofblegalfoundation.org/past/item.aspx?archive=0&page=8381.htm&id=8381

After looking at the petition for declaratory judgment, I suspect Oklahoma law includes exceptions for noncontiguous annexation similar to those that exist in Kansas (where, for example, a city may annex land it owns whether that is adjacent to its borders or not), since it was apparently necessary for the plaintiffs to argue both that the annexed parcels were noncontiguous and served no tangible municipal purpose.  There may be another exception for municipal services with approval of the county, since the plaintiffs also addressed this in the petition.

Durant was attempting to create county islands of 5 square miles in the west and 12.5 square miles in the east, which is pretty egregious even by 1970's Arizona standards.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on March 26, 2014, 01:04:13 PM
Quote from: J N Winkler on March 23, 2014, 06:20:40 PM
Quote from: algorerhythms on March 23, 2014, 05:51:21 PMApparently the new Google Maps allows you to zoom in on a city by clicking its name, and it shows you the city limits when it zooms in. So I tried it on a few cities and stumbled on this (https://www.google.com/maps/place/Owasso,+OK/@36.292856,-95.8048779,12z/data=!3m1!4b1!4m2!3m1!1s0x87b6effc128d6983:0xa1a8eef11b4b92b0). I'm wondering whether this is a Google Maps slipup, or if Owasso actually did annex a bunch of roads in the surrounding area, but none of the land attached to the roads.

This isn't a new feature--the old Google Maps showed you jurisdictional boundaries (states, counties, cities) too.  What Google Maps shows for Owasso is a classic deployment of the encircling-annexation tactic (which gained notoriety in Arizona when it was used by several municipalities in the Phoenix area to carve out parcels of rural land which their neighbors would then not be able to annex).

Oh, kind of like a giant game of Go?
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on March 26, 2014, 02:51:57 PM
Quote from: kkt on March 26, 2014, 01:04:13 PMOh, kind of like a giant game of Go?

Yup.  Bigger stakes, more players, no requirement to play in turn, plus some consent requirements (which in the bad old days could be gotten around by holding secret meetings in the small hours of the morning)--but, yes, very similar.
Title: Re: Google Maps just fucking SUCKS now
Post by: DSS5 on April 29, 2014, 01:30:57 PM
Yesterday I discovered that you can set Google Maps to use "Lite" mode (which automatically is used for slow connections) by default, the only big change being that you get satellite instead of 3D "earth" imagery. Now it is actually usable and not so bad.

As of yesterday almost brand-new imagery for Boone, NC and surrounding areas, which is awesome. The old imagery was very low resolution and from 2008. Also some new Street View imagery, but only main roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on April 29, 2014, 02:45:48 PM
Earlier today I found something odd with the new Google Maps: It appears the satellite view (or "Earth" view as it calls it) is far more zoomed in than the map view. If you zoom in fairly close on the map, then click over to the satellite view, the zoom level is so high that you have to zoom out to see anything. Very strange. I don't know why they don't have it use the same zoom on both views.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 29, 2014, 02:46:35 PM
Quote from: 1995hoo on April 29, 2014, 02:45:48 PM
Earlier today I found something odd with the new Google Maps: It appears the satellite view (or "Earth" view as it calls it) is far more zoomed in than the map view. If you zoom in fairly close on the map, then click over to the satellite view, the zoom level is so high that you have to zoom out to see anything. Very strange. I don't know why they don't have it use the same zoom on both views.

True with the old Google Maps too.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on April 29, 2014, 02:48:24 PM
Quote from: 1 on April 29, 2014, 02:46:35 PM
Quote from: 1995hoo on April 29, 2014, 02:45:48 PM
Earlier today I found something odd with the new Google Maps: It appears the satellite view (or "Earth" view as it calls it) is far more zoomed in than the map view. If you zoom in fairly close on the map, then click over to the satellite view, the zoom level is so high that you have to zoom out to see anything. Very strange. I don't know why they don't have it use the same zoom on both views.

True with the old Google Maps too.

I never had that problem with the old one.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 29, 2014, 02:56:48 PM
Quote from: 1995hoo on April 29, 2014, 02:48:24 PM
Quote from: 1 on April 29, 2014, 02:46:35 PM
Quote from: 1995hoo on April 29, 2014, 02:45:48 PM
Earlier today I found something odd with the new Google Maps: It appears the satellite view (or "Earth" view as it calls it) is far more zoomed in than the map view. If you zoom in fairly close on the map, then click over to the satellite view, the zoom level is so high that you have to zoom out to see anything. Very strange. I don't know why they don't have it use the same zoom on both views.

True with the old Google Maps too.

I never had that problem with the old one.

Maybe it's not the same, but where I live, the scale says "50 feet" in normal mode and "20 feet" in satellite mode when zoomed in fully.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 29, 2014, 03:38:30 PM
It's way, way slower.  Swimming through honey slow.  And clutters the screen with all this junk that won't even go away.  Google, remember the success of the Google search screen:  nothing on it that doesn't need to be there, and it loads fast!

And mapquest is adding crap to make it slower too.  Not as slow as the new Google Maps, but it still sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mike_OH on May 03, 2014, 03:12:38 PM
I've had problems clicking on the businesses and points of interest. The street view also sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: rschen7754 on May 05, 2014, 01:58:08 AM
I had to turn on hardware acceleration in Firefox to get it to pan at all. But it's still horribly sluggish.
Title: Re: Google Maps just fucking SUCKS now
Post by: countyguy on May 18, 2014, 05:03:03 PM
Also, I use classic google maps.  I enjoy making maps in which I determine distances to the hundredth of the mile and draw lines along roads.  Those are no longer possible with new Google Maps.  The fact that we can still use classic version is great.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on May 18, 2014, 08:58:43 PM
I still use the classic Google maps. I like it way better because it is easier to find mistakes to edit on map maker, and the distance measurement tool is nice to have.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 04, 2014, 10:25:37 PM
Quote from: Occidental Tourist on March 13, 2014, 06:39:29 PM
Quote from: roadman65 on March 04, 2014, 03:13:27 PM
One thing, though, I noticed that if you drag the yellow man down to the map for Street View you MUST hit the target!  If you miss the blue line, the map will suddenly zoom out.

And good luck trying to follow a road for any distance on Street View.  The old version had set arrows in the pavement to advance or retreat on a route.  The new version does not.  Go over a complex viaduct in the new version and you'll find yourself in an underpass with no way out and no way to advance.  Here's a good example:  Try to cross the Zakim Bunker Hill Memorial Bridge on Street View (https://www.google.com/maps/place/North+Point+Park/@42.371379,-71.066735,3a,75y,128.95h,87.27t/data=!3m4!1e1!3m2!1sz1UZs3sOmbn7kPaRE6uy2A!2e0!4m7!1m4!3m3!1s0x89e3652d0d3d311b:0x787cbf240162e8a0!2sBoston,+MA!3b1!3m1!1s0x0:0xdce6ae09ee27ad73).  I dare you.
I just found this out today, but it is possible to use the arrow keys to navigate street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: JMoses24 on July 27, 2014, 06:33:04 AM
NOTE: I've edited this to remove my address.

Ladies and gentlemen, may I present... failure.

This actually happened to me. I'm looking up transit directions to a local bar for Tuesday as I plan to meet a friend there for lunch. The sensible thing to do would be to take the bus to the nearest bus stop, then walk up the side of the road to the bar. Indeed, when you type in Dickmann's Sports Cafe, that's what it would seem to tell you to do...

https://goo.gl/maps/Snp2B

But when I manually dragged the end point to the parking lot of the bar...same property, mind you...well, Google Maps just threw this at me. It wanted me to actually walk across SIX LANES of Interstate 275.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FemYiQuV.jpg&hash=11a06f913ff0a181cffb43b57058e56f7f981c35) (http://imgur.com/emYiQuV)
Title: Re: Google Maps just fucking SUCKS now
Post by: sipes23 on July 27, 2014, 11:57:47 AM
Quote from: kkt on April 29, 2014, 03:38:30 PM
It's way, way slower.  Swimming through honey slow.  And clutters the screen with all this junk that won't even go away.  Google, remember the success of the Google search screen:  nothing on it that doesn't need to be there, and it loads fast!

And mapquest is adding crap to make it slower too.  Not as slow as the new Google Maps, but it still sucks.

You understate how slow it truly is. On a new chromebook, which is running Google's latest software to optimize the whole Google experience, it takes 10 seconds to load. I know that seems impatient, but remind yourself: It's that slow on Google designed software. How slow is it on something else?  :banghead:

I'm actively looking for a map website that works as well as the old Google maps, but that doesn't seem to exist.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 27, 2014, 12:12:40 PM
Quote from: sipes23 on July 27, 2014, 11:57:47 AM
Quote from: kkt on April 29, 2014, 03:38:30 PM
It's way, way slower.  Swimming through honey slow.  And clutters the screen with all this junk that won't even go away.  Google, remember the success of the Google search screen:  nothing on it that doesn't need to be there, and it loads fast!

And mapquest is adding crap to make it slower too.  Not as slow as the new Google Maps, but it still sucks.

You understate how slow it truly is. On a new chromebook, which is running Google's latest software to optimize the whole Google experience, it takes 10 seconds to load. I know that seems impatient, but remind yourself: It's that slow on Google designed software. How slow is it on something else?  :banghead:

I'm actively looking for a map website that works as well as the old Google maps, but that doesn't seem to exist.

The old Google Maps still exists. I use it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on July 27, 2014, 12:38:41 PM
I can't stand the new Google maps.  I have a 'Favorite' button on the PC browser that just goes to the old one.  Unfortunately, clicking on any GSV link here brings me to the new one, and then it's a struggle to do anything with it.  I don't like not being able to just zoom in and out of GSV to aerials/maps, without having to hit the 'Back to Maps' toggle which dumps me nowhere near where I just was on GSV.  Not being able to toggle labels on and off is also terrible too in the new version.  Thumbs down, Google.
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on July 27, 2014, 12:51:53 PM
Quote from: JMoses24 on July 27, 2014, 06:33:04 AM
Ladies and gentlemen, may I present... failure.

Per your screenshot you are using the old Google Maps. This thread is for complaining about the new one. :P


Which, honestly, I've gotten used to and am okay with at this point. I still have a few complaints but I had several complaints about the old one as well, so eh.

Things I don't like:
- when you ask for directions it recommends a mode of transportation automatically, you have to then manually select another option if Google's primary choice isn't what you're looking for (in particular, the freaking useless flying directions which merely serve as advertising for airlines can die in a fire)
- driving directions show most prominently the travel time in current traffic, leaving free flow time as an afterthought. This assumes the user is asking for directions for a trip they are about to make right now, not planning for something later. (to be fair, this assumption is probably correct for most users, especially mobile users. But it sure isn't correct for roadgeeks!)
- will not show the boundaries of a county if a town or city with the same name exists in the same state, will insist on showing you the town even if you specify "county"
- if you searched for something and haven't cleared it, any failure to drop pegman properly will jump you back to what you searched for rather than leaving you where you are
- on that note, pegman is more finnicky than in the old version about when and where he will let you drop him
Title: Re: Google Maps just fucking SUCKS now
Post by: The Nature Boy on July 27, 2014, 02:05:04 PM
Quote from: Duke87 on July 27, 2014, 12:51:53 PM
Quote from: JMoses24 on July 27, 2014, 06:33:04 AM
Ladies and gentlemen, may I present... failure.
Things I don't like:

- driving directions show most prominently the travel time in current traffic, leaving free flow time as an afterthought. This assumes the user is asking for directions for a trip they are about to make right now, not planning for something later. (to be fair, this assumption is probably correct for most

The big problem with this feature (for everyone, I assume) is that if I want directions from Charlotte, NC to Boston, MA, I don't really care what the travel time is NOW because the traffic that I'll hit in NY or DC will be gone by the time I get to it. Google Maps almost assumes that traffic will remain constant for your entire trip.

Not really helpful
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on July 27, 2014, 04:23:47 PM
I use the old Google Maps, but I use the new one if I want to see new streetview images.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 27, 2014, 07:18:08 PM
While the old maps exists, there's no denying that Google is no longer maintaining it.  Last I tried to make a link from it, the short URL feature no longer worked.

Quote from: Duke87 on July 27, 2014, 12:51:53 PM
- driving directions show most prominently the travel time in current traffic, leaving free flow time as an afterthought. This assumes the user is asking for directions for a trip they are about to make right now, not planning for something later. (to be fair, this assumption is probably correct for most users, especially mobile users. But it sure isn't correct for roadgeeks!)
I suspect that's why they mark temporarily closed roads as not existing.  Really hard if you're planning a future trip when the road is reopened.

Quote
- on that note, pegman is more finnicky than in the old version about when and where he will let you drop him
There's also some glitch where grabbing pegman causes the map to jump halfway up the screen.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on July 27, 2014, 10:28:34 PM
Quote from: vdeane on July 27, 2014, 07:18:08 PM
While the old maps exists, there's no denying that Google is no longer maintaining it.  Last I tried to make a link from it, the short URL feature no longer worked.
Short URL works for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: JMoses24 on July 27, 2014, 10:58:58 PM
Quote from: Duke87 on July 27, 2014, 12:51:53 PM
Quote from: JMoses24 on July 27, 2014, 06:33:04 AM
Ladies and gentlemen, may I present... failure.

Per your screenshot you are using the old Google Maps. This thread is for complaining about the new one. :P


Which, honestly, I've gotten used to and am okay with at this point. I still have a few complaints but I had several complaints about the old one as well, so eh.

Things I don't like:
- when you ask for directions it recommends a mode of transportation automatically, you have to then manually select another option if Google's primary choice isn't what you're looking for (in particular, the freaking useless flying directions which merely serve as advertising for airlines can die in a fire)
- driving directions show most prominently the travel time in current traffic, leaving free flow time as an afterthought. This assumes the user is asking for directions for a trip they are about to make right now, not planning for something later. (to be fair, this assumption is probably correct for most users, especially mobile users. But it sure isn't correct for roadgeeks!)
- will not show the boundaries of a county if a town or city with the same name exists in the same state, will insist on showing you the town even if you specify "county"
- if you searched for something and haven't cleared it, any failure to drop pegman properly will jump you back to what you searched for rather than leaving you where you are
- on that note, pegman is more finnicky than in the old version about when and where he will let you drop him

I don't like the new one, either. But I did want to point out there's fails in both versions and thought this was a good place to put that.
Title: Re: Google Maps just fucking SUCKS now
Post by: national highway 1 on July 28, 2014, 09:29:12 AM
Whenever I drag the Streetview Pinman onto the map, the map keeps panning north or south which I find really annoying about the new Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: MillTheRoadgeek on July 28, 2014, 09:45:33 AM
Well, here is my thoughts on the new Google Maps:

I think it is fine, but too hard to navigate for photos, distance measure, and all that stuff. Plus, it is much slower than classic Google Maps and only shows yellow for major arterials.

I've tried to switch back, but I found the non-fullscreen space too weird and hard to get used to back. I also have more problems, but I can't really list them right now.
Title: Re: Google Maps just fucking SUCKS now
Post by: mobilene on July 28, 2014, 09:50:54 AM
Old Maps was great for straight-up map power users, and I'll bet that means most of us. New Maps I'm betting is meant to be a more all-purpose map tool that integrates better with Google's other services.

That said, it's constantly dragging my browser performance into the toilet. Annoying as hell.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on July 28, 2014, 09:55:42 AM
Quote from: national highway 1 on July 28, 2014, 09:29:12 AM
Whenever I drag the Streetview Pinman onto the map, the map keeps panning north or south which I find really annoying about the new Google Maps.
Miss the target when pining and the map will zoom out.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 28, 2014, 06:15:11 PM
Quote from: freebrickproductions on July 27, 2014, 10:28:34 PM
Quote from: vdeane on July 27, 2014, 07:18:08 PM
While the old maps exists, there's no denying that Google is no longer maintaining it.  Last I tried to make a link from it, the short URL feature no longer worked.
Short URL works for me.
Are you signed in?  That might make a difference.  I usually do everything with driving directions in a private window because I don't want the directions/searching mucking up my search history/page thumbnail for the new tab page.  It happened in both IE8 at work and Chrome at home (when I tried to create the short URL there; had to email the long URL to myself).
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on July 28, 2014, 06:23:01 PM
I tried to jump on NJ 29 recently and I always end up on a nearby street and not 29 itself. This happens in other cities too, especially one where I ended up like 15 miles south of where I wanted to be. And before you ask - yes, there WAS Streetview data there.
Title: Re: Google Maps just fucking SUCKS now
Post by: mjb2002 on August 23, 2014, 11:30:50 AM
Quote from: agentsteel53 on February 26, 2014, 03:26:58 PM
well, shit.

it's gone from a tool that I rely on several times a day, to something for which I have had to erase the memorized auto-complete URL in my browser's address bar, lest I prefer to not absentmindedly crash my browser.

what the high holy fuck ever prompted Google to release this pile of shit?

it's like going from a car that reliably transports you to point B, to Ace Rothstein's Cadillac.

I have to agree with you here, especially on touchscreens, where you can't even move the Street View man.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 23, 2014, 01:37:14 PM
Anyone else notice that you can't modify a route as many times in the driving directions on new maps?
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on August 23, 2014, 05:46:07 PM
Quote from: vdeane on August 23, 2014, 01:37:14 PM
Anyone else notice that you can't modify a route as many times in the driving directions on new maps?

I've noticed that printing a map has become difficult.
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on August 23, 2014, 06:41:04 PM
Quote from: Brandon on August 23, 2014, 05:46:07 PM
Quote from: vdeane on August 23, 2014, 01:37:14 PM
Anyone else notice that you can't modify a route as many times in the driving directions on new maps?

I've noticed that printing a map has become difficult.

Yes, they force you to use CTRL+P to print...and the map size is tiny as hell.

Hate it hate it HATE IT!

And it ALWAYS defaults to the new map...you can never set the Goog to give you the older maps all the time.
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on August 23, 2014, 10:20:19 PM
That's weird. I have Google Maps always default to the old ones in my copy of Firefox.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on August 23, 2014, 11:40:42 PM
I have a "Favorites Bar" button in IE that goes directly to the old Google maps.  However, when I click a GSV link here, it always go to the new one of course.  Very annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on August 24, 2014, 11:13:53 AM
Quote from: rickmastfan67 on August 23, 2014, 10:20:19 PM
That's weird. I have Google Maps always default to the old ones in my copy of Firefox.

I've done it in my copy of Firefox before, but it never sticks for some reason...but now I look at what Roadrunner75 posted and now I'm wondering if when you click on a link it hard resets your browser to go back to the old one.

So I reset it in my browser, but now I've created a Google Maps Old School bookmark with the old maps up, let's see what happens here over time.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 24, 2014, 12:48:52 PM
The best way to ensure you're always using the old Google Maps is to do the following:
1. If you aren't using Windows 7 or earlier, switch to Windows 7.
2. Uninstall any IE upgrades (ie: IE9, 10, 11, etc.)
3. Go into "default programs" and make IE8 your default browser
4. Uninstall any other browsers (Firefox, Chrome, etc.) you may have

After this, you will never see the new Maps again!
Title: Re: Google Maps just fucking SUCKS now
Post by: algorerhythms on August 24, 2014, 01:09:17 PM
Quote from: vdeane on August 24, 2014, 12:48:52 PM
The best way to ensure you're always using the old Google Maps is to do the following:
1. If you aren't using Windows 7 or earlier, switch to Windows 7.
2. Uninstall any IE upgrades (ie: IE9, 10, 11, etc.)
3. Go into "default programs" and make IE8 your default browser
4. Uninstall any other browsers (Firefox, Chrome, etc.) you may have

After this, you will never see the new Maps again!
That's like saying the best cure for a cold is a cyanide capsule. It'll end your cold, but you might not like the side effects...
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on August 24, 2014, 03:17:26 PM
I use Waterfox and I never get the new Google Maps unless I'm clicking a link, and it hasn't reset to the old one after I click a link.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on August 24, 2014, 10:47:14 PM
I have Google Maps default to the old one and I never see the new one unless I choose to go to the new one.
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on September 12, 2014, 09:40:44 AM
Well, this morning I went to open up Google Maps and the new one was staring me in the face.  Not only that, the "Old School" map link I'd set aside in Firefox has ALSO reverted to the new Google Maps.

Almost three weeks...
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 12, 2014, 12:42:49 PM
I noticed yesterday that the distance measurement tool has returned (available in the right click menu).  It even looks like a ruler now and gives intermediate mileage and you can move/remove the points at will like with driving directions.  I haven't tried to measure an entire interstate though, so I don't know if there's a restriction on how many points you can have.

Now they just need to increase the number of points allowed in driving directions and my complaints will be satisfied.  I don't really care about the inability to generate a short URL in street view as the street view URLs in new Maps aren't terribly long.
Title: Re: Google Maps just fucking SUCKS now
Post by: SSOWorld on September 13, 2014, 08:52:03 AM
Quote from: vdeane on September 12, 2014, 12:42:49 PM
I noticed yesterday that the distance measurement tool has returned (available in the right click menu).  It even looks like a ruler now and gives intermediate mileage and you can move/remove the points at will like with driving directions.  I haven't tried to measure an entire interstate though, so I don't know if there's a restriction on how many points you can have.

Now they just need to increase the number of points allowed in driving directions and my complaints will be satisfied.  I don't really care about the inability to generate a short URL in street view as the street view URLs in new Maps aren't terribly long.
I use Google Maps Engine Lite for my customized road trips.  It supports up to about 20 points (SWAG)
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on September 23, 2014, 07:46:18 PM
I do like something GM did within the past day. Idk if anyone else noticed, but now the roads look slightly more like they did before that time last year when they really switched the roads' design around. http://prntscr.com/4ppu6m that's what I'm talking about. Anyone else like that they bring this back? You can much more clearly see if a road is a divided highway or non-divided highway, and I always liked this design on GM, and I'm glad it's back.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 23, 2014, 08:19:12 PM
Toll roads now look like shit when you zoom in. As they should, I suppose.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on September 23, 2014, 08:31:54 PM
Quote from: NE2 on September 23, 2014, 08:19:12 PM
Toll roads now look like shit when you zoom in. As they should, I suppose.

I haven't gotten the chance to zoom in on any toll roads until now, err..well this is new.. http://prntscr.com/4pqfnr I don't think it's that bad, but it's definitely something getting used to.  :hmmm:
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on September 23, 2014, 09:12:50 PM
Quote from: adventurernumber1 on September 23, 2014, 08:31:54 PM
Quote from: NE2 on September 23, 2014, 08:19:12 PM
Toll roads now look like shit when you zoom in. As they should, I suppose.

I haven't gotten the chance to zoom in on any toll roads until now, err..well this is new.. http://prntscr.com/4pqfnr I don't think it's that bad, but it's definitely something getting used to.  :hmmm:
How am I supposed to distinguish toll roads?  Tiny black borders on the otherwise typical freeway orange?  How about green like every other map?
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on September 23, 2014, 09:24:42 PM
Quote from: Roadrunner75 on September 23, 2014, 09:12:50 PM
Quote from: adventurernumber1 on September 23, 2014, 08:31:54 PM
Quote from: NE2 on September 23, 2014, 08:19:12 PM
Toll roads now look like shit when you zoom in. As they should, I suppose.

I haven't gotten the chance to zoom in on any toll roads until now, err..well this is new.. http://prntscr.com/4pqfnr I don't think it's that bad, but it's definitely something getting used to.  :hmmm:
How am I supposed to distinguish toll roads?  Tiny black borders on the otherwise typical freeway orange?  How about green like every other map?

Who the fuck thought that this was a good change? I would love to see toll roads in green instead of freeway orange. Well, I guess then tolled crossings would appear green as well with that criteria...
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 23, 2014, 09:45:14 PM
Tolled non-freeways would then be shown as freeways.
Title: Re: Google Maps just fucking SUCKS now
Post by: OracleUsr on September 23, 2014, 10:13:17 PM
I hate the new one.  I like to look at road signs and always preferred looking at them through Maps rather than doing an engine search and getting a bunch of irrelevant crap.

Half the time I get to a highway and it says it's going to Street View and it puts me on some side road where it is either nowhere near the road I'm looking for or it's impossible to get to the road I'm looking for.  I-85 in Suwanee, GA, is a great example.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on September 23, 2014, 10:19:39 PM
Quote from: OracleUsr on September 23, 2014, 10:13:17 PM
Half the time I get to a highway and it says it's going to Street View and it puts me on some side road where it is either nowhere near the road I'm looking for or it's impossible to get to the road I'm looking for.

Ikr, that happens to me all the time. It's really bad if you're doing something like trying to get on an interstate when it has frontage roads or a lot of roads right near it. But I've had to deal with it and I've found out how to get back to what I'm doing pretty quickly. When you move the mouse around, you of course should see a circle/oval looking thing. If the road or interstate you want to get on is in vision, click on it with that circle/oval. Another way is to drag the orange guy on the mini-map shown when in street-view to the road you want to be on.
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on September 23, 2014, 10:32:54 PM
It takes 3 clicks to return to classic. Couple more if you want to tell them exactly what parts of the new one suck. Of all the dumb things Google has done to maps, this doesn't even rate, trust me.
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on September 23, 2014, 11:08:08 PM
It seems they've even attempted to flag only one side of a bridge if it's only tolled in one direction.

I say "attempted" because I see they have rebuilt the eastbound Verazzano toll plaza. :rolleyes:
Title: Re: Google Maps just fucking SUCKS now
Post by: US71 on September 23, 2014, 11:19:02 PM
If I print out driving direction in the new Google Maps, it's all gibberish. I've reported the problem, but they've never responded.

So I have to switch back to classic and re-enter all the info.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on September 24, 2014, 09:58:31 AM
Does anyone else see a gray line next to this (https://www.google.com/maps/@40.2196554,-74.7784127,18z) view of the Calhoun Street Bridge in Trenton? There's nothing there on that side, I thought it was a pedestrian crossing, but it's literally nothing.

Also, it appears ramps that lead directly to tolls of some sort (I.E. no exits before it) are outlined to draw more attention as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on September 24, 2014, 12:16:27 PM
Quote from: Zeffy on September 24, 2014, 09:58:31 AM
Does anyone else see a gray line next to this (https://www.google.com/maps/@40.2196554,-74.7784127,18z) view of the Calhoun Street Bridge in Trenton? There's nothing there on that side, I thought it was a pedestrian crossing, but it's literally nothing.

Also, it appears ramps that lead directly to tolls of some sort (I.E. no exits before it) are outlined to draw more attention as well.

I see the grey line. Looking at Street View, it appears there is a pedestrian path on the bridge itself, so the line probably denotes that. It looks like the standard thing they use to show bike paths and the like.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on September 24, 2014, 12:20:25 PM
Quote from: 1995hoo on September 24, 2014, 12:16:27 PM
Quote from: Zeffy on September 24, 2014, 09:58:31 AM
Does anyone else see a gray line next to this (https://www.google.com/maps/@40.2196554,-74.7784127,18z) view of the Calhoun Street Bridge in Trenton? There's nothing there on that side, I thought it was a pedestrian crossing, but it's literally nothing.

Also, it appears ramps that lead directly to tolls of some sort (I.E. no exits before it) are outlined to draw more attention as well.

I see the grey line. Looking at Street View, it appears there is a pedestrian path on the bridge itself, so the line probably denotes that. It looks like the standard thing they use to show bike paths and the like.

The next bridge south is the Trenton Makes bridge, which also has a pedestrian walkway, but Google Maps does not show a gray line there.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 24, 2014, 01:03:42 PM
The best way to avoid having street view to go to the wrong road is to zoom in really close before dragging pegman.

I can see why they made that change.  Most people are using street view to find homes and businesses, not to gawk at guide signs.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on September 24, 2014, 02:06:29 PM
Quote from: jeffandnicole on September 24, 2014, 12:20:25 PM
The next bridge south is the Trenton Makes bridge, which also has a pedestrian walkway, but Google Maps does not show a gray line there.

I noticed that as well. I don't get it. On the Calhoun Street bridge, the walkway is a bit too far off the bridge (so it looks like the walkway is a separate entity), and on the Trenton Makes bridge... there's nothing. Also, I despise how thick the lines are in general now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 24, 2014, 03:29:49 PM
The new outlines on freeways is a bit inconsistent:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FGJ90q85.png&hash=f82ea5343ad28f3edf8000ff49a5cc36bcd663db)
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on September 24, 2014, 03:51:53 PM
Quote from: vdeane on September 24, 2014, 01:03:42 PM
The best way to avoid having street view to go to the wrong road is to zoom in really close before dragging pegman.

I just click on the highway, and no matter how zoomed in I am I'm usually teleported to a side street at least a few miles away from where I wanted to be.
Quote from: Bruce on September 24, 2014, 03:29:49 PM
The new outlines on freeways is a bit inconsistent

Yeah, I know. I don't like this "update" at ALL. It looks a lot more sloppy compared to what they had before.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 24, 2014, 05:06:52 PM
Quote from: Zeffy on September 24, 2014, 03:51:53 PM
Quote from: vdeane on September 24, 2014, 01:03:42 PM
The best way to avoid having street view to go to the wrong road is to zoom in really close before dragging pegman.

I just click on the highway, and no matter how zoomed in I am I'm usually teleported to a side street at least a few miles away from where I wanted to be.
Have you tried dragging pegman instead of clicking?
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 24, 2014, 05:28:43 PM
Quote from: Bruce on September 24, 2014, 03:29:49 PM
The new outlines on freeways is a bit inconsistent:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FGJ90q85.png&hash=f82ea5343ad28f3edf8000ff49a5cc36bcd663db)
Uh no. It's perfectly consistent - those are the pieces of road that you have to pay a toll to use.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on September 24, 2014, 05:50:46 PM
Quote from: Zeffy on September 24, 2014, 03:51:53 PM
I just click on the highway, and no matter how zoomed in I am I'm usually teleported to a side street at least a few miles away from where I wanted to be.
I only encounter new Google Maps when I click on a link here.  Otherwise, I just use a browser 'favorite' button that takes me directly to 'Classic'.  When I do get dumped into the new street view via a link, and I click the "Back to Map" at the bottom left corner to see where the GSV is located, it brings up the map, but it doesn't have the Pegman or anything else indicating where I just was. I assume it's centered, but I don't know the exact location of the street view image and can't go right back to it.

Classic is great because I can just zoom out to map/satellite from GSV by scrolling, and zoom back into GSV as well.  The new maps doesn't seem to have this, and forces me to toggle with the "Back to Maps" icon.  Terrible.


Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 24, 2014, 06:36:39 PM
Quote from: NE2 on September 24, 2014, 05:28:43 PM
Uh no. It's perfectly consistent - those are the pieces of road that you have to pay a toll to use.

Didn't realize that. Thanks for the heads up.

For reference, WA-16 (whose eastbound bridge is tolled) looks like this:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fpuu.sh%2FbMyBT%2Ff385b441c4.png&hash=cc0692f2fa423cd12059c5d4c2d0bb492bbc52e6)
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on September 24, 2014, 09:40:15 PM
Quote from: Zeffy on September 24, 2014, 09:58:31 AM
Does anyone else see a gray line next to this (https://www.google.com/maps/@40.2196554,-74.7784127,18z) view of the Calhoun Street Bridge in Trenton? There's nothing there on that side, I thought it was a pedestrian crossing, but it's literally nothing.
It'll be gone shortly. :cool:
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 24, 2014, 11:27:59 PM
There is a sidewalk there. dfwmapper is a vandalistic assclown.
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on September 25, 2014, 12:31:33 AM
Quote from: NE2 on September 24, 2014, 11:27:59 PM
There is a sidewalk there. dfwmapper is a vandalistic assclown.
Well, thanks for your kind words, but at least on Google Maps, sidewalks aren't supposed to be mapped separately from the road they are at the side of, they are set as an attribute of the road itself. The only exception would be an independent trail that parallels a road for a short distance before heading off on its own, which isn't the case here.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 25, 2014, 12:46:25 AM
Check the NYC bridges. Most of the East River and Harlem River bridges have separately mapped sidewalks. Not that it makes a difference - you're just a sucker doing free work for a for-profit corp.
Title: Re: Google Maps just fucking SUCKS now
Post by: KEK Inc. on September 25, 2014, 06:48:30 AM
The toll outline is hideous.  A slightly different color would have been better, in my opinion.
Title: Re: Google Maps just fucking SUCKS now
Post by: english si on September 25, 2014, 07:38:41 AM
Quote from: NE2 on September 25, 2014, 12:46:25 AMyou're just a sucker doing free work for a for-profit corp.
Yes, use OSM, rather than Google Map Maker!
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on September 25, 2014, 12:22:53 PM
I tried OSM, didn't care for the interface.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on September 25, 2014, 12:59:52 PM
I personally use Google Maps because they have satellite view and a broad street view coverage (Bing has barely any). I really need those for several of my maps, such as the Alabama Siren Map (https://maps.google.com/maps/ms?msid=214814604170748480658.0004e00578681d9d6ade6&msa=0).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 25, 2014, 01:06:12 PM
Quote from: Roadrunner75 on September 24, 2014, 05:50:46 PM
Classic is great because I can just zoom out to map/satellite from GSV by scrolling, and zoom back into GSV as well.  The new maps doesn't seem to have this, and forces me to toggle with the "Back to Maps" icon.  Terrible.
As someone who always hated being forced into/out of street view against her will when exploring the map/satellite imagery while closely zoomed in or when zooming out of street view, I have the opposite opinion.  I LOVE that it no longer does that.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on September 25, 2014, 03:45:36 PM
Quote from: vdeane on September 25, 2014, 01:06:12 PM
Quote from: Roadrunner75 on September 24, 2014, 05:50:46 PM
Classic is great because I can just zoom out to map/satellite from GSV by scrolling, and zoom back into GSV as well.  The new maps doesn't seem to have this, and forces me to toggle with the "Back to Maps" icon.  Terrible.
As someone who always hated being forced into/out of street view against her will when exploring the map/satellite imagery while closely zoomed in or when zooming out of street view, I have the opposite opinion.  I LOVE that it no longer does that.

While I use Classic for reasons of speed of performance, I do have to admit you have a point. I run Waterfox with a Flash blocker add-on to stop the annoying videos that play when you load ESPN and to avoid audio and video ads, and it works well, but the downside of it is that if I inadvertently scroll in too far using Google Maps, the Flash blocker kicks in when Street View tries to load and I'm forced to click the icon, let Street View load, and then exit back out. No way to scroll back out once the Flash blocker kicks in. The benefits of the blocker outweigh this nuisance, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 25, 2014, 04:31:34 PM
Quote from: 1995hoo on September 25, 2014, 03:45:36 PM
I run Waterfox with a Flash blocker add-on to stop the annoying videos that play when you load ESPN and to avoid audio and video ads, and it works well, but the downside of it is that if I inadvertently scroll in too far using Google Maps, the Flash blocker kicks in when Street View tries to load and I'm forced to click the icon, let Street View load, and then exit back out. No way to scroll back out once the Flash blocker kicks in. The benefits of the blocker outweigh this nuisance, though.
I don't know what the fuck Waterfox is, but Firefox now has a built-in flash blocker that lets you whitelist specific sites.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on September 25, 2014, 04:31:53 PM
Quote from: 1995hoo on September 25, 2014, 03:45:36 PM
Quote from: vdeane on September 25, 2014, 01:06:12 PM
Quote from: Roadrunner75 on September 24, 2014, 05:50:46 PM
Classic is great because I can just zoom out to map/satellite from GSV by scrolling, and zoom back into GSV as well.  The new maps doesn't seem to have this, and forces me to toggle with the "Back to Maps" icon.  Terrible.
As someone who always hated being forced into/out of street view against her will when exploring the map/satellite imagery while closely zoomed in or when zooming out of street view, I have the opposite opinion.  I LOVE that it no longer does that.

While I use Classic for reasons of speed of performance, I do have to admit you have a point. I run Waterfox with a Flash blocker add-on to stop the annoying videos that play when you load ESPN and to avoid audio and video ads, and it works well, but the downside of it is that if I inadvertently scroll in too far using Google Maps, the Flash blocker kicks in when Street View tries to load and I'm forced to click the icon, let Street View load, and then exit back out. No way to scroll back out once the Flash blocker kicks in. The benefits of the blocker outweigh this nuisance, though.
For me the scrolling feature is great because I can quickly jump further down the road (or to another road) by zooming out and then zooming back into GSV where I want.  The "Back to Maps" leaves me so far zoomed out that I don't know where I just was half the time.  I will admit that it is touchy and that I get occasionally sucked into GSV by accident.  It would be great if there was a toggle for this feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on September 25, 2014, 04:49:13 PM
Quote from: NE2 on September 25, 2014, 04:31:34 PM
Quote from: 1995hoo on September 25, 2014, 03:45:36 PM
I run Waterfox with a Flash blocker add-on to stop the annoying videos that play when you load ESPN and to avoid audio and video ads, and it works well, but the downside of it is that if I inadvertently scroll in too far using Google Maps, the Flash blocker kicks in when Street View tries to load and I'm forced to click the icon, let Street View load, and then exit back out. No way to scroll back out once the Flash blocker kicks in. The benefits of the blocker outweigh this nuisance, though.
I don't know what the fuck Waterfox is, but Firefox now has a built-in flash blocker that lets you whitelist specific sites.

If you ask politely, maybe someone will tell you.

Edited to add: But I just checked my add-on and found it has a whitelist function, so I've remedied the problem. Thanks for the tip, even if you need to learn not to speak like Cartman.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 25, 2014, 06:53:47 PM
Quote from: Roadrunner75 on September 25, 2014, 04:31:53 PM
For me the scrolling feature is great because I can quickly jump further down the road (or to another road) by zooming out and then zooming back into GSV where I want.  The "Back to Maps" leaves me so far zoomed out that I don't know where I just was half the time.  I will admit that it is touchy and that I get occasionally sucked into GSV by accident.  It would be great if there was a toggle for this feature.


At least in New Maps, if you mouse over the map insert in street view you can click on a street to teleport there, so no need to even exit street view.

Many of the performance issues can be solved by disabling WebGL.  In Chrome, there's an option for it in about://flags.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeek2500 on September 25, 2014, 07:53:23 PM
I may have found a good Gmaps replacement, HERE maps. They are the people who make the maps for all Garmin devices. Check it out. here.com (http://here.com)
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 25, 2014, 09:04:41 PM
Quote from: Roadgeek2500 on September 25, 2014, 07:53:23 PM
I may have found a good Gmaps replacement, HERE maps. They are the people who make the maps for all Garmin devices. Check it out. here.com (http://here.com)
If it doesn't have street view, it's not even in the running as a replacement.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on September 25, 2014, 09:36:13 PM
Quote from: NE2 on September 25, 2014, 09:04:41 PM
Quote from: Roadgeek2500 on September 25, 2014, 07:53:23 PM
I may have found a good Gmaps replacement, HERE maps. They are the people who make the maps for all Garmin devices. Check it out. here.com (http://here.com)
If it doesn't have street view, it's not even in the running as a replacement.

I tried it out. I wasn't on there long enough to really check it out, but it has some fairly good maps, and it actually does have street view, and it's the only site I've ever seen that has it besides Google Maps. But you must have Google Chrome to use it, and when you try to get street view, the only available street view I saw was clustered in urban areas across the U.S.

EDIT: Here Maps could possibly be on the rise to become a pretty rad website.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on September 25, 2014, 10:22:45 PM
Quote from: adventurernumber1 on September 25, 2014, 09:36:13 PM
Quote from: NE2 on September 25, 2014, 09:04:41 PM
Quote from: Roadgeek2500 on September 25, 2014, 07:53:23 PM
I may have found a good Gmaps replacement, HERE maps. They are the people who make the maps for all Garmin devices. Check it out. here.com (http://here.com)
If it doesn't have street view, it's not even in the running as a replacement.

I tried it out. I wasn't on there long enough to really check it out, but it has some fairly good maps, and it actually does have street view, and it's the only site I've ever seen that has it besides Google Maps. But you must have Google Chrome to use it, and when you try to get street view, the only available street view I saw was clustered in urban areas across the U.S.

EDIT: Here Maps could possibly be on the rise to become a pretty rad website.
Doesn't have much streetview though. Hell, they don't even have any of the streets in Huntsville. I'll give it a little bit before I make my decision to switch to it or not. Glad that they have a satellite view though.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on September 25, 2014, 10:51:58 PM
Quote from: freebrickproductions on September 25, 2014, 10:22:45 PM
Doesn't have much streetview though. Hell, they don't even have any of the streets in Huntsville. I'll give it a little bit before I make my decision to switch to it or not. Glad that they have a satellite view though.

I tried Trenton, Princeton, Newark and a bunch of other cities to see if it had SV. Nope. Even if Google Maps is a bit ugly, it still runs decent enough on IE, and if that doesn't work... well... I'll go back to classic.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on September 25, 2014, 11:16:35 PM
I think Bing Maps would be #2, with more 'bird's eye' view, but Google Maps is catching up in that department.  I used to jump back and forth between the two over bird's eye vs. street view, but mostly stay with Google now.
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on September 26, 2014, 12:39:58 AM
Quote from: Roadgeek2500 on September 25, 2014, 07:53:23 PM
I may have found a good Gmaps replacement, HERE maps. They are the people who make the maps for all Garmin devices. Check it out. here.com (http://here.com)

They're also the ones behind Yahoo! Maps as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on September 26, 2014, 11:12:09 AM
Does anyone else see how Google labeled some of the ramps and whatnot on I-676/US 30 in Philadelphia as toll roads? Look here (https://www.google.com/maps/@39.954842,-75.1466638,17z) and you'll notice the ramp for 5th Street is outlined as if it were a toll road. Same with I-676 and US 30 - (how many times do you see an Interstate labeled with anything but freeway orange?) even though the only toll is before the bridge in Camden. I get that if you don't go through the toll you won't be able to use those ramps (imagine that), but I don't think they should be marked as a toll road.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on September 26, 2014, 04:17:54 PM
Due to the areas I frequently check in Google Maps, for some things I discarded it in favor of Baidu Maps :bigass:.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on October 18, 2014, 01:03:47 AM
Does anyone else have Google Maps on a smartphone (such as an iPhone)? I do, and have for a while. But getting to the point, recently, multiple times, it has not let me gotten street view. I've probably had it for two years on my iPhone, and not one time has it failed to give me street view on a road/interstate that has it, but lately it has been failing me a lot.

https://m.flickr.com/#/photos/127322363@N08/15374784408/
That's an example of the crap Im seeing when I try to get street view many times now (that blank space on the bottom is where an option to get street view is supposed to be).

Has anybody else been having this issue?

EDIT: This is a fairly big deal for me, for I am a frequent Google Maps user, and when I'm not at my laptop (away from home or "asleep" in bed *cough* on my phone  :) *cough*), I use it a lot on my iPhone. Also, right now I'm trying to find SteveG's location (see the Where's Steve At thread in Photos/Videos subforum), so this is a major holdup  :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: Billy F 1988 on October 18, 2014, 03:14:43 AM
Just can the new GMaps. You're better off with Yahoo or Mapquest. Being that they're not as the best as GMaps, at least Yahoo and MapQuest don't glitch out and cause browser crashes unlike "new" GMaps. I can't really say the same for those accessing these map services on Smartphones, iPads, or Windows Phones, per se, because I am not familiar with these devices and how they can handle GMaps, Yahoo, or MapQuest.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 18, 2014, 10:28:32 AM
The current Google Maps app for iPhone and iPad doesn't seem to do Street View. You need to get the separate Google Earth app. It does allow Street View, though I cannot figure out how to get it to give me a link, such as if I want to post one here.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on October 18, 2014, 10:51:36 AM
Besides being a giant battery drainer, Google Maps Streetview is incredibly difficult to work with on my iPhone 6, so I choose not to use my phone for that.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on October 18, 2014, 12:15:50 PM
Google Streetview is a lost cause on any "I" device.  I won't even bother with GSV on my Iphone, but on the Ipad, it only works if you click on a named location/point of interest which then brings up pegman.  Clicking him will only bring you to the nearest street frontage of the named location, and you can then only slowly proceed in either direction along the street.  This is through Safari, and not an app, but I understand this is the same.  It makes GSV essentially useless for checking out roads.  Safari also frequently crashes on me, and when I reopen it, it puts me right back at the original location, losing any progress I made along the road.

Quote from: adventurernumber1 on October 18, 2014, 01:03:47 AM
This is a fairly big deal for me, for I am a frequent Google Maps user, and when I'm not at my laptop (away from home or "asleep" in bed *cough* on my phone  :) *cough*), I use it a lot on my iPhone. Also, right now I'm trying to find SteveG's location (see the Where's Steve At thread in Photos/Videos subforum), so this is a major holdup  :pan:

I only look for Steve's location on a desktop PC where I have full GSV at my disposal - and Classic GSV at that.  I could never do it on the new Google Maps, because it's much more cumbersome and doesn't allow me to quickly zoom in and out when I find a location that looks right and I need to check it at street level.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 18, 2014, 02:15:31 PM
In the Google Earth app you drag the man to whatever location. I never run it on my phone because of the small screen, but it works fine on my iPad.

I have no problem viewing Street View links via Safari on my iPad, though. Just can't seem to get to it myself if I wanted to use their website.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on October 18, 2014, 02:35:37 PM
I just get street view on the Google Maps app. When I hold down to get the red pointer thing for a location (if the road has available street view), I used to be able to get street view just fine. This past week, though, 95% of the time it just shows a blank screen where the street view option is supposed to be!! And sometimes, after entering the app for the first time in a while, it'll let me get street view one time, then not at all after that! But I only use Google Maps on my phone when I'm unable to be on my laptop, so luckily this isn't an issue most of my time, only when I'm on my phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on October 18, 2014, 10:29:42 PM
Quote from: 1995hoo on October 18, 2014, 02:15:31 PM
In the Google Earth app you drag the man to whatever location. I never run it on my phone because of the small screen, but it works fine on my iPad.

I have no problem viewing Street View links via Safari on my iPad, though. Just can't seem to get to it myself if I wanted to use their website.
I'll give the Google Earth app a try.  I'm not much for downloading apps, and I usually just use the browser for things that also have an app available.  What's the difference between Earth and the standard Maps app?  (I assume better Street View access for one?)

On the PC, I just use Google Maps in the browser, and not the Google Earth program.  I see others open it and watch it zoom in from space every time, and I think "I don't have time for that nonsense..."


Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 18, 2014, 11:13:36 PM
Main difference between the Earth app and the Maps app is Earth doesn't offer the "map" view, just "hybrid" or "satellite."
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on October 19, 2014, 12:31:54 AM
Quote from: 1995hoo on October 18, 2014, 11:13:36 PM
Main difference between the Earth app and the Maps app is Earth doesn't offer the "map" view, just "hybrid" or "satellite."
I just installed both on the Ipad.  I don't like Earth much so far due to the rotation/3D being integrated directly into the navigation.  It makes it cumbersome when I have to deal with rotation as well on a touchscreen device, unless there is a way to lock it to North, as with Maps.  In other words, how do I get Earth to act like Maps?  The hybrid / roadway display isn't all that great either (would prefer to have just maps).  On the plus side, pegman/Street View seems better integrated - more like the standard version I'm used to using a PC browser.

The Google Maps app is more like the Safari browser version I'm used to.  However, I discovered that I can drop a pin on any road, and then click on the location box to access GSV (unlike Safari which only lets you click a named location).  Unfortunately, it requires a couple of steps, and I don't have the little map available as an inset to see where I'm at while in GSV.  I prefer to see them both as with on the PC to see my direction.  I don't understand why it is so hard for Google to just have the Pegman always displayed in a corner like the PC browser version, so that I can click to see what GSV is available. 
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on October 19, 2014, 09:45:38 AM
I never knew you could do street view on the Google Earth app. But I just downloaded Google Earth on my iPhone, so Im going to see what it's like.  :-P
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 19, 2014, 11:11:49 AM
Quote from: Roadrunner75 on October 19, 2014, 12:31:54 AM
....

The Google Maps app is more like the Safari browser version I'm used to.  However, I discovered that I can drop a pin on any road, and then click on the location box to access GSV (unlike Safari which only lets you click a named location).  Unfortunately, it requires a couple of steps, and I don't have the little map available as an inset to see where I'm at while in GSV.  I prefer to see them both as with on the PC to see my direction.  I don't understand why it is so hard for Google to just have the Pegman always displayed in a corner like the PC browser version, so that I can click to see what GSV is available. 


I had no idea you could do that! Thanks for the info. I just tried it around the corner from our house and it took me a minute to understand what I needed to do, but sure enough, when I figured it out, there was my RX-7.

For viewing a single location, that's probably easier than the Earth app, and it uses fewer system resources. Thanks for explaining. I still don't see a way to get a Street View link for use here on the forum, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 19, 2014, 03:31:40 PM
At work I've had the issue where, instead of loading street view, I would just get a black screen where the imagery should be, and the location is not identified outside of the mini-map, but it otherwise functions normally.  This is also connected to times when Google would refuse to finish downloading the imagery and patches would be blurry forever.  I've never had Google Maps crash on any computer though, which is interesting as my copies of Chrome on my desktop and work computer both like to go "aw snap" at random intervals.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on October 19, 2014, 04:14:32 PM
Has anyone noticed that there is now a darker shade for (some) freeway-to-freeway interchanges? Look here:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FfmO96wt.png&hash=59594ca1beed65aade32016ece1cf1d385934a87)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fw7J11NR.png&hash=3ef6d7ccabf542a1c2d0ee1e89158ff5d4c30f46)

However, there are plenty of cases where this is not illustrated:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FrPYtIhP.png&hash=6a0317db619072bec2ff15ff9fb58217e1d3afc4)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FtBY8ar7.png&hash=d8a8972a82e5421bf9b95d8d4b278377ff82e500)
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on October 19, 2014, 04:22:22 PM
Quote from: Zeffy on October 19, 2014, 04:14:32 PM
Has anyone noticed that there is now a darker shade for (some) freeway-to-freeway interchanges? Look here:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FfmO96wt.png&hash=59594ca1beed65aade32016ece1cf1d385934a87)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fw7J11NR.png&hash=3ef6d7ccabf542a1c2d0ee1e89158ff5d4c30f46)

However, there are plenty of cases where this is not illustrated:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FrPYtIhP.png&hash=6a0317db619072bec2ff15ff9fb58217e1d3afc4)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FtBY8ar7.png&hash=d8a8972a82e5421bf9b95d8d4b278377ff82e500)
Hm. I have not noticed that. I have not a clue how they'd determine what shade the exit ramps be. That is very odd indeed.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on October 19, 2014, 04:37:01 PM
There's something that I call a "Google Partial Freeway". Before yellow roads became white (remember when that happened?), all Google Partial Freeways looked like freeways. Then when yellow roads turned white, they looked like light orange roads (just like major surface roads that did not turn white). Now they're freeway-colored again.

These are usually full freeways in the United States, but in other countries, where they are much more common, they are usually not freeways.

Examples of Google Partial Freeways in the northeastern US and Canada:

MA 2 in its western freeway section (exits 14 to 43)
Eastern 10 miles of US 44
Nova Scotia 101
Nova Scotia 103
US 1 in Maine from Brunswick to Bath
Taconic State Parkway
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on October 19, 2014, 04:42:22 PM
Some unpaid sucker probably has to set the 'freeway-to-freeway' flag.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on October 19, 2014, 11:09:42 PM
Quote from: 1995hoo on October 19, 2014, 11:11:49 AM
Quote from: Roadrunner75 on October 19, 2014, 12:31:54 AM
....
The Google Maps app is more like the Safari browser version I'm used to.  However, I discovered that I can drop a pin on any road, and then click on the location box to access GSV (unlike Safari which only lets you click a named location).  Unfortunately, it requires a couple of steps, and I don't have the little map available as an inset to see where I'm at while in GSV.  I prefer to see them both as with on the PC to see my direction.  I don't understand why it is so hard for Google to just have the Pegman always displayed in a corner like the PC browser version, so that I can click to see what GSV is available. 
I had no idea you could do that! Thanks for the info. I just tried it around the corner from our house and it took me a minute to understand what I needed to do, but sure enough, when I figured it out, there was my RX-7.

For viewing a single location, that's probably easier than the Earth app, and it uses fewer system resources. Thanks for explaining. I still don't see a way to get a Street View link for use here on the forum, though.
Update:  GSV via the Google Maps app on the Ipad isn't actually that bad.  Nowhere near the PC (via browser), but I've gotten used to it and I can toggle between maps and GSV pretty quickly now.  Didn't see the Street View web link yet though, as also noted above.  If I get that, I'm in business for posting GSV here from the Ipad.

Title: Re: Google Maps just fucking SUCKS now
Post by: signalman on October 22, 2014, 04:58:53 PM
I was just forced into the new google maps yesterday.  Now I see what all the complaints are about.  What a useless piece of dog shit!  It's absolutely horrible and as soon as I try to move in any direction or zoom in or out it locks up and says it's loading.  What a shame too, I used to love google maps and the ability to drop into street view whenever I wanted; provided it had been driven by the street car.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on October 22, 2014, 05:29:25 PM
Quote from: signalman on October 22, 2014, 04:58:53 PM
I was just forced into the new google maps yesterday.
??? The old one's still there.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on October 22, 2014, 06:15:38 PM
Used to be: https://maps.google.com (nothing after it)

Now (for about a week): https://maps.google.com/maps?output=classic&dg=brw

Typing the first one into my address bar will redirect to the second one.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on October 22, 2014, 06:18:58 PM
Quote from: signalman on October 22, 2014, 04:58:53 PM
I was just forced into the new google maps yesterday.  Now I see what all the complaints are about.  What a useless piece of dog shit!  It's absolutely horrible and as soon as I try to move in any direction or zoom in or out it locks up and says it's loading.  What a shame too, I used to love google maps and the ability to drop into street view whenever I wanted; provided it had been driven by the street car.

In the lower right corner, there's a question mark.  Clicking that will reveal the option "Return to classic Google Maps".  Don't bother checking anything - just click the link.
Title: Re: Google Maps just fucking SUCKS now
Post by: Alex on October 22, 2014, 06:20:52 PM
FWIW, I noticed today if you search for a county, the county is outlined in white now instead of with hash marks the way city limits are.
Title: Re: Google Maps just fucking SUCKS now
Post by: Pete from Boston on October 22, 2014, 09:44:28 PM

Quote from: NE2 on October 22, 2014, 05:29:25 PM
Quote from: signalman on October 22, 2014, 04:58:53 PM
I was just forced into the new google maps yesterday.
??? The old one's still there.

Reminds me of the commercials against expanding bottle deposits to water and juice that use the phrase "forced deposits" in a way that would make as much sense to use in "forced driver's licenses" and "forced stealing ban." 

In any case, yes, Google realizes lots of people aren't falling for it, so it's only fake-forced.
Title: Re: Google Maps just fucking SUCKS now
Post by: signalman on October 23, 2014, 02:40:34 AM
Thanks for your help, 1 and Jeff.  I didn't realize how easy it was to get back to classic Google Maps.  Of course, I'm not very computer savvy either, despite my not being very old.  It was probably mentioned upthread, but I hadn't been reading this thread since it didn't seem to affect me.  In any case, I appreciate the help and am grateful that I didn't lose what I knew and loved.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on October 23, 2014, 07:42:15 AM
You know, some discussion earlier in the thread made me realize that although Google Streetview was the first and is still the gold standard in terms of raw coverage, it would be pretty easy to improve upon. Streetview is plagued with problems like bad stitching between images and ridiculously high false-positive rates on their face-blurring algorithm that make reading some signs (not just guide signs, but things like speed limits and business signs) difficult to impossible. A lot of Google coverage is probably never really viewed, in any case. I'd settle for 100% coverage in urban areas and just state highways outside of them if it meant less stupid blurring.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 23, 2014, 08:26:22 AM
I've always wondered why on some roads the Street View image suddenly goes to a grainy black, as though a car were being driven at night with just the parking lights.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on October 23, 2014, 09:12:01 AM
Quote from: 1995hoo on October 23, 2014, 08:26:22 AM
I've always wondered why on some roads the Street View image suddenly goes to a grainy black, as though a car were being driven at night with just the parking lights.

I don't think I've ever seen night street view on any newer higher definition images, but I remember several years ago on my first days on Google Maps, I-24 Westbound in downtown Chattanooga was street view apparently done at night IIRC. I think I had occasionally seen street view done at night in other places, but I haven't seen anything like that in a looong time. One annoying thing was the occasional crappy street view where you could not see anything, and the whole screen looks like a unicorn barfed on the street view car, LOL. In other words, the whole screen had a bunch of rainbow colors and you literally couldn't see anything.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on October 23, 2014, 09:22:00 AM
I hate when they capture the sun blare making it totally blurry do to the bright sun.  Then the ones that use both old and new captions together when you virtually drive along a road to go alternatively between one image to another is one that makes me almost want to scream.

It may suck, but at least it serves its purpose.  I may not like the way you cannot see everything, but something is better than nothing especially when you want to see a place you have not been to ever or in a long time.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeek2500 on October 23, 2014, 10:03:58 PM
Quote from: adventurernumber1 on September 25, 2014, 09:36:13 PM
Quote from: NE2 on September 25, 2014, 09:04:41 PM
Quote from: Roadgeek2500 on September 25, 2014, 07:53:23 PM
I may have found a good Gmaps replacement, HERE maps. They are the people who make the maps for all Garmin devices. Check it out. here.com (http://here.com)
If it doesn't have street view, it's not even in the running as a replacement.

I tried it out. I wasn't on there long enough to really check it out, but it has some fairly good maps, and it actually does have street view, and it's the only site I've ever seen that has it besides Google Maps. But you must have Google Chrome to use it, and when you try to get street view, the only available street view I saw was clustered in urban areas across the U.S.

EDIT: Here Maps could possibly be on the rise to become a pretty rad website.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi1294.photobucket.com%2Falbums%2Fb619%2Fkherm2000%2FCapture_zps017381f1.png&hash=6a2263a26d2469cb4f44c9396f6d1728613ef0c5) (http://s1294.photobucket.com/user/kherm2000/media/Capture_zps017381f1.png.html)
Works in IE11 just fine
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on October 27, 2014, 09:53:56 PM
Giant CAT appears on Google Maps - but Google don't know how it got there:
http://www.mirror.co.uk/news/weird-news/giant-cat-appears-google-maps-4516293 (http://www.mirror.co.uk/news/weird-news/giant-cat-appears-google-maps-4516293)

Lol :bigass:
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on October 27, 2014, 10:50:51 PM
Quote from: billtm on October 27, 2014, 09:53:56 PM
Giant CAT appears on Google Maps - but Google don't know how it got there:
http://www.mirror.co.uk/news/weird-news/giant-cat-appears-google-maps-4516293 (http://www.mirror.co.uk/news/weird-news/giant-cat-appears-google-maps-4516293)

Lol :bigass:

If you read the article, it's clear how it got there.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 28, 2014, 07:44:24 AM
Quote from: NE2 on October 27, 2014, 10:50:51 PM
Quote from: billtm on October 27, 2014, 09:53:56 PM
Giant CAT appears on Google Maps - but Google don't know how it got there:
http://www.mirror.co.uk/news/weird-news/giant-cat-appears-google-maps-4516293 (http://www.mirror.co.uk/news/weird-news/giant-cat-appears-google-maps-4516293)

Lol :bigass:

If you read the article, it's clear how it got there.

And if YOU read the article, it clearly says Google's unsure how it got there. The prior description of the article was accurate.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on October 28, 2014, 07:58:17 AM
Google's probably sure by now. But Hoo's OK with tabloid headlines, so who am I to question them?
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 28, 2014, 10:16:04 AM
Quote from: NE2 on October 28, 2014, 07:58:17 AM
Google's probably sure by now. But Hoo's OK with tabloid headlines, so who am I to question them?

Do you have some kind of problem that causes you to engage in stupid pissing matches?
Title: Re: Google Maps just fucking SUCKS now
Post by: Billy F 1988 on October 28, 2014, 02:11:39 PM
The person must have been just flat-ass bored as hell to come up with the cat outline...while in Photoshop! It's clearly a hoax deal. Someone clipped a portion of a map, drew the cat on the map itself and advertised it as if there was a giant kitty on GMaps. Look at it again in reality. It's not there. Again, it's a hoax.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on October 28, 2014, 02:37:25 PM
Quote from: Billy F 1988 on October 28, 2014, 02:11:39 PM
The person must have been just flat-ass bored as hell to come up with the cat outline...while in Photoshop! It's clearly a hoax deal. Someone clipped a portion of a map, drew the cat on the map itself and advertised it as if there was a giant kitty on GMaps. Look at it again in reality. It's not there. Again, it's a hoax.
Its not there anymore because Google deleted it. You know you can edit Google maps right?
Title: Re: Google Maps just fucking SUCKS now
Post by: Billy F 1988 on October 28, 2014, 05:09:17 PM
Who cares about editing in GMaps? The functionality is crummy at best. Perhaps that said person used GMaps itself to draw the cat, but it still was Photoshopped in some fashion with the screen capture and crop. As long as I'm around, the GMaps cat is as good as dead. Nine lives my bucket of bolts (to put it nicely)!
Title: Re: Google Maps just fucking SUCKS now
Post by: kj3400 on October 28, 2014, 05:26:58 PM
Are we really getting mad over a digital drawing of a cat?
Title: Re: Google Maps just fucking SUCKS now
Post by: Pete from Boston on October 28, 2014, 05:37:49 PM

Quote from: kj3400 on October 28, 2014, 05:26:58 PM
Are we really getting mad over a digital drawing of a cat?

I don't think so.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on October 28, 2014, 07:54:36 PM
Slow emotion day.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 29, 2014, 12:58:36 PM
Quote from: kj3400 on October 28, 2014, 05:26:58 PM
Are we really getting mad over a digital drawing of a cat?
I think he's getting mad over the existence of print screen and image cropping.
Title: Re: Google Maps just fucking SUCKS now
Post by: kj3400 on October 29, 2014, 05:57:06 PM
Oh. Well we all have our peeves.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on December 15, 2014, 02:28:53 PM
Sorry for the bump, but I reverted back to classic Google Maps just now. I don't know what Google did, but even on Internet Explorer, which ironically was the best out of my three browsers for using Google Maps, it was just running too slow for me to handle. It would often take about 10 seconds for it to actually load in the first place, then street view was choppy, the images were sometimes not rendering at all, the map movement was so erratic that it angered me trying to scroll across the United States and had to suffer periods of smooth transitions turning into periods of delayed loading.

First time back on classic Google Maps and it runs literally 20 times faster. I have had no delays at all on the old version. I don't know why I didn't switch back earlier.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on December 15, 2014, 08:52:37 PM
Now that I've finally gotten used to the new google maps, I actually like it better than the old Google Maps. The best thing about it that it is a lot easier to move around in streetview since you can click on blue on the map in the bottom left corner.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on December 15, 2014, 08:59:54 PM
Funny thing for me is I had it set to the old interface because the new one was too slow, but for some reason it recently switched back to the new style (I assume I probably clicked a link somewhere on this forum) and I'm finding the new one seems to be a lot faster now than it was before. I haven't been motivated to change it again yet. I'm running Waterfox, a 64-bit version of Firefox.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on December 15, 2014, 09:01:44 PM
Quote from: 1995hoo on December 15, 2014, 08:59:54 PM
Funny thing for me is I had it set to the old interface because the new one was too slow, but for some reason it recently switched back to the new style (I assume I probably clicked a link somewhere on this forum) and I'm finding the new one seems to be a lot faster now than it was before. I haven't been motivated to change it again yet. I'm running Waterfox, a 64-bit version of Firefox.

Same here. They must've fixed whatever was causing it to run so slow.
Title: Re: Google Maps just fucking SUCKS now
Post by: connroadgeek on December 24, 2014, 08:33:01 AM
I hate it. Everything is hard to find. These tech companies keep making it harder and harder to use their "features" because they hide them under ambiguous icons or try to be smart about selectively showing what is available. How about just having simple textual buttons that just say "turn on traffic" "turn on terrain", etc. instead of hiding it and making it contextual where it is not obvious that something is not available or just not available at this zoom level for example. The best interface designs are the ones that are consistent and obvious. Google's is neither of these things.
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on December 24, 2014, 10:22:53 AM
Quote from: connroadgeek on December 24, 2014, 08:33:01 AM
I hate it. Everything is hard to find. These tech companies keep making it harder and harder to use their "features" because they hide them under ambiguous icons or try to be smart about selectively showing what is available. How about just having simple textual buttons that just say "turn on traffic" "turn on terrain", etc. instead of hiding it and making it contextual where it is not obvious that something is not available or just not available at this zoom level for example. The best interface designs are the ones that are consistent and obvious. Google's is neither of these things.

I agree, there was nothing wrong with the old Maps.  It's like they think: if it ain't broke fix it until it is.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on December 24, 2014, 02:57:39 PM
At least they have an option that lets you go back to the old Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on December 24, 2014, 03:32:15 PM
I hate it with how when you try to click on a certain place to go into street view, it thinks you're clicking 56456345 miles down the road.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on December 24, 2014, 03:41:11 PM
Quote from: freebrickproductions on December 24, 2014, 03:32:15 PM
I hate it with how when you try to click on a certain place to go into street view, it thinks you're clicking 56456345 miles down the road.

I've actually had this same problem. I don't know what causes it.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on December 24, 2014, 03:46:59 PM
Quote from: US 41 on December 24, 2014, 03:41:11 PM
Quote from: freebrickproductions on December 24, 2014, 03:32:15 PM
I hate it with how when you try to click on a certain place to go into street view, it thinks you're clicking 56456345 miles down the road.

I've actually had this same problem. I don't know what causes it.
I think sometimes it's caused by Google thinking that you're trying to street view the nearest building along the road. I don't know what causes it the other times though.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 24, 2014, 05:10:05 PM
Quote from: freebrickproductions on December 24, 2014, 03:46:59 PM
Quote from: US 41 on December 24, 2014, 03:41:11 PM
Quote from: freebrickproductions on December 24, 2014, 03:32:15 PM
I hate it with how when you try to click on a certain place to go into street view, it thinks you're clicking 56456345 miles down the road.

I've actually had this same problem. I don't know what causes it.
I think sometimes it's caused by Google thinking that you're trying to street view the nearest building along the road. I don't know what causes it the other times though.
Yeah, most street view "bugs" we find are probably the result of roadgeeks NOT being the target audience.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 24, 2014, 05:52:42 PM
Quote from: vdeane on December 24, 2014, 05:10:05 PM
Quote from: freebrickproductions on December 24, 2014, 03:46:59 PM
Quote from: US 41 on December 24, 2014, 03:41:11 PM
Quote from: freebrickproductions on December 24, 2014, 03:32:15 PM
I hate it with how when you try to click on a certain place to go into street view, it thinks you're clicking 56456345 miles down the road.

I've actually had this same problem. I don't know what causes it.
I think sometimes it's caused by Google thinking that you're trying to street view the nearest building along the road. I don't know what causes it the other times though.
Yeah, most street view "bugs" we find are probably the result of roadgeeks NOT being the target audience.

Yep. This has happened a million times. In fact, now that I think deeply about it, I can not remember ONE time since the new Google Maps (not one) that I tried to get on Interstate X, and it didn't put me on a frontage road or nearby neighborhood road. I guess I've gotten so used to the annoying thing I always just automatically go to the mini-map and find my way back to the interstate or freeway  :-D :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on December 31, 2014, 12:23:55 PM
Google Map Maker is a complete steaming pile of shit, filled with errors, runs slow, and the default response every time is "We're sorry but your edit was declined because our information is better"  It's so bad now you can't make a single edit without an error that prevents any changes at all, you report it to their coders and they do nothing but say "I'm sorry for the late response, but we will look into it" they then precede to do nothing. 
Title: Re: Google Maps just fucking SUCKS now
Post by: Pete from Boston on December 31, 2014, 12:30:04 PM

Quote from: silverback1065 on December 24, 2014, 10:22:53 AM
Quote from: connroadgeek on December 24, 2014, 08:33:01 AM
I hate it. Everything is hard to find. These tech companies keep making it harder and harder to use their "features" because they hide them under ambiguous icons or try to be smart about selectively showing what is available. How about just having simple textual buttons that just say "turn on traffic" "turn on terrain", etc. instead of hiding it and making it contextual where it is not obvious that something is not available or just not available at this zoom level for example. The best interface designs are the ones that are consistent and obvious. Google's is neither of these things.

I agree, there was nothing wrong with the old Maps.  It's like they think: if it ain't broke fix it until it is.

It's Google.  Their whole M.O. is continual replacement with whole new versions of things.  This is to be understood when choosing to use their products.  If you want very little change over many years, perhaps Apple can come out with a map site.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 31, 2014, 01:48:08 PM
Quote from: silverback1065 on December 31, 2014, 12:23:55 PM
Google Map Maker is a complete steaming pile of shit, filled with errors, runs slow, and the default response every time is "We're sorry but your edit was declined because our information is better"  It's so bad now you can't make a single edit without an error that prevents any changes at all, you report it to their coders and they do nothing but say "I'm sorry for the late response, but we will look into it" they then precede to do nothing.

I have turned CT 6 into US 6 successfully.
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on December 31, 2014, 01:49:44 PM
Quote from: 1 on December 31, 2014, 01:48:08 PM
Quote from: silverback1065 on December 31, 2014, 12:23:55 PM
Google Map Maker is a complete steaming pile of shit, filled with errors, runs slow, and the default response every time is "We're sorry but your edit was declined because our information is better"  It's so bad now you can't make a single edit without an error that prevents any changes at all, you report it to their coders and they do nothing but say "I'm sorry for the late response, but we will look into it" they then precede to do nothing.

I have turned CT 6 into US 6 successfully.
I've had no luck i keep getting these bizzare errors like "this road has an address but no name" and "failed geodata" etc
Title: Re: Google Maps just fucking SUCKS now
Post by: MillTheRoadgeek on January 31, 2015, 09:23:05 PM
One thing I've noticed when highlighting things on Street View is that most of the time, it's basically invisible (gray) for the roads with available SV, but it's also yellow sometimes (not the roads, but the covered lines).
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on February 01, 2015, 03:55:09 AM
I use the new version occasionally, particularly for old Street View imagery.  I don't have problems with it, but I don't use it enough to know if I really like it. The deal-killer for me is that it puts each individual map and Street View image in the browser history with a unique URL.  I don't want my history filled with a billion different Google Maps views.  For this reason, I use the new version only in a different browser.  I think there's some privacy mode that will keep my primary browser from recording history, but it's annoying to use and I wouldn't want to forget to turn it on or off.  For most use, I go to a bookmark for the old version.
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on February 01, 2015, 01:03:01 PM
So I bit the bullet and have slowly transitioned over to the new Google Maps. I've gotten sick of my browser forgetting my preference and having to go through the motions of going back to the classic maps. It appears to be a bit faster than I remember. I still don't like not being able to turn off road names, but I did discover one new feature I do like: It will automatically display weather warnings for the area you're in. I do wish I could permanently close the damned photo tour. I find the included measurement tool to be nicer than the Google Labs add-on for the classic maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on February 01, 2015, 02:05:08 PM
I noticed now that sometimes you go to street view and the image goes black.

Plus I had the experience of the map moving, but not the image on the satellite view.  In other words the route and street outline would move as you grabbed the image, but the whole base underneath it stayed put.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 01, 2015, 02:19:49 PM
Quote from: wxfree on February 01, 2015, 03:55:09 AM
I think there's some privacy mode that will keep my primary browser from recording history, but it's annoying to use and I wouldn't want to forget to turn it on or off.
Let me guess: Safari?

IE, Firefox (current versions), and Chrome all implement private browsing as a separate session in a different window that runs alongside the regular session.  Safari, on the other hand, is just a checkbox in a menu, and didn't even include an indication that the session was private until 2012.  Opera runs private tabs in the same window as other tabs.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on February 01, 2015, 03:01:12 PM
Quote from: vdeane on February 01, 2015, 02:19:49 PM
Quote from: wxfree on February 01, 2015, 03:55:09 AM
I think there's some privacy mode that will keep my primary browser from recording history, but it's annoying to use and I wouldn't want to forget to turn it on or off.
Let me guess: Safari?

IE, Firefox (current versions), and Chrome all implement private browsing as a separate session in a different window that runs alongside the regular session.  Safari, on the other hand, is just a checkbox in a menu, and didn't even include an indication that the session was private until 2012.  Opera runs private tabs in the same window as other tabs.

I use Firefox.  I'd never used a private session window or known how it works until just now.  I use new Google Maps in Chrome, which I can't stand as a primary browser because the address bar doesn't give a drop-down list, which is my usual means of navigation.  The private window is actually pretty easy to use.  There's a right-click option to open links in a private window, which is something I'll probably use for the links here so I can move the maps around without big blocks of history entries.  Thanks for getting me to look at that.  A lot of new features I just reject offhand because I hadn't known enough to want them before.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 01, 2015, 08:30:07 PM
Quote from: wxfree on February 01, 2015, 03:55:09 AM
I use the new version occasionally, particularly for old Street View imagery.
Sweet - didn't realize they had that. Preserved for posterity:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FEwVja0V.png&hash=8873a8459d25959dd51805aec93a9163af2c6ac9) (http://www.google.com/maps/@29.495549,-82.293755,3a,75y,72.41h,88.98t/data=!3m5!1e1!3m3!1sXO7TwGZ0OeQgi4p3S8vphQ!2e0!5s20080301T000000)

...and holy crap, if I click that link I see the old imagery in the old interface. There doesn't seem to be any other way to reach it, however.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on February 02, 2015, 09:20:34 AM
What I hate the most about the new Google Maps is that you can't make the satellite view the default view like you could on the old version.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on February 07, 2015, 01:34:34 PM
This is just a general issue (annoyance) I have with Google Maps. Any street view in the United States 2009 or older is awful. It's always blurry. I have no clue why because in Mexico there are images taken from 2008 and they are perfectly clear.

Another thing that annoys me is that in Mexico they will take new images of a road they already had street view of and then they will not take pictures of a road that is brand new, but was open at the time they went through. A perfect example of this is the toll bypass on the northwest side of Saltillo. And Most of the Monterrey toll bypass has no street view on it either. Also there is new streetview on the 40 libre between Durango and El Salto from November 2014, but they neglected to take streetview of the new autopista between El Salto and Mazatlan. Why would you neglect to take street view of maybe the neatest road in the continent?

Also they are sometimes slow to show updates. A new toll bypass around Torreon and Gomez Palacio opened several months ago and it is still not shown. 

With all these annoyances I still love google maps and their streetview, but sometimes I wish they would be faster to update and show new roads on streetview.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 07, 2015, 02:42:42 PM
I always switch back to the "old" Google Maps when using a PC.  I have no issues with it, but don't like using the "new" Google Maps because GSV is less intuitive for me and it's harder to jump multiple zoom levels.  However, Google Maps does tend to crash fairly often on my Android phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-39 on February 09, 2015, 07:25:26 PM
Whenever I use it, it runs slow, sometimes it doesn't go on street view when I drag the guy on the blue line the first time, and then I may have to refresh the page if it is not working right. It is really annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 10, 2015, 10:03:04 PM
Quote from: US 41 on February 07, 2015, 01:34:34 PM
Another thing that annoys me is that in Mexico they will take new images of a road they already had street view of and then they will not take pictures of a road that is brand new, but was open at the time they went through.
They probably autogenerated directions for the guy to drive to cover whatever was on their maps, and they hadn't yet added the new bypass. The same thing happened with the US 167 bypass of Sheridan, AR.
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on February 10, 2015, 11:07:58 PM
Quote from: US 41 on February 07, 2015, 01:34:34 PM
Also they are sometimes slow to show updates. A new toll bypass around Torreon and Gomez Palacio opened several months ago and it is still not shown. 
If you're not interested in mapping it yourself, at least use the Report Problem link at the bottom to tell them the new road is open. They can use GPS data they have collected to at least do a halfassed job of putting it on the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on February 11, 2015, 12:51:59 AM
Quote from: dfwmapper on February 10, 2015, 11:07:58 PM
Quote from: US 41 on February 07, 2015, 01:34:34 PM
Also they are sometimes slow to show updates. A new toll bypass around Torreon and Gomez Palacio opened several months ago and it is still not shown. 
If you're not interested in mapping it yourself, at least use the Report Problem link at the bottom to tell them the new road is open. They can use GPS data they have collected to at least do a halfassed job of putting it on the map.

Consider yourself lucky if they even do a half-assed job if you use the Report Problem. My experience: I used that link to report an interchange that was reconfigured, since I couldn't get the map maker editor to show the changes correctly. So I used the Report Problem link and simply directed them to their latest satellite photo that showed the new ramp configuration. Weeks later, I got an email stating that they couldn't understand the problem. I swear a room full of monkeys could have figured it out. :banghead:  Overlay old map on new photo. Trace photo. Done.

Between things like that and allowing people approving/denying map edits that have no clue about the area, I've given up trying to improve Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on February 11, 2015, 02:30:45 AM
Quote from: dfwmapper on February 10, 2015, 11:07:58 PM
Quote from: US 41 on February 07, 2015, 01:34:34 PM
Also they are sometimes slow to show updates. A new toll bypass around Torreon and Gomez Palacio opened several months ago and it is still not shown. 
If you're not interested in mapping it yourself, at least use the Report Problem link at the bottom to tell them the new road is open. They can use GPS data they have collected to at least do a halfassed job of putting it on the map.

I actually did that (reported the problem) a month ago and finally yesterday, they added the new bypass around Torreon. Maybe it was me telling them or maybe they finally just figured it out.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 13, 2015, 06:10:54 PM
Motherfucker: "this version of Google Maps is updating soon"
http://productforums.google.com/forum/#!topic/maps/nNQTsfCcgbk
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on February 13, 2015, 06:34:02 PM
Quote from: NE2 on February 13, 2015, 06:10:54 PM
Motherfucker: "this version of Google Maps is updating soon"
http://productforums.google.com/forum/#!topic/maps/nNQTsfCcgbk

I switched to the new Google Maps in Chrome after my Firefox experienced some weird glitches. It runs very smooth now, with the exception of Street View. Still, I'd rather not see classic go away just yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 13, 2015, 06:51:31 PM
New is still clunky for me in Firefox. No, I'm not switching to Chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 14, 2015, 12:38:57 AM
Quote from: NE2 on February 13, 2015, 06:10:54 PM
Motherfucker: "this version of Google Maps is updating soon"
I saw this again and managed to click the link before it disappeared. It leads here:
http://support.google.com/maps/?p=mfe_deprecation&hl=en#topic=3092425
The text here implies classic will still exist, but that could just be sloppiness in failing to update.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on April 19, 2015, 03:37:26 PM
https://www.google.com/maps/@42.099022,-75.786863,3a,75y,136.79h,90t/data=!3m4!1e1!3m2!1syr1oJYzUfUSB988vPYB0UQ!2e0

What is this supposed to be?  Most of all why is google allowing it to be shown in street view?
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on April 19, 2015, 04:34:53 PM
Quote from: roadman65 on April 19, 2015, 03:37:26 PM
https://www.google.com/maps/@42.099022,-75.786863,3a,75y,136.79h,90t/data=!3m4!1e1!3m2!1syr1oJYzUfUSB988vPYB0UQ!2e0

What is this supposed to be?  Most of all why is google allowing it to be shown in street view?

All right, which one of you jokers divided by zero?
Title: Re: Google Maps just fucking SUCKS now
Post by: Bickendan on April 19, 2015, 07:43:53 PM
Quote from: DeaconG on April 19, 2015, 04:34:53 PM
Quote from: roadman65 on April 19, 2015, 03:37:26 PM
https://www.google.com/maps/@42.099022,-75.786863,3a,75y,136.79h,90t/data=!3m4!1e1!3m2!1syr1oJYzUfUSB988vPYB0UQ!2e0

What is this supposed to be?  Most of all why is google allowing it to be shown in street view?

All right, which one of you jokers divided by zero?

Wasn't me. I merely took the square root of -1.

Fixed quote. (https://www.aaroads.com/forum/index.php?topic=4000.0) - rmf67
Title: Re: Google Maps just fucking SUCKS now
Post by: MillTheRoadgeek on April 19, 2015, 08:26:07 PM
For some reason, Google is now not showing Street View/Photo Sphere/Look Inside dates outside the archive. I hope this is just a bug/they'll bring it back in a jiffy.
Title: Re: Google Maps just fucking SUCKS now
Post by: tribar on April 19, 2015, 09:15:23 PM
Google Earth will solve all your problems. 
Title: Re: Google Maps just fucking SUCKS now
Post by: Mileage Mike on April 21, 2015, 07:22:31 AM
Using a Mac.  For me it lags and freezes up often in Safari. It runs relatively smooth in Chrome but Chrome itself is an unoptimized resource hog on OS X.  Damned if I do damned if I don't.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on April 22, 2015, 11:35:23 AM
Quote from: NE2 on February 13, 2015, 06:51:31 PM
New is still clunky for me in Firefox. No, I'm not switching to Chrome.

Don't fret.  It's clunky in Chrome too.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on April 22, 2015, 12:06:10 PM
Quote from: tribar on April 19, 2015, 09:15:23 PM
Google Earth will solve all your problems. 
That is all we have right now.  If you virtually follow all of I-86 E Bound( Including the US 11 connection to I-86) from I-81 you get this. 
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on April 22, 2015, 12:13:50 PM
Still no problems in Canada's version on Chrome for me...
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on April 22, 2015, 02:28:26 PM
How do you drag a route to add a via point in lite mode?
[edit] what the fuck, that's turned off: http://support.google.com/maps/answer/6070247
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on April 22, 2015, 04:31:03 PM
Google is going to lose a lot of users over this fiasco. The new product is half baked at best and unusable at worst. Tech companies like to change things willy nilly even when the old version is perfectly good. Facebook does this all the time, and one day they're going to make a change that really pisses off a large segment of the users and they will leave Fashboot and go to another social media website in droves. That will be the beginning of the end of Facebook. Remember how big Myspace was at one time and how irrelevant it is now? That will be Facebook in x years. Also, Yahoo ruined Flickr when they went to the new layout and removed the paid subscription option. Why can't they leave well enough alone?
Title: Re: Google Maps just fucking SUCKS now
Post by: Bickendan on April 22, 2015, 07:11:30 PM
Because if they don't make changes people will leave!!!1!one
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 22, 2015, 09:17:59 PM
Interestingly, I have been able to add via points in lite mode... I wonder if that's why it can be unreliable at times.

I don't think Google will lose too many users for this, despite the outrage from the roadgeek community, most users are probably OK with the changes, since they never used the old interface as extensively as we have, and because the new interface works like a smartphone app.  Plus there's nowhere to go.  Bing is a joke and MapQuest and Yahoo remind people of the 90s.
Title: Re: Google Maps just fucking SUCKS now
Post by: tribar on April 23, 2015, 12:16:29 AM

Quote from: bugo on April 22, 2015, 04:31:03 PM
Google is going to lose a lot of users over this fiasco. The new product is half baked at best and unusable at worst. Tech companies like to change things willy nilly even when the old version is perfectly good. Facebook does this all the time, and one day they're going to make a change that really pisses off a large segment of the users and they will leave Fashboot and go to another social media website in droves. That will be the beginning of the end of Facebook. Remember how big Myspace was at one time and how irrelevant it is now? That will be Facebook in x years. Also, Yahoo ruined Flickr when they went to the new layout and removed the paid subscription option. Why can't they leave well enough alone?

I agree.  If it isn't broke, don't fix it. 
Title: Re: Google Maps just fucking SUCKS now
Post by: halork on April 23, 2015, 05:36:49 AM
Quote from: vdeane on April 22, 2015, 09:17:59 PM
Plus there's nowhere to go.  Bing is a joke and MapQuest and Yahoo remind people of the 90s.

True, but Google is now so degraded that it gives the others a good opportunity to close the gap.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on April 23, 2015, 08:18:53 AM
Quote from: halork on April 23, 2015, 05:36:49 AM
Quote from: vdeane on April 22, 2015, 09:17:59 PM
Plus there's nowhere to go.  Bing is a joke and MapQuest and Yahoo remind people of the 90s.

True, but Google is now so degraded that it gives the others a good opportunity to close the gap.

Not by a longshot.  I don't care for the new Google Maps, but, I'm getting used to it. 

This is sounding more and more like a grumpy old man club where no one wants anything to change ever!
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on April 23, 2015, 10:07:17 AM
Google is still way in the lead. None of the other mapping sites have streetview except Bing, but Bing is only in large (American?) cities at this point. Google streetview is everywhere.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 23, 2015, 10:13:47 AM
Here's something strange: For me, the new "Lite" mode redirects to Classic.

Quote from: US 41 on April 23, 2015, 10:07:17 AM
Google is still way in the lead. None of the other mapping sites have streetview except Bing, but Bing is only in large (American?) cities at this point. Google streetview is everywhere.

So Google is ahead in streetview, but other maps are ahead in other areas. Why not use Google for streetview and others for other times you need an online map? (Not counting those who are still able/required to use Classic)
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on April 23, 2015, 10:35:18 AM
I did some comparisons of the routings of US 64 and 79 in Memphis and West Memphis. None of the mapping services agreed with each other. Map Quest even shows US 64 following I-40 over the DeSoto bridge instead of crossing at the Memphis-Arkansas bridge which it has since 1949.

https://www.aaroads.com/forum/index.php?topic=15379.0
Title: Re: Google Maps just fucking SUCKS now
Post by: Bickendan on April 23, 2015, 11:01:14 AM
MapQuest should be mirroring OSM.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on April 23, 2015, 02:48:05 PM
Quote from: 1 on April 23, 2015, 10:13:47 AM
Here's something strange: For me, the new "Lite" mode redirects to Classic.

Quote from: US 41 on April 23, 2015, 10:07:17 AM
Google is still way in the lead. None of the other mapping sites have streetview except Bing, but Bing is only in large (American?) cities at this point. Google streetview is everywhere.

So Google is ahead in streetview, but other maps are ahead in other areas. Why not use Google for streetview and others for other times you need an online map? (Not counting those who are still able/required to use Classic)

That's exactly what I do.  Plus, Bing has a great bird's eye view in a lot of places whereas Google's bird's eye view now sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on April 23, 2015, 10:42:52 PM
Quote from: Brandon on April 23, 2015, 02:48:05 PM
Plus, Bing has a great bird's eye view in a lot of places whereas Google's bird's eye view now sucks.
Agreed.  I used to use Bing the most, primarily for the bird's eye view.  When Streetview really picked up, I switched over primarily to Google.  For awhile I would use both, sometimes simultaneously to look at the same area with bird's eye and GSV.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on April 24, 2015, 10:03:23 AM
Well, it's good for something...

https://www.google.com/maps/place/33%C2%B030%2752.5%22N+73%C2%B003%2733.2%22E/@33.5145689,73.0603892,15z/data=!4m2!3m1!1s0x0:0x0?hl=en
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on April 24, 2015, 10:47:20 AM
Quote from: formulanone on April 24, 2015, 10:03:23 AM
Well, it's good for something...

https://www.google.com/maps/place/33%C2%B030%2752.5%22N+73%C2%B003%2733.2%22E/@33.5145689,73.0603892,15z/data=!4m2!3m1!1s0x0:0x0?hl=en

That's great.  :D Wonder how long that will last before it gets revised.
Title: Re: Google Maps just fucking SUCKS now
Post by: mvak36 on April 24, 2015, 11:13:58 AM
Quote from: SignGeek101 on April 24, 2015, 10:47:20 AM
Quote from: formulanone on April 24, 2015, 10:03:23 AM
Well, it's good for something...

https://www.google.com/maps/place/33%C2%B030%2752.5%22N+73%C2%B003%2733.2%22E/@33.5145689,73.0603892,15z/data=!4m2!3m1!1s0x0:0x0?hl=en

That's great.  :D Wonder how long that will last before it gets revised.

Also this: https://goo.gl/maps/Eiq5A
:-D
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on April 24, 2015, 11:20:58 AM
I don't see anything.
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on April 24, 2015, 11:30:31 AM
Quote from: NE2 on April 24, 2015, 11:20:58 AM
I don't see anything.

Zoom in a little bit.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on April 24, 2015, 11:35:27 AM
Don't see anything either--what I see is a blank piece of land near Rawalpindi.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on April 24, 2015, 11:46:34 AM
Quote from: J N Winkler on April 24, 2015, 11:35:27 AM
Don't see anything either--what I see is a blank piece of land near Rawalpindi.

Welp, looks like Google found it. It was a "drawing" of an Android (the one Google uses for their phone OS) character urinating on an Apple logo.
Title: Re: Google Maps just fucking SUCKS now
Post by: mvak36 on April 24, 2015, 11:48:49 AM
Here was an article from earlier about what they had. http://www.theverge.com/2015/4/24/8489127/android-apple-google-maps-urinating-mascot
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 24, 2015, 12:26:44 PM
I see it now so it hasn't been taken away.

The second one is strange, I see parts of it, but some rectangles don't load.  Zooming in makes some load but not others.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on April 24, 2015, 12:59:16 PM
Quote from: kkt on April 24, 2015, 12:26:44 PMI see it now so it hasn't been taken away.

It has here.  I suspect you may still see it because of a delay propagating the change through a decentralized system.
Title: Re: Google Maps just fucking SUCKS now
Post by: bing101 on April 25, 2015, 07:15:28 PM
http://fox40.com/2015/04/24/the-android-apple-rivalry-gets-vulgar-in-google-maps/

Here is an update.
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on April 25, 2015, 07:31:51 PM
Quote from: bing101 on April 25, 2015, 07:15:28 PM
http://fox40.com/2015/04/24/the-android-apple-rivalry-gets-vulgar-in-google-maps/

Here is an update.

I think the news reporters are a little stupid not to realize that the Android is urinating on the apple, not "throwing a glass of water on it".

Perhaps they didn't want to say that on TV though.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on April 26, 2015, 05:31:29 PM
Even so-called 'lite mode' uses an insane amount of memory. Fuck you, Goog.
Title: Re: Google Maps just fucking SUCKS now
Post by: SSOWorld on April 27, 2015, 08:45:33 AM
Quote from: NE2 on April 24, 2015, 11:20:58 AM
I don't see anything.
Exactly! :ded:
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on April 28, 2015, 12:28:47 PM
Credit where credit is due: the 'schedule explorer' rocks.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FTK8OKmv.png&hash=ca3cea7daadeea7fa63d115d1cc52699003ab8f8)
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on May 01, 2015, 01:09:43 AM
Well, I'm not happy. Can't get to classic view anymore. For as advanced as my PC is, under Firefox, google maps is exceedingly slow and buggy. Switching to Classic worked. Lite works well, but has zero functionality that classic had (adding waypoints, moving the route, etc). So, what's the point?

I understand they're trying to make a one-size fits all map for both desktop, tablet, and phone users,... but classic worked fine.

This is the problem with google, or really any tech company. Instead of just updating something, it must be 'redesigned' as part of the update. Want to add something? Let's not just add it. Let's redesign the whole system as well. It makes it look like they're doing something.
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on May 01, 2015, 04:23:44 AM
Quote from: Sykotyk on May 01, 2015, 01:09:43 AM
Well, I'm not happy. Can't get to classic view anymore. For as advanced as my PC is, under Firefox, google maps is exceedingly slow and buggy. Switching to Classic worked. Lite works well, but has zero functionality that classic had (adding waypoints, moving the route, etc). So, what's the point?

https://www.google.com/lochp
Title: Re: Google Maps just fucking SUCKS now
Post by: tcorlandoinsavannah on May 02, 2015, 02:06:05 PM
Google Maps now officially sucks like a ten dollar whore on OBT!  Why did they ruin a good product?  Now it won't even let me revert to the "classic" mode.  And when you check off the reasons the new one sucks balls, and click return to classic, it brings up this horsecrap "Lite" mode.  Screw you and your offspring, Google!!!!
End rant.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 02, 2015, 02:12:54 PM
http://www.google.com/mapmaker

Is this close enough to Classic? The one disadvantage is that traffic cannot be viewed.

(To get directions, right-click "get directions from here" and "get directions to here")
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on May 02, 2015, 02:27:01 PM
Quote from: tcorlandoinsavannah on May 02, 2015, 02:06:05 PM
Google Maps now officially sucks like a ten dollar whore on OBT!  Why did they ruin a good product?  Now it won't even let me revert to the "classic" mode.  And when you check off the reasons the new one sucks balls, and click return to classic, it brings up this horsecrap "Lite" mode.  Screw you and your offspring, Google!!!!
End rant.
As noted above and on the other Google maps thread, you can still use one of the following:
https://www.google.com/lochp (https://www.google.com/lochp)
https://maps.google.com/maps?output=classi (https://maps.google.com/maps?output=classi)

Maybe we need a pinned, locked, one post thread at the top of "Off Topic" or other appropriate board called "How to still access Classic Google Maps", listing whatever current links work at the time and updated as necessary.  It seems important enough to forum use, due to all the map links posted.

Now, can someone give me an easy way, via modifying the URL to one of the above links, to revert to Classic once I've already clicked on a GSV/Map link in a thread?  I can access Classic directly by clicking on the above links, which will take me to my current default location.  However, if I click on a link on the forum, it will go to new maps, and once I'm there, there is no way that I can figure out yet how to modify the URL using one of the above links to refresh the page to Classic mode.  I'm just stuck with new maps or Lite mode at that point.


Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on May 03, 2015, 04:47:03 PM
I've noticed that in Lite Mode, Street View shows up with the annoying curve effect of a panorama, but this doesn't happen in regular mode. Anyone else notice this?
Title: Re: Google Maps just fucking SUCKS now
Post by: Billy F 1988 on May 03, 2015, 09:49:25 PM
What a pile of toxic garbage from Google, and yet, I use Chrome and GMaps is THE WORST CPU eater of all time. Even when my WiFi signal is at optimum strength, it'll lag when I load something there. And quite frankly, I don't want a fucked up Google Maps. I want Google to stop fucking around with it and screwing up routes that do or don't appear, incorrectly marking up routes on miles of road where it shouldn't belong, using the wrong marker, etc. In lamen terms: Google should stop fucking around with GMaps...PERIOD!!!
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on May 04, 2015, 01:06:08 PM
Quote from: Roadrunner75 on May 02, 2015, 02:27:01 PM
As noted above and on the other Google maps thread, you can still use one of the following:
https://www.google.com/lochp (https://www.google.com/lochp)
https://maps.google.com/maps?output=classi (https://maps.google.com/maps?output=classi)

Maybe we need a pinned, locked, one post thread at the top of "Off Topic" or other appropriate board called "How to still access Classic Google Maps", listing whatever current links work at the time and updated as necessary.  It seems important enough to forum use, due to all the map links posted.

Make it, and I will pin it (till the links no longer work of course).
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on May 04, 2015, 01:36:24 PM
Quote from: rickmastfan67 on May 04, 2015, 01:06:08 PM
Quote from: Roadrunner75 on May 02, 2015, 02:27:01 PM
As noted above and on the other Google maps thread, you can still use one of the following:
https://www.google.com/lochp (https://www.google.com/lochp)
https://maps.google.com/maps?output=classi (https://maps.google.com/maps?output=classi)

Maybe we need a pinned, locked, one post thread at the top of "Off Topic" or other appropriate board called "How to still access Classic Google Maps", listing whatever current links work at the time and updated as necessary.  It seems important enough to forum use, due to all the map links posted.

Make it, and I will pin it (till the links no longer work of course).
Thanks - I just posted it on this board.
I've also been trying to find a good way to modify the URL once you're already in new maps to revert the current map/GSV to Classic.  No luck yet...
Title: Re: Google Maps just fucking SUCKS now
Post by: Brian556 on May 06, 2015, 09:40:09 PM
I was looking at the OKC area during storms and Google maps now displays Storm Warnings for the area you are looking at
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on May 08, 2015, 11:12:27 AM
I've been using the new maps for a while so all the fuss over tricks to still access classic doesn't appeal to me.

That said it seems as time goes on, Google's graphics team is increasingly shitting its pants and just not even trying. Ever since Google stopped using NavTeq data they've been struggling to keep the colors of roads straight. There are always orange expressways, yellow freeways, and even white freeways out there. Now you also get shit like this (https://www.google.com/maps/@40.7546047,-73.9491956,17z), where I don't even know how that happens.

The latest blunder is they've eliminated the "M" logo they used to use for subway stops and just given them the same icon as other rail stations... thus rendering subway and commuter rail services indistinguishable from each other on the map. Nice job! Meanwhile certain cities like Boston still get special logos for their stations that match those used by the local transit agency.

The idea of putting a different border on roadways you can't use without paying a toll is actually a nice feature... if it were implemented properly. For example, Google does not at all properly identify where free rides are available on the Garden State Parkway. Relevant stupidity. (https://www.google.com/maps/@40.4247671,-74.2189558,17z) This isn't even a pair of ramps open to the public. :pan: Who the fuck is drawing these maps and why do they seem to have brain capacity on par with the average dopefish?
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on May 08, 2015, 11:27:04 AM
Quote from: Duke87 on May 08, 2015, 11:12:27 AM
For example, Google does not at all properly identify where free rides are available on the Garden State Parkway.

The Parkway is a bit unique in that while it's a toll road, there are many options where one can enter and exit without paying a toll, while the guy driving next to you will be paying a toll as he will continue past the point where you exit.  Marking the whole thing as a toll road is the proper way to show it because it is a toll road, even though not all users will need to pay a toll.

(Technically, one can use the NJ Turnpike's southern most mile without paying a toll as well)
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on May 08, 2015, 11:41:55 AM
Quote from: jeffandnicole on May 08, 2015, 11:27:04 AM
Marking the whole thing as a toll road is the proper way to show it because it is a toll road, even though not all users will need to pay a toll.
Completely wrong. Should the entire length of I-95/295 from Baltimore to the NJ Turnpike be marked as a toll road? It's all maintained with toll money.
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on May 08, 2015, 12:09:40 PM
There are a few places where free sections of otherwise tolled highways are marked properly, e.g. https://goo.gl/rf0j6R, but the majority are marked incorrectly. There's no user access to set the toll attribute, it has to be reported and set by Google's monkeys.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on May 08, 2015, 12:12:29 PM
Quote from: NE2 on May 08, 2015, 11:41:55 AM
Quote from: jeffandnicole on May 08, 2015, 11:27:04 AM
Marking the whole thing as a toll road is the proper way to show it because it is a toll road, even though not all users will need to pay a toll.
Completely wrong. Should the entire length of I-95/295 from Baltimore to the NJ Turnpike be marked as a toll road? It's all maintained with toll money.

Using toll money to maintain a road is clearly not the same thing as paying a toll to use a toll road.  Rt. 42 in NJ is maintained in part by the Atlantic City Expressway, even though it's clearly not a toll road.

Using DE's I-95 as an example, everyone on that road between Interchange 1 and MD's Interchange 109 must pay a toll, but no one entering and exiting between Interchanges 1 & 5 need to pay a toll.

On the GSP, someone that enters the GSP North from Interchange 67 and exits at Interchange 74 does not pay a toll, but someone entering from Interchange 69 and exits at Interchange 74 does pay a toll.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on May 08, 2015, 01:34:42 PM
Quote from: jeffandnicole on May 08, 2015, 12:12:29 PM
On the GSP, someone that enters the GSP North from Interchange 67 and exits at Interchange 74 does not pay a toll, but someone entering from Interchange 69 and exits at Interchange 74 does pay a toll.
The correct way to code this is to have the entrance at 69 marked as toll. It may not look right, but the alternative is to have it not give correct directions. Consider this route (http://www.google.com/maps/dir/39.7608619,-74.2579405/39.8661518,-74.2275261/@39.8235958,-74.2307482,12z/data=!4m4!4m3!2m1!2b1!3e0) from Barnegat to Forked River while avoiding tolls.

Perhaps an even better example: the GSP has always been free from Cape May to Cape May Court House. When the south-facing ramps at exit 4 were built, the GSP tolled them. But nothing else changed; the GSP remains free there if you don't use exit 4.

(PS: the 1955 topo shows that the GSP was originally two lanes on the current southbound side. Does this explain the weird left entrance at exit 13? [edit: yes it does])
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 08, 2015, 02:19:44 PM
And then there is the occasional $0.00 toll on a toll road (one example is I-88 to I-87 on the Thruway).
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on May 08, 2015, 05:51:43 PM
Quote from: 1 on May 08, 2015, 02:19:44 PM
And then there is the occasional $0.00 toll on a toll road (one example is I-88 to I-87 on the Thruway).

This particular example at least is impossible to map properly since the way it is set up is indeterminate. There is no particular segment of roadway that is free for everyone who uses it.

The best way to program this would be to create a virtual free roadway connecting exit 25A to exits 26, 25, and 24 that has all the same attributes as the actual Thruway roads but is marked as free and does not render graphically on the map. This allows any "avoid tolls" algorithm to use the available free rides on the Thruway without sacrificing geographic accuracy on the map.

But that's way too much to expect from a mapping team that just traces satellite photos and guesses at what class each road should be marked as. I can appreciate that Google wants all their map data to be their own intellectual property rather than having to pay royalties for it but they really need better QC.
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on May 08, 2015, 08:13:06 PM
Just wait. They're disabling the entire Map Maker service "temporarily" as of May 12, with no specified date on when it will be available again. They claim to be doing it so they can catch up on the backlog of edits that have accumulated since auto-publishing and user reviews were disabled after the spam incidents, but that excuse smells a little bullshitty to me and it won't shock me if it never comes back. If you think it's bad now, just wait until there's no way to unfuck it.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on May 08, 2015, 11:16:50 PM
Quote from: Duke87 on May 08, 2015, 05:51:43 PM
Quote from: 1 on May 08, 2015, 02:19:44 PM
And then there is the occasional $0.00 toll on a toll road (one example is I-88 to I-87 on the Thruway).

This particular example at least is impossible to map properly since the way it is set up is indeterminate.

No it's not. It's free between exits 24 and 25A and exits 25A and 26. The east-facing ramps at exit 25 are toll, as are the main lanes through exit 25A.
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on May 09, 2015, 02:42:57 AM
Quote from: NE2 on May 08, 2015, 11:16:50 PM
Quote from: Duke87 on May 08, 2015, 05:51:43 PM
Quote from: 1 on May 08, 2015, 02:19:44 PM
And then there is the occasional $0.00 toll on a toll road (one example is I-88 to I-87 on the Thruway).

This particular example at least is impossible to map properly since the way it is set up is indeterminate.

No it's not. It's free between exits 24 and 25A and exits 25A and 26. The east-facing ramps at exit 25 are toll, as are the main lanes through exit 25A.

Hmm. That's weird since it's totally different from how the toll plazas are actually placed, but you're right, it does work.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on May 16, 2015, 09:06:39 PM
Quote from: dfwmapper on May 08, 2015, 08:13:06 PM
Just wait. They're disabling the entire Map Maker service "temporarily" as of May 12, with no specified date on when it will be available again. They claim to be doing it so they can catch up on the backlog of edits that have accumulated since auto-publishing and user reviews were disabled after the spam incidents, but that excuse smells a little bullshitty to me and it won't shock me if it never comes back. If you think it's bad now, just wait until there's no way to unfuck it.
FML. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on May 20, 2015, 12:45:46 PM
Quote from: billtm on May 16, 2015, 09:06:39 PM
Quote from: dfwmapper on May 08, 2015, 08:13:06 PM
Just wait. They're disabling the entire Map Maker service "temporarily" as of May 12, with no specified date on when it will be available again. They claim to be doing it so they can catch up on the backlog of edits that have accumulated since auto-publishing and user reviews were disabled after the spam incidents, but that excuse smells a little bullshitty to me and it won't shock me if it never comes back. If you think it's bad now, just wait until there's no way to unfuck it.
FML. :banghead:

Well, there's an extremely racist (http://www.msn.com/en-us/news/other/google-maps-hit-with-racial-slurs-directed-at-obama/ar-BBk060d) "prank" or whatever you want to call it in the new Google Maps... maybe it's best if the Google Map Maker is turned off for the general public, and maybe Google should look into only allowing certified people who know what the hell they are doing to edit it. (For example: dfwmapper  ;-))
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on May 20, 2015, 10:40:33 PM
Quote from: Zeffy on May 20, 2015, 12:45:46 PM
Quote from: billtm on May 16, 2015, 09:06:39 PM
Quote from: dfwmapper on May 08, 2015, 08:13:06 PM
Just wait. They're disabling the entire Map Maker service "temporarily" as of May 12, with no specified date on when it will be available again. They claim to be doing it so they can catch up on the backlog of edits that have accumulated since auto-publishing and user reviews were disabled after the spam incidents, but that excuse smells a little bullshitty to me and it won't shock me if it never comes back. If you think it's bad now, just wait until there's no way to unfuck it.
FML. :banghead:

Well, there's an extremely racist (http://www.msn.com/en-us/news/other/google-maps-hit-with-racial-slurs-directed-at-obama/ar-BBk060d) "prank" or whatever you want to call it in the new Google Maps... maybe it's best if the Google Map Maker is turned off for the general public, and maybe Google should look into only allowing certified people who know what the hell they are doing to edit it. (For example: dfwmapper  ;-))

If they were willing to pay me, I'd edit stuff for Google. lol.
Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on May 21, 2015, 02:50:05 AM
That actually has nothing to do with Map Maker or even any data on the map, it's all in Google's search algorithms. People make web pages or social media posts and other random crap with something like "mah n***a Obama" and those words become associated with each other. Make a search for a word often associated with Obama and "house" in Washington DC and guess what it's going to find? There's an entire industry of search engine optimization (SEO) that exists to try to get keyword matches like this on search engines, though without the racism.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 21, 2015, 03:00:31 AM
Quote from: dfwmapper on May 21, 2015, 02:50:05 AM
...though without the racism.

The computers are answering algorithms the way they were meant to (without emotion and opinion). Sure, it produces some unwanted answers, but censoring isn't going to help anyone.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 25, 2015, 11:48:32 AM
Okay, how about this; The standard train station logo on East 241st Street in the Bronx for Wakefield Metro-North station, which is on the Harlem Line was placed over the New Haven Line. I've tried to report this error to them in the past, and they actually moved the logo FURTHER EAST.

I scanned a picture of the error, but I haven't posted it on imugr yet.

Title: Re: Google Maps just fucking SUCKS now
Post by: dfwmapper on May 25, 2015, 05:30:09 PM
Not Google's problem. For any transit that has scheduling information, all of that data including exact station locations comes directly from the transit agency. MTA's own data files have the location listed as 40.905424,-73.854665, which is exactly where the marker is on Google (and Bing, and Mapquest). You'll have to get MTA to fix it. MTA has a Google Group at https://groups.google.com/forum/#!forum/mtadeveloperresources for discussion of their data, so you might consider posting there and asking them to review and correct the location.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on May 25, 2015, 07:28:06 PM
Quote from: D-Dey65 on May 25, 2015, 11:48:32 AM
I scanned a picture of the error, but I haven't posted it on imugr yet.
You took a physical photograph of your computer monitor and scanned it?
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 26, 2015, 12:05:29 AM
Quote from: NE2 on May 25, 2015, 07:28:06 PM
Quote from: D-Dey65 on May 25, 2015, 11:48:32 AM
I scanned a picture of the error, but I haven't posted it on imugr yet.
You took a physical photograph of your computer monitor and scanned it?
Yes, I just pushed the PrintScan button on my keyboard, then posted it on a Bitmap file. After that I edited the file and saved the new version as a JPEG, and just tossed the Bitmap version in the recycling bin.

Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 27, 2015, 10:39:13 PM
The links to the classic maps no longer work.  :-(
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on May 27, 2015, 10:43:58 PM
Quote from: US 41 on May 27, 2015, 10:39:13 PM
The links to the classic maps no longer work.  :-(

https://www.aaroads.com/forum/index.php?topic=15450.msg2066712#msg2066712
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 27, 2015, 10:52:50 PM
Quote from: SignGeek101 on May 27, 2015, 10:43:58 PM
Quote from: US 41 on May 27, 2015, 10:39:13 PM
The links to the classic maps no longer work.  :-(

https://www.aaroads.com/forum/index.php?topic=15450.msg2066712#msg2066712

Thanks
Title: Re: Google Maps just fucking SUCKS now
Post by: SteveG1988 on May 28, 2015, 03:20:02 PM
I265 in KY/IN is shown as complete.

https://www.google.com/maps/place/Louisville,+KY/@38.254078,-85.7880071,11z/data=!4m2!3m1!1s0x88690b1ab35bd511:0xd4d3b4282071fd32
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on May 28, 2015, 03:32:40 PM
Quote from: SteveG1988 on May 28, 2015, 03:20:02 PM
I265 in KY/IN is shown as complete.

https://www.google.com/maps/place/Louisville,+KY/@38.254078,-85.7880071,11z/data=!4m2!3m1!1s0x88690b1ab35bd511:0xd4d3b4282071fd32

haha if only that were true!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 28, 2015, 05:48:06 PM
Made a little video ... hopefully I'm not the only one who likes the Stereo MCs.

https://www.youtube.com/watch?v=tzxeqKku3_A
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on May 29, 2015, 09:47:07 AM
For some reason, the new Google Maps on the US servers now runs perfect in both map and street view form, with no lag. What I dislike immensely, however, is the UGLY squished single-digit Interstate shields that now appear on the map:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FAOF6lED.png&hash=5b603ab448c0eb59d0653fcd5187c69c9eb4a80c)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 29, 2015, 02:51:56 PM
Quote from: Zeffy on May 29, 2015, 09:47:07 AM
What I dislike immensely, however, is the UGLY squished single-digit Interstate shields that now appear on the map:

Classic has those, too.
Title: Re: Google Maps just fucking SUCKS now
Post by: Highway63 on May 30, 2015, 02:35:40 AM
The Washington Post just had an article about Mapquest (http://thegazette.com/subject/news/mapquest-seeking-a-second-life-20150526) (link to reprint elsewhere). MQ should try to capitalize on dissatisfaction with the new Google Maps, but the "new web version" mentioned at the very end could make that bad too.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 31, 2015, 05:13:03 PM
I like using Rand McNally's online map. It works really fast and is pretty accurate.

EDIT: I do like how Mapquest clearly maps whether a freeway is a toll road or a free road.

EDIT #2: Google Maps has the best streetview of course, but ever since the new maps came out, I think other sites have caught up and many are now even slightly better than Google on directions and maps. I hate when you go to change your route on the new Google Maps and it routes you onto a dead end road close to the highway instead of putting the modifier circle on the highway. The old maps was (and still is) way better.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on May 31, 2015, 07:49:25 PM
Quote from: D-Dey65 on May 26, 2015, 12:05:29 AM
Quote from: NE2 on May 25, 2015, 07:28:06 PM
Quote from: D-Dey65 on May 25, 2015, 11:48:32 AM
I scanned a picture of the error, but I haven't posted it on imugr yet.
You took a physical photograph of your computer monitor and scanned it?
Yes, I just pushed the PrintScan button on my keyboard, then posted it on a Bitmap file. After that I edited the file and saved the new version as a JPEG, and just tossed the Bitmap version in the recycling bin.
You should print out the JPEG and fax it to him.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on June 07, 2015, 09:16:55 AM
Quote from: Scott5114 on May 31, 2015, 07:49:25 PM
You should print out the JPEG and fax it to him.
Ugh! I can't do that, because I don't have an actual printer or fax machine, and have no plans to get one. In the meantime, I'll consider hooking up with that MTA Google Groups page dfwmapper mentioned.
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on June 07, 2015, 10:17:10 AM
I just hope Poogle doesn't fuck Gmail in its shitty ass and ruin it like they've ruined Maps. It would cause major problems.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on June 10, 2015, 01:29:28 PM
There is a box in the classic Google maps link blocking it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on June 10, 2015, 10:43:44 PM
Quote from: bugo on June 07, 2015, 10:17:10 AM
I just hope Poogle doesn't fuck Gmail in its shitty ass and ruin it like they've ruined Maps. It would cause major problems.

I use Gmail for work. They've already 'tweaked' the android app once and it became a lot less intuitive (plus, placing the 'write a new email' icon over top of some of your emails instead of in the header is odd). I'm hoping that's as bad as it gets.

As for Google Maps, there's still one more way into the old maps that I know of. Though it also says that it's soon to be replaced. Maybe they'll forget this one.

AND just as I say that, I check the link and it takes me to the new maps. So, scratch another hack off the list. I'm out of options now. I hate new maps. One thing I'd do frequently is string a bunch of waypoints in a row and then hit search. It was easy to just keep hitting 'add location' to get about 10-15-20 open, and then start entering locations. With new maps, it is WAY TOO SLOW to do that, and wants to keep updating the route as I add waypoints. Which is  data hog. Also, switching between map and earth is very slow. And street view, which used to be AWESOME is now almost an afterthought with Google.

Oh well. Yahoo Maps works pretty good without street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on June 11, 2015, 12:36:46 AM
For whatever it's worth, I discovered today that you can now turn off labels in Earth (satellite) mode. That was my original and biggest complaint with new Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 11, 2015, 01:26:33 AM
Quote from: empirestate on June 11, 2015, 12:36:46 AM
For whatever it's worth, I discovered today that you can now turn off labels in Earth (satellite) mode. That was my original and biggest complaint with new Maps.

I didn't notice that before. Great feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on June 17, 2015, 08:42:34 PM
I just opened the new Goog in IE and it runs fine. What the fuck.

[edit]Oh, it's lite mode. Still much faster than Firefox.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on June 25, 2015, 12:42:05 PM
I'm going to miss the classic google maps.  :-( I don't know what to do anymore.
Title: Re: Google Maps just fucking SUCKS now
Post by: intelati49 on June 25, 2015, 12:46:03 PM
Quote from: stormwatch7721 on June 25, 2015, 12:42:05 PM
I'm going to miss the classic google maps.  :-( I don't know what to do anymore.

Google Earth.

It's the only way to avoid crashing FF on my shitty work computer.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on June 25, 2015, 01:36:27 PM
Quote from: intelati49 on June 25, 2015, 12:46:03 PM
Google Earth.

It's the only way to avoid crashing FF on my shitty work computer.

Google Earth makes my shitty work computer glacial slow.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on August 11, 2015, 05:55:05 PM
Is everyone else no longer able to navigate in Street View with the arrow keys?  It lets me turn the view, but not move backward or forward with the arrows.  I have to click with the mouse to move, so I can only go forward or sideways; backward is no longer possible.

This is very annoying.  Now I can navigate Street View with arrow keys only in Google Earth.  I hardly use the new maps, and now I have more reason not to.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 11, 2015, 06:16:21 PM
I cannot use the arrow keys to do any more than rotate, but the only way I ever navigate in Street View is by clicking on the mini map in the bottom left. You can zoom in really far and get super precise.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on August 11, 2015, 06:21:40 PM
Quote from: wxfree on August 11, 2015, 05:55:05 PM
Is everyone else no longer able to navigate in Street View with the arrow keys?  It lets me turn the view, but not move backward or forward with the arrows.  I have to click with the mouse to move, so I can only go forward or sideways; backward is no longer possible.

This is very annoying.  Now I can navigate Street View with arrow keys only in Google Earth.  I hardly use the new maps, and now I have more reason not to.

You can still use the arrow keys in SV with Lite Mode. Lite Mode is the only thing I use unless I need directions, then I use Mapquest.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 11, 2015, 06:56:17 PM
My problem with MapQuest is that the vector set it uses has significant issues when getting directions.  Try getting to Confluence Point State Park in MO or Smith Falls State Park in Nebraska, for instance.  Roads are not drawn correctly or simply omitted from the data set (still NAVTEQ?).

The frustrating thing is that it wasn't always this way.  Something changed a year or so ago.  I loved the number of edit points you could put into a MapQuest route, but the vector set became so lousy that I gave it up altogether.

Very disappointing.

Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 11, 2015, 07:48:07 PM
Seriously, what will Google remove next?  Maybe in a few months there won't even be roads on the map?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 11, 2015, 07:55:06 PM
Quote from: vdeane on August 11, 2015, 07:48:07 PM
Seriously, what will Google remove next?  Maybe in a few months there won't even be roads on the map?

My guess is that on April 1, all roads (even dead end roads, biking trails, and roads in other countries) will be labeled as Interstate 1. It will not change back the next day.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on August 13, 2015, 04:18:41 PM
I was irked by Google Maps being slow this afternoon, so I tried Bing Maps because their site has been consistently fast. I noted they had a link on the left side suggesting you try the "new" Bing Maps. Out of curiosity, I clicked on it. Worst of all worlds: Similar interface to new Google Maps, slower than the old Bing Maps, outdated map data (multiple missing ramps along I-95 in Northern Virginia–the HO/T lanes have been open for almost eight months now, so the ramps should be there; the ICC in Maryland is incomplete; at least they do show the Jersey Turnpike widening as having been completed), even more outdated "Bird's Eye" satellite images.

On the plus side, they got rid of the embarrassing "Branch" and "Boulevard" banners they used to display on "Business Routes" and "Business Loops," but that's not much of an accomplishment.

There is an "Exit" button at the lower right corner that lets you return to old Bing Maps more easily than Google Maps allowed back when they still had that capability. It asks you what you didn't like, so I gave them an abridged version of the above–it limits the space you have to comment, although it doesn't TELL you there's a limit and instead it simply stops accepting text.
Title: Re: Google Maps just fucking SUCKS now
Post by: intelati49 on August 13, 2015, 04:24:35 PM
Quote from: 1995hoo on August 13, 2015, 04:18:41 PM
I was irked by Google Maps being slow this afternoon, so I tried Bing Maps because their site has been consistently fast. I noted they had a link on the left side suggesting you try the "new" Bing Maps. Out of curiosity, I clicked on it. Worst of all worlds: Similar interface to new Google Maps, slower than the old Bing Maps, outdated map data (multiple missing ramps along I-95 in Northern Virginia–the HO/T lanes have been open for almost eight months now, so the ramps should be there; the ICC in Maryland is incomplete; at least they do show the Jersey Turnpike widening as having been completed), even more outdated "Bird's Eye" satellite images.

On the plus side, they got rid of the embarrassing "Branch" and "Boulevard" banners they used to display on "Business Routes" and "Business Loops," but that's not much of an accomplishment.

There is an "Exit" button at the lower right corner that lets you return to old Bing Maps more easily than Google Maps allowed back when they still had that capability. It asks you what you didn't like, so I gave them an abridged version of the above–it limits the space you have to comment, although it doesn't TELL you there's a limit and instead it simply stops accepting text.

Well, shit...
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 16, 2015, 09:25:25 PM
No ability to print off turn-by-turn maps...ugggggggggggggggh.   :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on August 22, 2015, 03:33:31 PM
Quote from: dfwmapper on May 25, 2015, 05:30:09 PM
Not Google's problem. For any transit that has scheduling information, all of that data including exact station locations comes directly from the transit agency. MTA's own data files have the location listed as 40.905424,-73.854665, which is exactly where the marker is on Google (and Bing, and Mapquest). You'll have to get MTA to fix it. MTA has a Google Group at https://groups.google.com/forum/#!forum/mtadeveloperresources for discussion of their data, so you might consider posting there and asking them to review and correct the location.
Well, somebody must've fixed it, because the logo is where it belongs now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on August 24, 2015, 08:05:53 PM
It's kind of an error, but it's also kind of funny if you remove the hyphen from what is displayed:

https://www.google.com/maps/@37.2330692,-89.6272679,15.04z

Otherwise, it should be just AB, since the other county roads in Missouri are displayed with just their letters.
Title: Re: Google Maps just fucking SUCKS now
Post by: noelbotevera on August 24, 2015, 08:52:06 PM
I'm starting to drift away from Google a bit and try here drive+. Not half bad, except when you zoom out, it doesn't auto focus when you want to back on the arrow (your phone).
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on August 26, 2015, 11:26:27 AM
https://www.google.com/maps/place/Marshalls+Creek,+PA+18301/@41.041765,-75.128848,3a,66.8y,-290.3h,95.19t/data=!3m4!1e1!3m2!1sRPaWDSnr_55au28FFX_P0w!2e0!4m2!3m1!1s0x89c485c32088702f:0xb4e113a711e2cdfa

Is that signal head really slanted, or is it an illusion created by improper pasting of the photos like many cut out some things or a misaligned pasting of two photos.
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on August 26, 2015, 11:31:34 AM
Quote from: roadman65 on August 26, 2015, 11:26:27 AM
https://www.google.com/maps/place/Marshalls+Creek,+PA+18301/@41.041765,-75.128848,3a,66.8y,-290.3h,95.19t/data=!3m4!1e1!3m2!1sRPaWDSnr_55au28FFX_P0w!2e0!4m2!3m1!1s0x89c485c32088702f:0xb4e113a711e2cdfa

Is that signal head really slanted, or is it an illusion created by improper pasting of the photos like many cut out some things or a misaligned pasting of two photos.

The signal head is slanted. If you move to another location, the slant stays.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on August 31, 2015, 09:22:06 PM
The street view feature is taken off on Lite Mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on August 31, 2015, 09:29:12 PM
Quote from: stormwatch7721 on August 31, 2015, 09:22:06 PM
The street view feature is taken off on Lite Mode.

It worked for me. You just have to drag the man to a location instead of clicking.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on August 31, 2015, 09:37:29 PM
The pegman is not there anymore in lite mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on August 31, 2015, 09:44:36 PM
Quote from: stormwatch7721 on August 31, 2015, 09:37:29 PM
The pegman is not there anymore in lite mode.

I'm not sure what I set it to, then. I thought it was Lite Mode. The pegman icon was there but I had to drag it to a location, like the way it used to work. But my PC isn't on right now and I don't see much point in firing it up at this time of night just to find out how I had it set.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on September 01, 2015, 11:21:23 AM
Ugh, more bad news. Google Maps won't show subway lines anymore, at least in New York City. I haven't checked other systems yet.

  :angry:

Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 01, 2015, 02:06:50 PM
Quote from: D-Dey65 on September 01, 2015, 11:21:23 AM
Ugh, more bad news. Google Maps won't show subway lines anymore, at least in New York City. I haven't checked other systems yet.

It's still there for me when transit mode is on or when clicking on a station icon (along with other systems, such as those in Seattle, Chicago, LA, DC, SF, Portland).

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fe8CD9QM.jpg&hash=9761c0a576811f4ef91d3e32c3832400cc5b2317)

Also, Portland's new Orange Line (opening this month) is now included on Google Maps. Same goes for the tunnels for Seattle's University Link Extension (opening in 2016).
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on September 01, 2015, 03:08:50 PM
I still have Pegman in Lite mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on September 01, 2015, 04:57:59 PM
As much as I disliked old Bing Maps, I use them now unless I'm looking for street view. On my phone, for directions, I use mapquest's app.

In general, Google Maps feels like a kids toy, designed entirely to take the 'thought process' out of the users hands and assumes for you what you want.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on September 01, 2015, 08:26:05 PM
Quote from: 1995hoo on August 31, 2015, 09:44:36 PM
Quote from: stormwatch7721 on August 31, 2015, 09:37:29 PM
The pegman is not there anymore in lite mode.

I'm not sure what I set it to, then. I thought it was Lite Mode. The pegman icon was there but I had to drag it to a location, like the way it used to work. But my PC isn't on right now and I don't see much point in firing it up at this time of night just to find out how I had it set.

I'm at my PC now and it shows I have Google Maps set to Lite Mode, but the pegman icon is indeed there all the way in the lower right corner of the screen. As I said above, you have to drag it to a location.
Title: Re: Google Maps just fucking SUCKS now
Post by: noelbotevera on September 02, 2015, 03:43:42 PM
Quote from: 1995hoo on September 01, 2015, 08:26:05 PM
Quote from: 1995hoo on August 31, 2015, 09:44:36 PM
Quote from: stormwatch7721 on August 31, 2015, 09:37:29 PM
The pegman is not there anymore in lite mode.

I'm not sure what I set it to, then. I thought it was Lite Mode. The pegman icon was there but I had to drag it to a location, like the way it used to work. But my PC isn't on right now and I don't see much point in firing it up at this time of night just to find out how I had it set.

I'm at my PC now and it shows I have Google Maps set to Lite Mode, but the pegman icon is indeed there all the way in the lower right corner of the screen. As I said above, you have to drag it to a location.
They could use "Pegman Mode" as I call t. Click Pegman (and relocate him on the bottom of the screen), and it turns roads blue (and Pegman's location disappears), then click the road you want, and you instantly go into Street View.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on September 02, 2015, 08:47:29 PM
The pegman is back on Street View lite mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on September 03, 2015, 10:23:53 AM
Quote from: Bruce on September 01, 2015, 02:06:50 PM
Quote from: D-Dey65 on September 01, 2015, 11:21:23 AM
Ugh, more bad news. Google Maps won't show subway lines anymore, at least in New York City. I haven't checked other systems yet.

It's still there for me when transit mode is on or when clicking on a station icon (along with other systems, such as those in Seattle, Chicago, LA, DC, SF, Portland).

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fe8CD9QM.jpg&hash=9761c0a576811f4ef91d3e32c3832400cc5b2317)
I found the transit mode and clicked on that. Clicking on a station icon simply wasn't enough.

Title: Re: Google Maps just fucking SUCKS now
Post by: Thunderbyrd316 on September 17, 2015, 06:49:25 PM
I case anyone is interested, I just now discovered that ClassyGMap has added U.S. county lines to it's version of Google Maps. As far as I can tell, they appear to be pretty accurate.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 17, 2015, 06:50:26 PM
Is there still strong opposition to the new Google Maps? It seems to get better every time I use it (then again, I never had any significant issues with it).
Title: Re: Google Maps just fucking SUCKS now
Post by: Thunderbyrd316 on September 17, 2015, 07:29:01 PM
   For me, navigating in "Street View" is MUCH easier in ClassyGMap than New Google Maps because in "Classic" you can easily move "Pegman" around on the split screen map without having to constantly go in and out of Street View. (And you have a split screen map that you can actually zoom in and out and see the map in satellite view.) The tiny little map in New Maps is pretty much worthless, does NOT have satellite view and can only be zoomed in and out a small amount, certainly not far enough out to move "Pegman" 10 or 20 miles or more at a time without having to constantly switch in and out of Street View mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on September 17, 2015, 07:31:58 PM
Quote from: jakeroot on September 17, 2015, 06:50:26 PM
Is there still strong opposition to the new Google Maps? It seems to get better every time I use it (then again, I never had any significant issues with it).

I'd say it's better now, partly because I've gotten used to it more. But still, some features are annoying (such as the pictures on the bottom of the screen when in streetview). Also, I find it's more difficult to get Pegman to land on a street than in the old version.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 17, 2015, 07:45:44 PM
It appears that Google has finally reenabled the ability to use arrow keys in street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on September 19, 2015, 04:06:16 AM
Quote from: Thunderbyrd316 on September 17, 2015, 07:29:01 PM
   For me, navigating in "Street View" is MUCH easier in ClassyGMap than New Google Maps because in "Classic" you can easily move "Pegman" around on the split screen map without having to constantly go in and out of Street View. (And you have a split screen map that you can actually zoom in and out and see the map in satellite view.) The tiny little map in New Maps is pretty much worthless, does NOT have satellite view and can only be zoomed in and out a small amount, certainly not far enough out to move "Pegman" 10 or 20 miles or more at a time without having to constantly switch in and out of Street View mode.

You are like my new hero. I had no idea about ClassyGMap. I tried it out and I am definitely using it for now on.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on September 19, 2015, 08:34:36 AM
I may have to switch to ClassyGMap too, now that the Labels Off feature has stopped working in Google Maps. At first, it would just turn off the names and numbers but keep all the linework of the streets overlaid on the satellite view. Now, in addition to that, the labels only remain off for that one viewing of Satellite (Earth) mode. Each time you switch back, you have to turn the labels off all over again. (This problem started with going in and out of Street View, but now it seems to be with every mode switch.)

This functionality change seemed to happen over the course of a couple of hours yesterday and was accompanied, at least on my end, with a loss of connectivity to the Google Earth server. I wonder if something's just amiss over at Google?
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on September 21, 2015, 02:49:20 PM
I'm not a fan of ClassyGMap. The interface is nice, but there's no way to make the map portion of street view (the section where you see the map when you go into street view) smaller and it taking up half the screen makes it hard to see what you're looking at on street view, IMO.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on September 21, 2015, 08:20:51 PM
Quote from: freebrickproductions on September 21, 2015, 02:49:20 PM
I'm not a fan of ClassyGMap. The interface is nice, but there's no way to make the map portion of street view (the section where you see the map when you go into street view) smaller and it taking up half the screen makes it hard to see what you're looking at on street view, IMO.
Did you try the pull down menu at the top right?  There are a couple of options for adjusting the split screen including a Google like minimap, larger Streetview, larger Map, vertical split, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on September 21, 2015, 08:24:00 PM
Quote from: Roadrunner75 on September 21, 2015, 08:20:51 PM
Quote from: freebrickproductions on September 21, 2015, 02:49:20 PM
I'm not a fan of ClassyGMap. The interface is nice, but there's no way to make the map portion of street view (the section where you see the map when you go into street view) smaller and it taking up half the screen makes it hard to see what you're looking at on street view, IMO.
Did you try the pull down menu at the top right?  There are a couple of options for adjusting the split screen including a Google like minimap, larger Streetview, larger Map, vertical split, etc.

Didn't see that when I used it. I like it better now that I know I can do that, but I think I'll stick with regular Google Maps for now.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on September 30, 2015, 06:08:11 PM
Just a little curious. Why is there no street view in Puerto Rico? After all it is part of the United States.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 30, 2015, 06:18:49 PM
Quote from: US 41 on September 30, 2015, 06:08:11 PM
Just a little curious. Why is there no street view in Puerto Rico? After all it is part of the United States.

I'm sure it's in the pipeline. There's still plenty of the contiguous US they have to do.

First two things that come to mind are rural roads in rural counties, and islands. The San Juan Islands of Washington have not been touched yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 30, 2015, 07:26:37 PM
I just noticed how bad the watermarking on Streetview is getting:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fo0zacux.png&hash=b4b443091f073f931867d704a96fde30b124b7c4)
Title: Re: Google Maps just fucking SUCKS now
Post by: noelbotevera on September 30, 2015, 07:45:43 PM
Quote from: Bruce on September 30, 2015, 07:26:37 PM
I just noticed how bad the watermarking on Streetview is getting:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fo0zacux.png&hash=b4b443091f073f931867d704a96fde30b124b7c4)
OMIGOD...the Google logo...IT'S INFECTED THE SKY!

Ellis: OH MY GOD IT'S CHRISTMAS

This Christmas must suck then.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 30, 2015, 08:33:02 PM
Quote from: noelbotevera on September 30, 2015, 07:45:43 PM
Quote from: Bruce on September 30, 2015, 07:26:37 PM
I just noticed how bad the watermarking on Streetview is getting:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fo0zacux.png&hash=b4b443091f073f931867d704a96fde30b124b7c4)
OMIGOD...the Google logo...IT'S INFECTED THE SKY!

Ellis: OH MY GOD IT'S CHRISTMAS

This Christmas must suck then.

Google to Acquire Rights to Sky

MOUNTAIN VIEW, CA — SEPTEMBER 30, 2015 – Google Inc. (NASDAQ: GOOG) announced today that it has entered into an agreement to acquire rights to license the Sky™ from Earth Inc. (NASDAQ: TERRA) for an undisclosed fee.

Larry Page, CEO of Google, said: "We're thrilled to be able to provide this service to the entire world at the low cost of a few watermarks. Rest assured, we will work on cleaning up the skies in developing regions in accordance with our slogan–don't be evil."

About Google Inc.

Google is a global technology leader focused on improving the ways people connect with information. Google's innovations in web search and advertising have made its website a top internet property and its brand one of the most recognized in the world.

Contact
press@google.com
Title: Re: Google Maps just fucking SUCKS now
Post by: Big John on September 30, 2015, 08:43:48 PM
Obtrusive space advertising is not allowed in the US  https://www.law.cornell.edu/uscode/text/51/50911
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on October 16, 2015, 11:17:06 AM
Getting directions from Google Maps today for a trip from Trenton, NJ to Independence, OH, I noticed they now summarize the directions.

When I first grabbed the directions, this is what it gave me:

   Get on US 1 South (3 min/1 mi)

   Follow I-476 N and I-80 W to Rockside Rd in Independence. Take exit 155 from I-77 N (6 h 46 min/455 mi)

   Drive to Quarry Ln (2 min/0.2 mi)

Very concise.  Maybe a little too concise.  It would be nice to have the exit numbers for the main directional changes as well (in this case, from 476 to 80 & 80 to 77).  Sure, I can get that when I expand the selection, but then I also have to deal with "Stay on ramp for 0.4 miles, not that you have any other choice other than flipping over the guardrail and rolling down the embankment".
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on October 16, 2015, 02:26:27 PM
The elimination of turn-by-turn maps still ticks me off and the summaries are indeed too concise.
Title: Re: Google Maps just fucking SUCKS now
Post by: noelbotevera on October 16, 2015, 03:14:44 PM
Quote from: Rothman on October 16, 2015, 02:26:27 PM
The elimination of turn-by-turn maps still ticks me off and the summaries are indeed too concise.
Bring back Mapquest circa 2009 please.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2015, 03:23:57 PM
Pfff, who needs Google? Apple Maps has all the directions I need

to get lost.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 16, 2015, 05:06:08 PM
I used Apple Maps a few times late last month, primarily for walking directions in unfamiliar cities. Worked fine. They've definitely improved it since it was released (yes, I realize that's not saying much, but my experience with it suggests the stereotype of it as riddled with errors and incompetence is outdated).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2015, 05:38:04 PM
Quote from: 1995hoo on October 16, 2015, 05:06:08 PM
I used Apple Maps a few times late last month, primarily for walking directions in unfamiliar cities. Worked fine. They've definitely improved it since it was released (yes, I realize that's not saying much, but my experience with it suggests the stereotype of it as riddled with errors and incompetence is outdated).

I can actually thank Apple Maps for helping me find the shortest route to work. Google Maps always used the freeways, but Apple suggested some side streets. I never went back.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on October 19, 2015, 11:34:25 AM
I'm asking in case anyone has the answer to this particular problem at his or her fingertips--it is not obvious to me and Googling hasn't helped.

Google has decided (how, I am not sure) that I am to be signed in by default when I use Google Maps.  For at least a month now, maps have loaded for me without any route designations.  I don't want this behavior but my route knowledge in my local area is good enough that it hasn't seriously inconvenienced me until now, when I tried to re-check US 12 and SR 8 in the Olympic Peninsula in Washington state.  I logged out in case this behavior was being caused by my user profile; the map I was looking at reloaded initially with route shields--but once loading finished, the route shields disappeared!  What is going on?  (I'm using Windows 7, Firefox, and Flash is up to date.)
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on October 20, 2015, 12:08:55 PM
Quote from: J N Winkler on October 19, 2015, 11:34:25 AM
I'm asking in case anyone has the answer to this particular problem at his or her fingertips--it is not obvious to me and Googling hasn't helped.

Google has decided (how, I am not sure) that I am to be signed in by default when I use Google Maps.  For at least a month now, maps have loaded for me without any route designations.  I don't want this behavior but my route knowledge in my local area is good enough that it hasn't seriously inconvenienced me until now, when I tried to re-check US 12 and SR 8 in the Olympic Peninsula in Washington state.  I logged out in case this behavior was being caused by my user profile; the map I was looking at reloaded initially with route shields--but once loading finished, the route shields disappeared!  What is going on?  (I'm using Windows 7, Firefox, and Flash is up to date.)

Interesting.  I tried logging out on Google Maps and the maps reloaded normally.  I'm using MacOS X 10.9 and Safari 7.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mileage Mike on October 22, 2015, 04:10:22 PM
Anyone else use Waze (owned by Google) and notice that after the latest update it no longer shows the highway numbers of roads aside from interstates?  Seems like everytime these companies update something to make it better, they end up breaking something else in the process.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on October 22, 2015, 05:09:55 PM
Quote from: myosh_tino on October 20, 2015, 12:08:55 PMInteresting.  I tried logging out on Google Maps and the maps reloaded normally.  I'm using MacOS X 10.9 and Safari 7.

In my case, the shields appear when a Google Maps page loads, and then they disappear.  It is like there is a script that runs at the end of page load that takes them away.  It is very frustrating.
Title: Re: Google Maps just fucking SUCKS now
Post by: MrDisco99 on October 28, 2015, 02:23:02 PM
Whoah... You can't drag the blue line anymore in directions?  Screw this...

Hello again, Mapquest
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on October 28, 2015, 03:03:33 PM
Quote from: MrDisco99 on October 28, 2015, 02:23:02 PM
Whoah... You can't drag the blue line anymore in directions?  Screw this...

Hello again, Mapquest

Sure you can.   

But being that you're the type that says "Screw this" rather than "Is anyone else having this issue", I'm guessing you jump around a lot between various services.
Title: Re: Google Maps just fucking SUCKS now
Post by: mvak36 on October 28, 2015, 05:30:30 PM
Quote from: MrDisco99 on October 28, 2015, 02:23:02 PM
Whoah... You can't drag the blue line anymore in directions?  Screw this...

Hello again, Mapquest
You're probably in the Lite Mode of the google Maps. If you change it back to the Full version (thunderbolt looking button on bottom right of browser next to the icon for Streetview) you can do it again. That worked for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: OCGuy81 on October 29, 2015, 11:16:29 AM
Does Google Maps show county lines?

I was trying to map counties I'd hit on a road trip, but I only see state boundaries.

Any other maps out there, Apple, Mapquest show county lines?  I swear Google USED to show these, or at least had a way to enable them.
Title: Re: Google Maps just fucking SUCKS now
Post by: triplemultiplex on October 29, 2015, 11:20:29 AM
Google maps will only show the county boundaries of a county you do a search for.
Apple Maps doesn't show them either.

I haven't used Mapquest in over a decade so I couldn't tell you about that.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on October 29, 2015, 12:55:48 PM
Quote from: OCGuy81 on October 29, 2015, 11:16:29 AM
Does Google Maps show county lines?

I was trying to map counties I'd hit on a road trip, but I only see state boundaries.

Any other maps out there, Apple, Mapquest show county lines?  I swear Google USED to show these, or at least had a way to enable them.

Yeah, Mapquest and Bing both show them. So does OSM, the National Map, and ArcGIS.
Title: Re: Google Maps just fucking SUCKS now
Post by: Purgatory On Wheels on October 29, 2015, 05:45:06 PM
Google maps with county lines (http://www.mob-rule.com/g7?) courtesy mob-rule.com.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on November 01, 2015, 10:39:49 PM
Google Maps has made a small change that makes it hard to see roads above/below structures:

Seattle ferry terminal, which has a building above some parts of the dock (but not all):

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F1DKmOFL.png&hash=60df240687fb77792af8afb650a137c90ed257d4)

A transit center with a parking garage elevated above it:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F0I73TkA.png&hash=c5bcdc51310bee261251fc47ee10e79604ace57e)
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on November 02, 2015, 01:53:14 PM
One thing I noticed, is if you put Google Maps to half screen with another window open (such as transposing waypoints, etc), it forces you into lite mode and no option to switch back. I guess based on pixels, resolution of the window, etc, it assumes you're on a tablet/phone and won't let you. This includes losing markers for waypoints, moving the line, etc.

I've been using old Bing Maps for most non-phone related road look ups, even though their search engine is horrible at picking up proper points the way Google could (search engine problem, not maps, specifically).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 02, 2015, 03:40:18 PM
Quote from: Sykotyk on November 02, 2015, 01:53:14 PM
One thing I noticed, is if you put Google Maps to half screen with another window open (such as transposing waypoints, etc), it forces you into lite mode and no option to switch back. I guess based on pixels, resolution of the window, etc, it assumes you're on a tablet/phone and won't let you. This includes losing markers for waypoints, moving the line, etc.

I can't seem to replicate this issue. What's your operating system?
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on November 03, 2015, 01:40:58 AM
Windows 8, Firefox, latest version. Not sure why. Don't feel like tinkering with it. I mostly use Bing maps (old version) for most stuff, but sometimes google is faster at finding locations because their search engine is faster.

Switching from old Google Maps to new isn't working for me. The constant solid blue line that doesn't show the waypoints other than white dots just slightly bigger than change of direction smaller white dots doesn't work. Especially if I'm putting in 10 or 15 waypoints. And the fact you can't just enter them all, you have to enter one, let it search and route for it, then add another. And another. No more just hitting "add" ten or fifteen times, filling in the fields, and then searching.

Waste of time and bandwidth.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on November 12, 2015, 09:48:49 PM
Spotted today in DC (https://www.google.com/maps/@38.8785436,-76.9716547,14.75z):

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FEMp84hg.png&hash=3fafe5d724cea1274d8f673ade68ec91ea81f391)
Title: Re: Google Maps just fucking SUCKS now
Post by: Ian on November 13, 2015, 11:32:00 AM
Wow, Quebec City is a lot bigger than I imagined... (https://goo.gl/maps/sN5S7cMCdES2)
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on December 05, 2015, 09:39:41 AM
A bunch of non-road related errors with Google Maps; They're claiming that waterways like Orient Harbor, Long Beach Bay, the southern Shelter Island Sound, Cutchogue Bay, Sag Harbor Bay, Northwest Harbor and the North and South Races around Robins Island are (get this) part of the Peconic River!

Title: Re: Google Maps just fucking SUCKS now
Post by: Buffaboy on December 08, 2015, 07:35:35 PM
Trivial, but does Google actually edit business descriptions? Who are they to be able to drive-by judge places they may or may not have been to?

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F87d7I77.png&hash=393bb1a2c8a4a03ab87290c2b71d878def884cd2)

This is why I wish I could get rid of Google Maps. Nothing wrong with the business, it's an accurate description, but they just seem creepy in these cases.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2015, 10:11:30 PM
Quote from: Buffaboy on December 08, 2015, 07:35:35 PM
Trivial, but does Google actually edit business descriptions? Who are they to be able to drive-by judge places they may or may not have been to?

This is why I wish I could get rid of Google Maps. Nothing wrong with the business, it's an accurate description, but they just seem creepy in these cases.

You are joking, right? Google is a data company ... the descriptions were likely mined from food websites, such as OpenTable.
Title: Re: Google Maps just fucking SUCKS now
Post by: Highway63 on December 12, 2015, 09:13:02 PM
I am looking at GMaps in Chrome right now and all vertical and non-straight state lines are FUBAR'd. Instead of dashes they look like triangles, or dashes of increasing/decreasing width.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on December 14, 2015, 12:32:46 PM
Quote from: Jeff Morrison on December 12, 2015, 09:13:02 PM
I am looking at GMaps in Chrome right now and all vertical and non-straight state lines are FUBAR'd. Instead of dashes they look like triangles, or dashes of increasing/decreasing width.
Not seeing it in Lite Mode on Google Chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on February 06, 2016, 05:54:14 PM
I was trying to find an old house which appears to have been torn down, and the property belongs to the "Our Lady Of Loreto Roman Catholic Church, which is at  104 Greenwich Street, Hempstead, New York. The house in question was the Constance Wright House, which was at 90 Greenwich Street.

https://commons.wikimedia.org/wiki/File:Constance_Wright_House,_90_Greenwich_Street,_Hempstead,_Nassau_County,_NY_HABS_NY,30-HEMP,6-_(sheet_7_of_7).tif

The trouble is, when I tried to look at their website in order to see if they have any info on the property, I found out that the website was to another church with the same name in Foxfield, Colorado!


And I don't see any provisions on the maps to inform them of this error!

Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 06, 2016, 06:05:09 PM
Quote from: D-Dey65 on February 06, 2016, 05:54:14 PM
And I don't see any provisions on the maps to inform them of this error!

Hit the "suggest an edit" button on the panel that slides out when you hit the "Our Lady of Loreto RCC" icon the map (it's three clicks down from the web address that you speak of). It allows you to change the web address and submit the change to Google, who will likely approve the change once they discover the error.
Title: Re: Google Maps just fucking SUCKS now
Post by: Thunderbyrd316 on February 07, 2016, 06:16:36 PM
In case anybody is still interested, I am STILL able to access Classic Google Maps via ClassyGMaps despite continuing rumors that it is dead. Link: http://gokml.net/maps-azteca.php#ll=42.345573,-71.098326&z=3&t=r
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on February 07, 2016, 11:24:35 PM
Has anyone figured out how to get satellite imagery on the new google maps without having to go into lite mode? Because I still want to be able to drag the blue line in directions, but still see undistorted Satellite imagery. :hmmm:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 08, 2016, 01:05:20 AM
Quote from: billtm on February 07, 2016, 11:24:35 PM
Has anyone figured out how to get satellite imagery on the new google maps without having to go into lite mode? Because I still want to be able to drag the blue line in directions, but still see undistorted Satellite imagery.

Hit the "menu" button (three horizontal lines) in the top left of Maps, and select "3D on" below the "Earth" label. This will change the label to "3D off" and will disable 3D imagery.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on February 08, 2016, 10:41:07 AM
Quote from: Thunderbyrd316 on February 07, 2016, 06:16:36 PM
In case anybody is still interested, I am STILL able to access Classic Google Maps via ClassyGMaps despite continuing rumors that it is dead. Link: http://gokml.net/maps-azteca.php#ll=42.345573,-71.098326&z=3&t=r

I am. And thanks for the link.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 08, 2016, 02:22:57 PM
Quote from: US 41 on February 08, 2016, 10:41:07 AM
Quote from: Thunderbyrd316 on February 07, 2016, 06:16:36 PM
In case anybody is still interested, I am STILL able to access Classic Google Maps via ClassyGMaps despite continuing rumors that it is dead. Link: http://gokml.net/maps-azteca.php#ll=42.345573,-71.098326&z=3&t=r

I am. And thanks for the link.

Why are you two still using the old Maps? The new Maps is great. It's a hell of a lot faster than it used to be.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on February 08, 2016, 05:37:24 PM
Quote from: jakeroot on February 08, 2016, 02:22:57 PM
Quote from: US 41 on February 08, 2016, 10:41:07 AM
Quote from: Thunderbyrd316 on February 07, 2016, 06:16:36 PM
In case anybody is still interested, I am STILL able to access Classic Google Maps via ClassyGMaps despite continuing rumors that it is dead. Link: http://gokml.net/maps-azteca.php#ll=42.345573,-71.098326&z=3&t=r

I am. And thanks for the link.

Why are you two still using the old Maps? The new Maps is great. It's a hell of a lot faster than it used to be.

Um... because the new maps only runs in crippled mode on my computers?  My work computer really is pretty old but my workplace is cheap, so...

And at home the computer is fine but it's not running Windows or MacOS or Chrome so as far as Google is concerned it just doesn't count.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 08, 2016, 06:00:57 PM
Quote from: kkt on February 08, 2016, 05:37:24 PM
Quote from: jakeroot on February 08, 2016, 02:22:57 PM
Quote from: US 41 on February 08, 2016, 10:41:07 AM
Quote from: Thunderbyrd316 on February 07, 2016, 06:16:36 PM
In case anybody is still interested, I am STILL able to access Classic Google Maps via ClassyGMaps despite continuing rumors that it is dead. Link: http://gokml.net/maps-azteca.php#ll=42.345573,-71.098326&z=3&t=r

I am. And thanks for the link.

Why are you two still using the old Maps? The new Maps is great. It's a hell of a lot faster than it used to be.

Um... because the new maps only runs in crippled mode on my computers?  My work computer really is pretty old but my workplace is cheap, so...

And at home the computer is fine but it's not running Windows or MacOS or Chrome so as far as Google is concerned it just doesn't count.

I didn't know there were computers that still couldn't run it. My bad.

What OS do you run at home?
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on February 08, 2016, 06:39:04 PM
Quote from: jakeroot on February 08, 2016, 06:00:57 PM
What OS do you run at home?

PCBSD... it's a branch of FreeBSD with a KDE desktop environment.
Title: Re: Google Maps just fucking SUCKS now
Post by: Pete from Boston on February 08, 2016, 07:01:04 PM

Quote from: jakeroot on December 09, 2015, 10:11:30 PM
Quote from: Buffaboy on December 08, 2015, 07:35:35 PM
Trivial, but does Google actually edit business descriptions? Who are they to be able to drive-by judge places they may or may not have been to?

This is why I wish I could get rid of Google Maps. Nothing wrong with the business, it's an accurate description, but they just seem creepy in these cases.

You are joking, right? Google is a data company ... the descriptions were likely mined from food websites, such as OpenTable.

They seem to be scraping Gas Buddy now as well, because on the mobile version I recently saw gas prices under the names of stations in my area.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on February 09, 2016, 09:45:40 AM
Quote from: jakeroot on February 08, 2016, 06:00:57 PM
Quote from: kkt on February 08, 2016, 05:37:24 PM
Quote from: jakeroot on February 08, 2016, 02:22:57 PM
Quote from: US 41 on February 08, 2016, 10:41:07 AM
Quote from: Thunderbyrd316 on February 07, 2016, 06:16:36 PM
In case anybody is still interested, I am STILL able to access Classic Google Maps via ClassyGMaps despite continuing rumors that it is dead. Link: http://gokml.net/maps-azteca.php#ll=42.345573,-71.098326&z=3&t=r

I am. And thanks for the link.

Why are you two still using the old Maps? The new Maps is great. It's a hell of a lot faster than it used to be.

Um... because the new maps only runs in crippled mode on my computers?  My work computer really is pretty old but my workplace is cheap, so...

And at home the computer is fine but it's not running Windows or MacOS or Chrome so as far as Google is concerned it just doesn't count.

I didn't know there were computers that still couldn't run it. My bad.

What OS do you run at home?

I've been using Lite Mode which seems to work fine, but the "Full Mode" Google Maps runs way to slow. But when I'm planning out trips I can't edit my route on Lite Mode, so I still use ClassyGMap as much as I can. Trying to edit a route on Full Google Maps is just plain irritating. Example: You try dragging the edit dot onto US 70 and it puts the edit dot on some alley a quarter of a mile away from US 70. On the ClassyGMap that doesn't happen. It automatically puts the dot on the major highway near by.

EDIT: It doesn't look like you can do directions on ClassyGMap anymore.  :-(
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 09, 2016, 06:51:07 PM
Quote from: US 41 on February 09, 2016, 09:45:40 AM
I've been using Lite Mode which seems to work fine, but the "Full Mode" Google Maps runs way to slow. But when I'm planning out trips I can't edit my route on Lite Mode, so I still use ClassyGMap as much as I can. Trying to edit a route on Full Google Maps is just plain irritating. Example: You try dragging the edit dot onto US 70 and it puts the edit dot on some alley a quarter of a mile away from US 70. On the ClassyGMap that doesn't happen. It automatically puts the dot on the major highway near by.

This is the "feature" of the new Google Maps that I hate the most. I'm glad someone else doesn't like it either.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on February 09, 2016, 08:32:03 PM
Quote from: jakeroot on February 08, 2016, 01:05:20 AM
Quote from: billtm on February 07, 2016, 11:24:35 PM
Has anyone figured out how to get satellite imagery on the new google maps without having to go into lite mode? Because I still want to be able to drag the blue line in directions, but still see undistorted Satellite imagery.

Hit the "menu" button (three horizontal lines) in the top left of Maps, and select "3D on" below the "Earth" label. This will change the label to "3D off" and will disable 3D imagery.

Oh my goodness! I feel so stupid now! :banghead:
In non-3D mode, all the speed problems I had with the new Google Maps are fixed now. They seriously should just make Satellite the default mode, and then have you turn 3D on to get into Earth. The Satimagery is way more useful, while Earth just makes it look prettier.

Follow-up question: Is there a way to see the 45-degree imagery in the new Google Maps? :hmmm:
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on February 10, 2016, 11:17:25 AM
Quote from: billtm on February 09, 2016, 08:32:03 PM
Follow-up question: Is there a way to see the 45-degree imagery in the new Google Maps? :hmmm:
In standard Google Maps: No.
In Lite Mode: Yes.
45-degree mode seems to be a lite-mode only feature now, sadly. It's really a waste, IMO to get rid of it from standard Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on February 10, 2016, 11:36:07 AM
Quote from: freebrickproductions on February 10, 2016, 11:17:25 AM
Quote from: billtm on February 09, 2016, 08:32:03 PM
Follow-up question: Is there a way to see the 45-degree imagery in the new Google Maps? :hmmm:
In standard Google Maps: No.
In Lite Mode: Yes.
45-degree mode seems to be a lite-mode only feature now, sadly. It's really a waste, IMO to get rid of it from standard Google Maps.

Well that's really weird and really freaking stupid.
It would seem more logical to make regular mode have all the features of lite mode and more.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 10, 2016, 08:29:16 PM
I'm pretty sure Google decided to not move forward with the 45 degree imagery, which is why it's not in the regular google maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on February 28, 2016, 07:06:59 PM
What the frick is going on with Google Maps now! :banghead: Last week street view wouldn't work, and now the map is lagging to the point where it takes a minute to load a city! To top it all off, terrain mode is greyed out everywhere I go! At least I got around the street view problem by using the right-click whats here? feature. But before today, I have never had problems with Google Maps and lag. :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 28, 2016, 07:51:20 PM
Quote from: billtm on February 28, 2016, 07:06:59 PM
What the frick is going on with Google Maps now! :banghead: Last week street view wouldn't work...before today, I have never had problems with Google Maps and lag. :pan:

Are you sure? Certainly doesn't sound like it.  :-D

FWIW, I'm not having any problems.
Title: Re: Google Maps just fucking SUCKS now
Post by: bandit957 on February 29, 2016, 02:40:08 PM
Notice that Street View just removed the house numbers from the little box with the street name.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 29, 2016, 05:43:16 PM
Quote from: billtm on February 28, 2016, 07:06:59 PM
What the frick is going on with Google Maps now! :banghead: Last week street view wouldn't work, and now the map is lagging to the point where it takes a minute to load a city! To top it all off, terrain mode is greyed out everywhere I go! At least I got around the street view problem by using the right-click whats here? feature. But before today, I have never had problems with Google Maps and lag. :pan:
I don't know, but both Google Maps and Google Earth were running slow today for me at work.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on February 29, 2016, 10:21:19 PM
Quote from: vdeane on February 29, 2016, 05:43:16 PM
Quote from: billtm on February 28, 2016, 07:06:59 PM
What the frick is going on with Google Maps now! :banghead: Last week street view wouldn't work, and now the map is lagging to the point where it takes a minute to load a city! To top it all off, terrain mode is greyed out everywhere I go! At least I got around the street view problem by using the right-click whats here? feature. But before today, I have never had problems with Google Maps and lag. :pan:
I don't know, but both Google Maps and Google Earth were running slow today for me at work.
Google earth works fine for me, but the way it labels roads is not nice for route tracking. Just checked, and it looks like they finally brought back terrain mode, which I like alot for river tracking. It looks like its back up to speed too, so I don't know what the heck was going on yesterday... :confused:
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 04, 2016, 02:26:56 PM
So how am I supposed to use full mode on my computer? It's an eight-year-old Dell Vostro 2510 running Vista. Since I don't give a shit about video games, everything else I do runs fine. The version of IE on Vista won't even run full mode. In Firefox, full mode works but after about ten clicks in street view it's eaten so much memory that it won't load anything else. Chrome will soon stop supporting Vista, so while it works now, it probably won't in the future.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on March 07, 2016, 09:40:49 PM
Quote from: NE2 on March 04, 2016, 02:26:56 PM
So how am I supposed to use full mode on my computer? It's an eight-year-old Dell Vostro 2510 running Vista. Since I don't give a shit about video games, everything else I do runs fine. The version of IE on Vista won't even run full mode. In Firefox, full mode works but after about ten clicks in street view it's eaten so much memory that it won't load anything else. Chrome will soon stop supporting Vista, so while it works now, it probably won't in the future.
It might be slight overkill, but the best long term option (IMO) is to get a new computer. You can get a nice new laptop running windows 10 with a core i5 and 64GBs of ram for $375.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on March 08, 2016, 12:36:44 AM
A new computer just to run a website that used to work just fine. Thanks, planned obsolescence!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on March 08, 2016, 08:39:28 AM
Quote from: NE2 on March 08, 2016, 12:36:44 AM
A new computer just to run a website that used to work just fine. Thanks, planned obsolescence!

All computers have their limits. Sounds like yours is nearing its end.
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on March 14, 2016, 07:48:54 PM
I've been using Google Maps a bit the past month. Some things have improved. But, there's still some absurd limitations.

Can't move the man around once you drop him (you can click on the little insert map, but that doesn't work entirely).

My biggest complaint is still the driving directions. Because it's no longer HTML text boxes, they don't work the same with tab, CTRL+A, etc.

But, it also limits your point selections much more than previously. And, they insist on choosing a route first, rather than showing you the most likely and then allowing you to click on another option. Also, for longer trips, they insist on giving a flight option.

Which is ridiculous. If I was looking for directions between Cleveland and New Orleans, it's because I want to drive there. I don't think a suggestion to fly is going to set off a light in my mind).

The other thing is the distortion of the street view even moreso to get rid of identifying marks and signs. Nothing more annoying than trying to see a business or information sign, only to see the sign blurred.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on April 04, 2016, 10:44:10 AM
Google Maps finally put most of the new Autopista Durango - Mazatlan (40D) on street view. I'm exploring it right now. Sadly this will probably renew my excitement for wanting to do this trip.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 13, 2016, 12:06:43 AM
I swear, too many locations on Google Maps Street View are deliberately being blurred for no reason, especially in Georgia. My most recent gripe, over on US 19 in Georgia in the Chattahoochee-Oconee National Forest at this little natural landmark called "Stonepile Gap," there's a bicycle sign with two supplemental signs attached to it; one on the top and one on the bottom. Now due to the blurring, I can barely make out the one on the bottom that reads "Share the Road," but I haven't got the foggiest idea what the one on the top says.

Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 13, 2016, 01:06:34 PM
Indeed.  I was using Google Maps to try to find parking in Saratoga Springs last week and found a lot that was claimed to allow all day parking on the internet, but there was some sign that I couldn't read at the entrance, so I thought I wouldn't be able to use that lot.  Thankfully, someone who knows the area better claimed it was all day, and when I got there, it turned out the sign said "48 hour parking".  The blurring is defeating the point of even having street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on May 13, 2016, 07:17:04 PM
google maps is great again, google map maker is a piece of shit
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on May 13, 2016, 09:14:27 PM
Quote from: vdeane on May 13, 2016, 01:06:34 PM
Indeed.  I was using Google Maps to try to find parking in Saratoga Springs last week and found a lot that was claimed to allow all day parking on the internet, but there was some sign that I couldn't read at the entrance, so I thought I wouldn't be able to use that lot.  Thankfully, someone who knows the area better claimed it was all day, and when I got there, it turned out the sign said "48 hour parking".  The blurring is defeating the point of even having street view.

(https://i.imgflip.com/144ezd.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 14, 2016, 01:07:50 AM
Privacy trumps all. In every scenario. Street View is no different (hell, Street View is a textbook example of how privacy concerns can, to an extreme degree, hinder the usefulness of a product). The blurring you (vdeane) and the rest of us see is likely the result of an extremely complex algorithm confusing parking signs with other text such as licence plates, which is considered private information, and as such, is blurred automatically by the server. I'm sure if Google knew how to blur exactly what should be blurred, and not blur what shouldn't be, they'd have implemented said changes by now.

tl;dr: Google also doesn't like blurring stupid stuff like road signs, but the servers aren't smart enough to tell the difference...yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 14, 2016, 02:34:17 PM
But is street view a huge invasion of privacy?  It's just a snapshot, no different than if you observed someone on a street (or are we all now going to get eye implants that blurs out faces and licence plates of people who aren't our friends?).  It's not like they offered the ability to search for someone's image or aggregates where you're going all the time (which is where the problems come in... it's not the little pieces of information, it's what they can add up to if aggregated; however, as long as aggregation is impossible, as it is in street view, it's not an issue).  It's amazing how people are so paranoid about street view and then happily uses Facebook's new "reactions", which are basically a way for Facebook to analyze how you think so they can sell the data.
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on May 14, 2016, 05:01:09 PM
Quote from: vdeane on May 14, 2016, 02:34:17 PM
But is street view a huge invasion of privacy?  It's just a snapshot, no different than if you observed someone on a street (or are we all now going to get eye implants that blurs out faces and licence plates of people who aren't our friends?).  It's not like they offered the ability to search for someone's image or aggregates where you're going all the time (which is where the problems come in... it's not the little pieces of information, it's what they can add up to if aggregated; however, as long as aggregation is impossible, as it is in street view, it's not an issue).  It's amazing how people are so paranoid about street view and then happily uses Facebook's new "reactions", which are basically a way for Facebook to analyze how you think so they can sell the data.

I think Google's intention on blurring faces wasn't anything to do with privacy but rather just courtesy so someone's face isn't permanently emblazoned on Google, especially in instances where they're in front of their house (and a good reason for license plates to be blurred when in residential areas where it would be easy to mark a house to a license plate without driving by yourself.

In the end, Google does as they always do... go too far.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 15, 2016, 05:15:29 PM
I think it also had something to do with the EU, maybe even an attempt to placate Germany (which ultimately banned street view driving).
Title: Re: Google Maps just fucking SUCKS now
Post by: bandit957 on May 16, 2016, 02:34:03 PM
Quote from: vdeane on May 15, 2016, 05:15:29 PM
I think it also had something to do with the EU

So they did it for the wrong reasons.

What's next? Are they going to do what Yahoo did and please Red China by turning in journalists?
Title: Re: Google Maps just fucking SUCKS now
Post by: bandit957 on May 16, 2016, 02:37:17 PM
Lately I've noticed that at the top of the map, there's this skinny horizontal blue bar that continually "shoots" across the screen. What is this for? It is annoying, and has to go.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on May 16, 2016, 02:50:24 PM
Quote from: bandit957 on May 16, 2016, 02:37:17 PM
Lately I've noticed that at the top of the map, there's this skinny horizontal blue bar that continually "shoots" across the screen. What is this for? It is annoying, and has to go.
I think it's Google's "loading" image. IDK why it doesn't go away though.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 16, 2016, 05:11:34 PM
Quote from: freebrickproductions on May 16, 2016, 02:50:24 PM
Quote from: bandit957 on May 16, 2016, 02:37:17 PM
Lately I've noticed that at the top of the map, there's this skinny horizontal blue bar that continually "shoots" across the screen. What is this for? It is annoying, and has to go.

I think it's Google's "loading" image. IDK why it doesn't go away though.

Yes it's the loading bar. It appears to be a glitch. I see it too. Driving me nuts. Goes away if you refresh. 
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on May 16, 2016, 09:03:28 PM
Quote from: jakeroot on May 16, 2016, 05:11:34 PM
Quote from: freebrickproductions on May 16, 2016, 02:50:24 PM
Quote from: bandit957 on May 16, 2016, 02:37:17 PM
Lately I've noticed that at the top of the map, there's this skinny horizontal blue bar that continually "shoots" across the screen. What is this for? It is annoying, and has to go.

I think it's Google's "loading" image. IDK why it doesn't go away though.

Yes it's the loading bar. It appears to be a glitch. I see it too. Driving me nuts. Goes away if you refresh. 

When I see it, it won't let me do anything other than move the map around and gives a 'ding' sound. Only solution for me is to close the window (or back out of the page) and try again. It won't show up the Earth tab, zoom won't work, and the SV icon won't show up. Nor will it show you the directions if that's what you were trying to get, or info, etc.

For a while I thought GM was finally improving, and then this happens.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 16, 2016, 09:52:37 PM
Quote from: Sykotyk on May 16, 2016, 09:03:28 PM
When I see it, it won't let me do anything other than move the map around and gives a 'ding' sound. Only solution for me is to close the window (or back out of the page) and try again. It won't show up the Earth tab, zoom won't work, and the SV icon won't show up. Nor will it show you the directions if that's what you were trying to get, or info, etc.

For a while I thought GM was finally improving, and then this happens.

Perhaps we need more input from the rest of the users. None of the things you are describing, short of the continuous loading bar (which has actually gone away for me, now that I'm skipping around Google Maps) are things that I have experienced.

I suspect this is a simple code error, and will be fixed in a timely manner (like I said, the problems have already been solved on my end, so perhaps they're already on top of this).
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on May 17, 2016, 09:49:28 AM
Quote from: jakeroot on May 16, 2016, 09:52:37 PM
Quote from: Sykotyk on May 16, 2016, 09:03:28 PM
When I see it, it won't let me do anything other than move the map around and gives a 'ding' sound. Only solution for me is to close the window (or back out of the page) and try again. It won't show up the Earth tab, zoom won't work, and the SV icon won't show up. Nor will it show you the directions if that's what you were trying to get, or info, etc.

For a while I thought GM was finally improving, and then this happens.

Perhaps we need more input from the rest of the users. None of the things you are describing, short of the continuous loading bar (which has actually gone away for me, now that I'm skipping around Google Maps) are things that I have experienced.

I suspect this is a simple code error, and will be fixed in a timely manner (like I said, the problems have already been solved on my end, so perhaps they're already on top of this).
I'm the same as you jakeroot. Other than the loading bar, I ain't noticing any issues like what Sykotyk is describing.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 17, 2016, 12:47:11 PM
Is it true that it never finishes loading or are people just not giving it a chance?  I've never had one get stuck, but while you're panning the map, it won't be working on loading the interface not matter how fast that blue thing moves.  You have to let the map sit still for a few seconds to let it finish loading (it does seem to take a bit longer; the blue thing must be chewing up the browser's processing power).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 17, 2016, 12:59:14 PM
Quote from: vdeane on May 17, 2016, 12:47:11 PM
Is it true that it never finishes loading or are people just not giving it a chance?  I've never had one get stuck, but while you're panning the map, it won't be working on loading the interface not matter how fast that blue thing moves.  You have to let the map sit still for a few seconds to let it finish loading (it does seem to take a bit longer; the blue thing must be chewing up the browser's processing power).

I didn't notice any correlation. I let it sit numerous times for 10-20 seconds, and it just kept zooming across and zooming across, over and over and over...you get the point.

But like I said, I don't seem to have the issue anymore. Hell, I can barely get the loading bar to show up at all. On first load, if I immediately slam on the directions button, it'll zoom across once or twice, but then immediately goes away.
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on May 17, 2016, 02:42:28 PM
Quote from: vdeane on May 17, 2016, 12:47:11 PM
Is it true that it never finishes loading or are people just not giving it a chance?  I've never had one get stuck, but while you're panning the map, it won't be working on loading the interface not matter how fast that blue thing moves.  You have to let the map sit still for a few seconds to let it finish loading (it does seem to take a bit longer; the blue thing must be chewing up the browser's processing power).

I've let it sit and sit and sit. Open a new tab to google and search the same thing and it loads fine while the original tab is still in 'flying blue loading bar' mode. Once it decides to start up the loading bar, that tab is shot. It will not load google maps properly in that tab no matter how much you want it to.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 22, 2016, 12:10:15 AM
What happened to all the roads in South Korea?  :confused: None of them are showing up. Is anyone else having that problem?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 22, 2016, 12:33:02 AM
Quote from: US 41 on May 22, 2016, 12:10:15 AM
What happened to all the roads in South Korea?  :confused: None of them are showing up. Is anyone else having that problem?

I was browsing around the Incheon area yesterday, and couldn't help but notice how blurry everything was. Turns out, the Korean government has pretty stringent mapping laws. Google (plus every other mapping organization) is pretty limited in what it can map. There are no directions, and the maps must be intentionally blurry.

As to the roads themselves, G:Maps in South Korea is basically limited to two or three things: a map, which is blurry, and a crappy satellite mode, with no overlay. There is Street View, which is a nice surprise, but that's about the biggest luxury there is (the imagery is, however, quite old, and there are no street names)
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on May 22, 2016, 01:01:39 AM
Quote from: vdeane on May 15, 2016, 05:15:29 PM
I think it also had something to do with the EU, maybe even an attempt to placate Germany (which ultimately banned street view driving).

Not just the EU. Many other countries in the world (including the US) have a concept in intellectual property law called right of publicity - basically, if Google (or anyone) uses your personal image without your consent, you may have legal grounds to sue them and make them take it down.

It is rather annoying that the algorithm is overzealous and blurs things that don't need blurring, but it's better that than have it be underzealous and not blur things it should. For both legal reasons and because protecting people's privacy is a legitimate concern.

Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on May 22, 2016, 01:22:43 PM
Quote from: US 41 on May 22, 2016, 12:10:15 AM
What happened to all the roads in South Korea?  :confused: None of them are showing up. Is anyone else having that problem?
I can see the roads just fine in map view, but not in satellite view (as noted previously).  Meanwhile, North Korea shows up just fine (surprisingly, no Street View though!).  Yesterday I was scrolling along the border in satellite, but had to keep switching back and forth to map view just to see the border line itself.  Just now, however, I checked, and the border is once again showing up in satellite view.

Here's an interesting spot - the Joint Security Area where the two sides have face to face meetings in buildings on the border:
https://www.google.com/maps/@37.955861,126.6782779,17z/data=!3m1!1e3?force=lite (https://www.google.com/maps/@37.955861,126.6782779,17z/data=!3m1!1e3?force=lite)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 22, 2016, 02:07:16 PM
You'd think North Korea would WANT street view; it would be a chance for them to put on the ultimate show for the west where they try to convince everyone they're prosperous.  But maybe Google doesn't want to deal with "the car will show up at place X exactly at time Y under escort so we can show your viewers scene Z".  For that matter, they might not want to deal with North Korea anyways... I remember when the country was just a sea of blank data, without even geographic features that are obvious from the satellite imagery marked.

Quote from: jakeroot on May 22, 2016, 12:33:02 AM
Quote from: US 41 on May 22, 2016, 12:10:15 AM
What happened to all the roads in South Korea?  :confused: None of them are showing up. Is anyone else having that problem?

I was browsing around the Incheon area yesterday, and couldn't help but notice how blurry everything was. Turns out, the Korean government has pretty stringent mapping laws. Google (plus every other mapping organization) is pretty limited in what it can map. There are no directions, and the maps must be intentionally blurry.

As to the roads themselves, G:Maps in South Korea is basically limited to two or three things: a map, which is blurry, and a crappy satellite mode, with no overlay. There is Street View, which is a nice surprise, but that's about the biggest luxury there is (the imagery is, however, quite old, and there are no street names)
I wonder if South Korea pulled a Germany and banned Google from completing its street view coverage.  They certainly are strict... all the road coverage disappears near the DMZ.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 22, 2016, 02:34:56 PM
Quote from: vdeane on May 22, 2016, 02:07:16 PM
You'd think North Korea would WANT street view; it would be a chance for them to put on the ultimate show for the west where they try to convince everyone they're prosperous.  But maybe Google doesn't want to deal with "the car will show up at place X exactly at time Y under escort so we can show your viewers scene Z".

I think even North Korea knows that might be a stretch, at least as far as getting everything setup and whatnot. It would be a nice PR stunt though!

Quote from: vdeane on May 22, 2016, 02:07:16 PM
I wonder if South Korea pulled a Germany and banned Google from completing its street view coverage.  They certainly are strict... all the road coverage disappears near the DMZ.

It certainly seems that way. Seoul and Busan are the only cities in South Korea that have any Street View. And, as I said before, it's quite old. The imagery was published in 2012, so I would guess that they stopped trying to capture imagery.

I did some more reading, and perhaps if Google had some headquarters in South Korea, there might be better maps and Street View. Apparently this law is related to foreign companies mapping vs domestic ones.
Title: Re: Google Maps just fucking SUCKS now
Post by: US71 on May 23, 2016, 02:10:11 PM
I did an SCA gathering at Washington State Park north of Hope, AR this last weekend. Google maps said follow US 71 & US 270 to Hwy 27 South.

The actual directions should have said 71 to 270 to 27. If you look at the map, you can see which way to go. If you simply follow the directions, you'll get lost (2 people did).

Of course, AHTD not co-signing multiplexes didn't help (such as 27 missing from the AR 8 concurrency)
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on May 24, 2016, 11:31:12 PM
So you can't copy-and-paste the directions on the full version of Google Maps anymore in Google Chrome, great...
Doing the same in IE either crashes Word or pastes a huge mess that I don't want to have to deal with.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 24, 2016, 11:38:23 PM
Quote from: freebrickproductions on May 24, 2016, 11:31:12 PM
So you can't copy-and-paste the directions on the full version of Google Maps anymore in Google Chrome, great...
Doing the same in IE either crashes Word or pastes a huge mess that I don't want to have to deal with.

Out of curiosity, why were you copying and pasting directions?
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 25, 2016, 07:44:00 AM
Quote from: jakeroot on May 22, 2016, 02:34:56 PM
Quote from: vdeane on May 22, 2016, 02:07:16 PM
You'd think North Korea would WANT street view; it would be a chance for them to put on the ultimate show for the west where they try to convince everyone they're prosperous.  But maybe Google doesn't want to deal with "the car will show up at place X exactly at time Y under escort so we can show your viewers scene Z".

I think even North Korea knows that might be a stretch, at least as far as getting everything setup and whatnot. It would be a nice PR stunt though!

Google wouldn't do North Korea if North Korea asked. North Korea is a little hellhole controlled by a maniac and you'd have to have an IQ of about 2 to even consider visiting that place.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on May 25, 2016, 10:22:55 AM
Quote from: US 41 on May 25, 2016, 07:44:00 AM
Quote from: jakeroot on May 22, 2016, 02:34:56 PM
Quote from: vdeane on May 22, 2016, 02:07:16 PM
You'd think North Korea would WANT street view; it would be a chance for them to put on the ultimate show for the west where they try to convince everyone they're prosperous.  But maybe Google doesn't want to deal with "the car will show up at place X exactly at time Y under escort so we can show your viewers scene Z".

I think even North Korea knows that might be a stretch, at least as far as getting everything setup and whatnot. It would be a nice PR stunt though!

Google wouldn't do North Korea if North Korea asked. North Korea is a little hellhole controlled by a maniac and you'd have to have an IQ of about 2 to even consider visiting that place.

x1000!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 25, 2016, 02:42:24 PM
Quote from: US 41 on May 25, 2016, 07:44:00 AM
Quote from: jakeroot on May 22, 2016, 02:34:56 PM
Quote from: vdeane on May 22, 2016, 02:07:16 PM
You'd think North Korea would WANT street view; it would be a chance for them to put on the ultimate show for the west where they try to convince everyone they're prosperous.  But maybe Google doesn't want to deal with "the car will show up at place X exactly at time Y under escort so we can show your viewers scene Z".

I think even North Korea knows that might be a stretch, at least as far as getting everything setup and whatnot. It would be a nice PR stunt though!

Google wouldn't do North Korea if North Korea asked. North Korea is a little hellhole controlled by a maniac and you'd have to have an IQ of about 2 to even consider visiting that place.

That's as may be, but Google's decision to roam a country to capture street view imagery is related more to a country's privacy laws than anything else. Google couldn't give a rat's ass about North Korea or its beloved leader, but they do care about their privacy laws, which I'd imagine are pretty strict.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on May 25, 2016, 07:37:27 PM
Quote from: jakeroot on May 24, 2016, 11:38:23 PM
Quote from: freebrickproductions on May 24, 2016, 11:31:12 PM
So you can't copy-and-paste the directions on the full version of Google Maps anymore in Google Chrome, great...
Doing the same in IE either crashes Word or pastes a huge mess that I don't want to have to deal with.

Out of curiosity, why were you copying and pasting directions?
It's easier to copy and paste directions into a Word document to plan a trip for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on July 16, 2016, 12:50:43 PM
Quote from: Sykotyk on May 14, 2016, 05:01:09 PM
I think Google's intention on blurring faces wasn't anything to do with privacy but rather just courtesy so someone's face isn't permanently emblazoned on Google, especially in instances where they're in front of their house (and a good reason for license plates to be blurred when in residential areas where it would be easy to mark a house to a license plate without driving by yourself.

In the end, Google does as they always do... go too far.
You know, blurring faces and license plates are one thing, but blurring signs and scenery are a different story. Even then I could understand if they had an outdated route designation or something. But otherwise, there's just no point.

Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on July 16, 2016, 01:04:06 PM
Quote from: D-Dey65 on July 16, 2016, 12:50:43 PM
Quote from: Sykotyk on May 14, 2016, 05:01:09 PM
I think Google's intention on blurring faces wasn't anything to do with privacy but rather just courtesy so someone's face isn't permanently emblazoned on Google, especially in instances where they're in front of their house (and a good reason for license plates to be blurred when in residential areas where it would be easy to mark a house to a license plate without driving by yourself.

In the end, Google does as they always do... go too far.
You know, blurring faces and license plates are one thing, but blurring signs and scenery are a different story. Even then I could understand if they had an outdated route designation or something. But otherwise, there's just no point.

Unfortunately, Google has a hard time distinguishing between faces and signs, hence why signs are often blurred out.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 16, 2016, 05:40:56 PM
I would assume the issue with the signs is not a problem distinguishing from faces but from licence plates.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 25, 2016, 07:21:12 PM
They're changing the map style again.  I don't like it.
http://www.cnet.com/news/google-maps-update-cleaner-look-areas-of-interest/
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on July 25, 2016, 08:57:08 PM
Quote from: vdeane on July 25, 2016, 07:21:12 PM
They're changing the map style again.  I don't like it.
http://www.cnet.com/news/google-maps-update-cleaner-look-areas-of-interest/

I just now noticed it on my android phone. It looks like shit. Google is just doing to it's maps what they've done to YouTube. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on July 25, 2016, 09:03:20 PM
Quote from: vdeane on July 25, 2016, 07:21:12 PM
They're changing the map style again.  I don't like it.
http://www.cnet.com/news/google-maps-update-cleaner-look-areas-of-interest/

It reminds of Apple Maps, here's a screenshot of the new Google Maps style:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FKKCnR2b.png&hash=108431db9cbba02803c405117ddc9024c059b8f1)

It definitely de-emphasizes the roads without the outlines and the toned-down freeway colours, and while I sort of get what they're going for, I think this is a problem.
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on July 25, 2016, 10:33:06 PM
Google has continued to drag Maps backwards toward the Stone Age.  The newest update is a fucking goddamn worthless pile of rancid dead raccoon flesh sprayed with skunk spray and smeared with donkey shit.  Why do they insist on making streets harder to discern from the background by removing the dark outlines, just to ensure that the number of migraines acquired from trying to read this mess jumps by 1000%?  Why does the text for landmarks look like my computer just reverted back to Windows 3.1?  Why are there random orange puke squares on the screen like I'm playing RollerCoaster Tycoon?  Why does the font for place names have a white outline around it that's less than one pixel wide in spots, rendering it invisible at random spots around each letter?  And most importantly, why reinvent the wheel (and in honor of this here's a song about reinventing the wheel)?!? https://www.youtube.com/watch?v=Q8Z874LS-QY

Listen, Google.  You and I both know that Apple is trying to be a competitor.  But they didn't get going until way after the starting gun, and they continue to be inferior.  So what are you afraid of?  You're worried about people defecting to Apple, really?  So you adapted their style?  WHY?  YOURS WAS ALWAYS BETTER.  Have some fucking balls and stand your ground on what you think Maps are supposed to look like.  You had it right before!!
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on July 25, 2016, 10:34:25 PM
And that's why I like to use satellite view.

Though of course, this is probably all about trying to have "modern" styling. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on July 25, 2016, 10:39:17 PM
I really don't like the new look, the highways are faded and colorless. The new light orange 'points of interest' markings are inconsistent, and show from too far of a zoom level. The markings for schools seem to be completely gone now as well.

Google Maps has had roughly the same colors for highways for the last 7 or 8 years. I don't know why Google can't just let something look the same as it (almost) always has.
Title: Re: Google Maps just fucking SUCKS now
Post by: noelbotevera on July 26, 2016, 12:46:32 AM
Quote from: paulthemapguy on July 25, 2016, 10:33:06 PM
Google has continued to drag Maps backwards toward the Stone Age.  The newest update is a fucking goddamn worthless pile of rancid dead raccoon flesh sprayed with skunk spray and smeared with donkey shit.  Why do they insist on making streets harder to discern from the background by removing the dark outlines, just to ensure that the number of migraines acquired from trying to read this mess jumps by 1000%?  Why does the text for landmarks look like my computer just reverted back to Windows 3.1?  Why are there random orange puke squares on the screen like I'm playing RollerCoaster Tycoon?  Why does the font for place names have a white outline around it that's less than one pixel wide in spots, rendering it invisible at random spots around each letter?  And most importantly, why reinvent the wheel (and in honor of this here's a song about reinventing the wheel)?!?
I actually didn't notice the outline. Most notably is that the freeways make it look like the world is getting paler.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 26, 2016, 01:17:49 AM
If you consider the idea that many people use Google Maps to find places of interest, and not look at roads, the new Google Maps is a nice step in the right direction. And to be completely honest, I don't have any problem with the new colors. I like the more muted palette.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on July 26, 2016, 07:55:14 AM
Quote from: paulthemapguy on July 25, 2016, 10:33:06 PM
The newest update is a fucking goddamn worthless pile of rancid dead raccoon flesh sprayed with skunk spray and smeared with donkey shit. 
So you're not happy with it?
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on July 26, 2016, 08:04:09 AM
Quote from: CtrlAltDel on February 09, 2016, 06:51:07 PM
Quote from: US 41 on February 09, 2016, 09:45:40 AM
I've been using Lite Mode which seems to work fine, but the "Full Mode" Google Maps runs way to slow. But when I'm planning out trips I can't edit my route on Lite Mode, so I still use ClassyGMap as much as I can. Trying to edit a route on Full Google Maps is just plain irritating. Example: You try dragging the edit dot onto US 70 and it puts the edit dot on some alley a quarter of a mile away from US 70. On the ClassyGMap that doesn't happen. It automatically puts the dot on the major highway near by.

This is the "feature" of the new Google Maps that I hate the most. I'm glad someone else doesn't like it either.

On the bright side I noticed that they did fix this issue. I sometimes use the "new" Google Maps for directions, but I still use the KML Map (ClassyGMap) 99% of the time. (If I could still make directions on the KML Map, I'd never use the "new" Google Maps at all.)
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on July 26, 2016, 08:59:08 AM
Quote from: paulthemapguy on July 25, 2016, 10:33:06 PM
Google has continued to drag Maps backwards toward the Stone Age.  The newest update is a fucking goddamn worthless pile of rancid dead raccoon flesh sprayed with skunk spray and smeared with donkey shit.  Why do they insist on making streets harder to discern from the background by removing the dark outlines, just to ensure that the number of migraines acquired from trying to read this mess jumps by 1000%?  Why does the text for landmarks look like my computer just reverted back to Windows 3.1?  Why are there random orange puke squares on the screen like I'm playing RollerCoaster Tycoon?  Why does the font for place names have a white outline around it that's less than one pixel wide in spots, rendering it invisible at random spots around each letter?  And most importantly, why reinvent the wheel (and in honor of this here's a song about reinventing the wheel)?!? https://www.youtube.com/watch?v=Q8Z874LS-QY

Listen, Google.  You and I both know that Apple is trying to be a competitor.  But they didn't get going until way after the starting gun, and they continue to be inferior.  So what are you afraid of?  You're worried about people defecting to Apple, really?  So you adapted their style?  WHY?  YOURS WAS ALWAYS BETTER.  Have some fucking balls and stand your ground on what you think Maps are supposed to look like.  You had it right before!!

:rofl:
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on July 26, 2016, 09:19:03 AM
Google's new color palette looks nicer in Satellite Mode, but a little too muted in standard Map Mode. I guess I'll get used to it.
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on July 26, 2016, 09:37:45 AM
Quote from: freebrickproductions on July 25, 2016, 10:34:25 PM
And that's why I like to use satellite view.

Though of course, this is probably all about trying to have "modern" styling. :banghead:

Adapting to a modern style is always a losing proposition...Modern style is defined by what's happening in the present day, but adapting to a preexisting style means you're referencing something from the past!  "Adapting to the new style" is oxymoronic when the choices you make right now DEFINE the new style!...if that makes sense.  I just don't understand how a bunch of global trendsetters let themselves become submissive to a smaller entity's ideas.

Also I was hoping for my previous post to be rage-filled and also comedic...hope that came across.  Hard to judge tone through text written on the internet.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on July 26, 2016, 09:57:23 AM
Quote from: formulanone on July 26, 2016, 09:19:03 AM
Google's new color palette looks nicer in Satellite Mode, but a little too muted in standard Map Mode. I guess I'll get used to it.

Bingo.  And so will most people.  It's hard to find any website that made a change that didn't rile up its users.  Everything is so much worse now than it was before.  It's shocking that anyone ever uses the internet anymore with all of these changes.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on July 27, 2016, 09:34:29 PM
It'd be nice to be able to switch between "themed" (aka classic/intermediate/new) maps in settings. Sometimes I want to look at a map with roads first, other times with transit first, other times with parks first, etc.

The new place of interest highlighting makes it hard to distinguish things like university campuses from the rest of the city (especially now that they aren't highlighted at all sometimes...even though they're huge places of interest). And the place labels are too big.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F5uOgJcY.png&hash=bc0657ce659b94d96e0bfced886af01f78773fbe)
Title: Re: Google Maps just fucking SUCKS now
Post by: slorydn1 on July 27, 2016, 09:54:34 PM
I don't mind the labels or any of that other BS, but the white roads on a white background-c'mon, really Google??? At anything other than the tightest zoom levels outside of a major city anything lesser than a full freeway is now completely invisible. Thanks for making the map unusable as a map, Google!!
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 27, 2016, 09:59:18 PM
Quote from: slorydn1 on July 27, 2016, 09:54:34 PM
I don't mind the labels or any of that other BS, but the white roads on a white background-c'mon, really Google??? At anything other than the tightest zoom levels outside of a major city anything lesser than a full freeway is now completely invisible. Thanks for making the map unusable as a map, Google!!

I had the same problem even in Google Mapmaker, where it's yellow on white, not white on white. The colors are still too close.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 27, 2016, 10:25:44 PM
Quote from: jakeroot on July 26, 2016, 01:17:49 AM
If you consider the idea that many people use Google Maps to find places of interest, and not look at roads . . .

I think the idea is that places of interest buy advertising, but roads don't. Hence the change in emphasis. That said, I still think the new colors are too muted and blend into one another too easily.

Quote from: US 41 on July 26, 2016, 08:04:09 AM
Quote from: CtrlAltDel on February 09, 2016, 06:51:07 PM
Quote from: US 41 on February 09, 2016, 09:45:40 AM
I've been using Lite Mode which seems to work fine, but the "Full Mode" Google Maps runs way to slow. But when I'm planning out trips I can't edit my route on Lite Mode, so I still use ClassyGMap as much as I can. Trying to edit a routae on Full Google Maps is just plain irritating. Example: You try dragging the edit dot onto US 70 and it puts the edit dot on some alley a quarter of a mile away from US 70. On the ClassyGMap that doesn't happen. It automatically puts the dot on the major highway near by.

This is the "feature" of the new Google Maps that I hate the most. I'm glad someone else doesn't like it either.

On the bright side I noticed that they did fix this issue. I sometimes use the "new" Google Maps for directions, but I still use the KML Map (ClassyGMap) 99% of the time. (If I could still make directions on the KML Map, I'd never use the "new" Google Maps at all.)

This is good to know. Thanks.
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on July 27, 2016, 10:40:16 PM
Quote from: slorydn1 on July 27, 2016, 09:54:34 PM
I don't mind the labels or any of that other BS, but the white roads on a white background-c'mon, really Google??? At anything other than the tightest zoom levels outside of a major city anything lesser than a full freeway is now completely invisible. Thanks for making the map unusable as a map, Google!!

Glad somebody understands my frustration.  Lol.
What's the point of making a MAP if you can't see the MAP
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on July 27, 2016, 10:52:24 PM
Interchanges are also a lot harder to see on the new maps when you're zoomed out.
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on July 27, 2016, 11:03:35 PM
My frustration is that you can't see freeways as easily. It's beige for highways and major arterials, and a stronger beige for freeways.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on July 27, 2016, 11:08:18 PM
Quote from: SignGeek101 on July 27, 2016, 11:03:35 PM
My frustration is that you can't see freeways as easily. It's beige for highways and major arterials, and a stronger beige for freeways.

Biggest pet peeve with the new Maps. I liked the vibrant orange they used to have. Plus, they don't even have the outline for toll roads anymore!
Title: Re: Google Maps just fucking SUCKS now
Post by: compdude787 on July 27, 2016, 11:22:09 PM
Quote from: Zeffy on July 27, 2016, 11:08:18 PM
Plus, they don't even have the outline for toll roads anymore!

That's the one thing that bothers me about the new Google Maps. Other than than that, I don't really mind it all that much. (I know, I know, you're probably all just going to think I'm completely crazy... :P )
Title: Re: Google Maps just fucking SUCKS now
Post by: Duke87 on July 27, 2016, 11:39:49 PM
Remember when Google Maps used to look like this?
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FcPRazCF.png&hash=5020cd471124d9d99c23641767e03a53a0df2462)

Yeah, before we know it the design we just lost will look as primitive as that does.

I am not a fan of muted tones in general though, so...
Title: Re: Google Maps just fucking SUCKS now
Post by: compdude787 on July 27, 2016, 11:52:05 PM
When are tech companies ever going to figure out that people are getting sick of computer software and websites being dumbed down?  :confused:
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on July 28, 2016, 10:33:54 AM
Has nobody else noticed that they DO show incorporated and census-designated places now (without having to select them)?
Title: Re: Google Maps just fucking SUCKS now
Post by: slorydn1 on July 28, 2016, 11:08:15 AM
Quote from: empirestate on July 28, 2016, 10:33:54 AM
Has nobody else noticed that they DO show incorporated and census-designated places now (without having to select them)?

Yes I did notice that, too.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on July 28, 2016, 11:53:19 AM
Quote from: paulthemapguy on July 27, 2016, 10:40:16 PM
Quote from: slorydn1 on July 27, 2016, 09:54:34 PM
I don't mind the labels or any of that other BS, but the white roads on a white background-c'mon, really Google??? At anything other than the tightest zoom levels outside of a major city anything lesser than a full freeway is now completely invisible. Thanks for making the map unusable as a map, Google!!

Glad somebody understands my frustration.  Lol.
What's the point of making a MAP if you can't see the MAP

Kinda like how the phone on a cell phone takes 2nd place to everything else??  :)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 28, 2016, 01:05:01 PM
Seriously, I don't see how all the tech pundits think the new style is easier... I find that it's very hard to see anything but the most major roads at all.  You have to be zoomed much further in to see anything... even businesses, which are supposedly the focus now.  And they no longer differentiate between toll roads and free roads, and what's with having two different styles for freeways (with the style for more minor freeways being more visible except when zoomed way out)?  It's unusable.  Wouldn't be surprised if I end up having to switch to something else for planning roadtrips, just because everything is impossible to see in the new style.

I'm sick and tired of everything being dumbed down on account of phone users.  Let the phone uses have their dumbed down stuff if you must, but keep the desktop working!  Seriously, what's the point of even having a desktop computer if nobody writes software for them any more?
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on July 28, 2016, 02:07:11 PM
Quote from: jeffandnicole on July 28, 2016, 11:53:19 AM
Quote from: paulthemapguy on July 27, 2016, 10:40:16 PM
Quote from: slorydn1 on July 27, 2016, 09:54:34 PM
I don't mind the labels or any of that other BS, but the white roads on a white background-c'mon, really Google??? At anything other than the tightest zoom levels outside of a major city anything lesser than a full freeway is now completely invisible. Thanks for making the map unusable as a map, Google!!

Glad somebody understands my frustration.  Lol.
What's the point of making a MAP if you can't see the MAP

Kinda like how the phone on a cell phone takes 2nd place to everything else??  :)

It is EXACTLY like that.  Brilliantly said.  Excellent simile  :cool:

Quote from: vdeane on July 28, 2016, 01:05:01 PM
Seriously, I don't see how all the tech pundits think the new style is easier... I find that it's very hard to see anything but the most major roads at all.  You have to be zoomed much further in to see anything... even businesses, which are supposedly the focus now.  And they no longer differentiate between toll roads and free roads, and what's with having two different styles for freeways (with the style for more minor freeways being more visible except when zoomed way out)?  It's unusable.  Wouldn't be surprised if I end up having to switch to something else for planning roadtrips, just because everything is impossible to see in the new style.

I'm sick and tired of everything being dumbed down on account of phone users.  Let the phone uses have their dumbed down stuff if you must, but keep the desktop working!  Seriously, what's the point of even having a desktop computer if nobody writes software for them any more?

Everything is impossible to see -> destruction of a map's functionality.  This applies to PC's AND portable devices.
And I totally agree on your last point...It's almost like they're acting as if phones are going to REPLACE laptops and PC's.  Uhhh, the laptops and PC's aren't being phased out at all...so we should keep making stuff for them too
Title: Re: Google Maps just fucking SUCKS now
Post by: Thing 342 on July 28, 2016, 02:24:04 PM
I think the new UI is ok; only marginal improvement on the eye appeal and slightly worse functionality but not the massive disaster you guys seem to think it is. However, I do think the reasons they specified on the blog post were bullshit made up after the fact to justify the redesign, since it seems like none of the use cases they specified were all that common, and it doesn't seem to address them all that well.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on July 28, 2016, 02:28:26 PM
Just to be the voice of a different perspective, my reaction so far is that it's different. Not better or worse, just different. Some stuff is harder to see but some is easier. Certainly, I hate it far less than recent redesigns of MapQuest (not the current one, which I hadn't even noticed–I must say, I kind of dig how they're doing route shields now) or even OSM.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on July 28, 2016, 02:40:32 PM
Quote from: vdeane on July 28, 2016, 01:05:01 PM
Seriously, I don't see how all the tech pundits think the new style is easier... I find that it's very hard to see anything but the most major roads at all.  You have to be zoomed much further in to see anything... even businesses, which are supposedly the focus now.  And they no longer differentiate between toll roads and free roads, and what's with having two different styles for freeways (with the style for more minor freeways being more visible except when zoomed way out)?  It's unusable.  Wouldn't be surprised if I end up having to switch to something else for planning roadtrips, just because everything is impossible to see in the new style.

I just noticed this too. I would argue it emphasizes the minor freeways more, even though they're a lower class of road compared to a full freeway :pan:
In the example below, A-50 at the top looks more prominent than ON 417 below, even though A-50 is a super-two, while the 417 is a 4-lane freeway.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FpQ8cgJ8.png&hash=24ad18b7f1c293170a0bb8603815772c26ab7b5f)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 28, 2016, 02:54:56 PM
I will say that the shading of areas of interest does make it easier to locate businesses along an interstate, but at the same time, it's really annoying to have to zoom in close enough to measure the lane widths in order to see any businesses appear; combine that with the difficulty in seeing streets and interchanges, plus the loss of symbology of toll roads, definitely makes it a net negative.  While I don't particularly like the new color scheme, that alone I could get used to if not for the other issues affecting usability.
Title: Re: Google Maps just fucking SUCKS now
Post by: Thing 342 on July 28, 2016, 03:04:38 PM
Quote from: empirestate on July 28, 2016, 02:28:26 PM
Just to be the voice of a different perspective, my reaction so far is that it's different. Not better or worse, just different. Some stuff is harder to see but some is easier. Certainly, I hate it far less than recent redesigns of MapQuest (not the current one, which I hadn't even noticed–I must say, I kind of dig how they're doing route shields now) or even OSM.
Speaking of which, what is this recent fascination with making all of the roads the same color? OSM, MapQuest, and now GMaps have all recently gotten redesigns that have made different classes of routes nearly impossible to discern from each other, specifically freeways.
Title: Re: Google Maps just fucking SUCKS now
Post by: slorydn1 on July 28, 2016, 03:12:06 PM
For giggles I just pulled it up via my phone's app and yep, you guessed it-It sucks there too-so if this was done to make it look/work better on a phone then it was a humongous fail.

I do like the shading of populated places-that helps.

Look, I wasn't one of the ones that went berzerk when the last change (the one that prompted this thread to start with) so it's not just the fact they changed it. Change is good sometimes. But this last change has made the map useless as a map (or should I say as a road map anyway).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 28, 2016, 03:13:20 PM
Yeah, I'm annoyed by the lack of distinction between major functional classes and whether a road is toll or free.

However, MapQuest's vector file is total crap (e.g., actual roads that its routing algorithm fails to recognize, missing road segments altogether, etc.). 

Perhaps it's a race to the bottom where GoogleMaps will simply be the one that's not as awful as the others.

I also don't understand how this is better for phone users.  I'd want the distinctions as a phone user as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 28, 2016, 04:48:23 PM
No one, except us, uses Google Maps to look at roads. This change directly benefits the vast majority of users by highlighting important areas of interest (the orange blocks on the map), and muting the rest.

This change annoys us because it makes it a hair more difficult to look at maps. But, remember, we are in the minority of users. No one uses Google Maps in the same way as us.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 28, 2016, 04:53:41 PM
Businesses and areas of interest are not the same thing. (The Robert Frost Farm in Derry, NH is definitely an area of interest, but it is not shown in orange.)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 28, 2016, 04:58:13 PM
Quote from: 1 on July 28, 2016, 04:53:41 PM
Businesses and areas of interest are not the same thing. (The Robert Frost Farm in Derry, NH is definitely an area of interest, but it is not shown in orange.)

Key word is "areas" (plural). Not all businesses are highlighted in orange. Areas with high levels of business activity (like downtown areas or areas near shopping malls) are orange.
Title: Re: Google Maps just fucking SUCKS now
Post by: compdude787 on July 29, 2016, 02:08:24 AM
It seems that they've forgotten the primary use of maps, which is for navigation. If you can't see the roads clearly, it makes it harder to navigate. But then again, people don't just look at a map like Google Maps to navigate, they just put in the start and end point and then get GPS directions. As for me, I'm too cool for a GPS. :cool: I just look at the roads on the map and am able to remember the route in my head.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 29, 2016, 09:08:42 AM
Quote from: jakeroot on July 28, 2016, 04:48:23 PM
No one, except us, uses Google Maps to look at roads. This change directly benefits the vast majority of users by highlighting important areas of interest (the orange blocks on the map), and muting the rest.

I really doubt that this is the case.  I'm sure those even just using it as a GPS would like to tell if they're unexpectedly coming up on a toll road.
Title: Re: Google Maps just fucking SUCKS now
Post by: Zeffy on July 29, 2016, 09:21:28 AM
I definitely know more than a few people who aren't roadgeeks but use Google Maps for navigational purposes (I.E. seeing which roads go where). It's a good habit to know alternate routes in this state because it's not that unlikely you'll run into a traffic jam that can be avoided if you know alternate ways.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 29, 2016, 10:32:17 AM
Quote from: Rothman on July 29, 2016, 09:08:42 AM
Quote from: jakeroot on July 28, 2016, 04:48:23 PM
No one, except us, uses Google Maps to look at roads. This change directly benefits the vast majority of users by highlighting important areas of interest (the orange blocks on the map), and muting the rest.

I really doubt that this is the case.  I'm sure those even just using it as a GPS would like to tell if they're unexpectedly coming up on a toll toad.

You can still see which roads are tolls, so long as you plug in some directions:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FZyq3zqy.jpg&hash=68b7e12ac6b266b30cffb179da26184442a37d7c)
Title: Re: Google Maps just fucking SUCKS now
Post by: TXtoNJ on July 29, 2016, 10:35:30 AM
Quote from: compdude787 on July 27, 2016, 11:52:05 PM
When are tech companies ever going to figure out that people are getting sick of computer software and websites being dumbed down?  :confused:

Never, because they're not. Most people don't like too much complexity in their navigational systems. Roadgeeks like us do.

I think the upgrades are an improvement; however; they do force you to mess with your display contrast and brightness if you don't already have them optimized.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 29, 2016, 01:06:22 PM
Yeah, my home display isn't; I actually had to change the default theme for the text editor in Linux Mint because I couldn't see the highlighting of the current line in the default theme.  Now that I think about it, the minor roads do seem to be more visible at work.  I'm not an expert in monitors, though, so I'm not sure how to fix it.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on July 29, 2016, 01:09:20 PM
I actually think the new Google Maps is getting to be a lot better than what it used to be. I still use the KML Map (ClassyGMap), but the new Google Maps has a lot of neat functions.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 29, 2016, 02:20:29 PM
Quote from: jakeroot on July 29, 2016, 10:32:17 AM
Quote from: Rothman on July 29, 2016, 09:08:42 AM
Quote from: jakeroot on July 28, 2016, 04:48:23 PM
No one, except us, uses Google Maps to look at roads. This change directly benefits the vast majority of users by highlighting important areas of interest (the orange blocks on the map), and muting the rest.

I really doubt that this is the case.  I'm sure those even just using it as a GPS would like to tell if they're unexpectedly coming up on a toll toad.

You can still see which roads are tolls, so long as you plug in some directions:


Meh.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 29, 2016, 02:21:02 PM
Quote from: US 41 on July 29, 2016, 01:09:20 PM
I actually think the new Google Maps is getting to be a lot better than what it used to be. I still use the KML Map (ClassyGMap), but the new Google Maps has a lot of neat functions.

The multiple destination feature in the mobile version was very, very late in coming, but I'm grateful that it's now here.
Title: Re: Google Maps just fucking SUCKS now
Post by: TXtoNJ on July 29, 2016, 04:37:54 PM
The clear delineation of commercial districts using orange tiles is an awesome feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 29, 2016, 05:02:13 PM
I got used to it in about two days.  Crisis averted.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 30, 2016, 01:38:20 AM
While toll roads no longer have that stripe on the sides, a lot of ramps still do, like you can see here. https://www.google.com/maps/@41.8792165,-87.919907,16.5z

That makes me wonder if their absence is just a temporary thing.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on July 31, 2016, 01:22:21 PM
I don't think it's been mentioned yet, but they've now made it easier to move around in street view on mobile (or at least on my iPad anyway). Instead of clicking the arrows, which can be slow and tedious, you can now quickly swipe to move.
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on August 02, 2016, 01:05:15 AM
Quote from: 7/8 on July 31, 2016, 01:22:21 PM
I don't think it's been mentioned yet, but they've now made it easier to move around in street view on mobile (or at least on my iPad anyway). Instead of clicking the arrows, which can be slow and tedious, you can now quickly swipe to move.

Nice feature I guess.  Doesn't do me a whole lot of good on my traditional computers which don't have a touch interface.  :-/
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on August 02, 2016, 06:51:47 AM
Quote from: 7/8 on July 31, 2016, 01:22:21 PM
I don't think it's been mentioned yet, but they've now made it easier to move around in street view on mobile (or at least on my iPad anyway). Instead of clicking the arrows, which can be slow and tedious, you can now quickly swipe to move.

I find this feature to be helpful when you want to pan and swivel your view, but annoying when it assumes you don't want to pan, and moves you forward/back/left/right instead. I haven't quite figured out where that tipping point is...
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on August 03, 2016, 09:19:16 PM
New problem; During my June excursion into the New York Tri-State Area, I spent a day in Brooklyn. And on that day I walked from the Prospect Avenue entrance at Park Place station on the Franklin Avenue Shuttle to Franklin Avenue itself, to Bergen Street to Utica Avenue before finally catching the IND Fulton Line station at Boys and Girls High School. When I tried to find out the walking distance between these two spots, it kept directing me two blocks west of the Park Place station and around the two blocks, and it wouldn't let me delete that part!
:pan:

On the plus side, I was able to add some info on some rest areas off of I-20 in Georgia.

Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on September 05, 2016, 08:14:59 PM
A small change I've noticed from the past few days. Google Street View has a new "Expand" button in the bottom left (see red circle in screenshot below):

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F7qZbCur.png&hash=d0e4b1b71c8180f13023af7793621539a8a67eac) (http://i.imgur.com/7qZbCur.png)

This expands the box in the lower left corner to fill the bottom half of the page, allowing you to click on new Street View locations in a bigger area. You can minimize this by clicking the square in the bottom left:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FOIHmjbY.png&hash=aa425e8e0cb4a6fa44904745f06f19d1f88cc915) (http://i.imgur.com/OIHmjbY.png)

The only thing I have to get used to is the removal of the "Back to Map" button in the lower left corner (see red circle), taken 3 weeks ago:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FosDk3wa.png&hash=4886b64637c50e69c7391855aeb05d6a44cfc824) (http://i.imgur.com/osDk3wa.png)

Instead, the only way out of street view is to click the arrow in the top left corner, which has been around for a long time (but I personally never used) (see red circle):

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FySWzea0.png&hash=ead0bd2cb4a9d9b38705f2cd882b60b24fef024e) (http://i.imgur.com/ySWzea0.png)

I'm sure it won't take me long to get used to using the arrow in the top left corner, and I think the expand box could come in handy.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 13, 2016, 04:50:55 PM
Well, looks like corporate ads have started appearing for some users:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FSncMIeC.png&hash=4a35f0687a7d2b59688163d251502b722babab65)

Makes it really easy to see the number of Starbucks in Downtown Seattle.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FJk06AUY.png&hash=dce29f35c6803ed7b5361bb08333a19cfa49f141)
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on September 13, 2016, 05:31:44 PM
Jeez.  Just the other day I was saying that a web search to locate the nearest Starbucks is just too much work, and I needed their locations to pop up every time I use google maps without being asked.
Title: Re: Google Maps just fucking SUCKS now
Post by: TR69 on September 14, 2016, 09:34:31 AM
Quote from: Bruce on September 13, 2016, 04:50:55 PM
Well, looks like corporate ads have started appearing for some users:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FSncMIeC.png&hash=4a35f0687a7d2b59688163d251502b722babab65)



Hmm, I pulled up your Totem Park example on my laptop, using Chrome, and I still just got the old generic icons for the businesses -- no corporate logos.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 13, 2016, 01:07:09 PM
Probably a repeat of a complaint:

A lot of people plan trips in the winter that they'll take in the summer.  Google Maps allows you to change your departure date to avoid seasonal road closures...but then you can't do multiple destination trips!  WTF?!
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 13, 2016, 01:15:02 PM
My main problem with Google Maps (enough of a problem that I don't use it as my main online map) is that every time you scroll, it is considered a new page, and even using it for one minute will clog the history bar.

There are other websites that use Google Maps without having a history clogging problem (Google Mapmaker, also websites like zipmap.net and university webpages that are not meant for general purpose maps), but they don't have nearly as many features.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 13, 2016, 01:24:49 PM
That's why I always use Google Maps in an incognito browser window.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 13, 2016, 01:36:24 PM
^^ why exactly is that a complaint? I like that feature. Makes it ridiculously easy to copy links.

Do you guys like to erase your browser history? Too ashamed of all that map browsing? :D
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on December 13, 2016, 01:55:20 PM
Quote from: 1 on December 13, 2016, 01:15:02 PM
My main problem with Google Maps (enough of a problem that I don't use it as my main online map) is that every time you scroll, it is considered a new page, and even using it for one minute will clog the history bar.
Quote from: vdeane on December 13, 2016, 01:24:49 PM
That's why I always use Google Maps in an incognito browser window.

I have a history blocker app that allows you to add websites on it that won't produce history on Chrome (my standard browser). Guess what the only website on it is... I wonder.

Quote from: jakeroot on December 13, 2016, 01:36:24 PM
^^ why exactly is that a complaint? I like that feature. Makes it ridiculously easy to copy links.

Do you guys like to erase your browser history? Too ashamed of all that map browsing? :D

It's less about erasing it, and more about trying to access a webpage you looked at say, two days ago (because you want to), and being spammed with stupid Google Maps links. It is very annoying to say the least.

I don't try to hide anything (that is what incognito is for).  :-D The history list can be an important resource sometimes, and having that essentially taken away from you kind of sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 13, 2016, 07:27:38 PM
Honestly, I don't like the large amount of tracking sites do these days.  I actually do a large percentage of my browsing incognito because I don't want my Google search results affected by whatever happens to cross my mind on any given day.

It's also good for reducing the likelihood of triggering the paywall on certain news sites.  Pretty much any form of tracking using cookies or the browser cache won't work in incognito (IP address and browser header tracking still work, but those are less common and take more work to circumvent, and honestly aren't worth the trouble; dealing with the former will get you on a NSA watch list for using Tor, and the latter can itself be tracked because it's so rare).
Title: Re: Google Maps just fucking SUCKS now
Post by: noelbotevera on December 13, 2016, 10:13:57 PM
Quote from: vdeane on December 13, 2016, 07:27:38 PM
Honestly, I don't like the large amount of tracking sites do these days.  I actually do a large percentage of my browsing incognito because I don't want my Google search results affected by whatever happens to cross my mind on any given day.

It's also good for reducing the likelihood of triggering the paywall on certain news sites.  Pretty much any form of tracking using cookies or the browser cache won't work in incognito (IP address and browser header tracking still work, but those are less common and take more work to circumvent, and honestly aren't worth the trouble; dealing with the former will get you on a NSA watch list for using Tor, and the latter can itself be tracked because it's so rare).
Ads are off to the side, so I don't think of them as a problem. Better than pop-ups.

Paywalls, however, can burn in a fire. I have been able to get around them, however, if you know what to do.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 14, 2016, 12:42:20 PM
Google does more with one's search history than target ads.  It also factors into its relevancy algorithm, so it affects what results appear.  It's probably the luddite in me wishing that I could just have everything work like it did in 2005.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 14, 2016, 01:01:13 PM
Kind of depressing to go through my timeline and see that most of my trips are just to work and back.  Then again, glad I have some sort of proof of where I am if I'm ever falsely accused of a crime.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 14, 2016, 01:34:24 PM
Quote from: Rothman on December 14, 2016, 01:01:13 PMKind of depressing to go through my timeline and see that most of my trips are just to work and back.  Then again, glad I have some sort of proof of where I am if I'm ever falsely accused of a crime.

Where is this timeline?  I don't think I have ever seen it.  (I use a separate GPS recording app on my phone that allows me to segment travel records by vehicle or mode used.)
Title: Re: Google Maps just fucking SUCKS now
Post by: slorydn1 on December 14, 2016, 02:51:11 PM
Quote from: J N Winkler on December 14, 2016, 01:34:24 PM
Quote from: Rothman on December 14, 2016, 01:01:13 PMKind of depressing to go through my timeline and see that most of my trips are just to work and back.  Then again, glad I have some sort of proof of where I am if I'm ever falsely accused of a crime.

Where is this timeline?  I don't think I have ever seen it.  (I use a separate GPS recording app on my phone that allows me to segment travel records by vehicle or mode used.)

Click on the symbol (or picture) at the upper right hand corner that leads to your google account, click on "Your personal info" under "Personal Info and Privacy", scroll down to "Timeline In Google Maps" and click on "See the places you've been".

Your phone has been tattling on you and you haven't even been aware of it, lol.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 14, 2016, 03:13:18 PM
Never seen this before. Definitely didn't know they were following me. But I'm not really surprised. Not angry either. I think it's pretty cool, actually.

EDIT: Noticed there seemed to be a lot of gaps. They have data from way back in 2013 when I visited family in Colorado, but nothing on my jaunt north to Edmonton two summers ago. Then, it hit me: it wasn't tracking me when I had an iPhone. Only when I've had Android phones was it following me. Obviously not surprising given who created Android, but interesting discovery nonetheless.
Title: Re: Google Maps just fucking SUCKS now
Post by: slorydn1 on December 14, 2016, 05:08:35 PM
Quote from: jakeroot on December 14, 2016, 03:13:18 PM
Never seen this before. Definitely didn't know they were following me. But I'm not really surprised. Not angry either. I think it's pretty cool, actually.

EDIT: Noticed there seemed to be a lot of gaps. They have data from way back in 2013 when I visited family in Colorado, but nothing on my jaunt north to Edmonton two summers ago. Then, it hit me: it wasn't tracking me when I had an iPhone. Only when I've had Android phones was it following me. Obviously not surprising given who created Android, but interesting discovery nonetheless.

Yeah it was a shock to me as well when I first found it a year or so ago but it doesn't bother me either. If it had, I would have shut it off.

Actually, I find that it's not exactly accurate. If I pull up one of my road trip dates and match it up with the GPS track I uploaded from my Garmin to the BaseCamp program the overall look zoomed out seems accurate enough but when I zoom in to certain areas I'll note that it seems to jump from one point to another point in a straight line, sometimes missing places where I jumped off for gas (etc). It still is pretty cool though, I'm not complaining either way.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 15, 2016, 01:41:04 PM
Quote from: slorydn1 on December 14, 2016, 02:51:11 PMClick on the symbol (or picture) at the upper right hand corner that leads to your google account, click on "Your personal info" under "Personal Info and Privacy", scroll down to "Timeline In Google Maps" and click on "See the places you've been".

Your phone has been tattling on you and you haven't even been aware of it, lol.

Thanks for the explanation.  When I follow that breadcrumb trail on my phone, I get a dialog that asks me to turn on Location History.  Of course, Google cannot give me a credible assurance that it is not tracking the movements of my phone when Location History is turned off.

Quote from: slorydn1 on December 14, 2016, 05:08:35 PMActually, I find that it's not exactly accurate. If I pull up one of my road trip dates and match it up with the GPS track I uploaded from my Garmin to the BaseCamp program the overall look zoomed out seems accurate enough but when I zoom in to certain areas I'll note that it seems to jump from one point to another point in a straight line, sometimes missing places where I jumped off for gas (etc). It still is pretty cool though, I'm not complaining either way.

Since the main purpose of Google's location tracking appears to be targeted advertising, I suspect a generic set of GPS recording parameters is used that is just precise enough to detect close proximity to mapped businesses.  For my own GPS logs, I use a set of parameters (10 m distance filter, 50 m accuracy filter, 60 sec to match accuracy filter, 120 sec to obtain fix) that keeps me "within the curbs" > 99% of the time and produces tracks that are consistently 2% longer than odometer mileage (in a 2005 Toyota Camry V6 XLE with tire pressures maintained at label + 4 PSI) regardless of distance travelled, but with a lot of random corner-cutting in open areas and a lot of choppiness in downtown areas with tall buildings.  However, that translates to about 1.5 MB (GPX format) per 100 miles.

One reason I keep location history turned off is that I do not want targeted advertising to be visible that conflicts with how I choose to present myself to the world.  For example, I live in a city that is Facebook-notorious for having an adult bookstore next door to a church (the two are on Broadway/US 81 just within the southern Wichita city limits), so if I were a regular churchgoer and that was my church, in principle anyone could walk past my computer and see porn ads.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on January 11, 2017, 11:04:57 PM
Anyone else been having issues with getting Street View to load? Here's a video from a user on a forum I help run highlighting this issue:


I'm also having issues with moving around. It seems like Google will refuse to let me move to certain spots where there are images for no reason at random. Anyone else having that issue?
Title: Re: Google Maps just fucking SUCKS now
Post by: Max Rockatansky on January 11, 2017, 11:10:05 PM
Quote from: freebrickproductions on January 11, 2017, 11:04:57 PM
Anyone else been having issues with getting Street View to load? Here's a video from a user on a forum I help run highlighting this issue:


I'm also having issues with moving around. It seems like Google will refuse to let me move to certain spots where there are images for no reason at random. Anyone else having that issue?

I had the same problem last night and this morning.  It went away around mid-day and hasn't been a problem since.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 11, 2017, 11:11:16 PM
Quote from: freebrickproductions on January 11, 2017, 11:04:57 PM
Anyone else been having issues with getting Street View to load?

I've had some black-screen and failure-to-render issues, but they almost always fix themselves when I click around in the small map in the bottom left, or refresh. Sometimes, it will lock up on me entirely, and I have to refresh to get it to work again properly. Very strange issues, but relatively uncommon in my experience, so it doesn't bug me much.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on January 12, 2017, 05:49:42 PM
It also happened to me using the .es mirror. No longer now, as I'm doing another 'roadtrip' and runs fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 12, 2017, 07:59:37 PM
I've been having this problem the past couple days.
Title: Re: Google Maps just fucking SUCKS now
Post by: Lyon Wonder on January 15, 2017, 05:19:08 PM
state borders are now invisible in google maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on January 15, 2017, 05:38:36 PM
Quote from: Lyon Wonder on January 15, 2017, 05:19:08 PM
state borders are now invisible in google maps.

I had that problem earlier today; it was resolved with a quick stab of the refresh button.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on January 15, 2017, 08:37:15 PM
Quote from: Eth on January 15, 2017, 05:38:36 PM
Quote from: Lyon Wonder on January 15, 2017, 05:19:08 PM
state borders are now invisible in google maps.

I had that problem earlier today; it was resolved with a quick stab of the refresh button.

I tried that but it didn't work. It's fine now though. Just for the record, here's what it looked like:
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi67.tinypic.com%2F24azdec.jpg&hash=9714ad79de504df4f0dd1a473d04a3901659ff6b)
Title: Re: Google Maps just fucking SUCKS now
Post by: Sykotyk on January 16, 2017, 01:12:02 AM
Google has had a known history of experimenting with search algorithms at the same time. So, one person gets one result, another gets another. And they can switch back and forth for the same user. So, one day you'll see an experimental form, and a few days later back to 'normal'. As they determine whether to change full time or not.
Title: Re: Google Maps just f***ing SUCKS now
Post by: 20160805 on January 16, 2017, 07:12:55 AM
The feature I don't understand, but rather enjoy, is that when I'm in Google Street View on my tablet, there has been an odometer thing that pops up after a little while.  It first popped up on 9 August and originally I thought it was for the Olympics, but it didn't go away even after the Paralympics ended.  I've now put on over 4,600 km since the introduction of the feature.

Sometimes, annoyingly, the blue line on the road just dead ends in the middle of nowhere, even though the road physically continues and I'm certain the Google car has gone past that point.  This seems to happen more often on freeways and is why most of my GSV driving is in town and on back roads (not to mention that I find cities more interesting anyway).

Can anyone explain either of these?
Title: Re: Google Maps just fucking SUCKS now
Post by: Buck87 on January 18, 2017, 01:00:22 PM
I wish the measure distance tool was available in lite mode.  The only reason I ever switch from lite mode to the laggy piece of shit full mode is to use that tool, and then I quickly switch back.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on January 18, 2017, 01:43:22 PM
Quote from: J N Winkler on December 15, 2016, 01:41:04 PM
Quote from: slorydn1 on December 14, 2016, 02:51:11 PMClick on the symbol (or picture) at the upper right hand corner that leads to your google account, click on "Your personal info" under "Personal Info and Privacy", scroll down to "Timeline In Google Maps" and click on "See the places you've been".

Your phone has been tattling on you and you haven't even been aware of it, lol.

Thanks for the explanation.  When I follow that breadcrumb trail on my phone, I get a dialog that asks me to turn on Location History.  Of course, Google cannot give me a credible assurance that it is not tracking the movements of my phone when Location History is turned off.

Same here.  I've never enabled my phone's location thingy.
Title: Re: Google Maps just fucking SUCKS now
Post by: F350 on January 24, 2017, 10:00:16 AM
I saved a ton of notes/places I wanted to visit on google maps many years ago. Seems like I lost them even though I saved them with my gmail account. I've been itching to access them, any tips?
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on April 10, 2017, 10:25:44 PM
Quote from: jakeroot on January 11, 2017, 11:11:16 PM
I've had some black-screen and failure-to-render issues, but they almost always fix themselves when I click around in the small map in the bottom left, or refresh. Sometimes, it will lock up on me entirely, and I have to refresh to get it to work again properly. Very strange issues, but relatively uncommon in my experience, so it doesn't bug me much.
I've never tried refreshing it, but I doubt it'll work for me. I often try to point to one road or one off-ramp, and wind up somewhere other than where I want it to point. A most recent example is southbound Exit 143B on I-95 in Virginia. When I try to point to that ramp, it either goes to the main road or the west to south on ramp from VSR 610. I really want to see why there's a split at the end of that off-ramp.

Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on April 10, 2017, 10:36:09 PM
Quote from: D-Dey65 on April 10, 2017, 10:25:44 PM
Quote from: jakeroot on January 11, 2017, 11:11:16 PM
I've had some black-screen and failure-to-render issues, but they almost always fix themselves when I click around in the small map in the bottom left, or refresh. Sometimes, it will lock up on me entirely, and I have to refresh to get it to work again properly. Very strange issues, but relatively uncommon in my experience, so it doesn't bug me much.
I've never tried refreshing it, but I doubt it'll work for me. I often try to point to one road or one off-ramp, and wind up somewhere other than where I want it to point. A most recent example is southbound Exit 143B on I-95 in Virginia. When I try to point to that ramp, it either goes to the main road or the west to south on ramp from VSR 610. I really want to see why there's a split at the end of that off-ramp.

Switching to aerial view appears to answer that question with ease: The split to the left allows traffic to turn right, then access the two left turn lanes for Salisbury Drive.  https://goo.gl/maps/qApVDQVR19m  The turn lanes are separated from the thru lanes via a low-concrete barrier.
Title: Re: Google Maps just fucking SUCKS now
Post by: inkyatari on April 11, 2017, 10:43:13 AM
I was  traveling to Wisconsin over the weekend, and wanted to stop at Kettle  Moraine State Forest - South Unit on my way to my destination, and I could not find it on the map anywhere until I zoomed in very tight, and even then, it only showed about 20% of the forest, and not the area near the headquarters.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on April 25, 2017, 04:33:14 PM
Why do you it sucks? Have not noticed anything different. Unless it was updated again.
Title: Re: Google Maps just fucking SUCKS now
Post by: intelati49 on April 25, 2017, 04:42:47 PM
Check the date. This is from 2014

https://maps.googleblog.com/2014/02/thank-you-and-welcome-to-new-google-maps.html

This is the original google maps. (Which honestly is still my favorite. For some reason I associate Maps with lag nowadays)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fscreenwerk.com%2Fwpn%2Fmedia%2FScreen-Shot-2013-05-17-at-8.12.51-AM.png&hash=d7d517fa0e8e826596316880bb9fae169ba25a34)

Oh, and this thread is just for general complaints/missing features of the new google maps. (Which is fair enough for me)
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on April 25, 2017, 05:19:26 PM
Quote from: Roadgeekteen on April 25, 2017, 04:33:14 PM
Why do you it sucks? Have not noticed anything different. Unless it was updated again.

I know you're new here, but please read through the entire thread before posting. Also, it's okay to read and not post. Post Quality > Post Quantity. 

Quote from: F350 on January 24, 2017, 10:00:16 AM
I saved a ton of notes/places I wanted to visit on google maps many years ago. Seems like I lost them even though I saved them with my gmail account. I've been itching to access them, any tips?

Make sure you log in with the same Google Account login data.

That said, I like that they now allow you to mark a place with your own "label"...handy when you've spotted something in Street View (or real life) for later use.

A recent annoyance is when you search hotels *or* restaurants in an area (something I do when booking work reservations), whereby it shows you restaurants, grocery stores, bodegas, convenience stores, hotels, motels, and hostels...just in case. Sure, give me a side of Attention Deficit Disorder with that!
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 25, 2017, 05:52:39 PM
Quote from: formulanone on April 25, 2017, 05:19:26 PM
I know you're new here, but please read through the entire thread before posting. Also, it's okay to read and not post. Post Quality > Post Quantity. 

24 pages?

Do you expect someone to read the entire 100+ pages of Erroneous Road Signs or Worst of Road Signs, or 50+ pages of "New Jersey Turnpike", "Florida", or "Update on I-69 Extension in Indiana" just before that person is allowed to post?
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on April 25, 2017, 06:40:01 PM
Quote from: 1 on April 25, 2017, 05:52:39 PM
Quote from: formulanone on April 25, 2017, 05:19:26 PM
I know you're new here, but please read through the entire thread before posting. Also, it's okay to read and not post. Post Quality > Post Quantity. 

24 pages?

Do you expect someone to read the entire 100+ pages of Erroneous Road Signs or Worst of Road Signs, or 50+ pages of "New Jersey Turnpike", "Florida", or "Update on I-69 Extension in Indiana" just before that person is allowed to post?
some threads might have 150+ pages.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on April 25, 2017, 06:42:51 PM
Quote from: 1 on April 25, 2017, 05:52:39 PM
Quote from: formulanone on April 25, 2017, 05:19:26 PM
I know you're new here, but please read through the entire thread before posting. Also, it's okay to read and not post. Post Quality > Post Quantity. 

24 pages?

Do you expect someone to read the entire 100+ pages of Erroneous Road Signs or Worst of Road Signs, or 50+ pages of "New Jersey Turnpike", "Florida", or "Update on I-69 Extension in Indiana" just before that person is allowed to post?

Expect? Not really.

Should? Maybe.

The first few pages (to figure out the topic) and the last 3-4 pages (recent developments) of a thread...YES!

I always figured the point of a forum was to learn first, and contribute later, if needed. It's not a stacking contest. Naturally, if a forum is new, it's a bit different.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 25, 2017, 06:49:23 PM
Quote from: Roadgeekteen on April 25, 2017, 06:40:01 PM
Quote from: 1 on April 25, 2017, 05:52:39 PM
Quote from: formulanone on April 25, 2017, 05:19:26 PM
I know you're new here, but please read through the entire thread before posting. Also, it's okay to read and not post. Post Quality > Post Quantity. 

24 pages?

Do you expect someone to read the entire 100+ pages of Erroneous Road Signs or Worst of Road Signs, or 50+ pages of "New Jersey Turnpike", "Florida", or "Update on I-69 Extension in Indiana" just before that person is allowed to post?

some threads might have 150+ pages.

At least use the "search" function before posting your content, just in case somebody already posted similar content.

In your case, before posting, you could have opened this thread (to any page), then searched "why" to see if anyone already asked this question*. If not, feel free to post away.

*in the case of this thread, and most that have a subject similar to "X or Y sucks", post #1 probably explains why the user thinks "it" sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on April 26, 2017, 09:34:10 AM
Has anyone else noticed that in satellite view, they can't just zoom straight into street view on a road anymore? Sometimes it also doesn't let me click to move forward when in street view either.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 26, 2017, 12:44:29 PM
I just tested that and zoom to street view is gone for me too.  Never noticed it because I never use that "feature" - in fact, I hope it stays that way, because before one had to be really careful not to accidentally engage street view if they wanted to zoom in close.  Hopefully they'll remove the ability to zoom out of street view too so that I won't have to be paranoid to zoom out if I zoomed in while within street view; I find it to be EXTREMELY difficult to zoom out without accidentally going back to the map.

Not sure that the issues with clicking to move forward are new; it seem to happen to me intermittently and randomly, and has since the end of classic Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on April 26, 2017, 12:50:10 PM
Well I've never had any issue with accidentally zooming into street view. It wasn't very sensitive, and it showed a circle marker to indicate that any more zooming would enter street view. It just made it more convenient.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on April 26, 2017, 05:17:40 PM
Quote from: jeffandnicole on April 10, 2017, 10:36:09 PM
Switching to aerial view appears to answer that question with ease: The split to the left allows traffic to turn right, then access the two left turn lanes for Salisbury Drive.  https://goo.gl/maps/qApVDQVR19m  The turn lanes are separated from the thru lanes via a low-concrete barrier.
Okay, I suppose I can see that, although it doesn't exactly help me read the signs. I've lost count as to how many times I tried to zoom in on one place, and ended up somewhere I didn't want to be.

I think I might've mentioned this in the past, but it does misidentify a lot of bodies of water between the forks of Long Island.

One other question though; Does anybody know how tall a typical camera on a Google Car is? I'm pretty sure it played a role in my previous misconceptions about the view of 167th Street station on the IRT Jerome Avenue Line from Gerard Avenue in the South Bronx.

https://commons.wikimedia.org/wiki/File:167th_Street_(IRT_Jerome_Avenue_Line)_from_Gerard_Avenue.JPG


https://www.google.com/maps/@40.8354232,-73.9202985,3a,75y,298.79h,89.49t/data=!3m6!1e1!3m4!1suXBONsjKti_Mpec37nuUxw!2e0!7i13312!8i6656?hl=en


I've been guessing the camera was 8 feet above ground level, but I'm not 100% sure.

Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 26, 2017, 06:24:31 PM
Quote from: vdeane on April 26, 2017, 12:44:29 PM
I just tested that and zoom to street view is gone for me too.  Never noticed it because I never use that "feature" - in fact, I hope it stays that way, because before one had to be really careful not to accidentally engage street view if they wanted to zoom in close.  Hopefully they'll remove the ability to zoom out of street view too so that I won't have to be paranoid to zoom out if I zoomed in while within street view; I find it to be EXTREMELY difficult to zoom out without accidentally going back to the map.

Ditto. Zoom in for Street View drove me crazy. I would always zoom too far, and enter Street View. Glad it's gone.

Quote from: Roadsguy on April 26, 2017, 12:50:10 PM
Well I've never had any issue with accidentally zooming into street view. It wasn't very sensitive, and it showed a circle marker to indicate that any more zooming would enter street view. It just made it more convenient.

I never noticed that marker, but I wish I had. Would have made my Maps life a lot easier.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 26, 2017, 09:07:23 PM
The key with zooming is was to do it slowly enough at close zooms that one could notice the circle before street view was triggered.  I still feel like I can zoom in closer now than then, though (which is certainly helpful if one needs to check lane widths).  Unfortunately, there is no way to detect and avoid triggering the zoom out "feature", and that's still there.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on April 26, 2017, 09:37:45 PM
Quote from: Roadsguy on April 26, 2017, 09:34:10 AM
Has anyone else noticed that in satellite view, they can't just zoom straight into street view on a road anymore? Sometimes it also doesn't let me click to move forward when in street view either.
The 'zoom directly into Streetview' was my favorite feature on the old Google Maps.  I liked being able to quickly jump in and out of satellite and I was really disappointed when they got rid of it with the inferior newer version.  I've gotten used to the new Maps, but it's still really slow and it's gotten more difficult to move around in Streetview - often stuck moving only in short increments or randomly dumping me onto another nearby street.  I stay in Lite mode as much as possible.  On my Ipad it defaults into the feature that rotates the view with the device itself, which is really annoying.  For all its flaws though - and there are many - it sure beats the old days without it.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on April 27, 2017, 11:26:32 AM
Quote from: Roadrunner75 on April 26, 2017, 09:37:45 PM
Quote from: Roadsguy on April 26, 2017, 09:34:10 AM
Has anyone else noticed that in satellite view, they can't just zoom straight into street view on a road anymore? Sometimes it also doesn't let me click to move forward when in street view either.
The 'zoom directly into Streetview' was my favorite feature on the old Google Maps.  I liked being able to quickly jump in and out of satellite and I was really disappointed when they got rid of it with the inferior newer version.  I've gotten used to the new Maps, but it's still really slow and it's gotten more difficult to move around in Streetview - often stuck moving only in short increments or randomly dumping me onto another nearby street.  I stay in Lite mode as much as possible.  On my Ipad it defaults into the feature that rotates the view with the device itself, which is really annoying.  For all its flaws though - and there are many - it sure beats the old days without it.

I find that it's much less fiddly to simply click a spot on the road where you want to be, then click on the Street View thumbnail that pops up at the bottom. Less motion than the zoom technique (and easier to carry out on a trackpad).
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on April 28, 2017, 07:20:52 AM
I've also been having mobile Street View problems lately - since about Jan/Feb it's been extremely slow and tedious.  Instead of being able to freely drag the blue line (and thus move) as quickly as possible and thus move up to 110 mph, I now only get to drag it a little bit (0.05 km at most) and then wait for the image to fully load (which takes longer as well) before I can drag again.  There are also more random dead-ends in the blue line, so I'm constantly having to go around blocks and get lost before I can end up where I want to be.

Between 9 Aug 2016 and 9 Feb 2017, I put on about 5100 km in GSV with no problems.  Three months later, my total mileage is only 5500 km because it's just not fun to use if it's going to be slow and hard to use like this.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on April 28, 2017, 12:34:16 PM
Quote from: empirestate on April 27, 2017, 11:26:32 AM
Quote from: Roadrunner75 on April 26, 2017, 09:37:45 PM
Quote from: Roadsguy on April 26, 2017, 09:34:10 AM
Has anyone else noticed that in satellite view, they can't just zoom straight into street view on a road anymore? Sometimes it also doesn't let me click to move forward when in street view either.
The 'zoom directly into Streetview' was my favorite feature on the old Google Maps.  I liked being able to quickly jump in and out of satellite and I was really disappointed when they got rid of it with the inferior newer version.  I've gotten used to the new Maps, but it's still really slow and it's gotten more difficult to move around in Streetview - often stuck moving only in short increments or randomly dumping me onto another nearby street.  I stay in Lite mode as much as possible.  On my Ipad it defaults into the feature that rotates the view with the device itself, which is really annoying.  For all its flaws though - and there are many - it sure beats the old days without it.

I find that it's much less fiddly to simply click a spot on the road where you want to be, then click on the Street View thumbnail that pops up at the bottom. Less motion than the zoom technique (and easier to carry out on a trackpad).

Huh, I never actually noticed you could do that. If the zoom-into-street view feature were still gone, knowing about that would've made it a whole lot easier...

I just went back and tried it out, and it seems like it's back, but only in a few places. It's only letting me do it on a few segments of road, and not others. For me I can do it near the US 322/422/PA 39 interchange in Hershey at least, but I haven't tried anywhere else.

Either way I tried it out a little to see how easy it really is to accidentally enter street view, and it's really not very for me at least. The little circle indicator appears 2-3 zoom levels below the highest, and there seems to be a little bit of "resistance" before the final zoom into street view. Plus if you do accidentally zoom too far, the transition is smooth enough that you can just immediately zoom back out when the view starts tilting and it's like nothing ever happened.
Title: Re: Google Maps just fucking SUCKS now
Post by: sbeaver44 on May 02, 2017, 10:08:17 PM
Since the last update on Android if I click any gmaps links with a lat/lon it loads the app but never goes to the actual place, just shows the last place I was looking at.

Nexus 6P

Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on May 04, 2017, 03:12:50 PM
Zooming into street view seems to work everywhere for me again.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 04, 2017, 03:14:21 PM
Quote from: Roadsguy on May 04, 2017, 03:12:50 PM
Zooming into street view seems to work everywhere for me again.

Same for me. I thought they removed it on purpose. Damn.
Title: Re: Google Maps just fucking SUCKS now
Post by: Highway63 on May 11, 2017, 02:13:34 AM
While in Street View, it has a nasty habit of taking me off the interstate I've been following and dropping me onto the cross-road below. Then I have to return to map view and re-set the PegMan down. Then half the time it happens again.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 11, 2017, 02:24:23 AM
Quote from: Roadsguy on April 28, 2017, 12:34:16 PM
Quote from: empirestate on April 27, 2017, 11:26:32 AM
Quote from: Roadrunner75 on April 26, 2017, 09:37:45 PM
Quote from: Roadsguy on April 26, 2017, 09:34:10 AM
Has anyone else noticed that in satellite view, they can't just zoom straight into street view on a road anymore? Sometimes it also doesn't let me click to move forward when in street view either.
The 'zoom directly into Streetview' was my favorite feature on the old Google Maps.  I liked being able to quickly jump in and out of satellite and I was really disappointed when they got rid of it with the inferior newer version.  I've gotten used to the new Maps, but it's still really slow and it's gotten more difficult to move around in Streetview - often stuck moving only in short increments or randomly dumping me onto another nearby street.  I stay in Lite mode as much as possible.  On my Ipad it defaults into the feature that rotates the view with the device itself, which is really annoying.  For all its flaws though - and there are many - it sure beats the old days without it.

I find that it's much less fiddly to simply click a spot on the road where you want to be, then click on the Street View thumbnail that pops up at the bottom. Less motion than the zoom technique (and easier to carry out on a trackpad).

Huh, I never actually noticed you could do that. If the zoom-into-street view feature were still gone, knowing about that would've made it a whole lot easier...

I just went back and tried it out, and it seems like it's back, but only in a few places. It's only letting me do it on a few segments of road, and not others. For me I can do it near the US 322/422/PA 39 interchange in Hershey at least, but I haven't tried anywhere else.

Either way I tried it out a little to see how easy it really is to accidentally enter street view, and it's really not very for me at least. The little circle indicator appears 2-3 zoom levels below the highest, and there seems to be a little bit of "resistance" before the final zoom into street view. Plus if you do accidentally zoom too far, the transition is smooth enough that you can just immediately zoom back out when the view starts tilting and it's like nothing ever happened.

I've found that this feature doesn't exist when you turn off the (in my opinion unappealing) 3D model. It might not work that way for everyone though.

Quote from: Jeff Morrison on May 11, 2017, 02:13:34 AM
While in Street View, it has a nasty habit of taking me off the interstate I've been following and dropping me onto the cross-road below. Then I have to return to map view and re-set the PegMan down. Then half the time it happens again.

I usually just click on a different bit of the blue line in that little box at the bottom left.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on May 11, 2017, 07:49:38 PM
I'm having some issues with the pegman. When I click on the yellow circle, it doesn't let me go "inside" a place.
Title: Google dun goofed
Post by: Rover_0 on May 12, 2017, 07:58:49 PM
Not that I disagree or anything, but now Google Maps shows US-189 being effectively re-re-aligned onto UT-32:

(https://c1.staticflickr.com/5/4172/34235062430_6205c9fb10_c.jpg)

Two things to note:

First, I would welcome this change, but it's still (as far as I know) incorrect, and

Second, UDOT really needs to end the confusion and just sign US-189 on its US-40 and I-80 concurrencies already.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on May 14, 2017, 08:59:36 AM
It will be a great day when the mobile version of Google Maps has the same functionality of the web version...despite the drawbacks Google is progressively adding to the product.

You share a meticulously planned out trip with your phone and poof!  You lose all your via points between the destinations.
Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on May 16, 2017, 11:29:51 AM
Dammit GSV: https://goo.gl/maps/MqhujQZsQcx (CT 10, Southington, Aug 2015)
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on July 05, 2017, 08:57:20 AM
I noticed the past few weeks that Google Maps has the state/province listed after some cities, but not others. For example:
London, Ontario
Kitchener, Ontario
Toledo, Ohio
Fort Wayne, Indiana

But most only show the city name, for example:
Waterloo
Detroit
Indianapolis

Does anyone else see this on their version?
Title: Re: Google Maps just fucking SUCKS now
Post by: JJBers on July 05, 2017, 10:05:05 AM
Quote from: kurumi on May 16, 2017, 11:29:51 AM
Dammit GSV: https://goo.gl/maps/MqhujQZsQcx (CT 10, Southington, Aug 2015)
That's what you get for having trees
Title: Re: Google Maps just fucking SUCKS now
Post by: Highway63 on July 18, 2017, 12:02:04 PM
Quote from: Roadsguy on May 04, 2017, 03:12:50 PM
Zooming into street view seems to work everywhere for me again.
My problem isn't zooming into Street View, it's trying to follow a freeway along Street View, clicking ahead, and then suddenly being transported to the road above/below. It's maddening.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 19, 2017, 10:34:52 AM
Quote from: Jeff Morrison on July 18, 2017, 12:02:04 PM
Quote from: Roadsguy on May 04, 2017, 03:12:50 PM
Zooming into street view seems to work everywhere for me again.
My problem isn't zooming into Street View, it's trying to follow a freeway along Street View, clicking ahead, and then suddenly being transported to the road above/below. It's maddening.
Truth!
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman on July 19, 2017, 11:20:54 AM
Quote from: Jeff Morrison on July 18, 2017, 12:02:04 PM
My problem isn't zooming into Street View, it's trying to follow a freeway along Street View, clicking ahead, and then suddenly being transported to the road above/below. It's maddening.

^^^^ This times ten thousand.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on July 20, 2017, 01:02:58 PM
Quote from: Jeff Morrison on July 18, 2017, 12:02:04 PM
Quote from: Roadsguy on May 04, 2017, 03:12:50 PM
Zooming into street view seems to work everywhere for me again.
My problem isn't zooming into Street View, it's trying to follow a freeway along Street View, clicking ahead, and then suddenly being transported to the road above/below. It's maddening.
That's always been an issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 20, 2017, 10:50:41 PM
Remember: Street View's "click where you want to go" function doesn't rely on an active AI that's able to comprehend exactly what you're looking at as you're looking at it. The system relies on pre-set data points. You don't realise it, but you've accidentally clicked on a data point for another road. I experience this issue rather often in Japan (elevated roads over other roads are common).

The one problem I have had with that clicking function is that, occasionally, I'll click somewhere, and it will throw me a mile away from where I was. Jumps like those are genuine errors, but Google has to fix them one by one.
Title: Re: Google Maps just fucking SUCKS now
Post by: Aerobird on August 12, 2017, 03:39:14 AM
I've recently, abruptly, had Google Maps in Firefox have all the labels appear upside down and backwards. It doesn't happen in lite mode, or in either mode in Chrome.

A check showed a thread complaning about this from several years ago, with no resolution...
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on August 12, 2017, 10:59:48 PM
This isn't Google Maps but it does relate to it. There is a blog I'd follow from time to time that covers all things Google Earth. The blogger has recently gotten fed up with Google and will no longer post much about it after a decade of running his blog.

https://www.gearthblog.com/

One thing I've noticed is they don't seem to be updating aerial/satellite imagery as much as they used to. Especially in OKC. They used to update it once or twice a year but it's been nearly a year since last update. Same thing in a few other cities.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on August 13, 2017, 08:48:35 AM
Quote from: Plutonic Panda on August 12, 2017, 10:59:48 PM
One thing I've noticed is they don't seem to be updating aerial/satellite imagery as much as they used to. Especially in OKC. They used to update it once or twice a year but it's been nearly a year since last update. Same thing in a few other cities.

When there was an imagery update, there was a little trick you could use to find out where it was updated. Zoom way out, slide the date slider to the current date (just a hair off of all the way to the right) and then click the slider left to see where the imagery became different ∴ updated imagery in that area. Now, since they made the update where blurry low-res imagery is available for every single year since 1984, you can't use that trick anymore.
Title: Re: Google Maps just fucking SUCKS now
Post by: SignGeek101 on August 31, 2017, 10:29:35 AM
Well, it appears I can't change anything or get anything changed when it comes to errors. A week since I reported three errors to Google, and no response.

Also, how am I supposed to change information such as road type (arterial, freeway etc)? I feel like the options presented now are really primitive.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on August 31, 2017, 04:41:41 PM
Quote from: SignGeek101 on August 31, 2017, 10:29:35 AM
Well, it appears I can't change anything or get anything changed when it comes to errors. A week since I reported three errors to Google, and no response.

Also, how am I supposed to change information such as road type (arterial, freeway etc)? I feel like the options presented now are really primitive.

I reported several errors months ago, and nothing has changed.  CT 31 is still a county route north of US 44, someone put a restaurant on a corner where a library is (and misspelled the name of it and put it 4 miles from its correct location) and a Rite Aid is on the wrong side of the street.
Title: Re: Google Maps just fucking SUCKS now
Post by: JJBers on August 31, 2017, 06:24:15 PM
Quote from: jp the roadgeek on August 31, 2017, 04:41:41 PM
Quote from: SignGeek101 on August 31, 2017, 10:29:35 AM
Well, it appears I can't change anything or get anything changed when it comes to errors. A week since I reported three errors to Google, and no response.

Also, how am I supposed to change information such as road type (arterial, freeway etc)? I feel like the options presented now are really primitive.

I reported several errors months ago, and nothing has changed.  CT 31 is still a county route north of US 44, someone put a restaurant on a corner where a library is (and misspelled the name of it and put it 4 miles from its correct location) and a Rite Aid is on the wrong side of the street.
I can fix those last two things, just send the links to the places.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 31, 2017, 06:58:49 PM
A good way to get on Google's "trusted" side is to send a link along with your error report, often a website with the correct information, so that Google isn't just taking your word for things.

I've been sending errors to El Goog for a long time, always with a link attached. Nowadays, most errors I report are fixed within 24 hours.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on August 31, 2017, 09:08:30 PM
Quote from: JJBers on August 31, 2017, 06:24:15 PM
Quote from: jp the roadgeek on August 31, 2017, 04:41:41 PM
Quote from: SignGeek101 on August 31, 2017, 10:29:35 AM
Well, it appears I can't change anything or get anything changed when it comes to errors. A week since I reported three errors to Google, and no response.

Also, how am I supposed to change information such as road type (arterial, freeway etc)? I feel like the options presented now are really primitive.

I reported several errors months ago, and nothing has changed.  CT 31 is still a county route north of US 44, someone put a restaurant on a corner where a library is (and misspelled the name of it and put it 4 miles from its correct location) and a Rite Aid is on the wrong side of the street.
I can fix those last two things, just send the links to the places.

First one at the corner of CT 10 and CT 120.  The correct location is already accounted for, so it needs to be deleted.

https://www.google.com/maps/@41.5964205,-72.8778859,19z


Second one:  Rite Aid.  Location info correct, but location on map incorrect.  Needs to be the building across CT 10 where the pharmacist's name is.

https://www.google.com/maps/@41.5987352,-72.8780281,19z
Title: Re: Google Maps just fucking SUCKS now
Post by: JJBers on September 01, 2017, 12:50:10 AM
Quote from: jp the roadgeek on August 31, 2017, 09:08:30 PM
Quote from: JJBers on August 31, 2017, 06:24:15 PM
Quote from: jp the roadgeek on August 31, 2017, 04:41:41 PM
Quote from: SignGeek101 on August 31, 2017, 10:29:35 AM
Well, it appears I can't change anything or get anything changed when it comes to errors. A week since I reported three errors to Google, and no response.

Also, how am I supposed to change information such as road type (arterial, freeway etc)? I feel like the options presented now are really primitive.

I reported several errors months ago, and nothing has changed.  CT 31 is still a county route north of US 44, someone put a restaurant on a corner where a library is (and misspelled the name of it and put it 4 miles from its correct location) and a Rite Aid is on the wrong side of the street.
I can fix those last two things, just send the links to the places.

First one at the corner of CT 10 and CT 120.  The correct location is already accounted for, so it needs to be deleted.

https://www.google.com/maps/@41.5964205,-72.8778859,19z


Second one:  Rite Aid.  Location info correct, but location on map incorrect.  Needs to be the building across CT 10 where the pharmacist's name is.

https://www.google.com/maps/@41.5987352,-72.8780281,19z
Alright, and done, it may take a while to fix it on every server....
Also, funny, I've been to the library before.
Also if you look closly, you can see there's two Rite-Aid markers, but that should be fixed.
Title: Re: Google Maps just fucking SUCKS now
Post by: Great Lakes Roads on September 18, 2017, 07:31:44 PM
Um... no comment...  :pan: :pan: :pan:

https://www.google.com/maps/@36.2892003,-115.1005193,14.51z
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 18, 2017, 08:41:57 PM
Quote from: Great Lakes Roads on September 18, 2017, 07:31:44 PM
Um... no comment...

https://www.google.com/maps/@36.2892003,-115.1005193,14.51z

Looking past the mistake for a moment, those interchanges are ridiculously close to one another.
Title: Re: Google Maps just fucking SUCKS now
Post by: JJBers on September 18, 2017, 09:18:21 PM
Quote from: jakeroot on September 18, 2017, 08:41:57 PM
Quote from: Great Lakes Roads on September 18, 2017, 07:31:44 PM
Um... no comment...

https://www.google.com/maps/@36.2892003,-115.1005193,14.51z

Looking past the mistake for a moment, those interchanges are ridiculously close to one another.
Even better, the imagery shows that the highway isn't even built in the center.
Also two Targets and Walmarts 3 miles apart...jesus,
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on October 07, 2017, 04:34:42 PM
I'm not happy with recent improvements to their Android app. Here's a screenshot with two of my complaints:

(https://i.imgur.com/71DHpOj.png)

1) I hate the part on the left. It pops up constantly and I never use it!
2) The compass in the top right has been replaced with an icon that lets you switch map types. So how do I get my map to show true north again? (other than closing the app and reopening it)
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on October 07, 2017, 05:15:23 PM
Quote from: 7/8 on October 07, 2017, 04:34:42 PM
I'm not happy with recent improvements to their Android app. Here's a screenshot with two of my complaints:

(https://i.imgur.com/71DHpOj.png)

1) I hate the part on the left. It pops up constantly and I never use it!
2) The compass in the top right has been replaced with an icon that lets you switch map types. So how do I get my map to show true north again? (other than closing the app and reopening it)

I never use the sidebar on the left either, and what's worse is that I don't even think there's a way to avoid showing it.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on October 07, 2017, 05:18:03 PM
Quote from: 20160805 on October 07, 2017, 05:15:23 PM
Quote from: 7/8 on October 07, 2017, 04:34:42 PM
I'm not happy with recent improvements to their Android app. Here's a screenshot with two of my complaints:

(https://i.imgur.com/71DHpOj.png)

1) I hate the part on the left. It pops up constantly and I never use it!
2) The compass in the top right has been replaced with an icon that lets you switch map types. So how do I get my map to show true north again? (other than closing the app and reopening it)

I never use the sidebar on the left either, and what's worse is that I don't even think there's a way to avoid showing it.

You can press the left-pointing arrow, but it comes back everytime I re-enter the app, or leave street view :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 07, 2017, 09:27:26 PM
Seriously, how clueless can Google be?  Have they ever even USED their Android app before?  If they did, they'd realize that it is TRIVIALLY easy to accidentally change the direction it faces when trying to zoom and that the compass was essential.
Title: Re: Google Maps just fucking SUCKS now
Post by: Alex4897 on October 07, 2017, 09:35:32 PM
Quote from: 7/8 on October 07, 2017, 04:34:42 PM
2) The compass in the top right has been replaced with an icon that lets you switch map types. So how do I get my map to show true north again? (other than closing the app and reopening it)

My Android app is behaving just fine, the compass appears beneath the new layers button whenever I rotate away from true north.

(https://image.prntscr.com/image/ukB2XAbBSKeXZ65gGvAD6Q.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 08, 2017, 03:50:33 AM
^^
My compass also shows up just fine. I think you're experiencing a bug, 7/8.

Quote from: vdeane on October 07, 2017, 09:27:26 PM
Seriously, how clueless can Google be?  Have they ever even USED their Android app before?  If they did, they'd realize that it is TRIVIALLY easy to accidentally change the direction it faces when trying to zoom and that the compass was essential.

Is this comment based on your experience with the app, or 7/8's post?
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on October 08, 2017, 10:44:21 AM
I'm using a Samsung Galaxy S2 tablet. Maybe the mobile version is different?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 08, 2017, 06:45:43 PM
Quote from: 7/8 on October 08, 2017, 10:44:21 AM
I'm using a Samsung Galaxy S2 tablet. Maybe the mobile version is different?

I will need to test it on my Tab S3. The mobile version shares a substantial amount of code with the tablet version, so it surprises me that a bug may exist on the tablet that doesn't exist on the phone. But there is some variation in code, so the possibility is still there. I'll let you know.
Title: Re: Google Maps just fucking SUCKS now
Post by: US71 on October 08, 2017, 07:49:38 PM
Quote from: jakeroot on October 08, 2017, 06:45:43 PM
Quote from: 7/8 on October 08, 2017, 10:44:21 AM
I'm using a Samsung Galaxy S2 tablet. Maybe the mobile version is different?

I will need to test it on my Tab S3. The mobile version shares a substantial amount of code with the tablet version, so it surprises me that a bug may exist on the tablet that doesn't exist on the phone. But there is some variation in code, so the possibility is still there. I'll let you know.

I had to fix a error on Google today. It showed a campground 5 miles west of where it should be. I reported it, corrected it, and am waiting to see if they corrections holds.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on October 09, 2017, 06:53:05 AM
Quote from: Great Lakes Roads on September 18, 2017, 07:31:44 PM
Um... no comment...  :pan: :pan: :pan:

https://www.google.com/maps/@36.2892003,-115.1005193,14.51z

That's retarded!  Those are at-grade intersections with traffic lights, not interchanges!  I will say, odd road design, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on October 09, 2017, 08:09:41 AM
How many years and fixes do I have to put in to get CT 31 north of US 44 labeled as a state route rather than a county route? For the millionth time: THERE ARE NO COUNTY ROUTES IN CONNECTICUT!!
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on October 09, 2017, 08:28:28 AM
Quote from: 20160805 on October 09, 2017, 06:53:05 AM
Quote from: Great Lakes Roads on September 18, 2017, 07:31:44 PM
Um... no comment...  :pan: :pan: :pan:

https://www.google.com/maps/@36.2892003,-115.1005193,14.51z

That's retarded!  Those are at-grade intersections with traffic lights, not interchanges!  I will say, odd road design, though.

You can't comprehend that this will eventually be a highway someday, and they simply didn't build the bridges at this time?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 09, 2017, 02:38:06 PM
Quote from: jeffandnicole on October 09, 2017, 08:28:28 AM
Quote from: 20160805 on October 09, 2017, 06:53:05 AM
Quote from: Great Lakes Roads on September 18, 2017, 07:31:44 PM
Um... no comment...

https://www.google.com/maps/@36.2892003,-115.1005193,14.51z

That's retarded!  Those are at-grade intersections with traffic lights, not interchanges!  I will say, odd road design, though.

You can't comprehend that this will eventually be a highway someday, and they simply didn't build the bridges at this time?

I think he's saying that the bridges being shown on Google Maps, even though they aren't there in real life, is retarded. I assume the "odd road design" comment is in reference to the closely-spaced interchanges. Apparently, Clark County hasn't heard of other types of interchanges. Just diamonds and SPUIs.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 12, 2017, 09:56:24 AM
Quote from: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf

I don't think Google takes their own satellite imagery. Around here, I'm lucky to see new imagery once a year. Areas south of me haven't had new imagery since 2014.
Title: Re: Google Maps just fucking SUCKS now
Post by: inkyatari on October 12, 2017, 11:03:50 AM
Honestly, when it comes to satellite imagery anymore, I find Earth Explorer better.

https://earthexplorer.usgs.gov/
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on October 12, 2017, 05:47:52 PM
Quote from: jakeroot on October 12, 2017, 09:56:24 AM
Quote from: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf

I don't think Google takes their own satellite imagery. Around here, I'm lucky to see new imagery once a year. Areas south of me haven't had new imagery since 2014.

Google Earth (the standalone program, anyway, not sure about the new in-browser version) gets imagery updates far more often. Tacoma, WA, for example, has imagery from May of this year in GE.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on October 12, 2017, 07:11:25 PM
Look how they have I-11 signed. Just barely as its only got a small part anyway. At least they got this one right.  At first I though I was officially signed up to I-215, but that is up for debate right now.  So it does not suck here as I thought, but I thought we could give them credit anyway for some thing. :)
https://www.google.com/maps/@35.9747872,-114.9526115,12z
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on October 12, 2017, 07:42:04 PM
Today looking at google streetview seems to give my browser a whole lot of trouble.  It blacks out for a second, then shows the streetview again, then blacks out some more, then shows the streetview again.  All without even moving the mouse.  I closed the tab before it crashed the whole browser.  Viva KMLmap.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on October 12, 2017, 08:37:36 PM
Quote from: kkt on October 12, 2017, 07:42:04 PM
Today looking at google streetview seems to give my browser a whole lot of trouble.  It blacks out for a second, then shows the streetview again, then blacks out some more, then shows the streetview again.  All without even moving the mouse.  I closed the tab before it crashed the whole browser.  Viva KMLmap.

I keep having blackouts as well on the Maps app on my android. However, when I use the Chrome browser on my android to access Google Maps from Google's website, the blackouts are gone. It's a temporary fix that works for me, but using a desktop-style Google Maps on an android is a bitch and a half. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on October 12, 2017, 10:10:32 PM
Quote from: inkyatari on October 12, 2017, 11:03:50 AM
Honestly, when it comes to satellite imagery anymore, I find Earth Explorer better.

https://earthexplorer.usgs.gov/

Well, it's a shame that USGS has retired its hi-res imagery program, then. :-(
Title: Re: Google Maps just fucking SUCKS now
Post by: Aerobird on October 14, 2017, 01:44:31 AM
Quote from: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf

They are. The new road configuration that opened near here in the spring has already been updated twice since construction started last fall.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2017, 12:10:02 AM
Quote from: MNHighwayMan on October 12, 2017, 05:47:52 PM
Quote from: jakeroot on October 12, 2017, 09:56:24 AM
Quote from: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf

I don't think Google takes their own satellite imagery. Around here, I'm lucky to see new imagery once a year. Areas south of me haven't had new imagery since 2014.

Google Earth (the standalone program, anyway, not sure about the new in-browser version) gets imagery updates far more often. Tacoma, WA, for example, has imagery from May of this year in GE.

I've noticed this as well. Google Maps satellite view now has the 2017 imagery that previously only Google Earth had. But when that imagery comes out, Earth always gets it first. So soon after, clicking the "Historical Imagery" button won't show the newest imagery as an option on the slider (exiting historical view being the only way to return to the new imagery).
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on October 16, 2017, 04:16:44 AM
Quote from: Aerobird on October 14, 2017, 01:44:31 AM
Quote from: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf

They are. The new road configuration that opened near here in the spring has already been updated twice since construction started last fall.
Not in Oklahoma. Haven't updated OKC in a year now. Used to be twice or more a year. Same thing with Las Vegas, Reno, Milwaukee, Jacksonville, and Wichita.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on October 16, 2017, 04:17:54 AM
Quote from: jakeroot on October 16, 2017, 12:10:02 AM
Quote from: MNHighwayMan on October 12, 2017, 05:47:52 PM
Quote from: jakeroot on October 12, 2017, 09:56:24 AM
Quote from: Plutonic Panda on October 12, 2017, 03:00:21 AM
I think I said this earlier, but it looks like Google just isn't updating their shit either as far as imagery goes. Many project I used to look at which would updated a couple times a year have gone almost a year now and in some cases I think even more without imagery updates. Wtf

I don't think Google takes their own satellite imagery. Around here, I'm lucky to see new imagery once a year. Areas south of me haven't had new imagery since 2014.

Google Earth (the standalone program, anyway, not sure about the new in-browser version) gets imagery updates far more often. Tacoma, WA, for example, has imagery from May of this year in GE.

I've noticed this as well. Google Maps satellite view now has the 2017 imagery that previously only Google Earth had. But when that imagery comes out, Earth always gets it first. So soon after, clicking the "Historical Imagery" button won't show the newest imagery as an option on the slider (exiting historical view being the only way to return to the new imagery).
Thanks for confirming. I'll download Earth App for iOS.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2017, 04:37:50 PM
Quote from: Plutonic Panda on October 16, 2017, 04:17:54 AM
Quote from: jakeroot on October 16, 2017, 12:10:02 AM
Quote from: MNHighwayMan on October 12, 2017, 05:47:52 PM
Google Earth (the standalone program, anyway, not sure about the new in-browser version) gets imagery updates far more often. Tacoma, WA, for example, has imagery from May of this year in GE.

I've noticed this as well. Google Maps satellite view now has the 2017 imagery that previously only Google Earth had. But when that imagery comes out, Earth always gets it first. So soon after, clicking the "Historical Imagery" button won't show the newest imagery as an option on the slider (exiting historical view being the only way to return to the new imagery).

Thanks for confirming. I'll download Earth App for iOS.

As long as the Earth app has a way to disable 3D imagery (which I'm not sure it does). My area is covered with 3D imagery, so without a layer toggle that allows me to disable that overlay, I have to use the actual Google Maps app to view satellite imagery (which usually updates not long after Earth).
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on October 16, 2017, 05:42:50 PM
If only I could change my vote to "Not quite terrible, but still worse" instead of "I am indifferent"...

Google Maps in mid 2016 when I joined here was tolerable, but now it's becoming increasingly pathetic and unusable.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2017, 06:04:34 PM
An issue mentioned up-thread about Street View automatically throwing you into 3D imagery mode has been fixed. You can only enter Street View via the scroll-wheel when in 3D mode, and you may only exit Street View using the scroll-wheel if you were previously viewing 3D imagery.

An issue that I've been having lately is 3D imagery that doesn't completely render. I'll click over to satellite imagery, the 3D imagery will briefly render (just enough to get an idea of where land and water are), but it stops loading just after. I can exit 3D mode, but it gets really laggy. A window refresh fixes the problem.

Quote from: 20160805 on October 16, 2017, 05:42:50 PM
If only I could change my vote to "Not quite terrible, but still worse" instead of "I am indifferent"...

Google Maps in mid 2016 when I joined here was tolerable, but now it's becoming increasingly pathetic and unusable.

At least on my end, things have been improving. There's still the odd bug or graphical error (and there probably always will be), but it's far from "unusable" or "pathetic".
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on October 16, 2017, 08:41:43 PM
Quote from: jakeroot on October 16, 2017, 04:37:50 PM
Quote from: Plutonic Panda on October 16, 2017, 04:17:54 AM
Thanks for confirming. I'll download Earth App for iOS.

As long as the Earth app has a way to disable 3D imagery (which I'm not sure it does). My area is covered with 3D imagery, so without a layer toggle that allows me to disable that overlay, I have to use the actual Google Maps app to view satellite imagery (which usually updates not long after Earth).

Dunno if the mobile apps do, but I can confirm the desktop program does.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2017, 09:07:47 PM
Quote from: MNHighwayMan on October 16, 2017, 08:41:43 PM
Quote from: jakeroot on October 16, 2017, 04:37:50 PM
Quote from: Plutonic Panda on October 16, 2017, 04:17:54 AM
Thanks for confirming. I'll download Earth App for iOS.

As long as the Earth app has a way to disable 3D imagery (which I'm not sure it does). My area is covered with 3D imagery, so without a layer toggle that allows me to disable that overlay, I have to use the actual Google Maps app to view satellite imagery (which usually updates not long after Earth).

Dunno if the mobile apps do, but I can confirm the desktop program does.

Desktop definitely does. It's a feature I use all the time. But Earth on mobile phones lacks many of the features of the desktop app, including such things as historical imagery.

After looking at my phone, I can confirm that only the desktop app allows users to disable the 3D imagery. On mobile, 3D imagery is the only viewable map type, at least in areas with 3D imagery. Outside of those areas, normal satellite view is used.
Title: Re: Google Maps just fucking SUCKS now
Post by: davewiecking on October 17, 2017, 12:03:19 AM
Quote from: jakeroot on October 16, 2017, 09:07:47 PM
Quote from: MNHighwayMan on October 16, 2017, 08:41:43 PM
Quote from: jakeroot on October 16, 2017, 04:37:50 PM
Quote from: Plutonic Panda on October 16, 2017, 04:17:54 AM
Thanks for confirming. I'll download Earth App for iOS.

As long as the Earth app has a way to disable 3D imagery (which I'm not sure it does). My area is covered with 3D imagery, so without a layer toggle that allows me to disable that overlay, I have to use the actual Google Maps app to view satellite imagery (which usually updates not long after Earth).

Dunno if the mobile apps do, but I can confirm the desktop program does.

Desktop definitely does. It's a feature I use all the time. But Earth on mobile phones lacks many of the features of the desktop app, including such things as historical imagery.

After looking at my phone, I can confirm that only the desktop app allows users to disable the 3D imagery. On mobile, 3D imagery is the only viewable map type, at least in areas with 3D imagery. Outside of those areas, normal satellite view is used.
I don't know about on a phone, but on my iPad I just touch the little "3D" "button" at the lower left, and Google Earth switches to 2D mode (switching to a different angle, with an annoying, constantly, slowly rotating view). (The "3D" button is only visible if I've zoomed in a bit-it shows up if I've zoomed in to see half of the US, for example.) I've pretty much stopped using GE on the iPad in the past few months, and have switched to Google Maps if I want to research something.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 17, 2017, 12:16:31 AM
Quote from: davewiecking on October 17, 2017, 12:03:19 AM
Quote from: jakeroot on October 16, 2017, 09:07:47 PM
Quote from: MNHighwayMan on October 16, 2017, 08:41:43 PM
Quote from: jakeroot on October 16, 2017, 04:37:50 PM
Quote from: Plutonic Panda on October 16, 2017, 04:17:54 AM
Thanks for confirming. I'll download Earth App for iOS.

As long as the Earth app has a way to disable 3D imagery (which I'm not sure it does). My area is covered with 3D imagery, so without a layer toggle that allows me to disable that overlay, I have to use the actual Google Maps app to view satellite imagery (which usually updates not long after Earth).

Dunno if the mobile apps do, but I can confirm the desktop program does.

Desktop definitely does. It's a feature I use all the time. But Earth on mobile phones lacks many of the features of the desktop app, including such things as historical imagery.

After looking at my phone, I can confirm that only the desktop app allows users to disable the 3D imagery. On mobile, 3D imagery is the only viewable map type, at least in areas with 3D imagery. Outside of those areas, normal satellite view is used.

I don't know about on a phone, but on my iPad I just touch the little "3D" "button" at the lower left, and Google Earth switches to 2D mode (switching to a different angle, with an annoying, constantly, slowly rotating view). (The "3D" button is only visible if I've zoomed in a bit-it shows up if I've zoomed in to see half of the US, for example.) I've pretty much stopped using GE on the iPad in the past few months, and have switched to Google Maps if I want to research something.

I'm not even sure what the hell that button is supposed to do. You can click it, and it'll rotate the view as you mentioned. And it will get the camera pointing straight up again (if you've accidentally tilted the view). But that's about it. Certainly not what I wish it would do: disable 3D imagery.

FWIW, I think the Earth app and the Maps app (both from Google) receive the same satellite imagery data (only Earth on the desktop gets it first). If that is indeed the case, you're better off using the Google Maps app if you don't want to bother with 3D imagery (not a feature on Google Maps for Android/iOS, so Earth isn't completely redundant).
Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on October 17, 2017, 01:16:55 AM
I've been sleeping on Stafford apparently. Where in town is that beach?

(https://i.imgur.com/VAiyQt8.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on October 17, 2017, 03:58:46 AM
Quote from: kurumi on October 17, 2017, 01:16:55 AM
I've been sleeping on Stafford apparently. Where in town is that beach?

(https://i.imgur.com/VAiyQt8.jpg)
Reminds me of how Huntsville, AL used a picture of Chattanooga, TN for a while on Google Maps. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on October 17, 2017, 09:43:21 AM
My town at least uses a golf course.  However, the golf course they use looks a lot more lavish than the 2 1/2 we have.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 17, 2017, 11:06:29 PM
My home town of Puyallup, WA uses a photo of a lake nowhere near the city:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FLUxKsda.jpg&hash=4decf45ae944cdbba0ff1a4c84c53469e58c83f6)

I think this problem is more common than previously thought.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on October 26, 2017, 04:09:02 PM
Another oddity, for some stupid reason, Google prevents me from turning left across an area where the center line striping spreads out.

https://goo.gl/maps/AcbgNFns1qz

I use Google Maps to turn into and out of there, and it gives me some convoluted route to avoid turning left into or out of that street.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 26, 2017, 04:12:21 PM
Quote from: Brandon on October 26, 2017, 04:09:02 PM
Another oddity, for some stupid reason, Google prevents me from turning left across an area where the center line striping spreads out.

https://goo.gl/maps/AcbgNFns1qz

I use Google Maps to turn into and out of there, and it gives me some convoluted route to avoid turning left into or out of that street.

That's pretty common.  If you remove satellite and just go to the normal map view, you can see that it's considered a divided highway there, with two separate roadways.  Maybe it's not clear because the yellow lines rub shoulders, but Google doesn't realize there's pavement between the two.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 26, 2017, 05:26:14 PM
Quote from: Brandon on October 26, 2017, 04:09:02 PM
Another oddity, for some stupid reason, Google prevents me from turning left across an area where the center line striping spreads out.

https://goo.gl/maps/AcbgNFns1qz

I use Google Maps to turn into and out of there, and it gives me some convoluted route to avoid turning left into or out of that street.

Might be the result of how Google interprets street markings. In California, two sets of double yellow lines equal a hard median, which you aren't allowed to cross.

The maneuver you describe would not be legal in CA. That said, if the maneuver is legal in Illinois (which I suspect it is), Google ought to connect Bonnie Ln to both "carriageways" of Bridge St. Illinois is obviously not California, so you shouldn't be treated as though you are in California.

If you can confirm for me the legality of the maneuver, I will let Google know of the problem. Most of my changes are made within a few minutes. Not sure if I'm just lucky, or I make so many changes, they trust me now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on October 26, 2017, 06:11:37 PM
Quote from: jakeroot on October 26, 2017, 05:26:14 PM
Quote from: Brandon on October 26, 2017, 04:09:02 PM
Another oddity, for some stupid reason, Google prevents me from turning left across an area where the center line striping spreads out.

https://goo.gl/maps/AcbgNFns1qz

I use Google Maps to turn into and out of there, and it gives me some convoluted route to avoid turning left into or out of that street.

Might be the result of how Google interprets street markings. In California, two sets of double yellow lines equal a hard median, which you aren't allowed to cross.

The maneuver you describe would not be legal in CA. That said, if the maneuver is legal in Illinois (which I suspect it is), Google ought to connect Bonnie Ln to both "carriageways" of Bridge St. Illinois is obviously not California, so you shouldn't be treated as though you are in California.

If you can confirm for me the legality of the maneuver, I will let Google know of the problem. Most of my changes are made within a few minutes. Not sure if I'm just lucky, or I make so many changes, they trust me now.

Oh, it's very legal in Illinois to turn left across this type of striped area.  Street View of the area: https://goo.gl/maps/kboAcz8dkCF2 & https://goo.gl/maps/tbEqpRqrExr  There are no "no left turn" signs anywhere there.

Illinois Rules of the Road 2017: http://www.cyberdriveillinois.com/publications/pdf_publications/dsd_a112.pdf
Page 76 addresses striping.
625 ILCS: http://www.ilga.gov/legislation/ilcs/ilcs4.asp?DocName=062500050HCh%2E+11&ActID=1815&ChapterID=49&SeqStart=111500000&SeqEnd=136550000
http://www.ilga.gov/legislation/ilcs/ilcs3.asp?ChapterID=49&ActID=1815
Turning: http://www.ilga.gov/legislation/ilcs/ilcs4.asp?DocName=062500050HCh%2E+11+Art%2E+VIII&ActID=1815&ChapterID=49&SeqStart=122900000&SeqEnd=123600000
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on October 26, 2017, 08:26:08 PM
Quote from: kurumi on October 17, 2017, 01:16:55 AM
I've been sleeping on Stafford apparently. Where in town is that beach?

(https://i.imgur.com/VAiyQt8.jpg)

I could be wrong, but that picture looks an awful lot like a beach I've been to in Bermuda.
Title: Re: Google Maps just fucking SUCKS now
Post by: inkyatari on October 26, 2017, 08:45:30 PM
Quote from: Brandon on October 26, 2017, 04:09:02 PM
Another oddity, for some stupid reason, Google prevents me from turning left across an area where the center line striping spreads out.

https://goo.gl/maps/AcbgNFns1qz

I use Google Maps to turn into and out of there, and it gives me some convoluted route to avoid turning left into or out of that street.

I know the area.  I've turned across that many times.
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
What city is that? Chicago?
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on October 28, 2017, 06:41:19 AM
Quote from: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
What city is that? Chicago?

St. Louis, from the Arch.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on October 28, 2017, 09:25:33 PM
Quote from: Brandon on October 28, 2017, 06:41:19 AM
Quote from: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
What city is that? Chicago?

St. Louis, from the Arch.
Are there any similarities between the 2 cities that could cause confusion?
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on October 28, 2017, 11:06:06 PM
Quote from: Roadgeekteen on October 28, 2017, 09:25:33 PM
Quote from: Brandon on October 28, 2017, 06:41:19 AM
Quote from: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
What city is that? Chicago?

St. Louis, from the Arch.
Are there any similarities between the 2 cities that could cause confusion?

None, whatsoever.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on October 28, 2017, 11:48:23 PM
Quote from: Brandon on October 28, 2017, 11:06:06 PM
Quote from: Roadgeekteen on October 28, 2017, 09:25:33 PM
Quote from: Brandon on October 28, 2017, 06:41:19 AM
Quote from: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
What city is that? Chicago?

St. Louis, from the Arch.
Are there any similarities between the 2 cities that could cause confusion?

None, whatsoever.
What were the employees thinking? Google do this at 2 am?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.
does google do automated work on maps?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on October 29, 2017, 10:27:52 PM
Quote from: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.
Just proves that humans often work better than machines.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 29, 2017, 10:34:48 PM
Quote from: Roadgeekteen on October 29, 2017, 10:27:52 PM
Quote from: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.

Just proves that humans often work better than machines.

But there's not enough humans to do most of Google's dirty work, like web scraping.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 30, 2017, 02:36:58 PM
Quote from: Brandon on October 28, 2017, 06:41:19 AM
Quote from: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251
What city is that? Chicago?

St. Louis, from the Arch.

When I click on the link you provided, I get an image for the Jefferson Street Bridge.  ???

(https://i.imgur.com/K7CF84k.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 30, 2017, 04:32:58 PM
Quote from: kphoger on October 30, 2017, 02:36:58 PM
Quote from: Brandon on October 28, 2017, 06:41:19 AM
Quote from: Roadgeekteen on October 28, 2017, 12:10:50 AM
Quote from: paulthemapguy on October 27, 2017, 11:42:45 PM
OMG the photo for Joliet is DEFINITELY NOT Joliet hahahaha   :rofl:

https://www.google.com/maps/place/Joliet,+IL/@41.5795382,-88.1665708,11z/data=!4m13!1m7!3m6!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!2sJoliet,+IL!3b1!8m2!3d41.525031!4d-88.0817251!3m4!1s0x880e456bec363d7d:0x9f9e66f7a36bc042!8m2!3d41.525031!4d-88.0817251

What city is that? Chicago?

St. Louis, from the Arch.

When I click on the link you provided, I get an image for the Jefferson Street Bridge.  ???

https://i.imgur.com/K7CF84k.png

Interestingly, I do as well. But, I didn't two days ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on October 31, 2017, 09:57:16 AM
Quote from: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.

Could it be choosing the photo based on the location from which it was uploaded, rather than where it was taken? Perhaps someone from Stafford, CT took a photo of a beach while on vacation, then uploaded it to Google after returning home.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on October 31, 2017, 09:30:35 PM
New update to google maps makes it so that I've got to open and close this annoying sidebar just to search.

Oh well...
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 31, 2017, 10:10:27 PM
Quote from: empirestate on October 31, 2017, 09:57:16 AM
Quote from: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.

Could it be choosing the photo based on the location from which it was uploaded, rather than where it was taken? Perhaps someone from Stafford, CT took a photo of a beach while on vacation, then uploaded it to Google after returning home.

Very well could be. Or perhaps based on a tagging system, where people have tagged their upload location, rather than the location of the photo. I uploaded a picture of the Shard (tall building in London) on Instagram a few years back, but tagged it "Burger King" because that's where I was when I uploaded it. All of my subsequent tags were of the actual location. But, that Burger King permanently has a photo of the Shard attached to the location.  :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on November 01, 2017, 01:16:36 PM
Quote from: jakeroot on October 31, 2017, 10:10:27 PM
Quote from: empirestate on October 31, 2017, 09:57:16 AM
Quote from: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.

Could it be choosing the photo based on the location from which it was uploaded, rather than where it was taken? Perhaps someone from Stafford, CT took a photo of a beach while on vacation, then uploaded it to Google after returning home.

Very well could be. Or perhaps based on a tagging system, where people have tagged their upload location, rather than the location of the photo. I uploaded a picture of the Shard (tall building in London) on Instagram a few years back, but tagged it "Burger King" because that's where I was when I uploaded it. All of my subsequent tags were of the actual location. But, that Burger King permanently has a photo of the Shard attached to the location.  :-D

Then why are they all pictures of famous or beautiful things?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 01, 2017, 07:48:32 PM
Quote from: kphoger on November 01, 2017, 01:16:36 PM
Quote from: jakeroot on October 31, 2017, 10:10:27 PM
Quote from: empirestate on October 31, 2017, 09:57:16 AM
Quote from: jakeroot on October 29, 2017, 10:21:25 PM
Quote from: Roadgeekteen on October 29, 2017, 09:41:42 PM
Quote from: jakeroot on October 28, 2017, 11:51:31 PM
Quote from: Roadgeekteen on October 28, 2017, 11:48:23 PM
What were the employees thinking? Google do this at 2 am?

I don't think this involves employees. Likely a bug.

does google do automated work on maps?

The vast majority of Google Maps is automated, based on code. The images you see were not hand-picked by Google. The code selected the image based on various things, however, the code isn't working right, since many of the images aren't correct. I think any human would know that Stafford, CT doesn't have a tropical beach.

Could it be choosing the photo based on the location from which it was uploaded, rather than where it was taken? Perhaps someone from Stafford, CT took a photo of a beach while on vacation, then uploaded it to Google after returning home.

Very well could be. Or perhaps based on a tagging system, where people have tagged their upload location, rather than the location of the photo. I uploaded a picture of the Shard (tall building in London) on Instagram a few years back, but tagged it "Burger King" because that's where I was when I uploaded it. All of my subsequent tags were of the actual location. But, that Burger King permanently has a photo of the Shard attached to the location.

Then why are they all pictures of famous or beautiful things?

Good question. Perhaps Google has an algorithm to automatically detect photos that are good, versus ones that are shitty, but doesn't have enough data to determine if the good photos are geographically correct?
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

(https://media.discordapp.net/attachments/270725488958373888/381261859057041408/unknown.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 17, 2017, 09:32:36 PM
Quote from: 1 on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.

Also not me. Not every glitch is a feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 17, 2017, 09:55:54 PM
Quote from: jakeroot on November 17, 2017, 09:32:36 PM
Quote from: 1 on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.

Also not me. Not every glitch is a feature.

It's not a glitch.

https://www.blog.google/products/maps/google-maps-gets-new-look/

A quick google search will also show some articles relating to a new look for maps.

While improvements have been made, it, in my opinion, was not a smart choice to reduce road color coding to only yellow or white.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 17, 2017, 10:08:41 PM
Quote from: index on November 17, 2017, 09:55:54 PM
Quote from: jakeroot on November 17, 2017, 09:32:36 PM
Quote from: 1 on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.

Also not me. Not every glitch is a feature.

It's not a glitch.

https://www.blog.google/products/maps/google-maps-gets-new-look/

A quick google search will also show some articles relating to a new look for maps.

While improvements have been made, it, in my opinion, was not a smart choice to reduce road color coding to only yellow or white.

My bad. I see, too often on this thread, users complaining about a bug being some sort of new feature. It's kind of a knee-jerk response at this point.

I do agree, however. The new color scheme is a bit confusing. I'm not sure how many users use Google Maps to quickly find freeways, though. Most people seem to use Google Maps to find POIs, and then to help them get there. You don't need colors for navigation (Waze has a flat color scheme for comparison), you just need it for wayfinding. And this update makes it easier to do that, as long as you aren't trying to scope out the nearest freeway.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 17, 2017, 10:27:37 PM
Quote from: jakeroot on November 17, 2017, 10:08:41 PM
Quote from: index on November 17, 2017, 09:55:54 PM
Quote from: jakeroot on November 17, 2017, 09:32:36 PM
Quote from: 1 on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.

Also not me. Not every glitch is a feature.

It's not a glitch.

https://www.blog.google/products/maps/google-maps-gets-new-look/

A quick google search will also show some articles relating to a new look for maps.

While improvements have been made, it, in my opinion, was not a smart choice to reduce road color coding to only yellow or white.

My bad. I see, too often on this thread, users complaining about a bug being some sort of new feature. It's kind of a knee-jerk response at this point.

I do agree, however. The new color scheme is a bit confusing. I'm not sure how many users use Google Maps to quickly find freeways, though. Most people seem to use Google Maps to find POIs, and then to help them get there. You don't need colors for navigation (Waze has a flat color scheme for comparison), you just need it for wayfinding. And this update makes it easier to do that, as long as you aren't trying to scope out the nearest freeway.

I can agree with what you've said, I don't really think it matters to the traveler whether something's a freeway or expressway or arterial, but toll routes are a definite thing to consider when taking a route. Though, to be fair, Google maps does have an option to avoid tolls.  Perhaps these new road color schemes are just something that would bug people who are interested in roads?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 18, 2017, 02:19:59 AM
Quote from: index on November 17, 2017, 10:27:37 PM
Perhaps these new road color schemes are just something that would bug people who are interested in roads?

Almost certainly! Most of the changes to Google Maps, over the last few years, have not favored roadgeeks who simply use it to browse for fun. Ask any resident of the UK. The roads there used to be colored to match the route designation (blue, green, orange, white, etc). Now, all the colors match the rest of the world. This makes looking at maps confusing, especially since A-roads will sometimes be yellow, and sometimes white. Before, they were always green. Bing Maps still colors UK roads properly.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on November 18, 2017, 10:40:56 AM
1 year and 6 change requests, and CT 31 north of US 44 is still signed as a county route. of which there are none in CT.   I've had more luck with city hall and the DMV.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 18, 2017, 05:21:04 PM
I don't see anything in the article about road colors, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 18, 2017, 06:41:59 PM
Quote from: vdeane on November 18, 2017, 05:21:04 PM
I don't see anything in the article about road colors, though.

I thought I saw the changes in some of the preview images, but looking again, the Google Search and Google Assistant previews show the old colors. I thought I saw the new colors in the Google Maps preview, but I actually think it's showing the West Side Highway in Manhattan (notably not a freeway), which is already shown as a yellow today.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on November 18, 2017, 07:44:33 PM
Quote from: 1 on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.

I see it when I use Google Maps through the desktop version on Google's webpage, but not on my android app. I think the change sucks. If there's a way to fuck something up, Google will find it, come hell or high water.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on November 20, 2017, 08:24:01 PM
Quote from: index on November 17, 2017, 09:55:54 PM
Quote from: jakeroot on November 17, 2017, 09:32:36 PM
Quote from: 1 on November 17, 2017, 09:04:14 PM
Quote from: index on November 17, 2017, 09:01:15 PM
We've got another stupid update. The "improvement" in this one is that freeways, expressways, tolled routes, major arterials, and the like, are all the same color...

It's not happening to me.

Also not me. Not every glitch is a feature.

It's not a glitch.

https://www.blog.google/products/maps/google-maps-gets-new-look/

A quick google search will also show some articles relating to a new look for maps.

While improvements have been made, it, in my opinion, was not a smart choice to reduce road color coding to only yellow or white.

It looks like they may have rolled this back. I saw the change a couple days ago, but today it seems to be back to how it was last week. Maybe they realized they needed to make some adjustments.
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on November 20, 2017, 08:52:01 PM
Interesting...

To me it looks like it depends on what browser you are using.  On my main desktop Mac running OS X 10.12 (Sierra) using Safari, Google Maps appears like the example Index posted where arterials and freeways are the same color.  However, if I switch to Google Chrome, the colors of each type of roadway are different.

To make thing even more bizarre, on my MacBook Pro running OS X 10.11 (El Capitan) using Safari, freeways and arterials are colored differently.

So to summarize...
MacOS X 10.12 w/Safari v10 -- Arterials/Freeways Same Color
MacOS X 10.12 w/Chrome v62 -- Arterials/Freeways Different Color
MacOS X 10.11 w/Safari v9 -- Arterials/Freeways Different Color
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on November 20, 2017, 10:46:17 PM
Quote from: myosh_tino on November 20, 2017, 08:52:01 PM
So to summarize...
MacOS X 10.12 w/Safari v10 -- Arterials/Freeways Same Color
MacOS X 10.12 w/Chrome v62 -- Arterials/Freeways Different Color
MacOS X 10.11 w/Safari v9 -- Arterials/Freeways Different Color

My own observations:
MacOS 10.13 (High Sierra) w/ Chrome (61? I updated today, so may have been 61), November 18 – Arterials/Freeways Same Color
MacOS 10.13 w/ Chrome 62, November 20 – Arterials/Freeways Different Color
MacOS 10.13 w/ Safari 11, November 20 – Arterials/Freeways Different Color
Android 7.1.1 w/ Google Maps app v9.66.1, November 20 – Arterials/Freeways Different Color
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 20, 2017, 10:55:10 PM
On Windows 10....something, I can't get "the look" to show up on any browser. Chrome, Firefox, Edge, IE -- nothing.
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on November 21, 2017, 01:45:06 AM
Just did a quick check on my Windows 7 machine...

Windows 7 w/Firefox v55 -- Arterials/Freeways Different Color

Quote from: jakeroot on November 20, 2017, 10:55:10 PM
On Windows 10....something, I can't get "the look" to show up on any browser. Chrome, Firefox, Edge, IE -- nothing.

Windows 10 is banned from my computers  :)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 21, 2017, 02:19:36 AM
Quote from: myosh_tino on November 21, 2017, 01:45:06 AM
Quote from: jakeroot on November 20, 2017, 10:55:10 PM
On Windows 10....something, I can't get "the look" to show up on any browser. Chrome, Firefox, Edge, IE -- nothing.

Windows 10 is banned from my computers  :)

Windows 10 is by far the best OS Microsoft has ever made. They like to shove updates down the throats of users, but it's mostly for the greater good. Not like Apple doesn't do the same thing.

You could have also been making a "Windows sucks in general" joke. In which case, that's fine. But it's lost on gamers like me. You just can't game on a Mac.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on November 21, 2017, 06:40:53 AM
Quote from: jakeroot on November 21, 2017, 02:19:36 AM
You could have also been making a "Windows sucks in general" joke. In which case, that's fine. But it's lost on gamers like me. You just can't game on a Mac.

That's why I have Win10 too. It also helps that I have never had to purchase Windows myself. My first computer was a gift, and for the computer I built for myself in 2010 (and am still using albeit with upgrades), I got a license for Windows 7 for free from my university (which I later used to get the free 10 upgrade).
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on November 21, 2017, 07:17:51 AM
I just upgraded to Windows 7 from XP this past January.  I like being a little behind the times  ;-)
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 21, 2017, 09:49:22 AM
Quote from: 20160805 on November 21, 2017, 07:17:51 AM
I just upgraded to Windows 7 from XP this past January.  I like being a little behind the times  ;-)

As do I. I intend on staying on Windows 7 as long as it does what I need it to do and is supported by the programs, drivers, and hardware I use.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 21, 2017, 09:55:23 AM
Quote from: myosh_tino on November 20, 2017, 08:52:01 PM
Interesting...

To me it looks like it depends on what browser you are using.  On my main desktop Mac running OS X 10.12 (Sierra) using Safari, Google Maps appears like the example Index posted where arterials and freeways are the same color.  However, if I switch to Google Chrome, the colors of each type of roadway are different.

To make thing even more bizarre, on my MacBook Pro running OS X 10.11 (El Capitan) using Safari, freeways and arterials are colored differently.

So to summarize...
MacOS X 10.12 w/Safari v10 -- Arterials/Freeways Same Color
MacOS X 10.12 w/Chrome v62 -- Arterials/Freeways Different Color
MacOS X 10.11 w/Safari v9 -- Arterials/Freeways Different Color

Quote from: jakeroot on November 20, 2017, 10:55:10 PM
On Windows 10....something, I can't get "the look" to show up on any browser. Chrome, Firefox, Edge, IE -- nothing.

On the topic of this, I believe it's because Google is rolling out the new update in waves. Not all browsers/people/etc will get it at the same time. It showed up for one of my friends (who uses Chrome) the day after Google announced it, and showed up for another person I know a few days after it was announced. (they use Firefox) As for me, I still haven't got it yet. I'm a Chrome user.
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on November 21, 2017, 10:12:24 AM
it looks terrible, they just cant stop fucking with it.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on November 21, 2017, 10:54:02 AM
Quote from: myosh_tino on November 21, 2017, 01:45:06 AMWindows 7 w/Firefox v55 -- Arterials/Freeways Different Color

Also true here for same OS, Firefox version 48.

Not to drag this thread too far OT, but I have no plans to upgrade from Windows 7 on the current primary computer (purchased 2011, not going to be replaced until 2019 at earliest) and still run XP on a laptop (purchased 2006) that is now used primarily to operate a four-in-one multifunction printer as a document scanner.  In spite of repeated assurances from people working in IT support who maintain that Windows 10 is just fine on the majority of computers that meet its hardware specs, in this household we have noticed its implementation of SMB is rough-edged.  The family member who uses an Android tablet to look at PDF documents held on his laptop HD has had problems with Windows 10 suddenly refusing to serve directory listings or files over the SMB connection.  This is a well-known issue with Windows 10 and there are varying recipes for fixing it, each of which works for one subset of users and not for others.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on November 21, 2017, 11:56:09 AM
Quote from: silverback1065 on November 21, 2017, 10:12:24 AM
it looks terrible, they just cant stop fucking with it.

That's the problem with programmers.  It's perfect, so let's make it "better"!  More like, better, my ass.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 22, 2017, 01:10:02 AM
Quote from: MNHighwayMan on November 21, 2017, 06:40:53 AM
Quote from: jakeroot on November 21, 2017, 02:19:36 AM
You could have also been making a "Windows sucks in general" joke. In which case, that's fine. But it's lost on gamers like me. You just can't game on a Mac.

That's why I have Win10 too. It also helps that I have never had to purchase Windows myself. My first computer was a gift, and for the computer I built for myself in 2010 (and am still using albeit with upgrades), I got a license for Windows 7 for free from my university (which I later used to get the free 10 upgrade).

I'm mostly in the same boat. My current computer shipped with Windows 8, which I also upgraded to 10 for free (as did most people I know who were using Windows 8).

I've had computers in the past (all gifts because I was young) that ran XP Media Center Edition, and Vista, but I never upgraded either. XP to Vista was the big no-no, for many reasons. And although I would have been happy to upgrade Vista to Windows 7, the computer that ran it was also only used for very basic things. I was using our desktop iMac more at that point, so I just didn't care. I've had two computers that shipped with Windows 7, which I upgraded to 8. But because I replaced both with a new Windows 8 machine before Windows 10 was released, both were relegated to my storage drawer (both laptops). So, both continue to run Windows 8.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 22, 2017, 01:12:24 AM
Quote from: Brandon on November 21, 2017, 11:56:09 AM
Quote from: silverback1065 on November 21, 2017, 10:12:24 AM
it looks terrible, they just cant stop fucking with it.

That's the problem with programmers.  It's perfect, so let's make it "better"!  More like, better, my ass.

I'm sure programmers would rather have quite a few different colors. They are a lot like us: ordered, easily frustrated, etc. The reason Google changes stuff like this is because user feedback suggests it. My guess is, user feedback has increasingly said, "freeways are too bright", or "make things easier to find". They're focusing less on driving with this update, and more on things you can find while on foot.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on November 22, 2017, 08:58:08 AM
All this 3D imagery just creates very slow loading times on the PC. As someone who's used Google Maps extensively for the past dozen years or so, it's infuriating. I used to enjoy scanning the imagery, and checking out places on Street View, but it's no longer much fun, unless I have to do it (usually for work).

It's faster on a tablet and my phone, probably because it doesn't try to render every last tree, streetlamp, and mailbox in needlessly 3D.

Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on November 22, 2017, 09:35:01 AM
A few days ago, I had the color change with private browsing on Safari. When I checked a few minutes ago, it changed back to what it used to be. (I use private browsing so that it doesn't clog my history.)
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on November 22, 2017, 12:39:22 PM
Quote from: 1 on November 22, 2017, 09:35:01 AM
(I use private browsing so that it doesn't clog my history.)

Riiighhhhht... ;-)
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on November 22, 2017, 01:22:02 PM
Quote from: empirestate on November 22, 2017, 12:39:22 PM
Quote from: 1 on November 22, 2017, 09:35:01 AM
(I use private browsing so that it doesn't clog my history.)

Riiighhhhht... ;-)

Using private browsing on Google Maps is a bit of a waste, isn't it? ;-)
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on November 22, 2017, 01:28:26 PM
Quote from: MNHighwayMan on November 22, 2017, 01:22:02 PM
Quote from: empirestate on November 22, 2017, 12:39:22 PM
Quote from: 1 on November 22, 2017, 09:35:01 AM
(I use private browsing so that it doesn't clog my history.)

Riiighhhhht... ;-)

Using private browsing on Google Maps is a bit of a waste, isn't it? ;-)

In Firefox (and probably every other browser), anytime you move the map it logs a history point. Looking at the map for a few minutes can mark hundreds of points in your history log. I can see the logic in private browsing to de-clutter that.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on November 22, 2017, 01:41:32 PM
Quote from: SectorZ on November 22, 2017, 01:28:26 PM
Quote from: MNHighwayMan on November 22, 2017, 01:22:02 PM
Quote from: empirestate on November 22, 2017, 12:39:22 PM
Quote from: 1 on November 22, 2017, 09:35:01 AM
(I use private browsing so that it doesn't clog my history.)

Riiighhhhht... ;-)

Using private browsing on Google Maps is a bit of a waste, isn't it? ;-)

In Firefox (and probably every other browser), anytime you move the map it logs a history point. Looking at the map for a few minutes can mark hundreds of points in your history log. I can see the logic in private browsing to de-clutter that.

Yes.  This seems obvious to me.  I wish Google Maps didn't set history points every time you move, and private browsing is a reasonable response to that.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 22, 2017, 06:44:45 PM
Quote from: formulanone on November 22, 2017, 08:58:08 AM
All this 3D imagery just creates very slow loading times on the PC. As someone who's used Google Maps extensively for the past dozen years or so, it's infuriating. I used to enjoy scanning the imagery, and checking out places on Street View, but it's no longer much fun, unless I have to do it (usually for work).

You can disable 3D imagery, you know. When you switch to satellite view, the menu says '3D on', but you can click that and change it to '3D off'.

I personally like the 3D imagery, because it can be a lot clearer than satellite imagery. And you can get a different perspective just by panning around while holding ctrl or cmd. Still though, the imagery can be older than satellite view, so I don't always use it.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on November 22, 2017, 07:01:45 PM
Quote from: jakeroot on November 22, 2017, 06:44:45 PM
Quote from: formulanone on November 22, 2017, 08:58:08 AM
All this 3D imagery just creates very slow loading times on the PC. As someone who's used Google Maps extensively for the past dozen years or so, it's infuriating. I used to enjoy scanning the imagery, and checking out places on Street View, but it's no longer much fun, unless I have to do it (usually for work).

You can disable 3D imagery, you know. When you switch to satellite view, the menu says '3D on', but you can click that and change it to '3D off'.

I personally like the 3D imagery, because it can be a lot clearer than satellite imagery. And you can get a different perspective just by panning around while holding ctrl or cmd. Still though, the imagery can be older than satellite view, so I don't always use it.

Switching it off every time is silly when you're using Chrome and have a Google account, and the 3D view usually looks muddy and inconsistent.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 22, 2017, 08:32:04 PM
Quote from: formulanone on November 22, 2017, 07:01:45 PM
Quote from: jakeroot on November 22, 2017, 06:44:45 PM
Quote from: formulanone on November 22, 2017, 08:58:08 AM
All this 3D imagery just creates very slow loading times on the PC. As someone who's used Google Maps extensively for the past dozen years or so, it's infuriating. I used to enjoy scanning the imagery, and checking out places on Street View, but it's no longer much fun, unless I have to do it (usually for work).

You can disable 3D imagery, you know. When you switch to satellite view, the menu says '3D on', but you can click that and change it to '3D off'.

I personally like the 3D imagery, because it can be a lot clearer than satellite imagery. And you can get a different perspective just by panning around while holding ctrl or cmd. Still though, the imagery can be older than satellite view, so I don't always use it.

Switching it off every time is silly when you're using Chrome and have a Google account, and the 3D view usually looks muddy and inconsistent.

Google could theoretically implement the ability to disable 3D imagery, but I'm guessing they won't. The 3D imagery can take a little longer to load, but unlike a lot of other GMaps gripes that roadgeeks have, 3D imagery is not something that we're 100% against. And I think most of the public finds the 3D imagery useful. So, I hate to say it, but you're probably in the 1% here.

As for the imagery itself, I guess we'll have to agree to disagree. I've always found the 3D imagery to be extremely consistent from metro area to metro area, and the fact that it (for the most part) doesn't show cars can make it easier to decipher things like pavement markings. The imagery is usually very clean and smooth. Satellite shots are very good, of course. But sometimes they can be a little blurry. And they're usually of a lower resolution. The 3D imagery was taken from a much closer distance, so you can zoom in, and maintain clarity, to a much greater degree than with normal satellite mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 22, 2017, 08:34:28 PM
Quote from: empirestate on November 22, 2017, 12:39:22 PM
Quote from: 1 on November 22, 2017, 09:35:01 AM
(I use private browsing so that it doesn't clog my history.)

Riiighhhhht... ;-)

I must be the only person who browses pornography in the normal browser window. I appreciate the normal browser's ability to keep me logged in. And if I forget to favorite a video, I can usually go back and find it in my history.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on November 22, 2017, 09:48:26 PM
Quote from: jakeroot on November 22, 2017, 08:34:28 PM
I must be the only person who browses pornography in the normal browser window. I appreciate the normal browser's ability to keep me logged in. And if I forget to favorite a video, I can usually go back and find it in my history.
It's not just you.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 29, 2017, 01:37:12 PM
The stupid removal of differentiation for freeways is making it tempting to create my own maps style.
https://developers.google.com/maps/documentation/javascript/styling
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 29, 2017, 06:43:03 PM
I'm still not seeing the new look. None of my W10 browsers are pulling it up.

My mobile app (Google Maps version 9.66.1) on Android 7.0 also has the normal colors. Usually Google changes colors platform-wide.
Title: Re: Google Maps just fucking SUCKS now
Post by: Great Lakes Roads on November 29, 2017, 07:05:16 PM
Ugh!! My eyes!! They changed the colors on the map, and it's hurting my eyes!! They just updated it on my Chrome app on the computer!!  :no: :no: :banghead: :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on November 29, 2017, 07:07:42 PM
The new color scheme made its way to me earlier in the day.  I hated it.  At some levels I couldn't see the roads.  I could see the labels showing where the highways should be, but I had to open the Street View overlay to actually see them or the unnumbered roads.  At most levels they were at least hard to see.  Fortunately for now it's gone back to the way it was.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on November 30, 2017, 12:49:39 PM
My maps just updated last night. I actually don't think it's that bad (though it's not really an improvement either). I appreciate that they've reintroduced outlines for local/white roads, which makes them easier to see at more zoomed-in levels. Local/white roads are still very hard to read when zoomed-out though :pan:. Making freeways similar in colour to arterials is also a downgrade. In the end, the lack of good contrast is still my biggest gripe (what good is a map if you struggle to see the roads?)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 30, 2017, 12:58:59 PM
Honestly, looking at the new maps hurts my eyes.  Local roads are impossible to see when zoomed out due to the lack of contrast, and telling freeways/arterials apart is near impossible unless you already know the area, rendering the maps useless in many situations.  Since I generally use maps in incognito, I'll often close the browser window and reopen to get it back to the old rendering.  It's getting to the point where I'm getting the new maps more often, though, and I'll probably eventually be stuck with it.  At that point, I might switch to the API (which hasn't started updating), a custom rendering, or even start switching many of my activities to another product (MapQuest is acceptable for driving directions, though it's not as convenient because dragging to change the route creates new destinations rather than just moving the route).
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on November 30, 2017, 01:02:01 PM
They brought the change back to me.  Here's a snippet of what it looks like.  I know there are roads in that area, I've driven on them.  Google thinks I don't deserve to know where they are.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.patternsandprinciples.com%2Fotherfiles%2Frs%2Fwheresthemroadsat.png&hash=bbb1ae13752d52056019e7d3a24236eae1624c2e)
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 30, 2017, 01:03:48 PM
Quote from: 7/8 on November 30, 2017, 12:49:39 PM
In the end, the lack of good contrast is still my biggest gripe (what good is a map if you struggle to see the roads?)

Good point, I wouldn't have thought of it. What Google is trying to do here is trying to make Maps look pretty with all the lack of contrast between objects, at the expense of usability. They fail to realize that the goal of a map is clarity, detail/contrast, (and the ability to differentiate things in general) and navigability, not looks.

They're picking style over functionality here. Google can apply their flat material design/sleek looks to whatever they want, but a map isn't the place.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 30, 2017, 02:07:39 PM
Part of the problem is that Google doesn't care about those of us who use the maps to see roads.  They have two core user bases: those who only want to plug an address into the driving directions and use their phone as a GPS, and those who use it to find businesses and places while walking around downtown.  This update is for the latter.  They're making the roads hard to see to make places easier to see, similar to how many tourism maps will use a flat style with often inaccurate road data.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on November 30, 2017, 03:24:18 PM
Hate the new color scheme.  Blech.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on November 30, 2017, 07:05:19 PM
Quote from: vdeane on November 29, 2017, 01:37:12 PM
The stupid removal of differentiation for freeways is making it tempting to create my own maps style.

It's the Fritzowlization of Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 30, 2017, 08:14:22 PM
Got the update today, and all of my browsers saw the update. My Android app still has the old colors, though.

Upon first glance, it appears there are more freeways than there really are. But if you look very closely, you can see that freeways are a slightly darker yellow. It's not enough of a difference for it to mean anything, but at least Google still recognises the existence of grade-separated roads...

(https://i.imgur.com/t4DwuCK.png)

(https://i.imgur.com/QLP1qnw.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: ET21 on December 01, 2017, 09:01:46 AM
I've not liked their new traffic later, the colors almost seem too bold in some areas. They've started to sharpen the lines on their latest updates
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 01, 2017, 09:06:03 AM
This all begs the question: is there anybody out there who's developing an online, interactive mapping service that actually tries to emulate good, traditional cartographic principles and content? Is OSM the closest thing we have? Maybe ArcGIS? Anybody? Bueller?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 01, 2017, 12:32:23 PM
As far as I know, OSM is the closest we've got.  Maybe it's time to design a "roadgeek" tileset for OSM using something like MapWorks, Jimapco, or even what MapQuestOpen looked like?  Even a custom Google color scheme would still have to be Google-style, since they don't retain API hooks they themselves don't use.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on December 01, 2017, 01:06:27 PM
I was going WB on US 6 just past I-84 near Milford, PA and was caught in a treadmill.   As soon as I got to a point past the part where it narrows down to two lanes, I get moved back to the point before the Sunoco Station on the left side just past the interchange.   Though it was a one time thing until I was thrown back again.

Passing the same gas station over and over again is like being in the Flintstones' universe.  Passing the same house, sofa, lamp, over and over.  That is for those of you who remember the classic cartoon by Hana Barbara.
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on December 01, 2017, 03:29:45 PM
Why in the hell did they discontinue the darker orange color for limited-access freeways!?!?  It should be easier to discern different types of highways, not harder!  They need to use MORE colors!  Garbage  :pan: :pan: :pan: :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 01, 2017, 04:25:41 PM
Soon, it'll all be light grey on light grey.

Oh, wait, do I mean like this?  Yeah, I just snipped that today.   :ded:

(https://i.imgur.com/L379JJI.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: BrianP on December 01, 2017, 04:26:14 PM
Quote from: paulthemapguy on December 01, 2017, 03:29:45 PM
Why in the hell did they discontinue the darker orange color for limited-access freeways!?!?  It should be easier to discern different types of highways, not harder!  They need to use MORE colors!  Garbage  :pan: :pan: :pan: :pan:

Quote from: vdeane on November 30, 2017, 02:07:39 PM
Part of the problem is that Google doesn't care about those of us who use the maps to see roads.  They have two core user bases: those who only want to plug an address into the driving directions and use their phone as a GPS, and those who use it to find businesses and places while walking around downtown.  This update is for the latter.  They're making the roads hard to see to make places easier to see, similar to how many tourism maps will use a flat style with often inaccurate road data.

I came to the same conclusion.  Google Maps is not intended for finding a route from point A to B.  It is intended to find destination(s) and let the app find the best route for you which includes taking traffic into consideration from your start which is likely your current location to your destination.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on December 01, 2017, 04:53:03 PM
Now it feels like I cranked f.lux to maximum every time I use the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 01, 2017, 04:53:47 PM
Quote from: vdeane on November 30, 2017, 02:07:39 PM
Part of the problem is that Google doesn't care about those of us who use the maps to see roads.  They have two core user bases: those who only want to plug an address into the driving directions and use their phone as a GPS, and those who use it to find businesses and places while walking around downtown.  This update is for the latter.  They're making the roads hard to see to make places easier to see, similar to how many tourism maps will use a flat style with often inaccurate road data.

I don't think they're making roads harder to see, they're just making freeways less visible. In fact, the roads seem to stand out a bit more than they used to. There's a faint outline to all the roads that's more pronounced than I recall with previous versions.

After using the new maps for a day, I actually quite like it. The freeway colors are a bit odd, but I'll get used to it. To be completely honest, I always thought freeways were a bit unnecessarily bright. I don't know if they need to fade into the background quite as much as they do now, but I would be okay with a blue or greyish-red (like OSM). Orange was way too bright.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on December 01, 2017, 07:08:07 PM
^ The old OpenStreetMap colors were awesome IMO: blue, green, red, orange, and yellow IIRC for freeway, trunk road, primary, secondary, and tertiary arterial respectively.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 01, 2017, 07:17:24 PM
Quote from: 20160805 on December 01, 2017, 07:08:07 PM
^ The old OpenStreetMap colors were awesome IMO: blue, green, red, orange, and yellow IIRC for freeway, trunk road, primary, secondary, and tertiary arterial respectively.

OSM was/is great for map viewing/scanning -- to an extent. I use Google Street View and 3D imagery so often that using anything except GMaps is mostly a waste of my time. OSM isn't so great for finding POIs, though. It's capable, but it's nowhere near as useful as Google Maps. What would be most ideal would be if Google adopted some of OSM's color schemes, and then muted them a bit. OSM's "Humanitarian" color scheme would be an excellent choice to start with.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on December 01, 2017, 08:38:35 PM
OSM is just too busy, trying to render too much at once with colors that can be hard to distinguish. The current Carto style is better than the old Mapnik style in that regard for the most part (trunk routes through huge forests were hard to follow, like US 22 and 522 between I-99 and 322). Compare Google (https://goo.gl/maps/t1hSam4Rkdw) to OSM (https://www.openstreetmap.org/#map=6/45.568/18.962) in Europe. Which is easier to pick the names out from the borders? OSM needs front-end usability work for the map on the main site, aside from that it's just a great database.

As for Google, the only thing I really don't like about the new style is freeways being so yellow. Make them a more prominent orange and it'd be great.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 01, 2017, 10:19:45 PM
Quote from: jakeroot on December 01, 2017, 04:53:47 PMAfter using the new maps for a day, I actually quite like it. The freeway colors are a bit odd, but I'll get used to it. To be completely honest, I always thought freeways were a bit unnecessarily bright. I don't know if they need to fade into the background quite as much as they do now, but I would be okay with a blue or greyish-red (like OSM). Orange was way too bright.

I frankly didn't care about the color so much as I cared about there being enough contrast for me to differentiate freeway and expressway segments on the same road.  The former combination of orange and yellow worked well for this purpose; the current combination of gold and yellow, separated by just a few shades, does not.  This retrograde step is especially glaring in the case of roads which are slowly being upgraded to freeway and have disjoint freeway segments connected by expressway, like US 70 in North Carolina east of Raleigh.

I wonder if part of the motivation is to cut off customer feedback about which roads are freeways and which are not.  This is something Google still gets wrong--for example, here in Wichita it correctly tags the parts of Kellogg Avenue that are freeway, but further west it tags the Garden Plain-Kingman freeway segment as ordinary expressway.

It is still valuable to have online mapping make a clear distinction between freeways and expressways because a certain segment of the driving public (myself included) will accept slightly longer travel time and much longer travel distance in exchange for free flow, especially on freeways that are reliably uncongested.  This does not have to conflict with Google's apparent goal of improving the relevancy of Maps to people walkabout in strange cities.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on December 02, 2017, 12:41:50 AM
My issue with the new maps is that it seems the decision on which roads are arterials seems a bit arbitrary in some cases. For example, near SLC, why are 11400 S and 12600 S arterials when other similar roads like 9000 S aren't? Or why isn't Bangerter between UT-201 and the airport an arterial, when it is expressway to freeway grade in those areas?
That's what mostly pisses me off about this update. Freeways and arterials aren't really distinguished, and other roads are just white and tend to blend into the background. The arbitrary decisions about arterials make some roads look like freeways while other equivalent roads seem to fall off the map.

[/rant]
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 02, 2017, 01:35:23 AM
Heck, there are some places where the artieral ends randomly.  NY 33, for example, should be at arterial at least to I-490.
https://www.google.com/maps/@43.1475983,-77.7295579,14.71z

Quote from: jakeroot on December 01, 2017, 04:53:47 PM
I don't think they're making roads harder to see, they're just making freeways less visible. In fact, the roads seem to stand out a bit more than they used to. There's a faint outline to all the roads that's more pronounced than I recall with previous versions.

After using the new maps for a day, I actually quite like it. The freeway colors are a bit odd, but I'll get used to it. To be completely honest, I always thought freeways were a bit unnecessarily bright. I don't know if they need to fade into the background quite as much as they do now, but I would be okay with a blue or greyish-red (like OSM). Orange was way too bright.
Maybe at close in zooms, though I think the small border is offset by the overall lack of contrast.  Trying to see any of the white roads at zooms 11 or 12, though, is effectively impossible.  The map is just washed out (in fact, at zoom 5 it's like staring at a light bulb).

I didn't think the orange/brown was "too bright".  I liked being able to see which roads were freeway/expressway at a glance.  After all, freeways are the most important roads - they should stand out, right?

Quote from: Roadsguy on December 01, 2017, 08:38:35 PM
OSM is just too busy, trying to render too much at once with colors that can be hard to distinguish. The current Carto style is better than the old Mapnik style in that regard for the most part (trunk routes through huge forests were hard to follow, like US 22 and 522 between I-99 and 322). Compare Google (https://goo.gl/maps/t1hSam4Rkdw) to OSM (https://www.openstreetmap.org/#map=6/45.568/18.962) in Europe. Which is easier to pick the names out from the borders? OSM needs front-end usability work for the map on the main site, aside from that it's just a great database.

As for Google, the only thing I really don't like about the new style is freeways being so yellow. Make them a more prominent orange and it'd be great.
Agreed.  OSM is VERY cluttered, especially in areas with parks/forests, like the Adirondacks (or all of Canada, which seems to have splotches of green randomly placed all over the map).  If it weren't for that and the lack of many of Google's features, I'd switch over there.  It's too bad the MapQuestOpen style scheme went away.  That was awesome.

I still don't like the "staring into a light bulb" effect of the new Google color scheme, though I do agree that fixing the freeway color would go 80-90% of the way to fixing it.

Quote from: J N Winkler on December 01, 2017, 10:19:45 PM
Quote from: jakeroot on December 01, 2017, 04:53:47 PMAfter using the new maps for a day, I actually quite like it. The freeway colors are a bit odd, but I'll get used to it. To be completely honest, I always thought freeways were a bit unnecessarily bright. I don't know if they need to fade into the background quite as much as they do now, but I would be okay with a blue or greyish-red (like OSM). Orange was way too bright.

I frankly didn't care about the color so much as I cared about there being enough contrast for me to differentiate freeway and expressway segments on the same road.  The former combination of orange and yellow worked well for this purpose; the current combination of gold and yellow, separated by just a few shades, does not.  This retrograde step is especially glaring in the case of roads which are slowly being upgraded to freeway and have disjoint freeway segments connected by expressway, like US 70 in North Carolina east of Raleigh.

I wonder if part of the motivation is to cut off customer feedback about which roads are freeways and which are not.  This is something Google still gets wrong--for example, here in Wichita it correctly tags the parts of Kellogg Avenue that are freeway, but further west it tags the Garden Plain-Kingman freeway segment as ordinary expressway.

It is still valuable to have online mapping make a clear distinction between freeways and expressways because a certain segment of the driving public (myself included) will accept slightly longer travel time and much longer travel distance in exchange for free flow, especially on freeways that are reliably uncongested.  This does not have to conflict with Google's apparent goal of improving the relevancy of Maps to people walkabout in strange cities.
Unfortunately, it seems that Google removed the expressway distinction entirely.  Now those sections are considered arterials.  Since they also removed the corresponding API key, this unfortunately can't be fixed with a custom color scheme.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 02, 2017, 02:59:32 AM
Quote from: vdeane on December 02, 2017, 01:35:23 AM
Quote from: jakeroot on December 01, 2017, 04:53:47 PM
I don't think they're making roads harder to see, they're just making freeways less visible. In fact, the roads seem to stand out a bit more than they used to. There's a faint outline to all the roads that's more pronounced than I recall with previous versions.

After using the new maps for a day, I actually quite like it. The freeway colors are a bit odd, but I'll get used to it. To be completely honest, I always thought freeways were a bit unnecessarily bright. I don't know if they need to fade into the background quite as much as they do now, but I would be okay with a blue or greyish-red (like OSM). Orange was way too bright.

Maybe at close in zooms, though I think the small border is offset by the overall lack of contrast.  Trying to see any of the white roads at zooms 11 or 12, though, is effectively impossible.  The map is just washed out (in fact, at zoom 5 it's like staring at a light bulb).

I think you might need to adjust the contrast on your display. I don't have even the slightest problem distinguishing the white roads from the background. Granted, I have "perfect vision", but I think it's more about contrast than one's vision.

Quote from: vdeane on December 02, 2017, 01:35:23 AM
I didn't think the orange/brown was "too bright".  I liked being able to see which roads were freeway/expressway at a glance.  After all, freeways are the most important roads - they should stand out, right?

But there are other colors that could have been used that would stand out without blinding the user. Like I suggested upthread, blue is a great color, because it's not any where near as bright (it's usually opposite orange on color wheels), but it would still stand out against a white background.

Freeways are the most important road, yes. But having freeways stand out like they did appealed to only a small group of users. This latest update was a clear attempt at fading the colors more into the background, in order to highlight POIs. Google Maps' largest user base is clearly those who are using it to find POIs (and to help them get there).
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on December 02, 2017, 04:56:04 AM
Quote from: kphoger on December 01, 2017, 04:25:41 PM
Soon, it'll all be light grey on light grey.

Oh, wait, do I mean like this?  Yeah, I just snipped that today.   :ded:

(https://i.imgur.com/L379JJI.png)

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi0.kym-cdn.com%2Fphotos%2Fimages%2Foriginal%2F000%2F216%2F905%2F10333118.jpg&hash=5a6f1dd592da417656bc8c60546a6d2a0f42e3c3)

Thank God my android hasn't changed yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 02, 2017, 12:57:37 PM
Quote from: jakeroot on December 02, 2017, 02:59:32 AMFreeways are the most important road, yes. But having freeways stand out like they did appealed to only a small group of users.

Do you have independent evidence that this is so, or are you reasoning backward from the de-emphasizing of freeways?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 02, 2017, 03:01:44 PM
Quote from: J N Winkler on December 02, 2017, 12:57:37 PM
Quote from: jakeroot on December 02, 2017, 02:59:32 AM
Freeways are the most important road, yes. But having freeways stand out like they did appealed to only a small group of users.

Do you have independent evidence that this is so, or are you reasoning backward from the de-emphasizing of freeways?

Obviously the latter. But I wasn't the first to propose the theory:

Quote from: vdeane on November 30, 2017, 02:07:39 PM
Part of the problem is that Google doesn't care about those of us who use the maps to see roads.  They have two core user bases: those who only want to plug an address into the driving directions and use their phone as a GPS, and those who use it to find businesses and places while walking around downtown.  This update is for the latter.  They're making the roads hard to see to make places easier to see, similar to how many tourism maps will use a flat style with often inaccurate road data.

Valerie is spot on. Google Maps' core user base does not use the app to dick around like we do.

Now, I don't know why de-emphasizing freeways makes POI's stand out better (nor why we couldn't have it both ways), but if Google thinks that having freeways blend-in improves the visibility of POI's, then by all means, de-emphasize the freeways.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 02, 2017, 06:03:50 PM
My point is that we shouldn't assume the Google product designers understand their market or technology well enough to have a full appreciation of the implications of various design choices.  This is, after all, the same company that developed an AI for Google Photos that labeled black people as gorillas.

Assigning almost the same color to freeways as to expressways/arterials smacks of myopia arising from living in Silicon Valley, where the freeways are so congested the mobility they offer is not much better than on expressways or arterials.  There are still many regions of the country where this is not true.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 02, 2017, 10:45:02 PM
Quote from: J N Winkler on December 01, 2017, 10:19:45 PM
It is still valuable to have online mapping make a clear distinction between freeways and expressways because a certain segment of the driving public (myself included) will accept slightly longer travel time and much longer travel distance in exchange for free flow, especially on freeways that are reliably uncongested.

Whereas for some of us, in certain parts of the country, that same willingness results in avoiding freeways, rather than opting for them.
Title: Google Maps
Post by: doglover44 on December 04, 2017, 10:53:29 AM
Has Google maps gotten better ?
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on December 04, 2017, 01:08:42 PM
Quote from: doglover44 on December 04, 2017, 10:53:29 AM
Has Google maps gotten better ?

Short answer: no.  It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 04, 2017, 04:09:00 PM
Quote from: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.

Other than New York City and Montreal, where do traffic laws concerning allowed/prohibited movements differ within a state (or equivalent)?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 04, 2017, 04:13:39 PM
Quote from: 1 on December 04, 2017, 04:09:00 PM
Quote from: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.

Other than New York City and Montreal, where do traffic laws concerning allowed/prohibited movements differ within a state (or equivalent)?

U-turns are not allowed within Chicago city limits except where specifically permitted by signage.  In the rest of Illinois, U-turns are permitted at traffic-controlled intersections except where specifically prohibited by signage.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 03:01:32 AM
Quote from: 1 on December 04, 2017, 04:09:00 PM
Other than New York City and Montreal, where do traffic laws concerning allowed/prohibited movements differ within a state (or equivalent)?

As far as I know, "cities" (or equivalent legal term) in most (all?) states are capable of modifying traffic laws. I don't believe local laws are allowed to be less restrictive than state law, but they can be more restrictive (unless the state's supreme court finds the law to be unconstitutional). In Washington, while the state allows U-turns everywhere (unless a car's coming, or you're at a hill -- that's it), cities can implement U-turn laws that are more restrictive. Tacoma specifically bans them unless a sign allows the maneuver. Most other laws seem to be left unchanged; not sure why U-turns are often targeted at the municipal level.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 05, 2017, 10:04:28 AM
Quote from: jakeroot on December 05, 2017, 03:01:32 AM
Quote from: 1 on December 04, 2017, 04:09:00 PM
Other than New York City and Montreal, where do traffic laws concerning allowed/prohibited movements differ within a state (or equivalent)?

As far as I know, "cities" (or equivalent legal term) in most (all?) states are capable of modifying traffic laws. I don't believe local laws are allowed to be less restrictive than state law, but they can be more restrictive (unless the state's supreme court finds the law to be unconstitutional). In Washington, while the state allows U-turns everywhere (unless a car's coming, or you're at a hill -- that's it), cities can implement U-turn laws that are more restrictive. Tacoma specifically bans them unless a sign allows the maneuver. Most other laws seem to be left unchanged; not sure why U-turns are often targeted at the municipal level.

Forgot to state what might be obvious...  Laws like U-turns are actually more pertinent to the discussion.  I assume bringing up NYC and Montréal was in reference to turning right on red lights.  That being allowed or prohibited has no bearing on how Google Maps directs you from A to B.  You can still turn right at those red lights; you just have to wait till the light turns green first.  But laws regarding left turns across flush medians or U-turns in general do affect how you get from A to B.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on December 05, 2017, 12:07:22 PM
Quote from: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.

I don't see where it's all that hard on that issue.  California is the only place I've ever heard of with that prohibition.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 02:24:15 PM
^^^
Google doesn't see the intersection (posted previously (https://www.aaroads.com/forum/index.php?topic=11718.msg2269956#msg2269956) by Brandon) as a roadway with a flush median. It sees a hard median (and the intersecting road as a RIRO). There's no way for Google Maps to know that turning left is physically possible there; as far as it can tell, there's a physical obstruction, hence the divided roadway.

I did finally just contact Google Maps about South Bridge Street, but more about how it's shown as a divided highway, rather than a single-carriageway road. From just north of Stagecoach Trail, to Fairfax Way, South Bridge Street (IL-47) is shown as a divided highway, when at no point it is. I asked them to remove the divided highway indication.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 05, 2017, 02:32:21 PM
Quote from: jakeroot on December 05, 2017, 02:24:15 PM
^^^
Google doesn't see the intersection (posted previously (https://www.aaroads.com/forum/index.php?topic=11718.msg2269956#msg2269956) by Brandon) as a roadway with a flush median. It sees a hard median (and the intersecting road as a RIRO). There's no way for Google Maps to know that turning left is physically possible there; as far as it can tell, there's a physical obstruction, hence the divided roadway.

My experience with Google Maps is that it simply sees medians as medians.  In very many places where there's a painted flush median, it renders the road as a divided thoroughfare, thereby disallowing left turns.  The Illinois location is far from an isolated case; in fact, I'd say it's the norm.  Now, usually, it doesn't affect getting directions, because it also renders a crossover at each major intersection, and also because your destination is rarely on the other side of the road from you across a flush median.  But, unless such a crossover is rendered on the map for a side street, it won't give directions across the median.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 02:48:37 PM
Quote from: kphoger on December 05, 2017, 02:32:21 PM
Quote from: jakeroot on December 05, 2017, 02:24:15 PM
^^^
Google doesn't see the intersection (posted previously (https://www.aaroads.com/forum/index.php?topic=11718.msg2269956#msg2269956) by Brandon) as a roadway with a flush median. It sees a hard median (and the intersecting road as a RIRO). There's no way for Google Maps to know that turning left is physically possible there; as far as it can tell, there's a physical obstruction, hence the divided roadway.

My experience with Google Maps is that it simply sees medians as medians.  In very many places where there's a painted flush median, it renders the road as a divided thoroughfare, thereby disallowing left turns.  The Illinois location is far from an isolated case; in fact, I'd say it's the norm.  Now, usually, it doesn't affect getting directions, because it also renders a crossover at each major intersection, and also because your destination is rarely on the other side of the road from you across a flush median.  But, unless such a crossover is rendered on the map for a side street, it won't give directions across the median.

I was going to tell them draw a connecting road from Bonnie Lane to both directions of South Bridge Street, but I noticed that several other roads in the area also weren't connected to both directions, so I decided it was easier to tell them to just remove the divided highway indication altogether.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on December 05, 2017, 05:43:40 PM
Quote from: Brandon on December 05, 2017, 12:07:22 PM
Quote from: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.

I don't see where it's all that hard on that issue.  California is the only place I've ever heard of with that prohibition.

The way I understood UT law as I learned it in drivers ed, that movement would also be illegal in Utah. I can't find the law on that right now, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 05, 2017, 06:25:57 PM
Quote from: roadguy2 on December 05, 2017, 05:43:40 PM
Quote from: Brandon on December 05, 2017, 12:07:22 PM
Quote from: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.

I don't see where it's all that hard on that issue.  California is the only place I've ever heard of with that prohibition.

The way I understood UT law as I learned it in drivers ed, that movement would also be illegal in Utah. I can't find the law on that right now, though.

Well, stuff does get taught in driver's ed that isn't actually law...
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 05, 2017, 08:23:21 PM
The new Google Maps update is absolutely horrendous.  :eyebrow:  :no:  X-(  :thumbdown:

This marks the first time in the history of my life that I have searched "X" Maps up in replacement of Google Maps (I have obviously searched up other maps sites many times before, but this is the first time that I have done so for the reason that Google Maps has now become a really aversive option (for the most part) with this new update). I may literally have to do something like use Bing Maps and Google Maps simultaneously to be able to function in that regard (and that is what I was forced to do for the first time a few days ago). I have noticed a little bit of a cheat. In the hopes that something in the old color scheme and look of the roads was still in existence, I played around with things some. I found that at least in some spots (such as here (https://www.google.com/maps/@34.8017109,-85.0091954,3a,75y,307.84h,88.38t/data=!3m7!1e1!3m5!1siE4cfYyY98_0dc6myzO05g!2e0!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3DiE4cfYyY98_0dc6myzO05g%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D17.30978%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656) and here (https://www.google.com/maps/@33.9461556,-84.6220454,3a,75y,280.29h,94.44t/data=!3m7!1e1!3m5!1sO5ATmwWd7TtcWhz18-Wvkg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DO5ATmwWd7TtcWhz18-Wvkg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D275.03113%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656)), when you go into street-view, the old look of things is still present now in the mini-map in the bottom left corner of the screen - but from what I can tell, that is all we have left of it.  :-(

Unfortunately, the update has gone into effect in everything I've been on lately (computers, iPhone, etc.), so I personally cannot escape it no matter what I use to access Google Maps.  :rolleyes:

I can't stand how it is unbearably hard to differentiate between limited-access highways and surface streets, and another very annoying thing is that you can't even see the very, very minor small neighborhood roads and such. If I want to get a general idea of what the entire road system of a town or a city looks like (including all the small neighborhood roads), it is miles harder to do that now. Take the suburban sprawl in the Atlanta Metro Area, for example: when I try to get a feel of the entire road system of this area, it is almost impossible to detect all the very minor roads. When I look here (https://www.google.com/maps/@33.9861483,-84.4674293,14.75z), it is so freakin hard to see all the very small roads, because they completely blend in with the white background; the only thing I can really see is the names of the roads, and there's even only so many of those that are actually listed and visible. It actually hurts my eyes when I try to make out the white roads! They have truly jacked up the colors for small roads and big highways alike - it is all a terrible disaster now!

Google Maps has always been my favorite online maps tool, especially because of the street-view function, so this saddens me and frustrates me very greatly.  :angry:

Hopefully they will fix it, and hopefully that will be very soon - because they really truly have messed things up with this new update.


Quote from: jakeroot on November 18, 2017, 02:19:59 AM
Quote from: index on November 17, 2017, 10:27:37 PM
Perhaps these new road color schemes are just something that would bug people who are interested in roads?

Almost certainly! Most of the changes to Google Maps, over the last few years, have not favored roadgeeks who simply use it to browse for fun. Ask any resident of the UK. The roads there used to be colored to match the route designation (blue, green, orange, white, etc). Now, all the colors match the rest of the world. This makes looking at maps confusing, especially since A-roads will sometimes be yellow, and sometimes white. Before, they were always green. Bing Maps still colors UK roads properly.

That is a very good point. As irksome as it may be to us, us roadgeeks are in the minority, so the emphasis will unfortunately not be put on us. We may try to attempt to jump to streetview on a cool city interstate, but GMSV will force us to first be planted onto a random neighborhood road nearby, because most of its audience cares about the house and/or the destination, not the freeway. And then there's all these signs that are completely blurred out - because who would want to look at that...not most people, but little do they know about us. Most people probably don't use Google Maps and GMSV for fun like we do. Though, with that said...regarding something I said earlier in my post about not being able to decipher the white neighborhood roads and such, that means Google Maps is being very prohibitive to the public and most of its audience in general by doing that - because most people may want to get to the house or the building, but now even they can't see the very minor roads that it may be off of. This isn't good for anybody!  :confused:

It truly baffles me as to why they would do that, since us road enthusiasts are not the only people that it even affects. I apologize for the rant, but this was just a terrible update - I don't know what they were thinking. Maybe someone can key us in as to why in the world they would make such changes like this.  :confused:
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 05, 2017, 08:40:08 PM
Well, most people these days just plug the address into their GPS.  Google Maps isn't built for people to browse to their destination (unless they're looking for hip restaurants or shops in a city), but rather to plug the address in to the search window and let Google navigate.

There is still one loophole left: embedded maps (http://tm.teresco.org/user/mapview.php?u=vdeane&) (you'll have to switch to Google, but on the plus side, you can also use this to get street view in OSM).  Of course, Google closed the last loophole I used (repeatedly closing and reopening incognito windows until I got the old colors, and then leaving the tab open all day so it couldn't switch when even that became tenuous) within a few hours of me mentioning it on Facebook, so that might disappear any minute now.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 08:46:15 PM
Quote from: adventurernumber1 on December 05, 2017, 08:23:21 PM
I can't stand how it is unbearably hard to differentiate between limited-access highways and surface streets, and another very annoying thing is that you can't even see the very, very minor small neighborhood roads and such. If I want to get a general idea of what the entire road system of a town or a city looks like (including all the small neighborhood roads), it is miles harder to do that now. Take the suburban sprawl in the Atlanta Metro Area, for example: when I try to get a feel of the entire road system of this area, it is almost impossible to detect all the very minor roads. When I look here (https://www.google.com/maps/@33.9861483,-84.4674293,14.75z), it is so freakin hard to see all the very small roads, because they completely blend in with the white background; the only thing I can really see is the names of the roads, and there's even only so many of those that are actually listed and visible. It actually hurts my eyes when I try to make out the white roads! They have truly jacked up the colors for small roads and big highways alike - it is all a terrible disaster now!

I think you may need to adjust either the brightness of your display, or (more likely) the contrast settings. I have no problem seeing the minor roads against the background.

Freeways and highways are definitely harder to tell apart now, though. That said, I can still somewhat differentiate between the two due to the slightly different colors (I have good color vision), plus, I think I'm the only one with my contrast settings set correctly (vdeane is/was having similar issues).
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 05, 2017, 08:49:51 PM
Quote from: jakeroot on December 05, 2017, 08:46:15 PM
I think you may need to adjust either the brightness of your display, or (more likely) the contrast settings. I have no problem seeing the minor roads against the background.

Freeways and highways are definitely harder to tell apart now, though. That said, I can still somewhat differentiate between the two due to the slightly different colors (I have good color vision), plus, I think I'm the only one with my contrast settings set correctly (vdeane is/was having similar issues).

While it's possible that peoples' monitors may be poorly adjusted, I also think Google is to blame for making an absolutely correctly-tuned display necessary. There's no reason that the map should only be clearly legible on displays in ideal settings and conditions.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on December 05, 2017, 09:00:36 PM
Quote from: jakeroot on December 05, 2017, 08:46:15 PM
Quote from: adventurernumber1 on December 05, 2017, 08:23:21 PM
I can't stand how it is unbearably hard to differentiate between limited-access highways and surface streets, and another very annoying thing is that you can't even see the very, very minor small neighborhood roads and such. If I want to get a general idea of what the entire road system of a town or a city looks like (including all the small neighborhood roads), it is miles harder to do that now. Take the suburban sprawl in the Atlanta Metro Area, for example: when I try to get a feel of the entire road system of this area, it is almost impossible to detect all the very minor roads. When I look here (https://www.google.com/maps/@33.9861483,-84.4674293,14.75z), it is so freakin hard to see all the very small roads, because they completely blend in with the white background; the only thing I can really see is the names of the roads, and there's even only so many of those that are actually listed and visible. It actually hurts my eyes when I try to make out the white roads! They have truly jacked up the colors for small roads and big highways alike - it is all a terrible disaster now!

I think you may need to adjust either the brightness of your display, or (more likely) the contrast settings. I have no problem seeing the minor roads against the background.

Freeways and highways are definitely harder to tell apart now, though. That said, I can still somewhat differentiate between the two due to the slightly different colors (I have good color vision), plus, I think I'm the only one with my contrast settings set correctly (vdeane is/was having similar issues).

This issue actually happened on my local news last night. They used Google Maps to show a location, but the streets were completely invisible and the only things anyone could see were the street names and the interstate.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 09:22:07 PM
Huh. Well, maybe this is a bigger issue than I realised. Google definitely has a duty to ensure their map colors contrast properly on all displays (to a degree -- I don't think anyone is expecting them to use Playskool colors), however, I don't know if they realised this would become a big issue. After all, on my properly adjusted display, I have zero issues telling the colors apart. And I'm sure Google's programmer displays are adjusted properly as well. I do find it rather intriguing that some user's displays could have the contrast so fubar'd that they couldn't tell the colors apart, though (considering how far apart on the brightness scale the background and minor road colors actually are).
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 05, 2017, 09:29:15 PM
Quote from: jakeroot on December 05, 2017, 09:22:07 PM
I do find it rather intriguing that some user's displays could have the contrast so fubar'd that they couldn't tell the colors apart, though (considering how far apart on the brightness scale the background and minor road colors actually are).

Factory settings on a lot of monitors (particularly those on the low end) are absolutely trash, and I wouldn't be surprised if a large number of people assume the defaults are good or never bother to ensure they're properly adjusted.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 10:20:53 PM
Quote from: MNHighwayMan on December 05, 2017, 09:29:15 PM
Quote from: jakeroot on December 05, 2017, 09:22:07 PM
I do find it rather intriguing that some user's displays could have the contrast so fubar'd that they couldn't tell the colors apart, though (considering how far apart on the brightness scale the background and minor road colors actually are).

Factory settings on a lot of monitors (particularly those on the low end) are absolutely trash, and I wouldn't be surprised if a large number of people assume the defaults are good or never bother to ensure they're properly adjusted.

Well, I guess when this implementation is all said and done, there'll be a lot less poorly-adjusted monitors!
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 05, 2017, 10:49:02 PM
Quote from: jakeroot on December 05, 2017, 10:20:53 PM
Well, I guess when this implementation is all said and done, there'll be a lot less poorly-adjusted monitors!

That's taking a rather hopelessly proactive view on users' reactions to Google's change. :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 05, 2017, 11:22:18 PM
Quote from: MNHighwayMan on December 05, 2017, 10:49:02 PM
Quote from: jakeroot on December 05, 2017, 10:20:53 PM
Well, I guess when this implementation is all said and done, there'll be a lot less poorly-adjusted monitors!

That's taking a rather hopelessly proactive view on users' reactions to Google's change. :-D

Everytime Google changes something, people get all up in arms, threaten to leave the service, etc. But the fact is that there is nothing anywhere near as good as Google Maps. Other mapping services are good at directing you from A to B, but they don't have the integration that Google Maps does. I'm not suggesting we all permanently hail El Goog, but it's still the best mapping service, apart from some color issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on December 05, 2017, 11:26:24 PM
gokml.net/maps is good for a lot of things. Google's database, better color choices, faster.  But, no directions.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 05, 2017, 11:31:56 PM
Quote from: jakeroot on December 05, 2017, 11:22:18 PM
Quote from: MNHighwayMan on December 05, 2017, 10:49:02 PM
Quote from: jakeroot on December 05, 2017, 10:20:53 PM
Well, I guess when this implementation is all said and done, there'll be a lot less poorly-adjusted monitors!

That's taking a rather hopelessly proactive view on users' reactions to Google's change. :-D

Everytime Google changes something, people get all up in arms, threaten to leave the service, etc. But the fact is that there is nothing anywhere near as good as Google Maps. Other mapping services are good at directing you from A to B, but they don't have the integration that Google Maps does. I'm not suggesting we all permanently hail El Goog, but it's still best mapping service, apart from some color issues.

Well said. Google does have its issues but personally, I stick to Google Earth Pro (hasn't been updated in a while and street view is actually half decent. Plus I like the extra tools over the online version).
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 05, 2017, 11:35:57 PM
Personally, I dislike Street View in GE. Historic images aren't available and the controls are clunky and sometimes glitchy, IME.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 05, 2017, 11:55:58 PM
Quote from: MNHighwayMan on December 05, 2017, 11:35:57 PM
Personally, I dislike Street View in GE. Historic images aren't available and the controls are clunky and sometimes glitchy, IME.

I agree that it isn't great which is why I said half decent. At least the speed is good (although not driving speed) and It isn't cluttered with stuff besides the upper right hand corner. I only do it because I can't get to or afford to go on long road trips so this is my way to road trip. Cons: Flipping between sides of the road on two laners, no historical imagery, can be blurry, lag on my computer (although my computer isn't that good).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 06, 2017, 12:53:40 AM
I generally avoid using Street View in Earth. The lack of historical imagery bothers me as well, and the lack of a small map to click around makes it difficult to use (the control are indeed quite clunky). So, I often am running both Earth and Maps at the same time.

Although I find myself using Historic Aerials quite often now, I still prefer to use Google Earth's Historic Imagery because it doesn't have watermarks, and usually more recent historic imagery (Historic Aerials might have 10 shots from 2000-2017, but Earth would have 25+ at least in my area).
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 06, 2017, 12:56:38 AM
Quote from: roadguy2 on December 05, 2017, 05:43:40 PM
Quote from: Brandon on December 05, 2017, 12:07:22 PM
Quote from: kkt on December 04, 2017, 04:04:24 PM
Quote from: kphoger on December 04, 2017, 02:46:46 PM
Quote from: myosh_tino on December 04, 2017, 01:21:05 PM
Quote from: Brandon on December 04, 2017, 01:08:42 PM
It also doesn't help that Google suffers from creator provincialism and applies California traffic law everywhere.

In what way?  I'm just curious.

I think he's referring to prohibiting left turns across painted flush medians.

Ah.  I guess Google is being conservative, because even if some jurisdictions allow such left turns, some don't, and it's hard to keep track of thousands of local jurisdictions' laws.

I don't see where it's all that hard on that issue.  California is the only place I've ever heard of with that prohibition.

The way I understood UT law as I learned it in drivers ed, that movement would also be illegal in Utah. I can't find the law on that right now, though.

Pretty sure it's not allowed in NY, either.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 06, 2017, 01:38:09 AM
Quote from: jakeroot on December 06, 2017, 12:53:40 AM
I generally avoid using Street View in Earth. The lack of historical imagery bothers me as well, and the lack of a small map to click around makes it difficult to use (the control are indeed quite clunky). So, I often am running both Earth and Maps at the same time.

Although I find myself using Historic Aerials quite often now, I still prefer to use Google Earth's Historic Imagery because it doesn't have watermarks, and usually more recent historic imagery (Historic Aerials might have 10 shots from 2000-2017, but Earth would have 25+ at least in my area).

Yep, that's why I use both on a regular basis. It's too bad Google can't seem to put them together to make one awesome product. :meh:
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 06, 2017, 02:01:36 AM
Quote from: roadguy2 on December 05, 2017, 09:00:36 PM
Quote from: jakeroot on December 05, 2017, 08:46:15 PM
Quote from: adventurernumber1 on December 05, 2017, 08:23:21 PM
I can't stand how it is unbearably hard to differentiate between limited-access highways and surface streets, and another very annoying thing is that you can't even see the very, very minor small neighborhood roads and such. If I want to get a general idea of what the entire road system of a town or a city looks like (including all the small neighborhood roads), it is miles harder to do that now. Take the suburban sprawl in the Atlanta Metro Area, for example: when I try to get a feel of the entire road system of this area, it is almost impossible to detect all the very minor roads. When I look here (https://www.google.com/maps/@33.9861483,-84.4674293,14.75z), it is so freakin hard to see all the very small roads, because they completely blend in with the white background; the only thing I can really see is the names of the roads, and there's even only so many of those that are actually listed and visible. It actually hurts my eyes when I try to make out the white roads! They have truly jacked up the colors for small roads and big highways alike - it is all a terrible disaster now!

I think you may need to adjust either the brightness of your display, or (more likely) the contrast settings. I have no problem seeing the minor roads against the background.

Freeways and highways are definitely harder to tell apart now, though. That said, I can still somewhat differentiate between the two due to the slightly different colors (I have good color vision), plus, I think I'm the only one with my contrast settings set correctly (vdeane is/was having similar issues).

This issue actually happened on my local news last night. They used Google Maps to show a location, but the streets were completely invisible and the only things anyone could see were the street names and the interstate.

Wow, what a story. I can't believe that actually happened, but I could see it happening: the news anchors aiming to show a location on Google Maps to the camera in the next few seconds, but they are unpleasantly surprised to find that they cannot see any of the small roads at all except for street names on a few of them and the big highways nearby. That is definitely quite embarrassing for Google.  :wow:  :-o  :meh:


Quote from: jakeroot on December 05, 2017, 11:22:18 PM
Quote from: MNHighwayMan on December 05, 2017, 10:49:02 PM
Quote from: jakeroot on December 05, 2017, 10:20:53 PM
Well, I guess when this implementation is all said and done, there'll be a lot less poorly-adjusted monitors!

That's taking a rather hopelessly proactive view on users' reactions to Google's change. :-D

Everytime Google changes something, people get all up in arms, threaten to leave the service, etc. But the fact is that there is nothing anywhere near as good as Google Maps. Other mapping services are good at directing you from A to B, but they don't have the integration that Google Maps does. I'm not suggesting we all permanently hail El Goog, but it's still the best mapping service, apart from some color issues.

That is a very good point. I am quite upset with this new update, but I don't see myself really leaving Google Maps, still. As I said in my post just slightly upthread, I will have to manage my navigating online maps by having both Google Maps and something else (such as Bing Maps or Google Earth, or both, or more) open - which will definitely be more of a hassle, but I think it is just what I am going to have to begin doing consistently. I will definitely still be using Google Maps, despite my high dissatisfaction with the new update, but I now must have supplementary online mapping sites along with it to be able to function with that. I just hope Google Maps changes their mind and goes back to the better style; I truly would love to see that happen.  :nod:
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 06, 2017, 09:07:43 AM
For me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 06, 2017, 11:12:52 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AMFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

It depends on whether you use the desktop or mobile version.  Mobile doesn't show county lines (but will drop a placemark at or near the approximate centroid of the county), but desktop (even after latest revision) shows the county lines and shades the county.  I think there was some discussion upthread many pages ago about Google eliminating county lines and shading in the desktop version, but if they actually tried that, they had to retreat from it.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 06, 2017, 11:26:44 AM
Quote from: J N Winkler on December 06, 2017, 11:12:52 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AMFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

It depends on whether you use the desktop or mobile version.  Mobile doesn't show county lines (but will drop a placemark at or near the approximate centroid of the county), but desktop (even after latest revision) shows the county lines and shades the county.  I think there was some discussion upthread many pages ago about Google eliminating county lines and shading in the desktop version, but if they actually tried that, they had to retreat from it.

You have to search for a county for its boundaries to be shown in Google Maps. In OpenStreetMap, they are shown automatically.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 06, 2017, 03:45:03 PM
Quote from: 1 on December 06, 2017, 11:26:44 AM
You have to search for a county for its boundaries to be shown in Google Maps.

Plus, the shading disappears at closer zoom levels.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 06, 2017, 08:02:04 PM
Last I checked, Google Maps could show Village, City, and County lines if searched for; they took away Town lines at some point.

Quote from: MNHighwayMan on December 05, 2017, 09:29:15 PM
Quote from: jakeroot on December 05, 2017, 09:22:07 PM
I do find it rather intriguing that some user's displays could have the contrast so fubar'd that they couldn't tell the colors apart, though (considering how far apart on the brightness scale the background and minor road colors actually are).

Factory settings on a lot of monitors (particularly those on the low end) are absolutely trash, and I wouldn't be surprised if a large number of people assume the defaults are good or never bother to ensure they're properly adjusted.
Indeed.  They're usually set to look sexy on a store shelf, not to have accurate color/decent contrast/brightness.  I actually had to dig around to figure out how to get mine set properly; I had previously adjusted it some, but I had to find an explanation for what many of the settings meant (I was previously only familiar with contrast/brightness, neither of which seemed to help until I learned what "sRGB Mode" was).  It's amazing how many other things I'm suddenly noticing contrast on, such as VLC's media library.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 06, 2017, 09:41:36 PM

Quote from: 1 on December 06, 2017, 11:26:44 AM
You have to search for a county for its boundaries to be shown in Google Maps.

Earth to Google: How are we supposed to find the borders if you remove them? :hmmm: I can't even find Deschutes National Forest thanks to you (New project ending at the border of the forest). FIX IT!
Also, make freeways blue and keep the normal highways yellow, that will differentiate it a little more.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on December 07, 2017, 07:16:43 AM
While on the subject of road colors, my mom's car has a built-in navigation program, and it uses red for freeways, orange for expressways and big boulevards, green for arterials, and gray for side streets.  The only problem is that it is completely unreliable when it comes to city boundaries, is missing several streets, and the differentiation between gray and green and between green and orange are case-by-case, arbitrary, and inconsistent.  College Ave in metro Appleton between Casaloma Dr and County CB shows up as gray, for example.

When I make maps, I use a similar coloring scheme, but I also add a dark green color for minor arterials.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 07, 2017, 08:27:04 PM
Quote from: 20160805 on December 07, 2017, 07:16:43 AM
While on the subject of road colors, my mom's car has a built-in navigation program, and it uses red for freeways, orange for expressways and big boulevards, green for arterials, and gray for side streets.  The only problem is that it is completely unreliable when it comes to city boundaries, is missing several streets, and the differentiation between gray and green and between green and orange are case-by-case, arbitrary, and inconsistent.  College Ave in metro Appleton between Casaloma Dr and County CB shows up as gray, for example.

This consistency issue could be part of the reason that Google has consolidated their colors into white, bright yellow, and dark yellow. Google also uses thicker lines to indicate more important roads, so that they appear from further zoom levels.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 07, 2017, 10:09:08 PM
Quote from: J N Winkler on December 06, 2017, 11:12:52 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AMFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

It depends on whether you use the desktop or mobile version.  Mobile doesn't show county lines (but will drop a placemark at or near the approximate centroid of the county), but desktop (even after latest revision) shows the county lines and shades the county.  I think there was some discussion upthread many pages ago about Google eliminating county lines and shading in the desktop version, but if they actually tried that, they had to retreat from it.

I've never seen county lines displayed on either the desktop version or the mobile. Closest you can get is a single county's boundary highlighted as a search result, but once the search is no longer active, the outline disappears.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 07, 2017, 11:02:10 PM
Quote from: empirestate on December 07, 2017, 10:09:08 PM
Quote from: J N Winkler on December 06, 2017, 11:12:52 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AMFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

It depends on whether you use the desktop or mobile version.  Mobile doesn't show county lines (but will drop a placemark at or near the approximate centroid of the county), but desktop (even after latest revision) shows the county lines and shades the county.  I think there was some discussion upthread many pages ago about Google eliminating county lines and shading in the desktop version, but if they actually tried that, they had to retreat from it.

I've never seen county lines displayed on either the desktop version or the mobile. Closest you can get is a single county's boundary highlighted as a search result, but once the search is no longer active, the outline disappears.

I think that's what Jonathan is getting at. Desktop will show you the outline only after searching for the county, and only from a certain zoom. But GMaps-Mobile doesn't show a damn thing, just (as JN mentions) a pin near the approximate center of the county. I'll still take the desktop implementation over nothing.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on December 08, 2017, 09:58:51 AM
On the plus side, at least they finally figured out at some point that I-587 and I-42 aren't signed yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 08, 2017, 10:34:16 AM
Quote from: jakeroot on December 07, 2017, 11:02:10 PM
Quote from: empirestate on December 07, 2017, 10:09:08 PM
Quote from: J N Winkler on December 06, 2017, 11:12:52 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AMFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

It depends on whether you use the desktop or mobile version.  Mobile doesn't show county lines (but will drop a placemark at or near the approximate centroid of the county), but desktop (even after latest revision) shows the county lines and shades the county.  I think there was some discussion upthread many pages ago about Google eliminating county lines and shading in the desktop version, but if they actually tried that, they had to retreat from it.

I've never seen county lines displayed on either the desktop version or the mobile. Closest you can get is a single county's boundary highlighted as a search result, but once the search is no longer active, the outline disappears.

I think that's what Jonathan is getting at. Desktop will show you the outline only after searching for the county, and only from a certain zoom. But GMaps-Mobile doesn't show a damn thing, just (as JN mentions) a pin near the approximate center of the county. I'll still take the desktop implementation over nothing.

There's a difference in terminology here, then. By "show", I don't mean either a dropped pin or a highlighted search result. When I say that a map shows a feature, that means you see it as you look at the map. If additional interaction is required for the feature to appear, that's not what I'd call "showing" a feature. So to me, it doesn't depend on desktop or mobile–neither version shows the feature I'm interested in.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 08, 2017, 10:59:34 AM
I know that Google Maps will show city limits and county lines if the city or county name is typed into the search bar - however, it seems like at one time somewhat recently (maybe one or two years ago), Google Maps stopped having that feature (for a brief period of time). They had done it before that, and they have done it after that (which is right now), but they temporarily were no longer doing it. I don't know why, but thankfully they must have listened to the feedback and that may be why they have brought it back for a while now. If it never went away, then I am insane, or something was wrong with my computer.  :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 08, 2017, 11:34:27 AM
Yes:  when I said upthread that Google Maps "shows" county lines, I was referring to the fact that if you search for one county in the desktop version, it will highlight just that county (not any others) and show its borders at the zoom setting it lands on.  I realize this is not the same as showing all county (and other second-tier subdivision) lines at all zoom levels, but it is also not the same as never showing those lines at all, which is what you get with the mobile version.

And as Adventurernumber1 points out, this very limited way of showing counties in the desktop version is one that Google has toyed with taking away before.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on December 08, 2017, 12:09:48 PM
Quote from: adventurernumber1 on December 08, 2017, 10:59:34 AM
I know that Google Maps will show city limits and county lines if the city or county name is typed into the search bar - however, it seems like at one time somewhat recently (maybe one or two years ago), Google Maps stopped having that feature (for a brief period of time). They had done it before that, and they have done it after that (which is right now), but they temporarily were no longer doing it. I don't know why, but thankfully they must have listened to the feedback and that may be why they have brought it back for a while now. If it never went away, then I am insane, or something was wrong with my computer.  :-D

You're not insane; it did go away a couple years back for a month at least.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 11, 2017, 12:54:18 AM
Quote from: J N Winkler on December 08, 2017, 11:34:27 AM
And as Adventurernumber1 points out, this very limited way of showing counties in the desktop version is one that Google has toyed with taking away before.

Quote from: SectorZ on December 08, 2017, 12:09:48 PM
Quote from: adventurernumber1 on December 08, 2017, 10:59:34 AM
I know that Google Maps will show city limits and county lines if the city or county name is typed into the search bar - however, it seems like at one time somewhat recently (maybe one or two years ago), Google Maps stopped having that feature (for a brief period of time). They had done it before that, and they have done it after that (which is right now), but they temporarily were no longer doing it. I don't know why, but thankfully they must have listened to the feedback and that may be why they have brought it back for a while now. If it never went away, then I am insane, or something was wrong with my computer.  :-D

You're not insane; it did go away a couple years back for a month at least.

Oh okay. I thought that they must have done so at one point and that I recalled things correctly. I'm just glad that it wasn't that way for very long it sounds like, and that they brought it back.

And as J N Winkler says, while it is definitely not as good as showing all of the county lines without having to do anything at all, at least Google Maps does outline county borders and city limits if the said city or county is searched up (though not on mobile), and it is better than nothing.

Hopefully, Google Maps may even decide to show county lines and such by default in the future. That would be incredibly nice.  :nod:
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 11, 2017, 07:55:09 AM
People have been begging for the return of county lines for years, if not a decade.  Google has resisted the calls for them and I don't see that changing.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 12, 2017, 01:41:56 AM
Quote from: empirestate on December 08, 2017, 10:34:16 AM
Quote from: jakeroot on December 07, 2017, 11:02:10 PM
Quote from: empirestate on December 07, 2017, 10:09:08 PM
Quote from: J N Winkler on December 06, 2017, 11:12:52 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AM
For me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

It depends on whether you use the desktop or mobile version.  Mobile doesn't show county lines (but will drop a placemark at or near the approximate centroid of the county), but desktop (even after latest revision) shows the county lines and shades the county.  I think there was some discussion upthread many pages ago about Google eliminating county lines and shading in the desktop version, but if they actually tried that, they had to retreat from it.

I've never seen county lines displayed on either the desktop version or the mobile. Closest you can get is a single county's boundary highlighted as a search result, but once the search is no longer active, the outline disappears.

I think that's what Jonathan is getting at. Desktop will show you the outline only after searching for the county, and only from a certain zoom. But GMaps-Mobile doesn't show a damn thing, just (as JN mentions) a pin near the approximate center of the county. I'll still take the desktop implementation over nothing.

There's a difference in terminology here, then. By "show", I don't mean either a dropped pin or a highlighted search result. When I say that a map shows a feature, that means you see it as you look at the map. If additional interaction is required for the feature to appear, that's not what I'd call "showing" a feature. So to me, it doesn't depend on desktop or mobile–neither version shows the feature I'm interested in.

Very well. Seems a bit pedantic, though. Google does show county lines, you just have to search for it. It's not like county lines are inaccessible (not anymore, at least). If everything were shown by default, the map would be a bit busy.
Title: Re: Google Maps just fucking SUCKS now
Post by: myosh_tino on December 12, 2017, 02:56:45 AM
Not wanting to veer too much off-topic but if anyone is interested in seeing how destructive the October 2017 Wine Country fires in Northern California were, Google Maps Satellite View has been updated to show the devastation.

Coffey Park Neighborhood (Santa Rosa): https://goo.gl/maps/ZoVK8EKaMoM2

Fountaingrove Neighborhood (Santa Rosa): https://goo.gl/maps/vJovtKWeRAN2

Silverado Country Club: https://goo.gl/maps/J5FUKn93fiD2

Note: You will need to turn off the 3D view to get the updated satellite images.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on December 12, 2017, 04:29:50 AM
Quote from: Roadsguy on December 08, 2017, 09:58:51 AM
On the plus side, at least they finally figured out at some point that I-587 and I-42 aren't signed yet.

On the down side, I-495 is still labeled between I-540 and I-440 despite the fact that I-495 has been decommissioned since last spring.
Title: Re: Google Maps just fucking SUCKS now
Post by: oscar on December 12, 2017, 04:49:00 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AM
For me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

The county-counting site www.mob-rule.com has a feature where you can overlay county lines on a Google map. That comes in handy for places like Alaska and Canada where online mapping of county lines is uneven or non-existent even in OpenStreetMap. But mob-rule.com is slow to catch up with the latest changes to county (equivalent) definitions, which are fortunately rare in the lower 48 (mostly renames, and independent cities in Virginia folded into their surrounding counties).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 12, 2017, 08:20:33 AM
Quote from: oscar on December 12, 2017, 04:49:00 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AM
For me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

The county-counting site www.mob-rule.com has a feature where you can overlay county lines on a Google map. That comes in handy for places like Alaska and Canada where online mapping of county lines is uneven or non-existent even in OpenStreetMap. But mob-rule.com is slow to catch up with the latest changes to county (equivalent) definitions, which are fortunately rare in the lower 48 (mostly renames, and independent cities in Virginia folded into their surrounding counties).
Is the site currently behind in any changes that have been made?
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on December 12, 2017, 09:55:02 AM
Quote from: oscar on December 12, 2017, 04:49:00 AM
The county-counting site www.mob-rule.com has a feature where you can overlay county lines on a Google map. That comes in handy for places like Alaska and Canada where online mapping of county lines is uneven or non-existent even in OpenStreetMap.
Because counties are non-existent in Alaska and much of Canada...
Title: Re: Google Maps just fucking SUCKS now
Post by: oscar on December 12, 2017, 10:57:15 AM
Quote from: Rothman on December 12, 2017, 08:20:33 AM
Quote from: oscar on December 12, 2017, 04:49:00 AM
Quote from: empirestate on December 06, 2017, 09:07:43 AM
For me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

The county-counting site www.mob-rule.com has a feature where you can overlay county lines on a Google map. That comes in handy for places like Alaska and Canada where online mapping of county lines is uneven or non-existent even in OpenStreetMap. But mob-rule.com is slow to catch up with the latest changes to county (equivalent) definitions, which are fortunately rare in the lower 48 (mostly renames, and independent cities in Virginia folded into their surrounding counties).
Is the site currently behind in any changes that have been made?

It's mostly caught up in the U.S., except for some significant boundary changes in southeastern Alaska (including at least expansion of the Ketchikan Gateway borough, creation of the Petersburg borough out of part of the former Petersburg census area, and territory added to and removed from the Prince of Wales-Hyder census area).

I just noticed that a few weeks ago mob-rule.com made major changes to its Canada county equivalent list. I'll need to give that a closer look, as I update my own Canada counts.

Quote from: NE2 on December 12, 2017, 09:55:02 AM
Because counties are non-existent in Alaska and much of Canada...
Alaska has boroughs, which are as county-like as Louisiana's parishes, though it also has a large "Unorganized Borough" that the Census Bureau and mob-rule.com split up into census areas and treat as county equivalents (some county-counters disagree, and treat the Unorganized Borough as a single unit).

Canada is more complicated, but a majority of the provinces have counties or close equivalents (such as regional county municipalities in Quebec).
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 12, 2017, 11:06:48 AM
Mob-rule.com has also significantly updated the county line overlay (was on version "g25" earlier this year, is on version "g31" now) apparently to take account of Google Maps changes and to add municipios in Mexico.  I'm a bit curious as to whether this will increase south-of-the-border travel, at least within the county-collecting community.
Title: Re: Google Maps just fucking SUCKS now
Post by: oscar on December 12, 2017, 11:15:45 AM
Quote from: J N Winkler on December 12, 2017, 11:06:48 AM
Mob-rule.com has also significantly updated the county line overlay (was on version "g25" earlier this year, is on version "g31" now) apparently to take account of Google Maps changes and to add municipios in Mexico.  I'm a bit curious as to whether this will increase south-of-the-border travel, at least within the county-collecting community.

It won't change my (minimal) Mexico travels, but will affect how I track them. Previously I counted only estados, now I need to log smaller units.

EDIT:  Just updated my mob-rule.com user page to reflect my Mexico travels. Just seven municipios in three estados.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 12, 2017, 01:48:41 PM
Quote from: oscar on December 12, 2017, 10:57:15 AM
Quote from: NE2 on December 12, 2017, 09:55:02 AM
Because counties are non-existent in Alaska and much of Canada...

Canada is more complicated, but a majority of the provinces have counties or close equivalents (such as regional county municipalities in Quebec).

Yep, southern Ontario has counties.  I know this firsthand because I once ate lunch at Chatham-Kent Fire Station #18 in the town of Blenheim, while I was on vacation in nearby Rondeau Provincial Park.  One of the firemen gave me a free hat.  They had a box full of them, because the name of the fire station had recently changed.  The name had changed because the county lines had been redrawn recently.  (Blenheim is now part of Chatham-Kent municipality, not a county.)
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 12, 2017, 03:03:00 PM
Quote from: adventurernumber1 on December 11, 2017, 12:54:18 AM
And as J N Winkler says, while it is definitely not as good as showing all of the county lines without having to do anything at all, at least Google Maps does outline county borders and city limits if the said city or county is searched up (though not on mobile), and it is better than nothing.

But that's the whole point–if you want to know, say, what counties a road goes through, how the hell can you figure that out by already knowing what counties it goes through so you can search them one by one? That's what I would be using these mapping services for, and since Google doesn't show you the names of counties that you don't already know the names of, then no, it's not better than nothing, and it's certainly not better than just using Mapquest or Bing instead.

Quote from: jakeroot on December 12, 2017, 01:41:56 AM
Quote from: empirestate on December 08, 2017, 10:34:16 AM
There's a difference in terminology here, then. By "show", I don't mean either a dropped pin or a highlighted search result. When I say that a map shows a feature, that means you see it as you look at the map. If additional interaction is required for the feature to appear, that's not what I'd call "showing" a feature. So to me, it doesn't depend on desktop or mobile–neither version shows the feature I'm interested in.

Very well. Seems a bit pedantic, though. Google does show county lines, you just have to search for it. It's not like county lines are inaccessible (not anymore, at least). If everything were shown by default, the map would be a bit busy.

Not pedantic at all–as I describe above, it's not about the difference between two definitions of a word, it's about the complete absence of a functionality. That's no more pedantic than King Arthur informing the Black Night that the stupid bastard's got no arms left.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 12, 2017, 03:13:59 PM
Quote from: empirestate on December 12, 2017, 03:03:00 PM
Quote from: adventurernumber1 on December 11, 2017, 12:54:18 AM
And as J N Winkler says, while it is definitely not as good as showing all of the county lines without having to do anything at all, at least Google Maps does outline county borders and city limits if the said city or county is searched up (though not on mobile), and it is better than nothing.

But that's the whole point–if you want to know, say, what counties a road goes through, how the hell can you figure that out by already knowing what counties it goes through so you can search them one by one? That's what I would be using these mapping services for, and since Google doesn't show you the names of counties that you don't already know the names of, then no, it's not better than nothing, and it's certainly not better than just using Mapquest or Bing instead.

Quote from: jakeroot on December 12, 2017, 01:41:56 AM
Quote from: empirestate on December 08, 2017, 10:34:16 AM
There's a difference in terminology here, then. By "show", I don't mean either a dropped pin or a highlighted search result. When I say that a map shows a feature, that means you see it as you look at the map. If additional interaction is required for the feature to appear, that's not what I'd call "showing" a feature. So to me, it doesn't depend on desktop or mobile–neither version shows the feature I'm interested in.

Very well. Seems a bit pedantic, though. Google does show county lines, you just have to search for it. It's not like county lines are inaccessible (not anymore, at least). If everything were shown by default, the map would be a bit busy.

Not pedantic at all–as I describe above, it's not about the difference between two definitions of a word, it's about the complete absence of a functionality. That's no more pedantic than King Arthur informing the Black Night that the stupid bastard's got no arms left.

Exactly.

I can search in Google Maps for "Texas County Oklahoma" and it displays the boundaries.  But now suppose I want to know what county is to the west of there.  Can't tell!
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 12, 2017, 03:30:18 PM
Quote from: empirestate on December 12, 2017, 03:03:00 PM
Not pedantic at all–as I describe above, it's not about the difference between two definitions of a word, it's about the complete absence of a functionality. That's no more pedantic than King Arthur informing the Black Night that the stupid bastard's got no arms left.

Sure he does. They're right there on the ground. It's not like they're someone else's now.  :spin:
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 12, 2017, 03:34:17 PM
Quote from: empirestate on December 12, 2017, 03:03:00 PMBut that's the whole point–if you want to know, say, what counties a road goes through, how the hell can you figure that out by already knowing what counties it goes through so you can search them one by one? That's what I would be using these mapping services for, and since Google doesn't show you the names of counties that you don't already know the names of, then no, it's not better than nothing, and it's certainly not better than just using Mapquest or Bing instead.

Showing all counties a road passes through is not an application Google Maps supports.  However, it is useful for confirming whether a road passes through a particular county.  In cases where the road in question just barely clips the county (or misses doing so), it can actually be more useful for this purpose than much static mapping.

"Shows" is a bit slippery with dynamic mapping in general, because it depends partly on map state.  If I zoom onto a particular county so tightly that its borders are well off my screen, is the map "showing" county lines?  If the map has selectable layers and the county line layer is turned on, are county lines being "shown"?  Does it matter whether the map loads with that layer on by default?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 12, 2017, 03:48:54 PM
Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
If I zoom onto a particular county so tightly that its borders are well off my screen, is the map "showing" county lines?

If you scroll far enough to one direction, does the county line that exists there show up on your map?  If so, then yes.  If not, then no.

Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
If the map has selectable layers and the county line layer is turned on, are county lines being "shown"?  Does it matter whether the map loads with that layer on by default?

That should count, as long as they don't disappear at close zoom levels.




Basically, a user should be able to (not necessarily by default) see county lines on the map, until such point as he is zoomed out enough that they would cause clutter.  And, regarding shading and boundaries as they are now, it's insane to me that a layer be eliminated when zooming in.  That seems backwards.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on December 12, 2017, 03:50:42 PM
Quote from: kphoger on December 12, 2017, 03:48:54 PM
Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
If I zoom onto a particular county so tightly that its borders are well off my screen, is the map "showing" county lines?

If you scroll far enough to one direction, does the county line that exists there show up on your map?  If so, then yes.  If not, then no.

Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
If the map has selectable layers and the county line layer is turned on, are county lines being "shown"?  Does it matter whether the map loads with that layer on by default?

That should count, as long as they don't disappear at close zoom levels.




Basically, a user should be able to (not necessarily by default) see county lines on the map, until such point as he is zoomed out enough that they would cause clutter.  And, regarding shading and boundaries as they are now, it's insane to me that a layer be eliminated when zooming in.  That seems backwards.

Some programmer probably put < when they meant to put >.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 12, 2017, 04:01:14 PM
I don't think there is any real disagreement as to what Google Maps does in the desktop version:  it exposes a boundary and shading for one county at the landing zoom level only when that specific county is searched for.

My concern about saying that desktop Google Maps, with this behavior, "does not show county lines," is that it raises the question of how we are to describe the possible withdrawal of this useful functionality.  This is not an idle concern since Google has experimented with such a move in the past.  "Does not show county lines" is easily interpreted as meaning "Does not show county lines at all, in any context," and if "does not show county lines" is equally true before and after loss of county border search, then how can one say anything has changed at all?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 12, 2017, 04:24:23 PM
Imagine Google Maps without town name labels on the base map.  (Actually, I remember when it was like this for smaller towns in foreign countries; you could tell where a town was by the nest of streets and the darker shading, but there was no label.)  But, oh, the town name would suddenly appear if you searched for it by name–but you had to already know that it was possible to do so.

County lines don't exist on Google Maps in the same way state lines do.  If you search for "Kansas", you get a pink shaded area bounded by a red line–same as if you search for "Thomas County Kansas."  But state lines still exist on the map and are labeled as you zoom in.  County lines are not labeled at any zoom level.  Search for "Thomas County Kansas" and you have no idea what's on the other side of that line.  To my thinking, that's not a county line, it's just a polygon boundary.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 12, 2017, 05:04:39 PM
Quote from: empirestate on December 12, 2017, 03:03:00 PM
Quote from: adventurernumber1 on December 11, 2017, 12:54:18 AM
And as J N Winkler says, while it is definitely not as good as showing all of the county lines without having to do anything at all, at least Google Maps does outline county borders and city limits if the said city or county is searched up (though not on mobile), and it is better than nothing.

But that's the whole point–if you want to know, say, what counties a road goes through, how the hell can you figure that out by already knowing what counties it goes through so you can search them one by one? That's what I would be using these mapping services for, and since Google doesn't show you the names of counties that you don't already know the names of, then no, it's not better than nothing, and it's certainly not better than just using Mapquest or Bing instead.

Quote from: kphoger on December 12, 2017, 04:24:23 PM
Imagine Google Maps without town name labels on the base map.  (Actually, I remember when it was like this for smaller towns in foreign countries; you could tell where a town was by the nest of streets and the darker shading, but there was no label.)  But, oh, the town name would suddenly appear if you searched for it by name–but you had to already know that it was possible to do so.

County lines don't exist on Google Maps in the same way state lines do.  If you search for "Kansas", you get a pink shaded area bounded by a red line–same as if you search for "Thomas County Kansas."  But state lines still exist on the map and are labeled as you zoom in.  County lines are not labeled at any zoom level.  Search for "Thomas County Kansas" and you have no idea what's on the other side of that line.  To my thinking, that's not a county line, it's just a polygon boundary.

Those are some very good points. That's very true that this limited feature on Google Maps isn't even useful at all if you're in a situation where you don't know any of the counties in a certain area, but that's exactly the information that you are trying to find.

I think it would be wonderful if Google Maps decided to add county lines that you didn't have to do any work to see (except zoom in a little more if you are really zoomed out), and that these lines had the names of both bordering counties, each on their respective side, similar to the state line set-ups that currently exist on Google Maps. Though, I would definitely make these county lines less distinctive and bold as the state lines (since they are less important and significant) - the same way as country/national borders are significantly more bolded and noticeable than state and province lines - though they should definitely still exist!  :nod:

Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on December 12, 2017, 06:50:23 PM
I'd like it if it was a layer you could turn on.  I think it would tend to get too cluttered if it was on all the time, and isn't really necessary for typical navigation.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 12, 2017, 08:30:23 PM
Quote from: kkt on December 12, 2017, 06:50:23 PM
I'd like it if it was a layer you could turn on.  I think it would tend to get too cluttered if it was on all the time, and isn't really necessary for typical navigation.

That would work, as would the ability to search "county" and have the closest county automatically pop up. So if I was hovering over Seattle and typed "county", it would zoom out and automatically highlight King County (and also show county building search results).
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 12, 2017, 08:40:07 PM
Quote from: jakeroot on December 12, 2017, 08:30:23 PM
Quote from: kkt on December 12, 2017, 06:50:23 PM
I'd like it if it was a layer you could turn on.  I think it would tend to get too cluttered if it was on all the time, and isn't really necessary for typical navigation.

That would work, as would the ability to search "county" and have the closest county automatically pop up. So if I was hovering over Seattle and typed "county", it would zoom out and automatically highlight King County (and also show county building search results).

That would be nowhere near obvious for someone who doesn't already know that it exists (if this were to exist).
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 13, 2017, 12:21:06 AM
I've found another issue with the new Google Maps updates. I am pretty certain that at one time not too long ago, Universities and colleges and their campuses were easily seen and stood out - less recently, the coloring was typically brown (I think) - more recently, it became less distinguishable, but I believe it was still a reasonable darker shade of grey, IIRC. Now, there is nothing at all, from what I can tell. Now, I cannot see the boundaries and limits and size of the campuses of colleges and universities. This is a little bit annoying, and it is just another ingredient in the boiling pot that has been cooking up in the latest updates on Google Maps. Hopefully, they will fix this, too...but they probably won't..  :-/  :no:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 13, 2017, 12:29:58 AM
Quote from: 1 on December 12, 2017, 08:40:07 PM
Quote from: jakeroot on December 12, 2017, 08:30:23 PM
Quote from: kkt on December 12, 2017, 06:50:23 PM
I'd like it if it was a layer you could turn on.  I think it would tend to get too cluttered if it was on all the time, and isn't really necessary for typical navigation.

That would work, as would the ability to search "county" and have the closest county automatically pop up. So if I was hovering over Seattle and typed "county", it would zoom out and automatically highlight King County (and also show county building search results).

That would be nowhere near obvious for someone who doesn't already know that it exists (if this were to exist).

It would be an improvement to a feature that already exists (although a layer would indeed be more obvious and preferable): I can presently hover over just about any city, type in "county", examine the search results, and type in the relevant county to see the outline.

For example, zooming in on Oakhurst, CA, if I type in "county", I get several results for "Madera County...". So, I type in Madera County into the search bar, and I get the highlight. I would just rather I had the ability to type in "county", and have it automatically zoom out to show me the county outline of whatever county I was hovering overhead, plus any results containing "county". Although I could see this being problematic for geographically large counties with many county buildings.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 13, 2017, 02:06:26 AM
Quote from: jakeroot on December 13, 2017, 12:29:58 AM
Quote from: 1 on December 12, 2017, 08:40:07 PM
Quote from: jakeroot on December 12, 2017, 08:30:23 PM
Quote from: kkt on December 12, 2017, 06:50:23 PM
I'd like it if it was a layer you could turn on.  I think it would tend to get too cluttered if it was on all the time, and isn't really necessary for typical navigation.

That would work, as would the ability to search "county" and have the closest county automatically pop up. So if I was hovering over Seattle and typed "county", it would zoom out and automatically highlight King County (and also show county building search results).

That would be nowhere near obvious for someone who doesn't already know that it exists (if this were to exist).

It would be an improvement to a feature that already exists (although a layer would indeed be more obvious and preferable): I can presently hover over just about any city, type in "county", examine the search results, and type in the relevant county to see the outline.

For example, zooming in on Oakhurst, CA, if I type in "county", I get several results for "Madera County...". So, I type in Madera County into the search bar, and I get the highlight. I would just rather I had the ability to type in "county", and have it automatically zoom out to show me the county outline of whatever county I was hovering overhead, plus any results containing "county". Although I could see this being problematic for geographically large counties with many county buildings.
I like these ideas but another would be to double tap the screen to show the boundary of current city/county.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 13, 2017, 02:23:05 AM
Quote from: Hurricane Rex on December 13, 2017, 02:06:26 AM
Quote from: jakeroot on December 13, 2017, 12:29:58 AM
Quote from: 1 on December 12, 2017, 08:40:07 PM
Quote from: jakeroot on December 12, 2017, 08:30:23 PM
Quote from: kkt on December 12, 2017, 06:50:23 PM
I'd like it if it was a layer you could turn on.  I think it would tend to get too cluttered if it was on all the time, and isn't really necessary for typical navigation.

That would work, as would the ability to search "county" and have the closest county automatically pop up. So if I was hovering over Seattle and typed "county", it would zoom out and automatically highlight King County (and also show county building search results).

That would be nowhere near obvious for someone who doesn't already know that it exists (if this were to exist).

It would be an improvement to a feature that already exists (although a layer would indeed be more obvious and preferable): I can presently hover over just about any city, type in "county", examine the search results, and type in the relevant county to see the outline.

For example, zooming in on Oakhurst, CA, if I type in "county", I get several results for "Madera County...". So, I type in Madera County into the search bar, and I get the highlight. I would just rather I had the ability to type in "county", and have it automatically zoom out to show me the county outline of whatever county I was hovering overhead, plus any results containing "county". Although I could see this being problematic for geographically large counties with many county buildings.

I like these ideas but another would be to double tap the screen to show the boundary of current city/county.

I don't think that specific move would work. Right now, double-tapping zooms in, and double-tap-and-hold allows you to zoom in or out by moving your finger up or down the screen. This makes zooming in/out possible with one-finger.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on December 13, 2017, 01:39:44 PM
Quote from: adventurernumber1 on December 13, 2017, 12:21:06 AM
I've found another issue with the new Google Maps updates. I am pretty certain that at one time not too long ago, Universities and colleges and their campuses were easily seen and stood out - less recently, the coloring was typically brown (I think) - more recently, it became less distinguishable, but I believe it was still a reasonable darker shade of grey, IIRC. Now, there is nothing at all, from what I can tell. Now, I cannot see the boundaries and limits and size of the campuses of colleges and universities. This is a little bit annoying, and it is just another ingredient in the boiling pot that has been cooking up in the latest updates on Google Maps. Hopefully, they will fix this, too...but they probably won't..  :-/  :no:


I still see a very, very tiny color difference, but it looks like it's only visible at zoom level 13 or closer (and even then you may have to squint). The university campuses are an almost imperceptibly darker shade of light gray.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 13, 2017, 11:47:59 PM
Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
"Shows" is a bit slippery with dynamic mapping in general, because it depends partly on map state.  If I zoom onto a particular county so tightly that its borders are well off my screen, is the map "showing" county lines?  If the map has selectable layers and the county line layer is turned on, are county lines being "shown"?  Does it matter whether the map loads with that layer on by default?

Yes; either of those instances would solve my complaint. For your first point, USGS topographic quads show county lines, and that's true even when I'm looking at a quad that falls entirely within one county. For your second, if I can turn on a layer and show county lines, then they're shown, and my problem is solved. It may not be solved in the most convenient way, but it's progress.

Quote from: J N Winkler on December 12, 2017, 04:01:14 PM
I don't think there is any real disagreement as to what Google Maps does in the desktop version:  it exposes a boundary and shading for one county at the landing zoom level only when that specific county is searched for.

My concern about saying that desktop Google Maps, with this behavior, "does not show county lines," is that it raises the question of how we are to describe the possible withdrawal of this useful functionality.  This is not an idle concern since Google has experimented with such a move in the past.  "Does not show county lines" is easily interpreted as meaning "Does not show county lines at all, in any context," and if "does not show county lines" is equally true before and after loss of county border search, then how can one say anything has changed at all?

I'm not sure what the dispute is, at this point. It seems like you're trying to rebut something I said, but what you write doesn't achieve that purpose. I said:

QuoteFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

You replied with something beginning "It depends..."–but it doesn't depend. If I want to use an online mapping service that displays county lines, I have to use something other than Google. The functionality of highlighting a county if, and only if, it's searched for doesn't change that. What I wrote still stands as true; and furthermore, I'm at a loss as to how it's controversial.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 14, 2017, 12:39:02 AM
Quote from: empirestate on December 13, 2017, 11:47:59 PM
Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
"Shows" is a bit slippery with dynamic mapping in general, because it depends partly on map state.  If I zoom onto a particular county so tightly that its borders are well off my screen, is the map "showing" county lines?  If the map has selectable layers and the county line layer is turned on, are county lines being "shown"?  Does it matter whether the map loads with that layer on by default?

Yes; either of those instances would solve my complaint. For your first point, USGS topographic quads show county lines, and that's true even when I'm looking at a quad that falls entirely within one county. For your second, if I can turn on a layer and show county lines, then they're shown, and my problem is solved. It may not be solved in the most convenient way, but it's progress.

Quote from: J N Winkler on December 12, 2017, 04:01:14 PM
I don't think there is any real disagreement as to what Google Maps does in the desktop version:  it exposes a boundary and shading for one county at the landing zoom level only when that specific county is searched for.

My concern about saying that desktop Google Maps, with this behavior, "does not show county lines," is that it raises the question of how we are to describe the possible withdrawal of this useful functionality.  This is not an idle concern since Google has experimented with such a move in the past.  "Does not show county lines" is easily interpreted as meaning "Does not show county lines at all, in any context," and if "does not show county lines" is equally true before and after loss of county border search, then how can one say anything has changed at all?

I'm not sure what the dispute is, at this point. It seems like you're trying to rebut something I said, but what you write doesn't achieve that purpose. I said:

QuoteFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

You replied with something beginning "It depends..."–but it doesn't depend. If I want to use an online mapping service that displays county lines, I have to use something other than Google. The functionality of highlighting a county if, and only if, it's searched for doesn't change that. What I wrote still stands as true; and furthermore, I'm at a loss as to how it's controversial.

Empire, (although I know you said you weren't) you are being outrageously pedantic regarding the meaning of "show". Google's implementation of counties is far from traditional, but if you can show a county by searching for said county, then the feature exists. "Show" means "allow to be visible". Searching for a county allows it to be visible. Google shows counties. It's that simple.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 11:15:39 AM
For what it's worth...  If you want to still see the yellow/orange distinction for freeways, it's still there on the My Maps side of Google.  You have to have a Google account in order to log in to that, of course, and there is no street view or directions capability.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 11:18:24 AM
Quote from: jakeroot on December 14, 2017, 12:39:02 AM
Quote from: empirestate on December 13, 2017, 11:47:59 PM
Quote from: J N Winkler on December 12, 2017, 03:34:17 PM
"Shows" is a bit slippery with dynamic mapping in general, because it depends partly on map state.  If I zoom onto a particular county so tightly that its borders are well off my screen, is the map "showing" county lines?  If the map has selectable layers and the county line layer is turned on, are county lines being "shown"?  Does it matter whether the map loads with that layer on by default?

Yes; either of those instances would solve my complaint. For your first point, USGS topographic quads show county lines, and that's true even when I'm looking at a quad that falls entirely within one county. For your second, if I can turn on a layer and show county lines, then they're shown, and my problem is solved. It may not be solved in the most convenient way, but it's progress.

Quote from: J N Winkler on December 12, 2017, 04:01:14 PM
I don't think there is any real disagreement as to what Google Maps does in the desktop version:  it exposes a boundary and shading for one county at the landing zoom level only when that specific county is searched for.

My concern about saying that desktop Google Maps, with this behavior, "does not show county lines," is that it raises the question of how we are to describe the possible withdrawal of this useful functionality.  This is not an idle concern since Google has experimented with such a move in the past.  "Does not show county lines" is easily interpreted as meaning "Does not show county lines at all, in any context," and if "does not show county lines" is equally true before and after loss of county border search, then how can one say anything has changed at all?

I'm not sure what the dispute is, at this point. It seems like you're trying to rebut something I said, but what you write doesn't achieve that purpose. I said:

QuoteFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

You replied with something beginning "It depends..."–but it doesn't depend. If I want to use an online mapping service that displays county lines, I have to use something other than Google. The functionality of highlighting a county if, and only if, it's searched for doesn't change that. What I wrote still stands as true; and furthermore, I'm at a loss as to how it's controversial.

Empire, (although I know you said you weren't) you are being outrageously pedantic regarding the meaning of "show". Google's implementation of counties is far from traditional, but if you can show a county by searching for said county, then the feature exists. "Show" means "allow to be visible". Searching for a county allows it to be visible. Google shows counties. It's that simple.

Well....  you can only show one county's lines at a time.  AFAIK, it is impossible to see the all the county lines of the Oklahoma panhandle in one view.  This used to be possible years ago, by showing multiple searched locations, but that went away some time ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 14, 2017, 11:24:24 AM
Quote from: empirestate on December 13, 2017, 11:47:59 PMI'm not sure what the dispute is, at this point. It seems like you're trying to rebut something I said, but what you write doesn't achieve that purpose. I said:

QuoteFor me, it's been necessary for a long time to use multiple mapping services, if for no other reason than that Google doesn't show county lines.

You replied with something beginning "It depends..."–but it doesn't depend. If I want to use an online mapping service that displays county lines, I have to use something other than Google. The functionality of highlighting a county if, and only if, it's searched for doesn't change that. What I wrote still stands as true; and furthermore, I'm at a loss as to how it's controversial.

The issue here is that "doesn't show county lines" can easily be understood to mean "cannot be made to show the boundary of any county in any context," which is not true given the existence of county border search.  It seemed to me proper to point out that county border search does currently exist on Google Maps desktop, especially given Google's flirtation with withdrawing it in the past.  I wasn't setting out to make a rebuttal since you had indicated this way of displaying counties was not adequate for your purposes.  Since I do not know what these are precisely, it would be presumptuous for me to argue that Google Maps should be enough for them.

FWIW, I occasionally use Google Maps to check whether a particular road is within a particular county, but when I need something that displays all county lines, I use the Mob-Rule.com overlay.  It is an on-the-fly decision that depends partly on convenience and partly on the amount of memory I have already lost due to memory leaks.  I have a browser search plugin for Google Maps, but not for any other mapping services; meanwhile, the Mob-Rule.com overlay loads noticeably more slowly for me than straight Google Maps and is more likely to push the browser into a crash, especially when the underlying Windows session has gone stale (memory usage of > 6.5 GB out of 8 GB with no applications running versus 2.7 GB immediately after boot and initial login).
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 11:58:58 AM
Quote from: J N Winkler on December 14, 2017, 11:24:24 AM
Quote from: empirestate on December 13, 2017, 11:47:59 PM


you had indicated this way of displaying counties was not adequate for your purposes.  Since I do not know what these are precisely, it would be presumptuous for me to argue that Google Maps should be enough for them.

Someone had to point it out, so I guess it might as well be me...

Quote from: empirestate on December 12, 2017, 03:03:00 PM
if you want to know, say, what counties a road goes through, how the hell can you figure that out by already knowing what counties it goes through so you can search them one by one? That's what I would be using these mapping services for

Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 12:00:32 PM
Quote from: J N Winkler on December 14, 2017, 11:24:24 AM
the Mob-Rule.com overlay

Thank you for directing me to this!
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 14, 2017, 12:32:13 PM
Quote from: kphoger on December 14, 2017, 11:58:58 AM
Quote from: J N Winkler on December 14, 2017, 11:24:24 AM
. . . You had indicated this way of displaying counties was not adequate for your purposes.  Since I do not know what these are precisely, it would be presumptuous for me to argue that Google Maps should be enough for them.

Someone had to point it out, so I guess it might as well be me...

Quote from: empirestate on December 12, 2017, 03:03:00 PM
. . . if you want to know, say, what counties a road goes through, how the hell can you figure that out by already knowing what counties it goes through so you can search them one by one? That's what I would be using these mapping services for . . .

This discussion started on December 6 (two thread pages ago) and Empirestate's comment (quoted above) about his application was made on December 12.  It still does not entitle me to presume that I have a complete understanding of how he uses county lines.

Looking back at the preceding discussion, I see that in my original post I failed to specify that Google Maps' display of county lines and shading is for one county and only in the context of a search for that specific county.  In light of the subsequent conversation, this was a qualification I should have made clear at the outset (not leaving it to user 1's post immediately following mine), and I apologize for failing to do so.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 14, 2017, 12:47:59 PM
Quote from: kphoger on December 14, 2017, 12:00:32 PM
Quote from: J N Winkler on December 14, 2017, 11:24:24 AMthe Mob-Rule.com overlay

Thank you for directing me to this!

You are welcome.

In the meantime, I've discovered the Nominatim plugin for OSM and have been playing with it.  The main issue I see is that there are two layers of click-through to get to OSM with the searched-for feature appropriately highlighted.

Searching for my home address (search term specific as to house number, street, Wichita, KS, but no ZIP) --> results page, click on appropriate result (apparently there is a street with the same name in Wichita Falls, Texas) --> OSM profile page for the feature, click on OSM link --> feature (in this case, the entirety of the street, not my specific house) is highlighted.

Searching for my home county (search term {Sedgwick County, KS})--> results page, click on appropriate result (choose from among Sedgwick County, Colorado; Sedgwick, Sedgwick County, Colorado; Historic Sedgwick County Courthouse at 510 N. Main in Wichita; etc.) --> OSM profile page for the feature, click on OSM link --> feature (in this case, only Sedgwick County is highlighted or has borders shown at the landing zoom level; none of the surrounding counties have lines displayed).

In light of the discussion we've had about the hermeneutics of "show," it's worth pointing out that OSM displays county lines and county labels only at certain zoom ranges.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 01:26:42 PM
Quote from: J N Winkler on December 14, 2017, 12:47:59 PM
In light of the discussion we've had about the hermeneutics of "show," it's worth pointing out that OSM displays county lines and county labels only at certain zoom ranges.

As it should.  Not everything should be visible at all zoom levels.  And this is how paper maps work too.

As for the hermeneutics of "show"... imagine if state boundaries didn't show up except when you searched for a specific state, and then the shading/boundaries disappeared at a certain zoom level.  There would be thousands of people complaining that Google doesn't show state lines, and their complaint would be legitimate.  Now, that doesn't mean all available boundaries should always be shown.  After all, you can also search Google Maps for ZIP codes, neighborhoods, and towns and get similar shading–but showing all of those on the base map at once would be insanity.  What we're all saying is that, when you open Google Maps in your browser window, there should be county lines visible to you on the map that first comes up (by default or by selecting an overlay).

I actually think it would be awesome to have each of these types of boundaries available as an on/off overlay.  Sometimes it's useful to see a map with no political boundaries, and sometimes only one or two types of political boundaries.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on December 14, 2017, 02:28:20 PM
There are other maps that do show all county lines.  Google Maps doesn't have to try to be all things to all people.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 02:42:33 PM
Quote from: kkt on December 14, 2017, 02:28:20 PM
There are other maps that do show all county lines.  Google Maps doesn't have to try to be all things to all people.

While this is true, I find no other online map to be nearly as useful as Google Maps.  But, for the specific purposes mentioned so far on here, they would suffice.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on December 14, 2017, 02:44:33 PM
I have now sent 6 edit requests since November 29th for the same thing, and it has not been looked at.  Meanwhile, some other things that I send requests about, including adding a small road that wasn't on the map, was added the next day.  The change has to do with CT 31.  The portion south of US 44 is labeled correctly and the road is listed as "Connecticut 31".  However, the part concurrent with and north of US 44 is labeled incorrectly with a county route shield, and the road is listed as "State Hwy 31".  Just want them to combine the two and apply the correct labeling, and they haven't. 
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on December 14, 2017, 03:16:08 PM
Quote from: kkt on December 14, 2017, 02:28:20 PM
There are other maps that do show all county lines.  Google Maps doesn't have to try to be all things to all people.

For example, Bing Maps has county lines shown.  And in some regards, they're better than Google.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 14, 2017, 03:31:42 PM
Quote from: Brandon on December 14, 2017, 03:16:08 PM
Quote from: kkt on December 14, 2017, 02:28:20 PM
There are other maps that do show all county lines.  Google Maps doesn't have to try to be all things to all people.

For example, Bing Maps has county lines shown.  And in some regards, they're better than Google.

Bing Maps' implementation of counties is rather impressive. The lines are shown only at closer zoom levels (to prevent busyness when zoomed out), plus the Locate Me tab (on the right) automatically changes when you scroll around to show you which county you're hovering over, plus the city if you're hovering over that.

I assume Bing Maps' implementation would fit empirestate's definition of "show". ;-)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 14, 2017, 03:33:59 PM
Quote from: Brandon on December 14, 2017, 03:16:08 PM
For example, Bing Maps has county lines shown.

Shown, yes.  Labeled, no.  But, as jakeroot has mentioned, it's still kind of usable.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 16, 2017, 12:39:48 AM
Quote from: jakeroot on December 14, 2017, 03:31:42 PM
Quote from: Brandon on December 14, 2017, 03:16:08 PM
Quote from: kkt on December 14, 2017, 02:28:20 PM
There are other maps that do show all county lines.  Google Maps doesn't have to try to be all things to all people.

For example, Bing Maps has county lines shown.  And in some regards, they're better than Google.

Bing Maps' implementation of counties is rather impressive. The lines are shown only at closer zoom levels (to prevent busyness when zoomed out), plus the Locate Me tab (on the right) automatically changes when you scroll around to show you which county you're hovering over, plus the city if you're hovering over that.


Wow! That is actually really cool. I had no idea that Bing Maps did that, so I am going to have to give that a look when I get the chance.  :nod:


Quote from: kphoger on December 14, 2017, 02:42:33 PM
Quote from: kkt on December 14, 2017, 02:28:20 PM
There are other maps that do show all county lines.  Google Maps doesn't have to try to be all things to all people.

While this is true, I find no other online map to be nearly as useful as Google Maps.  But, for the specific purposes mentioned so far on here, they would suffice.

These are some good points, but I would like to see Google Maps be a little more useful when it comes to county lines and such, because it has such a pivotal status when it comes to online mapping, and at least before many of these bad updates in recent times (hence the creation of this thread in the first place), it has been highly admired, enjoyed, loved, and used by many, including myself. I think that if Google Maps could at least give you the option to turn on county lines at reasonable zoom levels, that would be an excellent decision. I would love it if they at least did that, as others have said.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 18, 2017, 04:29:52 PM
Quote from: jakeroot on December 14, 2017, 12:39:02 AM
Empire, (although I know you said you weren't) you are being outrageously pedantic regarding the meaning of "show". Google's implementation of counties is far from traditional, but if you can show a county by searching for said county, then the feature exists. "Show" means "allow to be visible". Searching for a county allows it to be visible. Google shows counties. It's that simple.

OH! Oh, oh, oh, oh!!!! Now I finally see what the problem is. :-D

Yes, you're absolutely right that being excessively pedantic about the meaning of "shows" is the problem here–but it was actually Mr. Winkler who was making that distinction, not me. I mentioned a functionality that Google doesn't have, and it was he who responded by saying that it depends on my definition of "shows". My point actually does not depend on that, for the very reason that I was not being so pedantic about the definition–I simply was not being as precise with my use of the term as Mr. Winkler was, as he explains and clarifies below.

(I hasten to point out that that's not a criticism of Mr. Winkler, merely identifying the source of our confusion. Indeed, I have always admired the comprehensiveness and precision of his comments in this forum.)

Quote from: J N Winkler on December 14, 2017, 11:24:24 AM
The issue here is that "doesn't show county lines" can easily be understood to mean "cannot be made to show the boundary of any county in any context," which is not true given the existence of county border search.  It seemed to me proper to point out that county border search does currently exist on Google Maps desktop, especially given Google's flirtation with withdrawing it in the past.  I wasn't setting out to make a rebuttal since you had indicated this way of displaying counties was not adequate for your purposes.  Since I do not know what these are precisely, it would be presumptuous for me to argue that Google Maps should be enough for them.

Absolutely; Google does indeed have the feature you describe, and it is informative to point it out. This misunderstanding arose by saying that my need to use other mapping services "depends on" what I mean by "shows"–it does not. I have that need regardless of what the word means (and regardless of whether Google has the functionality you mentioned.)

(jakeroot, you might be able to say I'm being overly pedantic about the meaning of "depends on"–I'm certainly capable of excessive pedantry when I'm so inclined, and so I certainly wouldn't deny it; it just doesn't happen to be the case with my use of "shows".)

Quote from: kphoger on December 14, 2017, 03:33:59 PM
Quote from: Brandon on December 14, 2017, 03:16:08 PM
For example, Bing Maps has county lines shown.

Shown, yes.  Labeled, no.  But, as jakeroot has mentioned, it's still kind of usable.

Yes, I have noticed that they're no longer labeled, which makes them less useful than previously.

Quote from: jakeroot on December 14, 2017, 03:31:42 PM
I assume Bing Maps' implementation would fit empirestate's definition of "show". ;-)

It is one of the "other services" I had in mind. But as to whether that meets a specific definition, you'll have to let me know that, as I didn't have any particular definition in mind over another. ;-)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 18, 2017, 04:50:32 PM
Quote from: empirestate on December 18, 2017, 04:29:52 PM
This misunderstanding arose by saying that my need to use other mapping services "depends on" what I mean by "shows"–it does not. I have that need regardless of what the word means (and regardless of whether Google has the functionality you mentioned.)

This!

I don't care what "shows" means and doesn't mean when it comes to layers and capabilities.  The fact of the matter is that Google Maps doesn't display counties in a way that is useful for any purpose other than researching them one-by-one.  Counties are hidden on Google Maps, and they cannot be un-hidden except individually, and even then only up to a certain zoom level–the latter actually eliminating the usefulness of it from any in-depth study.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 18, 2017, 05:20:52 PM
Quote from: empirestate on December 18, 2017, 04:29:52 PM
(jakeroot, you might be able to say I'm being overly pedantic about the meaning of "depends on"–I'm certainly capable of excessive pedantry when I'm so inclined, and so I certainly wouldn't deny it; it just doesn't happen to be the case with my use of "shows".)

I've noticed. You and Mr Winkler are much more skilled at writing and comprehension, so I sometimes get quickly confused, and/or misconstrue a comment by taking it out of context, and making an arse of myself. Nothing wrong with what you're doing, I'm just not good at following along.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 20, 2017, 08:46:30 PM
Anyone notice that Google seems to be routing over more non-freeways as of the last update?

Also, these issues may well be because of self-driving cars.  Who needs to differentiate freeways when the car will do the navigating? (said no roadgeek ever)
https://www.simpartners.com/google-maps-might-be-preparing-us-for-a-driverless-future/
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on December 21, 2017, 12:40:39 AM
I dunno... self-driving cars are still a long way away.  I think there are other reasons.  Probably non-roadgeeks don't care so much what type of road it is, they care how fast the traffic on it is.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 21, 2017, 04:15:37 AM
For the last few years, Google has had the fishhook section of the Newberg Dundeee bypass as a road but under road closed if you are in traffic mode only, its due to open on January 6th so it will be accirated about that then.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on December 21, 2017, 02:25:14 PM
Quote from: vdeane on December 20, 2017, 08:46:30 PM
Anyone notice that Google seems to be routing over more non-freeways as of the last update?

Also, these issues may well be because of self-driving cars.  Who needs to differentiate freeways when the car will do the navigating? (said no roadgeek ever)
https://www.simpartners.com/google-maps-might-be-preparing-us-for-a-driverless-future/

Indeed.  Just playing around, I requested a route from Fort Worth to Edmonton.

https://www.google.com/maps/dir/32.8029309,-97.3084119/53.5268903,-113.4050132/@47.1329948,-106.6690695,5z?hl=en (https://www.google.com/maps/dir/32.8029309,-97.3084119/53.5268903,-113.4050132/@47.1329948,-106.6690695,5z?hl=en)

"Non-freeways" doesn't quite cover where Google wants me to go, which includes a stretch of gravel road in the middle of nowhere in South Dakota.

https://www.google.com/maps/@42.9016299,-98.2889044,3a,75y,3.97h,90t/data=!3m6!1e1!3m4!1sTL68j24bqTZj1YvfYqZtxQ!2e0!7i3328!8i1664!5m1!1e4?hl=en (https://www.google.com/maps/@42.9016299,-98.2889044,3a,75y,3.97h,90t/data=!3m6!1e1!3m4!1sTL68j24bqTZj1YvfYqZtxQ!2e0!7i3328!8i1664!5m1!1e4?hl=en)

I doubt if many people think that saving 10 minutes on a 2,000 mile drive is worth the sense of uncertainty and actual risk of driving up an escarpment on an isolated unpaved road like that.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 21, 2017, 02:33:31 PM
Google made this mistake a few years back, when their preferred route going from points north of DC to points south of DC was -- I kid you not -- Taking US 50 down Rhode Island Ave and then down I-395.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 21, 2017, 02:59:12 PM
Quote from: wxfree on December 21, 2017, 02:25:14 PM"Non-freeways" doesn't quite cover where Google wants me to go, which includes a stretch of gravel road in the middle of nowhere in South Dakota.

https://www.google.com/maps/@42.9016299,-98.2889044,3a,75y,3.97h,90t/data=!3m6!1e1!3m4!1sTL68j24bqTZj1YvfYqZtxQ!2e0!7i3328!8i1664!5m1!1e4?hl=en (https://www.google.com/maps/@42.9016299,-98.2889044,3a,75y,3.97h,90t/data=!3m6!1e1!3m4!1sTL68j24bqTZj1YvfYqZtxQ!2e0!7i3328!8i1664!5m1!1e4?hl=en)

I doubt if many people think that saving 10 minutes on a 2,000 mile drive is worth the sense of uncertainty and actual risk of driving up an escarpment on an isolated unpaved road like that.

Another anomaly I noticed in casual exploration--Google Maps suggests a minimum-length route that is three miles longer than a plausible route with approximately the same amount of travel on unpaved roads.  This is the initial result for a Google Maps desktop search on {Wichita, KS to Castle Rock, Gove County, KS} using the Firefox search plugin:

https://www.google.com/maps/dir/Wichita,+KS/Castle+Rock,+Larrabee,+KS+67752/@38.4490808,-99.2696349,8.5z/data=!4m14!4m13!1m5!1m1!1s0x87badb6ad27f182d:0x9396d5bf74d33d3e!2m2!1d-97.330053!2d37.6871761!1m5!1m1!1s0x87a0f609f8ed05af:0x3c7b9bb17dfb6e1!2m2!1d-100.169852!2d38.861122!5i2

Shortest suggested route of 227 miles is three miles longer than this perfectly logical route that is free of construction:

https://www.google.com/maps/dir/Wichita,+KS/Castle+Rock,+Larrabee,+KS+67752/@38.4490808,-99.2696349,8.5z/data=!4m19!4m18!1m10!1m1!1s0x87badb6ad27f182d:0x9396d5bf74d33d3e!2m2!1d-97.330053!2d37.6871761!3m4!1m2!1d-97.6462284!2d37.8761959!3s0x87bb2fbed988deb9:0xd94bae37f70f1b59!1m5!1m1!1s0x87a0f609f8ed05af:0x3c7b9bb17dfb6e1!2m2!1d-100.169852!2d38.861122!3e0

I don't understand why Google Maps ignores K-96 when the combination of US 54-400 and K-14 (incidentally mismarked under its old designation of K-17) is ten miles longer and of worse standard (all-expressway versus about 20 miles of two-lane on K-14).
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on December 21, 2017, 04:22:46 PM
Speaking of odd routings, this was back in September and they fixed it now, but this is what it was coming up when looking directions from Meridian, ID to Idaho Falls, ID. The first one is perfectly fine, and my preferred route. But the second one is ridiculous. I mean, it's a cool scenic route, but not practical and should not show in in Google Maps.

(https://i.imgur.com/Xfx380S.png)

Here is the second suggestion that should have shown up. The funny thing is the time is the shortest of all of them, so Google really should have known better. I had to drag the route manually to get this routing.

(https://i.imgur.com/8Z0IK9e.png)

To be fair, they fixed this. Now all 3 routes show as options. It now picks I-84 to I-86 as the first option (fair enough, it estimates 7 minutes faster) and US-20 as the second option, though I'm not sure why the scenic route is even on there. I think there may have been a ramp closure on one of the off ramps near Burley, or maybe a bridge closure with a crossover (so 1 lane per direction over one bridge) but Google thought the actual highway was closed in that spot, so just avoided the entire thing.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 22, 2017, 03:19:04 AM
Quote from: doorknob60 on December 21, 2017, 04:22:46 PM
Speaking of odd routings, this was back in September and they fixed it now, but this is what it was coming up when looking directions from Meridian, ID to Idaho Falls, ID. The first one is perfectly fine, and my preferred route. But the second one is ridiculous. I mean, it's a cool scenic route, but not practical and should not show in in Google Maps.

(https://i.imgur.com/Xfx380S.png)

Here is the second suggestion that should have shown up. The funny thing is the time is the shortest of all of them, so Google really should have known better. I had to drag the route manually to get this routing.

(https://i.imgur.com/8Z0IK9e.png)

To be fair, they fixed this. Now all 3 routes show as options. It now picks I-84 to I-86 as the first option (fair enough, it estimates 7 minutes faster) and US-20 as the second option, though I'm not sure why the scenic route is even on there. I think there may have been a ramp closure on one of the off ramps near Burley, or maybe a bridge closure with a crossover (so 1 lane per direction over one bridge) but Google thought the actual highway was closed in that spot, so just avoided the entire thing.

They should have a senic route option then so those routes don't come up unless you tell it too.

I get the same problem when I use it as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 22, 2017, 07:50:36 AM
I wonder if it is possible to do a side-by-side feature comparison between free online mapping services. 
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 22, 2017, 01:31:21 PM
Quote from: Rothman on December 22, 2017, 07:50:36 AM
I wonder if it is possible to do a side-by-side feature comparison between free online mapping services. 

Yep.  You just need dual monitors.   :cool:
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 22, 2017, 01:33:17 PM
FWIW, I have noticed Google being more and more eager to route along minor roads as time has gone on.  I haven't had it route me along unpaved roads yet, though.  Occasionally, it now actually routes me along shortcuts I was already using but which used to take one or two drag-and-drop modifications.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 22, 2017, 02:17:20 PM
Quote from: kphoger on December 22, 2017, 01:31:21 PM
Quote from: Rothman on December 22, 2017, 07:50:36 AM
I wonder if it is possible to do a side-by-side feature comparison between free online mapping services. 

Yep.  You just need dual monitors.   :cool:
Heh.  I was envisioning a feature matrix.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 22, 2017, 04:48:35 PM
Quote from: Rothman on December 22, 2017, 02:17:20 PM
Quote from: kphoger on December 22, 2017, 01:31:21 PM
Quote from: Rothman on December 22, 2017, 07:50:36 AM
I wonder if it is possible to do a side-by-side feature comparison between free online mapping services. 

Yep.  You just need dual monitors.   :cool:

Heh.  I was envisioning a feature matrix.

In Windows 10 (and previous versions of Windows going back to 7, I think), you can snap windows to the left and right sides of the screen. Pretty easy way to pull off a comparison.

At least for me, there's no comparison. I use Street View far too often for any other mapping service to make sense.
Title: Re: Google Maps just fucking SUCKS now
Post by: english si on December 22, 2017, 07:50:18 PM
I use GMSV loads too. And the traffic function. And, on occasion, the point of interests that make the map terrible for browsing roads and such.

But if I want to browse maps for the road/rail, then I go elsewhere where there's better cartography for those functions.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on December 22, 2017, 08:29:07 PM
I guess we just keep finding more and more problems with the new Google Maps. It is now significantly harder for me to spot airports, even huge, international ones. Before, airports - especially large ones - were incredibly easy to spot - if I was browsing maps on an unfamiliar metro area in the country, I could easily notice where the international airport was, even if I had never previously known its location before. Now, it is unbearably hard to do so. I cannot do it when largely zoomed out, and even when I am highly zoomed in, it now takes an extremely long time to spot them, still. They just don't stand out like they used to, and I liked it when they did, because airports can be huge and very significant facilities.


______________________________________________________________________________________________________________________________________________________________


Also, I will say that I as well have noticed a higher frequency of Google Maps showing strange or even outrageous alternate routes from Point A to Point B when asking for directions in recent times. Though, I have never seen anything as severely off as this example:  :wow:  :-o

Quote from: doorknob60 on December 21, 2017, 04:22:46 PM
(https://i.imgur.com/Xfx380S.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on December 22, 2017, 09:27:43 PM
Quote from: adventurernumber1 on December 22, 2017, 08:29:07 PM
Also, I will say that I as well have noticed a higher frequency of Google Maps showing strange or even outrageous alternate routes from Point A to Point B when asking for directions in recent times. Though, I have never seen anything as severely off as this example:  :wow:  :-o

Quote from: doorknob60 on December 21, 2017, 04:22:46 PM
(https://i.imgur.com/Xfx380S.png)
That's nothing new to me. The real problem I have is that they don't always let you drag any part of the route to any road you want so you can see how things would be.





Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 23, 2017, 02:31:21 AM
^^
What's with the do-not-enter sign along I-84? Does that have anything to do with the odd routing? I notice that, even when the route was dragged down to I-84, it shows you having to exit before having to get back on. Maybe when it first calculated the route, the traffic was bad in the area, so it suggested a nearly-as-fast route via Fairfield.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 23, 2017, 04:15:40 PM
Quote from: D-Dey65 on December 22, 2017, 09:27:43 PM
The real problem I have is that they don't always let you drag any part of the route to any road you want so you can see how things would be.

Quote from: jakeroot on December 23, 2017, 02:31:21 AM
What's with the do-not-enter sign along I-84? Does that have anything to do with the odd routing? I notice that, even when the route was dragged down to I-84, it shows you having to exit before having to get back on. Maybe when it first calculated the route, the traffic was bad in the area, so it suggested a nearly-as-fast route via Fairfield.

In my experience, both of these things are the product of a road being closed or Google thinking a road is closed.  This can always be confirmed by turning on the Traffic overlay; closed sections are marked with a red do-not-enter symbol and, if you zoom in enough, the traffic status will be marked with a dashed red line to indicate it's closed.  Only on rare occasions have I gotten the Goog to actually route me along a road it thinks is closed, no matter how many drag-and-drops I perform.  On those rare occasions, the detailed driving directions have included a note indicating the road might be closed.

Also in my experience, road closures on divided highways present an especially difficult problem for Google to understand.  If, for example, the eastbound roadway of I-84 were closed due to road construction, and both directions of traffic were then driving head-to-head on the westbound roadway, Google can't wrap its head around that and simply refuses to route you eastbound along I-84 at all; after all, the eastbound half of that highway is closed, and the westbound roadway is one-way going the wrong direction.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 23, 2017, 11:16:57 PM
Quote from: kphoger on December 23, 2017, 04:15:40 PM
Also in my experience, road closures on divided highways present an especially difficult problem for Google to understand.  If, for example, the eastbound roadway of I-84 were closed due to road construction, and both directions of traffic were then driving head-to-head on the westbound roadway, Google can't wrap its head around that and simply refuses to route you eastbound along I-84 at all; after all, the eastbound half of that highway is closed, and the westbound roadway is one-way going the wrong direction.

To the best of my knowledge, Google can only route you along roads that it recognises as being something you can drive on (or reach, lest you're in a parking lot that it isn't drawn). For El Goog to route you onto the other carriageway (a contraflow situation), it would need to know that a crossover point exists to begin with, and it would need to be drawn on the map for Google to utilise it. It's one of the few occasions where I will admit that Google isn't perfect. Although, a paper map wouldn't know if the route was open or not. At least Google can quickly find you an alternate route, even if that route is much longer than just staying on the road, and hoping for contraflow.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on December 24, 2017, 07:20:50 AM
Quote from: kphoger on December 23, 2017, 04:15:40 PM
In my experience, both of these things are the product of a road being closed or Google thinking a road is closed.

However, Google tends to be late to the game on "reopening" a road after it is closed.  Case in point: a frontage road here was closed for a curve improvement.  The closure lasted a couple of weeks.  It was over a month later, after the road was reopened that Google finally figured out the frontage road was open.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on December 25, 2017, 01:51:44 AM
Quote from: kphoger on December 23, 2017, 04:15:40 PM
Quote from: jakeroot on December 23, 2017, 02:31:21 AM
What's with the do-not-enter sign along I-84? Does that have anything to do with the odd routing? I notice that, even when the route was dragged down to I-84, it shows you having to exit before having to get back on. Maybe when it first calculated the route, the traffic was bad in the area, so it suggested a nearly-as-fast route via Fairfield.

In my experience, both of these things are the product of a road being closed or Google thinking a road is closed.  This can always be confirmed by turning on the Traffic overlay; closed sections are marked with a red do-not-enter symbol and, if you zoom in enough, the traffic status will be marked with a dashed red line to indicate it's closed.  Only on rare occasions have I gotten the Goog to actually route me along a road it thinks is closed, no matter how many drag-and-drops I perform.  On those rare occasions, the detailed driving directions have included a note indicating the road might be closed.

Also in my experience, road closures on divided highways present an especially difficult problem for Google to understand.  If, for example, the eastbound roadway of I-84 were closed due to road construction, and both directions of traffic were then driving head-to-head on the westbound roadway, Google can't wrap its head around that and simply refuses to route you eastbound along I-84 at all; after all, the eastbound half of that highway is closed, and the westbound roadway is one-way going the wrong direction.

I touched on this a bit in the OP, but I think this was the exact situation that was happening. I didn't drive though that area at all (and I think they were finished by the time I would have), but I think there was either a contraflow situation, or maybe a ramp was closed. But I know the entire freeway definitely wasn't closed. Google doesn't usually have issues with contraflow construction around here though (it's pretty common on I-84).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 25, 2017, 02:41:14 AM
Quote from: doorknob60 on December 25, 2017, 01:51:44 AM
Google doesn't usually have issues with contraflow construction around here though (it's pretty common on I-84).

In your experience, how does Google handle contraflow? Is the freeway re-drawn on the map to show it as single-carriageway? I don't have much experience with contraflow around here. WSDOT seldom utilises it.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on December 25, 2017, 02:43:05 AM
Quote from: jakeroot on December 25, 2017, 02:41:14 AM
Quote from: doorknob60 on December 25, 2017, 01:51:44 AM
Google doesn't usually have issues with contraflow construction around here though (it's pretty common on I-84).

In your experience, how does Google handle contraflow? Is the freeway re-drawn on the map to show it as single-carriageway? I don't have much experience with contraflow around here. WSDOT seldom utilises it.

Usually it looks like any other freeway would look (doesn't look like a single carriageway), with a "work zone" symbol showing on the traffic map. Good enough for me, being just a temporary change.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 25, 2017, 02:45:23 AM
Quote from: doorknob60 on December 25, 2017, 02:43:05 AM
Quote from: jakeroot on December 25, 2017, 02:41:14 AM
Quote from: doorknob60 on December 25, 2017, 01:51:44 AM
Google doesn't usually have issues with contraflow construction around here though (it's pretty common on I-84).

In your experience, how does Google handle contraflow? Is the freeway re-drawn on the map to show it as single-carriageway? I don't have much experience with contraflow around here. WSDOT seldom utilises it.

Usually it looks like any other freeway would look (doesn't look like a single carriageway), with a "work zone" symbol showing on the traffic map. Good enough for me, being just a temporary change.

Oh okay. So you wouldn't know there was contraflow until you got to that point, unless there was a work zone symbol...I think that's how I've seen it done before, but couldn't remember.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 25, 2017, 05:15:39 PM
That's how I would think they'd do it.  Google sometimes goes overboard with temporary configurations, though.  They narrowed the carriageways during the exit 23-24 widening/reconstruction on the Thruway and it took them years to restore it to normal.  Meanwhile, NY 189 is still marked as "closed" at the border, even though the Canadian crossing will never reopen to my knowledge.  It should be marked one-way instead.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 26, 2017, 01:58:12 AM
Google can be nice and annoying. Please execs just pick one and save us from the insanity, preferably the nice side.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 26, 2017, 11:40:42 AM
Quote from: jakeroot on December 25, 2017, 02:45:23 AM
Quote from: doorknob60 on December 25, 2017, 02:43:05 AM
Quote from: jakeroot on December 25, 2017, 02:41:14 AM
Quote from: doorknob60 on December 25, 2017, 01:51:44 AM
Google doesn't usually have issues with contraflow construction around here though (it's pretty common on I-84).

In your experience, how does Google handle contraflow? Is the freeway re-drawn on the map to show it as single-carriageway? I don't have much experience with contraflow around here. WSDOT seldom utilises it.

Usually it looks like any other freeway would look (doesn't look like a single carriageway), with a "work zone" symbol showing on the traffic map. Good enough for me, being just a temporary change.

Oh okay. So you wouldn't know there was contraflow until you got to that point, unless there was a work zone symbol...I think that's how I've seen it done before, but couldn't remember.

Sounds to me like the closed roadway wasn't actually flagged as closed in Google's database.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on December 26, 2017, 10:40:31 PM
My biggest issues with the current Google Maps are the fact that the names of locations on the map act as links, which automatically rezoom and repan the map for you, I hate how Google won't default start out with all the layers still on from the previous session, and I wonder what happened to the 45-degree imagery that Google maps used to have? I found it to be really interesting and useful.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on December 27, 2017, 02:06:20 AM
Quote from: billtm on December 26, 2017, 10:40:31 PM
...and I wonder what happened to the 45-degree imagery that Google maps used to have? I found it to be really interesting and useful.
I think it can be accessed from Lite Mode still.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bickendan on December 27, 2017, 03:41:47 AM
Quote from: 20160805 on December 07, 2017, 07:16:43 AM
While on the subject of road colors, my mom's car has a built-in navigation program, and it uses red for freeways, orange for expressways and big boulevards, green for arterials, and gray for side streets.  The only problem is that it is completely unreliable when it comes to city boundaries, is missing several streets, and the differentiation between gray and green and between green and orange are case-by-case, arbitrary, and inconsistent.  College Ave in metro Appleton between Casaloma Dr and County CB shows up as gray, for example.

When I make maps, I use a similar coloring scheme, but I also add a dark green color for minor arterials.
It's good to know the Thomas Brothers symbology hasn't died.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 27, 2017, 11:58:39 AM
Quote from: billtm on December 26, 2017, 10:40:31 PM
the names of locations on the map act as links, which automatically rezoom and repan the map for you,

This is especially annoying if you have a bad mouse that likes to turn drags into clicks.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on December 27, 2017, 12:56:38 PM
Quote from: kphoger on December 26, 2017, 11:40:42 AM
Quote from: jakeroot on December 25, 2017, 02:45:23 AM
Quote from: doorknob60 on December 25, 2017, 02:43:05 AM
Quote from: jakeroot on December 25, 2017, 02:41:14 AM
Quote from: doorknob60 on December 25, 2017, 01:51:44 AM
Google doesn't usually have issues with contraflow construction around here though (it's pretty common on I-84).

In your experience, how does Google handle contraflow? Is the freeway re-drawn on the map to show it as single-carriageway? I don't have much experience with contraflow around here. WSDOT seldom utilises it.

Usually it looks like any other freeway would look (doesn't look like a single carriageway), with a "work zone" symbol showing on the traffic map. Good enough for me, being just a temporary change.

Oh okay. So you wouldn't know there was contraflow until you got to that point, unless there was a work zone symbol...I think that's how I've seen it done before, but couldn't remember.

Sounds to me like the closed roadway wasn't actually flagged as closed in Google's database.

I did say "usually". I think in this particular case, the eastbound carriageway was marked as closed. I have no way to confirm that at this point though.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 28, 2017, 04:40:23 AM
I wish google had a running option so I know how long it would be for me to run to a certain place at 8-10 mph.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 28, 2017, 11:03:23 AM
Quote from: Hurricane Rex on December 28, 2017, 04:40:23 AM
I wish google had a running option so I know how long it would be for me to run to a certain place at 8-10 mph.

There's math for that.  miles÷speed=hours.  With numbers like 8 or 10 mph, that should even be easy enough to figure in your head.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 28, 2017, 12:13:23 PM
Running speed is variable and to an extent dependent on age, as is reflected in pass standards for the triathlon-like Army Physical Fitness Test (if memory serves, a male recruit reaches the point where a pass equates to a ten-minute mile sometime in his mid- to late twenties).

I think I would place more emphasis on using StreetView to evaluate potential running routes for hazards such as stakes close to the sidewalk or running track.  I have family friends who are in their mid-seventies and very fitness-oriented, and their 2017 Christmas letter mentioned that the husband had cut his shin on such a stake, which was used to tie down an on-premises advertising display.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on December 28, 2017, 12:25:15 PM
Quote from: J N Winkler on December 28, 2017, 12:13:23 PM
Running speed is variable and to an extent dependent on age, as is reflected in pass standards for the triathlon-like Army Physical Fitness Test (if memory serves, a male recruit reaches the point where a pass equates to a ten-minute mile sometime in his mid- to late twenties).

I think I would place more emphasis on using StreetView to evaluate potential running routes for hazards such as stakes close to the sidewalk or running track.  I have family friends who are in their mid-seventies and very fitness-oriented, and their 2017 Christmas letter mentioned that the husband had cut his shin on such a stake, which was used to tie down an on-premises advertising display.
I hate random shit that sticks out of the ground and Oklahoma City seem to be ground zero for that.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on December 28, 2017, 05:36:16 PM
Recently I tried to use Google Street View to look at a bridge under the Metro-North New Haven Line in Mamaroneck (or Harrison, I forget), and the camera view kept swinging from side to side!

:eyebrow:

I really wish I could say I was kidding about that.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 28, 2017, 05:47:15 PM
Quote from: D-Dey65 on December 28, 2017, 05:36:16 PM
Recently I tried to use Google Street View to look at a bridge under the Metro-North New Haven Line in Mamaroneck (or Harrison, I forget), and the camera view kept swinging from side to side!

:eyebrow:

I really wish I could say I was kidding about that.

That's pretty much normal for Google.  I imagine it's either that or skipping longer distances.  I assume the Google car drove both directions, and it's merely finding the closest spot to your pointer click.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on December 29, 2017, 04:18:10 AM
Quote from: kphoger on December 28, 2017, 11:03:23 AM
Quote from: Hurricane Rex on December 28, 2017, 04:40:23 AM
I wish google had a running option so I know how long it would be for me to run to a certain place at 8-10 mph.

There's math for that.  miles÷speed=hours.  With numbers like 8 or 10 mph, that should even be easy enough to figure in your head.

I mean I do that all the time in my head however sometimes after a day in AP Calculus I just want to be lazy. :)      That is my reasoning for this. Otherwise your point is the way to do it.
Title: Re: Google Maps just fucking SUCKS now
Post by: billtm on December 29, 2017, 12:29:07 PM
Quote from: kphoger on December 27, 2017, 11:58:39 AM
Quote from: billtm on December 26, 2017, 10:40:31 PM
the names of locations on the map act as links, which automatically rezoom and repan the map for you,

This is especially annoying if you have a bad mouse that likes to turn drags into clicks.

Yeah, my trackpad turns drags into clicks very often. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 29, 2017, 12:56:04 PM
I have a MacBook Pro. There is an option to disable "tap to click".

I'm not sure if Windows systems have the same option.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brian556 on January 19, 2018, 01:04:53 AM
Is Google Maps running slow for you guys? It is painfully slow for me, to the point that its basically non-usable. The problem is not my computer because I just did a clean install of Windows on a new hard drive. I'm using Edge, which is really fast on other websites
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on January 19, 2018, 02:16:47 AM
Quote from: Brian556 on January 19, 2018, 01:04:53 AM
Is Google Maps running slow for you guys? It is painfully slow for me, to the point that its basically non-usable. The problem is not my computer because I just did a clean install of Windows on a new hard drive. I'm using Edge, which is really fast on other websites

It's running fine for me. I flip between edge and chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 20, 2018, 03:56:09 PM
Quote from: Brian556 on January 19, 2018, 01:04:53 AM
Is Google Maps running slow for you guys? It is painfully slow for me, to the point that its basically non-usable. The problem is not my computer because I just did a clean install of Windows on a new hard drive. I'm using Edge, which is really fast on other websites

I was having a problem on Thursday where, if I left a tab open for too long, it would get really laggy and I'd have to close it. Haven't used Gmaps desktop since then, so not sure if the problem persists.

On Gmaps mobile, I've been having this issue where the traffic layer keeps turning itself on. Very annoying since I don't use Gmaps for traffic (I have Waze for that).
Title: Re: Google Maps just fucking SUCKS now
Post by: english si on January 20, 2018, 04:37:05 PM
Quote from: Hurricane Rex on December 26, 2017, 01:58:12 AMGoogle can be nice and annoying.
Indeed, when it is good it is very very good, and when it is bad it is horrid.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on January 20, 2018, 07:59:32 PM
Extremely minor issue that I have on my laptop: if I leave a tab open for a while (and, I suspect, close/reopen the lid, though I haven't confirmed this) the map becomes ever so slightly blurry. Like, not to the point of being unreadable or anything, but just enough that you can see that text isn't quite as crisp as usual. Easily fixed with a refresh, though.

On another note: if you miss the old, more noticeable freeway colors, you can still see them by looking at South Korea, where I guess they haven't yet updated the static raster images they use there with the new scheme.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on January 20, 2018, 08:18:23 PM
A new change I've noticed is that they now put prices in the little flags that indicate where hotels are. Which is nice, although the font shading could use some work.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi67.tinypic.com%2F2v9f0uo.jpg&hash=589aa0aa071471cdd79d3e49cdcacd2a4f837abf)
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on January 20, 2018, 09:57:13 PM
Quote from: CtrlAltDel on January 20, 2018, 08:18:23 PM
A new change I've noticed is that they now put prices in the little flags that indicate where hotels are. Which is nice, although the font shading could use some work.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi67.tinypic.com%2F2v9f0uo.jpg&hash=589aa0aa071471cdd79d3e49cdcacd2a4f837abf)

Google, show me the nearest Post Offices / Zaxby’s / Grocery Stores...easy enough.

Google, show me the nearest Holiday Inn...It shows you every hotel, motel, hostel, dormitory, and gulag in a 100 mile radius.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on January 21, 2018, 02:41:54 AM
Aparently Google maps only allows 10 stops on directions which for someone like me, who goes on to fictionalize random road trips, its inconvienent and annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on January 24, 2018, 10:02:35 AM
You know, I would LOVE to correct Google Maps on the waterways of the east end of Long Island. They seem to have this crazy idea that the Peconic River includes Long Beach Bay, Orient Harbor, the Shelter Island Sound, Sag Harbor Bay, Noyack Bay, Southold Bay, Hog Neck Bay, Cutchogue Harbor, North Race, the Little and Great Peconic Bays, Flanders Bay, and Reeve's Bay.

Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on January 24, 2018, 01:56:12 PM
Quote from: D-Dey65 on January 24, 2018, 10:02:35 AM
You know, I would LOVE to correct Google Maps on the waterways of the east end of Long Island. They seem to have this crazy idea that the Peconic River includes Long Beach Bay, Orient Harbor, the Shelter Island Sound, Sag Harbor Bay, Noyack Bay, Southold Bay, Hog Neck Bay, Cutchogue Harbor, North Race, the Little and Great Peconic Bays, Flanders Bay, and Reeve's Bay.
Its handling of waterways in general id pretty lousy.  Labeling of them is sparse and inconsistent in general.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on January 29, 2018, 07:37:09 PM
Is it just me or is google maps a little slow?
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on January 30, 2018, 02:15:06 AM
Quote from: stormwatch7721 on January 29, 2018, 07:37:09 PM
Is it just me or is google maps a little slow?
It can be a little slow for me as well. Your not alone.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on February 09, 2018, 07:12:36 AM
Quote from: Hurricane Rex on January 21, 2018, 02:41:54 AM
Aparently Google maps only allows 10 stops on directions which for someone like me, who goes on to fictionalize random road trips, its inconvienent and annoying.

(Slight grave-dig)

Circa 2012 they used to allow about 15 stops, and you could modify the route by dragging it quite a few times too.  Always confused me why they removed those extra stops; I guess user friendliness isn't always on the top of their minds.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 13, 2018, 12:57:02 AM
I wouldn’t call this a feature that sucks, but apparently, for some multistory buildings, Google Maps offers a floor plan of each floor. For Boston City Hall, for example, you can see what’s on each of the nine, by clicking a number on the lower right of the map.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi68.tinypic.com%2F9fmc1k.png&hash=e5326b0f2d5dfc303a6fc9d8f4ccdc88d06e4d69)

https://www.google.com/maps/place/Boston+City+Hall/@42.360398,-71.0585033,19.42z/data=!3m1!5s0x89e37085a36acc1b:0xff95595e8d8887bb!4m5!3m4!1s0x89e37085a3300f2f:0x7e2c37cdd191455a!8m2!3d42.360406!4d-71.057993
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 13, 2018, 03:29:52 AM
Quote from: CtrlAltDel on February 13, 2018, 12:57:02 AM
I wouldn't call this a feature that sucks, but apparently, for some multistory buildings, Google Maps offers a floor plan of each floor. For Boston City Hall, for example, you can see what's on each of the nine, by clicking a number on the lower right of the map.

http://i68.tinypic.com/9fmc1k.png

https://www.google.com/maps/place/Boston+City+Hall/@42.360398,-71.0585033,19.42z/data=!3m1!5s0x89e37085a36acc1b:0xff95595e8d8887bb!4m5!3m4!1s0x89e37085a3300f2f:0x7e2c37cdd191455a!8m2!3d42.360406!4d-71.057993

As far as I know, this has been a feature for several years. Still pretty cool though.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 17, 2018, 06:51:52 PM
Looks like Google has updated the API maps to the new design, so even http://gokml.net/maps won't give you the old one any more.  Too bad none of their alternative styles are as good (the retro one would be nice, but it's missing many route markers, exit numbers, and borders).  The street view overlay haven't updated yet, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on March 01, 2018, 11:18:56 AM
Freeways are still orange here, although these have nowhere near the functionality of the full Google Maps:

http://xjubier.free.fr/en/site_pages/solar_eclipses/TSE_2017_GoogleMapFull.html

http://mhd.ms2soft.com/tcds/tsearch.asp?loc=Mhd&mod=
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on March 12, 2018, 07:22:04 PM
I somehow got orange freeways (not yellow) just by going to maps.google.com. It's still random, though. I only got it once.
Title: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on April 07, 2018, 02:59:56 PM
This is actually not a bad thing about Google Maps, but a good thing, which I just noticed today. It looks like, at least on this Home Depot building, Google Maps is now mapping out the layout within the store itself (each section with its respective supplies). This is very, very cool and useful. These pictures were taken on Google Maps off of Interstate 75's Exit 312 in Calhoun, Georgia (GA SR 53; Fairmount, Rome). I checked the Home Depot in Dalton, GA (my hometown) off of I-75's Exit 336, and it has had similar updates done to it. This is incredibly nice, and I wonder if this feature will continue to expand to other large stores and the sort. Here are the two screenshots of this from Google Maps, which I saw for the first time 20 or 30 minutes ago:

(https://uploads.tapatalk-cdn.com/20180407/e3f4a5c4f1bcb80b1b7cf32ddc36de84.jpg)

(https://uploads.tapatalk-cdn.com/20180407/c7ecbbc1235226770d51d28baae6dd75.jpg)


Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on April 07, 2018, 04:00:56 PM
Same for the Home Depots in Edmond and North OKC. I looked to see if other similar large stores like Target or Lowe's had the same thing and they don't.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on April 07, 2018, 04:06:43 PM
Quote from: Plutonic Panda on April 07, 2018, 04:00:56 PM
Same for the Home Depots in Edmond and North OKC. I looked to see if other similar large stores like Target or Lowe's had the same thing and they don't.

I also checked the Walmart and Kroger in my area, and they, too, do not have it (at least not yet). Hopefully it will eventually expand to them as well, though.  :nod:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 07, 2018, 04:52:49 PM
I think this has been around for a little while now. They started off mapping the basic layouts of large buildings, and they've now progressed down to labelling the layouts. Very impressive and time consuming, I'm sure. In fact, it's a bit hard to believe that they actually have a team of code monkeys mapping these stores. I'd rip my hair out having to do that over and over again.

Best Buy and Nordstrom are two that I've noticed having the more detailed maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on April 07, 2018, 08:04:28 PM
They tend to have the multi-level detailed maps of many of the large shopping malls, plus they map out many sports arenas and concert venues (MSG, the XL Center in Hartford).    Most Home Depots are (the two in my town are), plus the Chili's in my town is as well
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 07, 2018, 09:09:12 PM
I wonder if Home Depot notifies Google if they rearrange their shelves.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on April 08, 2018, 01:28:20 AM
This stuff really is amazing. Maybe it's been around longer than I thought, and I just hadn't noticed it until now. Regardless, I myself am very impressed, and I hope to see expansions of this feature in the future, which it sounds like is very possible.  :nod:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 08, 2018, 02:14:45 AM
Quote from: kkt on April 07, 2018, 09:09:12 PM
I wonder if Home Depot notifies Google if they rearrange their shelves.

I'm guessing that it'll be up to the end-user to report the issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on April 08, 2018, 09:18:56 AM
Can I just say at this point, what is the deal with all these navigation apps (Google or otherwise) insisting on washed out, no-contrast color schemes that aren't remotely visible when mounted in a vehicle?
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on April 09, 2018, 05:19:28 PM
Has anyone else noticed that street view images from around 10 years ago (2007-2009) are starting to disappear or become very inaccessible?
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on April 09, 2018, 05:34:24 PM
Quote from: freebrickproductions on April 09, 2018, 05:19:28 PM
Has anyone else noticed that street view images from around 10 years ago (2007-2009) are starting to disappear or become very inaccessible?

Yep. I'm starting to miss those potato-quality images.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on April 09, 2018, 05:35:11 PM
Quote from: freebrickproductions on April 09, 2018, 05:19:28 PM
Has anyone else noticed that street view images from around 10 years ago (2007-2009) are starting to disappear or become very inaccessible?

I have not noticed, but if that is true, that is extremely saddening for me. Even if they're blurry (compared to the quality of new stuff in recent years), it is priceless documentation of what roads and cities looked like in the past. If they are taking it away, we will no longer be able to see (at least not as easily) what highways and places looked like a decade or more ago. I really hope that they are not doing this, because that would be yet another horrible new thing that Google Maps has done, and it is erasing history from our fingertips. I've lived in Dalton, Georgia almost my entire life, but even with my photographic memory, I just forget things (like any human), and I can remind myself of what the roads and places in this town looked like in 2007 just by looking at old GMSV. It is truly a blast to the past. I don't want the ability to remember what my own town looked like when I was younger to be taken away from me. Hopefully this won't/isn't happen(ing), but only time will tell what actually happens in the end.  :-/


Title: Re: Google Maps just fucking SUCKS now
Post by: index on April 09, 2018, 06:02:21 PM
Quote from: LM117 on April 09, 2018, 05:34:24 PM
Quote from: freebrickproductions on April 09, 2018, 05:19:28 PM
Has anyone else noticed that street view images from around 10 years ago (2007-2009) are starting to disappear or become very inaccessible?

Yep. I'm starting to miss those potato-quality images.


I use them a lot to find old 12-8-8 signals that aren't there anymore, I don't want those old street views to be gone.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on April 11, 2018, 06:13:37 PM
Right now on my computer all the major roads look yellow, freeways and expressways being pretty much the exact same colour as the regular arterials.  :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 11, 2018, 06:29:06 PM
Quote from: 20160805 on April 11, 2018, 06:13:37 PM
Right now on my computer all the major roads look yellow, freeways and expressways being pretty much the exact same colour as the regular arterials.  :pan:

That's been the case (except for a random ~5% chance) for over a month now.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 12, 2018, 03:54:13 PM
Quote from: empirestate on April 08, 2018, 09:18:56 AM
Can I just say at this point, what is the deal with all these navigation apps (Google or otherwise) insisting on washed out, no-contrast color schemes that aren't remotely visible when mounted in a vehicle?

In my experience, apps like Waze are easier on the eyes, especially when driving at night. I prefer low contrast color schemes that don't stand out from the rest of the interior lights. It's less distracting.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on April 12, 2018, 07:47:03 PM
Quote from: jakeroot on April 12, 2018, 03:54:13 PM
Quote from: empirestate on April 08, 2018, 09:18:56 AM
Can I just say at this point, what is the deal with all these navigation apps (Google or otherwise) insisting on washed out, no-contrast color schemes that aren't remotely visible when mounted in a vehicle?

In my experience, apps like Waze are easier on the eyes, especially when driving at night. I prefer low contrast color schemes that don't stand out from the rest of the interior lights. It's less distracting.

I'm thinking of the daytime in particular. Even in those apps I've seen that have day and night modes, the day mode is similarly very low-contrast, and difficult to distinguish against the exterior light. But I don't actually have Waze; is it better in that respect?
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on April 14, 2018, 12:35:39 AM
I think the issue with the old street view is that the old street view tracks aren't getting "bound" to the roads properly anymore. You have to be at the right spots to switch from one to the other, but usually once you find a spot to switch to the old, you can stay there. Sometimes jumping far forward will kick you back into the current street view, but it's always been finicky with jumping like that. It's just hard sometimes to find the right points to be able to get the year you want if it's there. It seems to affect all past street view, too, not just 2007-2009.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on April 14, 2018, 01:32:19 AM
Quote from: Roadsguy on April 14, 2018, 12:35:39 AM
I think the issue with the old street view is that the old street view tracks aren't getting "bound" to the roads properly anymore. You have to be at the right spots to switch from one to the other, but usually once you find a spot to switch to the old, you can stay there. Sometimes jumping far forward will kick you back into the current street view, but it's always been finicky with jumping like that. It's just hard sometimes to find the right points to be able to get the year you want if it's there. It seems to affect all past street view, too, not just 2007-2009.
I remember when the feature to view old street view first came out, you could go from image to image without issue. Not sure why Google wants to make it difficult like it is...
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 14, 2018, 08:53:51 AM
Quote from: empirestate on April 12, 2018, 07:47:03 PM
Quote from: jakeroot on April 12, 2018, 03:54:13 PM
Quote from: empirestate on April 08, 2018, 09:18:56 AM
Can I just say at this point, what is the deal with all these navigation apps (Google or otherwise) insisting on washed out, no-contrast color schemes that aren't remotely visible when mounted in a vehicle?

In my experience, apps like Waze are easier on the eyes, especially when driving at night. I prefer low contrast color schemes that don't stand out from the rest of the interior lights. It's less distracting.

I'm thinking of the daytime in particular. Even in those apps I've seen that have day and night modes, the day mode is similarly very low-contrast, and difficult to distinguish against the exterior light. But I don't actually have Waze; is it better in that respect?

Depends on what you're looking for. During the day, Waze has a white background with dark grey roads. At night, it's a sort of blue-grey background with near-black roads. Either way, all roads are the same color. Which doesn't bother me, but it might bother some others.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on April 14, 2018, 06:25:04 PM
Quote from: jakeroot on April 14, 2018, 08:53:51 AM
Quote from: empirestate on April 12, 2018, 07:47:03 PM
Quote from: jakeroot on April 12, 2018, 03:54:13 PM
Quote from: empirestate on April 08, 2018, 09:18:56 AM
Can I just say at this point, what is the deal with all these navigation apps (Google or otherwise) insisting on washed out, no-contrast color schemes that aren't remotely visible when mounted in a vehicle?

In my experience, apps like Waze are easier on the eyes, especially when driving at night. I prefer low contrast color schemes that don't stand out from the rest of the interior lights. It's less distracting.

I'm thinking of the daytime in particular. Even in those apps I've seen that have day and night modes, the day mode is similarly very low-contrast, and difficult to distinguish against the exterior light. But I don't actually have Waze; is it better in that respect?

Depends on what you're looking for. During the day, Waze has a white background with dark grey roads. At night, it's a sort of blue-grey background with near-black roads. Either way, all roads are the same color. Which doesn't bother me, but it might bother some others.

I'd be looking for something in high contrast, to be readable in daylight. (Dark gray on white certainly sounds like a step in that direction.) Alternatively, road symbols with bold casing and lettering, viewable at a distance. Even any casing would be a start–too many apps seem to favor very muted color schemes: white roads on off-white backgrounds with no edges, faded or pastel hues for POI symbols, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: MrAndy1369 on April 19, 2018, 03:37:42 PM
Quote from: freebrickproductions on April 09, 2018, 05:19:28 PM
Has anyone else noticed that street view images from around 10 years ago (2007-2009) are starting to disappear or become very inaccessible?

Not to me. Browsing in many random places in California, there's plenty of 2007 imagery, as well as 2008-2011. It's a challenge sometimes on widened roads, to find the right "track" to go back in time, but they don't seem to be disappearing for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 19, 2018, 04:54:06 PM
Quote from: MrAndy1369 on April 19, 2018, 03:37:42 PM
Quote from: freebrickproductions on April 09, 2018, 05:19:28 PM
Has anyone else noticed that street view images from around 10 years ago (2007-2009) are starting to disappear or become very inaccessible?

Not to me. Browsing in many random places in California, there's plenty of 2007 imagery, as well as 2008-2011. It's a challenge sometimes on widened roads, to find the right "track" to go back in time, but they don't seem to be disappearing for me.

That's the problem I have. You really have to click around some times to get the right track with all the historic imagery. I swear every spot is slightly different. Once you do find the right track, you can usually stay in that year no problem, as long as you don't click too far away from where you are.

Quote from: empirestate on April 14, 2018, 06:25:04 PM
Quote from: jakeroot on April 14, 2018, 08:53:51 AM
Quote from: empirestate on April 12, 2018, 07:47:03 PM
Quote from: jakeroot on April 12, 2018, 03:54:13 PM
Quote from: empirestate on April 08, 2018, 09:18:56 AM
Can I just say at this point, what is the deal with all these navigation apps (Google or otherwise) insisting on washed out, no-contrast color schemes that aren't remotely visible when mounted in a vehicle?

In my experience, apps like Waze are easier on the eyes, especially when driving at night. I prefer low contrast color schemes that don't stand out from the rest of the interior lights. It's less distracting.

I'm thinking of the daytime in particular. Even in those apps I've seen that have day and night modes, the day mode is similarly very low-contrast, and difficult to distinguish against the exterior light. But I don't actually have Waze; is it better in that respect?

Depends on what you're looking for. During the day, Waze has a white background with dark grey roads. At night, it's a sort of blue-grey background with near-black roads. Either way, all roads are the same color. Which doesn't bother me, but it might bother some others.

I'd be looking for something in high contrast, to be readable in daylight. (Dark gray on white certainly sounds like a step in that direction.) Alternatively, road symbols with bold casing and lettering, viewable at a distance. Even any casing would be a start–too many apps seem to favor very muted color schemes: white roads on off-white backgrounds with no edges, faded or pastel hues for POI symbols, etc.

Waze is actually pretty good in that respect. There are three different color schemes. Default, "Map Editor" (aka high contrast?), and Night. Screenshots below in said order.

I have very good vision, so I don't even struggle with Google Maps. But I think Waze has at least equal footing with their counterparts.

(https://i.imgur.com/u1qQQem.jpg)(https://i.imgur.com/83tIOGF.jpg)(https://i.imgur.com/fTbaoaB.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 20, 2018, 08:20:05 PM
Here's a feature I haven't seen before. There are now little buttons you can click on to find various places of business. Sorry, it's in French, but it doesn't appear when I use the English version.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi68.tinypic.com%2F2nkqj5g.jpg&hash=c35c3e8c93f81df8134db27a83941226a6246c2f)

On the whole, I don't really like it since it takes up a bit too much space. People on the go might find it handy, and it will certainly keep their advertisers happy.

Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on April 22, 2018, 01:41:16 AM
Something strange has been happening to me lately with Google Maps. This probably happened to me for the first time about a week ago, and it has happened several times since then, including a few hours ago tonight. The issue is that when I turn Terrain on on Google Maps (the turning it on part works just fine), and then I try to turn it off, it doesn't respond. The only way to undo it is to actually go back to whatever was previously on that tab (the last thing I searched on Google Maps, directions I had, or last setting I touched, etc.), and this can be irksome, and sometimes it might go too far (where it will "X" out of Google Maps altogether, due to going all the way to the beginning of the history of that tab). This is definitely new, and it is quite annoying, but I don't know why it's happening. I use Terrain a lot on Google Maps, because I find it interesting to learn of the topography of the area, and knowing such things helps me understand roads much better as well, and why they traverse the land the way they do. Hopefully this issue will be fixed soon.  :-/
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 23, 2018, 08:55:31 PM
Quote from: CtrlAltDel on April 20, 2018, 08:20:05 PM
Here's a feature I haven't seen before. There are now little buttons you can click on to find various places of business. Sorry, it's in French, but it doesn't appear when I use the English version.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi68.tinypic.com%2F2nkqj5g.jpg&hash=c35c3e8c93f81df8134db27a83941226a6246c2f)

On the whole, I don't really like it since it takes up a bit too much space. People on the go might find it handy, and it will certainly keep their advertisers happy.


It appears for me once in a blue moon.  I hate it when that happens.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on April 24, 2018, 04:59:19 PM
A screenshot from a few minutes ago, presented without comment:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ften93.com%2F2018%2Fgmaps20180424.png&hash=e60cabf52b26b7a83a666b06e34588c2949bc93e)
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on April 24, 2018, 05:16:41 PM
Quote from: Eth on April 24, 2018, 04:59:19 PM
A screenshot from a few minutes ago, presented without comment:

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ften93.com%2F2018%2Fgmaps20180424.png&hash=e60cabf52b26b7a83a666b06e34588c2949bc93e)

It looks like Google Maps has presented a feature where you can view maps during the creation of the Interstate Highway System - except, it looks like, I-22 (which is one of the newest interstates in actuality) has been completed before all the other ones!

:wow:  :pan:  :bigass:  :rofl:
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 24, 2018, 05:17:52 PM
Only certain numbers are showing. However, it's not a mathematical sequence; this OEIS search (http://oeis.org/search?q=4+5+10+12+15+16+17+19+22+24+27+29+37+%7E8+%7E20+%7E25+%7E26+%7E30+%7E35&language=english&go=Search) returns no results.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on April 27, 2018, 08:44:36 PM
http://www.google.com/search?q=fog+willow+farms+wilton+ca
Read the first question on the right side under the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 28, 2018, 12:14:54 AM
Quote from: NE2 on April 27, 2018, 08:44:36 PM
http://www.google.com/search?q=fog+willow+farms+wilton+ca
Read the first question on the right side under the map.

Particularly alarming is the (apparent) unwillingness on Google's part to change the name to the correct one. At least with most of these errors, they're temporary.
Title: Re: Google Maps just fucking SUCKS now
Post by: chays on May 02, 2018, 01:43:00 PM
I love Google Maps and think the criticism is generally overblown.  However, this is pretty embarrassing:

(https://i.imgur.com/MoIQd1a.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on May 02, 2018, 02:20:25 PM
Quote from: chays on May 02, 2018, 01:43:00 PM
I love Google Maps and think the criticism is generally overblown.  However, this is pretty embarrassing:

Yeah, it's bad.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ften93.com%2F2018%2Fflorida_key.png&hash=5c9abbc74c1a92e5d88f9f3267f22eb46088430c) (https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Ften93.com%2F2018%2Fhawaiian_island.png&hash=a569941c51c1c013361103e141927b4b43ba984f)
Title: Re: Google Maps just fucking SUCKS now
Post by: chays on May 02, 2018, 02:59:24 PM
Wow, definitely a programming error, leaving off the last letter of the string.

https://www.google.com/search?q=little+sisters+bvi&oq=little+sisters+bvi&aqs=chrome..69i57.3821j0j7&sourceid=chrome&ie=UTF-8
Here's the Google search preview of the Little Sisters in the BVI:
(https://www.google.com/maps/vt/data=QQ4f6BdzOtXvbtJr7p3iBj3I5j5Tyy7oMw7e-yXkrbEtRSDZu-pgYsYqt4oQKAPH7RgX5Tu12XLtGLz5dJFkIZfEYTA3GWgiqnbWowcK3Efx8Ib-mcA_6cAQVgx4LdRC62AuXthQox3DFrMSxJIhKzaRgLQYOJ3DP3pm_50-IB8rNPtKTZYDZ5CcFp9PVp9QcAWsB50m)

If you click on picture (even the link URL shows is it as Sisters), you can see the leave off the "s" in the map: https://www.google.com/maps/place/Little+Sisters/@18.3509257,-64.690439,11z/data=!3m1!4b1!4m5!3m4!1s0x8c0571c645572493:0x152ac6e15eb9600f!8m2!3d18.3509769!4d-64.5503528
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 02, 2018, 03:15:07 PM
Is the curved lettering not intentional? A very 'classical' look in my opinion. I like it.
Title: Re: Google Maps just fucking SUCKS now
Post by: chays on May 02, 2018, 03:41:23 PM
Quote from: jakeroot on May 02, 2018, 03:15:07 PM
Is the curved lettering not intentional? A very 'classical' look in my opinion. I like it.
I like it too, but they are dropping the last letter of all these style labels.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 02, 2018, 04:12:04 PM
Quote from: chays on May 02, 2018, 03:41:23 PM
Quote from: jakeroot on May 02, 2018, 03:15:07 PM
Is the curved lettering not intentional? A very 'classical' look in my opinion. I like it.

I like it too, but they are dropping the last letter of all these style labels.

Oh no shit. Didn't notice that. Would have had I read your whole post.  :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on May 02, 2018, 06:39:55 PM
Darn off-by-one errors.
Darn live kamikaze-style programming.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on May 02, 2018, 10:07:32 PM
Quote from: chays on May 02, 2018, 02:59:24 PM
If you click on picture (even the link URL shows is it as Sisters), you can see the leave off the "s" in the map: https://www.google.com/maps/place/Little+Sisters/@18.3509257,-64.690439,11z/data=!3m1!4b1!4m5!3m4!1s0x8c0571c645572493:0x152ac6e15eb9600f!8m2!3d18.3509769!4d-64.5503528

It was really weird when I clicked that link: it showed the name right at first, and then the last letter vanished after a split second.
Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on May 02, 2018, 10:50:44 PM
I had to find a residential street that has been around for about 6 months now.  Google Maps STILL doesn't show the street -- or the whole subdivision for that matter -- yet Waze got me into that newer development and straight to that street. 

On the flip side, Waze is still not the greatest when it comes to identifying street names, or turn-offs to other streets or businesses.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 02, 2018, 10:54:25 PM
Quote from: thenetwork on May 02, 2018, 10:50:44 PM
I had to find a residential street that has been around for about 6 months now.  Google Maps STILL doesn't show the street -- or the whole subdivision for that matter -- yet Waze got me into that newer development and straight to that street. 

On the flip side, Waze is still not the greatest when it comes to identifying street names, or turn-offs to other streets or businesses.

My one reservation with Waze was that street changes were slower to show up compared to Google Maps, so it surprises me to hear that Google is on the slower end for once. You might consider letting them know, but include a link to some proof.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on May 02, 2018, 11:14:12 PM
Google can really drag their feet on a change.  I have put in multiple requests to correct their marking of CT 31, including map edit requests.   It is correctly marked as a state route south of US 44, but north of US 44, it all of a sudden is marked as a county route.  Despite telling them that it's the same road and that CT does not have county routes, the change has not been make in any updates released.  It has been the better part of a year and no changes.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 03, 2018, 12:31:35 AM
Quote from: jp the roadgeek on May 02, 2018, 11:14:12 PM
Google can really drag their feet on a change.  I have put in multiple requests to correct their marking of CT 31, including map edit requests.   It is correctly marked as a state route south of US 44, but north of US 44, it all of a sudden is marked as a county route.  Despite telling them that it's the same road and that CT does not have county routes, the change has not been make in any updates released.  It has been the better part of a year and no changes.

There's a house near me that's been marked as an Embressy Suites (with that spelling) for about two years now.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on May 04, 2018, 07:02:10 PM
Holy crap, some good news regarding Google Maps.  :-o  :-D 

I just saw some street-view, which shows very new images from December 2017. (https://www.google.com/maps/@33.7682123,-118.2811929,3a,75y,44.51h,84.01t/data=!3m7!1e1!3m5!1sY6CQ5ePBhKKNNcEld0GRBA!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DY6CQ5ePBhKKNNcEld0GRBA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D291.46323%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192) As can be seen, these images are very, very, very high-quality. I was caught off-guard and pleasantly surprised to see this beauty, as I was not expecting such clear images, even though they have gotten better over time (to the point where 2007 and 2008 imagery looks relatively quite blurry now). This was extremely nice to see, that's for sure.  :thumbsup:


Title: Re: Google Maps just fucking SUCKS now
Post by: US71 on May 06, 2018, 06:53:46 PM
Quote from: adventurernumber1 on May 04, 2018, 07:02:10 PM
Holy crap, some good news regarding Google Maps.  :-o  :-D 


And some bad news
https://developers.googleblog.com/2018/05/introducing-google-maps-platform.html
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on May 06, 2018, 07:37:05 PM
Quote from: US71 on May 06, 2018, 06:53:46 PM
Quote from: adventurernumber1 on May 04, 2018, 07:02:10 PM
Holy crap, some good news regarding Google Maps.  :-o  :-D 


And some bad news
https://developers.googleblog.com/2018/05/introducing-google-maps-platform.html

Wait, I'm just very, very lost. I've been looking at it for 20 minutes, but due to the debilitating, racing anxiety I am experiencing, I am having trouble figuring out what is going on (I am reading the same things over and over again but I am not encoding anything or understanding it). Does this mean I have to pay $200 a month just to use Google Maps now? Or is it only $200 for some super-special service. Does this mean that I can't do street-view anymore until I hand over my entire wallet and a little extra? What is the $200 for. Is that the minimum price to use Google Maps for the future, I have no idea. Someone please explain to me.  :wow:  :paranoid:  :no:
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on May 06, 2018, 07:45:27 PM
Quote from: adventurernumber1 on May 06, 2018, 07:37:05 PM
Quote from: US71 on May 06, 2018, 06:53:46 PM
Quote from: adventurernumber1 on May 04, 2018, 07:02:10 PM
Holy crap, some good news regarding Google Maps.  :-o  :-D 


And some bad news
https://developers.googleblog.com/2018/05/introducing-google-maps-platform.html

Wait, I'm just very, very lost. I've been looking at it for 20 minutes, but due to the debilitating, racing anxiety I am experiencing, I am having trouble figuring out what is going on (I am reading the same things over and over again but I am not encoding anything or understanding it). Does this mean I have to pay $200 a month just to use Google Maps now? Or is it only $200 for some super-special service. Does this mean that I can't do street-view anymore until I hand over my entire wallet and a little extra? What is the $200 for. Is that the minimum price to use Google Maps for the future, I have no idea. Someone please explain to me.  :wow:  :paranoid:  :no:


That message seems to be aimed at developers who are building their applications on the Google Maps database or API, not just users.  I wouldn't worry.  Agree that it's confusingly-written, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on May 06, 2018, 07:49:28 PM
Quote from: adventurernumber1 on May 06, 2018, 07:37:05 PM
Quote from: US71 on May 06, 2018, 06:53:46 PM
And some bad news
https://developers.googleblog.com/2018/05/introducing-google-maps-platform.html
Wait, I'm just very, very lost. I've been looking at it for 20 minutes, but due to the debilitating, racing anxiety I am experiencing, I am having trouble figuring out what is going on (I am reading the same things over and over again but I am not encoding anything or understanding it). Does this mean I have to pay $200 a month just to use Google Maps now? Or is it only $200 for some super-special service. Does this mean that I can't do street-view anymore until I hand over my entire wallet and a little extra? What is the $200 for. Is that the minimum price to use Google Maps for the future, I have no idea. Someone please explain to me.  :wow:  :paranoid:  :no:

Think about it this way: Google charging money for Maps would be suicide for their product.

That whole blog post is for outside developers working with the Google platform. There's not going to be any change for the average end-user.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on May 06, 2018, 07:58:09 PM
Quote from: MNHighwayMan on May 06, 2018, 07:49:28 PM
Quote from: adventurernumber1 on May 06, 2018, 07:37:05 PM
Quote from: US71 on May 06, 2018, 06:53:46 PM
And some bad news
https://developers.googleblog.com/2018/05/introducing-google-maps-platform.html
Wait, I'm just very, very lost. I've been looking at it for 20 minutes, but due to the debilitating, racing anxiety I am experiencing, I am having trouble figuring out what is going on (I am reading the same things over and over again but I am not encoding anything or understanding it). Does this mean I have to pay $200 a month just to use Google Maps now? Or is it only $200 for some super-special service. Does this mean that I can't do street-view anymore until I hand over my entire wallet and a little extra? What is the $200 for. Is that the minimum price to use Google Maps for the future, I have no idea. Someone please explain to me.  :wow:  :paranoid:  :no:

Think about it this way: Google charging money for Maps would be suicide for their product.

That whole blog post is for outside developers working with the Google platform. There's not going to be any change for the average end-user.

Quote from: kkt on May 06, 2018, 07:45:27 PM
That message seems to be aimed at developers who are building their applications on the Google Maps database or API, not just users.  I wouldn't worry.  Agree that it's confusingly-written, though.


Oh, thank goodness. Now I can breathe again.

I cannot tell you how relieved I am to hear this. I have a very bad habit of jumping to conclusions before knowing or understanding the whole story, with my mind clouded by pessimism (which in this case, made me immediately think of and believe the the worst, before knowing the 100% truth). Thank you very much for clearing that up for me.  :nod:  :thumbsup:

Now that really would be insane and ridiculous if Google Maps forced you to pay $200 a month just for usage by the average person. They would have pulled a Photobucket, except even worse.  X-(  :verymad:  :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on May 06, 2018, 10:12:33 PM
I've been following this thread over the past few years, and I have to say that I agree with most if not all of the complaints.  I was reading the link that US71 posted, and now I'm really worried since it looks like removing keyless API access will break KMLMap/ClassyGMap.  I have a link to the old code that still has ClassyGMap branding in my bookmarks bar.  Unless I click the address in a search result, I don't even use maps.google.com.  Even if I do click the address, I usually switch to ClassyGMap.

Since I use an old version of Chrome (I don't like the interface changes in newer versions, yet another thing Google has messed up), Maps is broken for me, and it only supports Lite mode.  A few months ago, the sidebar that appears for a search result started closing itself as soon as the page loads.  Around the same time, they changed embeds to require holding [CTRL] while scrolling to zoom, but that also broke scrolling with the scroll wheel in regular Maps.  For me, I discovered that I actually have to hold [ALT] instead of [CTRL] to zoom on embedded maps.

According to Google, the reasoning behind holding [CTRL] to zoom is to prevent zooming on an embedded map while scrolling on a webpage.  I rarely encountered this issue, and if I did, I just scrolled while not hovering over the map, or dragged the scrollbar in Chrome.  Also, since I'm stuck in Lite mode, I can't even drag a route line on the map, but I can in ClassyGMap.

On a side note, I think that removing keyless access will break Street View embeds on the forum.

Lastly, why does Google keep breaking things?!  ClassyGMap (without all the bells and whistles of regular Maps) can use over 1 GB of RAM in Street View between the tab and GPU process, whereas the old Flash based viewer in Classic Maps used at most 500 MB between the tab and Flash plugin.

Maps isn't the only thing Google has broken.  YouTube's HTML5 player is a good idea, but is horribly broken.  When implemented correctly, HTML5 is great.  On YouTube, clicking in the video area or using the spacebar to pause can crash the tab.  Also, it's fairly common for videos to not play and endlessly buffer.  Since I'm using an old version of Chrome, I can right-click twice and open the MP4 video in a new tab, which still loads forever, but plays fine after removing the "pltype" parameter from the URL.

The latest thing I'm worried about is the Polymer redesign of YouTube.  When I clicked the link to try it, it was a mostly blank page with a few images and no video.  I noticed that YouTube channels have begun to have "disable_polymer=1" at the end of the URL, and that worries me.  Classic Maps had "output=classic", then it was gone, then YouTube had "nohtml5=1" which was removed, and that pattern tells me that the current YouTube design will eventually be removed.

Of course, Google's response to the glitches and errors I've mentioned in this post would be "upgrade your browser", but like I mentioned, I don't like the new Chrome design.  What about people that can't upgrade?  Imagine if the DOT or DMV said "your car is no longer compatible with the road network" and that you had to purchase a new car to continue driving.
Title: Re: Google Maps just fucking SUCKS now
Post by: Thing 342 on May 07, 2018, 02:50:22 AM

Quote from: Michael on May 06, 2018, 10:12:33 PMOf course, Google's response to the glitches and errors I've mentioned in this post would be "upgrade your browser", but like I mentioned, I don't like the new Chrome design.  What about people that can't upgrade? 
Would like to note to the audience that purposefully not upgrading your browser because you don't like an interface change is a terrible idea and great way to have your computer compromised. There's a very good reason why browser and OS makers are so pushy when it comes to installing updates.

QuoteImagine if the DOT or DMV said "your car is no longer compatible with the road network" and that you had to purchase a new car to continue driving.
This ... already happened? Remember seat belt legislation?
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on May 07, 2018, 07:04:41 AM
Quote from: Thing 342 on May 07, 2018, 02:50:22 AM

Quote from: Michael on May 06, 2018, 10:12:33 PMOf course, Google's response to the glitches and errors I've mentioned in this post would be "upgrade your browser", but like I mentioned, I don't like the new Chrome design.  What about people that can't upgrade? 
Would like to note to the audience that purposefully not upgrading your browser because you don't like an interface change is a terrible idea and great way to have your computer compromised. There's a very good reason why browser and OS makers are so pushy when it comes to installing updates.

QuoteImagine if the DOT or DMV said "your car is no longer compatible with the road network" and that you had to purchase a new car to continue driving.
This ... already happened? Remember seat belt legislation?

Um, not exactly.  Anything new is mandated only for that model year vehicle or newer, older vehicles are exempt.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 07, 2018, 08:04:12 PM
There are other reasons for having an out of date browser, such as your IT department at work not pushing out the later updates or the case of my Chromebook, which fell out of support simply due to its age (even though the hardware works perfectly fine; planned obsolescence at its finest).  But overall I agree regarding not staying with the old version.  Chrome isn't IE, where old versions continued to get security updates even after the release of a new version.

Speaking of the hold CTRL to zoom thing in embeds, that has to be one of the more annoying things Google has ever done.

I used KMLMap briefly as a way of avoiding the new look, but eventually the new look migrated to the services using the API, and not only that, even the alternate schemes were affected.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on May 07, 2018, 08:10:34 PM
Quote from: vdeane on May 07, 2018, 08:04:12 PM
There are other reasons for having an out of date browser, such as your IT department at work not pushing out the later updates or the case of my Chromebook, which fell out of support simply due to its age (even though the hardware works perfectly fine; planned obsolescence at its finest).  But overall I agree regarding not staying with the old version.  Chrome isn't IE, where old versions continued to get security updates even after the release of a new version.

Speaking of the hold CTRL to zoom thing in embeds, that has to be one of the more annoying things Google has ever done.

I used KMLMap briefly as a way of avoiding the new look, but eventually the new look migrated to the services using the API, and not only that, even the alternate schemes were affected.

Or simply having a browser that doesn't auto-update and not wanting a newer version.  If it ain't broke, don't fix it.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 07, 2018, 08:54:51 PM
Quote from: 20160805 on May 07, 2018, 08:10:34 PM
Or simply having a browser that doesn't auto-update and not wanting a newer version.  If it ain't broke, don't fix it.
But then you're deliberately leaving your computer vulnerable to security vulnerabilities, and on an application what is used for accessing the wild west that is the world wide web.  Hope you don't mind a computer infected with malware.  Getting infected is as easy as having the wrong ad load on a site you're browsing.  Don't make it any easier for the bad guys to do more damage by leaving known security holes open.  Malware authors will often write code specifically targeting patched vulnerabilities in the hope of infecting the computers of people like you.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 13, 2018, 08:19:50 PM
Today, I did something I was trying to do in the past but failed with again. I tried to zoom in on the Valley Stream State Park Road, that runs between Parking Field 1, and the eastbound Southern State Parkway on-ramps at Exit 15, so I could try to figure out if, when, and how drivers can get into Parking Field 2, and it kept zipping me onto the Parkway.

There's a gate to that parking lot on Henry Street which is for exits only, but the only other access I can find is from that park road, which also has a Do Not Enter sign going in. So just how anyone could possibly get in there legally is a total mystery as far as I'm concerned. I was hoping GSV would show me some evidnce that it may be temporary or of something else going on, but it keeps dragging me away.



Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 14, 2018, 12:49:04 PM
That's because the street view car never drove on the portion of road directly in front of the lot.  Both directions the car went right onto the parkway.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 14, 2018, 10:08:43 PM
Quote from: Brandon on May 07, 2018, 07:04:41 AM
Quote from: Thing 342 on May 07, 2018, 02:50:22 AM
Quote from: Michael on May 06, 2018, 10:12:33 PMOf course, Google's response to the glitches and errors I've mentioned in this post would be "upgrade your
Imagine if the DOT or DMV said "your car is no longer compatible with the road network" and that you had to purchase a new car to continue driving.

This ... already happened? Remember seat belt legislation?

Um, not exactly.  Anything new is mandated only for that model year vehicle or newer, older vehicles are exempt.

Because cars are a large expense, that most people can't afford to just throw away whenever a new safety feature comes out.

On the other hand, browsers don't cost shit. So not upgrading is really stupid.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 19, 2018, 05:02:39 PM
Quote from: vdeane on May 14, 2018, 12:49:04 PM
That's because the street view car never drove on the portion of road directly in front of the lot.  Both directions the car went right onto the parkway.
So I guess I'm going to have to call them up directly on the phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: fillup420 on May 20, 2018, 09:09:56 AM
It seems someone has changed the entirety of US 15 to be labeled as "US Hwy 15/501" . In central NC, that is correct. But in Pennsylvania, it is not. It seems that edit took out all the 15 shields with it too.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on May 20, 2018, 12:48:59 PM
Quote from: vdeane on May 07, 2018, 08:54:51 PMBut then you're deliberately leaving your computer vulnerable to security vulnerabilities, and on an application what is used for accessing the wild west that is the world wide web.  Hope you don't mind a computer infected with malware.  Getting infected is as easy as having the wrong ad load on a site you're browsing.  Don't make it any easier for the bad guys to do more damage by leaving known security holes open.  Malware authors will often write code specifically targeting patched vulnerabilities in the hope of infecting the computers of people like you.

Quote from: jakeroot on May 14, 2018, 10:08:43 PMOn the other hand, browsers don't cost shit. So not upgrading is really stupid.

I respectfully disagree.  On my primary computer, I keep automatic updating disabled to the extent that I can and drag my feet on updating, since I generally find that with my usage patterns, it is far more likely that essential functionality will be broken than that I will be infected with malware.

I do use an ad-blocking HOSTS file, which is very effective at stopping malicious code hosted on ad servers and will not attract "Disable AdBlock Plus" prompts.

My Android phone is not rooted and cannot easily be either rooted or maintained in a rooted state, so I cannot install an ad-blocking HOSTS file on it.  Consequently, I have far more problems with unwanted code execution on it (generally as a result of clicking on the wrong piece of clickbait in Facebook), even though the OS and all apps auto-update.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 20, 2018, 02:31:36 PM
Quote from: J N Winkler on May 20, 2018, 12:48:59 PM
I respectfully disagree.  On my primary computer, I keep automatic updating disabled to the extent that I can and drag my feet on updating, since I generally find that with my usage patterns, it is far more likely that essential functionality will be broken than that I will be infected with malware.

I have done this with Windows updates, because several games that I play have been broken by previous updates. Not by small updates. The bigger ones that change functionality.

Security updates? I've never experienced broken functionality as the result of these.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 20, 2018, 02:31:58 PM
Quote from: fillup420 on May 20, 2018, 09:09:56 AM
It seems someone has changed the entirety of US 15 to be labeled as "US Hwy 15/501" . In central NC, that is correct. But in Pennsylvania, it is not. It seems that edit took out all the 15 shields with it too.
Yeah, I saw that. I was wondering who screwed that up.
:confused:
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on May 20, 2018, 02:46:11 PM
Quote from: jakeroot on May 20, 2018, 02:31:36 PMI have done this with Windows updates, because several games that I play have been broken by previous updates. Not by small updates. The bigger ones that change functionality.

Security updates? I've never experienced broken functionality as the result of these.

I just wait on updates of all types--with Microsoft now doing update rollups, it is not worth the trouble of separating out security updates for prompt application.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 20, 2018, 02:51:03 PM
Quote from: J N Winkler on May 20, 2018, 02:46:11 PM
Quote from: jakeroot on May 20, 2018, 02:31:36 PMI have done this with Windows updates, because several games that I play have been broken by previous updates. Not by small updates. The bigger ones that change functionality.

Security updates? I've never experienced broken functionality as the result of these.

I just wait on updates of all types--with Microsoft now doing update rollups, it is not worth the trouble of separating out security updates for prompt application.
Man, I wish I could reverse a recent Microsoft update, because they took out a lot of what I had before, including passwords (one of which was a Google password that they kept changing all the time). And this isn't the first time anything like this has happened either!  :verymad:

Title: Re: Google Maps just fucking SUCKS now
Post by: csw on May 25, 2018, 09:59:03 AM
Anyone know why I-37 isn't shown as an actual interstate?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 25, 2018, 01:01:37 PM
Quote from: csw on May 25, 2018, 09:59:03 AM
Anyone know why I-37 isn't shown as an actual interstate?

Because Texas is changing its number to I-69N ???
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on May 25, 2018, 04:48:17 PM
Quote from: kphoger on May 25, 2018, 01:01:37 PM
Quote from: csw on May 25, 2018, 09:59:03 AM
Anyone know why I-37 isn't shown as an actual interstate?

Because Texas is changing its number to I-69N ???

And I guess I-2 will become I-69S now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on May 27, 2018, 12:43:22 PM
Quote from: J N Winkler on May 20, 2018, 12:48:59 PM
Quote from: vdeane on May 07, 2018, 08:54:51 PMBut then you're deliberately leaving your computer vulnerable to security vulnerabilities, and on an application what is used for accessing the wild west that is the world wide web.  Hope you don't mind a computer infected with malware.  Getting infected is as easy as having the wrong ad load on a site you're browsing.  Don't make it any easier for the bad guys to do more damage by leaving known security holes open.  Malware authors will often write code specifically targeting patched vulnerabilities in the hope of infecting the computers of people like you.

Quote from: jakeroot on May 14, 2018, 10:08:43 PMOn the other hand, browsers don't cost shit. So not upgrading is really stupid.

I respectfully disagree.  On my primary computer, I keep automatic updating disabled to the extent that I can and drag my feet on updating, since I generally find that with my usage patterns, it is far more likely that essential functionality will be broken than that I will be infected with malware.

I do use an ad-blocking HOSTS file, which is very effective at stopping malicious code hosted on ad servers and will not attract "Disable AdBlock Plus" prompts.

My Android phone is not rooted and cannot easily be either rooted or maintained in a rooted state, so I cannot install an ad-blocking HOSTS file on it.  Consequently, I have far more problems with unwanted code execution on it (generally as a result of clicking on the wrong piece of clickbait in Facebook), even though the OS and all apps auto-update.

The part I bolded is the case for me too.  I also use an ad blocking hosts file (this one (http://winhelp2002.mvps.org/hosts.htm) to be exact).




Last night, I noticed this page (https://support.google.com/maps/answer/3031966) mentioned that "Maps in Lite Mode is currently being upgraded to full Google Maps".  Does that mean Lite Mode won't exist anymore at some point?  A little while ago, I was spoofing my useragent in Firefox, and forgot to change it back, and Bing Maps wouldn't even load.  I'm afraid this will become the case for Google Maps since Lite Mode is being "upgraded".
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on June 02, 2018, 08:32:10 PM
I noticed a weird gap in the Street View on US 1/City Avenue near Bala Cynwyd between Old Lancaster Road and 47th Street (https://goo.gl/maps/2vpvd5bohW32). There's plenty of coverage of the cross streets and even some of the business driveways along the road, but they all just stop abruptly. Anyone know what possible reason there might be?
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on June 04, 2018, 10:45:56 AM
Quote from: Roadsguy on June 02, 2018, 08:32:10 PM
I noticed a weird gap in the Street View on US 1/City Avenue near Bala Cynwyd between Old Lancaster Road and 47th Street (https://goo.gl/maps/2vpvd5bohW32). There's plenty of coverage of the cross streets and even some of the business driveways along the road, but they all just stop abruptly. Anyone know what possible reason there might be?

I just checked, I don't see the issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on June 04, 2018, 10:51:29 AM
Quote from: DeaconG on June 04, 2018, 10:45:56 AM
Quote from: Roadsguy on June 02, 2018, 08:32:10 PM
I noticed a weird gap in the Street View on US 1/City Avenue near Bala Cynwyd between Old Lancaster Road and 47th Street (https://goo.gl/maps/2vpvd5bohW32). There's plenty of coverage of the cross streets and even some of the business driveways along the road, but they all just stop abruptly. Anyone know what possible reason there might be?

I just checked, I don't see the issue.

Drag the Street View guy without letting go. Notice that a section of US 1 isn't highlighted.
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on June 04, 2018, 11:10:26 AM
Quote from: 1 on June 04, 2018, 10:51:29 AM
Quote from: DeaconG on June 04, 2018, 10:45:56 AM
Quote from: Roadsguy on June 02, 2018, 08:32:10 PM
I noticed a weird gap in the Street View on US 1/City Avenue near Bala Cynwyd between Old Lancaster Road and 47th Street (https://goo.gl/maps/2vpvd5bohW32). There's plenty of coverage of the cross streets and even some of the business driveways along the road, but they all just stop abruptly. Anyone know what possible reason there might be?

I just checked, I don't see the issue.

Drag the Street View guy without letting go. Notice that a section of US 1 isn't highlighted.

Okay, I see it now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 04, 2018, 10:06:31 PM
It looks like "Lite" mode is no more.  My "Lite" links are dumping me now right into regular snail-slow Maps.  A quick search found a new "2D" mode option, but it was fairly slow as well.  Has anyone found a back door into "Lite" mode, just like we had to do awhile back for Classic Maps?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 04, 2018, 10:23:36 PM
Didn't know Lite mode was still a thing. Thought they dumped it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on June 05, 2018, 04:49:07 PM
About a week ago, the words "Lite mode" disappeared, and scrolling to zoom started working on my old version of Chrome I mentioned earlier in the thread.  I can now zoom with the scroll wheel and plus/minus keys, but there's nothing else on the page, and I can't use the menu in the upper left corner.  If I spoof my useragent to Firefox, everything works fine except scrolling to zoom (even holding [ALT] or [CTRL]), and there are some minor alignment issues with the icons in the directions pane (which is normal on my version of Chrome).  Scrolling to zoom is broken in Street View as well.  Even in the old ClassyGMap I use, scrolling in Street View is broken if I use a Firefox useragent.  The useragent spoofer I use has Firefox 3.5 as the earliest version to spoof without adding a custom useragent, and that version works fine on Google Maps even though it'll be 10 years old at the end of the month.

Oddly, I was able to use 11 custom points on a route instead of the 10 that has been the limit.

These improvements give me a bit of hope for Google Maps not sucking anymore!
Title: Re: Google Maps just fucking SUCKS now
Post by: sbeaver44 on June 05, 2018, 06:53:16 PM
US 15 in Pennsylvania has suddenly become US 15/501 everywhere.  I've been noticing it for a few weeks.  I was in Gettysburg and "Home via US 15/501 N" appeared.  I live near Harrisburg...

Nexus 6P

Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on June 08, 2018, 04:02:00 PM
There may no longer be a proper "Lite mode", but I've been having some driver issues leading to occasional WebGL crashes, which breaks Google Maps until I restart Chrome. When that happens, it's stuck in "2D mode", and I can no longer enable 3D view. This is also what appears for devices that just straight-up can't run the full map.
Title: Re: Google Maps just fucking SUCKS now
Post by: chays on June 08, 2018, 04:30:05 PM
One thing that is bugging me is that Maps is prominently showing certain POIs on the display when I don't want to necessarily see them.  In the past, I have used Google Maps extensively to look for hotels when I am planning a trip.  Now, it seems that hotel points cover the screen too extensively, even though I'm not currently looking for them.  It is an annoyance in that it places hotels at the expense of other types of features I might like to see.
Title: Re: Google Maps just fucking SUCKS now
Post by: Kulerage on June 08, 2018, 09:03:47 PM
Quote from: sbeaver44 on June 05, 2018, 06:53:16 PM
US 15 in Pennsylvania has suddenly become US 15/501 everywhere.  I've been noticing it for a few weeks.  I was in Gettysburg and "Home via US 15/501 N" appeared.  I live near Harrisburg...

Nexus 6P
I can't believe this is STILL the case. Usually Google is better at fixing prominent issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on June 08, 2018, 09:05:25 PM
Quote from: Kulerage on June 08, 2018, 09:03:47 PM
Quote from: sbeaver44 on June 05, 2018, 06:53:16 PM
US 15 in Pennsylvania has suddenly become US 15/501 everywhere.  I've been noticing it for a few weeks.  I was in Gettysburg and "Home via US 15/501 N" appeared.  I live near Harrisburg...

Nexus 6P
I can't believe this is STILL the case. Usually Google is better at fixing prominent issues.

From what I remember, I-6 in Maine (should have been ME 6) lasted for over a year.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on June 11, 2018, 09:03:59 PM
Quote from: Roadsguy on June 02, 2018, 08:32:10 PM
I noticed a weird gap in the Street View on US 1/City Avenue near Bala Cynwyd between Old Lancaster Road and 47th Street (https://goo.gl/maps/2vpvd5bohW32). There's plenty of coverage of the cross streets and even some of the business driveways along the road, but they all just stop abruptly. Anyone know what possible reason there might be?

I have started to see this a fair bit the past few weeks, and I haven't noticed any sort of pattern with it. I've seen bridges, highways, and residential roads have this problem. My only theory is that Google has adjusted the location of the roads slightly, and it no longer thinks the street view that was there previously is located on that road.
Title: Re: Google Maps just fucking SUCKS now
Post by: Highway63 on June 12, 2018, 06:02:48 PM
Quote from: Kulerage on June 08, 2018, 09:03:47 PM
I can't believe this is STILL the case. Usually Google is better at fixing prominent issues.
Iowa's zombie highways of the Second Great Decommissioning say hi. (https://www.google.com/maps/place/42%C2%B000'00.0%22N+92%C2%B000'00.0%22W/@42,-92.0700378,12z/data=!4m5!3m4!1s0x0:0x0!8m2!3d42!4d-92) (Note, too, that IA 199 remains extended in the wrong place.)
Title: Re: Google Maps just fucking SUCKS now
Post by: Skye on June 15, 2018, 03:32:30 PM
I often like to use the maps feature that comes with Windows 10.  You have to go online to download the maps, complete with a search feature (for free) and once you do, you can access any downloaded maps while offline.  There are plenty of problems with these though.  I recently typed in "Rochester, NY" into the search bar and the map put me somewhere between the Catskills and Poughkeepsie.  There are plenty of other similar errors and issues with that.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on June 15, 2018, 03:36:59 PM
Quote from: Skye on June 15, 2018, 03:32:30 PM
I recently typed in "Rochester, NY" into the search bar and the map put me somewhere between the Catskills and Poughkeepsie.  There are plenty of other similar errors and issues with that.

There are two Rochesters in New York.

https://en.wikipedia.org/wiki/Rochester,_Ulster_County,_New_York
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on June 15, 2018, 03:37:44 PM
Quote from: Highway63 on June 12, 2018, 06:02:48 PM
Quote from: Kulerage on June 08, 2018, 09:03:47 PM
I can't believe this is STILL the case. Usually Google is better at fixing prominent issues.
Iowa's zombie highways of the Second Great Decommissioning say hi. (https://www.google.com/maps/place/42%C2%B000'00.0%22N+92%C2%B000'00.0%22W/@42,-92.0700378,12z/data=!4m5!3m4!1s0x0:0x0!8m2!3d42!4d-92) (Note, too, that IA 199 remains extended in the wrong place.)

I actually don't mind this, because it makes locating most of the decommissioned routes really easy.
Title: Re: Google Maps just fucking SUCKS now
Post by: NJRoadfan on June 20, 2018, 10:20:06 PM
Quote from: sbeaver44 on June 05, 2018, 06:53:16 PM
US 15 in Pennsylvania has suddenly become US 15/501 everywhere.  I've been noticing it for a few weeks.  I was in Gettysburg and "Home via US 15/501 N" appeared.  I live near Harrisburg...

One of NC's famous multiplexes is slowly taking over.....

The last time this happened also involved a NC highway label. US-64 was labeled as the Knightdale Bypass from end to end.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on June 27, 2018, 06:47:20 PM
There are some errors in the Village of Babylon along NY 27A that have to be changed. It shows the historic former Babylon Town Hall at 47 West Main Street (NY 27A) which is on the northwest corner of West Main Street and Cottage Row. However, they mark two other locations next door to it as being at 47 West Main Street, both of which are wrong. Furthermore, it claims that a local Chase Bank is located behind the former town hall, when in reality it's located on the northeast corner of West Main Street and Cottage Row, across from the old Town Hall.

The erroneous map here (https://www.google.com/maps/place/40%C3%82%C2%B041'47.1%22N+73%C3%82%C2%B019'26.8%22W/@40.6971813,-73.3208757,1414m/data=!3m1!1e3!4m5!3m4!1s0x0:0x0!8m2!3d40.696417!4d-73.324111?hl=en)


But thanks to Microsoft's fucked up updates that they forced on me back in May, I can't sign in and correct those errors!

:banghead: :angry:



Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 27, 2018, 07:59:09 PM
That stupid left column that appears when you first load the page appears to have been fully rolled out.  I can't get rid of it by loading a new incognito session any more.  Why does Google have to keep adding such annoying things?
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on June 27, 2018, 08:47:05 PM
Quote from: vdeane on June 27, 2018, 07:59:09 PM
That stupid left column that appears when you first load the page appears to have been fully rolled out.  I can't get rid of it by loading a new incognito session any more.  Why does Google have to keep adding such annoying things?

Because we're less and less supposed to use it like a traditional paper map.

Also, feature creep (https://en.wikipedia.org/wiki/Feature_creep).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 28, 2018, 07:28:50 PM
Quote from: MNHighwayMan on June 27, 2018, 08:47:05 PM
Quote from: vdeane on June 27, 2018, 07:59:09 PM
That stupid left column that appears when you first load the page appears to have been fully rolled out.  I can't get rid of it by loading a new incognito session any more.  Why does Google have to keep adding such annoying things?

Because we're less and less supposed to use it like a traditional paper map.

Also, feature creep (https://en.wikipedia.org/wiki/Feature_creep).
But why do they have to rub salt in the wound?  The sidebar does literally nothing that you can't do elsewhere.  And where are those of us who DO use it as a paper map that can give us travel times and street view supposed to go?  The sad thing is, even though Google Maps sucks more and more every single time they do an update, they're still several orders of magnitude better than the next-best online map simply because the others either implement features like street view and driving directions very badly (travel times on other providers are way off, and even though Google doesn't provide nearly enough points to alter routes, altering routes is even harder on every other map source) or not at all (only Bing has a street view equivalent, its imagery is updated rarely if ever, and it's a crapshoot as to whether an area will have coverage at all).
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on June 28, 2018, 10:04:13 PM
With regard to Google vs Bing for street view, I actually found Bing's to be superior, at least for my home county. Google only covered the main roads and a few streets in town. But Bing, on the other hand, not only did the entire city, but also just about every back road in the entire county. (Isanti County, Minnesota, for the curious.) Google's coverage hardly even compares to that–the only thing they have the upper hand on, there, is image quality, which is slightly better (provided the images aren't from 2007/08, in which case Bing beats them on that, too!)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 29, 2018, 12:40:55 PM
Bing tends to be pretty pervasive where available, probably because they do it specifically by county, whereas Google does not.  Although their coverage in the area, now that I look at it, makes me think they also divide by town.  There are some pretty major holes in their coverage because of this.  Plus it's US only, I don't think they update often (most everything around here is from 2011), if ever.  Plus it can be slower than Google in terms of computer performance, and there's a bug where you can get stuck in a loop if you try to navigate within streetside.
Title: Re: Google Maps just fucking SUCKS now
Post by: hbelkins on June 29, 2018, 02:32:32 PM
What's needed is a good mobile app that shows county boundaries, for those of us who sometimes go traipsing off little local roads to visit a new county.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on June 29, 2018, 03:00:44 PM
People have been asking for county lines from Google for years and they just refuse to incorporate them beyond the simple boundary search that can be done now.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on June 29, 2018, 06:37:57 PM
Quote from: vdeane on June 29, 2018, 12:40:55 PM
Bing tends to be pretty pervasive where available, probably because they do it specifically by county, whereas Google does not.  Although their coverage in the area, now that I look at it, makes me think they also divide by town.  There are some pretty major holes in their coverage because of this.  Plus it's US only, I don't think they update often (most everything around here is from 2011), if ever.  Plus it can be slower than Google in terms of computer performance, and there's a bug where you can get stuck in a loop if you try to navigate within streetside.

Yeah, Bing's controls are a bit clunky, and I did come across that "stuck in a loop" bug, once, which was annoying. It kept happening in the same spot, though (even after closing my browser and clearing the cache) which leads me to believe it's an error within the navigation/map data itself and not some overall interface bug (or a combination of both, I suppose). The images for my hometown area are from 2015, though, so it appears that they're slowly but surely filling in the holes!
Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on July 01, 2018, 10:21:24 AM
Anybody know the average time between GSV "recording" a street they drove down and the time it takes them to add it to the website?  I got in front of those elusive cars not too long ago on a street that was last recorded in 2012. 
Title: Re: Google Maps just fucking SUCKS now
Post by: Kulerage on July 01, 2018, 09:26:50 PM
The Red Outline for countries when you click them does not appear anymore. Normally this isn't a problem, but some of them have weird exclaves that are not easy to figure out. Especially when the country name doesn't always appear at the border
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 02, 2018, 02:03:22 PM
Quote from: Kulerage on July 01, 2018, 09:26:50 PM
The Red Outline for countries when you click them does not appear anymore. Normally this isn't a problem, but some of them have weird exclaves that are not easy to figure out. Especially when the country name doesn't always appear at the border

That might be why Google doesn't want to do it.  They don't want to be responsible if someone depends on that information for what jurisdiction they're in for laws, zoning, tax rates, etc., and it turns out it's wrong.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 03, 2018, 08:17:58 PM
Does anybody else get a massive sidebar instead just a search box now?  I find it to be a huge waste of space.  My laptop doesn't have a high resolution display to support this.  I get that people are moving towards higher resolution displays (my monitors at work are 1080p and I don't mind it as much there), but my laptop which is only a few years old has a 1366x768...

(https://cdn.pbrd.co/images/HsOL2Fn.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 03, 2018, 08:23:17 PM
Just click the left arrow on the right of the sidebar and it will go away.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on July 03, 2018, 08:40:23 PM
Quote from: 1 on July 03, 2018, 08:23:17 PM
Just click the left arrow on the right of the sidebar and it will go away.

It will, until you open Google Maps again. Seriously, why can't it remember that I want it closed? Why do I have to close it every single time I open a new Maps tab?
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on July 03, 2018, 08:46:35 PM
Quote from: MNHighwayMan on July 03, 2018, 08:40:23 PM
Quote from: 1 on July 03, 2018, 08:23:17 PM
Just click the left arrow on the right of the sidebar and it will go away.

It will, until you open Google Maps again. Seriously, why can't it remember that I want it closed? Why do I have to close it every single time I open a new Maps tab?

Because, as was pointed out a few days ago, we aren't typical users. Most people opening Google Maps are actually looking for the things in that sidebar. It's annoying for us, yes, but unfortunately that's just how these things work. In my day job I'm a web developer, and we certainly try to optimize for the most popular workflows whenever possible.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on July 03, 2018, 09:26:09 PM
Quote from: thenetwork on July 01, 2018, 10:21:24 AM
Anybody know the average time between GSV "recording" a street they drove down and the time it takes them to add it to the website?  I got in front of those elusive cars not too long ago on a street that was last recorded in 2012.

From all my observations of doing street-view very often for almost a decade, I want to say that the typical time between the capture of imagery and the uploading of the imagery to street-view on the site usually hovers around the ballpark of half a year (several months).
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on July 03, 2018, 09:34:49 PM
Quote from: adventurernumber1 on July 03, 2018, 09:26:09 PM
Quote from: thenetwork on July 01, 2018, 10:21:24 AM
Anybody know the average time between GSV "recording" a street they drove down and the time it takes them to add it to the website?  I got in front of those elusive cars not too long ago on a street that was last recorded in 2012.
From all my observations of doing street-view very often for almost a decade, I want to say that the typical time between the capture of imagery and the uploading of the imagery to street-view on the site usually hovers around the ballpark of half a year (several months).

That sounds about right. I've seen some from November 2017, but not any newer than that. Of course, winter isn't a good time for Street View around here, but there very easily could be more recent imagery in other areas of the country.

I also recall imagery from last summer being uploaded by around Thanksgiving, which tends to confirm the suggestion of a few months.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 03, 2018, 10:29:23 PM
I have 1920 x 1080 screen resolution on my primary laptop and I have little enthusiasm for the left sidebar.  I find myself clicking all the time to hide it so that the full map area is available for panning and zooming.  I have road-tested the search function and I can see how it would be useful for finding budget accommodation on the road, but unless I was down to the wire for overnight accommodation, I would still want to cross-reference with TripAdvisor.

The hotel search does update the results when the map is panned.  This is useful for large metro areas with tight lodging markets, like Chicago.  Booking.com has similar functionality but it is not as seamlessly integrated.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on July 03, 2018, 11:41:42 PM
Quote from: webny99 on July 03, 2018, 09:34:49 PM
Quote from: adventurernumber1 on July 03, 2018, 09:26:09 PM
Quote from: thenetwork on July 01, 2018, 10:21:24 AM
Anybody know the average time between GSV "recording" a street they drove down and the time it takes them to add it to the website?  I got in front of those elusive cars not too long ago on a street that was last recorded in 2012.
From all my observations of doing street-view very often for almost a decade, I want to say that the typical time between the capture of imagery and the uploading of the imagery to street-view on the site usually hovers around the ballpark of half a year (several months).

That sounds about right. I've seen some from November 2017, but not any newer than that. Of course, winter isn't a good time for Street View around here, but there very easily could be more recent imagery in other areas of the country.

I also recall imagery from last summer being uploaded by around Thanksgiving, which tends to confirm the suggestion of a few months.

A Google car came by my house in 2013 and the Streetview image still hasn't updated. The only Streetview image is from December 2007.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 04, 2018, 02:40:45 AM
Quote from: MNHighwayMan on July 03, 2018, 08:40:23 PM
Quote from: 1 on July 03, 2018, 08:23:17 PM
Just click the left arrow on the right of the sidebar and it will go away.

It will, until you open Google Maps again. Seriously, why can't it remember that I want it closed? Why do I have to close it every single time I open a new Maps tab?

Just hit the "HIDE" button in the bottom left, and it will stay hidden until you log out. If you're not logged in, I think it'll remember the setting through a cookie, but I'm not sure.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 04, 2018, 08:54:23 AM
Quote from: jakeroot on July 04, 2018, 02:40:45 AM
Quote from: MNHighwayMan on July 03, 2018, 08:40:23 PM
Quote from: 1 on July 03, 2018, 08:23:17 PM
Just click the left arrow on the right of the sidebar and it will go away.

It will, until you open Google Maps again. Seriously, why can't it remember that I want it closed? Why do I have to close it every single time I open a new Maps tab?

Just hit the "HIDE" button in the bottom left, and it will stay hidden until you log out. If you're not logged in, I think it'll remember the setting through a cookie, but I'm not sure.
But I'd still like to have the search box.  That's the problem with this design.  Having a search box there was always helpful, but having that huge sidebar going along with it is just annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 04, 2018, 12:20:06 PM
Quote from: ipeters61 on July 04, 2018, 08:54:23 AM
Quote from: jakeroot on July 04, 2018, 02:40:45 AM
Quote from: MNHighwayMan on July 03, 2018, 08:40:23 PM
Quote from: 1 on July 03, 2018, 08:23:17 PM
Just click the left arrow on the right of the sidebar and it will go away.

It will, until you open Google Maps again. Seriously, why can't it remember that I want it closed? Why do I have to close it every single time I open a new Maps tab?

Just hit the "HIDE" button in the bottom left, and it will stay hidden until you log out. If you're not logged in, I think it'll remember the setting through a cookie, but I'm not sure.
But I'd still like to have the search box.  That's the problem with this design.  Having a search box there was always helpful, but having that huge sidebar going along with it is just annoying.

I'm not sure what you're talking about. Don't use the arrow pointing left in the top right of the sidebar. That just temporarily hides everything including the search box. Hitting the "HIDE" button in the bottom left permanently hides everything except the search box.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on July 04, 2018, 03:49:47 PM
I just tried what jakeroot is talking about, and it works - at least until you "X" out of the tab. I clicked the "HIDE" button at the very bottom of the panel, and it got rid of it, but the search bar still existed.

That's really helpful. Thanks!  :thumbsup:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 04, 2018, 04:06:29 PM
Quote from: adventurernumber1 on July 04, 2018, 03:49:47 PM
I just tried what jakeroot is talking about, and it works - at least until you "X" out of the tab. I clicked the "HIDE" button at the very bottom of the panel, and it got rid of it, but the search bar still existed.

That's really helpful. Thanks!  :thumbsup:

No problem. Are you logged in to Google? The sidebar has not come back on for me for several days since I turned it off, but I am always logged in.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on July 04, 2018, 04:46:16 PM
Quote from: jakeroot on July 04, 2018, 04:06:29 PM
Quote from: adventurernumber1 on July 04, 2018, 03:49:47 PM
I just tried what jakeroot is talking about, and it works - at least until you "X" out of the tab. I clicked the "HIDE" button at the very bottom of the panel, and it got rid of it, but the search bar still existed.

That's really helpful. Thanks!  :thumbsup:

No problem. Are you logged in to Google? The sidebar has not come back on for me for several days since I turned it off, but I am always logged in.

I am logged into Google. That explains why the sidebar was still gone even after I had "X-ed" out of the tab then opened Google Maps back up. That really is useful.  :nod:
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 04, 2018, 05:34:09 PM
Quote from: jakeroot on July 04, 2018, 04:06:29 PM
Quote from: adventurernumber1 on July 04, 2018, 03:49:47 PM
I just tried what jakeroot is talking about, and it works - at least until you "X" out of the tab. I clicked the "HIDE" button at the very bottom of the panel, and it got rid of it, but the search bar still existed.

That's really helpful. Thanks!  :thumbsup:

No problem. Are you logged in to Google? The sidebar has not come back on for me for several days since I turned it off, but I am always logged in.
Ah okay.  Sorry, I was confused by what you meant when you described it the first time.  Thanks!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 04, 2018, 05:55:29 PM
Quote from: ipeters61 on July 04, 2018, 05:34:09 PM
Ah okay.  Sorry, I was confused by what you meant when you described it the first time.  Thanks!

No worries.




It should be noted that, upon loading Google Maps for the first time, even being logged in, a small half-sidebar will open showing recent searches and nearby POIs, but this will disappear upon clicking or dragging anywhere on the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 04, 2018, 07:54:24 PM
Of course, that doesn't help those of us who do everything (beyond Gmail and YouTube subscriptions) in incognito mode in order to minimize the amount of "personalization" Google can do.  Maybe that's why they make changes like this (and YouTube's autoplay video) - to make doing so really really annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 04, 2018, 07:58:50 PM
I have Google Maps in private browsing (the equivalent of incognito), but it's for a different purpose: so it doesn't clog my history.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 04, 2018, 10:11:05 PM
I'm not getting into this again. Google's job is not to build their products around tin hat folks and those who need to keep their history clear. They're a company with their hands in just about every industry, and the products really only work well when it collects your information. If you don't like that, Google isn't your friend.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 05, 2018, 01:06:28 PM
Quote from: jakeroot on July 04, 2018, 10:11:05 PM
I'm not getting into this again. Google's job is not to build their products around tin hat folks and those who need to keep their history clear. They're a company with with their hands in just about every industry, and the products really only work well when it collects your information. If you don't like that, Google isn't your friend.
It's "tin hat" to prioritize accurate results over Google trying to guess what you want?  When people/computers try to guess what I want, they usually guess wrong!  Unfortunately, it seems that the quality of Google's search results have been going down regardless, but no need to make it even worse.  I'm not typical in more ways than how I use Google Maps - I'd go so far as to say that smartphones were the worse thing to happen to the entire internet, since they brought the masses and a lot of dumbing down of all things computers with them.

Unfortunately, even though Google's paradigm is opposed to mine, they're still the best at everything they do by several orders of magnitude (only Apple and Amazon come close, at least in their spheres of influence, and I have issues with both of them too).

If I had the power to, I'd change things in the following ways:
-Keep roadgeek sites as they are
-Keep Linux as it is
-Keep the switch from Flash to HTML5
-Keep Chrome/Firefox/etc. as they are
-Roll back Google Maps to 2015 (not including data/street view)
-Roll back Gmail to 2012
-Roll back cell phones to 2005
-Roll back Google search to 2002
-Roll back everything else (Google's other products, Windows, etc.) to 2010
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on July 05, 2018, 01:24:09 PM
Quote from: vdeane on July 04, 2018, 07:54:24 PM
Of course, that doesn't help those of us who do everything (beyond Gmail and YouTube subscriptions) in incognito mode in order to minimize the amount of "personalization" Google can do.  Maybe that's why they make changes like this (and YouTube's autoplay video) - to make doing so really really annoying.

I think that in the grand scheme of things, people that use incognito mode or clear out their browser history on a daily or regular basis are the vast minority of users, and are accustomed to needing to reset things on a regular basis whether it be typing in usernames and passwords or refining the screen to what one likes.  Honestly, this is what people actually want when using those modes. 

If Google saved your screen preference history, it would immediately draw into question what other histories they are actually saving about you, even if you don't realize it.  Maybe you don't want Google to know where you live, but after a while it's figured it out enough where if you do trying searching for something, it'll discreetly mention the places near your home first if you don't specify a location.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 05, 2018, 01:27:58 PM
Quote from: vdeane on July 05, 2018, 01:06:28 PM
If I had the power to, I'd change things in the following ways:
-Keep roadgeek sites as they are
-Keep Linux as it is
-Keep the switch from Flash to HTML5
-Keep Chrome/Firefox/etc. as they are
-Roll back Google Maps to 2015 (not including data/street view)
-Roll back Gmail to 2012
-Roll back cell phones to 2005
-Roll back Google search to 2002
-Roll back everything else (Google's other products, Windows, etc.) to 2010

How long would you keep those things rolled back?

My experience with letting Google assess my search results has been quite positive. The few ads I do see do seem decently relatable. Suggested videos in YouTube are always stuff I want to watch. Google Play Music is always suggesting new music, much of it stuff I don't mind at all.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 05, 2018, 01:55:24 PM
Quote from: jeffandnicole on July 05, 2018, 01:24:09 PM
If Google saved your screen preference history, it would immediately draw into question what other histories they are actually saving about you, even if you don't realize it.  Maybe you don't want Google to know where you live, but after a while it's figured it out enough where if you do trying searching for something, it'll discreetly mention the places near your home first if you don't specify a location.
Or maybe they could keep it hidden by default instead of having it as a saved preference.  They already have my location through my ISP, and that one is actually useful.  I just don't need them saving every random town I've looked up due to a thread here, every hypothetical roadtrip (and revisions on real ones), etc.  The things I use incognito for tend to be things where I know full well that my use isn't typical and I don't need that screwing things up (also news sources that have paywalls once you hit a certain number of articles).  Also some force of habit, since I used to do a lot of things incognito because I was trying to keep Chrome's "new tab" page organized a certain way; ever since I bit the bullet and just set the sites I browse first thing as my home tabs, this isn't really necessary, but the habit has largely stuck.

Quote from: jakeroot on July 05, 2018, 01:27:58 PM
How long would you keep those things rolled back?
Depends on whether the developers would resume on a path favoring desktop-using techies or the current one favoring smartphone-addicted masses.

Quote
My experience with letting Google assess my search results has been quite positive. The few ads I do see do seem decently relatable. Suggested videos in YouTube are always stuff I want to watch. Google Play Music is always suggesting new music, much of it stuff I don't mind at all.
I don't really pay attention to ads; actually, Google search ads are some of the few I actually see, since I use AdBlock Plus.  Most of my searches tend to vary from deep questions about society (that invariably Google manages to never find answers to, but sometimes it finds interesting stuff that's kinda to mostly related) to things like how to disable the bios write protect on my Chrombook so I can install Linux on it rather than buy a new (and expensive) laptop (or switch back to my 9 year old Windows 7 laptop for a while; I won't buy another Chromebook because the modern ones lack ethernet ports, which I use when visiting my parents (and some hotels, the rare ones that have ethernet at least) and because they only last 5 years before Google pulls the plug on software updates).  My suggested videos actually manage to be pretty decent, even though everything that isn't a subscription or something to be added to a playlist (which I really use as bookmark folders instead, so Google's latest changes here aren't sitting well with me either) is incognito.  Most of my remaining use is for music that I can't (or will but haven't yet) download on Amazon MP3.  Yep, I'm one of those people who still has an offline music collection, though it's mostly mp3 downloads rather than CDs now.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 05, 2018, 06:26:57 PM
Quote from: vdeane on July 05, 2018, 01:06:28 PM
Quote from: jakeroot on July 04, 2018, 10:11:05 PM
I'm not getting into this again. Google's job is not to build their products around tin hat folks and those who need to keep their history clear. They're a company with with their hands in just about every industry, and the products really only work well when it collects your information. If you don't like that, Google isn't your friend.
It's "tin hat" to prioritize accurate results over Google trying to guess what you want?  When people/computers try to guess what I want, they usually guess wrong!  Unfortunately, it seems that the quality of Google's search results have been going down regardless, but no need to make it even worse.  I'm not typical in more ways than how I use Google Maps - I'd go so far as to say that smartphones were the worse thing to happen to the entire internet, since they brought the masses and a lot of dumbing down of all things computers with them.

Unfortunately, even though Google's paradigm is opposed to mine, they're still the best at everything they do by several orders of magnitude (only Apple and Amazon come close, at least in their spheres of influence, and I have issues with both of them too).

If I had the power to, I'd change things in the following ways:
-Keep roadgeek sites as they are
-Keep Linux as it is
-Keep the switch from Flash to HTML5
-Keep Chrome/Firefox/etc. as they are
-Roll back Google Maps to 2015 (not including data/street view)
-Roll back Gmail to 2012
-Roll back cell phones to 2005
-Roll back Google search to 2002
-Roll back everything else (Google's other products, Windows, etc.) to 2010

I like it.   :clap:

Can we also roll back Microsoft Word to version 5?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 05, 2018, 06:46:08 PM
Quote from: vdeane on July 05, 2018, 01:55:24 PM
Quote from: jakeroot on July 05, 2018, 01:27:58 PM
How long would you keep those things rolled back?

Depends on whether the developers would resume on a path favoring desktop-using techies or the current one favoring smartphone-addicted masses.

The trend has not been to butt-F desktop users. Google, much like Apple or Microsoft, is mostly interested in syncing all of our devices together. This allows you to have many devices, all slightly different in their capabilities and interface, but all pretty well synced up. Any emails you delete disappear on every device, all of your internet history and bookmarks are the same on each device. All of your music, photos, Google Maps labels, and other stuff are the same across each device. This wasn't really happening 10 years ago. Each device was standalone. The only thing that was the same was the internet (you could log into any website on any computer, and obviously it would be as you left it).

Most of us don't seem to have multiple devices. Honestly, a lot of us are technophobes. I don't know why that is, but it just is. On the other hand, I have an Android watch, phone, and tablet, and a desktop Windows 10 machine. Virtually everything (except my music and photos to my watch) is the same on all of my devices, because I allow Google, Amazon, Microsoft, and Samsung to "watch" me. It's not like it's a person seeing what I look at and do. It's a computer, and I'm not afraid of Skynet! It's done nothing except make my life easier.

Thinking about it, I would hate technology if I was one of those "Incognito"-only users. Google, Amazon, Apple, and Microsoft services are best used when continually logged in. If you're not interested in doing that, I certainly can't help you, and neither can any of those companies.

Quote from: kkt on July 05, 2018, 06:26:57 PM
Can we also roll back Microsoft Word to version 5?

What year was that? I'm not familiar with any version 5. It goes 2.0 (1991) to 6.0 (1993). I hope to God you don't really want Word going back that far.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 05, 2018, 08:44:24 PM
Quote from: jakeroot on July 05, 2018, 06:46:08 PMMost of us don't seem to have multiple devices. Honestly, a lot of us are technophobes. I don't know why that is, but it just is. On the other hand, I have an Android watch, phone, and tablet, and a desktop Windows 10 machine. Virtually everything (except my music and photos to my watch) is the same on all of my devices, because I allow Google, Amazon, Microsoft, and Samsung to "watch" me. It's not like it's a person seeing what I look at and do. It's a computer, and I'm not afraid of Skynet! It's done nothing except make my life easier.

I think technophobe is a poor fit for a person who understands, and rejects, the use model on offer.

Quote from: jakeroot on July 05, 2018, 06:46:08 PMThinking about it, I would hate technology if I was one of those "Incognito"-only users. Google, Amazon, Apple, and Microsoft services are best used when continually logged in. If you're not interested in doing that, I certainly can't help you, and neither can any of those companies.

The problem is actually much broader than privacy, which in itself is wider than the concern that giving up information to interact with a free platform amounts to selling an entity with vast economic power the rope it can use to hang you.  At the consumer end, most cloud computing applications are oriented toward facilitating mass consumption, either directly by offering you goods or services you might like to buy, or indirectly by holding content you want to consume behind ads for things you might be interested in buying.  The recent changes to Google Maps are about making it easier to push out consumables like lodging and restaurant meals to you; YouTube autoplay and clip suggestions are all about making it easier to push out ads to you, especially on mobile where ads are unskippable; etc.  For an end user who approaches them with something in mind other than consumption, such as research, or who simply prefers to stand aloof of the consumerist mindset, this is very alienating.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 05, 2018, 08:53:46 PM
Well, I primarily work on my desktop.  I also have a "Chromebook" (now running Linux) so that I can do things like visit the forum and browse on a proper screen size and with a mouse when traveling.  I still have my college laptop, but I hardly ever use it, and honestly the main reason I still have it is because I figured I might as well keep a Windows machine around while the OS is still being updated.  I did also acquiesce and get a smartphone a couple years ago, but mainly I use it to look at Google Maps while on the road (getting lost after missing a turn while looking for a hotel at night is the reason I got it, actually) or glancing at Facebook or something while bored.  I don't really do much else on it, though I did eventually copy my media library over in case my drive to/from Florida got too boring to do without music.  I don't come anywhere close to using even a fraction of my data each month.  Quite frankly, I don't understand those people who use phones or tablets as their primary computer.  How do they manage to do serious work or browsing with such a tiny screen limited interface, and no mouse?

Things are indeed being made more for phones now.  Just look at how many programs and sites have removed features in the name of simplification, and many designed have been made more phone-like, even where it makes no sense for a desktop environment.  Google Maps doesn't allow as many points to be set when modifying driving directions.  Microsoft tried to get rid of the start menu and depreciate the desktop environment completely in Windows 8, and while they did roll this back in Windows 8.1 and Windows 10, the resulting start menu still incorporates a lot of the metro interface, and the visual effects are still more primitive than Windows 7 (Aero Glass was removed).  Office 2010 and later make the file menu full screen even though it functioned just fine in Office 2007 as an actual menu.  User customization is becoming less and less supported.

I still use my devices the way one would 10 years ago.  I can hardly even conceive of another way.  I do use Chrome synchronization, mainly because manually synchronizing bookmarks is annoying, though I do have to be careful - I used to include my college laptop in the sync, and it once resulted in a bunch of old bookmarks popping onto my other computers since they hadn't synced in a while and Google didn't know what to do.  I don't really trust such features to not screw things up.  In my mind, if you want your email to be the same across devices, you should just use webmail instead of a dedicated email client.  I'm also of the firm belief that new technologies shouldn't result in the removal of capabilities.  I don't trust companies not to screw things up.  I've seen too many computer bugs to do so.  Also, I'm a control freak and like to keep everything neat and orderly, to the point of obsession.  The modern way of doing things strikes me as a way of ceding control and embracing chaos.

Quote from: J N Winkler on July 05, 2018, 08:44:24 PM
The problem is actually much broader than privacy, which in itself is wider than the concern that giving up information to interact with a free platform amounts to selling an entity with vast economic power the rope it can use to hang you.  At the consumer end, most cloud computing applications are oriented toward facilitating mass consumption, either directly by offering you goods or services you might like to buy, or indirectly by holding content you want to consume behind ads for things you might be interested in buying.  The recent changes to Google Maps are about making it easier to push out consumables like lodging and restaurant meals to you; YouTube autoplay and clip suggestions are all about making it easier to push out ads to you, especially on mobile where ads are unskippable; etc.  For an end user who approaches them with something in mind other than consumption, such as research, or who simply prefers to stand aloof of the consumerist mindset, this is very alienating.
Agreed.  The Internet is rapidly becoming cable 2.0, and I don't like it one bit.  I remember when we were promised that the internet would free us from such consumerist stuff.  Whether that was a bad prediction or an outright lie is a point for debate.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 06, 2018, 01:56:59 AM
Quote from: J N Winkler on July 05, 2018, 08:44:24 PM
Quote from: jakeroot on July 05, 2018, 06:46:08 PMMost of us don't seem to have multiple devices. Honestly, a lot of us are technophobes. I don't know why that is, but it just is. On the other hand, I have an Android watch, phone, and tablet, and a desktop Windows 10 machine. Virtually everything (except my music and photos to my watch) is the same on all of my devices, because I allow Google, Amazon, Microsoft, and Samsung to "watch" me. It's not like it's a person seeing what I look at and do. It's a computer, and I'm not afraid of Skynet! It's done nothing except make my life easier.

I think technophobe is a poor fit for a person who understands, and rejects, the use model on offer.

I think it's fair to say that those with various phobias understand their fears more than those who have no fear. You know how sometimes, you just can't...look...away? If you understand tech, but refuse to adopt it for various reasons, by all accounts, you're still a technophobe. I don't know of any other words that fit the description.

Quote from: J N Winkler on July 05, 2018, 08:44:24 PM
Quote from: jakeroot on July 05, 2018, 06:46:08 PMThinking about it, I would hate technology if I was one of those "Incognito"-only users. Google, Amazon, Apple, and Microsoft services are best used when continually logged in. If you're not interested in doing that, I certainly can't help you, and neither can any of those companies.

The problem is actually much broader than privacy, which in itself is wider than the concern that giving up information to interact with a free platform amounts to selling an entity with vast economic power the rope it can use to hang you.  At the consumer end, most cloud computing applications are oriented toward facilitating mass consumption, either directly by offering you goods or services you might like to buy, or indirectly by holding content you want to consume behind ads for things you might be interested in buying.  The recent changes to Google Maps are about making it easier to push out consumables like lodging and restaurant meals to you; YouTube autoplay and clip suggestions are all about making it easier to push out ads to you, especially on mobile where ads are unskippable; etc.  For an end user who approaches them with something in mind other than consumption, such as research, or who simply prefers to stand aloof of the consumerist mindset, this is very alienating.

I think you're painting the situation with far too big of a brush stroke. The core functions of our favorite apps, and most features of them, are still there and accessible. The accessing method might have become slightly more complex or less obvious, but most features are still there. Are these various applications geared more towards consumption? Of course, but that's always been their purpose. Youtube has always been about sharing videos, and they've since made it easier to find videos you might be interested in. Google Maps has always been about finding points of interest and navigating to them -- their recent redesigns have simply made it easier for the majority of users to do what they need to do. Back when these apps launched, I guarantee you they would have had many of the same features as their modern counterparts, had their designers had the technology to support the features. It's only recently that these technology has come around.

In my opinion, anyone who feels alienated by consumerism needs to take a step back and understand the world. Virtually all western-style countries are consumer-based societies. If consumers like applications that use their information to make their life easier, you're going to see more applications like that. Evidently, most people like that. Are there, and will there always be outliers who'd rather not be bombarded by suggestions for this or that? Sure, but they are quickly becoming the minority.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 06, 2018, 01:59:13 AM
Quote from: jakeroot on July 05, 2018, 06:46:08 PM
What year was that? I'm not familiar with any version 5. It goes 2.0 (1991) to 6.0 (1993). I hope to God you don't really want Word going back that far.

I was thinking Word for Mac 5.1, released in 1992.

Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 06, 2018, 03:28:02 AM
Quote from: kkt on July 06, 2018, 01:59:13 AM
Quote from: jakeroot on July 05, 2018, 06:46:08 PM
What year was that? I'm not familiar with any version 5. It goes 2.0 (1991) to 6.0 (1993). I hope to God you don't really want Word going back that far.

I was thinking Word for Mac 5.1, released in 1992.

So what made it so great?

This is your last chance to admit any sarcasm.  :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 06, 2018, 04:46:36 AM
Didn't have a whole butload of dubious features that I never use.  The menus didn't constantly mutate.  Wasn't spyware.
Title: Re: Google Maps just fucking SUCKS now
Post by: csw on July 06, 2018, 08:20:48 AM
Quote from: kkt on July 06, 2018, 04:46:36 AM
Didn't have a whole butload of dubious features that I never use.  The menus didn't constantly mutate.  Wasn't spyware.

Are we using the same program? Where is the spyware in Microsoft Word?!

edit: I'm also curious which features you think are "dubious".
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on July 06, 2018, 08:44:17 AM
Quote from: vdeane on July 05, 2018, 08:53:46 PM
Agreed.  The Internet is rapidly becoming cable 2.0, and I don't like it one bit.  I remember when we were promised that the internet would free us from such consumerist stuff.  Whether that was a bad prediction or an outright lie is a point for debate.

I think the internet continues to evolve in ways no one ever saw.  Back in the 80's, cable was envisioned that it would have hundreds of channels and we'd be shopping from those channels.  Cable eventually got to having hundreds of channels, but it took way longer than estimated.  And all those home shopping possibilities?  Aside from the Home Shopping Network and QVC, it never branched much further than that.  The internet took over, and at first was a way to get news and chat with others, and just kept growing. 

Mobile phones were big monstrosities, which at one point were only really useable in one's local area.  Absolutely no one foresaw that a home based computer would eventually be less useful than a 3"x5" handheld phone.  No one foresaw that one of the lesser-used features on a handheld phone would be the actual phone.  We had more of a promise of people living on the moon and Mars, and flying cars by this point.

So, did anyone really foresee that the internet would basically be a way to shop?  No way.  It would basically be the same as trying to tell us how things will be 25 years from now.  We can all try to predict what will happen, but chances are we'll be either wrong, or will have to skew our predictions to make it sound right.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 06, 2018, 09:00:23 AM
Quote from: jeffandnicole on July 06, 2018, 08:44:17 AM
a home based computer would eventually be less useful than a 3"x5" handheld phone.

I don't think that's true, at least quite yet. Desktop computers have actual keyboards (making typing much faster) and can hold more data. Workplaces still have desktop computers, not smartphones. Try typing anything more than a few paragraphs on a smartphone. It takes too long, unless you use your voice. And if you do use your voice, it will make a few mistakes.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 06, 2018, 09:46:26 AM
Quote from: jakeroot on July 06, 2018, 01:56:59 AMI think it's fair to say that those with various phobias understand their fears more than those who have no fear. You know how sometimes, you just can't...look...away? If you understand tech, but refuse to adopt it for various reasons, by all accounts, you're still a technophobe. I don't know of any other words that fit the description.

There are plenty of alternatives:  refusenik is one.  Technophobe doesn't fit those who reject consumer-oriented platforms (or selectively use the features of such platforms that are less keyed toward promoting consumption) since in many cases they are extremely tech-literate and comfortable using technology--just not necessarily the kind that big players like Google, Amazon, Microsoft, or Facebook would like them to use.  If a person chooses to use LaTeX for major writing projects instead of Microsoft Word or Google Docs, it is not because he or she is irrationally afraid of technology.

Quote from: jakeroot on July 06, 2018, 01:56:59 AMIn my opinion, anyone who feels alienated by consumerism needs to take a step back and understand the world. Virtually all western-style countries are consumer-based societies. If consumers like applications that use their information to make their life easier, you're going to see more applications like that. Evidently, most people like that. Are there, and will there always be outliers who'd rather not be bombarded by suggestions for this or that? Sure, but they are quickly becoming the minority.

"Virtually all" western-style countries have more stringent advertising controls and better legal protections for privacy than we do.  And, more fundamentally, the feedback loop of building applications that harvest ever more of our personal data to push us to consume ever more is not intrinsic to capitalism but is one plausible way in which it can fail.  The folks who stand aloof and insist on protecting personal autonomy are not "failing to understand the world."  They are, arguably, showing more foresight than their peers who keep running inside the wire wheels while tech CEOs buy houses in New Zealand or condos inside former missile silos to hedge against the catastrophe they fear from economic underregulation.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on July 06, 2018, 11:18:29 AM
To get a bit back on topic, it would be nice if Google Maps just offered lighter versions on different websites, so it can run faster and consistent. Keep the 3D Google Earth stuff on a separate sub-domain. Making websites "lighter" and load quicker has been all lip service for the best part of a decade. More devices are competing for the same limited bandwidth.

Quote from: kkt on July 06, 2018, 04:46:36 AM
Didn't have a whole butload of dubious features that I never use.  The menus didn't constantly mutate.  Wasn't spyware.

To be fair, I don't think anyone can truly use every feature of most software. Usually the added benefits are of no/limited use, because there's added complexity in recalling how to use a rarely-needed feature, among numerous other reasons. I used Wordpad for a few years, jumped on the Office bandwagon with Word/Excel 97, and noticed unnecessary features creeping in with 2000 and 2003. I still have my copies of 97 and 2003, the later running nicely on modern machinery with minimal start-up lag. If it wasn't for the spell-checker and grammar features, I'd just use WordPad, and usually use it for the little bit of coding that I still do (or if I'm using a PC that doesn't have any sort of Office access).

Quote from: J N Winkler on July 06, 2018, 09:46:26 AMAnd, more fundamentally, the feedback loop of building applications that harvest ever more of our personal data to push us to consume ever more is not intrinsic to capitalism but is one plausible way in which it can fail.  The folks who stand aloof and insist on protecting personal autonomy are not "failing to understand the world."  They are, arguably, showing more foresight than their peers who keep running inside the wire wheels while tech CEOs buy houses in New Zealand or condos inside former missile silos to hedge against the catastrophe they fear from economic underregulation.

While I can't disagree with that, there's usually a time investment in bypassing the mainstream...some of us do not have as much of that to spare as before, and wander back to the familiar ways of doing things on our various computing platforms. I grate my teeth at the thought of using Windows 8/10 with its advertising tiles (on paid software, no less), bothering with a TV set that suggests what I watch, browsing the internet with a clumsy bunch of intelligence-insulting disruptions, misguided clickbait, imbalanced comments, and the appalling miasma of enternewsvertising currently on tap.

We're not all the vacuous mobile wallets purported by the other side of the fringe; some of us enjoy the mobilty, choose carefully in how we use it, spend our time/money wisely on it, resist the urges to keep up with most possible Tech Joneses, enjoy plenty of "unplugged" time, and understand there's a few risks. There's just that annoying cycle of Hardware - OS - Software - (Battery Life?) wheel that's always "improving" but always seems to go out of balance.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 06, 2018, 01:11:40 PM
Quote from: formulanone on July 06, 2018, 11:18:29 AMTo be fair, I don't think anyone can truly use every feature of most software. Usually the added benefits are of no/limited use, because there's added complexity in recalling how to use a rarely-needed feature, among numerous other reasons. I used Wordpad for a few years, jumped on the Office bandwagon with Word/Excel 97, and noticed unnecessary features creeping in with 2000 and 2003. I still have my copies of 97 and 2003, the later running nicely on modern machinery with minimal start-up lag. If it wasn't for the spell-checker and grammar features, I'd just use WordPad, and usually use it for the little bit of coding that I still do (or if I'm using a PC that doesn't have any sort of Office access).

I like the fact that the current formats for Word and Excel are XML-based and are accessible to older versions with a compatibility pack, although the natively generated XML is very dirty and comes packed into ZIP archives, both of which impair portability.  I have largely switched to LaTeX because the source files are easily human-readable (being plain text), are portable across different operating systems, and the output PDFs produced using pdflatex are very, very clean.  I do still use Word for things that have to be dashed off very quickly and for collaboration, e.g. library board meeting minutes which I receive via email in .docx format and send back with suggested revisions.

I have Office 2003 on my primary computer, as a second copy under a two-workstation license.  I would actually prefer Office 2000 Professional, which I also have and originally purchased for a Windows 98 machine, but I have not been able to get it to install on my Windows 7 machine even in compatibility mode.  I have Access databases I now cannot access directly on my current machine since the Office bundle it will install does not include Access.  This was one factor in my decision to move toward plain-text source files since at least those cannot be taken away.

Quote from: formulanone on July 06, 2018, 11:18:29 AMWhile I can't disagree with that, there's usually a time investment in bypassing the mainstream...some of us do not have as much of that to spare as before, and wander back to the familiar ways of doing things on our various computing platforms. I grate my teeth at the thought of using Windows 8/10 with its advertising tiles (on paid software, no less), bothering with a TV set that suggests what I watch, browsing the internet with a clumsy bunch of intelligence-insulting disruptions, misguided clickbait, imbalanced comments, and the appalling miasma of enternewsvertising currently on tap.

The tradeoffs involved encompass know-how as well as time.  I don't opt out completely--I have a Facebook account I actively use--but I stuck with Windows 7 because I knew how to prevent Windows 10 from auto-installing on my primary workstation, and my browsing is fairly silent in terms of advertising because I use an ad-blocking HOSTS file instead of relying on AdBlock Plus.  (Because ad-blocking HOSTS files represent a minority approach compared to AdBlock Plus, website developers spend less time trying to figure out how to block them, so I am less likely to encounter defeat mechanisms for my HOSTS file than I am for AdBlock.)

It is easy for me to steer clear of TV because I have never actually gotten the hang of how digital TV works.  I was living out of the country when it was introduced, so I still don't know how to access OTA digital programming for the network affiliates in my area.  With TV shows now available on DVD or through streaming, it is now more natural for me to think of TV programming I want to watch as a collection of video streams I can access through mechanisms other than walking up to a TV set and turning it on.

It is actually with mobile that I feel most keenly the limitations of my own know-how.  I only recently learned how to write shell scripts for Android, for example.  I still haven't figured out a free way to root my phone and keep it rooted through OS updates.  But Windows 10 is starting to catch up.  I suspect one of the unrefusable updates is responsible for a family member no longer being able to use a tablet to access files on his computer through a SMB network.  I suspect the computer is now set to reject all incoming connections that aren't SMB 2.0, but I barely know how to start fixing this.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 06, 2018, 01:16:31 PM
Quote from: jakeroot on July 06, 2018, 01:56:59 AM
I think you're painting the situation with far too big of a brush stroke. The core functions of our favorite apps, and most features of them, are still there and accessible. The accessing method might have become slightly more complex or less obvious, but most features are still there. Are these various applications geared more towards consumption? Of course, but that's always been their purpose. Youtube has always been about sharing videos, and they've since made it easier to find videos you might be interested in. Google Maps has always been about finding points of interest and navigating to them -- their recent redesigns have simply made it easier for the majority of users to do what they need to do. Back when these apps launched, I guarantee you they would have had many of the same features as their modern counterparts, had their designers had the technology to support the features. It's only recently that these technology has come around.
I'm not sure I'd say that they were the same.  My impression is that early YouTube was about end users freely sharing their own videos; there were no ads, no payments for number of views, and major companies hadn't yet started uploading videos.  Likewise, early Google Maps was a more advanced MapQuest (which at the time didn't allow one to use the mouse to drag the map; clicking buttons on the side to incrementally move the map in fixed-size steps was required); both back then were more oriented to providing directions to a predetermined address that one would print out than finding new places with search.  I do actually use Google Maps to find places (and to look at photos of places and read reviews), though when I do I'm usually either panning the map to see what I can find like I would with a hypothetical paper map that had that info or searching for a specific business (and I then get annoyed when Google tries to include results for everything it deems "relevant" regardless of relevancy; it once included Chinese places when searching for diners, for example, on one of my rare times doing a general search, so clearly it doesn't work well).

Quote from: formulanone on July 06, 2018, 11:18:29 AM
To get a bit back on topic, it would be nice if Google Maps just offered lighter versions on different websites, so it can run faster and consistent. Keep the 3D Google Earth stuff on a separate sub-domain. Making websites "lighter" and load quicker has been all lip service for the best part of a decade. More devices are competing for the same limited bandwidth.
I think at this point the developers are basically saying "we'll do what we want and eventually 5G will make it work".
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 07, 2018, 02:39:32 AM
Quote from: J N Winkler on July 06, 2018, 09:46:26 AM
Quote from: jakeroot on July 06, 2018, 01:56:59 AMI think it's fair to say that those with various phobias understand their fears more than those who have no fear. You know how sometimes, you just can't...look...away? If you understand tech, but refuse to adopt it for various reasons, by all accounts, you're still a technophobe. I don't know of any other words that fit the description.

There are plenty of alternatives:  refusenik is one.

Well, like many of the words in your posts, I am unfamiliar with that one. Point taken.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 07, 2018, 02:28:40 PM
Quote from: J N Winkler on July 06, 2018, 01:11:40 PM
I like the fact that the current formats for Word and Excel are XML-based and are accessible to older versions with a compatibility pack, although the natively generated XML is very dirty and comes packed into ZIP archives, both of which impair portability.  I have largely switched to LaTeX because the source files are easily human-readable (being plain text), are portable across different operating systems, and the output PDFs produced using pdflatex are very, very clean.  I do still use Word for things that have to be dashed off very quickly and for collaboration, e.g. library board meeting minutes which I receive via email in .docx format and send back with suggested revisions.

The Office Open XML formats are a badly-done attempt to copy the OpenDocument standard, with several decades of Microsoft compatibility cruft baked into the design. OpenDocument is comparatively cleaner, since it was designed to be an interchange format not tied to any specific office suite. It uses the same XML-in-a-ZIP structure, although there is a specification for a "flat" XML file, though that variant of the standard is less supported than the full ZIP format.

Office does support the OpenDocument standard, although it pops up a dire warning asking if you really want to do this if you try to save to it. I suspect that this is Microsoft's attempt to get users to use their own janky file format instead of the standard one.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 07, 2018, 07:10:16 PM
Quote from: Scott5114 on July 07, 2018, 02:28:40 PM
Office does support the OpenDocument standard, although it pops up a dire warning asking if you really want to do this if you try to save to it. I suspect that this is Microsoft's attempt to get users to use their own janky file format instead of the standard one.
As much as I am a supporter of free software (outside of work, I am practically a religious Linux user), I find it a bit odd when someone says "the standard" when it's not very commonly used.

Again, don't get me wrong, I very much agree that OpenDocument should be the standard, considering how many Word 2013 documents I email to myself from work look like alphabet soup when I open them on my home Linux machine, but at the same time I feel like the standard is (but shouldn't necessarily be) the widely used format.

As a counterexample, though, we could talk about Internet Explorer 6 and how much of a disaster that was, despite it being used by up to 90% of internet users at one point, when any technically knowledgeable person would know that Mozilla/Firefox conformed to the HTML standards better.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 08, 2018, 03:29:59 AM
OpenDocument is a standard because it was certified as such by both the industry consortium that created it and ISO, which blessed it with a standard number (ISO 26300). Lack of adoption by users that don't know any better doesn't make it any less the standard.

Hilariously, Office XML also much later got granted an ISO number, ISO 29500. Microsoft's implementation of the file format is not in compliance with ISO 29500, however, so anyone attempting to implement a program that reads Office XML files using only the standard as reference will probably not be able to open actual files emitted from Microsoft Office correctly.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 08, 2018, 09:13:09 AM
Quote from: Scott5114 on July 08, 2018, 03:29:59 AM
OpenDocument is a standard because it was certified as such by both the industry consortium that created it and ISO, which blessed it with a standard number (ISO 26300). Lack of adoption by users that don't know any better doesn't make it any less the standard.

Hilariously, Office XML also much later got granted an ISO number, ISO 29500. Microsoft's implementation of the file format is not in compliance with ISO 29500, however, so anyone attempting to implement a program that reads Office XML files using only the standard as reference will probably not be able to open actual files emitted from Microsoft Office correctly.
Ah...I forgot about ISO and their standards.  Thanks for reminding me.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on July 16, 2018, 07:59:18 AM
Quote from: vdeane on July 05, 2018, 01:06:28 PM
Quote from: jakeroot on July 04, 2018, 10:11:05 PM
I'm not getting into this again. Google's job is not to build their products around tin hat folks and those who need to keep their history clear. They're a company with with their hands in just about every industry, and the products really only work well when it collects your information. If you don't like that, Google isn't your friend.
It's "tin hat" to prioritize accurate results over Google trying to guess what you want?  When people/computers try to guess what I want, they usually guess wrong!  Unfortunately, it seems that the quality of Google's search results have been going down regardless, but no need to make it even worse.  I'm not typical in more ways than how I use Google Maps - I'd go so far as to say that smartphones were the worse thing to happen to the entire internet, since they brought the masses and a lot of dumbing down of all things computers with them.

Unfortunately, even though Google's paradigm is opposed to mine, they're still the best at everything they do by several orders of magnitude (only Apple and Amazon come close, at least in their spheres of influence, and I have issues with both of them too).

If I had the power to, I'd change things in the following ways:
-Keep roadgeek sites as they are
-Keep Linux as it is
-Keep the switch from Flash to HTML5
-Keep Chrome/Firefox/etc. as they are
-Roll back Google Maps to 2015 (not including data/street view)
-Roll back Gmail to 2012
-Roll back cell phones to 2005
-Roll back Google search to 2002
-Roll back everything else (Google's other products, Windows, etc.) to 2010
Old post, but let me also state for the record that I agree 100%.  :clap:

I'd even suggest rolling back Google Maps to 2012, when you could go up to a point "N" (14 destinations) IIRC as opposed to just ten the last time I tried to do a really silly long trip in there with a whole bunch of destinations.

For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on July 16, 2018, 04:19:10 PM
Quote from: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.
That would mean having used this perfectly good computer for only three years before getting rid of it  :rolleyes:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 16, 2018, 04:37:20 PM
Quote from: 20160805 on July 16, 2018, 04:19:10 PM
Quote from: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.

That would mean having used this perfectly good computer for only three years before getting rid of it  :rolleyes:

It's perfectly good, until it's not.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on July 16, 2018, 04:58:28 PM
Quote from: jakeroot on July 16, 2018, 04:37:20 PM
Quote from: 20160805 on July 16, 2018, 04:19:10 PM
Quote from: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.

That would mean having used this perfectly good computer for only three years before getting rid of it  :rolleyes:

It's perfectly good, until it's not.
Also consider that some people may not be able to afford getting a brand new computer with a brand new operating system every year or two when the new one comes out.  :rolleyes:

By the way, and I realise we're drifting from the topic at hand, is there ever going to be a "Windows 11"?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 16, 2018, 05:06:41 PM
Quote from: 20160805 on July 16, 2018, 04:58:28 PM
Quote from: jakeroot on July 16, 2018, 04:37:20 PM
Quote from: 20160805 on July 16, 2018, 04:19:10 PM
Quote from: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.

That would mean having used this perfectly good computer for only three years before getting rid of it  :rolleyes:

It's perfectly good, until it's not.
Also consider that some people may not be able to afford getting a brand new computer with a brand new operating system every year or two when the new one comes out.  :rolleyes:

By the way, and I realise we're drifting from the topic at hand, is there ever going to be a "Windows 11"?

Probably. Mac OS X will never change, though; they'll just keep incrementing the first number after the decimal point (currently at 10.13.6, which I just updated to less than an hour ago).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 16, 2018, 05:12:58 PM
Quote from: 20160805 on July 16, 2018, 04:58:28 PM
Quote from: jakeroot on July 16, 2018, 04:37:20 PM
Quote from: 20160805 on July 16, 2018, 04:19:10 PM
Quote from: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.

That would mean having used this perfectly good computer for only three years before getting rid of it  :rolleyes:

It's perfectly good, until it's not.
Also consider that some people may not be able to afford getting a brand new computer with a brand new operating system every year or two when the new one comes out.  :rolleyes:

All Windows 7, 8, and 8.1 licence keys work for Windows 10, making it essentially a free upgrade. The last person I know to pay for a new OS was my mother, who purchased Windows 7 to install over Vista back in 2009.

Quote from: 20160805 on July 16, 2018, 04:58:28 PM
By the way, and I realise we're drifting from the topic at hand, is there ever going to be a "Windows 11"?

Windows 10 was the last major "new" OS (https://goo.gl/wPrTtg). There will not be a Windows 11. Windows is now a service. Microsoft intends to do major updates to their OS twice a year, instead of huge leaps every three years. The most recent update was Redstone 4, released in April.

Quote from: 1 on July 16, 2018, 05:06:41 PM
Probably. Mac OS X will never change, though; they'll just keep incrementing the first number after the decimal point (currently at 10.13.6, which I just updated to less than an hour ago).

Microsoft will be doing it Apple style from now on.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 16, 2018, 07:58:30 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
Old post, but let me also state for the record that I agree 100%.  :clap:

I'd even suggest rolling back Google Maps to 2012, when you could go up to a point "N" (14 destinations) IIRC as opposed to just ten the last time I tried to do a really silly long trip in there with a whole bunch of destinations.

For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.
I'm pretty sure the new Google Maps didn't become mandatory until 2016 or so, since my meet directions for the Utica/Rome meet (May 2015) were done in the old version.

Quote from: jakeroot on July 16, 2018, 05:12:58 PM
Quote from: 20160805 on July 16, 2018, 04:58:28 PM
Quote from: jakeroot on July 16, 2018, 04:37:20 PM
Quote from: 20160805 on July 16, 2018, 04:19:10 PM
Quote from: jakeroot on July 16, 2018, 01:57:11 PM
Quote from: 20160805 on July 16, 2018, 07:59:18 AM
For the record, the computer from which I'm typing this runs Windows 7 and Office 2007; I recently upgraded to 7 from XP in January 2017, and I really like both operating systems.  I've been using Office 2007 since 2014, and I really like both 03 and 07; I have no reason or desire to upgrade from this configuration anytime soon.  If it ain't broke, don't fix it.

Consider upgrading to Windows 10 before Janauary 2020. Support for Windows 7 ends then, and you're creating a liability for yourself, and anyone else who might use your computer, by using an OS that isn't supported by security patches.

IMO, any OS that isn't supported by its creators should be considered "broke" for primary usage. Usage for historical purposes is different.

That would mean having used this perfectly good computer for only three years before getting rid of it  :rolleyes:

It's perfectly good, until it's not.
Also consider that some people may not be able to afford getting a brand new computer with a brand new operating system every year or two when the new one comes out.  :rolleyes:

All Windows 7, 8, and 8.1 licence keys work for Windows 10, making it essentially a free upgrade. The last person I know to pay for a new OS was my mother, who purchased Windows 7 to install over Vista back in 2009.

Quote from: 20160805 on July 16, 2018, 04:58:28 PM
By the way, and I realise we're drifting from the topic at hand, is there ever going to be a "Windows 11"?

Windows 10 was the last major "new" OS (https://goo.gl/wPrTtg). There will not be a Windows 11. Windows is now a service. Microsoft intends to do major updates to their OS twice a year, instead of huge leaps every three years. The most recent update was Redstone 4, released in April.

Quote from: 1 on July 16, 2018, 05:06:41 PM
Probably. Mac OS X will never change, though; they'll just keep incrementing the first number after the decimal point (currently at 10.13.6, which I just updated to less than an hour ago).

Microsoft will be doing it Apple style from now on.
I'm pretty sure the "upgrade" was only free for a year.  Not that I'd really consider something that spies on you, doesn't let you chose when to update (I'll never even consider it for a travel laptop for that reason, as such a laptop, by definition, wouldn't even be turned on most days, and doing them on my own schedule before/during the trip wouldn't be possible), removed the sexy Aero Glass, and replaced Windows 7's wonderful start menu with one that is optimized to include a bunch of phone/tablet apps an "upgrade".

Quite frankly, Microsoft and Apple's way of never increment version numbers is just as stupid as Google and Mozilla's way of constantly incrementing them for the littlest things.  I remember a day when version numbers MEANT something.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 17, 2018, 12:43:04 AM
Quote from: vdeane on July 16, 2018, 07:58:30 PM
I'm pretty sure the "upgrade" was only free for a year.  Not that I'd really consider something that spies on you, doesn't let you chose when to update (I'll never even consider it for a travel laptop for that reason, as such a laptop, by definition, wouldn't even be turned on most days, and doing them on my own schedule before/during the trip wouldn't be possible), removed the sexy Aero Glass, and replaced Windows 7's wonderful start menu with one that is optimized to include a bunch of phone/tablet apps an "upgrade".

Quite frankly, Microsoft and Apple's way of never increment version numbers is just as stupid as Google and Mozilla's way of constantly incrementing them for the littlest things.  I remember a day when version numbers MEANT something.

It's still free: https://www.howtogeek.com/266072/you-can-still-get-windows-10-for-free-with-a-windows-7-8-or-8.1-key/ (you just need a licence key from a previous version of Windows). Once you get the update, apparently, you're set for life, since Microsoft apparently never again intends to make users pay for a new edition.

- You can disable automatic updates. Talk to people over at Notebook Forums. I don't know how to do it exactly.
- Aero Glass was a waste of vRAM; that said, Windows 10 has the blurry background/glass effect if you want it (my start menu is transparent). You just have to enable it.
- You can re-implement the Windows 7 start menu, but honestly, it's not that different from Windows 10. You can pin just about anything to the start menu, if you want it to act more like 7. Besides, real power users use their fingers for everything. You want to open control panel? Win+S, "co", "enter". Windows 10 search seems to be better than Windows 7.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 17, 2018, 12:25:12 PM
Now you're making me wonder whether to keep my Windows 7 laptop beyond 2020.  I'm mainly keeping it around in case I ever need Windows for anything.  Hardware still works (though it has a tendency to run hot when doing updates), even though it will be a decade old next year.  I guess I'll have to decide how much I care to deal with Windows 10 and maintaining a computer I don't really use.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 17, 2018, 04:49:48 PM
Quote from: jakeroot on July 17, 2018, 12:43:04 AM- You can disable automatic updates. Talk to people over at Notebook Forums. I don't know how to do it exactly.

There are multiple options; the trick is finding one that doesn't roll itself back without telling you through some kind of "self-healing" mechanism that loads automatically through Task Scheduler.

Quote from: jakeroot on July 17, 2018, 12:43:04 AM- You can re-implement the Windows 7 start menu, but honestly, it's not that different from Windows 10. You can pin just about anything to the start menu, if you want it to act more like 7. Besides, real power users use their fingers for everything. You want to open control panel? Win+S, "co", "enter". Windows 10 search seems to be better than Windows 7.

The start menu is editable in the Windows Explorer file chooser, at least in Windows 7 through 8.1, though the process is much more cumbersome for 8+ because the icons are stored in multiple silos.  I assume the same is true for 10.

One of my biggest annoyances with Windows versions later than 7 is the additional hoops that have to be jumped through to open a command prompt with administrator privileges.  This issue comes up when attempting to diagnose something that has been broken by a Windows update.  For the two computers we have that are in daily use, this happens far more often (by a factor of at least 20) for the one that has 10 than it does for the one running 7.

To summarize the last two support problems for the 10 machine:

*  A Windows update somehow broke PaperPort 14, which is absolutely key for day-to-day use of that machine.  Uninstalling and then reinstalling PaperPort failed.  Rolling back to the restore point set before the update also failed.  Upgrading PaperPort failed.  The solution that worked was buying a new scanning and document management solution, at a cost of $250.

*  The user of the 10 machine hosts files on it that he reads over the house LAN on a tablet.  After a Windows update, the tablet lost its ability to connect to the 10 machine via SMB.  We determined the update had turned off SMB 1 support.  The tablet did not have robust SMB 2 support.  It took much Googling to figure out how to re-enable SMB 1.  (Microsoft has deprecated SMB 1 since 2014, and it seems the update that borked the connection was oriented at weaning the user population off it.  Microsoft evidently had to backtrack owing to the lack of robust SMB 2 support on other network devices.  The webpage we ultimately found most helpful had lots of strikethrough text indicating where Microsoft gave up on automatically uninstalling SMB 1 support.)

Quote from: vdeane on July 17, 2018, 12:25:12 PMNow you're making me wonder whether to keep my Windows 7 laptop beyond 2020.  I'm mainly keeping it around in case I ever need Windows for anything.  Hardware still works (though it has a tendency to run hot when doing updates), even though it will be a decade old next year.  I guess I'll have to decide how much I care to deal with Windows 10 and maintaining a computer I don't really use.

I wouldn't think twice about keeping it running on 7 well beyond end of support.  I am still running XP on a twelve-year-old laptop that not only is more than four years beyond the end of support, but also has seriously out-of-date antivirus software.  I use it primarily to run an old Brother multifunction printer as a document scanner, but haven't had trouble using it for light Internet surfing on trips.  The risk of virus infestation goes way down with an ad-blocking HOSTS file and an email client set to display emails as plain text by default.

My current computer has 7, dates from 2011, and still runs well.  Given all the problems people have been having with Windows 10, I may very well keep it going as my primary computer beyond the end of support for 7.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 18, 2018, 02:43:58 AM
Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
Quote from: jakeroot on July 17, 2018, 12:43:04 AM- You can disable automatic updates. Talk to people over at Notebook Forums. I don't know how to do it exactly.

There are multiple options; the trick is finding one that doesn't roll itself back without telling you through some kind of "self-healing" mechanism that loads automatically through Task Scheduler.

An issue that I've had myself. I've been told there's a proper way to do it (I did it by keeping my OS drive just full enough not to allow downloading, but eventually by telling Windows that all my WiFi connections were metered). Somehow it outsmarted me, and now I'm completely up to date. No issues though! Except one of my games would crash after the update, but I fixed that by re-downloading the mods I had.

Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
The start menu is editable in the Windows Explorer file chooser, at least in Windows 7 through 8.1, though the process is much more cumbersome for 8+ because the icons are stored in multiple silos.  I assume the same is true for 10.

I only had Windows 8 for a short amount of time, but Windows 10's start menu is vastly improved. You can pretty much right-click on any program, folder, or file anywhere in Windows, and click "Pin to Start". It will appear as a clickable icon on the right side of the Start Menu (to the right of all your programs). You can drag it around however you want. You can create as many columns and rows as you'd like.

Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
One of my biggest annoyances with Windows versions later than 7 is the additional hoops that have to be jumped through to open a command prompt with administrator privileges.  This issue comes up when attempting to diagnose something that has been broken by a Windows update.  For the two computers we have that are in daily use, this happens far more often (by a factor of at least 20) for the one that has 10 than it does for the one running 7.

In Windows 10, this is best done by hitting Win+S, typing in at least "com", right-clicking on the program when it pops up, and hitting "Run as Administrator".

The Fall Creator's update to 10 switched the default automation tool from Command Promp to PowerShell. This can be launched by hitting Win+X, and then on the menu that pops up, hitting "Windows PowerShell (Admin). You can change the menu to offer Command Prompt instead, if you'd prefer. But PowerShell offers basically everything that Command Prompt does, plus quite a bit else. I'm not a Command Prompt geek like some, but I've heard it's rather impressive.




You seem to be experiencing more issues with 10 than I have, and more than I've heard of others having. Honestly, growing up, the running joke was always how unreliable Windows was, in any iteration, compared to Mac OS or Linux. Nowadays, you don't really hear those same jokes like before. My thought was that Windows was finally a solid OS, with an occasional weak spot, but it wouldn't leave you stranded like some past iterations might have. Back in 2006, my father got so fed up with his Windows XP machine that he went out and bought an iMac. He never looked back!

FWIW, I don't think there's any problem with using an unsupported OS on a computer that barely connects to the internet. But for an everyday device that connects to the internet 24/7, it doesn't seem smart. Seems to me that it puts you in a position where only you can help yourself. Just make sure to keep a backup image handy.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 18, 2018, 07:47:35 AM
I work at Stop & Shop. A few of their computers (I believe for inventory management) are text-only with no cursor or graphics, and just a single color. They estimate that those computers are from 1985, but they aren't sure of the exact year.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 18, 2018, 07:53:23 AM
I find Windows 10 to be incredibly unreliable. I have a dual-boot laptop, and I only use two applications on Windows: GRLevelX for tracking severe weather (because Oklahoma), and a driver program for my vinyl cutter. Windows is remarkably consistent at deciding the proper time to install updates is right when a tornado is bearing down on Cleveland County, leaving me without one of my tools to keep myself safe. The last severe weather event I even left the laptop powered on and booted into Windows for several hours when severe weather was predicted and it didn't go into update until the severe weather began.

How reliable is an OS if it stays running but doesn't allow you to use it for anything? How reliable is it if its update cycle directly threatens your life?

Quote from: 1 on July 18, 2018, 07:47:35 AM
I work at Stop & Shop. A few of their computers (I believe for inventory management) are text-only with no cursor or graphics, and just a single color. They estimate that those computers are from 1985, but they aren't sure of the exact year

At the casino I work at, our most critical software functions (jackpot processing, accounting, ticket redemption) are done through a program fairly similar to what you describe. It is an application running on Windows 7, however.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 18, 2018, 11:21:31 AM
Quote from: jakeroot on July 18, 2018, 02:43:58 AM
Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
One of my biggest annoyances with Windows versions later than 7 is the additional hoops that have to be jumped through to open a command prompt with administrator privileges.  This issue comes up when attempting to diagnose something that has been broken by a Windows update.  For the two computers we have that are in daily use, this happens far more often (by a factor of at least 20) for the one that has 10 than it does for the one running 7.

In Windows 10, this is best done by hitting Win+S, typing in at least "com", right-clicking on the program when it pops up, and hitting "Run as Administrator".

Yes, I have used that technique.  It is a hell of a lot less handy than Win+R and "cmd," or just Shift+right-click on a folder in the Explorer file chooser and then "Open command window here."

Quote from: jakeroot on July 18, 2018, 02:43:58 AMThe Fall Creator's update to 10 switched the default automation tool from Command Prompt to PowerShell. This can be launched by hitting Win+X, and then on the menu that pops up, hitting "Windows PowerShell (Admin). You can change the menu to offer Command Prompt instead, if you'd prefer. But PowerShell offers basically everything that Command Prompt does, plus quite a bit else. I'm not a Command Prompt geek like some, but I've heard it's rather impressive.

I have heard that it was Microsoft's intention to deprecate the NT command prompt in favor of PowerShell in this way, but the former (thankfully) seems still to be the default console application on the 10 computer here.  I do have NT batch scripts that call on PowerShell functions such as the GUID generator, but I have never written anything natively in PowerShell because I find the syntax very unhandy.

My heaviest use of NT batch is for automatically downloading highway construction documents from websites.  I have probably at least three or four dozen scripts that are reducible to the following pseudocode:

Login to server

Obtain a listing of "rooms" where project documentation is held (each project having its own "room")

Block out rooms that, owing to the operation of logic rules specific to a given agency, are not expected to have had new content uploaded since a prior visit (e.g., in the case of NYSDOT, on the first visit after the letting date, the room is marked on a blockout list:  on the next few subsequent visits, the room is not visited when it is found on the blockout list; and once the letting date is one month in the past, the room is eliminated outright and neither visited nor checked against the blockout list)

Visit each room and list the available content

Block out all previously downloaded content in each room

Update log files with rooms and new content to block out from download in the future

Download all new content

This is very easy to code in NT batch because the rooms and the downloadable data in each room can be written to text files, one room per line in a room listing file and one document per line in a file listing (either one file per session or one file per room), and each listing file can be used as the basis for a FOR /F loop that goes through one iteration per line.  Command output can be sent to FOR /F as if it were a file, which allows it to be used for conditional flow control since FOR /F will not execute at all if the command has null output while it will execute at least once if the command has non-null output.  FOR /F (for most program flow control) and findstr (for checking that text strings do, or do not exist, in text files) are my killer apps.

It is easy enough to see how these flow control strategies can be implemented in the various flavors of Unix shell, but in PowerShell I struggle even to get started.  The pseudocode outlined above essentially fits into the structured programming paradigm while PowerShell is object-oriented.

Quote from: jakeroot on July 18, 2018, 02:43:58 AMYou seem to be experiencing more issues with 10 than I have, and more than I've heard of others having. Honestly, growing up, the running joke was always how unreliable Windows was, in any iteration, compared to Mac OS or Linux. Nowadays, you don't really hear those same jokes like before. My thought was that Windows was finally a solid OS, with an occasional weak spot, but it wouldn't leave you stranded like some past iterations might have. Back in 2006, my father got so fed up with his Windows XP machine that he went out and bought an iMac. He never looked back!

The primary user of the 10 machine is not a digital native and I suspect he has more trouble with it than I would, simply because it is not second nature to him to steer clear of trouble by sticking close to low-footprint usage.  But he is far from unique in having problems with 10.  When it first came out, my Facebook feed filled with reports from people having various issues with 10, mostly due to half-baked updates, and most of the reports originated from highly computer-literate people, including one who makes a living programming in assembler and another who regularly uses CAD applications to produce engineering plans.

As for my experience with Windows, my biggest problems have been disk data losses due to memory errors.  In the early noughties I had a major loss on a Windows 98 machine due to an ill-thought-out memory upgrade.  About a decade later on a Windows XP machine, I had another major loss on an external HD (fortunately not my main HD) due to corruption of the master file table.  I have since not been inconvenienced by data loss episodes, although there was one incident when my backup external HD became unreadable; I determined this was a hardware problem, not the fault of Windows 7 on the primary computer, and replaced the disk.  I have never had a problem due to a bad Windows update on any of my computers, and I think probably the biggest reason for this is that I postpone updates until they can be installed during scheduled downtime.

Quote from: jakeroot on July 18, 2018, 02:43:58 AMFWIW, I don't think there's any problem with using an unsupported OS on a computer that barely connects to the internet. But for an everyday device that connects to the internet 24/7, it doesn't seem smart. Seems to me that it puts you in a position where only you can help yourself. Just make sure to keep a backup image handy.

Self-help is the only practical option even with versions of Windows that are still supported.

Quote from: Scott5114 on July 18, 2018, 07:53:23 AMI find Windows 10 to be incredibly unreliable. I have a dual-boot laptop, and I only use two applications on Windows: GRLevelX for tracking severe weather (because Oklahoma), and a driver program for my vinyl cutter. Windows is remarkably consistent at deciding the proper time to install updates is right when a tornado is bearing down on Cleveland County, leaving me without one of my tools to keep myself safe. The last severe weather event I even left the laptop powered on and booted into Windows for several hours when severe weather was predicted and it didn't go into update until the severe weather began.

Have you tried booting to Windows in good weather and running Windows Update with the force-update option, and then applying one of the registry hacks to prevent unwanted updates when you next boot it during a storm?  It is easy enough to apply and unapply registry hacks using batch files.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 18, 2018, 02:03:29 PM
Quote from: J N Winkler on July 18, 2018, 11:21:31 AM
Quote from: jakeroot on July 18, 2018, 02:43:58 AM
Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
One of my biggest annoyances with Windows versions later than 7 is the additional hoops that have to be jumped through to open a command prompt with administrator privileges.  This issue comes up when attempting to diagnose something that has been broken by a Windows update.  For the two computers we have that are in daily use, this happens far more often (by a factor of at least 20) for the one that has 10 than it does for the one running 7.

In Windows 10, this is best done by hitting Win+S, typing in at least "com", right-clicking on the program when it pops up, and hitting "Run as Administrator".

Yes, I have used that technique.  It is a hell of a lot less handy than Win+R and "cmd," or just Shift+right-click on a folder in the Explorer file chooser and then "Open command window here."

I was not aware that either of those techniques automatically ran an elevated command prompt. Guess you got me here.

I will say, though, that the new method of Win+X, clicking arrow up eight times, and hitting enter isn't exactly a slow process. At least it's all keyboard.

Quote from: J N Winkler on July 18, 2018, 11:21:31 AM
I have heard that it was Microsoft's intention to deprecate the NT command prompt in favor of PowerShell in this way, but the former (thankfully) seems still to be the default console application on the 10 computer here.  I do have NT batch scripts that call on PowerShell functions such as the GUID generator, but I have never written anything natively in PowerShell because I find the syntax very unhandy.
[clipped]

Wow, clipped for brevity. While I may not see eye to eye with you on this topic, I highly admire your ability to exploit Command Prompt. I am truly lost using that program, except for basic tasks. Guess that's the result of growing up in the "point and click" era.

Quote from: J N Winkler on July 18, 2018, 11:21:31 AM
Self-help is the only practical option even with versions of Windows that are still supported.

True. Microsoft support is garbage.

That said, as time goes on, even total geeks will move on to Windows 10 and beyond, making it harder to troubleshoot an issue. I prefer to keep up with the Joneses for this reason. In the event that a problem does pop up, I can usually solve it quickly by consulting other users. Using an old version of Windows, while I would have to go to the "forums" for help just the same, the chance of me finding someone who might know how to help dwindles by the day. IME, it's difficult to help someone troubleshoot an issue without being able to use the OS in question.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 18, 2018, 02:41:05 PM
The changes to Google Maps for developers have started manifesting themselves in certain end products, and I have to admit I'm feeling a loss.

First, the route tracings on Wikipedia no longer work. I used them surprisingly often for various roadgeeking purposes, and now they're gone. (I mean, I could load the KML files into Earth, but that's an extra step, and I like toggling between aerial views and the map, and you can't do that in Earth.)

Second, the website I used to plot multiple points on Google Maps now uses the Open Street Map, and there too, you can't toggle between aerial views and the maps.

The Route 66 map I use from time to time still works, though, so there's that.

On the whole, it's been something of a frustrating change for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on July 18, 2018, 07:15:30 PM
Quote from: CtrlAltDel on July 18, 2018, 02:41:05 PM
The changes to Google Maps for developers have started manifesting themselves in certain end products, and I have to admit I'm feeling a loss.

Looks like it manifested on ACME Mapper with a message saying:"This page can't load Google Maps correctly" while MyTopo still works for now but for how long?
Title: Re: Google Maps just fucking SUCKS now
Post by: bzakharin on July 18, 2018, 08:02:32 PM
Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
Quote from: jakeroot on July 17, 2018, 12:43:04 AM- You can disable automatic updates. Talk to people over at Notebook Forums. I don't know how to do it exactly.

There are multiple options; the trick is finding one that doesn't roll itself back without telling you through some kind of "self-healing" mechanism that loads automatically through Task Scheduler.
If you set your Wi-Fi or ethernet network as a "metered connection" you will not get any Windows Updates automatically. And it won't be rolled back as long as you keep using the same connection.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 18, 2018, 11:26:15 PM
Quote from: bzakharin on July 18, 2018, 08:02:32 PM
Quote from: J N Winkler on July 17, 2018, 04:49:48 PM
Quote from: jakeroot on July 17, 2018, 12:43:04 AM- You can disable automatic updates. Talk to people over at Notebook Forums. I don't know how to do it exactly.

There are multiple options; the trick is finding one that doesn't roll itself back without telling you through some kind of "self-healing" mechanism that loads automatically through Task Scheduler.

If you set your Wi-Fi or ethernet network as a "metered connection" you will not get any Windows Updates automatically. And it won't be rolled back as long as you keep using the same connection.

That's what I used to do, but it eventually downloaded anyway. Not sure if it was in smaller pieces to keep me from noticing, but it outsmarted me nonetheless. I also have a tower, so it's not like I was changing WiFi networks too often.

Worst case option: partition your OS drive so that there's not enough room for it to download. Of course, at that point, it's probably easier to just download the update and deal with any issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 19, 2018, 11:35:44 AM
Quote from: jakeroot on July 18, 2018, 02:03:29 PMI was not aware that either of those techniques automatically ran an elevated command prompt. Guess you got me here.

In Windows 7 they do if the current account is designated the Administrator account.  Requiring additional steps to evoke a command prompt with administrator privileges in Windows 8+ is part of Microsoft's strategy to encourage users to do nearly all of their computing on low-privilege accounts that are harder to hack.  This is fine, so far as it goes, but as with the dozens of other instances in which Microsoft tries to force change, it leaves the end user caught between Microsoft and the rest of the IT industry.  It has been over two years since we were told to turn browser Java support off, full stop, and there are still applications out there (e.g. the "classic" version of MnDOT's Hummingbird DMS) that require a Java applet.  The industry has been moving away from Flash and toward HTML5 for several years now (from my perspective, this is a good move, because AMF is nothing but trouble when trying to code text-based Web scrapers), and it is only now that I am starting to notice a tailing-off in websites whose code elicits the "Your version of Flash is outdated and vulnerable" bar in Firefox.

Quote from: jakeroot on July 18, 2018, 02:03:29 PMWow, clipped for brevity. While I may not see eye to eye with you on this topic, I highly admire your ability to exploit Command Prompt. I am truly lost using that program, except for basic tasks. Guess that's the result of growing up in the "point and click" era.

Your words are kind, but I suspect I find NT batch intuitive largely because my (limited) training in computer science consisted of functional programming in Pascal.  I think you are young enough that object-oriented programming would have been the dominant idiom in whatever programming classes you took.  NT batch was also the path of least resistance for me when I first started trying to automate routine tasks, because it would run at the command prompt without the need to download and install a compiler or interpreter, and did not need to be specially evoked at the command line (which is still the case with PowerShell in Windows 7).  I do have Python installed for certain special purposes, such as using the haversine formula to calculate the length of GPS tracks, and I now have NT batch scripts that depend very heavily on GnuWin ports of standard Unix tools like sed.

Notwithstanding the multiple flavors of Unix shell, I think shell scripts are probably more portable than NT batch simply because the Unix substrate is more widely supported across multiple hardware and software platforms.  Microsoft's foray into Windows as mobile OS is increasingly deemed a failure, while Android, iOS, and MacOS are basically all Unix underneath the skin.

I found Rob van der Woude's scripting site (http://www.robvanderwoude.com/batchstart.php) helpful when I was getting started writing NT batch scripts.  I notice it has a section on PowerShell as well--perhaps a new learning opportunity for me . . .

Quote from: jakeroot on July 18, 2018, 02:03:29 PMThat said, as time goes on, even total geeks will move on to Windows 10 and beyond, making it harder to troubleshoot an issue. I prefer to keep up with the Joneses for this reason. In the event that a problem does pop up, I can usually solve it quickly by consulting other users. Using an old version of Windows, while I would have to go to the "forums" for help just the same, the chance of me finding someone who might know how to help dwindles by the day. IME, it's difficult to help someone troubleshoot an issue without being able to use the OS in question.

I think communications styles and the business model driving an OS both make a difference.  I almost never seek help interactively and Windows 7 is essentially still a static OS.  Therefore, I tend to take the view that once a fix has been posted on one of the Web forums dedicated to helping Windows users, a very long time will pass before it decays off the live Web, and the fix will still be relevant to my copy of Windows 7.  Meanwhile, with Microsoft's new OS-as-service model, the look and feel of Windows 10 changes often enough that a person trying to fix a particular problem has to look at the date attached to the advice to evaluate whether it is relevant.  (BTW, many of the changes are deliberate efforts to overcome user attempts to prevent Windows 10 from updating.)

Windows is a complex enough OS that it often makes more sense to work around problems than to try to tackle them directly.  For example, earlier this year I was plagued with tons of unscheduled shutdowns due to something forcing a BugCheckCode of 9F in iastor.sys.  Attempts to troubleshoot the problem using Windows debugging tools failed.  Later, in an unrelated initiative, I decided to free up disk space by archiving old log files.  I ended up packing away 1-2 million, about 20 GB worth, cutting total file count on my data partition to under 500,000.  Mysteriously, system performance has greatly improved--the last BugCheckCode was months and months ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: jon daly on July 19, 2018, 12:17:40 PM
This isn't a major problem, but recently I was getting directions for someplace and GMaps told me to take S Road. The road was actually South Road.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 19, 2018, 12:49:43 PM
Quote from: J N Winkler on July 19, 2018, 11:35:44 AM
(BTW, many of the changes are deliberate efforts to overcome user attempts to prevent Windows 10 from updating.)
Maybe if they would make an update process that didn't brick the system for long periods of time, they wouldn't have that problem.  On Linux, updates are easy; they do not require that other work be suspended, nor do they force a reboot afterwards (although it's a good idea to log off/back in at some point and to reboot for kernel updates, since the pre-updated code will still be running until a given process is restarted).  A normal batch of updates doesn't take very long, either; rarely more than 30 seconds to a minute (of course, Microsoft's "Patch Tuesday" model is responsible for some of this, but not all; even the first batch upon setting up my desktop, it only took a couple minutes, whereas Windows will take over an hour on first setup - and if you need to check/download/install, even a Patch Tuesday batch can take that long!).
Title: Re: Google Maps just fucking SUCKS now
Post by: bzakharin on July 19, 2018, 12:59:24 PM
Quote from: vdeane on July 19, 2018, 12:49:43 PM
Quote from: J N Winkler on July 19, 2018, 11:35:44 AM
(BTW, many of the changes are deliberate efforts to overcome user attempts to prevent Windows 10 from updating.)
Maybe if they would make an update process that didn't brick the system for long periods of time, they wouldn't have that problem.  On Linux, updates are easy; they do not require that other work be suspended, nor do they force a reboot afterwards (although it's a good idea to log off/back in at some point and to reboot for kernel updates, since the pre-updated code will still be running until a given process is restarted).  A normal batch of updates doesn't take very long, either; rarely more than 30 seconds to a minute (of course, Microsoft's "Patch Tuesday" model is responsible for some of this, but not all; even the first batch upon setting up my desktop, it only took a couple minutes, whereas Windows will take over an hour on first setup - and if you need to check/download/install, even a Patch Tuesday batch can take that long!).
This is not entirely true. If you're updating the Linux kernel (which would certainly be the case for something equivalent to a Redstone 4) you absolutely do have to reboot. As for everything else, well, you can't really expect Windows to change how it loads executing files into memory. That would completely upend the entire architecture of the OS.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 19, 2018, 01:20:07 PM
Quote from: bzakharin on July 19, 2018, 12:59:24 PM
Quote from: vdeane on July 19, 2018, 12:49:43 PM
Quote from: J N Winkler on July 19, 2018, 11:35:44 AM
(BTW, many of the changes are deliberate efforts to overcome user attempts to prevent Windows 10 from updating.)
Maybe if they would make an update process that didn't brick the system for long periods of time, they wouldn't have that problem.  On Linux, updates are easy; they do not require that other work be suspended, nor do they force a reboot afterwards (although it's a good idea to log off/back in at some point and to reboot for kernel updates, since the pre-updated code will still be running until a given process is restarted).  A normal batch of updates doesn't take very long, either; rarely more than 30 seconds to a minute (of course, Microsoft's "Patch Tuesday" model is responsible for some of this, but not all; even the first batch upon setting up my desktop, it only took a couple minutes, whereas Windows will take over an hour on first setup - and if you need to check/download/install, even a Patch Tuesday batch can take that long!).
This is not entirely true. If you're updating the Linux kernel (which would certainly be the case for something equivalent to a Redstone 4) you absolutely do have to reboot. As for everything else, well, you can't really expect Windows to change how it loads executing files into memory. That would completely upend the entire architecture of the OS.
Regardless, the fact that Linux can apply updates much more quickly (and in a more centralized manner, thanks to proper package managers) than Windows was one of my main reasons for switching on my own personal computers.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 19, 2018, 02:05:16 PM
Quote from: bzakharin on July 19, 2018, 12:59:24 PM
This is not entirely true. If you're updating the Linux kernel (which would certainly be the case for something equivalent to a Redstone 4) you absolutely do have to reboot. As for everything else, well, you can't really expect Windows to change how it loads executing files into memory. That would completely upend the entire architecture of the OS.
You have to reboot for it to take effect.  You do NOT have to reboot for it to simply finish installing, as with Windows.  Linux does not have the "Preparing to configure updates", "Installing update 1 of X", "please do not turn off your computer" issue that Windows has, not does it nag you to reboot, or prevent installation of other updates (it's rare that I have to install updates in separate batches, but guaranteed in Windows if you're setting up for the first time or it's been a while, and each batch requires a reboot in between for Windows but can go one after the other in Linux).
Title: Re: Google Maps just fucking SUCKS now
Post by: bzakharin on July 19, 2018, 02:18:03 PM
Quote from: vdeane on July 19, 2018, 02:05:16 PM
Quote from: bzakharin on July 19, 2018, 12:59:24 PM
This is not entirely true. If you're updating the Linux kernel (which would certainly be the case for something equivalent to a Redstone 4) you absolutely do have to reboot. As for everything else, well, you can't really expect Windows to change how it loads executing files into memory. That would completely upend the entire architecture of the OS.
You have to reboot for it to take effect.  You do NOT have to reboot for it to simply finish installing, as with Windows.  Linux does not have the "Preparing to configure updates", "Installing update 1 of X", "please do not turn off your computer" issue that Windows has, not does it nag you to reboot, or prevent installation of other updates (it's rare that I have to install updates in separate batches, but guaranteed in Windows if you're setting up for the first time or it's been a while, and each batch requires a reboot in between for Windows but can go one after the other in Linux).
True, this is something that doesn't bother me as much as having to reboot at all because I tend to have a lot of stuff open, and the time it takes to restore everything can be a lot longer than "Installing update 1 of X" or even multiple reboots, but I can certainly see where it would bother other people.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 19, 2018, 03:26:21 PM
I also tend to shut down my computer whenever I go to bed, so for Linux kernel updates I don't do a separate reboot from that at all.  Windows, meanwhile would nag me again and again, possibly do it on its own if I didn't catch it in time, and if I didn't do a separate reboot, it would take a lot longer to shut down and start up during the normal shutdown/power-up, which I'd also find quite annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 19, 2018, 05:47:39 PM
Quote from: J N Winkler on July 19, 2018, 11:35:44 AM
Notwithstanding the multiple flavors of Unix shell, I think shell scripts are probably more portable than NT batch simply because the Unix substrate is more widely supported across multiple hardware and software platforms.  Microsoft's foray into Windows as mobile OS is increasingly deemed a failure, while Android, iOS, and MacOS are basically all Unix underneath the skin.

Shell scripting as end-user programming is more or less dead on Linux, having been mostly supplanted by Python. You still see shell scripts for simple things like configuration and setup of larger programs, but shell scripts are regarded as kind of a kludge to be avoided if possible. I will sometimes throw together a short shell script to issue a few commands in a batch (I had a program to kill and restart Skype during a period where it had a tendency to freeze), but once any sort of logic starts getting involved it is usually easier to do things in Python. Even for things like shell scripts using sed, often there's a better choice (Perl, for anything you might use sed for).

Quote from: J N Winkler on July 18, 2018, 11:21:31 AM
Quote from: Scott5114 on July 18, 2018, 07:53:23 AMI find Windows 10 to be incredibly unreliable. I have a dual-boot laptop, and I only use two applications on Windows: GRLevelX for tracking severe weather (because Oklahoma), and a driver program for my vinyl cutter. Windows is remarkably consistent at deciding the proper time to install updates is right when a tornado is bearing down on Cleveland County, leaving me without one of my tools to keep myself safe. The last severe weather event I even left the laptop powered on and booted into Windows for several hours when severe weather was predicted and it didn't go into update until the severe weather began.

Have you tried booting to Windows in good weather and running Windows Update with the force-update option, and then applying one of the registry hacks to prevent unwanted updates when you next boot it during a storm?  It is easy enough to apply and unapply registry hacks using batch files.

I haven't, although my plan for the next severe weather is to do a force-update in good weather. Unfortunately, my days off are Tuesday-Wednesday-Thursday, which means most of the severe weather I will be at home for and thus using the laptop will be occurring immediately after a Patch Tuesday.

I am very leery of messing with the Registry, as it represents a single point of failure in the OS, and I've had to wipe-and-reload Windows due to something smashing the Registry before. I would hope that in Windows 10 the Registry is not quite so fragile, but nonetheless it presents a risk that is not present when editing the analogous dotfiles on Linux.

One problem here is that I have not used Windows as my "daily driver" since XP, so I lack the acquaintance of Windows' internals that I had back then, having exchanged it for equivalent knowledge of Linux. This is my own failing, such as it is, but it does provide a handy excuse when someone is trying to rope me into fixing their broken computer for free.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on July 21, 2018, 11:35:33 AM
Here's a pretty major problem: if I leave a Google Maps tab open too long, sometimes trying to scroll or zoom the map will freeze my entire OS, leaving me with no recourse other than to do a hard reboot. This is in Chrome 67 on macOS 10.13.5, and I can think of at least three times this has happened.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on July 21, 2018, 12:49:10 PM
For me, occasionally the map will disappear, and the latitude, longitude, and zoom numbers in the URL will all be replaced with "NaN". Then, if I can reload the page, it will put me at max zoom at latitude-longitude 0,0 off the coast of Africa. It doesn't happen too often, but it pisses me off when it does.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on July 21, 2018, 02:25:46 PM
I guess we got to check for alternatives like Bing, OpenStreetmap and Mapquest who are still there.

What do you think of Here? http://wego.here.com
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 21, 2018, 02:52:49 PM
Quote from: Stephane Dumas on July 21, 2018, 02:25:46 PM
I guess we got to check for alternatives like Bing, OpenStreetmap and Mapquest who are still there.

What do you think of Here? http://wego.here.com

I really don't have any trouble with Google Maps, but Here isn't bad at all! Satellite imagery is a little blurry in the SEA area, but otherwise pretty up-to-date. As are the roads themselves. Couple of changes lately that have been reflected. There's even a roundabout on Here WeGo that Google doesn't have listed (Google (https://goo.gl/myiE3K), Here WeGo (https://goo.gl/7b1ct5)).
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on July 21, 2018, 02:58:31 PM
Quote from: jakeroot on July 21, 2018, 02:52:49 PM
Quote from: Stephane Dumas on July 21, 2018, 02:25:46 PM
I guess we got to check for alternatives like Bing, OpenStreetmap and Mapquest who are still there.

What do you think of Here? http://wego.here.com

I really don't have any trouble with Google Maps, but Here isn't bad at all! Satellite imagery is a little blurry in the SEA area, but otherwise pretty up-to-date. As are the roads themselves. Couple of changes lately that have been reflected. There's even a roundabout on Here WeGo that Google doesn't have listed (Google (https://goo.gl/myiE3K), Here WeGo (https://goo.gl/7b1ct5)).

It's pretty good with the roads themselves, but not necessarily with the highway designations. There are several route decommissionings, realignments, and the like that haven't been updated. But I guess it's no worse than Google, who has refused to listen to my edit requests.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 22, 2018, 12:24:30 AM
Quote from: Eth on July 21, 2018, 11:35:33 AM
Here's a pretty major problem: if I leave a Google Maps tab open too long, sometimes trying to scroll or zoom the map will freeze my entire OS, leaving me with no recourse other than to do a hard reboot. This is in Chrome 67 on macOS 10.13.5, and I can think of at least three times this has happened.

One could argue that that's MacOS's fault.  Nothing a user-mode program can do should be able to make the OS crash.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on July 22, 2018, 09:16:34 AM
Quote from: Stephane Dumas on July 21, 2018, 02:25:46 PM
I guess we got to check for alternatives like Bing, OpenStreetmap and Mapquest who are still there.

What do you think of Here? http://wego.here.com
The accuracy for my local area, in regards to street names, highway designations, and general correctness, "just f***ing SUCKS now".
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 22, 2018, 09:58:53 AM
Errors I can find:

Exits 19B-C on I-95/MA 128 are listed as 19A-B. Less than a year outdated.
US 4/MA 16 overlap isn't shown as a full freeway.
Exit 8 on the Everett Turnpike is listed as NH 101A Bypass. I'm pretty sure there's no such designation.
NH 122 continues into Massachusetts.
US 1A in Rhode Island is shown as RI 1A.
CT/RI 78 is not shown as a freeway.
RI 2 is shown on US 1 as if CT/RI 2 was a single route.
RI 103A is missing entirely.
MA 129 follows MA 129A through Lynn, and MA 129A isn't shown.
Old Dover Rd. in Rochester, NH is shown as NH 16B. It should be unnumbered. Similarly, part of NH 9 in the same area is shown as being overlapped with NH 16A.
MA 21 reaches I-91, Exit 2, which almost doubles its length.
MA 2 is not shown as a freeway between Exit 16 and Exit 28.
MA 125 got extended to MA 62 (about one mile).
Hopkinton, RI is listed twice.

Apple Maps has about the same number of errors.
Title: Re: Google Maps just fucking SUCKS now
Post by: jon daly on July 22, 2018, 11:52:58 AM
RI 2 is shown on US 1 as if CT/RI 2 was a single route.

This reminds me that I found an old topographical map that showed this as a multiplex, but that map was ooooold.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on July 22, 2018, 08:18:51 PM
Quote from: Stephane Dumas on July 18, 2018, 07:15:30 PM
Quote from: CtrlAltDel on July 18, 2018, 02:41:05 PM
The changes to Google Maps for developers have started manifesting themselves in certain end products, and I have to admit I'm feeling a loss.

Looks like it manifested on ACME Mapper with a message saying:"This page can't load Google Maps correctly" while MyTopo still works for now but for how long?

ACME Mapper now has the "For development purposes only" message on satellite views.  When I first read that Google would be doing that, I was expecting them to add a watermark server side like Historic Aerials.  I was pleasantly surprised to find that for now, it's just a DIV that I can block with an Adblock Plus filter:

mapper.acme.com##div[style="background-color: rgba(0, 0, 0, 0.496094); position: absolute; overflow: hidden; top: 0px; left: 0px; width: 256px; height: 256px; z-index: 100; "]

Hopefully, they don't start adding the watermark server side!
Title: Re: Google Maps just fucking SUCKS now
Post by: ftballfan on July 25, 2018, 06:47:50 PM
In Sandusky, OH, Rohde Street is marked as Rhode Street (confirmed as Rohde in the field)
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on July 26, 2018, 12:34:35 AM
Quote from: ftballfan on July 25, 2018, 06:47:50 PM
In Sandusky, OH, Rohde Street is marked as Rhode Street (confirmed as Rohde in the field)
A minor error is not a reason they fucking SUCK.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 26, 2018, 01:27:56 AM
Quote from: NE2 on July 26, 2018, 12:34:35 AM
A minor error is not a reason they fucking SUCK.

Of course, the reasons they fucking SUCKed have mostly gone by the wayside. I haven't had major issues like some here, granted, but even I've seen improvements in the last couple years. Still lacking in a couple departments (trips with more a dozen stops, for example), but vastly improved.

I would say, at this point, a more apt thread title would be "Google Maps still needs work".
Title: Re: Google Maps just SUCKS now
Post by: webny99 on July 26, 2018, 12:50:09 PM
Quote from: jakeroot on July 26, 2018, 01:27:56 AM
I would say, at this point, a more apt thread title would be "Google Maps still needs work".

True, although this is the go to thread for Google Maps issues, even if they're not glaring/large-scale failures.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 26, 2018, 02:14:58 PM
Quote from: webny99 on July 26, 2018, 12:50:09 PM
Quote from: jakeroot on July 26, 2018, 01:27:56 AM
I would say, at this point, a more apt thread title would be "Google Maps still needs work".

True, although this is the go to thread for Google Maps issues, even if they're not glaring/large-scale failures.

There is the Incorrect highways marked on Google Maps (https://www.aaroads.com/forum/index.php?topic=2001.0) thread for general non-technical issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on July 26, 2018, 05:17:22 PM
Last night, I found this (http://acme.com/updates/archive/203.html) blog post from the author of ACME Mapper.  It's nice to hear that he's actively trying to fix anything that breaks.  I remember that something broke (I don't remember what) on ACME Mapper when Google first released the new map style, even though the new style wasn't on ACME Mapper yet.  Within a week, it was fixed.
Title: Re: Google Maps just fucking SUCKS now
Post by: ET21 on July 27, 2018, 08:41:29 AM
Works for me now and have gotten used to the new updates
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on July 27, 2018, 05:32:40 PM
Probably discussed above somewhere, but I found a new way to get some of the recently retired "Lite" mode back by now using "Canvas" mode.  The URL would be "https://www.google.com/maps?force=canvas" which starts in 2D mode, which is essentially what "Lite" devolved into before it disappeared.  This saves me having to go to the settings every time to click off 3D, which is sluggish and completely unnecessary for me most of the time.

Now if we can just find the link to hide the search panel on the side.  I found some method that worked in good ol' Explorer and gives a full screen of the maps on launch, but doesn't have access to Streetview, so not good enough...


Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 28, 2018, 02:30:45 AM
Quote from: Roadrunner75 on July 27, 2018, 05:32:40 PM
Now if we can just find the link to hide the search panel on the side.  I found some method that worked in good ol' Explorer and gives a full screen of the maps on launch, but doesn't have access to Streetview, so not good enough...

Click the up arrow in the bottom left. I've addressed this above several times. If you don't remain logged in, it's going to reset itself every time. If you do stay logged in, it will stay hidden.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 28, 2018, 06:05:19 AM
Quote from: jakeroot on July 28, 2018, 02:30:45 AM
Quote from: Roadrunner75 on July 27, 2018, 05:32:40 PM
Now if we can just find the link to hide the search panel on the side.  I found some method that worked in good ol' Explorer and gives a full screen of the maps on launch, but doesn't have access to Streetview, so not good enough...

Click the up arrow in the bottom left. I've addressed this above several times. If you don't remain logged in, it's going to reset itself every time. If you do stay logged in, it will stay hidden.

That still won't fix it for me. I use private browsing (Safari's version of incognito) so that it doesn't clog my history.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 28, 2018, 06:20:19 AM
Quote from: 1 on July 28, 2018, 06:05:19 AM
Quote from: jakeroot on July 28, 2018, 02:30:45 AM
Quote from: Roadrunner75 on July 27, 2018, 05:32:40 PM
Now if we can just find the link to hide the search panel on the side.  I found some method that worked in good ol' Explorer and gives a full screen of the maps on launch, but doesn't have access to Streetview, so not good enough...

Click the up arrow in the bottom left. I've addressed this above several times. If you don't remain logged in, it's going to reset itself every time. If you do stay logged in, it will stay hidden.

That still won't fix it for me. I use private browsing (Safari's version of incognito) so that it doesn't clog my history.

If you want to remain anonymous, Google isn't going to be able to remember your settings. Therefore it's always going to reset back to standard view, which includes an open side bar.

By the way, "clog [your] history"? You can't clog your history. There's no upper limit. If you meant "keep it clean", that I understand. But what difference does it make? How often do you view your history? I only use it once in a blue moon to track down previously-viewed adult videos.

(it's friday -- I stay up late doing nothing productive)
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 28, 2018, 10:37:06 AM
Quote from: jakeroot on July 28, 2018, 06:20:19 AMBy the way, "clog [your] history"? You can't clog your history. There's no upper limit. If you meant "keep it clean", that I understand. But what difference does it make? How often do you view your history? I only use it once in a blue moon to track down previously-viewed adult videos.

I use it fairly often for many purposes, such as tracking down articles I read in the past few days but did not bookmark and now want to share on Facebook, or re-visiting project advertisement pages that may have had new content uploaded to them.  For previously viewed content that is not readily Googlable (e.g., did not show up in the first few Google results, or is buried by other hits on the same topic), going to browser history is often the last hope.

In Firefox, history is filtrable by URL fragment, so I tend not to worry too much about clogging from Google Maps entries, but I can understand that being a concern for others because URLs or parts thereof are not always as remembered.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 28, 2018, 01:25:19 PM
Quote from: J N Winkler on July 28, 2018, 10:37:06 AM
Quote from: jakeroot on July 28, 2018, 06:20:19 AMBy the way, "clog [your] history"? You can't clog your history. There's no upper limit. If you meant "keep it clean", that I understand. But what difference does it make? How often do you view your history? I only use it once in a blue moon to track down previously-viewed adult videos.

I use it fairly often for many purposes, such as tracking down articles I read in the past few days but did not bookmark and now want to share on Facebook, or re-visiting project advertisement pages that may have had new content uploaded to them.  For previously viewed content that is not readily Googlable (e.g., did not show up in the first few Google results, or is buried by other hits on the same topic), going to browser history is often the last hope.

In Firefox, history is filtrable by URL fragment, so I tend not to worry too much about clogging from Google Maps entries, but I can understand that being a concern for others because URLs or parts thereof are not always as remembered.

That's also a feature in Chrome (pic follows); not sure how many people still use browsers that aren't Chrome or Firefox, though.

I have used Chrome's history search to track down quite a few things in the past. Still waiting for the day when each page's text is archived in the search tool, and can be searched through via the history section. Maybe put a three day max on that, but it would be cool.

(https://i.imgur.com/Fx84WkK.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 28, 2018, 10:28:48 PM
Quote from: jakeroot on July 28, 2018, 06:20:19 AM
If you want to remain anonymous, Google isn't going to be able to remember your settings. Therefore it's always going to reset back to standard view, which includes an open side bar.
If they didn't insist on the sidebar being open by default, it wouldn't be a problem.

Incidentally, on the phone, it doesn't bother to remember either, which is weird because there's no incognito in the app.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 28, 2018, 11:00:22 PM
Quote from: vdeane on July 28, 2018, 10:28:48 PM
Quote from: jakeroot on July 28, 2018, 06:20:19 AM
If you want to remain anonymous, Google isn't going to be able to remember your settings. Therefore it's always going to reset back to standard view, which includes an open side bar.
If they didn't insist on the sidebar being open by default, it wouldn't be a problem.

Incidentally, on the phone, it doesn't bother to remember either, which is weird because there's no incognito in the app.

Perhaps not, but it's a 'problem' I solved weeks ago. Consider how many users might not be able to find the side bar if it weren't open by default; Google's choice makes sense. For those of us who don't need it, an extra step or two isn't ridiculous.

Side bar on Google Maps for the phone? I'm not familiar. The only side bar on mine has to be opened manually from the left.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 29, 2018, 12:05:34 AM
Honestly, the sidebar doesn't provide anything that isn't available elsewhere in the interface.  Traffic is already available in the menu.  Restaurants and whatnot are already easy to find by finding the shaded area on the map and looking at the icons for the businesses (does anyone even use the search results on the left?  Or is using the map only something those of us who are visual-spatial thinkers do?).

In fact, when I do open Google Maps for traffic, my actions are "close nag to enable notifications, hide sidebar, open menu, click traffic", so what used to be two clicks became four because my way of doing things and Google's don't match, and I tend not to change my ways unless something comes along that solves a pre-existing problem I had (on the other hand, if some company comes along and makes my way more annoying because they want me to be doing things a different way, then I just get stubborn and keep doing things my way no matter the costs).  That's probably why I liked technology better 10 years ago; back then, the paradigms I follow were still the main ones, so new features were ones I found to eliminate annoyances I had and make things easier; now, the dominant paradigms are ones that don't fit with the way I operate, so new "features" generally cause me annoyance.

Whenever I open Google Maps on my phone, it automatically opens an annoying panel on the bottom that looks just like the sidebar on the website.  Your's doesn't?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 29, 2018, 01:33:36 AM
Quote from: vdeane on July 29, 2018, 12:05:34 AM
(on the other hand, if some company comes along and makes my way more annoying because they want me to be doing things a different way, then I just get stubborn and keep doing things my way no matter the costs).

(https://i.imgur.com/RG0BS1U.gif)

Unfortunately, modern computing requires users to trust the internet, and adjust to change. If one does not trust the internet, the internet cannot trust back. Therefore every return to any website will be like visiting for the first time. I solved this problem by accepting a crowded history, blocking notifications, and staying logged in (I don't use Incognito, even to browse you-know-what). I'm willing to accept the risks. If you're not, by all means...but you have to be able to accept when your way of doing things causes you issues. You're not using the website the way Google intended for it to be used.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 29, 2018, 05:09:42 PM
Well, I have Aspergers, so change is something I just don't do.  Not if it isn't completely forced on me (which just makes me mad, so I'll resist in any way possible), or it's entirely my own decision.  I also absolutely detest the idea of companies dictating how I do things.  It's fine for them to provide a tool; it is NOT fine for them to also dictate to me how/when I'm supposed to use the tool, and build measures in to prevent me from doing anything else or to make such use annoying.  This is why I won't have anything to do with anything Apple does, for example.  It was one thing when their philosophy was restricted to them.  Now, it's pervasive, with Linux being the only holdout.

I don't really like the changes the internet has undergone either.  I was happier when it was mostly still Web 1.0 with forums and RSS.  I wouldn't mind Facebook if it would stop trying to decide for me what it thinks I want to see, I really like reading comments on news articles, and I do use Gmail and Google Calendar on the web, but that's about as far as I've taken it.  I don't really understand social media, to be honest.  I also don't see why people would put all their stuff on the cloud when hard drives plus backups are perfectly fine.  Why run the risk of your data going away if a company changes its policies or goes away, and why give up your fourth amendment rights and make things vulnerable to hackers?

Quite honestly, technology of the past was designed more for people like me, with Aseprgers, but now it's being redesigned for neurotypicals.  I don't like it.  Just one more thing to alienate me from the world, I suppose.

You also mentioned accepting risks, and that's also something I have trouble with.  I'm extraordinarily risk adverse.  I never even learned how to ride a bike without training wheels because I'm too afraid of falling (the fact that I have gross motor difficulties does not help).

Quote from: jakeroot on July 29, 2018, 01:33:36 AM
I don't use Incognito, even to browse you-know-what
I think you're the first person I've heard of who doesn't.  I also use incognito to bypass paywalls on news articles.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on July 30, 2018, 09:09:04 AM
Quote from: vdeane on July 29, 2018, 05:09:42 PM
I also don't see why people would put all their stuff on the cloud when hard drives plus backups are perfectly fine.  Why run the risk of your data going away if a company changes its policies or goes away, and why give up your fourth amendment rights and make things vulnerable to hackers?

Because if your house burns down, there goes both your original + your backup. One could store a backup on an offline drive and put it in a safety deposit box, but that is a lot of work if one needs to change the data. I like my method of using original + offline backup + Dropbox. For 95 percent of things I want to keep, this works. I'll take a chance on the other five percent.

QuoteQuite honestly, technology of the past was designed more for people like me, with Aseprgers, but now it's being redesigned for neurotypicals.  I don't like it.  Just one more thing to alienate me from the world, I suppose.

I'm sorry you feel that way, but people with Asperger's Syndrome make up approximately <1 percent of the population (https://en.wikipedia.org/wiki/Asperger_syndrome#Epidemiology). You can't expect a major company like Google to cater to you–or even the roadgeek community as a whole, as this thread demonstrates: we are a tiny minority of Google's userbase.

The whole "Asperger's vs neurotypicals" mentality helps no-one, either.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 30, 2018, 12:58:56 PM
Quote from: MNHighwayMan on July 30, 2018, 09:09:04 AM
Because if your house burns down, there goes both your original + your backup. One could store a backup on an offline drive and put it in a safety deposit box, but that is a lot of work if one needs to change the data. I like my method of using original + offline backup + Dropbox. For 95 percent of things I want to keep, this works. I'll take a chance on the other five percent.
I've been taking my external hard drive with me while traveling for exactly that reason (I used to leave it locked in my desk at work, but then my group was moved and my current cubicle doesn't have any lockable storage).

Quote
QuoteQuite honestly, technology of the past was designed more for people like me, with Aseprgers, but now it's being redesigned for neurotypicals.  I don't like it.  Just one more thing to alienate me from the world, I suppose.

I'm sorry you feel that way, but people with Asperger's Syndrome make up approximately <1 percent of the population (https://en.wikipedia.org/wiki/Asperger_syndrome#Epidemiology). You can't expect a major company like Google to cater to you–or even the roadgeek community as a whole, as this thread demonstrates: we are a tiny minority of Google's userbase.

The whole "Asperger's vs neurotypicals" mentality helps no-one, either.
And yet, somehow, technology used to be designed for such cases.  Google could well add the additional functionality without impeding existing use cases.  That's what Microsoft used to do with Windows (prior to Windows 8).  For some reason, they're choosing to give those of us with less common use cases a lesser experience.  Seriously, what happened?  Apple used to be just one company, and now their philosophy has taken over just about everything.

It doesn't help that everything is being phonefied.  Seriously, why are phones taking over as the dominant types of computers?  I only use mine if I'm bored or need to look something up when I'm away from my computer.  The screen size is too small and the less convenient interface resulting from not having a mouse (and not having a full-size or physical keyboard) means that you can't really do serious work on them.  Yet, somehow, they're taking over as the dominant form of computing.  Apps are displacing both websites and real programs alike.  Heck, just look at Windows 8 - Microsoft fully intended on deprecating the desktop completely and moving everything to Metro (never mind that Metro was less sophisticated of an interface than even Windows 2.0); they had to backtrack when Metro flopped HARD (largely because the phone/tablet market was already cornered between the iPhone and Android).  And speaking of tablets, I can't really think of what the use case of them is.  They're too big to have the convenience of a phone and too small to do the serious work of a desktop or laptop.

I can't really pinpoint WHY everything changed, but I can pinpoint WHEN - and that was the release of the iPhone 3G and the App Store.

The point is, there's no reason Google couldn't offer us a Maps product that was useful for both roadgeeks wanting to browse around and people looking to find restaurants and stuff (and I do use Google Maps for that too, just apparently not in the way most people do because I tend to favor the familiar (and such usually search for a specific place), and because my visual/spatial skills so far outstrip everything else).  They CHOOSE to use a low-contrast design that makes freeways and expressways fade into the background.  They CHOOSE to reduce the number of points we can set for "driving directions" (which I only use to get travel time for and to save routes for future trips).  They CHOOSE to place an annoying sidebar on the left side with features that were only a click away (if that) in the first place.  Why do they choose these things?  I just don't know.
Title: Re: Google Maps just fucking SUCKS now
Post by: jon daly on July 30, 2018, 01:43:13 PM
I don't use a smartphone at all. Mainly, I use the internet for things that require more reading than I imagine would be comfortable to do on such a small screen.

Wrt Google Maps, I do sometimes have trouble navigating to Streetview from an overhead map or satellite view.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 30, 2018, 02:31:09 PM
Quote from: vdeane on July 30, 2018, 12:58:56 PM
Quote from: MNHighwayMan on July 30, 2018, 09:09:04 AM
Because if your house burns down, there goes both your original + your backup. One could store a backup on an offline drive and put it in a safety deposit box, but that is a lot of work if one needs to change the data. I like my method of using original + offline backup + Dropbox. For 95 percent of things I want to keep, this works. I'll take a chance on the other five percent.
I've been taking my external hard drive with me while traveling for exactly that reason (I used to leave it locked in my desk at work, but then my group was moved and my current cubicle doesn't have any lockable storage).

You risk losing it that way. Or having it stolen. At least with cloud backups, it's always there. And if the service ever gets shut down, you just download the files onto a drive and then upload it somewhere else. Not that I've heard of a service being shut down. If they did, the files would likely get turned over to another company, rather than just up and disappearing.

Quote from: vdeane on July 29, 2018, 05:09:42 PM
Quote from: jakeroot on July 29, 2018, 01:33:36 AM
I don't use Incognito, even to browse you-know-what
I think you're the first person I've heard of who doesn't.  I also use incognito to bypass paywalls on news articles.

As I get older, that may change. I'm the only person who uses my computer, phone, etc so I didn't see the reason to be secretive. I'm obviously not browsing anything illegal, so worse case scenario someone stumbles upon my...vices, and they laugh or whatever. It's not like I'm alone! Anyone who says they don't peruse the lesser parts of the internet, is probably lying.

Quote from: vdeane on July 30, 2018, 12:58:56 PM
It doesn't help that everything is being phonefied. Seriously, why are phones taking over as the dominant types of computers?  I only use mine if I'm bored or need to look something up when I'm away from my computer.

What do you expect? Smartphone shipments have exploded since 2009 (https://goo.gl/NHzSTU).

Most people I know don't use even 5% of their computer's power. They use it to briefly browse the web, watch some videos, send some emails...the basics. Smartphones do all of these things just as well, and they tie into other devices (such as TV's, smart home devices, cars, etc) much better than a desktop. So, do you spend $600 on a device that sits still, and is bulky, despite it not doing anything more than a phone for most people, or do you just get a damn smartphone, which does everything you need, in your pocket? It's a no-brainer for most.

For me? I just bought a $5100 custom-built laptop for rendering purposes (it's basically a mobile workstation) -- I, and those like me, still have a use for a laptop. And I enjoy typing on a keyboard, so I can appreciate a computer. But my use-case is very unusual, and if I didn't play computer games and use hard-core programs, I probably would use my phone for almost everything (since it does most everything beyond those aforementioned programs).
Title: Re: Google Maps just fucking SUCKS now
Post by: hbelkins on July 30, 2018, 03:01:54 PM
Quote from: vdeane on July 29, 2018, 05:09:42 PM

Quote from: jakeroot on July 29, 2018, 01:33:36 AM
I don't use Incognito, even to browse you-know-what
I think you're the first person I've heard of who doesn't.  I also use incognito to bypass paywalls on news articles.

I haven't had any luck bypassing paywalls or article limits with incognito/private browsing on either Chrome or Firefox.
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on July 30, 2018, 03:06:16 PM
Quote from: hbelkins on July 30, 2018, 03:01:54 PM
Quote from: vdeane on July 29, 2018, 05:09:42 PM

Quote from: jakeroot on July 29, 2018, 01:33:36 AM
I don't use Incognito, even to browse you-know-what
I think you're the first person I've heard of who doesn't.  I also use incognito to bypass paywalls on news articles.

I haven't had any luck bypassing paywalls or article limits with incognito/private browsing on either Chrome or Firefox.

If the website has a limited number of articles you can view for free, incognito starts you anew every time.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on July 30, 2018, 03:17:33 PM
Quote from: vdeane on July 30, 2018, 12:58:56 PMAnd yet, somehow, technology used to be designed for such cases.  Google could well add the additional functionality without impeding existing use cases.  That's what Microsoft used to do with Windows (prior to Windows 8).  For some reason, they're choosing to give those of us with less common use cases a lesser experience.  Seriously, what happened?  Apple used to be just one company, and now their philosophy has taken over just about everything.

What has happened is that the tech companies are chasing profit.  One way of doing this is to redesign interfaces to attract free-spending normies rather than miserly power users.  (I fall into the latter category since my Google Maps usage produces tons of API calls and I give Google nothing back because my ad-blocking HOSTS file blocks pay-per-click and my script traffic ignores UTM cookies.)  Another part of the profit pursuit is converting fixed items (some maintainable by subscription, some not) such as the hardware, the OS, and pay-only-once software programs into services that yield an ongoing revenue stream.  Windows 10 is "free" only in the sense that is relatively easy to get without a cash payment; you pay for it through the nose with unblockable ads that disrupt focus and consume eyeball time.

Not all of that profit goes to Wall Street portfolio capitalists.  A lot of tech CEOs believe our political system is not capable of meeting the challenges of income inequality on top of the demographic time bomb of the aging boomer generation.  So they invest in condos in missile silos (each of which costs millions of dollars) or property in New Zealand.

Quote from: vdeane on July 30, 2018, 12:58:56 PMIt doesn't help that everything is being phonefied.  Seriously, why are phones taking over as the dominant types of computers?  I only use mine if I'm bored or need to look something up when I'm away from my computer.  The screen size is too small and the less convenient interface resulting from not having a mouse (and not having a full-size or physical keyboard) means that you can't really do serious work on them.

Why buy a Bobcat when a traditional backhoe can do so much more?  Yet Bobcats not only are the norm on construction sites, but have also been shown to increase productivity.

Portable computers do not have to be fully capable to allow some forms of serious work to be done.  For example, when I travel, I find it much easier to keep a travel diary on my phone with a Bluetooth keyboard than I do with a laptop, and if I type the diary directly into Evernote, I also get three layers of backup--one on the phone, one on Evernote's servers, and one on my local hard drive back home since I have the Evernote desktop program installed specifically to access the command-line API that allows me to run a script every night to back up my entire Evernote note collection.

I also serve on the board of my local library.  A week before the monthly meeting, I receive an agenda packet that usually runs to about fifty pages.  I have elected to have it sent to me as a PDF rather than as a printout through the mail.  I bring it to the meeting on my phone so I can refer to it.

I go to the gym three times a week and often find myself having to fill recovery time between sets.  If I am up to date on the New Yorker (I subscribe to the print version), I often take my phone with me onto the gym floor to read signing plans.  Right now I am working my way through the signing plans for the Yamatogawa Route expressway segment that is currently under construction near Osaka.

Though I don't like to do it, owing to the additional steps required to maintain a local archive of my own work, I have used Gmail on my phone to put out fires.  One recent example involved taking care of a business detail just before 5 PM on a Friday when I was at the gym and not scheduled to come home (where I could have used Thunderbird on my laptop) until 6.30 PM at the earliest.

Quote from: vdeane on July 30, 2018, 12:58:56 PMYet, somehow, they're taking over as the dominant form of computing.  Apps are displacing both websites and real programs alike.  Heck, just look at Windows 8 - Microsoft fully intended on deprecating the desktop completely and moving everything to Metro (never mind that Metro was less sophisticated of an interface than even Windows 2.0); they had to backtrack when Metro flopped HARD (largely because the phone/tablet market was already cornered between the iPhone and Android).

I don't think Metro failed just because Android and iOS already had incumbency advantage.  Those two other OSes just work, while anything Microsoft produces (even for the non-PC market) is crash-prone.  And the killer hardware for Metro, such as flat touchscreen desktops, never took off.

Quote from: vdeane on July 30, 2018, 12:58:56 PMAnd speaking of tablets, I can't really think of what the use case of them is.  They're too big to have the convenience of a phone and too small to do the serious work of a desktop or laptop.

Tablets are easier on older eyes.  While I use my phone in library board meetings, others who take agenda packets in PDF (such as our former president) use tablets.  Otherwise, they are well-suited for many types of work using Bluetooth peripherals, just as smartphones are.

Quote from: jeffandnicole on July 30, 2018, 03:06:16 PM
Quote from: hbelkins on July 30, 2018, 03:01:54 PMI haven't had any luck bypassing paywalls or article limits with incognito/private browsing on either Chrome or Firefox.

If the website has a limited number of articles you can view for free, incognito starts you anew every time.

It depends on the news site and where it is in its process of shutting off paywall leakage.  Incognito mode used to work quite well with the Washington Post but now does so no longer because they use browser treatment of UTM cookies to determine whether you are trying to evade the paywall.  The only reliable way to access Post articles "incognito" I have found is to download them through wget, stripping UTM references from the URL string, and then load the downloaded local copy in the browser, which cannot access the JavaScript (hosted server-side, I think) that partially covers the article text with a sidebar and prevents you from scrolling to read it.  I still read the occasional New York Times article using incognito but the article counter still increments.  Meanwhile, if I go to the Wichita Eagle, any article linked off the normally loaded main page will load in incognito, but any link off that article will go to the paywall if an incognito load is attempted.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 30, 2018, 03:25:11 PM
Quote from: jakeroot on July 30, 2018, 02:31:09 PM
You risk losing it that way. Or having it stolen. At least with cloud backups, it's always there. And if the service ever gets shut down, you just download the files onto a drive and then upload it somewhere else. Not that I've heard of a service being shut down. If they did, the files would likely get turned over to another company, rather than just up and disappearing.
I'm very pro-cloud storage but Barracuda did shut down their Copy service a few years back: https://www.theregister.co.uk/2016/02/04/barracuda_kills_cudadrive_and_copy_cloud_storage_services/

That might not mean much to you but they were the only one (that I'm aware of) that had more storage than Dropbox from the get go and had native Linux support.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 30, 2018, 09:05:04 PM
Quote from: jakeroot on July 30, 2018, 02:31:09 PM
What do you expect? Smartphone shipments have exploded since 2009 (https://goo.gl/NHzSTU).

Most people I know don't use even 5% of their computer's power. They use it to briefly browse the web, watch some videos, send some emails...the basics. Smartphones do all of these things just as well, and they tie into other devices (such as TV's, smart home devices, cars, etc) much better than a desktop. So, do you spend $600 on a device that sits still, and is bulky, despite it not doing anything more than a phone for most people, or do you just get a damn smartphone, which does everything you need, in your pocket? It's a no-brainer for most.

For me? I just bought a $5100 custom-built laptop for rendering purposes (it's basically a mobile workstation) -- I, and those like me, still have a use for a laptop. And I enjoy typing on a keyboard, so I can appreciate a computer. But my use-case is very unusual, and if I didn't play computer games and use hard-core programs, I probably would use my phone for almost everything (since it does most everything beyond those aforementioned programs).
Just because smartphones are everywhere doesn't mean other computers have to be turned into bigger versions of them.  As far as I'm concerned, they're two completely different devices, with different use cases.  I couldn't imagine even doing my primary web browsing on a phone or tablet.  Too small screen size, and the interface isn't as good with dealing with multiple tabs, and you don't have windows - everything is full screen.  I have a hard enough time having only a single monitor (alas, my desk doesn't really have room for a second) - it's hard to watch, say, a Roadwaywiz video at the same time as browsing here, for example.  I certainly couldn't compose the long an intricate replies with multiple quotes of parts of previous posts on a phone/tablet, either.  Much easier with a keyboard and especially a mouse (for selecting text).

I actually spent a bit more than that - getting something optimized for Linux isn't cheap, and I wanted something that could play Cities: Skylines.  Still, I'm hoping it will last a while, so I should get my money's worth.  My phone, meanwhile, was the cheapest thing I could get that wasn't refurbished.

Quote from: J N Winkler on July 30, 2018, 03:17:33 PM
It depends on the news site and where it is in its process of shutting off paywall leakage.  Incognito mode used to work quite well with the Washington Post but now does so no longer because they use browser treatment of UTM cookies to determine whether you are trying to evade the paywall.  The only reliable way to access Post articles "incognito" I have found is to download them through wget, stripping UTM references from the URL string, and then load the downloaded local copy in the browser, which cannot access the JavaScript (hosted server-side, I think) that partially covers the article text with a sidebar and prevents you from scrolling to read it.  I still read the occasional New York Times article using incognito but the article counter still increments.  Meanwhile, if I go to the Wichita Eagle, any article linked off the normally loaded main page will load in incognito, but any link off that article will go to the paywall if an incognito load is attempted.
Interesting... I haven't had that problem with Washington Post.  Its article count seems to reset every time.  I'd say Adblock Plus, but I actually have it disabled on Washington Post.  Maybe the fact that I block third party cookies?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 30, 2018, 10:58:10 PM
I use incognito and look at a bunch of articles on the Post and the Times daily.  I have yet to hit a limit when using incognito.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 31, 2018, 01:29:20 AM
Quote from: vdeane on July 30, 2018, 09:05:04 PM
Quote from: jakeroot on July 30, 2018, 02:31:09 PM
What do you expect? Smartphone shipments have exploded since 2009 (https://goo.gl/NHzSTU).

Most people I know don't use even 5% of their computer's power. They use it to briefly browse the web, watch some videos, send some emails...the basics. Smartphones do all of these things just as well, and they tie into other devices (such as TV's, smart home devices, cars, etc) much better than a desktop. So, do you spend $600 on a device that sits still, and is bulky, despite it not doing anything more than a phone for most people, or do you just get a damn smartphone, which does everything you need, in your pocket? It's a no-brainer for most.

For me? I just bought a $5100 custom-built laptop for rendering purposes (it's basically a mobile workstation) -- I, and those like me, still have a use for a laptop. And I enjoy typing on a keyboard, so I can appreciate a computer. But my use-case is very unusual, and if I didn't play computer games and use hard-core programs, I probably would use my phone for almost everything (since it does most everything beyond those aforementioned programs).
Just because smartphones are everywhere doesn't mean other computers have to be turned into bigger versions of them.  As far as I'm concerned, they're two completely different devices, with different use cases.  I couldn't imagine even doing my primary web browsing on a phone or tablet.  Too small screen size, and the interface isn't as good with dealing with multiple tabs, and you don't have windows - everything is full screen.  I have a hard enough time having only a single monitor (alas, my desk doesn't really have room for a second) - it's hard to watch, say, a Roadwaywiz video at the same time as browsing here, for example.  I certainly couldn't compose the long an intricate replies with multiple quotes of parts of previous posts on a phone/tablet, either.  Much easier with a keyboard and especially a mouse (for selecting text).

They are definitely two different devices, but they do very similar things on the basic level. It's the more complex tasks where they differ (obviously). In defence of mobile web browsing, apps are generally taking the place of general perusing, so usage of mobile browsers has limited importance. A lot of users here (definitely not me) seem to use the Tapatalk app, if that means anything.

Modern tablets have multi-window support. Hell, my Galaxy S8+ has multi-window support. It's two small windows, but it's technically multi window.

Also, modern phones have giant screens. Not tablet or computer size, but damn big compared to ten years ago.

Quote from: vdeane on July 30, 2018, 09:05:04 PM
I actually spent a bit more than that - getting something optimized for Linux isn't cheap, and I wanted something that could play Cities: Skylines.  Still, I'm hoping it will last a while, so I should get my money's worth.  My phone, meanwhile, was the cheapest thing I could get that wasn't refurbished.

I have a feeling I'm wasting my time, if I'm talking to someone who spent $5k+ on a computer. We are not normal! :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on July 31, 2018, 07:28:11 AM
Quote from: jakeroot on July 31, 2018, 01:29:20 AM
They are definitely two different devices, but they do very similar things on the basic level. It's the more complex tasks where they differ (obviously). In defence of mobile web browsing, apps are generally taking the place of general perusing, so usage of mobile browsers has limited importance. A lot of users here (definitely not me) seem to use the Tapatalk app, if that means anything.

I browse and comment on this forum perfectly fine in Chrome for Android on my GS7. The only thing that sucks, which someone previously mentioned, is parsing quotes using the mobile cursor, and I'm not sure the Tapatalk app would help with that issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 31, 2018, 01:00:40 PM
Honestly, I find browsing the forum on the phone to be cumbersome.  You need to zoom in and pan all around the screen, since the forum software doesn't have a mobile stylesheet.  Ignoring that, it would still be cumbersome for me since I tend to read everything in batches; most people seem to browse a bit here and there, or focus on views like "replies to your posts" or something like that, which would probably be easier than systemically searching out every thread with new posts and reading the ones in interesting threads verbatim.

Quote from: jakeroot on July 31, 2018, 01:29:20 AM
They are definitely two different devices, but they do very similar things on the basic level. It's the more complex tasks where they differ (obviously). In defence of mobile web browsing, apps are generally taking the place of general perusing, so usage of mobile browsers has limited importance. A lot of users here (definitely not me) seem to use the Tapatalk app, if that means anything.
Yeah, I never quite understood the whole app craze, at least not from the user's point of view (developers like them because of advertising, notifications, and being able to scoop up more user data).  Most mobile sites are fine.  Facebook stands out to me - the app is HUGE and tends to do rather intensive spying on users.  The latter would prevent me from installing it even if my phone had room to actually install apps, which is doesn't.  It's amazing how Android phones come pre-loaded with so much junk that there's no room for users to add anything, and the bloat only gets worse over time (it's far, far worse than Windows ever was; it used to have over a gigabyte of internal storage free, but now I'm lucky if I can squeeze out 400 megabytes!).  My phone is to the point where I have to clear the cache multiple times per day and keep automatic updates disabled, and it's only two years old, and pictures/music are already on the micro SD card.
Title: Re: Google Maps just fucking SUCKS now
Post by: silverback1065 on August 02, 2018, 07:31:58 AM
it doesn't suck anymore, this topic is unneeded
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 02, 2018, 07:36:59 AM
Quote from: silverback1065 on August 02, 2018, 07:31:58 AM
it doesn't suck anymore, this topic is unneeded

Until they change it again.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 04, 2018, 10:41:08 AM
OK, I just this minute re-loaded Google Maps, and suddenly it wasn't on Mercator projection anymore. I zoomed it out, and it's on a globe. :-/
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 04, 2018, 11:28:23 AM
Quote from: empirestate on August 04, 2018, 10:41:08 AMOK, I just this minute re-loaded Google Maps, and suddenly it wasn't on Mercator projection anymore. I zoomed it out, and it's on a globe. :-/

Same here, and with search on a specific location (I tried Moscow), there appears to be a second load (screen redraws) to convert from Mercator to whatever projection Maps is using for less-than-full-globe views (Robinson?).

Quote from: vdeane on July 30, 2018, 09:05:04 PMMy phone, meanwhile, was the cheapest thing I could get that wasn't refurbished.

I have found bargain basement is not the way to go, even for something that is not being used as a primary IT device.  My first phone was an entry-level Droid Razr M, acquired through my phone provider via a two-year plan with no supplemental charge.  It turned out not to have enough hardware capacity (not sure whether memory or CPU) to handle GPS recording reliably without daily rebooting, and after two years I was happy to decommission it.  My current phone is a Droid Turbo, phone plan + $200 supplementary charge, and it has been robust enough to handle everything I have thrown at it over four years, though the screen now shows noticeable burn-in from the status line and battery life is a lot shorter.

Quote from: vdeane on July 30, 2018, 09:05:04 PMInteresting... I haven't had that problem with Washington Post.  Its article count seems to reset every time.  I'd say Adblock Plus, but I actually have it disabled on Washington Post.  Maybe the fact that I block third party cookies?

I have disabled third-party cookies (I am on Firefox 48.0) and am now trying the Post every so often to see if I get redirected to the subscription page.  I still get a blue banner on the side to prompt me to disable tracking protection since I haven't configured Firefox to load new incognito windows with tracking protection disabled by default.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on August 04, 2018, 01:40:39 PM
ACME mapper switched from Google maps to Leaflet.js . http://acme.com/updates/archive/204.html

Now if only Bing's Steetside do cover Canada....
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 04, 2018, 02:07:31 PM
Quote from: empirestate on August 04, 2018, 10:41:08 AM
OK, I just this minute re-loaded Google Maps, and suddenly it wasn't on Mercator projection anymore. I zoomed it out, and it's on a globe. :-/

Wonder what took them so long. The world isn't flat.

The only reason flat maps exist was because spherical projection wasn't always an option. As far as I know.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on August 04, 2018, 03:23:55 PM
Quote from: jakeroot on August 04, 2018, 02:07:31 PM
Quote from: empirestate on August 04, 2018, 10:41:08 AM
OK, I just this minute re-loaded Google Maps, and suddenly it wasn't on Mercator projection anymore. I zoomed it out, and it's on a globe. :-/
Wonder what took them so long. The world isn't flat.

Gotta be able to develop the technology to be able to browse a virtual globe first. It's not a simple task, either in terms of tech, or in terms of having enough data to make it work. I remember when I first discovered Google Earth, nearly around the time it first came out, and thinking about how awesome it was, despite all the mismatched (and low resolution) aerial imagery that was often misaligned by several feet on the edges, among other issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 04, 2018, 04:16:18 PM
Quote from: MNHighwayMan on August 04, 2018, 03:23:55 PM
Quote from: jakeroot on August 04, 2018, 02:07:31 PM
Quote from: empirestate on August 04, 2018, 10:41:08 AM
OK, I just this minute re-loaded Google Maps, and suddenly it wasn't on Mercator projection anymore. I zoomed it out, and it's on a globe. :-/
Wonder what took them so long. The world isn't flat.
Gotta be able to develop the technology to be able to browse a virtual globe first. It's not a simple task, either in terms of tech, or in terms of having enough data to make it work. I remember when I first discovered Google Earth, nearly around the time it first came out, and thinking about how awesome it was, despite all the mismatched (and low resolution) aerial imagery that was often misaligned by several feet on the edges, among other issues.

It's true that a satellite-overlaid spherical earth is not perfect, but a spherical earth with a map overlay should be much easier, since it's just placing lines on a sphere. 3D mode on Google Maps' website has allowed users to zoom out and spin around a 3D globe for several years now (with a map overlay, no less), so it was just a matter of disabling the satellite imagery, me thinks.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on August 06, 2018, 02:27:36 PM
While the logic in moving Google Maps to a globe is sound and makes sense, I don't like it. Good news is, it's optional. Click the hamburger menu on the top left, then click Globe, and it will toggle it off.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 06, 2018, 04:39:25 PM
For more fun, switch to "satellite" in Globe mode, then zoom way, way out. :-)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 06, 2018, 07:08:04 PM
Quote from: doorknob60 on August 06, 2018, 02:27:36 PM
While the logic in moving Google Maps to a globe is sound and makes sense, I don't like it. Good news is, it's optional. Click the hamburger menu on the top left, then click Globe, and it will toggle it off.

Sound and sensical...still there are those that just don't like it. I really don't get it.

Quote from: empirestate on August 06, 2018, 04:39:25 PM
For more fun, switch to "satellite" in Globe mode, then zoom way, way out. :-)

Nice, I hadn't noticed that feature before! Always wanted to explore Mars.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 06, 2018, 09:32:09 PM
Quote from: jakeroot on August 06, 2018, 07:08:04 PM
Quote from: doorknob60 on August 06, 2018, 02:27:36 PMWhile the logic in moving Google Maps to a globe is sound and makes sense, I don't like it. Good news is, it's optional. Click the hamburger menu on the top left, then click Globe, and it will toggle it off.

Sound and sensical...still there are those that just don't like it. I really don't get it.

I can understand why people would want to turn it off.  If you do directions search for journeys long enough to involve curvature of the Earth (e.g., Los Angeles to New York), you lose the use of screen area off the "globe" and features are compressed as they run toward the globe edge.  In this context it is more trouble than it is worth, especially since great circle routes (for airborne options) will still display correctly in both map and globe view--it is just that they appear as curves in the former.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 06, 2018, 09:42:50 PM
Agreed.  The globe is cool, and makes it easier to see why "curved" lines are the way they are, but it also looks odd at certain zoom levels (generally the ones that are far enough out to see the curvature but not the horizon), and you do see less when zoomed far enough to see the globe.  It does, however, allow me to confirm something that I long suspected: that Google Maps does not have tiles all the way down to the South Pole.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 07, 2018, 04:07:13 AM
Quote from: J N Winkler on August 06, 2018, 09:32:09 PM
Quote from: jakeroot on August 06, 2018, 07:08:04 PM
Quote from: doorknob60 on August 06, 2018, 02:27:36 PMWhile the logic in moving Google Maps to a globe is sound and makes sense, I don't like it. Good news is, it's optional. Click the hamburger menu on the top left, then click Globe, and it will toggle it off.

Sound and sensical...still there are those that just don't like it. I really don't get it.

I can understand why people would want to turn it off.  If you do directions search for journeys long enough to involve curvature of the Earth (e.g., Los Angeles to New York), you lose the use of screen area off the "globe" and features are compressed as they run toward the globe edge.  In this context it is more trouble than it is worth, especially since great circle routes (for airborne options) will still display correctly in both map and globe view--it is just that they appear as curves in the former.

I'm not seeing that. Viewing a map of the US, it's almost impossible to notice any curvature. Viewing a flight from SEA to LGW looks like this (below). Even in cases where it's impossible to view two airports at once, what's stopping users from slightly moving the map to see the rest of the route? Besides, viewing any such route on a flat map could mislead users into thinking the distance being covered is less than it really is (due to flat map inaccuracies).

(https://i.imgur.com/DnW64zR.png)

Now, I'm not saying there's no use for a flat map (if there weren't, they wouldn't have given users the option to exit "globe" mode), but flat maps are geographically incorrect, no matter how they're displayed. Google's job, being (to a degree) a mapping company, should be to, as accurately as possible, map the earth as we know it. This is best done by displaying the map as a sphere. Keep the flat map around for the extremely unusual circumstances that require it, fine. But would I go back to Google Maps a week ago, when there was no globe mode for map? Not a chance. Globe mode is a good addition with, as implemented, zero drawbacks.

Quote from: vdeane on August 06, 2018, 09:42:50 PM
you do see less when zoomed far enough to see the globe.

Sure, but did you ever do that before? I can only look at one section of a map at a time, and I don't mind spinning a sphere around to see a different part of the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 07, 2018, 10:42:36 AM
Have to say I am a fan of the globe.  Accurately comparing the size of Great Britain to Borneo is practically impossible in any 2D projection given their latitudes (even in my beloved Dymaxion projection). The Google globe is the closest I have seen to the fact that Borneo dwarfs Great Britain in size.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 07, 2018, 11:02:57 AM
Quote from: jakeroot on August 07, 2018, 04:07:13 AM
Now, I'm not saying there's no use for a flat map (if there weren't, they wouldn't have given users the option to exit "globe" mode), but flat maps are geographically incorrect, no matter how they're displayed. Google's job, being (to a degree) a mapping company, should be to, as accurately as possible, map the earth as we know it. This is best done by displaying the map as a sphere. Keep the flat map around for the extremely unusual circumstances that require it, fine. But would I go back to Google Maps a week ago, when there was no globe mode for map? Not a chance. Globe mode is a good addition with, as implemented, zero drawbacks.

To be fair, it's still a flat map. It's a representation of a globe on a 2D screen, so the map is still distorted as our eye travels farther from the center of the image. And so, as you point out, all flat maps are geographically inaccurate in some way.

The globe view does offer the advantage, in that respect, of representing a 3D figure that our eyes and brains readily understand, so we can absorb much of the "responsibility" of compensating for the distortion, in lieu of things like complicated scale graphs that appear on traditional flat map projections.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 07, 2018, 11:53:41 AM
Quote from: jakeroot on August 07, 2018, 04:07:13 AMI'm not seeing that. Viewing a map of the US, it's almost impossible to notice any curvature.

I see curvature even with directions search for Wichita to Topeka (shortest driving distance of 139 miles).  Also, as Google Maps is currently configured, the flat projection loads first, then there is a pause, and the globe loads, which is a cognitive speed bump that hits just as you are starting to parse the detail.

Quote from: jakeroot on August 07, 2018, 04:07:13 AMBesides, viewing any such route on a flat map could mislead users into thinking the distance being covered is less than it really is (due to flat map inaccuracies).

Eh?  On a flat map distances look longer the further away from the equator the origin and destination are.

Quote from: jakeroot on August 07, 2018, 04:07:13 AM
Quote from: vdeane on August 06, 2018, 09:42:50 PM
you do see less when zoomed far enough to see the globe.

Sure, but did you ever do that before? I can only look at one section of a map at a time, and I don't mind spinning a sphere around to see a different part of the map.

I have done it.  Moscow-Vladivostok is noticeably less convenient to look at in globe view than in map view because of the edge distortion and the fact the route track covers a much smaller portion of the screen.  This appears to be because Google programs the initial view to show the origin point (Moscow in this case) in roughly the same place (horizontal middle of the upper quarter of the screen) in both map view and globe view.  As a result, on my 1920 x 1080 screen with side bar left open, almost all of Africa (completely irrelevant to this search) is visible in both globe view and map view, and the route track is about three times shorter in globe view than in map view.

Route length on initial load appears to be close to the same in globe view and map view only up to desert-belt latitudes--e.g. Sydney to Perth, or Jacksonville to Los Angeles.

And before you ask, yes, I was looking up Moscow-Vladivostok long before globe view became available, because I found Russian highway construction documentation online last month and this resurrected my daydream of driving the Amur Highway.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 07, 2018, 12:49:30 PM
True.  Plus I've been known to look at far-out views to get overviews of continents or to compare what places have street view and which ones don't.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 07, 2018, 02:46:34 PM
Quote from: empirestate on August 07, 2018, 11:02:57 AM
Quote from: jakeroot on August 07, 2018, 04:07:13 AM
Now, I'm not saying there's no use for a flat map (if there weren't, they wouldn't have given users the option to exit "globe" mode), but flat maps are geographically incorrect, no matter how they're displayed. Google's job, being (to a degree) a mapping company, should be to, as accurately as possible, map the earth as we know it. This is best done by displaying the map as a sphere. Keep the flat map around for the extremely unusual circumstances that require it, fine. But would I go back to Google Maps a week ago, when there was no globe mode for map? Not a chance. Globe mode is a good addition with, as implemented, zero drawbacks.

To be fair, it's still a flat map. It's a representation of a globe on a 2D screen, so the map is still distorted as our eye travels farther from the center of the image. And so, as you point out, all flat maps are geographically inaccurate in some way.

The globe view does offer the advantage, in that respect, of representing a 3D figure that our eyes and brains readily understand, so we can absorb much of the "responsibility" of compensating for the distortion, in lieu of things like complicated scale graphs that appear on traditional flat map projections.

It's the best we can do with computers, though. And, it's far better than a flat map when representing true size and distance.

Quote from: J N Winkler on August 07, 2018, 11:53:41 AM
Quote from: jakeroot on August 07, 2018, 04:07:13 AM
I'm not seeing that. Viewing a map of the US, it's almost impossible to notice any curvature.

I see curvature even with directions search for Wichita to Topeka (shortest driving distance of 139 miles).  Also, as Google Maps is currently configured, the flat projection loads first, then there is a pause, and the globe loads, which is a cognitive speed bump that hits just as you are starting to parse the detail.

Must be your computer. For me, globe mode only starts to become clear around the 20-mi scale mark (well out from the default starting point of 1000-ft scale). Here's a map of the Topeka/Wichita area on my computer, with globe enabled. No obvious signs of curvature: https://i.imgur.com/aegsB9d.png

Quote from: J N Winkler on August 07, 2018, 11:53:41 AM
Quote from: jakeroot on August 07, 2018, 04:07:13 AM
Besides, viewing any such route on a flat map could mislead users into thinking the distance being covered is less than it really is (due to flat map inaccuracies).

Eh?  On a flat map distances look longer the further away from the equator the origin and destination are.

My bad. *More than it really is. I should proofread a bit better when posting that late.

Quote from: J N Winkler on August 07, 2018, 11:53:41 AM
Quote from: jakeroot on August 07, 2018, 04:07:13 AM
Quote from: vdeane on August 06, 2018, 09:42:50 PM
you do see less when zoomed far enough to see the globe.

Sure, but did you ever do that before? I can only look at one section of a map at a time, and I don't mind spinning a sphere around to see a different part of the map.

I have done it.  Moscow-Vladivostok is noticeably less convenient to look at in globe view than in map view because of the edge distortion and the fact the route track covers a much smaller portion of the screen.  This appears to be because Google programs the initial view to show the origin point (Moscow in this case) in roughly the same place (horizontal middle of the upper quarter of the screen) in both map view and globe view.  As a result, on my 1920 x 1080 screen with side bar left open, almost all of Africa (completely irrelevant to this search) is visible in both globe view and map view, and the route track is about three times shorter in globe view than in map view.

Route length on initial load appears to be close to the same in globe view and map view only up to desert-belt latitudes--e.g. Sydney to Perth, or Jacksonville to Los Angeles.

And before you ask, yes, I was looking up Moscow-Vladivostok long before globe view became available, because I found Russian highway construction documentation online last month and this resurrected my daydream of driving the Amur Highway.

I made a gif of the Moscow-Vladivostok drive, switching between globe and flat modes (default view for both). Definitely some obvious, and perhaps annoying, curvature in globe mode. But I don't see any advantage, beyond just looking at the route quickly, of viewing the route from that far out. My first instinct would always be to zoom in to view the route in more detail. Globe mode is not meant to provide great detail, obviously, since less map can be displayed at once than using the flat mode. But it does provide a more accurate representation of the route, and once you zoom in to view more detail, the globe effects are not anywhere near as noticeable (though still perhaps having a positive effect on size and scale).

(https://i.imgur.com/DXDWB52.gif)

Quote from: vdeane on August 07, 2018, 12:49:30 PM
True.  Plus I've been known to look at far-out views to get overviews of continents or to compare what places have street view and which ones don't.

If you zoom all the way out in globe mode, and grab the pegman, you can drag him to the edges of the screen and the globe will spin in the appropriate direction. Flat map has this feature, but it makes it easier to see which countries have street view without having to put the pegman back and keep spinning.

I have noticed that, in flat mode, not all of the earth is visible at the 1000-mi scale point (all the way out for me). For instance, I can't see Hawaii and New Zealand on the same screen, when the former is placed on the west edge of the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 07, 2018, 04:31:34 PM
Jakeroot--the difference between map and globe seems to be much less pronounced on your PC.  Here is what it looks like on mine:

(https://i.imgur.com/bF6IKBm.gif)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 07, 2018, 05:00:39 PM
Quote from: J N Winkler on August 07, 2018, 04:31:34 PM
Jakeroot--the difference between map and globe seems to be much less pronounced on your PC.  Here is what it looks like on mine:

https://i.imgur.com/bF6IKBm.gif

Yikes! No wonder you guys hate the new globe mode. Weird that it would display so differently. I see you're using Firefox, instead of the memory-hungry Chrome. Maybe that's the difference? Vdeane, which browser do you use?

To be sure that I wasn't experiencing something unusual, I opened a new tab, went back to GMaps, hit the "directions" button, entered in Moscow (waited for it to pull up Moscow), entered in Vladivostok, hit "enter", and then it pulled up the overview. It pulled up the same view as in my gif.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on August 07, 2018, 05:13:38 PM
Let me just say that this new globe feature is probably going to tick off a few of those crazy Flat-Earthers. ;)
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on August 07, 2018, 05:26:40 PM
Quote from: 20160805 on August 07, 2018, 05:13:38 PM
Let me just say that this new globe feature is probably going to tick off a few of those crazy Flat-Earthers. ;)

Don't worry, they'll just call it "fake news".
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 07, 2018, 06:12:39 PM
Quote from: jakeroot on August 07, 2018, 02:46:34 PM
Quote from: empirestate on August 07, 2018, 11:02:57 AM

To be fair, it's still a flat map. It's a representation of a globe on a 2D screen, so the map is still distorted as our eye travels farther from the center of the image. And so, as you point out, all flat maps are geographically inaccurate in some way.

The globe view does offer the advantage, in that respect, of representing a 3D figure that our eyes and brains readily understand, so we can absorb much of the "responsibility" of compensating for the distortion, in lieu of things like complicated scale graphs that appear on traditional flat map projections.

It's the best we can do with computers, though.

Sure; it's a very useful tool. My point simply is that it is also geographically inaccurate, as it is also a flat map.

QuoteAnd, it's far better than a flat map when representing true size and distance.

Well, because we compensate for its distortion as we view it; essentially, our eyes create an optical illusion that happens to give us a more correct image, rather than the less correct one that most illusions produce. (You could argue that the same thing happens when we look at a real globe–we can't see around the other side of the globe, but we can move it around and relate what we see to what we remember seeing when the globe was in a different position.)

We also compensate for other flat maps, of course: with Google's Mercator display, we compensate for the distortion at high latitudes when we view the map at large scales. A map of Alaska, viewed in Mercator at a close zoom level, is substantially in scale with itself, even though it's grossly out of scale to a map of Puerto Rico at the same zoom level.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on August 07, 2018, 06:28:54 PM
Quote from: jakeroot on August 07, 2018, 05:00:39 PM
Quote from: J N Winkler on August 07, 2018, 04:31:34 PM
Jakeroot--the difference between map and globe seems to be much less pronounced on your PC.  Here is what it looks like on mine:

https://i.imgur.com/bF6IKBm.gif

Yikes! No wonder you guys hate the new globe mode. Weird that it would display so differently. I see you're using Firefox, instead of the memory-hungry Chrome. Maybe that's the difference? Vdeane, which browser do you use?

Maybe the difference is related to the window size/screen resolution. My browser window is 1152x980 (not maximized, so that's only part of the screen) and what I see falls somewhere in between what the two of you have shown.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 07, 2018, 06:55:18 PM
Quote from: jakeroot on August 07, 2018, 05:00:39 PMYikes! No wonder you guys hate the new globe mode. Weird that it would display so differently. I see you're using Firefox, instead of the memory-hungry Chrome. Maybe that's the difference?

Speaking for myself, I don't hate globe view, but with the usability issues it creates on my system, I am happy to have the ability to turn it off as needed.  I'm happy you had the idea of posting a screen comparison as an animated GIF because otherwise it would not have occurred to me that there would be such an enormous difference in screen rendering.

And yes, it is Firefox 48.0 under Windows 7 with a screen resolution of 1920 x 1080.  Both maps were pulled up by entering {Moscow, Russia to Vladivostok, Russia} (no braces) in the search plugin box and choosing a Google Maps search plugin.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 07, 2018, 08:56:33 PM
Yeah, I suspect screen resolution is the big thing.  Mine varies based on whether Chrome is maximized or not (which it almost never is).

Quote from: jakeroot on August 07, 2018, 02:46:34 PM
If you zoom all the way out in globe mode, and grab the pegman, you can drag him to the edges of the screen and the globe will spin in the appropriate direction. Flat map has this feature, but it makes it easier to see which countries have street view without having to put the pegman back and keep spinning.

I have noticed that, in flat mode, not all of the earth is visible at the 1000-mi scale point (all the way out for me). For instance, I can't see Hawaii and New Zealand on the same screen, when the former is placed on the west edge of the map.
True, though the fact that I can see less is an annoyance when zoomed out far.  And, of course, it is an adjustment when you've been using mercator for so long.  I routinely hit zoom level 5 when quickly panning across the US, and even further out if panning overseas (yeah, I still pan to different places rather than use search).
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on August 07, 2018, 10:17:58 PM
I guess I'm missing out on all the fun of "Globe Mode".  I was wondering where this even was until I realized I was still defaulting (via Bookmark link) to "Lite" mode (2D) which doesn't have it, which is just fine with me.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 08, 2018, 02:15:54 AM
Quote from: Eth on August 07, 2018, 06:28:54 PM
Quote from: jakeroot on August 07, 2018, 05:00:39 PM
Quote from: J N Winkler on August 07, 2018, 04:31:34 PM
Jakeroot--the difference between map and globe seems to be much less pronounced on your PC.  Here is what it looks like on mine:

https://i.imgur.com/bF6IKBm.gif

Yikes! No wonder you guys hate the new globe mode. Weird that it would display so differently. I see you're using Firefox, instead of the memory-hungry Chrome. Maybe that's the difference? Vdeane, which browser do you use?

Maybe the difference is related to the window size/screen resolution. My browser window is 1152x980 (not maximized, so that's only part of the screen) and what I see falls somewhere in between what the two of you have shown.

Normally, I would say that would be the normal culprit. A small window wouldn't work as well with this feature. But Winkler's experience is apparently worse than yours, despite using a higher resolution and full screen.

Quote from: vdeane on August 07, 2018, 08:56:33 PM
I routinely hit zoom level 5 when quickly panning across the US, and even further out if panning overseas (yeah, I still pan to different places rather than use search).

Actually I do that too. Mostly in Google Earth, since it has to do that god-damn animation every time you search for some place else. Sometimes I'll pan to challenge my memory; I use search far more often, though.

Quote from: J N Winkler on August 07, 2018, 06:55:18 PM
Quote from: jakeroot on August 07, 2018, 05:00:39 PMYikes! No wonder you guys hate the new globe mode. Weird that it would display so differently. I see you're using Firefox, instead of the memory-hungry Chrome. Maybe that's the difference?

Speaking for myself, I don't hate globe view, but with the usability issues it creates on my system, I am happy to have the ability to turn it off as needed.  I'm happy you had the idea of posting a screen comparison as an animated GIF because otherwise it would not have occurred to me that there would be such an enormous difference in screen rendering.

I was just really confused. Unlike other issues with Maps, I really didn't notice this one. So when the complaints started rolling in, I just assumed it was because users here don't seem to like change. Apparently things changed more for other users!

Quote from: J N Winkler on August 07, 2018, 06:55:18 PM
And yes, it is Firefox 48.0 under Windows 7 with a screen resolution of 1920 x 1080.  Both maps were pulled up by entering {Moscow, Russia to Vladivostok, Russia} (no braces) in the search plugin box and choosing a Google Maps search plugin.

Most oddly, although the browser is different, I'm running the same 1920x1080 resolution. I am just stumped. You don't use any UI scaling, do you? Your UX seems slightly larger than mine. Maybe that's just a Windows 10 thing.

Here's a video I made using Google Maps on my computer/browser/resolution combo. Anyone else's look like this? Or just me?

https://youtu.be/BE9Znn1lSXQ
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 08, 2018, 12:14:18 PM
Quote from: jakeroot on August 08, 2018, 02:15:54 AMMost oddly, although the browser is different, I'm running the same 1920x1080 resolution. I am just stumped. You don't use any UI scaling, do you? Your UX seems slightly larger than mine. Maybe that's just a Windows 10 thing.

I don't scale anything at the level of the OS.  In Firefox, however, I scale things up by a factor that corresponds to 4 mouse wheel clicks larger than normal size and between 3 and 4 strikes of the Ctrl+Plus key combination.  (Mouse wheel and keyboard seem to use different incrementing schemes and I cannot reach my preferred scale on the keyboard.)  However, while this affects the size of text I see on this forum and on other websites, it doesn't affect Google Maps rendering in either globe or map view.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 08, 2018, 06:11:27 PM
Quote from: J N Winkler on August 08, 2018, 12:14:18 PM
Quote from: jakeroot on August 08, 2018, 02:15:54 AMMost oddly, although the browser is different, I'm running the same 1920x1080 resolution. I am just stumped. You don't use any UI scaling, do you? Your UX seems slightly larger than mine. Maybe that's just a Windows 10 thing.

I don't scale anything at the level of the OS.  In Firefox, however, I scale things up by a factor that corresponds to 4 mouse wheel clicks larger than normal size and between 3 and 4 strikes of the Ctrl+Plus key combination.  (Mouse wheel and keyboard seem to use different incrementing schemes and I cannot reach my preferred scale on the keyboard.)  However, while this affects the size of text I see on this forum and on other websites, it doesn't affect Google Maps rendering in either globe or map view.

Have you tried using Google Maps on another browser?

That's probably not a realistic long-term solution, but I am curious if Firefox is to blame.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on August 08, 2018, 09:33:28 PM
Works just fine for me in Firefox.  Using Firefox 61.0.1 on Ubuntu MATE 18.04, with my $60 desktop. :nod:  It's a Lenovo ThinkCentre M79, AMD A4-6300B dual core 3.7 GHz, 8 GB DDR3-1600 RAM, AMD Radeon 8370D graphics - definitely not a high end machine but it is modern.  Regardless, seems to work fine, and Linux is pesky with non-Intel video drivers.

Display resolution is 1600x900 on some HP monitor my friend got at a Goodwill for $3 (and yes, that works fine too!).

(https://cdn.pbrd.co/images/HyiL4Jl.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 09, 2018, 04:40:00 AM
Quote from: ipeters61 on August 08, 2018, 09:33:28 PM
Works just fine for me in Firefox.  Using Firefox 61.0.1 on Ubuntu MATE 18.04, with my $60 desktop. :nod:  It's a Lenovo ThinkCentre M79, AMD A4-6300B dual core 3.7 GHz, 8 GB DDR3-1600 RAM, AMD Radeon 8370D graphics - definitely not a high end machine but it is modern.  Regardless, seems to work fine, and Linux is pesky with non-Intel video drivers.

Display resolution is 1600x900 on some HP monitor my friend got at a Goodwill for $3 (and yes, that works fine too!).

https://cdn.pbrd.co/images/HyiL4Jl.png

I'll wait for Winkler to chime in and confirm that Chrome or Edge have the same issue (if that's the case), but until then, I'm still baffled.

$3 wide-screen monitor with a resolution higher than 720p?! Not a bad deal!
Title: Re: Google Maps just fucking SUCKS now
Post by: Kulerage on August 09, 2018, 12:18:02 PM
The globe is fine to me. We don't have the horrible Mercator Projection anymore.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 09, 2018, 01:22:54 PM
Quote from: jakeroot on August 09, 2018, 04:40:00 AMI'll wait for Winkler to chime in and confirm that Chrome or Edge have the same issue (if that's the case), but until then, I'm still baffled.

The issue is present but less pronounced in Internet Explorer version 11.0 with zoom returned to the neutral level:

(https://i.imgur.com/ypISie6.gif)
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 09, 2018, 03:48:52 PM
Quote from: J N Winkler on August 09, 2018, 01:22:54 PM
Quote from: jakeroot on August 09, 2018, 04:40:00 AMI'll wait for Winkler to chime in and confirm that Chrome or Edge have the same issue (if that's the case), but until then, I'm still baffled.

The issue is present but less pronounced in Internet Explorer version 11.0 with zoom returned to the neutral level:

(https://i.imgur.com/ypISie6.gif)

Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.

Well, he can't use Edge because he only has Windows 7. Agreed that IE is not optimal for GMaps browsing, although it appears to be superior to Firefox for this purpose.

Maybe it's a Windows 7 thing.

Mr Winkler, can you try Chrome to be sure it doesn't have the issue as well? Or do you not like that browser?
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on August 09, 2018, 04:02:21 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PM
Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.
Well, he can't use Edge because he only has Windows 7. Agreed that IE is not optimal for GMaps browsing, although it appears to be superior to Firefox for this purpose.

Besides that, I guess I just don't understand what the problem is. Of course it's going to look different if you're viewing the route in the Mercator projection vs a globe.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 09, 2018, 04:08:35 PM
Quote from: MNHighwayMan on August 09, 2018, 04:02:21 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PM
Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.
Well, he can't use Edge because he only has Windows 7. Agreed that IE is not optimal for GMaps browsing, although it appears to be superior to Firefox for this purpose.
Besides that, I guess I just don't understand what the problem is. Of course it's going to look different if you're viewing the route in the Mercator projection vs a globe.

If you look at the gif's and video on the last page, the way globe mode renders on my computer is radically different than the way it renders on J N Winkler's computer, despite us using the same resolution monitor. It isn't really a Mercator vs sphere issue. It's a "why does globe mode look like shit on my PC but not on someone else's" issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 09, 2018, 04:17:26 PM
Looks good on Safari.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 09, 2018, 04:19:37 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PMMaybe it's a Windows 7 thing.

Mr Winkler, can you try Chrome to be sure it doesn't have the issue as well? Or do you not like that browser?

I went ahead and installed the current version of Chrome (64-bit for Windows 10/8.x/7):

(https://i.imgur.com/pRFYzzL.gif)

Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PMYour problem is using Internet Explorer.

The same issue is present to varying degrees in Firefox, IE, and Chrome.  And BTW, I don't use IE by choice.  Before I fired it up this morning for the specific purpose of checking globe view rendering, I had last loaded it about four months ago when I was trying to see if I could get the Java applet for "classic view" on MnDOT's EDMS to work.  (The search interface MnDOT now promotes, eDIGS, is much more robust, but the metadata it shows and uses in keyword search is much more limited, and does not include work type for construction projects.)

Quote from: MNHighwayMan on August 09, 2018, 04:02:21 PMBesides that, I guess I just don't understand what the problem is. Of course it's going to look different if you're viewing the route in the Mercator projection vs a globe.

On my PC there is more wasted screen area and more distortion in the route displayed in globe view on initial load.

Quote from: jakeroot on August 09, 2018, 04:08:35 PMIf you look at the gif's and video on the last page, the way globe mode renders on my computer is radically different than the way it renders on J N Winkler's computer, despite us using the same resolution monitor. It isn't really a Mercator vs sphere issue. It's a "why does globe mode look like shit on my PC but not on someone else's" issue.

Exactly.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 09, 2018, 04:50:27 PM
Quote from: J N Winkler on August 09, 2018, 04:19:37 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PMMaybe it's a Windows 7 thing.

Mr Winkler, can you try Chrome to be sure it doesn't have the issue as well? Or do you not like that browser?

I went ahead and installed the current version of Chrome (64-bit for Windows 10/8.x/7):

(https://i.imgur.com/pRFYzzL.gif)

Well, as with IE, it's better than Firefox, but still not optimal. Still confused as to why it wouldn't zoom in more. The route is definitely centered between the right edge of the navigation panel and the screen edge (unlike what Firefox was doing), but it's still zoomed way too far out.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on August 10, 2018, 06:17:44 PM
Since I'm using an old computer with Windows XP, I can't use 3D mode.  I used it within the past week or two on a friend's Windows 7 laptop, and "diving" into Street View looked cool, but I don't think it has any more value than just being eye candy.  One issue I've had is with Street View in Firefox or in Chrome with a spoofed Firefox useragent.  In these cases, there is a "space warp" effect on the image.




Last night, I was tracking an Amtrak train on my friend's (same one as above) Note 8.  It was annoying that I had to use two fingers to pan the map.  It shows the message "use two fingers to move the map", similar to the message about using [CTRL] and the mouse wheel to zoom.  As soon as I saw it, I thought "Oh great, the mobile version of 'use ctrl + scroll to zoom the map'".  I was going to say I don't have any idea why they did this, but I just realized that there could be a fullscreen map on a webpage, and you can't use a scrollbar like on a computer.  As I'm typing this, I'm wondering if this is more of the "mobile first" approach that companies and websites seem to be taking.  It's like they're forgetting that computers exist, and I'm not a fan of it, but that's a whole different topic.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 10, 2018, 09:24:24 PM
Quote from: Michael on August 10, 2018, 06:17:44 PM
It's like they're forgetting that computers exist, and I'm not a fan of it, but that's a whole different topic.
Definitely.  I hate it.  It's understandable that they don't want mobile users accidentally panning the map when they wanted to scroll the page, but why inconvenience desktop users because of it?  They could have easily implemented this on mobile but left the desktop behavior the same.

There's allegedly an API setting that will disable it, but I've never seen it used.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on August 11, 2018, 07:07:39 AM
Screw the "mobile first" approach - I've been a loyal user of desktop computers my whole life, and there's no reason to change when computers are still everywhere in offices, libraries, and schools, among other places; and when computers are so much easier to see on, use, and work with than clunky mobile devices anyway.  Besides, on a computer you get vastly more hard drive space (this one has 571 GB total, and even after years of using it it's still more than 80% free), and it's much easier to use a keyboard with actual keys than to try to manoeuvre your fat fingers around tiny little spaces on a screen.
Title: Re: Google Maps just fucking SUCKS now
Post by: jon daly on August 11, 2018, 09:35:54 AM
^Preach it!
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on August 11, 2018, 02:52:52 PM
I suppose the whole "mobile first" approach is due to more and more traffic being on mobile devices, which is probably soon to pass the traffic from computers for most major websites (Google, Facebook, YouTube, Twitter, Tumblr, etc.) if it hasn't already. Can't say I approve of it though.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 11, 2018, 02:54:27 PM
Quote from: freebrickproductions on August 11, 2018, 02:52:52 PM
I suppose the whole "mobile first" approach is due to more and more traffic being on mobile devices, which is probably soon to pass the traffic from computers for most major websites (Google, Facebook, YouTube, Twitter, Tumblr, etc.) if it hasn't already. Can't say I approve of it though.

It's already easy to make separate mobile and desktop versions of pages, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on August 11, 2018, 02:55:55 PM
Quote from: 1 on August 11, 2018, 02:54:27 PM
Quote from: freebrickproductions on August 11, 2018, 02:52:52 PM
I suppose the whole "mobile first" approach is due to more and more traffic being on mobile devices, which is probably soon to pass the traffic from computers for most major websites (Google, Facebook, YouTube, Twitter, Tumblr, etc.) if it hasn't already. Can't say I approve of it though.

It's already easy to make separate mobile and desktop versions of pages, though.
"B-but making a page that works on both devices is so much cooler though!!1!"
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 11, 2018, 03:47:29 PM
Mobile web browsers have very quickly caught up to desktop web browsers. It was really common back in the day for websites to have desktop and mobile versions, but that's not as necessary as it once was due to larger displays and similar browser technology. Plus, the code behind websites is being written for both uses in mind, unlike ten years ago when desktop use was the only thing considered. The one thing holding mobile browsers back was Flash, and that's nearly dead (and will be by 2020). The Maps API being discussed here is an example of an API that was developed for both environments. It's not "great" in either environment, but anything else might severely compromise one environment, while benefiting the other.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 11, 2018, 09:43:39 PM
It's possible to make designs optimal for both versions without making something completely separate, though.  Take my website, for example.  I don't have a completely separate mobile site, but I do have code that detects mobile devices and downloads a separate stylesheet for them that changes things like text and photo size to make the mobile experience more optimal.  Couldn't Google do something similar with the API?  Granted, my site is actually XHTML 1.1 rather than HTML 5, but I'm sure there's something that could make it work.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 12, 2018, 12:08:45 AM
Quote from: vdeane on August 11, 2018, 09:43:39 PM
It's possible to make designs optimal for both versions without making something completely separate, though.  Take my website, for example.  I don't have a completely separate mobile site, but I do have code that detects mobile devices and downloads a separate stylesheet for them that changes things like text and photo size to make the mobile experience more optimal.  Couldn't Google do something similar with the API?  Granted, my site is actually XHTML 1.1 rather than HTML 5, but I'm sure there's something that could make it work.

Certainly it's possible. But I'm sure if you asked Google, they would be more interested in moving towards a single stylesheet that works for all devices (with the only real differences at this point being screen size and input method). I am personally annoyed by websites that optimize for my mobile browser, since my screen and processing power is optimal for browsing normal websites.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on August 13, 2018, 11:04:18 AM
Quote from: silverback1065 on August 02, 2018, 07:31:58 AM
it doesn't suck anymore, this topic is unneeded
Nah, there are still too many errors. I just told them about their exaggerated length of the US 15/501 overlap, and though I only mentioned it in Santee, SC, I did point out that the error covers the whole highway. 


Quote from: fillup420 on May 20, 2018, 09:09:56 AM
It seems someone has changed the entirety of US 15 to be labeled as "US Hwy 15/501" . In central NC, that is correct. But in Pennsylvania, it is not. It seems that edit took out all the 15 shields with it too.
They could always replace the label with "US Hwy 15/401" from Society Hill, SC to Laurinburg, NC, and "US Hwy 15/301" from Exit 97 on I-95 to Summerton. Now that I think about it, I should've told them the exact details of where the 301, 401 and 501 overlaps begin and end.


Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 13, 2018, 01:04:40 PM
Quote from: D-Dey65 on August 13, 2018, 11:04:18 AM
Quote from: silverback1065 on August 02, 2018, 07:31:58 AM
it doesn't suck anymore, this topic is unneeded
Nah, there are still too many errors. I just told them about their exaggerated length of the US 15/501 overlap, and though I only mentioned it in Santee, SC, I did point out that the error covers the whole highway. 

Those issues are unrelated to the topic of this thread. This thread is about issues with Google Maps' interface and usability, not route accuracy. Google Maps had these same route "inaccuracy" issues before it was redesigned a few years ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: hbelkins on August 13, 2018, 01:28:20 PM
Quote from: jakeroot on August 13, 2018, 01:04:40 PM
Quote from: D-Dey65 on August 13, 2018, 11:04:18 AM
Quote from: silverback1065 on August 02, 2018, 07:31:58 AM
it doesn't suck anymore, this topic is unneeded
Nah, there are still too many errors. I just told them about their exaggerated length of the US 15/501 overlap, and though I only mentioned it in Santee, SC, I did point out that the error covers the whole highway. 

Those issues are unrelated to the topic of this thread. This thread is about issues with Google Maps' interface and usability, not route accuracy. Google Maps had these same route "inaccuracy" issues before it was redesigned a few years ago.

To me, usability is directly related to accuracy.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 13, 2018, 04:27:15 PM
Quote from: hbelkins on August 13, 2018, 01:28:20 PM
Quote from: jakeroot on August 13, 2018, 01:04:40 PM
Quote from: D-Dey65 on August 13, 2018, 11:04:18 AM
Quote from: silverback1065 on August 02, 2018, 07:31:58 AM
it doesn't suck anymore, this topic is unneeded
Nah, there are still too many errors. I just told them about their exaggerated length of the US 15/501 overlap, and though I only mentioned it in Santee, SC, I did point out that the error covers the whole highway. 

Those issues are unrelated to the topic of this thread. This thread is about issues with Google Maps' interface and usability, not route accuracy. Google Maps had these same route "inaccuracy" issues before it was redesigned a few years ago.

To me, usability is directly related to accuracy.

That's fine, but for the purposes of this thread, they are two distinct things. You can't locate map inaccuracies if you can't use Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on August 13, 2018, 05:31:25 PM
Quote from: vdeane on August 10, 2018, 09:24:24 PM
Quote from: Michael on August 10, 2018, 06:17:44 PM
It's like they're forgetting that computers exist, and I'm not a fan of it, but that's a whole different topic.
Definitely.  I hate it.  It's understandable that they don't want mobile users accidentally panning the map when they wanted to scroll the page, but why inconvenience desktop users because of it?  They could have easily implemented this on mobile but left the desktop behavior the same.

There's allegedly an API setting that will disable it, but I've never seen it used.

T-Mobile's MVNO map (https://maps.t-mobile.com/pcc.html?map=mvno-roamd-34l) allows you to zoom with the wheel without CTRL, but their postpaid map (https://www.t-mobile.com/coverage/coverage-map) requires you to use CTRL. They both are Google Maps based, so clearly the setting exists.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 13, 2018, 05:44:51 PM
Quote from: doorknob60 on August 13, 2018, 05:31:25 PM
Quote from: vdeane on August 10, 2018, 09:24:24 PM
Quote from: Michael on August 10, 2018, 06:17:44 PM
It's like they're forgetting that computers exist, and I'm not a fan of it, but that's a whole different topic.
Definitely.  I hate it.  It's understandable that they don't want mobile users accidentally panning the map when they wanted to scroll the page, but why inconvenience desktop users because of it?  They could have easily implemented this on mobile but left the desktop behavior the same.

There's allegedly an API setting that will disable it, but I've never seen it used.

T-Mobile's MVNO map (https://maps.t-mobile.com/pcc.html?map=mvno-roamd-34l) allows you to zoom with the wheel without CTRL, but their postpaid map (https://www.t-mobile.com/coverage/coverage-map) requires you to use CTRL. They both are Google Maps based, so clearly the setting exists.

Both implementations on a mobile browser require users to use +/- buttons in the bottom right. Which is weird, since the pre-paid map should be coded correctly to allow pinch-to-zoom with touchscreen devices.

I don't mind using +/- buttons, but it's not as straight-forward as pinching. Plus, given the way Google Maps normally works on a phone, it's reasonable to think that website implementations would have similar controls. At least from a typical user's perspective. I'm sure if you showed the two above maps to people on the street, their first instinct would be to pinch to zoom, not use the buttons.

FWIW, I don't mind holding control to zoom.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on August 13, 2018, 10:35:46 PM
I just was looking at the old ClassyGMap, and the new API and color style has made it there sometime within the past 24 hours.  It's an old link to before the KMLMap rebranding, and I assume that it isn't updated anymore, so the change is probably on Google's end.  I can't use the scroll wheel to zoom with or without [CTRL] (or in my case, it was [ALT]), and the buttons are larger than they used to be and are missing labels.  The map/satellite buttons are labeled, but they're large too.  After zooming in enough in an area with 45 degree imagery, the tilt and rotate buttons are labeled, but they're large like all the other buttons.  It also appears that I can only have 8 points in a route (10 including the endpoints).  I used to be able to have 11 points (yes, one more than the limit of 10 for some reason) in addition to the two endpoints.

Lastly, I can drag Pegman to the map, but Street View won't open.  I tried several different useragents, but none of them worked.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 13, 2018, 10:47:36 PM
Google Maps still sucks due to no county lines, a woefully small number of destinations/via points and no visual indication of toll roads versus free roads.

I miss the old Rand McNally atlases where they would show you free and tolled portions of highways (Garden State's multicoloring comes to mind).
Title: Re: Google Maps just fucking SUCKS now
Post by: skluth on August 13, 2018, 11:00:01 PM
Quote from: MNHighwayMan on August 09, 2018, 04:02:21 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PM
Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.
Well, he can't use Edge because he only has Windows 7. Agreed that IE is not optimal for GMaps browsing, although it appears to be superior to Firefox for this purpose.

Besides that, I guess I just don't understand what the problem is. Of course it's going to look different if you're viewing the route in the Mercator projection vs a globe.

Google Maps does not use Mercator. It uses something called Web Mercator which doesn't exaggerate as much near the poles. This was a serious problem where I used to work (I recently retired from NGA.) as many new employees didn't know there was a difference and would reproject incorrectly.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 14, 2018, 02:21:40 AM
Quote from: skluth on August 13, 2018, 11:00:01 PM
Quote from: MNHighwayMan on August 09, 2018, 04:02:21 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PM
Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.
Well, he can't use Edge because he only has Windows 7. Agreed that IE is not optimal for GMaps browsing, although it appears to be superior to Firefox for this purpose.

Besides that, I guess I just don't understand what the problem is. Of course it's going to look different if you're viewing the route in the Mercator projection vs a globe.

Google Maps does not use Mercator. It uses something called Web Mercator which doesn't exaggerate as much near the poles. This was a serious problem where I used to work (I recently retired from NGA.) as many new employees didn't know there was a difference and would reproject incorrectly.

Well, you caught me. Although, on the basic level, our main concern here is flat vs spherical. Whether the flat map is Mercator or Web Mercator isn't the point; it's still a flat projection, totally different from the spherical projection.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on August 14, 2018, 12:34:27 PM
Well, it turns out that my old ClassyGMap link is working correctly again.  I'm afraid that the glitches I had yesterday will someday become permanent.  I looked on the GitHub page for any bug reports, and I didn't find anything, but I did find this workaround (https://github.com/barryhunter/classygmaps/issues/126) for Street View, which worked for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on August 14, 2018, 05:25:50 PM
Quote from: Rothman on August 13, 2018, 10:47:36 PM
Google Maps still sucks due to no county lines, a woefully small number of destinations/via points and no visual indication of toll roads versus free roads.

I miss the old Rand McNally atlases where they would show you free and tolled portions of highways (Garden State's multicoloring comes to mind).
I don't know if/how many times this has been mentioned, but you can't even see state lines at low zoom levels either, so as a general rule I'm seriously starting to prefer OpenStreetMap by a long shot.  (I'm a member on there too, having corrected quite a few, generally relatively minor, errors in my local area; my profile, however, identifies me as being from the Northern Territory of Australia.)

Although now that I'm looking at OSM, where the heck did Lake Superior go?
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on August 14, 2018, 05:49:57 PM
Quote from: 20160805 on August 14, 2018, 05:25:50 PM
Quote from: Rothman on August 13, 2018, 10:47:36 PM
Google Maps still sucks due to no county lines, a woefully small number of destinations/via points and no visual indication of toll roads versus free roads.

I miss the old Rand McNally atlases where they would show you free and tolled portions of highways (Garden State's multicoloring comes to mind).
I don't know if/how many times this has been mentioned, but you can't even see state lines at low zoom levels either, so as a general rule I'm seriously starting to prefer OpenStreetMap by a long shot.  (I'm a member on there too, having corrected quite a few, generally relatively minor, errors in my local area; my profile, however, identifies me as being from the Northern Territory of Australia.)

Although now that I'm looking at OSM, where the heck did Lake Superior go?

Lake Huron's gone too (except at zoom level 6, where the southern half of it shows up).
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on August 14, 2018, 07:31:59 PM
Quote from: 20160805 on August 14, 2018, 05:25:50 PM
I don't know if/how many times this has been mentioned, but you can't even see state lines at low zoom levels either

Can't reproduce that one. I see the state lines in all their glory at every zoom level from 1.82 (as far out as I can go) to 21 (all the way in).
Title: Re: Google Maps just fucking SUCKS now
Post by: skluth on August 14, 2018, 09:22:18 PM
Quote from: jakeroot on August 14, 2018, 02:21:40 AM
Quote from: skluth on August 13, 2018, 11:00:01 PM
Quote from: MNHighwayMan on August 09, 2018, 04:02:21 PM
Quote from: jakeroot on August 09, 2018, 03:48:52 PM
Quote from: MNHighwayMan on August 09, 2018, 03:46:10 PM
Your problem is using Internet Explorer.
Well, he can't use Edge because he only has Windows 7. Agreed that IE is not optimal for GMaps browsing, although it appears to be superior to Firefox for this purpose.

Besides that, I guess I just don't understand what the problem is. Of course it's going to look different if you're viewing the route in the Mercator projection vs a globe.

Google Maps does not use Mercator. It uses something called Web Mercator which doesn't exaggerate as much near the poles. This was a serious problem where I used to work (I recently retired from NGA.) as many new employees didn't know there was a difference and would reproject incorrectly.

Well, you caught me. Although, on the basic level, our main concern here is flat vs spherical. Whether the flat map is Mercator or Web Mercator isn't the point; it's still a flat projection, totally different from the spherical projection.

Sorry. Pet peeve from when I used to work standards. You'd be surprised how many college grads using GIS don't know the difference. It's worth pointing out the difference if I can save even one future GIS user from making this mistake when reprojecting.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 14, 2018, 10:16:19 PM
Meh.  Mercator is a horrible 2D projection.  There are better ones out there with less distortion.
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on August 14, 2018, 10:46:39 PM
Quote from: US 89 on August 14, 2018, 05:49:57 PM
Quote from: 20160805 on August 14, 2018, 05:25:50 PM
Quote from: Rothman on August 13, 2018, 10:47:36 PM
Google Maps still sucks due to no county lines, a woefully small number of destinations/via points and no visual indication of toll roads versus free roads.

I miss the old Rand McNally atlases where they would show you free and tolled portions of highways (Garden State's multicoloring comes to mind).
I don't know if/how many times this has been mentioned, but you can't even see state lines at low zoom levels either, so as a general rule I'm seriously starting to prefer OpenStreetMap by a long shot.  (I'm a member on there too, having corrected quite a few, generally relatively minor, errors in my local area; my profile, however, identifies me as being from the Northern Territory of Australia.)

Although now that I'm looking at OSM, where the heck did Lake Superior go?

Lake Huron's gone too (except at zoom level 6, where the southern half of it shows up).

Looks like somebody broke the relation.  I'll take a look and see if it's an easy fix.

EDIT:  Yeah, seems somebody broke it, and the render then didn't render it.  Then somebody else has already fix it, but the tiles just haven't been rerendered again.  So, it might take awhile for it to show up once again.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 15, 2018, 12:54:12 PM
Quote from: Rothman on August 14, 2018, 10:16:19 PM
Meh.  Mercator is a horrible 2D projection.  There are better ones out there with less distortion.
Less distortion of area maybe, but not necessarily in shape.  Google Maps would need to use a rectangular one for flat views in order to get it to wrap around because of how our screens are (or at the very least limit how far we can zoom out in ways they don't right now), and the Peters projection in particular has a LOT of shape distortion.  It makes South America look anorexic!

I think most of the complaints concerning Mercator boil down to "it makes Europe, Russia, and the US/Canada look big, so therefore it's racist".  Never mind that it was designed to facilitate marine navigation, not to justify imperialism, despite what people seem to think these days.

I personally favor Robinson, but I'm not sure how one would fit that into an application like Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 15, 2018, 01:49:08 PM
I don't think it has to be rectangular.  Just have gores.

I also don't think Mercator criticism is as restricted as you make it out to be.  Greenland looks ridiculous and has led a lot of people to believe it is much larger than it is.  Africa looks a lot smaller than it is.  I know the accusations about racism and whatnot, but I think the simple misrepresentation of size argument against Mercator wins hands-down.  It's distortion probably played a part in bad policy decisions, too (Vietnam is a tiny country...).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 15, 2018, 01:55:54 PM
Are there people who actually try to do size comparisons with Mercator?  I suppose it could be hard for me to see since I'm young enough that just about every world map I ever saw growing up was Robinson, so Mercator was "that weird projection that you sometimes see on really old maps" (and, later, online maps like Google).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 15, 2018, 01:57:30 PM
Heh.  Mercator was still used in schools when I attended grade school.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 15, 2018, 02:13:44 PM
Quote from: Rothman on August 15, 2018, 01:49:08 PMIts distortion probably played a part in bad policy decisions, too (Vietnam is a tiny country...).

How?  Vietnam is very close to the equator, so is among the countries least distorted by a Mercator projection.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 15, 2018, 02:16:18 PM
Quote from: J N Winkler on August 15, 2018, 02:13:44 PM
Quote from: Rothman on August 15, 2018, 01:49:08 PMIts distortion probably played a part in bad policy decisions, too (Vietnam is a tiny country...).

How?  Vietnam is very close to the equator, so is among the countries least distorted by a Mercator projection.

It's distorted in the other direction from what we're used to (which is 25°-50°).
Title: Re: Google Maps just fucking SUCKS now
Post by: jon daly on August 15, 2018, 03:19:08 PM
Quote from: doorknob60 on August 06, 2018, 02:27:36 PM
While the logic in moving Google Maps to a globe is sound and makes sense, I don't like it. Good news is, it's optional. Click the hamburger menu on the top left, then click Globe, and it will toggle it off.

Thanks. I just noticed that I was set to Globe and it gave me vertigo. I toggled it off.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 15, 2018, 08:25:45 PM
Quote from: Rothman on August 15, 2018, 01:49:08 PM
I also don't think Mercator criticism is as restricted as you make it out to be.  Greenland looks ridiculous and has led a lot of people to believe it is much larger than it is.  Africa looks a lot smaller than it is.  I know the accusations about racism and whatnot, but I think the simple misrepresentation of size argument against Mercator wins hands-down.

Well, and of course, that's only a problem when you select the Mercator projection for the purpose that is the exact opposite of what it does well, such as correctly displaying sizes at high latitudes. :-)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 15, 2018, 08:46:02 PM
Quote from: empirestate on August 15, 2018, 08:25:45 PM
Quote from: Rothman on August 15, 2018, 01:49:08 PM
I also don't think Mercator criticism is as restricted as you make it out to be.  Greenland looks ridiculous and has led a lot of people to believe it is much larger than it is.  Africa looks a lot smaller than it is.  I know the accusations about racism and whatnot, but I think the simple misrepresentation of size argument against Mercator wins hands-down.

Well, and of course, that's only a problem when you select the Mercator projection for the purpose that is the exact opposite of what it does well, such as correctly displaying sizes at high latitudes. :-)

Do tell more. I don't follow.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 16, 2018, 09:47:08 AM
Quote from: jakeroot on August 15, 2018, 08:46:02 PM
Quote from: empirestate on August 15, 2018, 08:25:45 PM
Quote from: Rothman on August 15, 2018, 01:49:08 PM
I also don't think Mercator criticism is as restricted as you make it out to be.  Greenland looks ridiculous and has led a lot of people to believe it is much larger than it is.  Africa looks a lot smaller than it is.  I know the accusations about racism and whatnot, but I think the simple misrepresentation of size argument against Mercator wins hands-down.

Well, and of course, that's only a problem when you select the Mercator projection for the purpose that is the exact opposite of what it does well, such as correctly displaying sizes at high latitudes. :-)

Do tell more. I don't follow.
I am also not following.  If anything, high latitudes are awful on Mercator.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 16, 2018, 10:09:12 AM
Quote from: jakeroot on August 15, 2018, 08:46:02 PM
Quote from: empirestate on August 15, 2018, 08:25:45 PM
Quote from: Rothman on August 15, 2018, 01:49:08 PM
I also don't think Mercator criticism is as restricted as you make it out to be.  Greenland looks ridiculous and has led a lot of people to believe it is much larger than it is.  Africa looks a lot smaller than it is.  I know the accusations about racism and whatnot, but I think the simple misrepresentation of size argument against Mercator wins hands-down.

Well, and of course, that's only a problem when you select the Mercator projection for the purpose that is the exact opposite of what it does well, such as correctly displaying sizes at high latitudes. :-)

Do tell more. I don't follow.

Well, choosing a map projection is all about the purpose of the map you're making, because all flat maps introduce distortion in one or more of several aspects (size, shape, area, etc.) while preserving others. The Mercator projection is useful because it preserves direction: any straight line on the map represents a line of constant bearing on the surface, which is why it's used for navigation. (Nautical charts are usually made in this projection.)

However, there is also a tradition of using Mercator for general purpose reference maps of the world. This is not an application where preserving direction is as important as preserving relative areas and distances (and to a lesser extent, shapes)—all of which Mercator does not do, especially at high latitudes. Therefore, Mercator is a very inappropriate projection to select for that type of map, and that's the context from which all the criticism stems. On the other hand, nobody minds that nautical charts use Mercator, because it's very appropriate to that situation. (And note that not a lot of navigation happens near the poles, where Mercator is least useful; in fact, it literally cannot display the poles at all.)

In other words, the problem isn't with the Mercator projection itself; it's with mapmakers selecting that projection in applications for which it's fundamentally unsuitable.

Quote from: Rothman on August 16, 2018, 09:47:08 AM
I am also not following.  If anything, high latitudes are awful on Mercator.

I think I see the problem—my clause "such as correctly displaying sizes at high latitudes" was meant to modify the entire object, "purpose that is the exact opposite of what it does well", not just the subordinate phrase "what it does well". So:

QuoteWell, and of course, that's only a problem when you select the Mercator projection for a purpose, such as correctly displaying sizes at high latitudes, that is the exact opposite of what it does well.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on August 16, 2018, 10:52:03 AM
Quote from: Eth on August 14, 2018, 07:31:59 PM
Quote from: 20160805 on August 14, 2018, 05:25:50 PM
I don't know if/how many times this has been mentioned, but you can't even see state lines at low zoom levels either

Can't reproduce that one. I see the state lines in all their glory at every zoom level from 1.82 (as far out as I can go) to 21 (all the way in).
I can't see any mention of state lines below level 11; if it makes a difference, I'm using Chrome on a Windows 7 computer from 2011.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 16, 2018, 11:05:58 AM
Quote from: 20160805 on August 16, 2018, 10:52:03 AM
Quote from: Eth on August 14, 2018, 07:31:59 PM
Quote from: 20160805 on August 14, 2018, 05:25:50 PM
I don't know if/how many times this has been mentioned, but you can't even see state lines at low zoom levels either

Can't reproduce that one. I see the state lines in all their glory at every zoom level from 1.82 (as far out as I can go) to 21 (all the way in).
I can't see any mention of state lines below level 11; if it makes a difference, I'm using Chrome on a Windows 7 computer from 2011.

I can see them just fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on August 16, 2018, 06:42:26 PM
To cheer up with the semi-loss of ACME Mapper (who founded another source for maps and satellite views). I founded by luck this site called Satellites Pro. http://satellites.pro  who give us for now the option to use Google Maps, Esri, OpenStreetmap.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brian556 on September 01, 2018, 07:37:36 PM
Google Maps is slower than an 85-year old woman driving a Buick
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 02, 2018, 12:18:07 AM
Quote from: Brian556 on September 01, 2018, 07:37:36 PM
Google Maps is slower than an 85-year old woman driving a Buick

Depends on the computer.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 02, 2018, 07:27:20 AM
Google Maps API:
https://maps.googleapis.com/maps/... no longer works. It has to be http://maps.googleapis.com/maps/..., with http, not https.

Maybe an admin/mod could add this to the word filter, so that a lot of images are no longer broken? I already changed mine, but it didn't fix anyone who quoted me, and some other people have used the Google Maps API.
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on September 02, 2018, 08:04:58 AM
Done.  LMK if it works.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 02, 2018, 08:18:45 AM
It doesn't seem to work. Look at Reply #90 here: https://www.aaroads.com/forum/index.php?topic=1151.msg2285453#msg2285453
Title: Re: Google Maps just fucking SUCKS now
Post by: rickmastfan67 on September 02, 2018, 09:35:02 AM
Quote from: 1 on September 02, 2018, 08:18:45 AM
It doesn't seem to work. Look at Reply #90 here: https://www.aaroads.com/forum/index.php?topic=1151.msg2285453#msg2285453

Don't know what to do then. :/  Sorry.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 02, 2018, 09:52:18 AM
Never did like that API. Not interactive enough. May I suggest screenshots from here on? That's what I've always done.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brian556 on September 02, 2018, 10:01:50 AM
Quote from: jakeroot on September 02, 2018, 12:18:07 AM
Quote from: Brian556 on September 01, 2018, 07:37:36 PM
Google Maps is slower than an 85-year old woman driving a Buick

Depends on the computer.

3.6 GHz processor, 8G RAM. Motherboard has on-board graphics
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on September 29, 2018, 06:08:43 PM
A few days ago, the ClassyGMap link I use that still has ClassyGMap branding had the "for development purposes only" watermark.  I got the watermark once before when Acme Mapper still used Google Maps as a base, and it was just a DIV that I was able to add a filter for in Adblock Plus.  When I added the filter, I was surprised that the watermark wasn't added server-side, and wondered how long it would take for Google to start adding it.  It turns out that this week was when it happened.  I did notice something weird though: while loading the map, it didn't have a watermark for a split second.  After looking at Chrome's developer tools, I found that it turns out that there's a sort of key that tells it to load the watermarked tiles.  I was able to block the key, and it worked fine.  Here's the filter I used:


http://maps.googleapis.com/maps/api/js/QuotaService.RecordEvent?1shttp%3A%2F%2Fgokml.net%2Fmaps-azteca.php*


I assume that the address at the end could be changed to another address and it would work on that site too.  Now the question is if Google will figure this out and move everything server-side.
Title: Re: Google Maps just fucking SUCKS now
Post by: bzakharin on October 09, 2018, 07:45:24 PM
Has anyone noticed that any time there is street view from 2018 there is no history even when there used to be older data?
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on October 09, 2018, 08:15:35 PM
Quote from: bzakharin on October 09, 2018, 07:45:24 PM
Has anyone noticed that any time there is street view from 2018 there is no history even when there used to be older data?

It worked fine for me. I used streetview in Goldsboro, NC and I was able to use the history. I just wish the history feature was available on the Google Maps app.
Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on October 09, 2018, 10:57:33 PM
Kinda cool that the latest GSV shows me just ahead of them for 3 blocks going down one of the streets in my town.  They were driving in town back in June and it finally got posted.  :bigass:
Title: Re: Google Maps just fucking SUCKS now
Post by: bzakharin on October 09, 2018, 10:59:31 PM
Quote from: LM117 on October 09, 2018, 08:15:35 PM
Quote from: bzakharin on October 09, 2018, 07:45:24 PM
Has anyone noticed that any time there is street view from 2018 there is no history even when there used to be older data?

It worked fine for me. I used streetview in Goldsboro, NC and I was able to use the history. I just wish the history feature was available on the Google Maps app.
You are right, I found places where it sort of works for me (the number of items in the history changes depending on which one is selected), so it's not everywhere
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 10, 2018, 01:24:46 AM
Quote from: bzakharin on October 09, 2018, 10:59:31 PM
Quote from: LM117 on October 09, 2018, 08:15:35 PM
Quote from: bzakharin on October 09, 2018, 07:45:24 PM
Has anyone noticed that any time there is street view from 2018 there is no history even when there used to be older data?

It worked fine for me. I used streetview in Goldsboro, NC and I was able to use the history. I just wish the history feature was available on the Google Maps app.
You are right, I found places where it sort of works for me (the number of items in the history changes depending on which one is selected), so it's not everywhere

While I love historic street view, it's not without its flaws. Depending on the exact point you're "standing", you could have anywhere from one to eight (or more) options. Big issue in cities, where the cars drive around a lot.
Title: Re: Google Maps just fucking SUCKS now
Post by: seicer on October 10, 2018, 09:12:16 AM
I was going to report that I see past histories, but now it's been removed for a few areas I know have prior data. Might just be a bug.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 10, 2018, 12:45:23 PM
I've been seeing the prior data most of the time.  Only location I can think of where I didn't was on I-86/NY 17 WB near Chemung, which had the right lane closed when street view went through and may have interfered with the data points matching up.  I've also found at least one location where Google defaulted to an older year and I had to keep using the history menu to get the recent data (Brookdale Ave in Cornwall).  Speaking of Cornwall, I think it's interesting that they drove across the bridge onto the island, turned around at the former location of customs (too bad they didn't get imagery for the other streets on the island while they were doing this!) and then went through present-day customs, camera on.  This happened a lot in the first round of street view (the blurry era), but they usually try to avoid it now.  The area still looks like a construction site even though theoretically it was supposed to be done; I guess they don't see the need to tidy everything up.

This round of street view updates seems to be the least exciting in a while.  No new countries, no new areas they had previously missed, not even high-profile new highways like I-11 or FL 9B.  Seems like they stuck mostly to major roads they already had.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on October 12, 2018, 09:22:32 AM
Quote from: vdeane on October 10, 2018, 12:45:23 PM
This round of street view updates seems to be the least exciting in a while.  No new countries, no new areas they had previously missed, not even high-profile new highways like I-11 or FL 9B.  Seems like they stuck mostly to major roads they already had.

The June-July 2018 GSV does seem to have a slightly higher resolution and more vivid colors than even hi-res imagery from 2017, 2016. As I play Geoguessr, I can immediately tell which imagery is from this past summer and I bet I would be right if I cheated and hit the Google Maps hyperlink that appears in the game (which brings you to the spot you're viewing).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 12, 2018, 05:34:48 PM
Quote from: Mr. Matté on October 12, 2018, 09:22:32 AM
Quote from: vdeane on October 10, 2018, 12:45:23 PM
This round of street view updates seems to be the least exciting in a while.  No new countries, no new areas they had previously missed, not even high-profile new highways like I-11 or FL 9B.  Seems like they stuck mostly to major roads they already had.

The June-July 2018 GSV does seem to have a slightly higher resolution and more vivid colors than even hi-res imagery from 2017, 2016. As I play Geoguessr, I can immediately tell which imagery is from this past summer and I bet I would be right if I cheated and hit the Google Maps hyperlink that appears in the game (which brings you to the spot you're viewing).

I noticed the change in camera quality as well. Noticeably easier to read signs, and there's less in the way of clipping (or whatever it's called, when the images are put together, but they don't always overlap correctly). Evidently, Google found it harder to take proper 360 degree photos than they initially expected, as it's taken 11 years to get to this point. There was a giant boost in quality around 2008 to 2009, but quality has been relatively stagnant since then.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 12, 2018, 06:00:28 PM
I've seen a few flaws with the new imagery.  Specifically, they seem to have gotten the directions wrong on some.  There have been locations I've browsed, where the pegman moved at 90° to where I clicked, and one instance where the pegman moved backwards from where I clicked.  With that having happened in multiple locations, I'm none too thrilled.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 12, 2018, 06:29:13 PM
Quote from: kphoger on October 12, 2018, 06:00:28 PM
I've seen a few flaws with the new imagery.  Specifically, they seem to have gotten the directions wrong on some.  There have been locations I've browsed, where the pegman moved at 90° to where I clicked, and one instance where the pegman moved backwards from where I clicked.  With that having happened in multiple locations, I'm none too thrilled.

Have the images lined up with the direction the pegman was facing on the bottom-left map? (assuming you're browsing on a computer). I was browsing around Rodbourne Road, near the Bruce Street Bridges Roundabout in Swindon, England, and every time I clicked in what was clearly the correct direction on both the images and the map, it went backwards. I reloaded the page and "went around the block"; the error did not re-occur.

EDIT: actually it's still doing it. Check it out: https://goo.gl/uqyTho (images and pegman are pointing in opposite direction this time, so clearly the cock-up is the imagery)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 16, 2018, 01:33:03 AM
https://youtu.be/B3KmWuMWh6Y
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on October 17, 2018, 10:10:02 AM
For the first time ever, this weekend I saw the Google Street View car go by me.  I'll post pictures when/if they appear.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 17, 2018, 12:43:17 PM
Quote from: ErmineNotyours on October 17, 2018, 10:10:02 AM
For the first time ever, this weekend I saw the Google Street View car go by me.  I'll post pictures when/if they appear.

Be warned: it usually takes a couple months for the images to end up online.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on October 17, 2018, 04:46:32 PM
Quote from: jakeroot on October 17, 2018, 12:43:17 PM
Quote from: ErmineNotyours on October 17, 2018, 10:10:02 AM
For the first time ever, this weekend I saw the Google Street View car go by me.  I'll post pictures when/if they appear.

Be warned: it usually takes a couple months for the images to end up online.

If they appear at all. A Streetview car went past my house in 2013 and it still doesn't show. The only Streetview image of my house is from December 2007, long before I moved here.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 17, 2018, 06:36:58 PM
Quote from: LM117 on October 17, 2018, 04:46:32 PM
Quote from: jakeroot on October 17, 2018, 12:43:17 PM
Quote from: ErmineNotyours on October 17, 2018, 10:10:02 AM
For the first time ever, this weekend I saw the Google Street View car go by me.  I'll post pictures when/if they appear.

Be warned: it usually takes a couple months for the images to end up online.

If they appear at all. A Streetview car went past my house in 2013 and it still doesn't show. The only Streetview image of my house is from December 2007, long before I moved here.

It must not have been taking any images. That does happen from time to time.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on October 17, 2018, 11:08:58 PM
Quote from: jakeroot on October 17, 2018, 12:43:17 PM
Quote from: ErmineNotyours on October 17, 2018, 10:10:02 AM
For the first time ever, this weekend I saw the Google Street View car go by me.  I'll post pictures when/if they appear.

Be warned: it usually takes a couple months for the images to end up online.

The current imagery for that location is July 2018, which is fairly recent.  The car I saw was on the opposite side of the street from the current view.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on October 23, 2018, 08:06:57 PM
Within the past day, my ClassyGMap workaround was finally "fixed" by Google.  Map tiles are served with the watermark embedded now.  Imagery is still served with the watermark as a DIV, but I'm guessing they just haven't "fixed" that yet.  On my older version of Chrome, the only things that work on Google Maps are panning and zooming with the scroll wheel.  There's no buttons for zooming or Street View, and I can't switch to satellite view.  Links to satellite view only show a blinking satellite view.

For a while, I have been able to set my useragent spoofer extension to spoof Firefox 31, which fixes these issues, but breaks scrolling, closing a search, and the minimap in Street View.  I haven't been able to use the minimap for the past two months or so anyway since a change from Google made the map and satellite buttons so big they covered the entire minimap.  The problem with spoofing Firefox 31 on google.com is that it messes up the formatting of search pages, and it's annoying to switch my useragent every time I want to look at a map.  Since it looks like I won't be able to use ClassyGMap any more, I decided to try putting "google.com/maps" in the domain field of my useragent spoofer.  That didn't work, so I tried "google.com/maps*" (note the asterisk at the end), and that worked.  I wasn't sure if using a full URL in the domain field would work, but thankfully it does!
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on October 27, 2018, 08:26:51 AM
Looks like the Google fix caught up with my go-to site for quick access to GM and GSV: http://mytopo.com/maps

Anyone have any recommendations as to another site that has the simple & quick GM interface and default lite mode on GSV?
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on October 27, 2018, 11:20:31 AM
Quote from: Mr. Matté on October 27, 2018, 08:26:51 AM
Looks like the Google fix caught up with my go-to site for quick access to GM and GSV: http://mytopo.com/maps

Anyone have any recommendations as to another site that has the simple & quick GM interface and default lite mode on GSV?

http://www.acme.com/mapper/
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 27, 2018, 04:54:37 PM
Quote from: Mr. Matté on October 27, 2018, 08:26:51 AM
Looks like the Google fix caught up with my go-to site for quick access to GM and GSV: http://mytopo.com/maps

Anyone have any recommendations as to another site that has the simple & quick GM interface and default lite mode on GSV?

I feel like a broken record.

Have you tried regular Google Maps recently? They've changed it a ton and, while it's not perfect (no mapping site is), it's improved dramatically from when the current generation came out.

Quote from: ErmineNotyours on October 27, 2018, 11:20:31 AM
http://www.acme.com/mapper/

I might be alone, but the lack of Street View makes that site a no-go. Also, that's a really clunky interface.
Title: Re: Google Maps just fucking SUCKS now
Post by: chays on November 01, 2018, 09:34:26 AM
I don't see how this happens.  Total lack of situational awareness, and surely the road was barricaded?  I just hope the lead-up to this makes it into GSV.

https://www.autoevolution.com/news/google-street-view-car-drives-into-flooded-texas-road-becomes-submerged-129826.html

(https://s1.cdn.autoevolution.com/images/news/google-street-view-car-drives-into-flooded-texas-road-becomes-submerged-129826_1.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on November 01, 2018, 09:59:40 AM
Quote from: chays on November 01, 2018, 09:34:26 AM
I don't see how this happens.  Total lack of situational awareness, and surely the road was barricaded?  I just hope the lead-up to this makes it into GSV.

https://www.autoevolution.com/news/google-street-view-car-drives-into-flooded-texas-road-becomes-submerged-129826.html

(image)

https://www.youtube.com/watch?v=DOW_kPzY_JY (https://www.youtube.com/watch?v=DOW_kPzY_JY)
Title: Re: Google Maps just fucking SUCKS now
Post by: seicer on November 01, 2018, 12:19:58 PM
Doing some spot checks of Apple Maps, and I was surprised to see newer imagery in upstate New York, West Virginia and parts of Kentucky than Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 01, 2018, 12:42:44 PM
Quote from: chays on November 01, 2018, 09:34:26 AM
I don't see how this happens.  Total lack of situational awareness, and surely the road was barricaded?  I just hope the lead-up to this makes it into GSV.
I'm guessing it won't - the camera is down in the picture, so I doubt anything was even being recorded (and it would be sideways if it was).
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on November 24, 2018, 11:19:42 AM
Just found a major error in Google Maps; The Park and Ride on the Long Island Expressway at Exit 49 was placed way too far north onto a house on John Daves Lane in northwestern Huntington, New York.


For the record, I corrected their error. But it should've been obvious from the beginning.




Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on November 24, 2018, 05:43:19 PM
Quote from: D-Dey65 on November 24, 2018, 11:19:42 AM
Just found a major error in Google Maps; The Park and Ride on the Long Island Expressway at Exit 49 was placed way too far north onto a house on John Daves Lane in northwestern Huntington, New York.
Major error my arse.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on November 25, 2018, 05:10:11 PM
Quote from: NE2 on November 24, 2018, 05:43:19 PM
Major error my arse.
Sure. Try saying that when they claim that a rest area along an interstate highway 20+miles away is at your house.

:-P
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on November 25, 2018, 06:50:03 PM
Quote from: D-Dey65 on November 25, 2018, 05:10:11 PM
Quote from: NE2 on November 24, 2018, 05:43:19 PM
Major error my arse.
Sure. Try saying that when they claim that a rest area along an interstate highway 20+miles away is at your house.

:-P
Major error my arse.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on November 25, 2018, 08:26:49 PM
Oh, so you must want people to think your house is a rest area or park and ride.


Ooookay.

:-/   :-P  :biggrin:


Title: Re: Google Maps just fucking SUCKS now
Post by: wanderer2575 on November 25, 2018, 08:50:05 PM
Quote from: chays on November 01, 2018, 09:34:26 AM
I don't see how this happens.  Total lack of situational awareness, and surely the road was barricaded? 

Jeez, what kind of old-school driver are you?  You don't need situational awareness; you just go where your GPS tells you to go and rely on the collision warning systems to handle the rest.

/sarcasm
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on November 26, 2018, 04:28:54 AM
Quote from: chays on November 01, 2018, 09:34:26 AM
I don't see how this happens.  Total lack of situational awareness, and surely the road was barricaded?  I just hope the lead-up to this makes it into GSV.

https://www.autoevolution.com/news/google-street-view-car-drives-into-flooded-texas-road-becomes-submerged-129826.html

[pic of sunken Google car]

As long as they show hiking trails as drivable roads, I'm not surprised.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on November 28, 2018, 10:16:05 PM
Apparently the Dallas North Tollway and Sam Rayburn Tollway were recently overrun by ghost cars.

https://www.google.com/maps/@33.0908657,-96.8228992,61m/data=!3m1!1e3?hl=en (https://www.google.com/maps/@33.0908657,-96.8228992,61m/data=!3m1!1e3?hl=en)

In nearby parking lots, and a short distance away on each road, the cars are normal.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 28, 2018, 10:27:32 PM
Quote from: wxfree on November 28, 2018, 10:16:05 PM
Apparently the Dallas North Tollway and Sam Rayburn Tollway were recently overrun by ghost cars.

https://www.google.com/maps/@33.0908657,-96.8228992,61m/data=!3m1!1e3?hl=en (https://www.google.com/maps/@33.0908657,-96.8228992,61m/data=!3m1!1e3?hl=en)

In nearby parking lots, and a short distance away on each road, the cars are normal.

That's an effect of the 3D imagery present in Google Maps' Globe mode. Moving vehicles appear as slightly-transparent objects, whereas parked cars appear normal.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on December 05, 2018, 07:00:48 PM
Quote from: jakeroot on November 28, 2018, 10:27:32 PM
Quote from: wxfree on November 28, 2018, 10:16:05 PM
Apparently the Dallas North Tollway and Sam Rayburn Tollway were recently overrun by ghost cars.

https://www.google.com/maps/@33.0908657,-96.8228992,61m/data=!3m1!1e3?hl=en (https://www.google.com/maps/@33.0908657,-96.8228992,61m/data=!3m1!1e3?hl=en)

In nearby parking lots, and a short distance away on each road, the cars are normal.

That's an effect of the 3D imagery present in Google Maps' Globe mode. Moving vehicles appear as slightly-transparent objects, whereas parked cars appear normal.
There was a discussion on this on the WikiProject:New York City Public Transit talk page. Somebody showed a GSV link to a woman who's head was blended into the sidewalk near a Downtown Manhattan subway station entrance.



Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 06, 2018, 10:49:46 AM
Quote from: D-Dey65 on December 05, 2018, 07:00:48 PM
a GSV link to a woman who's head was appeared to be blended into the sidewalk near a Downtown Manhattan subway station entrance.

One can only hope that was an appropriate correction.   :wow:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 06, 2018, 05:12:04 PM
Quote from: D-Dey65 on December 05, 2018, 07:00:48 PM
There was a discussion on this on the WikiProject:New York City Public Transit talk page. Somebody showed a GSV link to a woman who's head was blended into the sidewalk near a Downtown Manhattan subway station entrance.

Well, and GSV is an entirely different monster. Until the new cameras started coming around, which can capture wider-angle photos with less stitching, poor stitching was a serious problem on older photos. Trying to get a GSV photo of a sign often took lots of clicking around to find an angle without stitching. The 3D (globe) satellite mode has less stitching but the "ghosting" effect is a common symptom of the production process.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: seicer on December 27, 2018, 07:07:59 PM
I noticed that around my hometown. A third-party company operates their own 360 vehicle but it's of inferior quality (think of Google in 2013). You can jump back on desktop Google Maps but not on the mobile version.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on December 27, 2018, 09:51:43 PM
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.
I don't quite get it, just zoom in a bunch.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 27, 2018, 10:43:06 PM
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.

In my experience, if I quickly grab the pegman, and then drop him somewhere roughly near the road, the chance of dropping him on a user-submitted spherical photo is quite a bit higher. But if I wait for the blue lines to show up, the chances drop to near-zero.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on December 27, 2018, 10:59:20 PM
Quote from: jakeroot on December 27, 2018, 10:43:06 PM
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.

In my experience, if I quickly grab the pegman, and then drop him somewhere roughly near the road, the chance of dropping him on a user-submitted spherical photo is quite a bit higher. But if I wait for the blue lines to show up, the chances drop to near-zero.
Does google want you to see user photos for some reason? Or is it just a quirk in the software?
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on January 05, 2019, 01:45:53 PM
Quote from: Roadgeekteen on December 27, 2018, 10:59:20 PM
Does google want you to see user photos for some reason? Or is it just a quirk in the software?
They certainly want users to add user photos. The trouble is, they don't always make it so you can add them. I took pictures along the Thomson Avenue Bridge in Long Island City that I was sure they were going to want, but at the same time, the QR-code thing kept interrupting my attempt to capture images there.

Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on January 09, 2019, 08:47:10 PM
I don't think I've ever hit a user-submitted Street View set by zooming into a road, but it's definitely the prioritized thing when clicking around on the minimap when already in Street View.

It wouldn't bother me so much if you could actually jump around them properly instead of one at a time. I would think they should just go right into the set of Street View captures for the road alongside the official ones, but they never seem to link together properly, instead appearing as a series of the individual 360 photo dots along the road, separate from the official Street View path.
Title: Re: Google Maps just fucking SUCKS now
Post by: NoGoodNamesAvailable on January 10, 2019, 04:45:59 PM
Does google maps just toss out data problem reports or what? I've reported several streets near me multiple times for incorrect one-way information that would be easy to verify on satellite imagery or street view and nothing ever gets changed. Who reviews this stuff?
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on January 10, 2019, 06:17:54 PM
Quote from: NoGoodNamesAvailable on January 10, 2019, 04:45:59 PM
Does google maps just toss out data problem reports or what? I've reported several streets near me multiple times for incorrect one-way information that would be easy to verify on satellite imagery or street view and nothing ever gets changed. Who reviews this stuff?
I had them rename one of the streets in Dover without issue but then they didn't fix the street that I actually live on when I reported that.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 11, 2019, 03:20:41 PM
I've had pretty good luck with them accepting my suggestions with roads, but they aren't having one of my point of interest suggestions. A Love's truck stop in Fife, WA has been demolished, and is being rebuilt. To not confuse anyone, I reported the truck stop as closed. But Google continues to show it as open. I'm not sure what their policy is on "temporarily closed" POI's, but it continues to be shown as operating on Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on January 18, 2019, 01:25:14 PM
Sometimes my reports get accepted, other times they get ignored and I get no indication of any decision. Most recently, they drew the Sellersville Bypass on PA 309 as a freeway after years of it not being shown as such.

What's really annoying now is that it seems to no longer be possible to select several segments. They always had a weird arbitrary cap on the number of segments you could select (which is annoying in denser places since they break up the roads into many segments), but now it's the entire road or just one segment.
Title: Re: Google Maps just fucking SUCKS now
Post by: DandyDan on January 23, 2019, 03:54:10 PM
So how is Google Maps can accurately change over MN 110 to MN 62, but they can't change over the oodles of old Iowa highways which are now county roads?
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on January 23, 2019, 04:20:54 PM
Quote from: DandyDan on January 23, 2019, 03:54:10 PM
So how is Google Maps can accurately change over MN 110 to MN 62, but they can't change over the oodles of old Iowa highways which are now county roads?

One's a much higher profile change? I dunno, but I kind of like being able to see the old Iowa highways still labeled. Helps me see where they were.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on January 24, 2019, 06:18:01 PM
Not a complaint, but it looks like Google has changed how they denote municipal boundaries.  They're starting to dim out the surrounding areas, anything closer than zoom level 16 will cause the dimming to fade, anything closer than 17 will cause the boundaries to fade.

(https://cdn.pbrd.co/images/HXZHX6L.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on January 24, 2019, 08:26:41 PM
Quote from: ipeters61 on January 24, 2019, 06:18:01 PM
Not a complaint, but it looks like Google has changed how they denote municipal boundaries.  They're starting to dim out the surrounding areas, anything closer than zoom level 16 will cause the dimming to fade, anything closer than 17 will cause the boundaries to fade.

(https://cdn.pbrd.co/images/HXZHX6L.png)

It works on mobile now, too, so definitely an improvement.

Meanwhile, they still haven't updated the northernmost segment of I-73 finished in NC (along US 220) after several months. They also find rather creative ways to mess up when implementing suggestions I make to mark major roads in yellow.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on January 25, 2019, 03:11:11 PM
Quote from: ipeters61 on January 24, 2019, 06:18:01 PM
Not a complaint, but it looks like Google has changed how they denote municipal boundaries.  They're starting to dim out the surrounding areas, anything closer than zoom level 16 will cause the dimming to fade, anything closer than 17 will cause the boundaries to fade.

(https://cdn.pbrd.co/images/HXZHX6L.png)

I like this change for the most part, except for cities with large land area, it starts dimming it way too soon so it's hard to see the exactly where the boundary is at times. For an extreme example try Chesapeake, VA. But any larger city will have the same problem. Portland was pretty bad, even Boise bothered me. But for small and medium sized cities, it works out much better (for example Meridian, ID is fine).
Title: Re: Google Maps just fucking SUCKS now
Post by: Ben114 on January 25, 2019, 04:50:12 PM
Quote from: ipeters61 on January 24, 2019, 06:18:01 PM
Not a complaint, but it looks like Google has changed how they denote municipal boundaries.  They're starting to dim out the surrounding areas, anything closer than zoom level 16 will cause the dimming to fade, anything closer than 17 will cause the boundaries to fade.

(https://cdn.pbrd.co/images/HXZHX6L.png)
I do know that they don't have boundaries for Machester-by-thd-Sea, Mass., but the town's ZIP code, 01944, does have boundaries.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on January 25, 2019, 10:16:00 PM
Quote from: Ben114 on January 25, 2019, 04:50:12 PM
I do know that they don't have boundaries for Machester-by-thd-Sea, Mass., but the town's ZIP code, 01944, does have boundaries.

1. Towns, as they exist in New England, probably don't register in Google Maps as proper incorporated places. Same goes for townships in the Midwest.
2. Zip codes often have little to do with actual incorporated boundaries.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on January 25, 2019, 10:26:48 PM
Quote from: MNHighwayMan on January 25, 2019, 10:16:00 PM

1. Towns, as they exist in New England, probably don't register in Google Maps as proper incorporated places. Same goes for townships in the Midwest.

Other towns work just fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 26, 2019, 10:06:20 PM
Whether a municipality works or not seems to be somewhat random.  Greece, NY is notable for actually having boundaries that are wrong, only covering a small portion of the town.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on January 26, 2019, 10:08:05 PM
Quote from: vdeane on January 26, 2019, 10:06:20 PM
Whether a municipality works or not seems to be somewhat random.  Greece, NY is notable for actually having boundaries that are wrong, only covering a small portion of the town.

This (https://en.wikipedia.org/wiki/Greece_(CDP),_New_York), maybe?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 26, 2019, 10:25:56 PM
Possibly.  That is roughly the center of where the border is.  The border Google has looks like what a Village of Greece would look like, if it had a central village like Pittsford, Penfield, and Webster do.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on January 26, 2019, 10:32:52 PM
I wouldn't be surprised if a lot of city boundaries are also out of date. I know Des Moines is, for example: the area on the south side, between Easter Lake and US-65 (https://www.google.com/maps/@41.534108,-93.5373631,14z) was annexed in 2009.
Title: Re: Google Maps just fucking SUCKS now
Post by: US71 on January 26, 2019, 10:51:42 PM
I was looking for some old bridges in Oklahoma today and Google maps showed one continuous road as opposed to 3 separate sections. They may have connected at one time, but not for many years .
Title: Re: Google Maps just fucking SUCKS now
Post by: polarscribe on January 26, 2019, 11:34:45 PM
Two entire ranger districts of the Wallowa-Whitman National Forest don't show up in green – the Whitman and La Grande districts. Compare https://www.google.com/maps/@44.5974292,-117.6645387,8.83z (https://www.google.com/maps/@44.5974292,-117.6645387,8.83z) to the same area in Bing, Apple Maps, MapQuest, literally anyone else. I've attempted to report the issue numerous times but gotten nowhere.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on January 27, 2019, 08:27:57 AM
Quote from: MNHighwayMan on January 26, 2019, 10:32:52 PM
I wouldn't be surprised if a lot of city boundaries are also out of date. I know Des Moines is, for example: the area on the south side, between Easter Lake and US-65 (https://www.google.com/maps/@41.534108,-93.5373631,14z) was annexed in 2009.

Likewise, it doesn't include Atlanta's annexation of Emory University (somewhat more excusable, as it was just last year). Then again, OSM doesn't have that one either.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on January 27, 2019, 12:32:25 PM
Hell, there are two county line changes in the past few years in Utah that Google doesn't have: a slight change in the Davis/Salt Lake border east of I-15, and a realignment of the Juab/Millard border off a ridgeline onto the nearest section line. OSM has the Davis/Salt Lake change, but not the Juab/Millard one.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on February 17, 2019, 01:29:20 AM
I have sent about 20 requests to Google Maps to change the route markings for CT 31 north of US 44, and it continues to be rejected.  It is marked correctly south of 44 with the ovular state shield.  But along and north of the concurrency, it is marked as a county route (small square shield).  Despite telling them to look at GSV and see that the shields are exactly the same on both stretches of the road, and the fact that CT does not have county routes, they refuse to make the change.  I've got them to correct the name of a street in my town, but they can't do anything for a numbered route? :angry:
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on February 17, 2019, 10:10:02 AM
Quote from: jp the roadgeek on February 17, 2019, 01:29:20 AM
I have sent about 20 requests to Google Maps to change the route markings for CT 31 north of US 44, and it continues to be rejected.  It is marked correctly south of 44 with the ovular state shield.  But along and north of the concurrency, it is marked as a county route (small square shield).  Despite telling them to look at GSV and see that the shields are exactly the same on both stretches of the road, and the fact that CT does not have county routes, they refuse to make the change.  I've got them to correct the name of a street in my town, but they can't do anything for a numbered route? :angry:
There's the same problem with portions of DE-15, I believe, where it's marked as a county road.
Title: Re: Google Maps just fucking SUCKS now
Post by: Flint1979 on February 17, 2019, 10:36:13 AM
Well looking at the maps and traveling in a certain area things sometimes don't add up the way you think. I was looking at Google Maps in Midland County, Michigan. Looking at Gordonville Road you would think that it went all the way through between Meridian Road and Coleman Road according to Google Maps that is. However between Castor Road and Almando Road the road doesn't exist. I don't really want to take a drive out there this time of the year since it's a dirt road and we have several inches of snow on the ground but I don't think Gordonville even goes east of Almando until it picks up again at Castor. That area is very wooded so it's hard to tell and I haven't been back that way in years.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 17, 2019, 10:50:10 AM
I actually just notified them of all sorts of imaginary roads near the new Katahdin Woods and Waters National Monument in Maine.  A five-year old probably got the vector set out there together, scribbling with crayon.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.

And as for the more-current discussion about municipal boundaries, they still don't have anything about Fox Crossing, WI (incorporated in 2016 from the former Menasha Twp) anywhere.

Edit: That would be kind of a grave dig, wouldn't it?
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on March 14, 2019, 09:27:46 PM
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.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on March 14, 2019, 10:49:40 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.
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.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on April 03, 2019, 10:51:29 AM
See the Garden State Parkway address:

https://goo.gl/maps/Vb2XuYPZnwo
Title: Re: Google Maps just fucking SUCKS now
Post by: 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
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on April 03, 2019, 11:55:21 AM
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.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 13, 2019, 06:41:38 PM
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?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 13, 2019, 06:44:51 PM
No problem here.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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?

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.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 13, 2019, 06:58:07 PM
I would like to comment, additionally, that I'm not seeing the issue along every road. Just, quite a few of them.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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?)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 13, 2019, 07:01:47 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?)

That happens to me for 2007—2009 imagery, which seems to be a different issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 13, 2019, 08:41:33 PM
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).
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: Ben114 on May 13, 2019, 09:10:24 PM
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)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 13, 2019, 10:03:38 PM
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.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on May 14, 2019, 08:09:36 AM
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. (https://www.google.com/maps/@39.1607331,-75.5301372,3a,75y,78.22h,83.38t/data=!3m6!1e1!3m4!1sZad0XmHA1Xx__XMu3yG5Uw!2e0!7i13312!8i6656)
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on May 14, 2019, 10:36:54 AM
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.
Title: Re: Google Maps just fucking SUCKS now
Post by: 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.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on May 14, 2019, 11:53:43 AM
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...
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on May 14, 2019, 11:49:22 PM
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.

The very similar thin grey lines for railroads and non-trail walking paths has led to some confusion and detouring in the past.  Open Street Map uses dashed lines as in the international map symbol for railroads, and makes it much easier to tell the difference.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on May 15, 2019, 05:07:33 PM
Quote from: 1 on May 13, 2019, 07:01:47 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?)

That happens to me for 2007—2009 imagery, which seems to be a different issue.
This has been around forever and is an issue I've gotten used to in my many years of GSV driving; I think it has to do with the resolution of the images themselves.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 15, 2019, 06:57:23 PM
Quote from: 20160805 on May 15, 2019, 05:07:33 PM
Quote from: 1 on May 13, 2019, 07:01:47 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?)

That happens to me for 2007—2009 imagery, which seems to be a different issue.
This has been around forever and is an issue I've gotten used to in my many years of GSV driving; I think it has to do with the resolution of the images themselves.

I've noticed it on and off for a long time too, but seems to be amplified with the "single track" issue mentioned on the last page.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on May 16, 2019, 06:14:23 PM
I noticed on Monday that there was no historic Street View on a street in Raleigh I know had older imagery.  I also noticed the track issue after reading it in this thread.  I looked in other places and noticed both issues in other locations as well.  I just checked a few minutes ago, and the issues appear to be mostly fixed.  I tried Jakeroot's link on the previous page, and it works now.  I think there may still be imagery missing, since I saw my car in my driveway in one of the Street View dates, but now I don't.  Some of the tracks might still be goofy, but I can't tell for sure since sometimes it's super picky about where you click.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 16, 2019, 11:19:52 PM
Quote from: Michael on May 16, 2019, 06:14:23 PM
I noticed on Monday that there was no historic Street View on a street in Raleigh I know had older imagery.  I also noticed the track issue after reading it in this thread.  I looked in other places and noticed both issues in other locations as well.  I just checked a few minutes ago, and the issues appear to be mostly fixed.  I tried Jakeroot's link on the previous page, and it works now.  I think there may still be imagery missing, since I saw my car in my driveway in one of the Street View dates, but now I don't.  Some of the tracks might still be goofy, but I can't tell for sure since sometimes it's super picky about where you click.

Thank you for the update. There are still some areas that appear to be unfixed, but that Downtown Seattle link I posted is also working for me as well.

What an annoying bug.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 17, 2019, 07:25:56 PM
I've been noticing the bug too.  It's REALLY annoying.  It's probably an over-correction for tying to reduce the incidence of accidentally clicking onto another road, especially where bridges/tunnels are involved.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)

https://goo.gl/maps/tH8jMj7E4HiaRaxF8
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on May 21, 2019, 03:33:41 PM
Quote from: Michael on May 16, 2019, 06:14:23 PM
I noticed on Monday that there was no historic Street View on a street in Raleigh I know had older imagery.  I also noticed the track issue after reading it in this thread.  I looked in other places and noticed both issues in other locations as well.  I just checked a few minutes ago, and the issues appear to be mostly fixed.  I tried Jakeroot's link on the previous page, and it works now.  I think there may still be imagery missing, since I saw my car in my driveway in one of the Street View dates, but now I don't.  Some of the tracks might still be goofy, but I can't tell for sure since sometimes it's super picky about where you click.

I've just finished doing this year's Giro d'Italia route, and that bug appeared halfway through. It was really annoying, I ended up clicking on the map through the areas where that bug was present.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 21, 2019, 04:11:27 PM
Quote from: webny99 on May 21, 2019, 03:17:17 PM

Quote from: 1 on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)

https://goo.gl/maps/tH8jMj7E4HiaRaxF8

That's really weird. It's like a Street View island - you can't go in either direction on the next (or previous) cross street.

Which is exactly what we had been talking about for 22 of the last 25 posts...
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 21, 2019, 04:41:45 PM
Quote from: 1 on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)

https://goo.gl/maps/tH8jMj7E4HiaRaxF8
Maybe it does exist, but it's a trap street?
https://www.youtube.com/watch?v=oHaG9zDZU2Y
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on May 21, 2019, 06:16:56 PM
Quote from: kphoger on May 21, 2019, 04:11:27 PM
Quote from: webny99 on May 21, 2019, 03:17:17 PM
Quote from: 1 on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)
https://goo.gl/maps/tH8jMj7E4HiaRaxF8
That's really weird. It's like a Street View island - you can't go in either direction on the next (or previous) cross street.
Which is exactly what we had been talking about for 22 of the last 25 posts...

No, this is different. While true that you can't jump to cross streets here either, this actual road does not exist.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 21, 2019, 06:44:13 PM
Quote from: webny99 on May 21, 2019, 06:16:56 PM
Quote from: kphoger on May 21, 2019, 04:11:27 PM
Quote from: webny99 on May 21, 2019, 03:17:17 PM
Quote from: 1 on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)
https://goo.gl/maps/tH8jMj7E4HiaRaxF8
That's really weird. It's like a Street View island - you can't go in either direction on the next (or previous) cross street.
Which is exactly what we had been talking about for 22 of the last 25 posts...

No, this is different. While true that you can't jump to cross streets here either, this actual road does not exist.

It exists: https://goo.gl/maps/pnQSyX7qk6YSvSZj8

I don't know why it's showing on the map in Street View mode as being somewhere off in the distance. Some code got screwed up somewhere, and it misaligned that old imagery, apparently.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on May 21, 2019, 08:32:41 PM
Quote from: webny99 on May 21, 2019, 06:16:56 PM
this actual road does not exist.

"Nah, the map can't be wrong! These images are fake!"
Title: Re: Google Maps just fucking SUCKS now
Post by: Verlanka on May 22, 2019, 08:41:47 AM
Quote from: webny99 on May 21, 2019, 03:17:17 PM
Quote from: 1 on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)

https://goo.gl/maps/tH8jMj7E4HiaRaxF8

That's really weird. It's like a Street View island - you can't go in either direction on the next (or previous) cross street.
It's like they want to trap you in that area for eternity.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on May 22, 2019, 08:57:41 AM
Quote from: jakeroot on May 21, 2019, 06:44:13 PM
Quote from: webny99 on May 21, 2019, 06:16:56 PM
Quote from: kphoger on May 21, 2019, 04:11:27 PM
Quote from: webny99 on May 21, 2019, 03:17:17 PM
Quote from: 1 on May 21, 2019, 02:18:10 PM
This street doesn't even exist in real life, so how does it exist on Street View? (It's a diagonal in a grid that doesn't have any.)
https://goo.gl/maps/tH8jMj7E4HiaRaxF8
That's really weird. It's like a Street View island - you can't go in either direction on the next (or previous) cross street.
Which is exactly what we had been talking about for 22 of the last 25 posts...
No, this is different. While true that you can't jump to cross streets here either, this actual road does not exist.
It exists: https://goo.gl/maps/pnQSyX7qk6YSvSZj8
I don't know why it's showing on the map in Street View mode as being somewhere off in the distance. Some code got screwed up somewhere, and it misaligned that old imagery, apparently.

Quote from: MNHighwayMan on May 21, 2019, 08:32:41 PM
Quote from: webny99 on May 21, 2019, 06:16:56 PM
this actual road does not exist.
"Nah, the map can't be wrong! These images are fake!"

Of course the road exists :pan:
It just doesn't exist in that area, meaning this is a map / alignment issue separate from what is discussed above.
Title: Re: Google Maps just fucking SUCKS now
Post by: Ben114 on May 22, 2019, 05:22:36 PM
Quote from: CNGL-Leudimin on May 21, 2019, 03:33:41 PM
Quote from: Michael on May 16, 2019, 06:14:23 PM
I noticed on Monday that there was no historic Street View on a street in Raleigh I know had older imagery.  I also noticed the track issue after reading it in this thread.  I looked in other places and noticed both issues in other locations as well.  I just checked a few minutes ago, and the issues appear to be mostly fixed.  I tried Jakeroot's link on the previous page, and it works now.  I think there may still be imagery missing, since I saw my car in my driveway in one of the Street View dates, but now I don't.  Some of the tracks might still be goofy, but I can't tell for sure since sometimes it's super picky about where you click.

I've just finished doing this year's Giro d'Italia route, and that bug appeared halfway through. It was really annoying, I ended up clicking on the map through the areas where that bug was present.
They recently deleted the Street View on the street I live on.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 22, 2019, 11:57:36 PM
I was reading the  thread (https://www.aaroads.com/forum/index.php?topic=11707.msg2418081#msg2418081) on the I-95 interchange with the Pennsylvania Turnpike, wherein Mr. Matté shows that new imagery of the interchange has appeared on Google Earth. At which point I went to Google Maps (because I misread) to check it out, and it turns out that I no longer have a Globe view option. I’m not sure why that is (perhaps they are thinking of removing the option?), but I thought it something worth mentioning.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi65.tinypic.com%2F1zno8ee.png&hash=caba42e8d2013d1250a223e2a51a1a46a1caca3f)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 24, 2019, 04:47:18 PM
Quote from: CtrlAltDel on May 22, 2019, 11:57:36 PM
I was reading the  thread (https://www.aaroads.com/forum/index.php?topic=11707.msg2418081#msg2418081) on the I-95 interchange with the Pennsylvania Turnpike, wherein Mr. Matté shows that new imagery of the interchange has appeared on Google Earth. At which point I went to Google Maps (because I misread) to check it out, and it turns out that I no longer have a Globe view option. I'm not sure why that is (perhaps they are thinking of removing the option?), but I thought it something worth mentioning.

(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fi65.tinypic.com%2F1zno8ee.png&hash=caba42e8d2013d1250a223e2a51a1a46a1caca3f)

It probably means that they don't think your computer can handle it.  They occasionally blacklist certain system configurations.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 24, 2019, 05:30:39 PM
Quote from: vdeane on May 24, 2019, 04:47:18 PM
It probably means that they don't think your computer can handle it.  They occasionally blacklist certain system configurations.

I did not know that. That's interesting, if weird, since my computer is brand new.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 24, 2019, 05:41:13 PM
Could also be OS/drivers or even whether hardware acceleration is enabled.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 24, 2019, 11:41:22 PM
Quote from: vdeane on May 24, 2019, 05:41:13 PM
Could also be OS/drivers or even whether hardware acceleration is enabled.

I did not know that either.

Title: Re: Google Maps just fucking SUCKS now
Post by: Bickendan on May 26, 2019, 06:55:48 AM
Apparently CA 15 finally got upgraded to I-15 :meh:

https://goo.gl/maps/TsyFxBb8Xm7wLYHu8
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 29, 2019, 12:10:00 AM
I've been noticing the bug too, especially on newer images.

The new cameras aren't as good either. Everytime they go under a bridge the imagery is just absolutely horrible. Example (March 2019) --> https://goo.gl/maps/zkhtvgQdKJDDo2KH7
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 29, 2019, 02:38:11 AM
Quote from: US 41 on May 29, 2019, 12:10:00 AM
The new cameras aren't as good either. Everytime they go under a bridge the imagery is just absolutely horrible. Example (March 2019) --> https://goo.gl/maps/zkhtvgQdKJDDo2KH7

Perhaps the quality is not so good under a bridge, but the overall capture quality has improved quite a bit. This was primarily to assist Google's AI in reading real-world text:

https://youtu.be/s0bZx4u1hxQ
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on May 29, 2019, 03:02:16 AM
Quote from: US 41 on May 29, 2019, 12:10:00 AM
The new cameras aren't as good either. Everytime they go under a bridge the imagery is just absolutely horrible. Example (March 2019) --> https://goo.gl/maps/zkhtvgQdKJDDo2KH7

I'm pretty sure the old ones were just as bad.
Title: Re: Google Maps just fucking SUCKS now
Post by: jamess on May 29, 2019, 04:27:43 PM
This Streetview says its from May 2019, but the image quality is very bad

https://goo.gl/maps/aC5ECoop9DmGhDPdA
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 29, 2019, 04:39:56 PM
Quote from: jamess on May 29, 2019, 04:27:43 PM
This Streetview says its from May 2019, but the image quality is very bad

https://goo.gl/maps/aC5ECoop9DmGhDPdA

"Very bad" ???  I can read the trim line of the cars parked on the street.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 29, 2019, 05:06:50 PM
Quote from: jamess on May 29, 2019, 04:27:43 PM
This Streetview says its from May 2019, but the image quality is very bad

https://goo.gl/maps/aC5ECoop9DmGhDPdA

That's from a series of photos taken by someone, and posted to Google Maps. They sometimes show up in Street View, usually as a blue circle. Quality is usually quite a bit worse.

In this instance, the uploader posted a huge series of photos, probably taken from a bike or something, which is why so many streets in that area have his photos.

Quote from: kphoger on May 29, 2019, 04:39:56 PM
"Very bad" ???  I can read the trim line of the cars parked on the street.

Does your link take you to a photo by "Mark Henninger"? The quality is pretty poor on my end.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 29, 2019, 05:53:37 PM
Quote from: jakeroot on May 29, 2019, 05:06:50 PM
Quote from: kphoger on May 29, 2019, 04:39:56 PM
"Very bad" ???  I can read the trim line of the cars parked on the street.

Does your link take you to a photo by "Mark Henninger"? The quality is pretty poor on my end.

I'm getting Mark Henninger, but the quality is pretty good.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 29, 2019, 06:17:13 PM
Quote from: 1 on May 29, 2019, 05:53:37 PM
Quote from: jakeroot on May 29, 2019, 05:06:50 PM
Quote from: kphoger on May 29, 2019, 04:39:56 PM
"Very bad" ???  I can read the trim line of the cars parked on the street.

Does your link take you to a photo by "Mark Henninger"? The quality is pretty poor on my end.

I'm getting Mark Henninger, but the quality is pretty good.

Two screenshots on my end. First is the Henninger photos, the second from Street View. I can make out the car makes and names only in the latter.

(https://i.imgur.com/nn9N5ae.png)
(https://i.imgur.com/SGlc6GE.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on May 29, 2019, 07:49:05 PM
Quote from: jamess on May 29, 2019, 04:27:43 PM
This Streetview says its from May 2019, but the image quality is very bad

But of course–because technological regression. :-)
Title: Re: Google Maps just fucking SUCKS now
Post by: Verlanka on May 30, 2019, 08:48:43 AM
Quote from: 1 on May 29, 2019, 05:53:37 PM
Quote from: jakeroot on May 29, 2019, 05:06:50 PM
Quote from: kphoger on May 29, 2019, 04:39:56 PM
"Very bad" ???  I can read the trim line of the cars parked on the street.

Does your link take you to a photo by "Mark Henninger"? The quality is pretty poor on my end.

I'm getting Mark Henninger, but the quality is pretty good.
Same here.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on May 30, 2019, 09:19:08 AM
Quote from: Verlanka on May 30, 2019, 08:48:43 AM
Quote from: 1 on May 29, 2019, 05:53:37 PM
I'm getting Mark Henninger, but the quality is pretty good.
Same here.

You call this pretty good? Can I have some of what you're smoking? This is blurry as shit and the colors are slightly off. (Edit: chromatic aberration is the term I meant and couldn't remember until now.)

(https://i.imgur.com/NshQQOi.png)

Going back to the topic, I wish Google would stop adding user submitted photos to places where GSV already exists. It's making a good product worse.
Title: Re: Google Maps just fucking SUCKS now
Post by: jamess on May 30, 2019, 11:01:06 AM
Quote from: jakeroot on May 29, 2019, 05:06:50 PM
Quote from: jamess on May 29, 2019, 04:27:43 PM
This Streetview says its from May 2019, but the image quality is very bad

https://goo.gl/maps/aC5ECoop9DmGhDPdA

That's from a series of photos taken by someone, and posted to Google Maps. They sometimes show up in Street View, usually as a blue circle. Quality is usually quite a bit worse.

In this instance, the uploader posted a huge series of photos, probably taken from a bike or something, which is why so many streets in that area have his photos.


I get the blue circle stuff, but this is the entire avenue. I ant find a way to switch to the official images or access the timeline to go to another date.

Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 30, 2019, 01:58:41 PM
Quote from: jakeroot on May 29, 2019, 06:17:13 PM
I can make out the car makes and names only in the latter.

Nissan Altima 2.5 SL

(https://i.imgur.com/KU0jsA5.jpg)

Quote from: MNHighwayMan on May 30, 2019, 09:19:08 AM
You call this pretty good? Can I have some of what you're smoking? This is blurry as shit and the colors are slightly off. (Edit: chromatic aberration is the term I meant and couldn't remember until now.)

I wouldn't say it's "pretty good", but I certainly wouldn't say it's "very bad" either.  Go ahead and smoke some 2008 GSV imagery and see if you feel any different.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 30, 2019, 08:57:25 PM
Quote from: kphoger on May 30, 2019, 01:58:41 PM
Quote from: jakeroot on May 29, 2019, 06:17:13 PM
I can make out the car makes and names only in the latter.

Nissan Altima 2.5 SL

https://i.imgur.com/KU0jsA5.jpg

But you can't actually read 2.5 SL. And Altima looks more like "ALTIVA".

Note the screenshots I posted up-thread. From equal distances, Henninger's photos are much worse quality.

Quote from: kphoger on May 30, 2019, 01:58:41 PM
I wouldn't say it's "pretty good", but I certainly wouldn't say it's "very bad" either.  Go ahead and smoke some 2008 GSV imagery and see if you feel any different.

What we're smoking is Mark's photos and 2018-era GSV, not that crappy 2008 imagery you get in some places (many places have HQ 2008 imagery). Comparing the former two...well, there's no comparison.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on June 03, 2019, 10:48:23 PM
Google Maps intentionally distorts the aerial photography imagery in areas of very steep slopes.  Since the Acme Mapper site no longer uses Google's service, you can see cliffs clearly there.  In some places the imagery is of lower quality, but it's still better because it isn't distorted.  Google's photography is distorted in every method of access I've tried.  I think it's related to the way they portray the shape of the ground in the imagery, but that feature should have an option to disable, and its application should be limited so it doesn't completely mess up the data.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hurricane Rex on June 08, 2019, 03:38:02 PM
Has anyone else noticed it's more tedious to get traffic data on google recently?

I skipped through the thread so I apologize if this was said.

SM-J737T

Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on June 08, 2019, 04:09:57 PM
I ran into the issue with third-party imagery substituting for StreetView when I was exploring the eastbound signing leading up to the Breezewood exit on the Pennsylvania Turnpike.  I was trying to find the messages for a three-sign sequence that advises trucks to stay on the Turnpike until Fort Littleton rather than to exit and take US 30 to McConnellsburg, and it was a pain because the advance function would go forward or backward only a few feet at a time.  The third of the three signs also appeared to be missing (unless it has been posted past Breezewood) and there was no option to go to past imagery, which should have existed in high resolution for such an important route.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheBox on June 09, 2019, 09:59:36 PM
The one and only thing that grinds my gears is the way editing roads is now?

First, they removed Google Map Maker (or however it was) so you had to remember the type of streets (physical divider, expressway, freeway, etc.) when changing/editing.

They replaced with the new one before the current one (which i'll get to later) went from infinity amounts of length for road to edit, to limited amounts of length for road to edit.

But the current one is the worse one, its so time consuming AF now, cause you now have to edit one part of length for road to edit and as a result you have to edit piece by piece.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on July 04, 2019, 06:33:09 AM
Is it my imagination or is Google using HDR in the new late-2018 and 2019 Streetview images?

For example, this image in front of the mall in my area: https://goo.gl/maps/JGT4ppcnoM9F1DqE9 (https://goo.gl/maps/JGT4ppcnoM9F1DqE9)
Title: Re: Google Maps just fucking SUCKS now
Post by: skluth on July 04, 2019, 12:20:30 PM
Quote from: wxfree on June 03, 2019, 10:48:23 PM
Google Maps intentionally distorts the aerial photography imagery in areas of very steep slopes.  Since the Acme Mapper site no longer uses Google's service, you can see cliffs clearly there.  In some places the imagery is of lower quality, but it's still better because it isn't distorted.  Google's photography is distorted in every method of access I've tried.  I think it's related to the way they portray the shape of the ground in the imagery, but that feature should have an option to disable, and its application should be limited so it doesn't completely mess up the data.

I doubt Google intentionally distorts imagery with steep slopes. Distortion is a byproduct of every orthorectified image. To orthorectify imagery, you need:

  • A satellite image that either comes with ephemeral data for georectification or (though less accurate) reference points you can georeference
  • A Digital Elevation Model or DEM of the area
You can also use imagery stereo pairs but this is much less common.

Digital Globe, IKONOS, and every other satellite image comes with ephemeral data which can be read by imagery software. (Erdas Imagine on my workstation) This data contains the info to georectify without processing. A high density DEM will be more geographically accurate but will stretch the image in areas of steep slopes. This is inevitable. A low density DEM will be less accurate but the distortion will be spread over a large area of the imagery. Or you can just dispose of the DEM entirely. This leaves the user with a less accurate georectified image but almost free of distortion.

By your description, I would guess Acme Mapper is only doing georectification and not orthorectification, i.e., not doing any adjustments for elevation. It may look better on steep slopes, but it's less accurate geographically. The geographical accuracy may be good enough for your purposes. This doesn't make it better, just more useful for your purposes. Google is doing what is better for the majority of people who want an image that more accurately follows changes of elevation.

FWIW, once imagery is orthoed, you can't put it back easily as you've discovered. It's likely impossible to exactly revert it to the original. Not much different than when you might add a filter to an image in Photoshop.
Title: Re: Google Maps just fucking SUCKS now
Post by: skluth on July 04, 2019, 12:53:31 PM
^^^^^^^^^^^^^^^^^^^^^^
A bit more on orthorectification.

Google gets most of its imagery from Digital Globe. DG sells some imagery already orthorectified, often done at the request of the customer. The orthoed imagery, when available, is often the default they sell when it's available as it's what most customers prefer. We had to make sure we ordered the original imagery to ortho for our purposes.

Orthorectification also distorts colors. Multispectral (color) imagery is not as dense as panchromatic (black and white) imagery. DG panchromatic is typically about 1 meter pixels though there is imagery down to 25 cm. Multispectral is typically 1/3 to 1/4 the resolution. It's not exact and as the panchromatic and multispectral images are orthoed, strong dark areas are typically muted. This is why very dark shingle roofs often look a blue-purple shade on satellite imagery.

Between the slope and color changes, it's essentially impossible to exactly restore the original imagery.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on July 10, 2019, 12:49:47 PM
It seems as of late that if I try to grab the the orange man to view a Streetview location, the blue lines that show where imagery is available is much spottier than usual. However, if I do go to one of the roads where said blue line doesn't appear, the SV imagery is available.

(https://i.imgur.com/Qe4PpaA.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 10, 2019, 12:51:50 PM
Street View doesn't seem to be working very smoothly, either.  I have been "stuck" in more areas recently despite available arrows or whatnot.
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on July 10, 2019, 12:58:18 PM
Sometimes, usually on 2009 or older street view, I'll be clicking along a road, and then there will be a gap in the SV. Usually small and not that annoying, but weird.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 10, 2019, 01:10:02 PM
That situation I understand.  Clicking on arrows or the line to move and GSV refuses to do so is what I do not understand.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 10, 2019, 02:50:28 PM
Quote from: Mr. Matté on July 10, 2019, 12:49:47 PM
It seems as of late that if I try to grab the the orange man to view a Streetview location, the blue lines that show where imagery is available is much spottier than usual. However, if I do go to one of the roads where said blue line doesn't appear, the SV imagery is available.

I haven't had any issues with Street View since the last bug I reported was fixed (related to "tracks" and getting stuck in one).

That said, I seem to recall (a while ago) some situations where not all the areas covered by Street View were correctly highlighted. Not good to see that it's back for some.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on July 15, 2019, 02:59:54 PM
Once again, Google Maps rejected my request to get CT 31 along and north of US 44 changed from the square County Route shield to a round state route shield.  Is there anyone here that has the power to change it?  I have emailed them about it and even included pictures from GSV showing them it's the same damn route shield on both sides of US 44, and they still keep rejecting it.  It's been over 3 years and 20 requests, even with visual evidence, and they keep rejecting my edit suggestion, even though they've accepted several of my minor requests, including corrections to street names in my town.  They just don't grasp the concept that there are no county highways in CT and that it's the same damn route.   :angry: 
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 16, 2019, 01:03:17 AM
Quote from: jp the roadgeek on July 15, 2019, 02:59:54 PM
over 3 years and 20 requests

There's no way it's that big of a deal.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on July 16, 2019, 03:28:38 AM
Quote from: jakeroot on July 16, 2019, 01:03:17 AM
Quote from: jp the roadgeek on July 15, 2019, 02:59:54 PM
over 3 years and 20 requests

There's no way it's that big of a deal.

Gotta admire the tenacity, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: mrsman on July 17, 2019, 02:21:27 PM
One thing I hate about G maps is that it is difficult to tell between multi-lane primary routes, freeways, and tollways since all are shown as being on yellow.  It would be nice to have an online map that distinguished freeways and tollways with different colors.  Bing used to do this well.  While Bing seem to denote freeways and expressways with a clearly darker shade of yellow, they no longer properly distinguish toll roads (they used to be in turquoise).

Does anyone know of an online map that denotes toll roads in a clear manner?  Especially helpful if they denote toll direction (only showing tolls on bridges in the direction that you have to pay).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 17, 2019, 08:11:20 PM
Google used to do it, two versions ago.  Oddly enough, they removed it because it looked too similar to the symbol for expressways, only to get rid of differentiating expressways in the latest version without bringing back the differentiation of freeway toll roads.  Toll roads are still shown for other types of roads (https://www.google.com/maps/@44.7344798,-75.468089,14z), but not freeways.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 17, 2019, 09:44:33 PM
Quote from: mrsman on July 17, 2019, 02:21:27 PM
It would be nice to have an online map that distinguished freeways and tollways with different colors.

Most tollways in my neck of the woods are freeways.
Title: Re: Google Maps just fucking SUCKS now
Post by: mrsman on July 19, 2019, 01:14:19 PM
Quote from: vdeane on July 17, 2019, 08:11:20 PM
Google used to do it, two versions ago.  Oddly enough, they removed it because it looked too similar to the symbol for expressways, only to get rid of differentiating expressways in the latest version without bringing back the differentiation of freeway toll roads.  Toll roads are still shown for other types of roads (https://www.google.com/maps/@44.7344798,-75.468089,14z), but not freeways.

I've seen that also, but IMO simply bolding the edges is too subtle of a difference.

Some of the old paper maps that I have would make the distinction really clear.  Only freeways would have red.  Only toll roads would have green.  Other roads would be yellow or black.

It's too bad that we can't get that in online maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: ipeters61 on July 19, 2019, 02:30:34 PM
Quote from: mrsman on July 19, 2019, 01:14:19 PM
Quote from: vdeane on July 17, 2019, 08:11:20 PM
Google used to do it, two versions ago.  Oddly enough, they removed it because it looked too similar to the symbol for expressways, only to get rid of differentiating expressways in the latest version without bringing back the differentiation of freeway toll roads.  Toll roads are still shown for other types of roads (https://www.google.com/maps/@44.7344798,-75.468089,14z), but not freeways.

I've seen that also, but IMO simply bolding the edges is too subtle of a difference.

Some of the old paper maps that I have would make the distinction really clear.  Only freeways would have red.  Only toll roads would have green.  Other roads would be yellow or black.

It's too bad that we can't get that in online maps.
Reminds me of when I had a manual once, where colors would have been helpful.  The manual was only available as a PDF....so why was it only in black and white!?
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on July 19, 2019, 09:15:43 PM
Quote from: jp the roadgeek on July 15, 2019, 02:59:54 PM
Once again, Google Maps rejected my request to get CT 31 along and north of US 44 changed from the square County Route shield to a round state route shield.  Is there anyone here that has the power to change it?  I have emailed them about it and even included pictures from GSV showing them it's the same damn route shield on both sides of US 44, and they still keep rejecting it.  It's been over 3 years and 20 requests, even with visual evidence, and they keep rejecting my edit suggestion, even though they've accepted several of my minor requests, including corrections to street names in my town.  They just don't grasp the concept that there are no county highways in CT and that it's the same damn route.   :angry:

Meanwhile, they still haven't updated PA 295 to PA 297 (http://en.wikipedia.org/wiki/Pennsylvania_Route_297). Granted, Street View hasn't been updated anywhere near it. Even the BGSes on I-83 still say 295 for some reason.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on July 20, 2019, 05:34:40 PM
Quote from: jp the roadgeek on July 15, 2019, 02:59:54 PM
Once again, Google Maps rejected my request to get CT 31 along and north of US 44 changed from the square County Route shield to a round state route shield.  Is there anyone here that has the power to change it?  I have emailed them about it and even included pictures from GSV showing them it's the same damn route shield on both sides of US 44, and they still keep rejecting it.  It's been over 3 years and 20 requests, even with visual evidence, and they keep rejecting my edit suggestion, even though they've accepted several of my minor requests, including corrections to street names in my town.  They just don't grasp the concept that there are no county highways in CT and that it's the same damn route.   :angry:
Reason #1012614 that I have no respect for Google.  Stupid monopolistic hacks who can't figure out how to do anything right.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on July 20, 2019, 05:50:41 PM
Quote from: Roadsguy on July 19, 2019, 09:15:43 PM
Quote from: jp the roadgeek on July 15, 2019, 02:59:54 PM
Once again, Google Maps rejected my request to get CT 31 along and north of US 44 changed from the square County Route shield to a round state route shield.  Is there anyone here that has the power to change it?  I have emailed them about it and even included pictures from GSV showing them it's the same damn route shield on both sides of US 44, and they still keep rejecting it.  It's been over 3 years and 20 requests, even with visual evidence, and they keep rejecting my edit suggestion, even though they've accepted several of my minor requests, including corrections to street names in my town.  They just don't grasp the concept that there are no county highways in CT and that it's the same damn route.   :angry:

Meanwhile, they still haven't updated PA 295 to PA 297 (http://en.wikipedia.org/wiki/Pennsylvania_Route_297). Granted, Street View hasn't been updated anywhere near it. Even the BGSes on I-83 still say 295 for some reason.

To add to this pile, US-117 in NC between Goldsboro and Wilson is labeled as both US-117 AND US-117 Alternate. The short-lived US-117 Alternate was decommissioned in 2009 when US-117 was taken off what's now I-795 and put back on it's old alignment. Google Streetview has driven up and down that road several times since then. :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on July 21, 2019, 12:42:01 AM
Quote from: LM117 on July 20, 2019, 05:50:41 PM
Google Streetview has driven up and down that road several times since then. :pan:

Probably not a good assumption that Google uses SV imagery to check the accuracy of their map data.
Title: Re: Google Maps just fucking SUCKS now
Post by: 20160805 on July 21, 2019, 06:46:25 AM
Quote from: MNHighwayMan on July 21, 2019, 12:42:01 AM
Quote from: LM117 on July 20, 2019, 05:50:41 PM
Google Streetview has driven up and down that road several times since then. :pan:

Probably not a good assumption that Google uses SV imagery to check the accuracy of their map data.
It only makes sense that they should, though, which is what makes this ridiculous.
Title: Re: Google Maps just fucking SUCKS now
Post by: Verlanka on August 15, 2019, 05:04:41 AM
I was using Google Maps the other day and noticed that it no longer told you that you were changing time zones driving directions, which is ridiculous. :pan:

Edit: It appears they brought it back for now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 15, 2019, 06:32:45 AM
I am still ticked you can't print out directions with turn by turn maps and yet the option still reads "print with maps."
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 21, 2019, 09:23:46 AM
I noticed this morning that the Streetview feature on the Google Maps app on my iPhone 6s is gone. No matter where I try to look, no Streetview. Anybody else having this problem?
Title: Re: Google Maps just fucking SUCKS now
Post by: FightingIrish on August 21, 2019, 09:48:02 AM
Quote from: LM117 on August 21, 2019, 09:23:46 AM
I noticed this morning that the Streetview feature on the Google Maps app on my iPhone 6s is gone. No matter where I try to look, no Streetview. Anybody else having this problem?
Google really screwed up the iOS version of the Maps app. No Street View, and an obnoxious Explore sidebar that takes up a third of the screen. However, now the sidebar is gone. Still no SV - for now you have to use the SV app for that.

Google needs to fix this mess ASAP.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on August 21, 2019, 02:45:12 PM
Quote from: FightingIrish on August 21, 2019, 09:48:02 AM
Quote from: LM117 on August 21, 2019, 09:23:46 AM
I noticed this morning that the Streetview feature on the Google Maps app on my iPhone 6s is gone. No matter where I try to look, no Streetview. Anybody else having this problem?
Google really screwed up the iOS version of the Maps app. No Street View, and an obnoxious Explore sidebar that takes up a third of the screen. However, now the sidebar is gone. Still no SV - for now you have to use the SV app for that.

Google needs to fix this mess ASAP.

Have been having the same issue with street view on the Google Maps app. The GSV feature was always a little buggy in that you needed to drop the pin exactly on the road, and there wasn't a way to definitively tell whether the road didn't have SV or if the pin needed to be more accurate. Took me a few days to realize it had been totally turned off.

Also TIL there's a separate Street View app. The things you learn...
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on August 21, 2019, 07:39:50 PM
https://www.google.com/maps/place/Bedminster,+NJ/@40.6436115,-74.6605591,3a,75y,96.63h,90.5t,0.23r/data=!3m1!1e3!4m5!3m4!1s0x89c396b7daf761a7:0x47d1f51b0a27c8e0!8m2!3d40.669264!4d-74.6804  Going from Street View to map does this.  This is supposed to be Bedminster, NJ.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 21, 2019, 08:23:32 PM
Quote from: LM117 on August 21, 2019, 09:23:46 AM
I noticed this morning that the Streetview feature on the Google Maps app on my iPhone 6s is gone. No matter where I try to look, no Streetview. Anybody else having this problem?
Same issue here... very frustrating having to swap between apps and get to one particular location. The Street View app sucks to add to this mess more.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 22, 2019, 02:44:56 AM
Looks to be an iOS issue. No problems on Android 9:

(https://i.imgur.com/sOkvup6.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 22, 2019, 08:41:54 AM
Quote from: jakeroot on August 22, 2019, 02:44:56 AM
Looks to be an iOS issue. No problems on Android 9:
Actually, it appears whatever issue it was is now fixed. My iPhone is now letting me view Street View once again like normal.

Appears this was just a bug, thankfully it's not permanent, and was fixed quickly.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 22, 2019, 10:23:25 AM
Quote from: sprjus4 on August 22, 2019, 08:41:54 AM
Quote from: jakeroot on August 22, 2019, 02:44:56 AM
Looks to be an iOS issue. No problems on Android 9:
Actually, it appears whatever issue it was is now fixed. My iPhone is now letting me view Street View once again like normal.

Appears this was just a bug, thankfully it's not permanent, and was fixed quickly.

I just checked it on mine after seeing this post and it's back to normal for me too.

*knock on wood*
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on August 28, 2019, 10:14:15 PM
Quote from: roadman65 on August 21, 2019, 07:39:50 PM
https://www.google.com/maps/place/Bedminster,+NJ/@40.6436115,-74.6605591,3a,75y,96.63h,90.5t,0.23r/data=!3m1!1e3!4m5!3m4!1s0x89c396b7daf761a7:0x47d1f51b0a27c8e0!8m2!3d40.669264!4d-74.6804  Going from Street View to map does this.  This is supposed to be Bedminster, NJ.

That issue happens to me every so often too.  I can get around it by changing the end of the URL to ,XXz to go back to map view, then switch back to satellite view.




Lately, Google Maps uses a lot of CPU on my computer.  I'm on an older browser and computer, which means I don't have full GPU acceleration so the CPU gets used more, but until recently, the CPU usage wasn't as bad.  I noticed that Session Buddy and Adblock Plus were using a lot of CPU in addition to the Browser and map tab processes.  Killing the extensions makes a minor improvement, but the CPU is still higher than normal.

I tried using a Slimjet, which is a fork of Chrome above 50 for XP with just a map open, and the issue persists.  I also disabled Slimjet's built-in ad blocker to reduce the CPU load, and the CPU is still high.

I was watching a friend use Google Maps today on a new Windows 10 laptop, and the screen kept flashing completely black.  That makes me think that Google changed something, and it's not just me.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on August 28, 2019, 10:35:37 PM
Quote from: Michael on August 28, 2019, 10:14:15 PM
Quote from: roadman65 on August 21, 2019, 07:39:50 PM
https://www.google.com/maps/place/Bedminster,+NJ/@40.6436115,-74.6605591,3a,75y,96.63h,90.5t,0.23r/data=!3m1!1e3!4m5!3m4!1s0x89c396b7daf761a7:0x47d1f51b0a27c8e0!8m2!3d40.669264!4d-74.6804  Going from Street View to map does this.  This is supposed to be Bedminster, NJ.

That issue happens to me every so often too.  I can get around it by changing the end of the URL to ,XXz to go back to map view, then switch back to satellite view.




Lately, Google Maps uses a lot of CPU on my computer.  I'm on an older browser and computer, which means I don't have full GPU acceleration so the CPU gets used more, but until recently, the CPU usage wasn't as bad.  I noticed that Session Buddy and Adblock Plus were using a lot of CPU in addition to the Browser and map tab processes.  Killing the extensions makes a minor improvement, but the CPU is still higher than normal.

I tried using a Slimjet, which is a fork of Chrome above 50 for XP with just a map open, and the issue persists.  I also disabled Slimjet's built-in ad blocker to reduce the CPU load, and the CPU is still high.

I was watching a friend use Google Maps today on a new Windows 10 laptop, and the screen kept flashing completely black.  That makes me think that Google changed something, and it's not just me.

Back in 2016 I just about burned myself giving my parents directions using Google Maps because of the high amount of CPU usage on my phone. It also drained my battery very quickly. That being said I was using a DROID MINI from 2013 (my first phone, I have an S9+ now).
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on September 21, 2019, 10:51:36 AM
Is this here on Google an error? https://www.google.com/maps/place/Texarkana,+TX/@33.4415416,-94.1639111,12z/data=!3m1!4b1!4m5!3m4!1s0x86344132c2a06457:0x9d583c9261db5b70!8m2!3d33.425125!4d-94.0476882  What I am talking about is the city limit line on US 59 at the point it leaves I-369 for Lake Drive?

If you look at a photo I took, you will see a City Limit sign for Texarkana going SB and not NB, that is heading out of the city per Googlemaps.  Now the sign could be in error by leaving out the other half of the info it is implying such as not featuring "Leaving" as other Texas city limits signs convey or like Virginia does at each city limit with enter a county and leave the city thing.
https://www.flickr.com/photos/54480415@N08/48764321847/in/dateposted-public/
Title: Re: Google Maps just fucking SUCKS now
Post by: seicer on September 26, 2019, 07:20:39 AM
Is there a list of updates from Google of new imagery?
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on October 06, 2019, 09:06:12 PM
Sometime within the week or so before September 26th, Google changed something that now forces a redirect to an "upgrade your browser" page when I use my old version of Chrome.  I tried spoofing my useragent to the newest version of Chrome, but I still got the redirect, so it's more than a simple useragent check.  Based on looking at the developer tools, it looks like some sort of JavaScript test that fails.  I hate programming, so I can't write a userscript to force it to work.  I tried looking up code snippets to block the variables from being set, but that didn't work.

The thing that annoys me is that there wasn't any visible change on Maps itself.  It seems to use more CPU on the browsers it does work on though. In addition to the change with Maps, the scores at the top of search result pages for sports are gone unless I use a newer browser.  Facebook has made similar changes in the past, and those annoy me too.  I'd understand not supporting old browsers in a redesign, but in both cases, there hasn't been any visible design change!  It's as if people with old browsers are being "punished".  I've used the "your car is no longer compatible with the road network" analogy before, but after this latest issue, I'd expand that to include the fact that there wasn't any change in the road.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 06, 2019, 09:19:42 PM
Just because there wasn't a design change doesn't mean there wasn't a back-end change in the code.  Large programs, apps, and websites have pretty much constant bug fixes, library updates, etc.  That said, "punish people with old hardware/software" seems to be a thing these days now that hardware upgrades aren't spurring people to get new computers and phones as often as was typical in the past.  Amazon just discontinued the ability to watch CBS All Access in their app on my smart TV for no good reason, for example.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 07, 2019, 12:34:34 AM
Quote from: Michael on October 06, 2019, 09:06:12 PM
Sometime within the week or so before September 26th, Google changed something that now forces a redirect to an "upgrade your browser" page when I use my old version of Chrome..

Why not upgrade your browser?

Chrome certainly isn't a "lite" browser, but I would never consider any version from the past two years as being any better than the current version.
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on October 07, 2019, 12:47:03 PM
Quote from: vdeane on October 06, 2019, 09:19:42 PM
Just because there wasn't a design change doesn't mean there wasn't a back-end change in the code.  Large programs, apps, and websites have pretty much constant bug fixes, library updates, etc.

Exactly this.

I'm a web developer in my day job, and I can promise y'all that we don't just tell you to upgrade your browsers for the hell of it. (Indeed, not infrequently I have to scrap or significantly alter plans for new features specifically because we have to accommodate some customer out there who's still using IE8 or something like that.) It really is a last resort.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on October 07, 2019, 06:43:36 PM
Quote from: jakeroot on October 07, 2019, 12:34:34 AM
Quote from: Michael on October 06, 2019, 09:06:12 PM
Sometime within the week or so before September 26th, Google changed something that now forces a redirect to an "upgrade your browser" page when I use my old version of Chrome..
Why not upgrade your browser?

This. Especially for security reasons. There are very few good reasons to use an old browser these days.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 07, 2019, 08:03:22 PM
Quote from: MNHighwayMan on October 07, 2019, 06:43:36 PM
Quote from: jakeroot on October 07, 2019, 12:34:34 AM
Quote from: Michael on October 06, 2019, 09:06:12 PM
Sometime within the week or so before September 26th, Google changed something that now forces a redirect to an "upgrade your browser" page when I use my old version of Chrome..
Why not upgrade your browser?
This. Especially for security reasons. There are very few good reasons to use an old browser these days.

I can't even think of one reason.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on October 07, 2019, 08:15:55 PM
Because maybe some people don't want to upgrade their browser?
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on October 07, 2019, 08:31:13 PM
Quote from: sprjus4 on October 07, 2019, 08:15:55 PM
Because maybe some people don't want to upgrade their browser?

Which is idiotic, if it's mere preference.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on October 07, 2019, 08:41:58 PM
Quote from: MNHighwayMan on October 07, 2019, 08:31:13 PM
Quote from: sprjus4 on October 07, 2019, 08:15:55 PM
Because maybe some people don't want to upgrade their browser?

Which is idiotic, if it's mere preference.
It's just your opinion. It's not really always "idiotic" .
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on October 07, 2019, 08:53:38 PM
Quote from: sprjus4 on October 07, 2019, 08:15:55 PM
Because maybe some people don't want to upgrade their browser?
Or they can't upgrade their browser. I'm mainly referring to Windows XP users here, as most if not all the major browsers have cut support for the OS.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on October 07, 2019, 10:36:38 PM
Quote from: jakeroot on October 07, 2019, 12:34:34 AM
Quote from: Michael on October 06, 2019, 09:06:12 PM
Sometime within the week or so before September 26th, Google changed something that now forces a redirect to an "upgrade your browser" page when I use my old version of Chrome..

Why not upgrade your browser?

Chrome certainly isn't a "lite" browser, but I would never consider any version from the past two years as being any better than the current version.

I'm not a fan of the design changes in newer versions.  If I were a programmer, I suppose I could compile a custom version with the older GUI.

Quote from: Eth on October 07, 2019, 12:47:03 PM
Quote from: vdeane on October 06, 2019, 09:19:42 PM
Just because there wasn't a design change doesn't mean there wasn't a back-end change in the code.  Large programs, apps, and websites have pretty much constant bug fixes, library updates, etc.

Exactly this.

I'm a web developer in my day job, and I can promise y'all that we don't just tell you to upgrade your browsers for the hell of it. (Indeed, not infrequently I have to scrap or significantly alter plans for new features specifically because we have to accommodate some customer out there who's still using IE8 or something like that.) It really is a last resort.

I'm suspicious of there being a major under the hood change that actually breaks older browsers because it actually starts loading before it redirects.  As it starts to load, it looks the exact same as it did before the redirect.  Instead of forcing a redirect for browsers older than a certain version, they should have a message bar or popup like YouTube has.  Just because a browser is old, that doesn't mean it won't at least somewhat work.  Before this latest change, if I didn't spoof my useragent, Maps at least gave me a basic map view that I could pan and zoom.  When this latest change happened, I tried Firefox 2 (yes, 2) just to see what would happen.  I got a blank white page, but hey, I guess at least there wasn't a redirect!

As I was typing this post, I thought I'd try a version of Firefox that was released around the same time as my version of Chrome.  I got the redirect, but when I tried to spoof my useragent in about:config, I somehow got Maps to work with just a few CSS glitches.  Even Street View worked!  When I tried again, I couldn't get it to work.  This tells me that it's just a blanket block without any consideration as to if an old browser actually supports the necessary standards.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on October 08, 2019, 03:04:18 PM
Quote from: sprjus4 on October 07, 2019, 08:41:58 PM
Quote from: MNHighwayMan on October 07, 2019, 08:31:13 PM
Quote from: sprjus4 on October 07, 2019, 08:15:55 PM
Because maybe some people don't want to upgrade their browser?
Which is idiotic, if it's mere preference.
It's just your opinion. It's not really always "idiotic" .

No. Running older browsers just because you prefer that version is allowing yourself to run a browser with known security exploits. If you want your banking info or other personal information stolen, that's on you. It's still idiotic, though.

Besides that, technology changes, evolves. At some point people need to stop using ancient software.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on October 08, 2019, 03:51:02 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PMI can't even think of one reason.

I can.  Tamper Data.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 08, 2019, 11:17:02 PM
Quote from: Michael on October 07, 2019, 10:36:38 PM
I'm not a fan of the design changes in newer versions.  If I were a programmer, I suppose I could compile a custom version with the older GUI.

What design changes? It's looked virtually the same since release.

Quote from: J N Winkler on October 08, 2019, 03:51:02 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PMI can't even think of one reason.

I can.  Tamper Data.

Shortest post ever! :-D

Do tell more. There are Chrome extensions having to do with Tamper Data, but I don't know much about it.

Do you think the negatives of upgrading outweigh the positives? I'm sure there might be a few good reasons, but certainly they don't outweigh the benefits of upgrading. I can understand not upgrading software if the device is never connected to the internet. But for an internet browser itself? Seems like a stretch to try and keep that one out of date.
Title: Re: Google Maps just fucking SUCKS now
Post by: Verlanka on October 09, 2019, 05:09:56 AM
Quote from: jakeroot on October 08, 2019, 11:17:02 PM

Quote from: J N Winkler on October 08, 2019, 03:51:02 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PMI can't even think of one reason.

I can.  Tamper Data.

Shortest post ever! :-D
I'm sure there are shorter posts out there.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on October 09, 2019, 07:10:33 AM
Quote from: Verlanka on October 09, 2019, 05:09:56 AM
Quote from: jakeroot on October 08, 2019, 11:17:02 PM

Quote from: J N Winkler on October 08, 2019, 03:51:02 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PMI can't even think of one reason.

I can.  Tamper Data.

Shortest post ever! :-D
I'm sure there are shorter posts out there.

I think Jake meant "shortest J N Winkler post" :)
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on October 09, 2019, 08:08:20 AM
Quote from: Verlanka on October 09, 2019, 05:09:56 AM
Quote from: jakeroot on October 08, 2019, 11:17:02 PM

Quote from: J N Winkler on October 08, 2019, 03:51:02 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PMI can't even think of one reason.

I can.  Tamper Data.

Shortest post ever! :-D
I'm sure there are shorter posts out there.
yep
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on October 09, 2019, 08:42:20 AM
Quote from: US 89 on October 09, 2019, 08:08:20 AM
Quote from: Verlanka on October 09, 2019, 05:09:56 AM
Quote from: jakeroot on October 08, 2019, 11:17:02 PM

Quote from: J N Winkler on October 08, 2019, 03:51:02 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PMI can't even think of one reason.

I can.  Tamper Data.

Shortest post ever! :-D
I'm sure there are shorter posts out there.
yep

Sí
Title: Re: Google Maps just fucking SUCKS now
Post by: english si on October 09, 2019, 10:15:26 AM
Quote from: LM117 on October 09, 2019, 08:42:20 AMSí
:wave:
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on October 09, 2019, 01:11:02 PM
Title: Re: Google Maps just fucking SUCKS now
Post by: Big John on October 09, 2019, 04:40:39 PM
Short post: (https://2static1.fjcdn.com/comments/See+this+this+is+a+short+post+_57b4a943f4a802a1ecbfdc76f5a1d589.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: ftballfan on October 09, 2019, 05:29:35 PM
https://www.google.com/maps/@44.1937941,-86.1845789,14.75z?hl=en
https://www.google.com/maps/@44.1856518,-86.1671143,1103m/data=!3m1!1e3?hl=en
https://www.google.com/maps/@44.1910698,-86.1782038,1094m/data=!3m1!1e3?hl=en

This has been like this on Google Maps for years! Google Maps is way off in this area:
Little River Road and Six Mile Bridge Road are through roads (neither dead end in real life; the paths can be seen from satellite imagery)

Not far from these areas, Carty Road and Lindeman Road, although both dead ends, are short-changed compared to the satellite imagery. It goes double as both roads are paved and county maintained!
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on October 09, 2019, 08:58:38 PM
Quote from: jakeroot on October 08, 2019, 11:17:02 PM
Quote from: Michael on October 07, 2019, 10:36:38 PM
I'm not a fan of the design changes in newer versions.  If I were a programmer, I suppose I could compile a custom version with the older GUI.

What design changes? It's looked virtually the same since release.


Even though it was a minor change, my initial compliant was the change from a wrench icon to an ellipsis for the menu icon.  Looking back, that's not a huge deal compared to the changes since then.  I'm one of those people who browse in incognito mode to keep my history from being clogged (from what I've read on the forum, I'm not the only one who does that).  Older versions of Chrome have a clunky "hidden" way to delete incognito cookies without closing all incognito windows.  In an incognito window, I can press [CTRL]+[H] to open my history, but unlike newer versions of Chrome, it opens in the current incognito window instead of opening a regular window.  From the history page, I can click Settings, and ultimately delete individual incognito cookies.

The other design change I don't like is the new Developer Tools.  The old icons for the panes were bigger and easier to click.  In the old Developer Tools, you could click the gear icon at the bottom right to get a screen where you could disable JavaScript and change your useragent.  In newer versions, you can disable JavaScript from the favico in the Omnibox.  To change your useragent, you have to click the ellipsis at the top of the Developer Tools, go to More Tools, then Network Conditions.  Clicking that opens a pane where the console would normally be, and that pane has the option for changing your useragent.  To me, adding more steps to a task is not "improvement".  Also, I prefer having the document tree and CSS side by side instead of above and below each other in the Elements pane.

EDIT: I just found the option to change the Elements pane layout in newer Chrome versions, but the default option is the above and below layout.  I found this setting before, but I forgot about it.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 11, 2019, 01:58:27 PM
Quote from: jakeroot on October 07, 2019, 08:03:22 PM
Quote from: MNHighwayMan on October 07, 2019, 06:43:36 PM
Quote from: jakeroot on October 07, 2019, 12:34:34 AM
Quote from: Michael on October 06, 2019, 09:06:12 PM
Sometime within the week or so before September 26th, Google changed something that now forces a redirect to an "upgrade your browser" page when I use my old version of Chrome..
Why not upgrade your browser?
This. Especially for security reasons. There are very few good reasons to use an old browser these days.

I can't even think of one reason.

The computer I'm using isn't mine, so I can't very well just decide to upgrade the browser.  I'm on lunch break at work.  Certain programs I use for work have serious issues with newer versions of both OS and browsers.  For example, in order to get one of my work VPNs to function correctly, I have to use IExplorer (no longer supported) and run it in emulation mode at document mode 8.  Running it in normal IE11 makes absolutely nothing on the internet work as soon as I lock down the VPN–even programs that I access inside of the VPN won't work.  People in other offices (and at other desks in my own office) who never upgrade anything unless they have no choice don't tend to have this sort of problem.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on October 11, 2019, 04:05:43 PM
Quote from: jakeroot on October 08, 2019, 11:17:02 PMShortest post ever! :-D

Keeping it short is one way to set the hook . . .

Quote from: jakeroot on October 08, 2019, 11:17:02 PMDo tell more. There are Chrome extensions having to do with Tamper Data, but I don't know much about it.

Tamper Data is a Firefox plugin (now no longer being updated and not compatible with current versions of Firefox) that allows inspection of traffic between the browser and the server.  It runs in a separate window and each transaction (client transmission/server response) is on one line.  I use it for writing wget wrapper scripts to automate plan acquisition.  In order to work successfully, wget has to supply headers and postdata of the correct form when they are appropriate (some scripts have an "AjaxHeaders" variable defined for use in cases where a server call requires XMLHttpRequest, and many subroutines have "Confect Postdata" as part of their title).  Tamper Data makes this information available in a form that is easy to work with for coding purposes.

Chrome Developer Tools has some of the same functionality, but in a form that is harder to work with.  (The "Copy request as curl" function that is built in often omits many of the headers that are required for a transaction to succeed.)

In terms of third-party apps, WireShark can track web traffic but cannot penetrate HTTPS encryption.  Fiddler will penetrate ordinary HTTPS using an interposed key (effectively a type of "man in the middle" attack since the traffic is being routed from server to Fiddler to browser), but can do nothing about HTTPS with HTST because the server actually checks that the browser is on the other end of the tunnel.

Quote from: jakeroot on October 08, 2019, 11:17:02 PMDo you think the negatives of upgrading outweigh the positives? I'm sure there might be a few good reasons, but certainly they don't outweigh the benefits of upgrading. I can understand not upgrading software if the device is never connected to the internet. But for an internet browser itself? Seems like a stretch to try and keep that one out of date.

From a user point of view, whether the negatives outweigh the positives depends on the specific use cases.  I can say that no longer being able to use Tamper Data would set me back in terms of automation.  However, given that Tamper Data is no longer being developed and there is continuing evolution in how client/server transactions are handled, lack of Tamper Data will become less important in time as a reason not to upgrade Firefox.  And a good point was made upthread about using an up-to-date browser to access banking information.  I personally have been very hesitant to write scripts to access sites that can commit money.  I have done this just once or twice, and in the case I remember best--Indoxservices, back when MoDOT was still using it for plan distribution--I wrote a breakpoint in the code that would parse the account statement page and cause the script to exit if a nonzero total was shown.  (Indoxservices' deal with MoDOT was that there would be a per-sheet charge for plans on paper and a media charge for plans on CD, but none for plans downloaded electronically.  I think MoDOT took plans distribution back in-house when it was realized almost no-one was choosing the pay options.)

I continue to use Firefox because, so far, nothing significant is broken, and I don't normally do banking online.  (I think the banking industry's current approach to two-factor security, with one factor consisting of varying challenge questions, is very badly designed.  I think it should be restricted to a level of access that allows money to be committed, while the customer should have the option of accessing certain types of information, such as statements and a transaction history, through an alternate method that is easily scriptable and does not require access to proprietary software.)  I do have an up-to-date version of Chrome that I can use when a higher level of security is required.

My personal approach to security, which I have found very effective, is to limit the scope for things to execute rather than to focus on keeping everything absolutely up to date.  I generally read email in text only; if an email lands with a "Won't display" message (basically a prod to view the HTML version), I often set a filter for it for that reason alone, because I am not interested in doing business with entities that won't respect my desire to read email in plain text only.  I use both AdBlock Plus and an ad-blocking HOSTS file, and I find the latter to be much more effective in keeping my system fast and clutter-free; there is no actual need for AdBlock Plus to kick in to block anything if the browser loops back to localhost instead of visiting the ad server.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 12, 2019, 02:36:11 AM
Thanks for the post, JN. Good explanation. Seems fair!




My post on the last page was referencing this post from a while back. Didn't want to straight-up steal Alps' (Steve's) line...my quote was one word shorter! I'd been patiently awaiting the day.

Quote from: Alps on April 02, 2012, 11:05:58 PM
Quote from: J N Winkler on April 02, 2012, 07:56:26 PM
Quote from: Steve on April 02, 2012, 07:18:50 PMSomeone needs a sense of humor installed.

I'd certainly agree with that.
Congrats on your shortest post ever!
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on October 30, 2019, 11:25:45 PM
As of this evening, there seems to be a bug where no route shields display at all. Everything else seems to still work.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on November 05, 2019, 07:28:26 PM
The actual map on Google Maps now shows green basically everywhere there are trees; so at first glance, park boundaries aren't very clear. 
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 05, 2019, 07:50:14 PM
Quote from: ozarkman417 on November 05, 2019, 07:28:26 PM
The actual map on Google Maps now shows green basically everywhere there are trees; so at first glance, park boundaries aren't very clear. 
I was wondering if the seemingly random green patches meant anything.  I don't understand why they did this.  It makes the map less readable and parks harder to see.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on November 05, 2019, 07:58:43 PM
Quote from: vdeane on November 05, 2019, 07:50:14 PM
Quote from: ozarkman417 on November 05, 2019, 07:28:26 PM
The actual map on Google Maps now shows green basically everywhere there are trees; so at first glance, park boundaries aren't very clear. 
I was wondering if the seemingly random green patches meant anything.  I don't understand why they did this.  It makes the map less readable and parks harder to see.

So it's not just me that noticed this!
Weirdly, it's only at the mid-zoom levels. Zoom in or out far enough, and it returns to normal. I don't like it either; not only does it make it harder to see what's going on, there's no rhyme or reason to the green patches, with some entire suburban neighborhoods being green.

My guess is it's a trial of some sort, they get negative feedback, and it returns to normal soon.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on November 05, 2019, 08:25:28 PM
Quote from: webny99 on November 05, 2019, 07:58:43 PM
My guess is it's a trial of some sort, they get negative feedback, and it returns to normal soon they keep it that way anyway.

FTFY
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on November 07, 2019, 09:48:06 AM
Quote from: vdeane on November 05, 2019, 07:50:14 PM
Quote from: ozarkman417 on November 05, 2019, 07:28:26 PM
The actual map on Google Maps now shows green basically everywhere there are trees; so at first glance, park boundaries aren't very clear. 
I was wondering if the seemingly random green patches meant anything.  I don't understand why they did this.  It makes the map less readable and parks harder to see.

Agreed. I think it sucks. If there's a way for Google to fuck something up, they'll find it.

Quote from: Roadsguy on November 05, 2019, 08:25:28 PM
Quote from: webny99 on November 05, 2019, 07:58:43 PM
My guess is it's a trial of some sort, they get negative feedback, and it returns to normal soon they keep it that way anyway.

FTFY

Yep. They don't give a shit.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 07, 2019, 12:40:44 PM
Honestly, part of me wishes I had the time/resources to figure out how to make a roadgeek Google Maps replacement.  It's quite clear that browsing around the map isn't something they really support, especially for people looking at the roads and not for businesses.  They want you to use search and driving directions for everything.  This isn't just Google, either - the modern paradigm is to ask the computer to find things for you.  More and more the same trend is on businesses when finding locations where they're at.  They won't allow you to just browse a map of all their locations, even though they could easily do so - they want you to enter your location in the search bar and show only the nearest ones.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on November 07, 2019, 01:55:41 PM
Quote from: vdeane on November 07, 2019, 12:40:44 PM
They won't allow you to just browse a map of all their locations, even though they could easily do so - they want you to enter your location in the search bar and show only the nearest ones.

Many restaurant websites themselves do this, as well, which frustrates me to no end.
Say for example, I want to check to see if they're nationwide or not (https://www.aaroads.com/forum/index.php?topic=25912).
Nope, impossible: There's one in Webster, one in Greece, and one in Henrietta, and that's all we'll disclose!
Title: Re: Google Maps just fucking SUCKS now
Post by: jamess on November 07, 2019, 03:22:52 PM
Quote from: vdeane on November 07, 2019, 12:40:44 PM
Honestly, part of me wishes I had the time/resources to figure out how to make a roadgeek Google Maps replacement.  It's quite clear that browsing around the map isn't something they really support, especially for people looking at the roads and not for businesses.  They want you to use search and driving directions for everything.  This isn't just Google, either - the modern paradigm is to ask the computer to find things for you.  More and more the same trend is on businesses when finding locations where they're at.  They won't allow you to just browse a map of all their locations, even though they could easily do so - they want you to enter your location in the search bar and show only the nearest ones.

Have you tried Open Streets Maps?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 07, 2019, 08:07:00 PM
Quote from: jamess on November 07, 2019, 03:22:52 PM
Quote from: vdeane on November 07, 2019, 12:40:44 PM
Honestly, part of me wishes I had the time/resources to figure out how to make a roadgeek Google Maps replacement.  It's quite clear that browsing around the map isn't something they really support, especially for people looking at the roads and not for businesses.  They want you to use search and driving directions for everything.  This isn't just Google, either - the modern paradigm is to ask the computer to find things for you.  More and more the same trend is on businesses when finding locations where they're at.  They won't allow you to just browse a map of all their locations, even though they could easily do so - they want you to enter your location in the search bar and show only the nearest ones.

Have you tried Open Streets Maps?
OSM isn't perfect either on that front and has much fewer features.  I do have a bookmark for it, but I'm not really a fan of having to switch between a ton of different on mapping sources.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on November 08, 2019, 12:47:25 AM
Quote from: vdeane on November 07, 2019, 08:07:00 PM
Quote from: jamess on November 07, 2019, 03:22:52 PM
Quote from: vdeane on November 07, 2019, 12:40:44 PM
Honestly, part of me wishes I had the time/resources to figure out how to make a roadgeek Google Maps replacement.  It's quite clear that browsing around the map isn't something they really support, especially for people looking at the roads and not for businesses.  They want you to use search and driving directions for everything.  This isn't just Google, either - the modern paradigm is to ask the computer to find things for you.  More and more the same trend is on businesses when finding locations where they're at.  They won't allow you to just browse a map of all their locations, even though they could easily do so - they want you to enter your location in the search bar and show only the nearest ones.

Have you tried Open Streets Maps?
OSM isn't perfect either on that front and has much fewer features.  I do have a bookmark for it, but I'm not really a fan of having to switch between a ton of different on mapping sources.

The easiest (but still not easy) way would probably be to take use OSM data and create your own renderer/tileset for it that includes the legend you want.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 08, 2019, 12:55:17 PM
I liked when MapQuest had "MapQuest Open" doing just that.  Pity that's no longer available.  Unfortunately, that's still not ideal, as I'm a power user of Google Maps.  I'd have to switch back and forth whenever I wanted to measure something, use street view, use "driving directions" to plot a route (with via points, which OSM doesn't support) to get the drive time and a URL to save the trip (OSM drive times are wildly inaccurate, although OSRM is worse than GraphHopper; maybe the latter just assumes that one drives the speed limit, and the former is just plain wrong?  Regardless, the lack of via points makes it useless for my purposes), look for businesses, look at photos/reviews of businesses, etc. - which is (very) often.  Not to mention that OSM search/direction functionality isn't as nice due to the lack of autocomplete, and the inability to search by address - you have to type in the nearest town and then drag the marker.

Honestly, if it weren't for those limitations, I'd have probably switched, as even baseline OSM cartography beats Google, MapQuest, and Bing at this point.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 08, 2019, 01:06:41 PM
Ight, I'm gonna say it: I like the new forest look. Adds some color to the zoomed out view.

For the record, a roadgeek-friendly Google Maps would not likely be very normal person-friendly.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 08, 2019, 01:28:53 PM
I don't understand how making it easy to scan the map for roads and places and lifting the cap on via points would make it less friendly for everyone else.

To me, green means "park".  Thus, for me, having it green everywhere messes everything up even if it didn't make it hard to see everything else.  Nobody is looking for vegetation when using Google Maps.  Anyone who is looking for vegetation is already using GIS.  It may look pretty, but it destroys usability while offering no functional gains.  Pretty cartography is a virtue, but not when it makes it harder to use the map (though, to be honest, I'm not really a fan of the saturated green everywhere either; I find beauty in the shape of the roads, which is now drowned out and the whole thing looks like a mish-mash of colors).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on November 08, 2019, 01:46:12 PM
I am with vdeane on this one.  The saturation makes the park/public land much harder to discern.  It stinks.
Title: Re: Google Maps just fucking SUCKS now
Post by: adventurernumber1 on November 15, 2019, 09:37:38 PM
I also noticed the new update where forestry is shown in green on Google Maps. While it's interesting to see areas of forest versus lack of forestry, you could theoretically already see that on Google Maps Satellite, so it really isn't necessary on the regular maps. And of course as noted, this gets confusing when mixed in with parks and whatnot that are already recognizable by their green color code. And vdeane is spot-on, as I also find beauty simply in looking at the shape of the roads, so extra aesthetics aren't necessary if they interfere with things (such as making it harder to see where parks are and such).


Quote from: Roadsguy on November 05, 2019, 08:25:28 PM
Quote from: webny99 on November 05, 2019, 07:58:43 PM
My guess is it's a trial of some sort, they get negative feedback, and it returns to normal soon they keep it that way anyway.

FTFY

I'm still waiting for the day when they revert to the old color schemes with the roads (back when the freeway and surface highway colors didn't look almost exactly the same). That still bugs me just as much to this day, even if I've adapted to other bad updates (even though those are still bad too). Maybe they'll change it eventually...  :)  :-/  :meh:
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 15, 2019, 10:23:37 PM
It's yet another step in reducing the contrast of everything.  That green doesn't contrast everything else as much as the default gray does.  When did being able to see things clearly become bad in the eyes of developers?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 03, 2019, 01:13:21 PM
Anybody else notice that globe view is now disabled by default?
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on December 03, 2019, 02:31:01 PM
Quote from: vdeane on December 03, 2019, 01:13:21 PM
Anybody else notice that globe view is now disabled by default?

I did, and was glad to see that, since I usually ended up switching it back to normal ("flat") view anyways.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 04, 2019, 01:05:42 AM
Quote from: vdeane on December 03, 2019, 01:13:21 PM
Anybody else notice that globe view is now disabled by default?

Not for me. But I'm always logged in, unlike some other users, so I suspect it remembers my settings.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 04, 2019, 03:18:34 AM
Quote from: jakeroot on December 04, 2019, 01:05:42 AM
Quote from: vdeane on December 03, 2019, 01:13:21 PM
Anybody else notice that globe view is now disabled by default?
Not for me. But I'm always logged in, unlike some other users, so I suspect it remembers my settings.

I'm always logged in and globe view is now disabled for me (though it was easily re-enabled with a single click, since there was a button for it).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 04, 2019, 04:31:14 AM
Quote from: MNHighwayMan on December 04, 2019, 03:18:34 AM
Quote from: jakeroot on December 04, 2019, 01:05:42 AM
Quote from: vdeane on December 03, 2019, 01:13:21 PM
Anybody else notice that globe view is now disabled by default?
Not for me. But I'm always logged in, unlike some other users, so I suspect it remembers my settings.

I'm always logged in and globe view is now disabled for me (though it was easily re-enabled with a single click, since there was a button for it).

Disabled? As in not able to be enabled? That's definitely strange.

I know I've gotten the update since the globe mode icon has appeared in the bottom right. Possible that the website is determining computer power and giving users one or the other by default, depending on the analysis.
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on December 04, 2019, 04:58:35 AM
Quote from: jakeroot on December 04, 2019, 04:31:14 AM
Quote from: MNHighwayMan on December 04, 2019, 03:18:34 AM
Quote from: jakeroot on December 04, 2019, 01:05:42 AM
Quote from: vdeane on December 03, 2019, 01:13:21 PM
Anybody else notice that globe view is now disabled by default?
Not for me. But I'm always logged in, unlike some other users, so I suspect it remembers my settings.
I'm always logged in and globe view is now disabled for me (though it was easily re-enabled with a single click, since there was a button for it).
Disabled? As in not able to be enabled? That's definitely strange.

Disabled, as in not enabled. As I said, I only had to click one button to turn it back on.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 04, 2019, 12:48:23 PM
Another interesting thing I've noticed: when I open Google Maps at home, either logged in or in incognito, it defaults to the Rochester area, same view as I would expect if I was staying at with my parents.  I checked the location of my IP address and it is showing a location around Albany as I would expect, so I don't know what's going on.  This affects Google News too - my "local" news is now coming from Rochester and not the Capital District.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 04, 2019, 01:43:42 PM
Quote from: vdeane on December 04, 2019, 12:48:23 PM
Another interesting thing I've noticed: when I open Google Maps at home, either logged in or in incognito, it defaults to the Rochester area, same view as I would expect if I was staying at with my parents.  I checked the location of my IP address and it is showing a location around Albany as I would expect, so I don't know what's going on.  This affects Google News too - my "local" news is now coming from Rochester and not the Capital District.

Even after clearing your cache, cookies, history, etc?
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 04, 2019, 01:53:42 PM
Quote from: vdeane on December 04, 2019, 12:48:23 PMAnother interesting thing I've noticed: when I open Google Maps at home, either logged in or in incognito, it defaults to the Rochester area, same view as I would expect if I was staying at with my parents.  I checked the location of my IP address and it is showing a location around Albany as I would expect, so I don't know what's going on.  This affects Google News too - my "local" news is now coming from Rochester and not the Capital District.

I suspect they are using browser fingerprinting.  The last time I ran a fingerprinting test, I found my browser (or, to be more precise, the combination of browser, graphics adapter, etc.) produced an unique hash through a screen drawing test.  There is no way to prevent such tests from being run without disabling JavaScript, and that is uncommon enough to be itself useful for fingerprinting.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 04, 2019, 01:58:49 PM
Quote from: J N Winkler on December 04, 2019, 01:53:42 PM
Quote from: vdeane on December 04, 2019, 12:48:23 PMAnother interesting thing I've noticed: when I open Google Maps at home, either logged in or in incognito, it defaults to the Rochester area, same view as I would expect if I was staying at with my parents.  I checked the location of my IP address and it is showing a location around Albany as I would expect, so I don't know what's going on.  This affects Google News too - my "local" news is now coming from Rochester and not the Capital District.

I suspect they are using browser fingerprinting.  The last time I ran a fingerprinting test, I found my browser (or, to be more precise, the combination of browser, graphics adapter, etc.) produced an unique hash through a screen drawing test.  There is no way to prevent such tests from being run without disabling JavaScript, and that is uncommon enough to be itself useful for fingerprinting.
Except I was using my former Chromebook while traveling, and this is my desktop.  And what would be the point of doing this?  If I'm traveling, I like how the default location changes.  I don't want it to be fixed to a set location no matter where I am.

I can try clearing my cache, but I don't clear cookies because I don't want to lose my auto-logins.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on December 04, 2019, 08:02:08 PM
Microsoft Edge crashes after a few minutes of lurking on GSV.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on December 04, 2019, 08:13:41 PM
Quote from: stormwatch7721 on December 04, 2019, 08:02:08 PM
Microsoft Edge crashes after a few minutes of lurking on GSV.
Why would you even want to use Microsoft Edge in the First place?




I once forgot to sign out of my Google account on a family member's phone when they left town, and then I get shown a bunch a crap from the city they left to and my map is centered on their location on launch despite the fact I am signed in & looking at the map from my own computer and/or phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: stormwatch7721 on December 04, 2019, 08:43:17 PM
It's my favorite browser, Okay?! It just that GSV crashes after a few minutes of lurking.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 04, 2019, 11:19:25 PM
Quote from: MNHighwayMan on December 04, 2019, 04:58:35 AM
Quote from: jakeroot on December 04, 2019, 04:31:14 AM
Quote from: MNHighwayMan on December 04, 2019, 03:18:34 AM
I'm always logged in and globe view is now disabled for me (though it was easily re-enabled with a single click, since there was a button for it).
Disabled? As in not able to be enabled? That's definitely strange.
Disabled, as in not enabled. As I said, I only had to click one button to turn it back on.

You should have said "was disabled" not "is now disabled" (or at the very least wrote "by default" immediately following). That seems to imply that it's disabled right now. That's not how you meant it, but that's how I read it.

For the record, I tried again today and my browser still defaults to globe view. Which is fine by me.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 04, 2019, 11:42:10 PM
Quote from: vdeane on December 04, 2019, 01:58:49 PMExcept I was using my former Chromebook while traveling, and this is my desktop.

This definitely sounds like a situation in which browser fingerprinting is involved, since you say the incorrect location is given in both regular and incognito mode.  Here is what I think is going on:

*  Google fingerprints the browser on your Chromebook while you are in Rochester.

*  Back in Albany, Google detects the Chromebook, recognizes the fingerprint, and concludes all browsers connecting through the same "pipe" have a location of Rochester.  This location attribution persists across both normal and incognito mode because it is based on fingerprinting the other devices' browsers.

Fingerprinting works regardless of whether you are in incognito mode--in other words, incognito is not really incognito.

Quote from: vdeane on December 04, 2019, 01:58:49 PMAnd what would be the point of doing this?  If I'm traveling, I like how the default location changes.  I don't want it to be fixed to a set location no matter where I am.

It could be a bug or future anti-feature.  I view it in the same light as (e.g.) AI software consistently misidentifying black people as chimpanzees, or Google Calendar permanently storing the wrong date for a friend's birthday because Gmail sees that I sent him an email to wish him a happy birthday and does not see that I sent it the day before the actual birthday.

Quote from: vdeane on December 04, 2019, 01:58:49 PMI can try clearing my cache, but I don't clear cookies because I don't want to lose my auto-logins.

I wouldn't either.  And clearing cookies wouldn't work if browser fingerprinting is driving this.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 05, 2019, 12:00:02 PM
Similarly...  If I check the weather forecast on the Weather Underground website from my phone while travelling, it takes a few weeks upon returning home for my phone to figure out that I want Wichita to once again be my default location rather than the place I was only in for like ten minutes.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 05, 2019, 12:52:27 PM
Quote from: J N Winkler on December 04, 2019, 11:42:10 PM
Quote from: vdeane on December 04, 2019, 01:58:49 PMExcept I was using my former Chromebook while traveling, and this is my desktop.

This definitely sounds like a situation in which browser fingerprinting is involved, since you say the incorrect location is given in both regular and incognito mode.  Here is what I think is going on:

*  Google fingerprints the browser on your Chromebook while you are in Rochester.

*  Back in Albany, Google detects the Chromebook, recognizes the fingerprint, and concludes all browsers connecting through the same "pipe" have a location of Rochester.  This location attribution persists across both normal and incognito mode because it is based on fingerprinting the other devices' browsers.

Fingerprinting works regardless of whether you are in incognito mode--in other words, incognito is not really incognito.
That would be one heck of a fingerprint, because I don't think the "Chromebook" (in actuality, Chrome OS hit end of life over a year ago and I replaced it with Linux) has actually had Chrome launch in Albany in who knows how long.  I do connect it to the network periodically for updates, but not since I traveled.  And since it's only used while traveling, it would have pings from all over (although Rochester most prominently).  Granted, it's a pretty close software mirror of my desktop (although it doesn't have everything the desktop does), and both browsers are signed in to Google to sync bookmarks (and I think Google stealth added a bunch of other sync things without my approval), but still.  I'll have to check Firefox.  In any case, would there be a way to purge this location info from my profile?  I sent feedback to Google, but they'll probably ignore it as usual.

Quote from: kphoger on December 05, 2019, 12:00:02 PM
Similarly...  If I check the weather forecast on the Weather Underground website from my phone while travelling, it takes a few weeks upon returning home for my phone to figure out that I want Wichita to once again be my default location rather than the place I was only in for like ten minutes.
My phone app seems to work OK - I have the location set to "use current location from GPS".  Alas, the widget stopped working with it so I now need to explicitly open the app for more than radar.  On my computer I actually have one of my start pages set to the Weather Underground forecast for Albany.  If I'm in Rochester, I just switch to the bookmark I have set.  Elsewhere, I have to search... I used to be able to do this from the address bar via a custom search engine, but Weather Underground removed the ability to do that it seems.  Now I have to use their own search bar, which is much less convenient for trip planning.

Stuff like this is why I want to be in control of the computer, not have it assume it knows what I want, because it invariably will get it wrong.  I don't understand why tech companies keep insisting on having software assume things and taking away options for user convenience and control.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 05, 2019, 01:10:36 PM
Quote from: vdeane on December 05, 2019, 12:52:27 PM

Quote from: kphoger on December 05, 2019, 12:00:02 PM
Similarly...  If I check the weather forecast on the Weather Underground website from my phone while travelling, it takes a few weeks upon returning home for my phone to figure out that I want Wichita to once again be my default location rather than the place I was only in for like ten minutes.

My phone app seems to work OK - I have the location set to "use current location from GPS".  Alas, the widget stopped working with it so I now need to explicitly open the app for more than radar.  On my computer I actually have one of my start pages set to the Weather Underground forecast for Albany.  If I'm in Rochester, I just switch to the bookmark I have set.  Elsewhere, I have to search... I used to be able to do this from the address bar via a custom search engine, but Weather Underground removed the ability to do that it seems.  Now I have to use their own search bar, which is much less convenient for trip planning.

Stuff like this is why I want to be in control of the computer, not have it assume it knows what I want, because it invariably will get it wrong.  I don't understand why tech companies keep insisting on having software assume things and taking away options for user convenience and control.

I don't use the WU app.  Rather, I go to the mobile version of their website and search by city name.  I also have location turned off on my phone.  After a while of searching for Wichita on the site, it eventually learns to go to the Wichita forecast by default.  Then, when I go on a trip, I'll search for that other location just one time.  Then, when I get back to Wichita, the site defaults to that other location for like two or three weeks, and I have to search for Wichita every time.  I don't understand why it remembers the travel location after only one search, but then it can't learn my home location until a dozen searches later.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on December 08, 2019, 01:20:05 AM
One thing I've noticed recently is that it seems like when you go into street view, you can't view the image date unless you click the button to view past images.

Seems rather dumb.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2019, 03:33:20 AM
Quote from: freebrickproductions on December 08, 2019, 01:20:05 AM
One thing I've noticed recently is that it seems like when you go into street view, you can't view the image date unless you click the button to view past images.

Seems rather dumb.

I just started noticing this about 48 hours ago. Gotta be a bug. It makes no sense.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on December 08, 2019, 09:54:03 AM
Quote from: jakeroot on December 08, 2019, 03:33:20 AM
Quote from: freebrickproductions on December 08, 2019, 01:20:05 AM
One thing I've noticed recently is that it seems like when you go into street view, you can't view the image date unless you click the button to view past images.

Seems rather dumb.

I just started noticing this about 48 hours ago. Gotta be a bug. It makes no sense.

The date still appears all the time in the bottom strip near the right. I don't remember if that was there before or not. Still annoying, though, since I still look first at the button.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 08, 2019, 10:51:31 AM
Quote from: Roadsguy on December 08, 2019, 09:54:03 AM
Quote from: jakeroot on December 08, 2019, 03:33:20 AM
Quote from: freebrickproductions on December 08, 2019, 01:20:05 AM
One thing I've noticed recently is that it seems like when you go into street view, you can't view the image date unless you click the button to view past images.

Seems rather dumb.

I just started noticing this about 48 hours ago. Gotta be a bug. It makes no sense.

The date still appears all the time in the bottom strip near the right. I don't remember if that was there before or not. Still annoying, though, since I still look first at the button.

It was there before. (I still have a window open from before the change.)
Title: Re: Google Maps just fucking SUCKS now
Post by: mgk920 on December 08, 2019, 12:47:47 PM
For at least a month now, when I turn the 'labels' off on the aerial/satellite images, the logos of various sponsored locations are still there, something that is über-annoying and makes it pretty much useless if you are taking screenshots for whatever reason.

:angry:

Mike
Title: Re: Google Maps just fucking SUCKS now
Post by: JoePCool14 on December 08, 2019, 01:49:19 PM
Quote from: 1 on December 08, 2019, 10:51:31 AM
Quote from: Roadsguy on December 08, 2019, 09:54:03 AM
Quote from: jakeroot on December 08, 2019, 03:33:20 AM
Quote from: freebrickproductions on December 08, 2019, 01:20:05 AM
One thing I've noticed recently is that it seems like when you go into street view, you can't view the image date unless you click the button to view past images.

Seems rather dumb.

I just started noticing this about 48 hours ago. Gotta be a bug. It makes no sense.

The date still appears all the time in the bottom strip near the right. I don't remember if that was there before or not. Still annoying, though, since I still look first at the button.

It was there before. (I still have a window open from before the change.)

I also just noticed it. As long as we can see imagery data somewhere, I don't mind. However knowing Google, I feel like it's a matter of time before they remove that too, since of course all modern tech companies hate users actually being able to see data and information.
Title: Re: Google Maps just fucking SUCKS now
Post by: bandit957 on December 09, 2019, 10:49:36 AM
I noticed Google Street View just removed the dates of the photos. Why? Because they can.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on December 09, 2019, 10:52:51 AM
Quote from: bandit957 on December 09, 2019, 10:49:36 AM
I noticed Google Street View just removed the dates of the photos. Why? Because they can.

Still near the bottom-right as it's always been, but I agree it's annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on December 23, 2019, 10:19:25 PM
Recently, I was able to tag an extra parking lot at Sunken Meadow State Park, correct the name of one other parking lot there, and correct the location for George's Lighthouse Café at Montauk Point State Park, but I still can't correct the waterways that are mismarked as part of the Peconic River.


Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on January 25, 2020, 07:32:30 PM
Quote from: D-Dey65 on December 23, 2019, 10:19:25 PM
Recently, I was able to tag an extra parking lot at Sunken Meadow State Park, correct the name of one other parking lot there, and correct the location for George's Lighthouse Café at Montauk Point State Park, but I still can't correct the waterways that are mismarked as part of the Peconic River.
Unfortunately, the correction I made for Parking Lot Number 3 at Sunken Meadow State Park was reverted!

:confused: :angry:
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on January 28, 2020, 06:20:30 PM
I just noticed that Acme Maps has dropped USGS topo maps from their service.  I can get them from other places, but I can't so easily switch between a topo and satellite view.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on January 30, 2020, 07:30:20 PM
Quote from: ErmineNotyours on January 28, 2020, 06:20:30 PM
I just noticed that Acme Maps has dropped USGS topo maps from their service.  I can get them from other places, but I can't so easily switch between a topo and satellite view.

You can do that on Topoview, but not at such close resolution.
Title: Re: Google Maps just fucking SUCKS now
Post by: MikeTheActuary on February 03, 2020, 11:02:12 AM
Someone has "hacked" the traffic on Google maps: https://9to5google.com/2020/02/02/google-maps-hack-virtual-traffic-jam/
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on February 04, 2020, 03:48:43 PM
Anyone else hear notice that satellite imagery on Google Maps is lower res these days?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 04, 2020, 11:06:23 PM
Quote from: TheGrassGuy on February 04, 2020, 03:48:43 PM
Anyone else hear notice that satellite imagery on Google Maps is lower res these days?

Depends on the area.  Lots of imagery in my area is way clearer than it used to be.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 04, 2020, 11:07:15 PM
Quote from: jakeroot on February 04, 2020, 11:06:23 PM
Quote from: TheGrassGuy on February 04, 2020, 03:48:43 PM
Anyone else hear notice that satellite imagery on Google Maps is lower res these days?

Depends on the area.  Lots of imagery in my area is way clearer than it used to be.
Some hasn't been updated in over a decade.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 05, 2020, 12:50:28 AM
Quote from: Rothman on February 04, 2020, 11:07:15 PM
Quote from: jakeroot on February 04, 2020, 11:06:23 PM
Quote from: TheGrassGuy on February 04, 2020, 03:48:43 PM
Anyone else hear notice that satellite imagery on Google Maps is lower res these days?

Depends on the area.  Lots of imagery in my area is way clearer than it used to be.
Some hasn't been updated in over a decade.

yeah, I don't understand how that happens. Parts of the UK have insanely old satellite imagery.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on February 06, 2020, 05:45:25 PM
It appears that Google Maps has changed it's logo, the occasion being the service's fifteenth anniversary.

(https://live.staticflickr.com/65535/49498803696_6a4219f438_o.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 07, 2020, 01:47:27 PM
I don't think that sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 07, 2020, 03:59:29 PM
Quote from: jakeroot on February 05, 2020, 12:50:28 AM
yeah, I don't understand how that happens. Parts of the UK have insanely old satellite imagery.

Until recently the same was true for Teruel, Spain. The A-23 freeway was shown under construction, and in that area it has been open to traffic since October 2005 (not long after Google Maps was launched).
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 07, 2020, 04:19:56 PM
Google Maps thinks there's a Jimmy John's restaurant here (https://goo.gl/maps/x6WKYcqWFvtuEa3u6) in a Mexican town 300 miles south of the border.  I've confirmed with people who live in town that there isn't a Jimmy John's there.  In fact, Jimmy John's doesn't even operate in Mexico at all.  I reported the issue on Google Maps by using the "does not exist" option.  For maybe one day, it was removed from the back, but then it popped back on there.  It's not like someone called the place of business to confirm or looked up their location online or anything, because it doesn't exist.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on February 07, 2020, 04:37:36 PM
Quote from: kphoger on February 07, 2020, 04:19:56 PM
Google Maps thinks there's a Jimmy John's restaurant here (https://goo.gl/maps/x6WKYcqWFvtuEa3u6) in a Mexican town 300 miles south of the border.  I've confirmed with people who live in town that there isn't a Jimmy John's there.  In fact, Jimmy John's doesn't even operate in Mexico at all.  I reported the issue on Google Maps by using the "does not exist" option.  For maybe one day, it was removed from the back, but then it popped back on there.  It's not like someone called the place of business to confirm or looked up their location online or anything, because it doesn't exist.
I reported it. Hopefully that helps.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on February 07, 2020, 09:09:21 PM
Complaint about a sister project, DAE notice in Google Earth it seems that not all the tiles in your view properly load? See snippet below but if I were to zoom into one of the blurry areas, most of the area comes in nice and clean except again for a few tiles which are blurry.
(https://i.imgur.com/tKksFF4.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: MNHighwayMan on February 07, 2020, 09:53:54 PM
Quote from: Mr. Matté on February 07, 2020, 09:09:21 PM
Complaint about a sister project, DAE notice in Google Earth it seems that not all the tiles in your view properly load? See snippet below but if I were to zoom into one of the blurry areas, most of the area comes in nice and clean except again for a few tiles which are blurry.

I've noticed this too. I think their data servers are having issues, since areas which are already in the cache don't have this problem.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 08, 2020, 01:35:21 AM
Quote from: CNGL-Leudimin on February 07, 2020, 03:59:29 PM
Quote from: jakeroot on February 05, 2020, 12:50:28 AM
yeah, I don't understand how that happens. Parts of the UK have insanely old satellite imagery.

Until recently the same was true for Teruel, Spain. The A-23 freeway was shown under construction, and in that area it has been open to traffic since October 2005 (not long after Google Maps was launched).

Wow, you're not kidding. I see a 10 year gap there on Google Earth. In my area, there's a gap between 1990 and 2002, with some pockets of imagery around 1998. At any rate, doing research on parcel history is difficult without those years. Since 2002, I've been seeing fairly regular satellite updates, though current imagery is only at 2018-May.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 08, 2020, 02:01:17 AM
Quote from: MNHighwayMan on February 07, 2020, 09:53:54 PM
Quote from: Mr. Matté on February 07, 2020, 09:09:21 PM
Complaint about a sister project, DAE notice in Google Earth it seems that not all the tiles in your view properly load? See snippet below but if I were to zoom into one of the blurry areas, most of the area comes in nice and clean except again for a few tiles which are blurry.

I've noticed this too. I think their data servers are having issues, since areas which are already in the cache don't have this problem.

Also here to confirm that I see this problem. Right as I'm doing some of the aforementioned (^^^^^^) historic parcel research.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 08, 2020, 03:22:08 PM
This (https://goo.gl/maps/t93ZGwcZSf8b8Hyu7) is not a freeway.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on February 08, 2020, 11:29:21 PM
"Uh, I forgot to take the tarp off the camera when I recorded imagery."

"Don't worry.  We'll post it anyway. (https://goo.gl/maps/Co8cCWM4T9ysccuU8)  No one will notice.

Edit: They've taken down the imagery.  Well, that's no fun.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 09, 2020, 03:32:22 PM
Quote from: ErmineNotyours on February 08, 2020, 11:29:21 PM
"Uh, I forgot to take the tarp off the camera when I recorded imagery."

"Don't worry.  We'll post it anyway. (https://goo.gl/maps/Co8cCWM4T9ysccuU8)  No one will notice.

Ahh yes, that early stuff truly had a lot of mistakes: tilted cameras, night photos, rainy photos, leaves on cameras, sun ruining the shot (overexposure), etc. These things still happen, just a lot less often it seems.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on February 10, 2020, 12:45:01 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?

Yes, Google Maps got a new logo.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 10, 2020, 01:05:53 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?

It did, and what's amazing, at least to me, is that while I noticed the new one right away, I have absolutely no idea what the old one was.
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on February 10, 2020, 02:22:50 PM
Quote from: CtrlAltDel on February 10, 2020, 01:05:53 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?

It did, and what's amazing, at least to me, is that while I noticed the new one right away, I have absolutely no idea what the old one was.

Old vs New logo (https://inshorts.com/en/news/google-reveals-new-logo-for-google-maps-as-it-completes-15-years-of-release-1580992827828)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 10, 2020, 03:37:37 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?

Just a few posts up...

Quote from: ozarkman417 on February 06, 2020, 05:45:25 PM
It appears that Google Maps has changed it's logo, the occasion being the service's fifteenth anniversary.

(https://live.staticflickr.com/65535/49498803696_6a4219f438_o.png)

Quote from: CtrlAltDel on February 10, 2020, 01:05:53 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?

It did, and what's amazing, at least to me, is that while I noticed the new one right away, I have absolutely no idea what the old one was.

I always thought it was too busy, and certainly not memorable. I really like the new logo; a map pin seems completely logical.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on February 10, 2020, 05:53:46 PM
Quote from: CtrlAltDel on February 10, 2020, 01:05:53 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?
It did, and what's amazing, at least to me, is that while I noticed the new one right away, I have absolutely no idea what the old one was.

You know, I did the exact same thing: noticed the new logo, and simultaneously completely blanked on what the old one looked like, despite having looked at it multiple times a day for the past few years.  :pan:

I wonder how long it will be before the Maps app changes as well. At least "busy" is OK for an app icon more so than the corner of a browser tab, so maybe the app icon will remain as-is for now.
Title: Re: Google Maps just fucking SUCKS now
Post by: DaBigE on February 10, 2020, 06:02:12 PM
Quote from: webny99 on February 10, 2020, 05:53:46 PM
Quote from: CtrlAltDel on February 10, 2020, 01:05:53 PM
Quote from: webny99 on February 10, 2020, 12:05:01 PM
Am I seeing things, or did Google Maps get a new logo?
It did, and what's amazing, at least to me, is that while I noticed the new one right away, I have absolutely no idea what the old one was.

You know, I did the exact same thing: noticed the new logo, and simultaneously completely blanked on what the old one looked like, despite having looked at it multiple times a day for the past few years.  :pan:

I wonder how long it will be before the Maps app changes as well. At least "busy" is OK for an app icon more so than the corner of a browser tab, so maybe the app icon will remain as-is for now.

It already has. My app icon changed with the last app update.

I'm hoping they update the 'View in Google Maps' button in Google Earth Pro to the new icon. I find that button and the Save Image to be difficult to remember which is which with how small they are on the screen and being right next to each other.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadsguy on February 12, 2020, 07:09:36 AM
I don't mind the new logo so much, aside from the fact that the Android app icon is now yet another for the "thing on a white circle" series.
Title: Re: Google Maps just fucking SUCKS now
Post by: Dustin DeWinn on February 16, 2020, 01:29:32 PM
My issue with Maps is that it's unreliable. It takes me on bullshit cockamamie routes and I will give 4 recent examples within the past 6 months. Each of these has been independently verified by others.

1) There are 2 Wal-Marts near me, and when I first moved to my new apartment, GMaps didn't know where it was. It brought me to some residential neighborhood about 7 miles in the other direction from where it actually is. Strangely, the Streetview image preview is correct. I rely on my car GPS (hasn't been updated since 2013 bc it's too expensive) to get me there.

When I got lost, I see an old dude walking his dog.

"Excuse me sir. I'm looking for -"
"- Walmart?"
"Yeah, how did you know?"
"You're the third person to ask me today. I don't know where it is."

2) I go to a job interview in an area unfamiliar to me. I'm talking to another applicant I'm competing with and asked if he had a hard time finding the place. He said yeah, and then described the exact route I was promoted to take.

3) I was making an errand towards an area I had never been in, and it took me on 4 cloverleafs all over the place before putting me back on the route I was on. Wasted about 2 miles for nothing.

4) I have it set to AVOID TOLLS and it took me on a toll road and then on an overpass and back the other way where I was before. By the time I realized what was happening it was too late. When I arrived at the place, someone was complaining about the same thing happening to them.

Google Maps is not fun to use anymore, and frankly, I think they know exactly what they're doing.

SIDE NOTE: Voice-to-text has gone from ~80% accuracy to ~20%. The sentence "I am serving chicken and eggs" comes out as "I am certain chicken end eggs"....You slow down. "I AM SER-VING" comes out as "I am Sir Ving"....not kidding you.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 17, 2020, 01:39:03 PM
Quote from: Dustin DeWinn on February 16, 2020, 01:29:32 PM
2) I go to a job interview in an area unfamiliar to me. I'm talking to another applicant I'm competing with and asked if he had a hard time finding the place. He said yeah, and then described the exact route I was promoted to take.

3) I was making an errand towards an area I had never been in, and it took me on 4 cloverleafs all over the place before putting me back on the route I was on. Wasted about 2 miles for nothing.

4) I have it set to AVOID TOLLS and it took me on a toll road and then on an overpass and back the other way where I was before. By the time I realized what was happening it was too late. When I arrived at the place, someone was complaining about the same thing happening to them.

These instances sound like you need to put less blink trust in turn-by-turn sat-nav directions.  I've never put much stock in those being accurate, because they tend to get lane closures and restricted turns a lot–by overestimating usually.  If you're already using Google Maps, then start out by looking at the general route to follow, then you'll know better when it tells you to do some crazy route like what you've described.

Quote from: Dustin DeWinn on February 16, 2020, 01:29:32 PM
Google Maps is not fun to use anymore, and frankly, I think they know exactly what they're doing.

What, exactly, are they doing?

Quote from: Dustin DeWinn on February 16, 2020, 01:29:32 PM
SIDE NOTE: Voice-to-text has gone from ~80% accuracy to ~20%. The sentence "I am serving chicken and eggs" comes out as "I am certain chicken end eggs"....You slow down. "I AM SER-VING" comes out as "I am Sir Ving"....not kidding you.

The first one looks 80% accurate to me:  5 words correct out of 6 total.  The second one looks 100% accurate:  you slowed down enough to make the two syllables come out like two words, and it transcribed that as accurately as possible.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 17, 2020, 02:38:00 PM
Quote from: kphoger on February 17, 2020, 01:39:03 PM
Quote from: Dustin DeWinn on February 16, 2020, 01:29:32 PM
Google Maps is not fun to use anymore, and frankly, I think they know exactly what they're doing.

What, exactly, are they doing?

I'm guessing he's had a few bad experiences, and is sure that Google is just screwing with him at this point.

For the record, I've experienced none of the listed issues (navigation or voice-to-text). Particularly for voice-to-text, it is far more dependent on the individual phone's software than on Google. I use that feature a ton on my Note9, and seldom have it get things wrong. Hell, I can swear into it, and it'll pick things up (none of those dumb asterisks).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 17, 2020, 08:41:18 PM
The voice to text thing sounds like the poster is expecting the computer to know as much about language as a human.  Of course, it doesn't.  A human can tell the difference between "serving" spoken slowly and each syllable emphasized to make it more understandable and "Sir Ving" from context, but the phone knows nothing of that.  Voice to text doesn't know anything about English grammar or what words actually mean, social cues, whether you've gotten exasperated at its inability to comprehend, or anything else - all it's doing is taking sounds and attempting to figure out what words they were.

The directions look like a good example of why a GPS is a supplement to reading maps and navigating, not a replacement.  I don't understand people who rely on it entirely.  That's just asking for trouble.  Such really does cause one's brain to rot, too.  I know someone in his 80s who presumably was able to navigate just fine (heck, he even did photogrammetry in the 60!), but now is wholly reliant on GPS even to drive to and from work.  I went out in the field with him a few times and noticed quite a few times that looking over where we were going with Google Maps beforehand rather than just blindly following the GPS would have avoided issues (as an aside, the number of people who don't bother to look at a map of where they're going before they go places, even those not relying on GPS, is staggering; I feel like I'm at the other end of the extreme, since I don't feel comfortable leaving for a trip without writing out my predetermined (and probably memorized) route on a piece of paper and look at ever single turn in street view if possible).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 18, 2020, 05:09:01 AM
I would guess that the proliferation of phone-based navigation is due in part to at least a few reasons:

1) time savings: just opening your phone and asking for directions to "wherever" is way faster than plotting it beforehand;
2) lack of consistent issues: the chances of running into serious navigational errors is reasonably slim;
3) paper maps generally don't show points-of-interest nor house numbers (house numbers are based on a grid system, but consult reason 1); and
4) digital mapping services are more likely to be up-to-date under the vast majority of circumstances.

I've seen some people experience issues more consistently, but they seem to be one-off situations with their phones, or, in several situations, people using magnetic phone mounts that messed with their internal GPS receiver.

From the perspective of an Uber/Lyft driver, my only complaint is that digital mapping services will sometimes show a POI as being around a corner, when the address is on the first street. This is mainly due to the "pin" for that address being closer to the side street, but I would think a smarter GPS app would just take me to the street that the address is on. But even so, this does not happen all the time, and I still use common sense.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 18, 2020, 12:44:15 PM
Quote from: jakeroot on February 18, 2020, 05:09:01 AM
3) paper maps generally don't show points-of-interest nor house numbers (house numbers are based on a grid system, but consult reason 1); and
4) digital mapping services are more likely to be up-to-date under the vast majority of circumstances.
Of course, there is something in between "rely on the GPS" and "use paper maps".  I do have paper maps of many areas, and I do take them with me on most longer trips, but my primary plotting in through Google Maps over my desktop computer, using the directions mainly to calculate drive time and save the route.  Then again, I seem to be in the minority who still uses a desktop computer and their primary means of going online (which made my FiOS outage yesterday especially annoying).
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 18, 2020, 02:05:37 PM
I use Google Maps to plan my routes but do not own a sat-nav device, nor do I ever use Google Maps on my phone for directions.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 18, 2020, 03:47:48 PM
Quote from: vdeane on February 18, 2020, 12:44:15 PM
Quote from: jakeroot on February 18, 2020, 05:09:01 AM
3) paper maps generally don't show points-of-interest nor house numbers (house numbers are based on a grid system, but consult reason 1); and
4) digital mapping services are more likely to be up-to-date under the vast majority of circumstances.
Of course, there is something in between "rely on the GPS" and "use paper maps".  I do have paper maps of many areas, and I do take them with me on most longer trips, but my primary plotting in through Google Maps over my desktop computer, using the directions mainly to calculate drive time and save the route.  Then again, I seem to be in the minority who still uses a desktop computer and their primary means of going online (which made my FiOS outage yesterday especially annoying).

I think total reliance on GPS is not advisable under any circumstances, as every system is prone to failure (such as incorrect routing). But it helps that we, as roadgeeks, have slightly higher levels of common sense than those that not only drive only because they have to, but don't even really understand roads and routes in general. I, for one, don't even own a recent paper map, but I know most roads in my area, and am happy to use Google Maps or Waze or whatever for when I don't know what I'm doing.

I would guess that the average Joe probably uses phone-based navigation apps, as they don't bring their desktop computer on the road. Even with that, some people don't own printers anymore (given their ridiculous operational costs, depending on model), so they can't print out directions either. Both certainly add up to a predominantly phone-based navigation populace.

Quote from: kphoger on February 18, 2020, 02:05:37 PM
I use Google Maps to plan my routes but do not own a sat-nav device, nor do I ever use Google Maps on my phone for directions.

As I understand it, you run a program that entails a great deal of driving. So I'm guessing you've found something that works. But I think the average person would find using Google Maps on the computer, but never using it on their phone, to be a bit unusual. Since, after all, it's the same map. I personally use Waze for navigation pretty frequently. I've beat it on several occasions, but it's usually pretty spot-on for arrival time (seldom ever under-estimates, though I've seen ETA's change mid-drive). As someone who knows routes pretty well, ETA's are something that I really appreciate out of sat-nav devices.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on February 18, 2020, 03:56:58 PM
I use StreetView heavily to check parking availability and the streetscape in situations that I expect to involve significant task loading, such as hunting for a specific address on a busy five-lane thoroughfare.  Aside from that, I just look for an overview from Google Maps.

I have found it helps to have relaxed standards for distance parked from the place being visited.  When the location is unfamiliar or only semi-familiar (say, visited once every year or so), it is easier for me to park on a street nearby than to scrounge for a space in off-street parking, even if the latter is a little bit closer to the front door.  Quite often I offer dropoff and pickup at the door just to ensure I can handle the parking without an observer riding in the car with me.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on February 18, 2020, 04:06:34 PM
Quote from: jakeroot on February 18, 2020, 03:47:48 PM
I think total reliance on GPS is not advisable under any circumstances, as every system is prone to failure (such as incorrect routing). [...]
https://en.wikipedia.org/wiki/Death_by_GPS
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 18, 2020, 04:19:21 PM
Quote from: jakeroot on February 18, 2020, 03:47:48 PM

Quote from: kphoger on February 18, 2020, 02:05:37 PM
I use Google Maps to plan my routes but do not own a sat-nav device, nor do I ever use Google Maps on my phone for directions.

As I understand it, you run a program that entails a great deal of driving. So I'm guessing you've found something that works. But I think the average person would find using Google Maps on the computer, but never using it on their phone, to be a bit unusual. Since, after all, it's the same map. I personally use Waze for navigation pretty frequently. I've beat it on several occasions, but it's usually pretty spot-on for arrival time (seldom ever under-estimates, though I've seen ETA's change mid-drive). As someone who knows routes pretty well, ETA's are something that I really appreciate out of sat-nav devices.

I should have worded that more carefully.  I never have Google Maps on my phone give me directions.  I do use Google Maps on my phone while out and about, but only to look at the map itself while stopped somewhere.  I figure out on my own how to get from A to B on that map.  It's only in advance of travel, from the comfort of my home computer, that I utilize the directions feature of Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on February 22, 2020, 09:26:55 PM
For some, South Korea specifically looks blurry and has a different colour scheme (looks like old Google Maps?). Even zooming in on South Korea, the map still looks low resolution. My brother sees the same thing (we're both using google.ca/maps in case that affects anything).
(https://i.imgur.com/G55R5z4.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 22, 2020, 09:52:09 PM
Japan does that too, but it's not as obvious because it isn't quite as low resolution and it look/functions more like Google Maps elsewhere (the terrain view of North Korea is also affected within the rectangle with the dark blue water).  I think it's because of some security laws relating to mapping in the area; it seems like all the countries in that area have them in some form (it would be ironic if North Korea was the exception, but I suspect Google just doesn't care in their case).
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on February 22, 2020, 09:55:32 PM
Quote from: 7/8 on February 22, 2020, 09:26:55 PM
For some, South Korea specifically looks blurry and has a different colour scheme (looks like old Google Maps?). Even zooming in on South Korea, the map still looks low resolution. My brother sees the same thing (we're both using google.ca/maps in case that affects anything).
<snipped>
It's not specific to .ca. I started to notice it around the 2018 winter Olympics, but it has probably been there longer than that. Tried .de, .fr, and for some reason, there is no google.kr (South Korea's domain).
https://nationalinterest.org/blog/the-buzz/one-thing-north-korea-has-the-south-doesnt-google-maps-24650 (https://nationalinterest.org/blog/the-buzz/one-thing-north-korea-has-the-south-doesnt-google-maps-24650)
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on February 22, 2020, 10:07:45 PM
(https://live.staticflickr.com/65535/49571527068_a995eb9f79.jpg)

I feel indifferent about this... Took me a couple of taps to figure out why it was doing nothing.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on February 22, 2020, 10:13:15 PM
Quote from: ozarkman417 on February 22, 2020, 09:55:32 PM
Quote from: 7/8 on February 22, 2020, 09:26:55 PM
For some, South Korea specifically looks blurry and has a different colour scheme (looks like old Google Maps?). Even zooming in on South Korea, the map still looks low resolution. My brother sees the same thing (we're both using google.ca/maps in case that affects anything).
<snipped>
It's not specific to .ca. I started to notice it around the 2018 winter Olympics, but it has probably been there longer than that. Tried .de, .fr, and for some reason, there is no google.kr (South Korea's domain).
https://nationalinterest.org/blog/the-buzz/one-thing-north-korea-has-the-south-doesnt-google-maps-24650 (https://nationalinterest.org/blog/the-buzz/one-thing-north-korea-has-the-south-doesnt-google-maps-24650)

Thanks for the info, that's very intesting!

Quote from: vdeane on February 22, 2020, 09:52:09 PM
Japan does that too, but it's not as obvious because it isn't quite as low resolution and it look/functions more like Google Maps elsewhere (the terrain view of North Korea is also affected within the rectangle with the dark blue water).  I think it's because of some security laws relating to mapping in the area; it seems like all the countries in that area have them in some form (it would be ironic if North Korea was the exception, but I suspect Google just doesn't care in their case).

Personally I don't notice anything unusual with Japan, but maybe it's too subtle for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 22, 2020, 10:44:53 PM
Japan's changes are MUCH more subtle than those of South Korea (the latter is about as subtle as being hit over the head with a sledgehammer).  Main differences between Japan and most of the rest of the world is the lack of borders on the freeway symbology, the ramps change colors to match the freeways at sufficiently close zoom levels, and traffic lights are shown.  Interchanges and toll gates are also marked with names at much further out than exit numbers are shown elsewhere.  Transit lines are also shown (albeit usually in black and white) at all times, not just when the transit layer is turned on (which simply turns them to color).
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on February 22, 2020, 11:20:00 PM
In general, if you are in serious need of maps for another developed non-Anglo country you are better off using one of the native providers. South Korea has Naver, and China has Baidu (which gets around the annoying discrepancy between satellite and road data imposed by the GPS fudging).
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 23, 2020, 05:14:17 AM
Quote from: 7/8 on February 22, 2020, 09:26:55 PM
For some, South Korea specifically looks blurry and has a different colour scheme (looks like old Google Maps?). Even zooming in on South Korea, the map still looks low resolution. My brother sees the same thing (we're both using google.ca/maps in case that affects anything).

Same in .es. It's a superimposed old map, because if you switch to satellite view you'll see there are no marked roads at all. This also explains why directions don't work (How you can get anywhere if there are no roads to begin with?), and Street View doesn't show any address at all, just who has taken the imagery (Mr. Google, who not...).
Title: Re: Google Maps just fucking SUCKS now
Post by: Verlanka on February 23, 2020, 05:22:37 AM
Quote from: ozarkman417 on February 22, 2020, 10:07:45 PM
(https://live.staticflickr.com/65535/49571527068_a995eb9f79.jpg)

I feel indifferent about this... Took me a couple of taps to figure out why it was doing nothing.
After looking at the picture, the only takeaway from it is that only the interstate has traffic.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on February 23, 2020, 10:43:29 AM
Quote from: Verlanka on February 23, 2020, 05:22:37 AM
Quote from: ozarkman417 on February 22, 2020, 10:07:45 PM
<snipped>
I feel indifferent about this... Took me a couple of taps to figure out why it was doing nothing.
After looking at the picture, the only takeaway from it is that only the interstate has traffic.
They are phasing out the three dashes on the left side of the search bar and putting its former contents in different places.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 23, 2020, 03:08:16 PM
Quote from: vdeane on February 22, 2020, 10:44:53 PM
Japan's changes are MUCH more subtle than those of South Korea (the latter is about as subtle as being hit over the head with a sledgehammer).  Main differences between Japan and most of the rest of the world is the lack of borders on the freeway symbology, the ramps change colors to match the freeways at sufficiently close zoom levels, and traffic lights are shown.  Interchanges and toll gates are also marked with names at much further out than exit numbers are shown elsewhere.  Transit lines are also shown (albeit usually in black and white) at all times, not just when the transit layer is turned on (which simply turns them to color).

Japan's map symbology is very interesting, and I've never quite understood why their rendering is so unique. It's definitely nice to see street widths closer to reality, colors that don't overlap as much, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on February 23, 2020, 07:18:01 PM
Quote from: jakeroot on February 23, 2020, 03:08:16 PM
Quote from: vdeane on February 22, 2020, 10:44:53 PM
Japan's changes are MUCH more subtle than those of South Korea (the latter is about as subtle as being hit over the head with a sledgehammer).  Main differences between Japan and most of the rest of the world is the lack of borders on the freeway symbology, the ramps change colors to match the freeways at sufficiently close zoom levels, and traffic lights are shown.  Interchanges and toll gates are also marked with names at much further out than exit numbers are shown elsewhere.  Transit lines are also shown (albeit usually in black and white) at all times, not just when the transit layer is turned on (which simply turns them to color).

Japan's map symbology is very interesting, and I've never quite understood why their rendering is so unique. It's definitely nice to see street widths closer to reality, colors that don't overlap as much, etc.

Google bought out a Japanese firm and superimposed their existing maps since they were much more comprehensive. This firm managed to get the right formula for displaying complex underground maps (a necessity with their subway-level malls), which regular Google Maps still struggles to support.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 24, 2020, 03:20:55 AM
Quote from: Bruce on February 23, 2020, 07:18:01 PM
Quote from: jakeroot on February 23, 2020, 03:08:16 PM
Quote from: vdeane on February 22, 2020, 10:44:53 PM
Japan's changes are MUCH more subtle than those of South Korea (the latter is about as subtle as being hit over the head with a sledgehammer).  Main differences between Japan and most of the rest of the world is the lack of borders on the freeway symbology, the ramps change colors to match the freeways at sufficiently close zoom levels, and traffic lights are shown.  Interchanges and toll gates are also marked with names at much further out than exit numbers are shown elsewhere.  Transit lines are also shown (albeit usually in black and white) at all times, not just when the transit layer is turned on (which simply turns them to color).

Japan's map symbology is very interesting, and I've never quite understood why their rendering is so unique. It's definitely nice to see street widths closer to reality, colors that don't overlap as much, etc.

Google bought out a Japanese firm and superimposed their existing maps since they were much more comprehensive. This firm managed to get the right formula for displaying complex underground maps (a necessity with their subway-level malls), which regular Google Maps still struggles to support.

Guess that would explain the copyright notice in Google Earth! Thanks for the information.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on February 26, 2020, 02:47:33 PM
I just noticed a change that makes it suck a little less.  When downloading maps for offline use, the maps will expire if not updated.  Previously, the time limit was 30 days, which seems a little excessive.  The real problem is that even if you set it to update automatically, it will save space and data by updating only maps that are used frequently.  That means that if you save some maps and set them to update automatically, if you don't do it manually, they might just disappear because Google decided that they're not important.  I downloaded a new map area yesterday, and it has an expiration date of a year later.  I updated my existing offline maps and they all now expire in a year.  It's understandable that they don't want to have their reputation tarnished by people using outdated 15-year-old maps and complaining that they aren't accurate, but having to update every 30 days is too much.  They should still let me decide if maps are important enough to keep past their expiration date.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on March 08, 2020, 02:05:05 PM
Does anyone know why in China the road markers are consistently hundreds of feet off from the actual road? Is this done on purpose?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on March 08, 2020, 02:38:58 PM
Quote from: Plutonic Panda on March 08, 2020, 02:05:05 PM
Does anyone know why in China the road markers are consistently hundreds of feet off from the actual road? Is this done on purpose?

China requires it to be that way by law.
Title: Re: Google Maps just fucking SUCKS now
Post by: Brandon on March 08, 2020, 04:59:44 PM
Quote from: Bruce on February 23, 2020, 07:18:01 PM
Quote from: jakeroot on February 23, 2020, 03:08:16 PM
Quote from: vdeane on February 22, 2020, 10:44:53 PM
Japan's changes are MUCH more subtle than those of South Korea (the latter is about as subtle as being hit over the head with a sledgehammer).  Main differences between Japan and most of the rest of the world is the lack of borders on the freeway symbology, the ramps change colors to match the freeways at sufficiently close zoom levels, and traffic lights are shown.  Interchanges and toll gates are also marked with names at much further out than exit numbers are shown elsewhere.  Transit lines are also shown (albeit usually in black and white) at all times, not just when the transit layer is turned on (which simply turns them to color).

Japan's map symbology is very interesting, and I've never quite understood why their rendering is so unique. It's definitely nice to see street widths closer to reality, colors that don't overlap as much, etc.

Google bought out a Japanese firm and superimposed their existing maps since they were much more comprehensive. This firm managed to get the right formula for displaying complex underground maps (a necessity with their subway-level malls), which regular Google Maps still struggles to support.

They need to borrow that for the multi-level street system of downtown Chicago.  It's a crapshoot as to whether one lands on Upper, Middle, or Lower Wacker Drive with the street view thingy.
Title: Re: Google Maps just fucking SUCKS now
Post by: stevashe on March 09, 2020, 02:40:54 PM
Quote from: 1 on March 08, 2020, 02:38:58 PM
Quote from: Plutonic Panda on March 08, 2020, 02:05:05 PM
Does anyone know why in China the road markers are consistently hundreds of feet off from the actual road? Is this done on purpose?

China requires it to be that way by law.

If you go to google.cn then the satellite imagery shown will match up properly with the map data, though this is just the satellite being moved to match up with the map data that's off, again because of said law, so the coordinates are still incorrect.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on March 11, 2020, 12:13:56 PM
Quote from: Brandon on March 08, 2020, 04:59:44 PM
They need to borrow that for the multi-level street system of downtown Chicago.  It's a crapshoot as to whether one lands on Upper, Middle, or Lower Wacker Drive with the street view thingy.
Too true
Title: Re: Google Maps just fucking SUCKS now
Post by: cpzilliacus on March 11, 2020, 01:45:56 PM
Washington Post: What happens when Google Maps gets it wrong (https://www.washingtonpost.com/opinions/what-happens-when-google-loses-your-address-you-cease-to-exist/2020/03/09/b1885f28-622c-11ea-b3fc-7841686c5c57_story.html)

QuoteTwo and a half years ago, my dad and his wife took an Uber from the airport to my house in Washington, D.C., as they've done many times before. Only this time, it took them to the wrong place: an empty lot by a cemetery, two miles from my house. My dad told the Uber driver it was not my house, but the driver didn't believe him. His app had led him here, so it must be right!

QuoteThey all sat there for a few minutes, staring at the driver's phone, paralyzed by the startling gap that had opened between the app and reality.

QuoteThis is how we discovered that Google Maps had two locations listed for our home. One was right, one was wrong. This seemed like a pretty minor problem in the scheme of things, and it was. For a while, I even thought it was kind of wonderful. We could be anonymous! Even Google didn't know where we lived!

QuoteBut over time, as Google Maps got embedded in more and more apps, the problem worsened. Google Maps is used by Uber, Instacart, Lyft, Door Dash and even something called the Zombie Outbreak Simulator.

QuoteThe second-most-popular maps app in the United States is Waze. Guess who owns Waze? Google Maps again! Soon Waze had our address wrong, too. Eventually, almost everyone who tried to find our house was directed to the wrong place.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 04, 2020, 12:38:02 AM
So, the latest Street View on I-290 in the Chicago area near where I grew up is this:

(https://i.imgur.com/Ea1ic7s.png)

And if you go there (https://www.google.com/maps/@41.8854821,-87.9204051,3a,75y,323.8h,15.18t/data=!3m7!1e1!3m5!1su91Okgrw2FWPk_Hbj6u9rg!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3Du91Okgrw2FWPk_Hbj6u9rg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D104.932945%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192), it's pretty messed up.

This is bad enough, but for whatever reason, they've taken away access to earlier Street Views, so there's no way to see the road. Worse, I've noticed this elsewhere, most notably the newer sections of I-69 in Indiana north of Bloomington.

This is unfortunate, since looking at the older images, even if they had a lower resolution, often showed unique details as well as the change in the road over time.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 04, 2020, 12:49:56 AM
Quote from: CtrlAltDel on April 04, 2020, 12:38:02 AM
This is bad enough, but for whatever reason, they've taken away access to earlier Street Views, so there's no way to see the road. Worse, I've noticed this elsewhere, most notably the newer sections of I-69 in Indiana north of Bloomington.

This is unfortunate, since looking at the older images, even if they had a lower resolution, often showed unique details as well as the change in the road over time.

The access to older imagery seems to disappear if the Street View path doesn't perfectly align with older imagery. Since this imagery is all screwed up, the path got screwed up so GMaps thinks it new, without any older imagery attached to it. At least, that's how I'm interpreting the situation; notice that the floating arrow (that allows you to click around) is basically floating on top of the car? That's obviously not right, and definitely an indication that the path is screwed up.

If you click onto the southbound carriageway, go back in historic imagery, and then click back to the northbound carriageway, it'll get you back onto the correct alignment (https://goo.gl/maps/dwun6HDEJJNmtFCt6) and you can go back to seeing the old set of images. Kind of an annoying workaround, but it's not my first rodeo with bullshit like this unfortunately.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 04, 2020, 01:57:38 AM
Quote from: jakeroot on April 04, 2020, 12:49:56 AM
The access to older imagery seems to disappear if the Street View path doesn't perfectly align with older imagery. Since this imagery is all screwed up, the path got screwed up so GMaps thinks it new, without any older imagery attached to it.

I do believe you are right. I was vaguely aware of all the things you mention, but I never put the pieces together. It makes me want to check out that section of I-69 (https://www.google.com/maps/@39.3762312,-86.4767887,3a,75y,229.27h,86.22t/data=!3m6!1e1!3m4!1sNA4MDLjB7ahkrCQYHPWptA!2e0!7i16384!8i8192) I brought up.

ETA: It worked (https://www.google.com/maps/@39.3761508,-86.4764473,3a,75y,64.97h,88.2t/data=!3m6!1e1!3m4!1s8QvjsoW-dlDP9KcTePWaZw!2e0!7i13312!8i6656).
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on April 04, 2020, 10:03:48 AM
One thing to file under "mildly annoying" : the distance measuring tool now measures in km.
Title: Re: Google Maps just fucking SUCKS now
Post by: Revive 755 on April 04, 2020, 01:08:54 PM
I see Google Maps has started showing toll plazas for the Illinois tollways.  However they got a couple of the plazas types wrong at the I-90/Roselle Road interchange. (https://goo.gl/maps/Zq1LinsfDkeMUPsV7).  The eastbound entrance has a self service lane (https://goo.gl/maps/bLgU6sWrBnSnHfCy8) (which there is probably a better view available of, but Streetview keeps dumping me onto mainline I-90), and the westbound entrance from Central Road is I-Pass/EZ Pass only (https://goo.gl/maps/xgvudzXNhjpbETmG8).

They are also missing a couple plazas at the I-90/Barrington Road interchange (https://goo.gl/maps/7otWVMdUw2qPJwpk6) - every ramp at that interchange has a plaza, but the ramps on the west side are I-Pass only.

(Although right now they should be showing all the toll plazas as I-Pass only due to Covid-19.)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 04, 2020, 02:36:53 PM
Quote from: CtrlAltDel on April 04, 2020, 01:57:38 AM
Quote from: jakeroot on April 04, 2020, 12:49:56 AM
The access to older imagery seems to disappear if the Street View path doesn't perfectly align with older imagery. Since this imagery is all screwed up, the path got screwed up so GMaps thinks it new, without any older imagery attached to it.

I do believe you are right. I was vaguely aware of all the things you mention, but I never put the pieces together. It makes me want to check out that section of I-69 (https://www.google.com/maps/@39.3762312,-86.4767887,3a,75y,229.27h,86.22t/data=!3m6!1e1!3m4!1sNA4MDLjB7ahkrCQYHPWptA!2e0!7i16384!8i8192) I brought up.

ETA: It worked (https://www.google.com/maps/@39.3761508,-86.4764473,3a,75y,64.97h,88.2t/data=!3m6!1e1!3m4!1s8QvjsoW-dlDP9KcTePWaZw!2e0!7i13312!8i6656).

It's a trick that I've used off-and-on especially along arterial roads. I really wish Google would do a better job of consolidating their paths, since it shouldn't be necessary to trick the program just to get to a path that was very recently the only path.

Quote from: US 89 on April 04, 2020, 10:03:48 AM
One thing to file under "mildly annoying" : the distance measuring tool now measures in km.

I'm still seeing miles, but see KM when in Canada. Anything unusual about your URL or location?
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on April 04, 2020, 06:09:20 PM
Quote from: jakeroot on April 04, 2020, 02:36:53 PM
Quote from: US 89 on April 04, 2020, 10:03:48 AM
One thing to file under "mildly annoying" : the distance measuring tool now measures in km.
I'm still seeing miles, but see KM when in Canada.

Same here. The actual "ruler" shows miles only, while the pop up box gives you the total distance in both miles and km.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on April 04, 2020, 07:31:36 PM
It appears that Google is now telling us if carryout is available at a given restaurant, and is finally telling us which businesses are closed due to COVID-19 (most of them, anyway).
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 04, 2020, 09:49:04 PM
Quote from: webny99 on April 04, 2020, 06:09:20 PM
Quote from: jakeroot on April 04, 2020, 02:36:53 PM
Quote from: US 89 on April 04, 2020, 10:03:48 AM
One thing to file under "mildly annoying" : the distance measuring tool now measures in km.
I'm still seeing miles, but see KM when in Canada.
Same here. The actual "ruler" shows miles only, while the pop up box gives you the total distance in both miles and km.

For me, the ruler itself is in metric, even if the box shows both. Behold:

(https://i.imgur.com/IMsYRuK.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 04, 2020, 10:23:01 PM
Quote from: jakeroot on April 04, 2020, 12:49:56 AM
Quote from: CtrlAltDel on April 04, 2020, 12:38:02 AM
This is bad enough, but for whatever reason, they've taken away access to earlier Street Views, so there's no way to see the road. Worse, I've noticed this elsewhere, most notably the newer sections of I-69 in Indiana north of Bloomington.

This is unfortunate, since looking at the older images, even if they had a lower resolution, often showed unique details as well as the change in the road over time.

The access to older imagery seems to disappear if the Street View path doesn't perfectly align with older imagery. Since this imagery is all screwed up, the path got screwed up so GMaps thinks it new, without any older imagery attached to it. At least, that's how I'm interpreting the situation; notice that the floating arrow (that allows you to click around) is basically floating on top of the car? That's obviously not right, and definitely an indication that the path is screwed up.

If you click onto the southbound carriageway, go back in historic imagery, and then click back to the northbound carriageway, it'll get you back onto the correct alignment (https://goo.gl/maps/dwun6HDEJJNmtFCt6) and you can go back to seeing the old set of images. Kind of an annoying workaround, but it's not my first rodeo with bullshit like this unfortunately.
Annoying as it is, the current system does have one advantage: the ability to browse old alignments (https://www.google.com/maps/@45.4968561,-73.5578633,3a,61.4y,297.41h,91.89t/data=!3m6!1e1!3m4!1sRn0fs6fwIVvzCF9GEVlkSw!2e0!7i13312!8i6656) in some instances.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 05, 2020, 01:05:29 AM
Quote from: vdeane on April 04, 2020, 10:23:01 PM
Quote from: jakeroot on April 04, 2020, 12:49:56 AM
Quote from: CtrlAltDel on April 04, 2020, 12:38:02 AM
This is bad enough, but for whatever reason, they've taken away access to earlier Street Views, so there's no way to see the road. Worse, I've noticed this elsewhere, most notably the newer sections of I-69 in Indiana north of Bloomington.

This is unfortunate, since looking at the older images, even if they had a lower resolution, often showed unique details as well as the change in the road over time.

The access to older imagery seems to disappear if the Street View path doesn't perfectly align with older imagery. Since this imagery is all screwed up, the path got screwed up so GMaps thinks it new, without any older imagery attached to it. At least, that's how I'm interpreting the situation; notice that the floating arrow (that allows you to click around) is basically floating on top of the car? That's obviously not right, and definitely an indication that the path is screwed up.

If you click onto the southbound carriageway, go back in historic imagery, and then click back to the northbound carriageway, it'll get you back onto the correct alignment (https://goo.gl/maps/dwun6HDEJJNmtFCt6) and you can go back to seeing the old set of images. Kind of an annoying workaround, but it's not my first rodeo with bullshit like this unfortunately.
Annoying as it is, the current system does have one advantage: the ability to browse old alignments (https://www.google.com/maps/@45.4968561,-73.5578633,3a,61.4y,297.41h,91.89t/data=!3m6!1e1!3m4!1sRn0fs6fwIVvzCF9GEVlkSw!2e0!7i13312!8i6656) in some instances.

Yeah, true. I didn't mean to imply that access to those old alignment should disappear, but where roads exist now and have existed for some time, there's no reason to have several almost-identical paths along that road. Obviously paths should stick around for old roads, even if they don't remain visible on the blue street view map.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 05, 2020, 01:08:44 AM
Quote from: CtrlAltDel on April 04, 2020, 09:49:04 PM
Quote from: webny99 on April 04, 2020, 06:09:20 PM
Quote from: jakeroot on April 04, 2020, 02:36:53 PM
Quote from: US 89 on April 04, 2020, 10:03:48 AM
One thing to file under "mildly annoying" : the distance measuring tool now measures in km.
I'm still seeing miles, but see KM when in Canada.
Same here. The actual "ruler" shows miles only, while the pop up box gives you the total distance in both miles and km.

For me, the ruler itself is in metric, even if the box shows both. Behold:

(https://i.imgur.com/IMsYRuK.png)

I'm still seeing imperial. Odd:

(https://i.imgur.com/rkeKFGw.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 05, 2020, 01:53:52 AM
Quote from: jakeroot on April 05, 2020, 01:08:44 AM
(https://i.imgur.com/rkeKFGw.png)

Kudos for finding the same spot. It has personal meaning since the dealership to the east is where my car was towed when my alternator broke when I was on my way to Florida a few weeks ago, and the hotel to the west is where I stayed while waiting for them to open, since the car broke down at about 1 in the morning. The night clerk at the hotel was quite surprised at the random person getting dropped off by a giant tow truck in the middle of the night.
Title: Re: Google Maps just fucking SUCKS now
Post by: ftballfan on April 05, 2020, 11:01:52 AM
Quote from: CtrlAltDel on April 05, 2020, 01:53:52 AM
Quote from: jakeroot on April 05, 2020, 01:08:44 AM
(https://i.imgur.com/rkeKFGw.png)

Kudos for finding the same spot. It has personal meaning since the dealership to the east is where my car was towed when my alternator broke when I was on my way to Florida a few weeks ago, and the hotel to the west is where I stayed while waiting for them to open, since the car broke down at about 1 in the morning. The night clerk at the hotel was quite surprised at the random person getting dropped off by a giant tow truck in the middle of the night.
Speaking of alternators breaking, about 10 years ago my family was on our way back to Michigan from Florida when the alternator broke in the family SUV just past the Adcock Rd overpass (just south of exit 55) and we had to get towed to a garage on 2nd St east of downtown. Luckily, it was just before close when we got there, so they were able to fix it and get us back on the road that evening.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on April 05, 2020, 11:55:12 AM
Some places, Google needs to update their satellite imagery. Here an sample of Apple maps showing an aera of Rock Forest, now amalgated to Sherbrooke then I was able to see via https://satellites.pro/Canada_map#45.381437,-71.981778,15  Now, compare it to Google satellite view. Satellite Pro allow to switch from Apple maps to Google maps minus Streetview and Ersi but it would had been more cool if they have Bing maps as well.

Edit: Looks like Satellite. pro automatically switch to Google maps when we're on Windows.  :angry: Well we got to use Apple Maps via DuckDuckGo.com https://duckduckgo.com/?q=Sherbrooke%2C+QC%2C+Canada&t=h_&ia=web&iaxm=maps&strict_bbox=0&bbox=45.43616763855972%2C-72.00765613361817%2C45.37958549108413%2C-71.8771934871338&metatoken=0

Edit #2: If Apple decide to allow directly Windows 10 users to use Apple Maps, that would be a big wake-up call for Google Maps but that's another story. :spin:
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 05, 2020, 12:20:57 PM
Quote from: ftballfan on April 05, 2020, 11:01:52 AM
Speaking of alternators breaking, about 10 years ago my family was on our way back to Michigan from Florida when the alternator broke in the family SUV just past the Adcock Rd overpass (just south of exit 55) and we had to get towed to a garage on 2nd St east of downtown. Luckily, it was just before close when we got there, so they were able to fix it and get us back on the road that evening.

Amazing. That's almost exactly the same place my alternator died, just after the Magnolia Plantation. I used what little battery power I had to make it to the next exit, ending up at the Chevron at exit 49, which is where I called for a tow truck.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on April 07, 2020, 12:33:27 AM
Quote from: jakeroot on April 05, 2020, 01:08:44 AM
Quote from: CtrlAltDel on April 04, 2020, 09:49:04 PM
Quote from: webny99 on April 04, 2020, 06:09:20 PM
Quote from: jakeroot on April 04, 2020, 02:36:53 PM
Quote from: US 89 on April 04, 2020, 10:03:48 AM
One thing to file under “mildly annoying”: the distance measuring tool now measures in km.
I'm still seeing miles, but see KM when in Canada.
Same here. The actual "ruler" shows miles only, while the pop up box gives you the total distance in both miles and km.
For me, the ruler itself is in metric, even if the box shows both. Behold:
I'm still seeing imperial. Odd:

Apparently if you click the scale in the bottom right of Google Maps, it toggles between customary and metric units. I could believe I might have done that on accident, but the really weird part is that Google Earth also decided to switch to metric. Before tonight, I hadn't opened that up in at least a month. Must have been some weird Google update that came to just a few of us.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 07, 2020, 12:54:03 PM
Quote from: US 89 on April 07, 2020, 12:33:27 AM
Apparently if you click the scale in the bottom right of Google Maps, it toggles between customary and metric units. I could believe I might have done that on accident, but the really weird part is that Google Earth also decided to switch to metric. Before tonight, I hadn't opened that up in at least a month. Must have been some weird Google update that came to just a few of us.
Good to know.  I've been using the measurement tool when upgrading my website's photo gallery and was wondering how to get the ruler to show metric for when I get around to tagging my photos from Canada.
Title: Re: Google Maps just fucking SUCKS now
Post by: sbeaver44 on April 18, 2020, 05:08:53 PM
Seeing this in several places in the Android App....arrows pointing the wrong way on divided highways without access control

Here in Ohio
US 11 in Virginia
US 278 on Hilton Head Island
US 23 in Kentucky

Oddly enough limited access highways seem fine, except I noticed one of the ramps in the 81/581 interchange near Roanoke is backwards.(https://uploads.tapatalk-cdn.com/20200418/eb76c4a335f9cb82f5f3137b186f784d.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 05, 2020, 09:54:35 PM
I've noticed that some businesses now have square markers.  Here (https://www.google.com/maps/@39.2787064,-76.8093983,15.38z) are a couple of examples.  Any idea what the square is for?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 05, 2020, 09:56:28 PM
Quote from: vdeane on May 05, 2020, 09:54:35 PM
I've noticed that some businesses now have square markers.  Here (https://www.google.com/maps/@39.2787064,-76.8093983,15.38z) are a couple of examples.  Any idea what the square is for?

They're not square on my screen.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 05, 2020, 10:26:07 PM
Quote from: 1 on May 05, 2020, 09:56:28 PM
Quote from: vdeane on May 05, 2020, 09:54:35 PM
I've noticed that some businesses now have square markers.  Here (https://www.google.com/maps/@39.2787064,-76.8093983,15.38z) are a couple of examples.  Any idea what the square is for?

They're not square on my screen.

Seconded. Just a bunch of pins.

Try a screenshot, vdeane.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on May 05, 2020, 10:27:59 PM
Garden State Parkway is showing again as NJ 444.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on May 06, 2020, 01:08:19 AM
My latest complaint about Google Maps is that after a little while of scrolling around and jumping in and out of Streetview (from the "Lite" version of the maps site) the GSV pegman eventually stops functioning for no apparent reason.  I can see the highlighted GSV streets but the pegman just jumps right back to his spot on the corner of the screen and GSV won't open.  The only way to get it to work again from that same location is to reload the page which always gives me the "I'm not a robot" checkbox page and usually Google's fun little game of having to select the boxes with the traffic lights, clouds, cars, or whatever else it throws at me to prove I'm an actual human.  Google seems to think that scrolling around randomly looking at stuff is for bots trying to hack their system.

I'm concerned that eventually they're going to ask me to identify the specific model of the traffic lights shown in the images and then I'm going to have to spend all my time asking people here just to use Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 06, 2020, 12:22:34 PM
Quote from: sbeaver44 on April 18, 2020, 05:08:53 PM
Seeing this in several places in the Android App....arrows pointing the wrong way on divided highways without access control

I noticed this on the desktop version somewhere just recently.

In the past, stuff like that was indicative of road construction, with one roadway completely closed and the other carrying both directions of traffic.  But I don't think that's necessarily what's going on with these new cases.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 06, 2020, 01:09:53 PM
Quote from: jakeroot on May 05, 2020, 10:26:07 PM
Quote from: 1 on May 05, 2020, 09:56:28 PM
Quote from: vdeane on May 05, 2020, 09:54:35 PM
I've noticed that some businesses now have square markers.  Here (https://www.google.com/maps/@39.2787064,-76.8093983,15.38z) are a couple of examples.  Any idea what the square is for?

They're not square on my screen.

Seconded. Just a bunch of pins.

Try a screenshot, vdeane.
I happened to mouse over a few after I posted this last night, and I figured out what they all have in common: they're ads!  I guess Google is no longer using the "larger marker with the business logo" paradigm any more.
Title: Re: Google Maps just fucking SUCKS now
Post by: NWI_Irish96 on May 06, 2020, 01:34:21 PM
Anybody have any idea why so many state boundaries are off, sometimes by quite a bit?

Example 1: https://www.google.com/maps/@41.5740327,-87.5255677,146m/data=!3m1!1e3

This is a few hundred feet from my house.  The actual state boundary is in the median of State Line Rd.  The boundary marked on the map is in the NB lane.  Off by only a few feet, but off nonetheless.

Example 2: https://www.google.com/maps/@41.5253767,-87.5254971,123m/data=!3m1!1e3

This is a few miles to the south.  The actual state boundary is along the fenceline that the shed of the house with the pool backs up to.  The boundary marked on the map is through everybody's front yards.  Much more significant different. 

I am not an expert on mapping technology but it seems like it shouldn't be hard to at least be more accurate than Example 2, if not Example 1.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 06, 2020, 01:57:50 PM
Quote from: cabiness42 on May 06, 2020, 01:34:21 PM
Anybody have any idea why so many state boundaries are off, sometimes by quite a bit?

Example 1: https://www.google.com/maps/@41.5740327,-87.5255677,146m/data=!3m1!1e3

This is a few hundred feet from my house.  The actual state boundary is in the median of State Line Rd.  The boundary marked on the map is in the NB lane.  Off by only a few feet, but off nonetheless.

Example 2: https://www.google.com/maps/@41.5253767,-87.5254971,123m/data=!3m1!1e3

This is a few miles to the south.  The actual state boundary is along the fenceline that the shed of the house with the pool backs up to.  The boundary marked on the map is through everybody's front yards.  Much more significant different. 

I am not an expert on mapping technology but it seems like it shouldn't be hard to at least be more accurate than Example 2, if not Example 1.

I figured this was worth posting as a possible partial explanation:

Title: Re: Google Maps just fucking SUCKS now
Post by: NWI_Irish96 on May 06, 2020, 02:41:12 PM
I understand that explanation as to why it might not be perfect, and could reasonably be off as far as it is in Example 1, but I went a bit farther south and found this:

https://www.google.com/maps/@41.5227606,-87.5257605,123m/data=!3m1!1e3

Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 06, 2020, 02:55:42 PM
Quote from: cabiness42 on May 06, 2020, 02:41:12 PM
I understand that explanation as to why it might not be perfect, and could reasonably be off as far as it is in Example 1, but I went a bit farther south and found this:

https://www.google.com/maps/@41.5227606,-87.5257605,123m/data=!3m1!1e3

I may be totally off base here, but are you sure a "straight line" definition of the border actually matches the official boundary markers?
Title: Re: Google Maps just fucking SUCKS now
Post by: NWI_Irish96 on May 06, 2020, 03:24:03 PM
Quote from: kphoger on May 06, 2020, 02:55:42 PM
Quote from: cabiness42 on May 06, 2020, 02:41:12 PM
I understand that explanation as to why it might not be perfect, and could reasonably be off as far as it is in Example 1, but I went a bit farther south and found this:

https://www.google.com/maps/@41.5227606,-87.5257605,123m/data=!3m1!1e3

I may be totally off base here, but are you sure a "straight line" definition of the border actually matches the official boundary markers?

I don't know about the original definition of the boundary, but the straight line is what is observed by the states, counties, and municipalities involved.  Nobody considers the properties on that street to be straddling the boundary.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 06, 2020, 03:36:41 PM
Quote from: cabiness42 on May 06, 2020, 03:24:03 PM

Quote from: kphoger on May 06, 2020, 02:55:42 PM

Quote from: cabiness42 on May 06, 2020, 02:41:12 PM
I understand that explanation as to why it might not be perfect, and could reasonably be off as far as it is in Example 1, but I went a bit farther south and found this:

https://www.google.com/maps/@41.5227606,-87.5257605,123m/data=!3m1!1e3

I may be totally off base here, but are you sure a "straight line" definition of the border actually matches the official boundary markers?

I don't know about the original definition of the boundary, but the straight line is what is observed by the states, counties, and municipalities involved.  Nobody considers the properties on that street to be straddling the boundary.

I'm not saying that my suggestion is what is causing the discrepancy:  it's quite possible the mismatch is due to errors in the dataset or during data transformation.  But, if what you're looking for is accuracy, then you're looking for a map whose borders follow the official boundary markers, not one whose borders follow where those boundary markers are supposed to be, not one whose borders follow the line people consider to the the border.
Title: Re: Google Maps just fucking SUCKS now
Post by: NWI_Irish96 on May 06, 2020, 03:42:17 PM
Quote from: kphoger on May 06, 2020, 03:36:41 PM
Quote from: cabiness42 on May 06, 2020, 03:24:03 PM

Quote from: kphoger on May 06, 2020, 02:55:42 PM

Quote from: cabiness42 on May 06, 2020, 02:41:12 PM
I understand that explanation as to why it might not be perfect, and could reasonably be off as far as it is in Example 1, but I went a bit farther south and found this:

https://www.google.com/maps/@41.5227606,-87.5257605,123m/data=!3m1!1e3

I may be totally off base here, but are you sure a "straight line" definition of the border actually matches the official boundary markers?

I don't know about the original definition of the boundary, but the straight line is what is observed by the states, counties, and municipalities involved.  Nobody considers the properties on that street to be straddling the boundary.

I'm not saying that my suggestion is what is causing the discrepancy:  it's quite possible the mismatch is due to errors in the dataset or during data transformation.  But, if what you're looking for is accuracy, then you're looking for a map whose borders follow the official boundary markers, not one whose borders follow where those boundary markers are supposed to be, not one whose borders follow the line people consider to the the border.

I find it virtually impossible that, back when the Indiana Territory was carved out of the Northwest Territory, that the border took a random perpendicular jog of several hundred feet, at a spot that had no significance at the time but over a hundred years later would become the border between two townships within Lake County.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 06, 2020, 03:49:02 PM
Quote from: cabiness42 on May 06, 2020, 03:42:17 PM
I find it virtually impossible that, back when the Indiana Territory was carved out of the Northwest Territory, that the border took a random perpendicular jog of several hundred feet, at a spot that had no significance at the time but over a hundred years later would become the border between two townships within Lake County.

You can't imagine a group of surveyors making their way through wilderness to plot boundary markers and not walking a perfectly straight line?

The two 90-degree angles I don't understand, but it's easy to understand how one line segment could be farther west than another, even if the theoretical border is a straight line.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 06, 2020, 04:04:16 PM
Apple Maps has it as only the eastern line.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 06, 2020, 04:06:12 PM
Quote from: 1 on May 06, 2020, 04:04:16 PM
Apple Maps has it as only the eastern line.

So it goes through the people's houses?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on May 06, 2020, 04:08:30 PM
Quote from: kphoger on May 06, 2020, 04:06:12 PM
Quote from: 1 on May 06, 2020, 04:04:16 PM
Apple Maps has it as only the eastern line.

So it goes through the people's houses?

Yes.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 06, 2020, 04:15:37 PM
Quote from: kphoger on May 06, 2020, 03:49:02 PM
You can't imagine a group of surveyors making their way through wilderness to plot boundary markers and not walking a perfectly straight line?

The two 90-degree angles I don't understand, but it's easy to understand how one line segment could be farther west than another, even if the theoretical border is a straight line.

If the surveying were off, then it's far more likely than not (although admittedly not certain) that the houses and other lines on the ground would show some sort of skew, as the streets do in Vegas.

What I think is happening in this case, though is some sort of error in the data, in that shortly north of the jog, the border disappears, only returning near the airport.

(https://i.imgur.com/i3j19TA.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on May 09, 2020, 02:27:30 PM
Quote from: cabiness42 on May 06, 2020, 01:34:21 PM
I am not an expert on mapping technology but it seems like it shouldn't be hard to at least be more accurate than Example 2, if not Example 1.

It isn't hard at all, somebody just has to, you know...do it. The process for online commercial mapping these days is vastly automated, and it's pretty rare (if not completely unheard of) for an actual cartographer to come and check over the data, resolve any discrepancies, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on May 19, 2020, 08:38:51 PM
Today, Google Maps is placing my current location in Magnolia, just south of Discovery Park, instead of accurately in Renton.  This only happens when viewed in Firefox.  On Chrome and on my Android smart phone, the location is accurate.  Because I'm in the middle of dealing with changing my bank account because someone has hijacked it, perhaps I'm getting paranoid that someone has hacked my Google account too, though it may be something as simple as someone from Magnolia moving their Wi-Fi router near me.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on June 01, 2020, 09:13:52 AM
Something that irritates me about Street View coverage is that in the UK and Ireland, they'll gladly drive down just about anything, even something like this (https://www.google.com/maps/@54.3098282,-9.305911,3a,80.7y,355.98h,82.55t/data=!3m7!1e1!3m5!1sh7bRbw8lePuPluWH3RKUAA!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3Dh7bRbw8lePuPluWH3RKUAA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D80.507355%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), that calling a road would be generous. Meanwhile in the US, it seems as though they run away in fear at the sight of a wide gravel road.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on June 01, 2020, 11:01:21 AM
Quote from: bm7 on June 01, 2020, 09:13:52 AMSomething that irritates me about Street View coverage is that in the UK and Ireland, they'll gladly drive down just about anything, even something like this (https://www.google.com/maps/@54.3098282,-9.305911,3a,80.7y,355.98h,82.55t/data=!3m7!1e1!3m5!1sh7bRbw8lePuPluWH3RKUAA!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3Dh7bRbw8lePuPluWH3RKUAA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D80.507355%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), that calling a road would be generous. Meanwhile in the US, it seems as though they run away in fear at the sight of a wide gravel road.

The UK has almost three times the number of drivers per centerline mile of road that the US does--200 versus 75.  And over there, over 99% of public road mileage has had some form of bound surfacing since the 1950's; only about two-thirds of ours does.

Where Google Maps really falls short, IMV, is not upgrading to high-resolution StreetView even along lengths of road that not only are paved but are also state highway.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 01, 2020, 11:16:01 AM
Quote from: bm7 on June 01, 2020, 09:13:52 AM
Something that irritates me about Street View coverage is that in the UK and Ireland, they'll gladly drive down just about anything, even something like this (https://www.google.com/maps/@54.3098282,-9.305911,3a,80.7y,355.98h,82.55t/data=!3m7!1e1!3m5!1sh7bRbw8lePuPluWH3RKUAA!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3Dh7bRbw8lePuPluWH3RKUAA%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D80.507355%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656), that calling a road would be generous. Meanwhile in the US, it seems as though they run away in fear at the sight of a wide gravel road.
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 01, 2020, 11:18:33 AM
Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.

Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 01, 2020, 11:22:14 AM
Quote from: kphoger on June 01, 2020, 11:18:33 AM
Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.

Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.
Did you see the link?  That's basically someone's driveway.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 01, 2020, 11:30:49 AM
Quote from: Roadrunner75 on June 01, 2020, 11:22:14 AM

Quote from: kphoger on June 01, 2020, 11:18:33 AM

Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.

Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.

Did you see the link?  That's basically someone's driveway.

Plenty of dirt roads that are basically just driveways around where I grew up, and I never once encountered a person pulling a gun out if I came up that road by car or by bicycle.  I think you must have a warped view of what this part of the country is like.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 01, 2020, 11:38:33 AM
Quote from: kphoger on June 01, 2020, 11:30:49 AM
Quote from: Roadrunner75 on June 01, 2020, 11:22:14 AM

Quote from: kphoger on June 01, 2020, 11:18:33 AM

Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.

Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.

Did you see the link?  That's basically someone's driveway.

Plenty of dirt roads that are basically just driveways around where I grew up, and I never once encountered a person pulling a gun out if I came up that road by car or by bicycle.  I think you must have a warped view of what this part of the country is like.
I wasn't really commenting on your part of the country.   I think I'd feel a lot better about going down a dirt road in Kansas than some around here.  But the Google driver is probably (maybe?) a bit more apprehensive about rolling through what looks like a typical private drive over here.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 01, 2020, 11:48:39 AM
Fair enough, although I'm not really sure why things would be different if the road in question were paved.

I have noticed, back to the point at hand, that Google street view commonly ends where the pavement ends, even if the road keeps going.  For example, what other reason was there for the driver to end GSV coverage at this otherwise random spot (https://goo.gl/maps/v87Wrkbo4mrCDQg86) along the Highway of Legends scenic byway in Colorado?
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on June 01, 2020, 11:58:09 AM
Quote from: kphoger on June 01, 2020, 11:30:49 AM
Quote from: Roadrunner75 on June 01, 2020, 11:22:14 AM
Quote from: kphoger on June 01, 2020, 11:18:33 AM
Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.
Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.
Did you see the link?  That's basically someone's driveway.
Plenty of dirt roads that are basically just driveways around where I grew up, and I never once encountered a person pulling a gun out if I came up that road by car or by bicycle.  I think you must have a warped view of what this part of the country is like.
I agree. The Street View coverage probably has a lot to do with the magnitude of the area, and hardly anything to do with the fear of the property owners, most of whom are probably quite friendly and laid back. (There's probably a few hundred roads/driveways like that in the UK, compared to thousands in Kansas alone. The entire UK could fit inside Wyoming or Colorado with room to spare, while most Plains states are only slightly smaller than the UK.)

Quote from: Roadrunner75 on June 01, 2020, 11:38:33 AM
I wasn't really commenting on your part of the country. I think I'd feel a lot better about going down a dirt road in Kansas than some around here.  But the Google driver is probably (maybe?) a bit more apprehensive about rolling through what looks like a typical private drive over here.
Yeah, I would be much more apprehensive about going down random dirt roads in the South and Northeast than the Midwest. Visibility is much better in the Plains, population density is lower, and there's so many roads that all look similar that you could have got the wrong one, or turned down a driveway that you thought was a through road, and no one would probably even notice, much less care.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 01, 2020, 12:06:22 PM
Let's give Google some credit:

https://www.google.com/maps/@68.2243586,-149.4081092,3a,90y,140.46h,91.61t/data=!3m6!1e1!3m4!1sVabGlbl2GbHxBCdVU9ZuKw!2e0!7i13312!8i6656?hl=en (https://www.google.com/maps/@68.2243586,-149.4081092,3a,90y,140.46h,91.61t/data=!3m6!1e1!3m4!1sVabGlbl2GbHxBCdVU9ZuKw!2e0!7i13312!8i6656?hl=en)

https://www.google.com/maps/@65.6354017,-144.4432964,3a,75y,35.65h,89.56t/data=!3m6!1e1!3m4!1slOOxegsfuFltNjhIA03agw!2e0!7i13312!8i6656?hl=en (https://www.google.com/maps/@65.6354017,-144.4432964,3a,75y,35.65h,89.56t/data=!3m6!1e1!3m4!1slOOxegsfuFltNjhIA03agw!2e0!7i13312!8i6656?hl=en)

https://www.google.com/maps/@39.7357178,-74.7125319,3a,49.5y,131.02h,86.33t/data=!3m7!1e1!3m5!1sF4FDVmV_5GkIyMwMVn5smQ!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DF4FDVmV_5GkIyMwMVn5smQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D213.65996%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656?hl=en (https://www.google.com/maps/@39.7357178,-74.7125319,3a,49.5y,131.02h,86.33t/data=!3m7!1e1!3m5!1sF4FDVmV_5GkIyMwMVn5smQ!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DF4FDVmV_5GkIyMwMVn5smQ%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D213.65996%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656?hl=en)

https://www.google.com/maps/@39.8904268,-74.5409342,3a,75y,123.03h,79.19t/data=!3m7!1e1!3m5!1sqSaooBWwxdUBaasbIAPnuw!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DqSaooBWwxdUBaasbIAPnuw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D50.172806%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192?hl=en (https://www.google.com/maps/@39.8904268,-74.5409342,3a,75y,123.03h,79.19t/data=!3m7!1e1!3m5!1sqSaooBWwxdUBaasbIAPnuw!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DqSaooBWwxdUBaasbIAPnuw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D50.172806%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192?hl=en)

For the last two - yes, we have dirt roads in NJ.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 01, 2020, 12:12:11 PM
Quote from: Roadrunner75 on June 01, 2020, 12:06:22 PM
yes, we have dirt roads in NJ.

That's what caused my misunderstanding:  when I think of dirt roads, I certainly don't think of New Jersey!
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on June 01, 2020, 01:46:17 PM
Quote from: webny99 on June 01, 2020, 11:58:09 AM
Quote from: Roadrunner75 on June 01, 2020, 11:38:33 AM
I wasn't really commenting on your part of the country. I think I'd feel a lot better about going down a dirt road in Kansas than some around here.  But the Google driver is probably (maybe?) a bit more apprehensive about rolling through what looks like a typical private drive over here.

I agree, that feeling is probably more prevalent in suburban/exurban residential areas. I used to live on a dead-end public street in just such a town, and there's definitely an idea that not everyone who might travel that type of street is "supposed" to be there. I would not feel that way in the middle of rural Kansas or Ireland.

(There was an overall confusion among many town resident as to the distinction between a private and a public roadway. A number of residents who lived on private roads started to complain that although they were taxpayers, they weren't receiving the public service of snow plowing on their roads. It lead to the enactment of a new layer of local government, a snow removal district, that is probably the opposite of what they would have preferred!) :-D
Yeah, I would be much more apprehensive about going down random dirt roads in the South and Northeast than the Midwest. Visibility is much better in the Plains, population density is lower, and there's so many roads that all look similar that you could have got the wrong one, or turned down a driveway that you thought was a through road, and no one would probably even notice, much less care.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on June 01, 2020, 05:00:37 PM
I've also observed in the past that Google Maps has a tendency to show driveways (or double tracks intended for internal circulation on large farms and ranches) as if they were public roads.  I think this is a result of bad validation of satellite-sourced mapping.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on June 01, 2020, 08:50:22 PM
Quote from: J N Winkler on June 01, 2020, 05:00:37 PM
I've also observed in the past that Google Maps has a tendency to show driveways (or double tracks intended for internal circulation on large farms and ranches) as if they were public roads.  I think this is a result of bad validation of satellite-sourced mapping.

They also show sometimes some backyard alleys like this one in Calgary. https://goo.gl/maps/H8z1z14zfcswfKew8
Title: Re: Google Maps just fucking SUCKS now
Post by: Hot Rod Hootenanny on June 01, 2020, 09:39:28 PM
Quote from: J N Winkler on June 01, 2020, 05:00:37 PM
I've also observed in the past that Google Maps has a tendency to show driveways (or double tracks intended for internal circulation on large farms and ranches) as if they were public roads.  I think this is a result of bad validation of satellite-sourced mapping.

Google isn't the only one that has done this. DeLormes was notorious for doing this, and national topo maps would occasionally show private roads as public roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: ftballfan on June 02, 2020, 09:07:34 AM
More credit for Google (bonus points for this one being recent):
https://www.google.com/maps/@43.9957103,-85.9952178,3a,75y,279.77h,87.91t/data=!3m6!1e1!3m4!1sx5A0By7Ao-FBqbRdSAm8Fg!2e0!7i16384!8i8192
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on June 02, 2020, 10:33:52 AM
Quote from: Roadrunner75 on June 01, 2020, 11:38:33 AM
Quote from: kphoger on June 01, 2020, 11:30:49 AM
Quote from: Roadrunner75 on June 01, 2020, 11:22:14 AM

Quote from: kphoger on June 01, 2020, 11:18:33 AM

Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.

Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.

Did you see the link?  That's basically someone's driveway.

Plenty of dirt roads that are basically just driveways around where I grew up, and I never once encountered a person pulling a gun out if I came up that road by car or by bicycle.  I think you must have a warped view of what this part of the country is like.
I wasn't really commenting on your part of the country.   I think I'd feel a lot better about going down a dirt road in Kansas than some around here.  But the Google driver is probably (maybe?) a bit more apprehensive about rolling through what looks like a typical private drive over here.

I wind up on dirt roads a bunch...if it's not a 2-track road nor had an open gate in front of it, then I've never been bothered or threatened by anyone. If anything, you're more likely to get a wave (smiles are not guaranteed).
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 02, 2020, 10:51:35 AM
Quote from: formulanone on June 02, 2020, 10:33:52 AM
Quote from: Roadrunner75 on June 01, 2020, 11:38:33 AM
Quote from: kphoger on June 01, 2020, 11:30:49 AM
Quote from: Roadrunner75 on June 01, 2020, 11:22:14 AM

Quote from: kphoger on June 01, 2020, 11:18:33 AM

Quote from: Roadrunner75 on June 01, 2020, 11:16:01 AM
Agreed, but they're probably more likely to encounter some angry property owner coming out guns a'blazing on that same "road" in the US.

Having grown up in a small town in a very rural part of the country, where I used to be able to name all the paved roads and streets in the entire county from memory, I don't find that statement to match reality.

Did you see the link?  That's basically someone's driveway.

Plenty of dirt roads that are basically just driveways around where I grew up, and I never once encountered a person pulling a gun out if I came up that road by car or by bicycle.  I think you must have a warped view of what this part of the country is like.
I wasn't really commenting on your part of the country.   I think I'd feel a lot better about going down a dirt road in Kansas than some around here.  But the Google driver is probably (maybe?) a bit more apprehensive about rolling through what looks like a typical private drive over here.

I wind up on dirt roads a bunch...if it's not a 2-track road nor had an open gate in front of it, then I've never been bothered or threatened by anyone. If anything, you're more likely to get a wave (smiles are not guaranteed).
Out here, a dirt road is more than likely someone's driveway unless you're in the middle of the Pine Barrens, of which two examples are posted above.   
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 02, 2020, 12:10:28 PM
Quote from: Hot Rod Hootenanny on June 01, 2020, 09:39:28 PM

Quote from: J N Winkler on June 01, 2020, 05:00:37 PM
I've also observed in the past that Google Maps has a tendency to show driveways (or double tracks intended for internal circulation on large farms and ranches) as if they were public roads.  I think this is a result of bad validation of satellite-sourced mapping.

Google isn't the only one that has done this. DeLormes was notorious for doing this, and national topo maps would occasionally show private roads as public roads.

I'm not questioning that it happens (I know it does, at least with Google).  But I do caution that plenty of public roads look like driveways.  Just because something is a two-track overgrown with weeds, that doesn't mean it isn't in the county log books as a public road.  It might just mean there's no longer an active farm for it to lead to anymore.

One example that comes immediately to mind is Corncrib Road (https://goo.gl/maps/y6VamuoyZpSKZdWD7) near Ridgway, IL.  Just looking at Google Maps and satellite/street view imagery, you'd think they labeled it as a public road in error.  However, it's not an error.  Go back to older street view imagery, and you can even find a street sign at the corner.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on June 02, 2020, 02:20:53 PM
Gravel road on Google Street View. (https://goo.gl/maps/PpWMkTk8Lw1Z1oxi8)  This is State Route 165, perhaps the only long gravel state road in Western Washington, and access to part of Mt. Rainier National Park.  The Google car got part way up the road until it got to a turnaround, and gave up.  I've never been up this road.  My family always went to the Carbon River Entrance instead.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 02, 2020, 02:50:04 PM
Oh, there are plenty of gravel roads on GSV.  Practically every county road in Sedgwick County (KS) is covered, for example, and the majority of them are gravel or dirt.

Maybe it depends on the driver.  ??
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 02, 2020, 03:14:57 PM
The Google car gave up here where the pavement ends:
https://www.google.com/maps/@39.8926329,-74.3424548,3a,75y,242h,77.25t/data=!3m6!1e1!3m4!1s8IsNbeMNAQLffJ_ma6lp5A!2e0!7i13312!8i6656 (https://www.google.com/maps/@39.8926329,-74.3424548,3a,75y,242h,77.25t/data=!3m6!1e1!3m4!1s8IsNbeMNAQLffJ_ma6lp5A!2e0!7i13312!8i6656)

Not me though.  My son loves it when we "off-road" through the Pine Barrens.  It's not really that much of a shortcut, but I've used the dirt road beyond to get out to CR 539.  If you look on aerials, you can seen the signs of a development that was planned there including two cul-de-sacs to the south of the main road.   Not far to the north, NJ 70 was blocked by an accident one afternoon not too long ago near 539, and they were turning everyone around to drive miles back west to the 70/72 circle.  I wasn't about to do that, so I turned south onto a dirt road through a cranberry bog and decided to wing it and find a way around the accident.  A bunch of other drivers must have thought I knew what I was doing so they started following me right through the bog.  Eventually they started to disappear in my cloud of dust (they're probably still wandering around the woods to this day).  We found a utility pole easement and turned east and eventually popped out on 539, dodging a lot of huge puddles along the way.  No cell phone coverage or maps needed.  This is off-road excitement in New Jersey.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on June 02, 2020, 03:50:55 PM
Quote from: ErmineNotyours on June 02, 2020, 02:20:53 PM
Gravel road on Google Street View. (https://goo.gl/maps/PpWMkTk8Lw1Z1oxi8)  This is State Route 165, perhaps the only long gravel state road in Western Washington, and access to part of Mt. Rainier National Park.  The Google car got part way up the road until it got to a turnaround, and gave up.  I've never been up this road.  My family always went to the Carbon River Entrance instead.

I've been up that road once.  The road was fine all the way, good gravel.  The hike up to the fire lookout had some great views, but some of the worst mosquitos I've had the misfortune of encountering in western Washington.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on June 02, 2020, 09:14:10 PM
Quote from: kphoger on June 02, 2020, 02:50:04 PM
Oh, there are plenty of gravel roads on GSV.  Practically every county road in Sedgwick County (KS) is covered, for example, and the majority of them are gravel or dirt.

Maybe it depends on the driver.  ??
I was exaggerating a little in my original post. There are some parts of the US where they have gone down nearly every road. If you turn on the Street View layer and move around you can see them pretty easily. Some of the more notable ones are around Wichita, KS; Omaha/Lincoln, NE; La Crosse WI; and Springfield, IL.

But outside those sorts of areas it can be quite hard to find gravel roads that have Street View coverage. In fact when looking at my general area in the Street View layer, you can clearly see where many roads change from paved to gravel, because that's where the blue line ends.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on June 08, 2020, 06:11:55 PM
Quote from: Stephane Dumas on June 01, 2020, 08:50:22 PM
They also show sometimes some backyard alleys like this one in Calgary. https://goo.gl/maps/H8z1z14zfcswfKew8

Shouldn't they?

Quote from: Hot Rod Hootenanny on June 01, 2020, 09:39:28 PM
DeLormes was notorious for doing this, and national topo maps would occasionally show private roads as public roads.

You mean USGS topo maps? I've never known them to make any assertions about whether a road is private, unless perhaps by placing a highway shield or color fill on it.

Quote from: kphoger on June 02, 2020, 12:10:28 PM
One example that comes immediately to mind is Corncrib Road (https://goo.gl/maps/y6VamuoyZpSKZdWD7) near Ridgway, IL.  Just looking at Google Maps and satellite/street view imagery, you'd think they labeled it as a public road in error.  However, it's not an error.  Go back to older street view imagery, and you can even find a street sign at the corner.

And how about them class VI highways in NH? "Subject to gates and bars"...
Title: Re: Google Maps just fucking SUCKS now
Post by: BridgesToIdealism on June 18, 2020, 12:02:35 PM
Not sure if either of these two issues have been brought up previously, but my two biggest pet peeves with Google Maps are the following:

* Inconsistency when defining toll roads. Some toll roads are simply marked with their road name and "(toll road)" appended on the end, while others are marked with a solid black outline around the road which makes it stick out too much

* Google Maps Directions doesn't let you get directions involving roads that are closed, even when the road is only closed temporarily for construction. The one exception seems to be closures due to accidents, where you can force the route onto the road in desktop mode with the route modification drags. However, in cases of construction closures (most recently noted the Murray Baker I-74 Bridge closure in Peoria) it won't even let you drag/modify the route onto the temporarily closed road.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 18, 2020, 02:16:18 PM
Quote from: BridgesToIdealism on June 18, 2020, 12:02:35 PM
* Google Maps Directions doesn't let you get directions involving roads that are closed, even when the road is only closed temporarily for construction. The one exception seems to be closures due to accidents, where you can force the route onto the road in desktop mode with the route modification drags. However, in cases of construction closures (most recently noted the Murray Baker I-74 Bridge closure in Peoria) it won't even let you drag/modify the route onto the temporarily closed road.

I don't think this has specifically been discussed yet, maybe so.  But it's certainly one of my biggest frustrations.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on June 18, 2020, 05:23:34 PM
Around the end of April or beginning of May (I can't remember exactly), I noticed that Google Maps had started to use all my CPU, even just browsing around the map.  Over the next week or two, I noticed Facebook and Indeed started to use a lot of RAM and CPU.  These sites still use a lot of RAM and CPU, but thankfully within the last 2 or 3 weeks, Maps has stopped using all my CPU.  Sometimes it spikes, but it's mostly usable again.  Since multiple sites started acting up around the same time, I'm wondering if there was some web library like React or Angular that was updated.  For me, websites using React are notoriously resource hungry and/or glitchy.

About three weeks ago, I decided to see if the "force=canvas" switch still worked for Maps even though Lite Mode isn't a thing anymore.  Surprisingly, it worked!  There was even a lightning bolt icon in the corner like Lite mode had.  I tried "force=canvas" in my "too old" version of Chrome since I thought maybe that's why Google was blocking it, and it worked there too!  Later, I tried regular mode in Chrome again and it works!  The only glitches still there are the scroll wheel not working for zoom (that was the case before, I just use the plus and minus keys), and the minimap in Street View not displaying properly.

Between the time that Maps got slow and better again, I decided to try to adapt an embed since I noticed they were still smooth.  Being able to at least use a map smoothly would be somewhat helpful.  I was able to adapt their embed example into a bookmark with HTML in the URL itself to display a working full-screen map.

Lastly, I'll take a moment to complain about Indeed.  Why do you need almost 400 MB of RAM and 50% of my CPU?!  It worked fine before.  I can block the JavaScript that causes the spikes, but it's a polyfill that displays the "Apply Now" button.  That's the whole point of the site, so I can't block it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadrunner75 on June 18, 2020, 07:36:16 PM
Quote from: Michael on June 18, 2020, 05:23:34 PM
About three weeks ago, I decided to see if the "force=canvas" switch still worked for Maps even though Lite Mode isn't a thing anymore.  Surprisingly, it worked!  There was even a lightning bolt icon in the corner like Lite mode had.  I tried "force=canvas" in my "too old" version of Chrome since I thought maybe that's why Google was blocking it, and it worked there too!  Later, I tried regular mode in Chrome again and it works! 
I always use the "force-canvas" ("lite mode") switch.  Unless I'm clicking on a Maps link in a post, all my Google Maps fun starts out from that bookmark tab in Chrome (at least on the PC where I have an easy choice).  Other than lag, the only glitch I get occasionally is Pegman refusing to jump to Streetview (sometimes he has better things to do...)

Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on June 25, 2020, 06:15:38 PM
While exploring around, I found that the most recent street view imagery in Anchorage from October 2019 is absolutely terrible. Compare it with the 2009 imagery, and it's worse in almost every way.

https://www.google.com/maps/@61.2146283,-149.8996004,3a,78.6y,59.78h,89.95t/data=!3m6!1e1!3m4!1s33Ch-9l2_5bvQmQlGjn5PA!2e0!7i13312!8i6656

How did they even manage that?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 25, 2020, 06:31:00 PM
Quote from: bm7 on June 25, 2020, 06:15:38 PM
While exploring around, I found that the most recent street view imagery in Anchorage from October 2019 is absolutely terrible. Compare it with the 2009 imagery, and it's worse in almost every way.

https://www.google.com/maps/@61.2146283,-149.8996004,3a,78.6y,59.78h,89.95t/data=!3m6!1e1!3m4!1s33Ch-9l2_5bvQmQlGjn5PA!2e0!7i13312!8i6656

How did they even manage that?

To be fair, that's probably the best 2009 imagery I've ever seen on Google.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on June 25, 2020, 06:43:11 PM
Quote from: bm7 on June 25, 2020, 06:15:38 PM
While exploring around, I found that the most recent street view imagery in Anchorage from October 2019 is absolutely terrible. Compare it with the 2009 imagery, and it's worse in almost every way.

https://www.google.com/maps/@61.2146283,-149.8996004,3a,78.6y,59.78h,89.95t/data=!3m6!1e1!3m4!1s33Ch-9l2_5bvQmQlGjn5PA!2e0!7i13312!8i6656

How did they even manage that?

We waited 8 years for shit like that?
On a side note, it's nice to see Alaska bulking up its mast arms (compare this from 2019 (https://www.google.com/maps/@61.2136405,-149.8993896,3a,75y,316.02h,97.01t/data=!3m6!1e1!3m4!1sBDOV7p_m-H_4djk7fX2bjg!2e0!7i13312!8i6656/) to this from 2009 (https://www.google.com/maps/@61.213622,-149.8995441,3a,75y,352.52h,98.19t/data=!3m6!1e1!3m4!1stMI6RypSQ6zZEriDCvrVgw!2e0!7i13312!8i6656/).)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 25, 2020, 08:38:35 PM
Quote from: kphoger on June 25, 2020, 06:31:00 PM
Quote from: bm7 on June 25, 2020, 06:15:38 PM
While exploring around, I found that the most recent street view imagery in Anchorage from October 2019 is absolutely terrible. Compare it with the 2009 imagery, and it's worse in almost every way.

https://www.google.com/maps/@61.2146283,-149.8996004,3a,78.6y,59.78h,89.95t/data=!3m6!1e1!3m4!1s33Ch-9l2_5bvQmQlGjn5PA!2e0!7i13312!8i6656

How did they even manage that?

To be fair, that's probably the best 2009 imagery I've ever seen on Google.
There's actually a fair amount of good 2009 imagery, but most of it is outside the US (https://www.google.com/maps/@45.4840071,-73.5376895,3a,81.5y,14.35h,90.69t/data=!3m6!1e1!3m4!1spzWvQtlscMhHL8hZC_6sdw!2e0!7i13312!8i6656).
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on June 25, 2020, 09:55:33 PM
I was just looking around in Street View, and noticed that there are now clickable icons over businesses.  I assumed (and was hoping) this was an A/B test, and it turns out that it is (https://www.engadget.com/google-maps-street-view-ar-markers-141426824.html).  The picture in the article is similar to what I saw.  I took a quick look at Developer Tools to see if I could add a filter to my ad blocker to block the icons, but I couldn't use "pick element" nor did I see any obvious DIV I could block.  Thankfully, the icons disappear completely when I move my mouse out of the part of my screen with Street View on it.  While writing this post, I tried clearing my cookies, and that made the icons go away for now.

About a month ago, I saw another A/B test I forgot to mention in my last post.  When right-clicking the map, the coordinates of the spot I right-clicked on were listed at the top of the menu.  I liked that, but it only happened once.

On a side note, Maps is now always taking all my CPU again.  It started happening literally right after making my previous post saying it was sometimes better.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 27, 2020, 07:41:06 PM
Quote from: STLmapboy on June 25, 2020, 06:43:11 PM
We waited 8 years for shit like that?
On a side note, it's nice to see Alaska bulking up its mast arms (compare this from 2019 (https://www.google.com/maps/@61.2136405,-149.8993896,3a,75y,316.02h,97.01t/data=!3m6!1e1!3m4!1sBDOV7p_m-H_4djk7fX2bjg!2e0!7i13312!8i6656/) to this from 2009 (https://www.google.com/maps/@61.213622,-149.8995441,3a,75y,352.52h,98.19t/data=!3m6!1e1!3m4!1stMI6RypSQ6zZEriDCvrVgw!2e0!7i13312!8i6656/).)

Do you have like a fetish for thick mast arms? This is the second time I've seen you bring this up in a matter of days  :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: ftballfan on June 28, 2020, 02:33:40 PM
In My Maps, there is no way to have a line stick to a road without using the Directions mode. Years ago, there used to be a way to do so
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on July 06, 2020, 02:56:17 PM
Could someone explain to stupid fucking Google that white symbology on a white background makes their maps literally unreadable?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 06, 2020, 06:56:51 PM
Still ticked they took away the ability to print turn-by-turn maps with your directions.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 06, 2020, 09:47:18 PM
Quote from: paulthemapguy on July 06, 2020, 02:56:17 PM
Could someone explain to stupid fucking Google that white symbology on a white background makes their maps literally unreadable?

Could be your screen. Some people have the contrast way up and that seems to screw with it. For me it's perfectly readable, and actually preferable to other colors because the contrast between every single street and the background is far less jarring than if the colors were something stronger.

The major streets are still a thicker white and the major, major roads are still stronger yellows. I personally like it right now.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 06, 2020, 09:58:14 PM
I've noticed that monitor age makes a difference too.  Newer monitors seem to be designed brighter than older monitors, which look very dark if the contrast ins't turned all the way up.  It can turn into a choice between legible Google Maps and a monitor that is bright enough for anything else to look decent.
Title: Re: Google Maps just fucking SUCKS now
Post by: BridgesToIdealism on July 06, 2020, 10:46:25 PM
Okay, so in a similar manner to how Google won't let you get directions involving temporarily closed roads, here's another even more bizarre one to ponder over:

The World Trade International Toll Bridge in Laredo, Texas (future I-69W) is currently only open to commercial vehicles (passenger cars need to use the two bridges downtown). However, Google will not let you get directions involving the World Trade Bridge at all - it basically treats it like a closed road. What the hell? How on earth does Google know whether you are getting directions for a commercial vehicle that is permitted or not? Answer: It doesn't. This is beyond stupid. Just allow the use of the World Trade Bridge in directions for crying out loud... perhaps mark it as a "restricted usage road" if you want to make a fuss, but don't completely prevent its usage.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on July 06, 2020, 10:52:30 PM
Quote from: BridgesToIdealism on July 06, 2020, 10:46:25 PM
Okay, so in a similar manner to how Google won't let you get directions involving temporarily closed roads, here's another even more bizarre one to ponder over:

The World Trade International Toll Bridge in Laredo, Texas (future I-69W) is currently only open to commercial vehicles (passenger cars need to use the two bridges downtown). However, Google will not let you get directions involving the World Trade Bridge at all - it basically treats it like a closed road. What the hell? How on earth does Google know whether you are getting directions for a commercial vehicle that is permitted or not? Answer: It doesn't. This is beyond stupid. Just allow the use of the World Trade Bridge in directions for crying out loud... perhaps mark it as a "restricted usage road" if you want to make a fuss, but don't completely prevent its usage.

I noticed that the other day--if you click on of the marks there (I think on the Mexican side) it says "permanently closed." It's obviously not.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 07, 2020, 12:48:02 PM
It's because Google is not catering to people like us - it's catering to people who just want to plug in a destination and follow whatever directions are given.  We're lucky they still allow us to modify directions at all.

I'm actually surprised they're allowing directions over the US/Canada border... but maybe they don't want to break it for people with essential trips.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 07, 2020, 01:11:59 PM
Quote from: vdeane on July 07, 2020, 12:48:02 PM
I'm actually surprised they're allowing directions over the US/Canada border... but maybe they don't want to break it for people with essential trips.

Is the border closed to Canadian citizens returning from the US?
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on July 07, 2020, 01:13:39 PM
I believe Canadian citizens can enter Canada (and vice versa) as long as they quarantine for two weeks.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 07, 2020, 01:26:29 PM
Quote from: webny99 on July 07, 2020, 01:13:39 PM
I believe Canadian citizens can enter Canada (and vice versa) as long as they quarantine for two weeks.

Crap!  Canada can enter Canadian citizens and stay there for two weeks??
Title: Re: Google Maps just SUCKS now
Post by: webny99 on July 07, 2020, 01:31:39 PM
Quote from: kphoger on July 07, 2020, 01:26:29 PM
Canada COVID-19 can enter Canadian citizens and stay there for two weeks??

Not Canada itself, but another C-word, yes.

I thought it was obvious what vice versa meant in this context. When will I ever learn not to take that bet on this forum?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 07, 2020, 01:33:52 PM
Quote from: webny99 on July 07, 2020, 01:31:39 PM
When will I ever learn not to take that bet on this forum?

When nerds stop being pedantic.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 08, 2020, 12:02:05 AM
I would guess that roughly 1/10 posts are people correcting other people over minor niggles (correct something tiny, making a point that doesn't need making/not relevant). Drives me up the fucking wall.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on July 08, 2020, 12:24:45 AM
Quote from: jakeroot on July 08, 2020, 12:02:05 AM
I would guess that roughly 1/10 posts are people correcting other people over minor niggles (correct something tiny, making a point that doesn't need making/not relevant). Drives me up the fucking wall.

You don't say?
Quote from: NE2 on July 27, 2019, 09:54:43 PM
poop
Title: Re: Google Maps just fucking SUCKS now
Post by: BridgesToIdealism on July 10, 2020, 09:47:44 PM
Not sure if this has been mentioned before, but one of my biggest other pet peeves is that for whatever reason, the "Tunnel" category for place listing seems to no longer exist/be valid, so for any new tunnels that have not yet been added to the map, you have to list them as "bridges". Weird. On those same lines, has anyone else noticed the number of nonexistent categories that are being used by places? If you go into the form to edit a place, sometimes the category that it is currently listed as will be an invalid one, yet as long as you don't touch the "category" field it lets you keep it. Of course, if you touch the category field it will then say that the category is invalid.

Perhaps along similar lines but not exactly... how many other people have noticed the sheer number of places that have fake phone numbers? While I haven't actually tried to call them and see if they went anywhere, it is physically impossible to call a bridge or a tunnel or to call a toll booth, and yet many bridges, tunnels, and toll plazas have phone numbers in their listings. Even if its the phone number of the management authority, it doesn't belong on the actual infrastructure - it belongs on the authority headquarters office. Yet all too often Google doesn't let you remove them either... they don't even make it into the review queue. Any edits to that effect automatically get bounced back as "Not Applied - Google couldn't verify your edit".

...Which brings me to my third point for this post. I really don't think that the folks at Google are manually reviewing every single edit that is submitted to the map. I think that the vast majority of the edits are checked by a robot/computer software, and if the robot is unsure, it gets bumped back for human review. Therefore, many edits, such as simply correcting misplaced map markers, will get automatically approved. More complex edits that change multiple things at once will often get suck in the "Pending review" queue. For some reason, renaming places that either have typos or punctuation errors, and/or are outright wrong, seems to always get automatically rejected by the robot without any human review.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on July 11, 2020, 01:27:16 PM
It appears Google has added a feature (or I'm just noticing it) to GSV to better locate businesses while in that mode. Of course, this is bound to be troublesome with outdated imagery or recent changes to the area.

A good example of this new feature:

(https://live.staticflickr.com/65535/50100691748_c56667a400.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: Big John on July 21, 2020, 10:57:24 PM
I can't find the man icon to bring me to street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 22, 2020, 02:32:16 PM
Quote from: Big John on July 21, 2020, 10:57:24 PM
I can't find the man icon to bring me to street view.

The pegman is in the bottom right. Can you share a screenshot?
Title: Re: Google Maps just fucking SUCKS now
Post by: Big John on July 22, 2020, 03:11:43 PM
I got the pegman today.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 22, 2020, 03:17:45 PM
I am the eggman.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on July 22, 2020, 05:19:09 PM
Quote from: kphoger on July 22, 2020, 03:17:45 PM
I am the eggman.

Google g'joob
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 23, 2020, 01:33:09 AM
Sometimes the pegman gets lost :)
Title: Re: Google Maps just fucking SUCKS now
Post by: csw on July 27, 2020, 06:03:00 PM
I just realized today that if you drop the streetview man in Nevada, it puts the streetview man in a UFO...probably not a new discovery, but still a fun easter egg.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on July 27, 2020, 09:01:52 PM
Quote from: csw on July 27, 2020, 06:03:00 PM
I just realized today that if you drop the streetview man in Nevada, it puts the streetview man in a UFO...probably not a new discovery, but still a fun easter egg.

In Hawaii, he's a mermaid.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on July 27, 2020, 09:46:20 PM
Is it no longer possible to rotate Google Maps (i.e. rotate the map to so that a direction other than north is at the top) from a computer??

If so, that is a massive oversight, and I can't believe I didn't notice until now.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 27, 2020, 10:45:07 PM
Quote from: webny99 on July 27, 2020, 09:46:20 PM
Is it no longer possible to rotate Google Maps (i.e. rotate the map to so that a direction other than north is at the top) from a computer??

If so, that is a massive oversight, and I can't believe I didn't notice until now.

For me, it's not possible in 3D map mode, but it is possible in 3D satellite mode. I couldn't tell you if that's a change though since I almost always use 2D mode, which has never allowed rotation as far as I'm aware.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on July 28, 2020, 10:12:07 AM
Quote from: ozarkman417 on July 11, 2020, 01:27:16 PM
It appears Google has added a feature (or I'm just noticing it) to GSV to better locate businesses while in that mode. Of course, this is bound to be troublesome with outdated imagery or recent changes to the area.

A good example of this new feature:

(https://live.staticflickr.com/65535/50100691748_c56667a400.jpg)

They added it sometime in June. At the time I was cruising up and down Barcelona following the lines of their orthogonal bus network, and now it's a PITA to go through narrow streets. You almost have to go photo by photo in order not to click in a business. Historic Street View imagery doesn't have that feature.
Quote from: webny99 on July 27, 2020, 09:46:20 PM
Is it no longer possible to rotate Google Maps (i.e. rotate the map to so that a direction other than north is at the top) from a computer??

If so, that is a massive oversight, and I can't believe I didn't notice until now.

AFAIK it has never been possible to rotate the browser-based Google Maps on map mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on July 28, 2020, 08:58:21 PM
Quote from: BridgesToIdealism on July 06, 2020, 10:46:25 PM
Okay, so in a similar manner to how Google won't let you get directions involving temporarily closed roads, here's another even more bizarre one to ponder over:

The World Trade International Toll Bridge in Laredo, Texas (future I-69W) is currently only open to commercial vehicles (passenger cars need to use the two bridges downtown). However, Google will not let you get directions involving the World Trade Bridge at all - it basically treats it like a closed road. What the hell? How on earth does Google know whether you are getting directions for a commercial vehicle that is permitted or not? Answer: It doesn't. This is beyond stupid. Just allow the use of the World Trade Bridge in directions for crying out loud... perhaps mark it as a "restricted usage road" if you want to make a fuss, but don't completely prevent its usage.


It's the same for the Spokane Street Bridge in Seattle, which is currently closed to all but transit and freight in the daytime but open to most traffic at night.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 29, 2020, 01:01:32 PM
Quote from: CNGL-Leudimin on July 28, 2020, 10:12:07 AM
Quote from: webny99 on July 27, 2020, 09:46:20 PM
Is it no longer possible to rotate Google Maps (i.e. rotate the map to so that a direction other than north is at the top) from a computer??

If so, that is a massive oversight, and I can't believe I didn't notice until now.

AFAIK it has never been possible to rotate the browser-based Google Maps on map mode.

Also my experience. Changing from satellite view back to map view, regardless of the map mode (globe or flat) has always thrown the map back to north-up. There has never been a way to rotate the regular map in Google Maps, possibly ever.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on July 29, 2020, 01:11:56 PM
Quote from: jakeroot on July 29, 2020, 01:01:32 PM
Changing from satellite view back to map view, regardless of the map mode (globe or flat) has always thrown the map back to north-up. There has never been a way to rotate the regular map in Google Maps, possibly ever.

I do it all the time on my phone, though, so I guess I'm just surprised it never occurred to me I couldn't do it from my computer.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 29, 2020, 01:20:58 PM
Quote from: webny99 on July 29, 2020, 01:11:56 PM
Quote from: jakeroot on July 29, 2020, 01:01:32 PM
Changing from satellite view back to map view, regardless of the map mode (globe or flat) has always thrown the map back to north-up. There has never been a way to rotate the regular map in Google Maps, possibly ever.

I do it all the time on my phone, though, so I guess I'm just surprised it never occurred to me I couldn't do it from my computer.

That's primarily because Google Maps on the phone is used for navigation, where having the map oriented relative to the viewer is especially important. On the computer? I mean, it's something they could easily code (as they already have for satellite view), but I don't think there's as-much of a use case.
Title: Re: Google Maps just fucking SUCKS now
Post by: ilpt4u on August 03, 2020, 02:29:46 AM
Anyone else notice, using iOS, since the latest update/version 5.49 of the Google Maps App, has broken the ability to launch GSV from a location pin?

Found a Google Support thread on it, so I know I'm not the only one having this issue: https://support.google.com/maps/thread/61807479?hl=en
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 03, 2020, 06:42:15 AM
Quote from: ilpt4u on August 03, 2020, 02:29:46 AM
Anyone else notice, using iOS, since the latest update/version 5.49 of the Google Maps App, has broken the ability to launch GSV from a location pin?

Found a Google Support thread on it, so I know I'm not the only one having this issue: https://support.google.com/maps/thread/61807479?hl=en
I noticed the same thing as well. Quite annoying, and hopefully it's just a bug and will be fixed.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 03, 2020, 09:32:21 AM
I see that 2007-quality Streetview images are making a comeback for 2020. :banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on August 03, 2020, 09:36:57 AM
Quote from: LM117 on August 03, 2020, 09:32:21 AM
I see that 2007-quality Streetview images are making a comeback for 2020. :banghead:
They seem to be gradually going away to me. Used to be that all of the GSV for just about anywhere in WI north of hwy 29 was bad quality. Now there's good quality GSV on most of the state routes.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 03, 2020, 09:43:42 AM
Quote from: thspfc on August 03, 2020, 09:36:57 AM
Quote from: LM117 on August 03, 2020, 09:32:21 AM
I see that 2007-quality Streetview images are making a comeback for 2020. :banghead:
They seem to be gradually going away to me. Used to be that all of the GSV for just about anywhere in WI north of hwy 29 was bad quality. Now there's good quality GSV on most of the state routes.

I was referring to the new images that were taken this year.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on August 13, 2020, 10:36:05 AM
Not exactly Google maps but Bing maps can sucks as well. Their streetside view of St. Regis/Akwasasne Indian Reserve stop right in the Canadian/US border.
https://www.bing.com/maps?osid=e02eff4f-a700-40ea-aa51-a33f501e0972&cp=44.999479~-74.646697&lvl=19&dir=50.282&pi=-0.44&style=x&mo=z.0&v=2&sV=2&form=S00027

I still wonder when Bing Streetside will cover Canada but that's for another topic. ;)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 17, 2020, 11:49:31 PM
Quote from: Stephane Dumas on August 13, 2020, 10:36:05 AM
Not exactly Google maps but Bing maps can sucks as well. Their streetside view of St. Regis/Akwasasne Indian Reserve stop right in the Canadian/US border.
https://www.bing.com/maps?osid=e02eff4f-a700-40ea-aa51-a33f501e0972&cp=44.999479~-74.646697&lvl=19&dir=50.282&pi=-0.44&style=x&mo=z.0&v=2&sV=2&form=S00027

I still wonder when Bing Streetside will cover Canada but that's for another topic. ;)

Wait, so Bing Maps 'fucking sucks' because they don't yet cover all of Canada? That seems a bit harsh.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 18, 2020, 08:34:21 PM
Well, Google is at it again.  Sure, the natural features look pretty, but the roads look ugly, and it's now even more difficult to pick out freeways cities than it was before (seriously, freeways and arterials have gone from being nearly the same color to being actually the same color).  Why does Google keep suppressing the data that one would use a map for in favor of things that one would use satellite images for?

I wish there were a true competitor to Google Maps, but between street view, accurate drive times, the traffic layer, business information/photos/reviews, and the ability to set shaping points in directions, there's really nobody else that comes close.

https://www.theverge.com/2020/8/18/21373363/google-maps-redesign-detail-natural-features-environment
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on August 18, 2020, 08:41:16 PM
Over the past few months, I've switched to using OSM for anything map-based and only bringing up Google Maps if I need imagery of some kind. Because I usually am more interested in the location of things like county lines than the location of things like capitalism.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 19, 2020, 12:45:08 AM
As usual, I actually like the changes.

I think it's a mistake to assume that people only use Google Maps to view roads. There's a lot of other stuff going on.

This update actually looks really cool. Especially street-level detail. The contrast also appears to have improved. Check out the sliding image for Mt Rainier National Park (the roads are a bit easier to see now, against the new colors).
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 19, 2020, 09:15:25 AM
Quote from: vdeane on August 18, 2020, 08:34:21 PM
Well, Google is at it again.  Sure, the natural features look pretty, but the roads look ugly, and it's now even more difficult to pick out freeways cities than it was before (seriously, freeways and arterials have gone from being nearly the same color to being actually the same color).

I don't care for that, either. Plus, I still don't understand why the new 2020 Streetview images were taken with a potato. Sure, the pandemic has hit budgets pretty hard, but you'd think Google can still afford HD cameras. :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 19, 2020, 12:56:39 PM
Quote from: jakeroot on August 19, 2020, 12:45:08 AM
As usual, I actually like the changes.

I think it's a mistake to assume that people only use Google Maps to view roads. There's a lot of other stuff going on.

This update actually looks really cool. Especially street-level detail. The contrast also appears to have improved. Check out the sliding image for Mt Rainier National Park (the roads are a bit easier to see now, against the new colors).
Meanwhile, on that Arizona image... can you tell which road is the freeway and which roads aren't on the new one (ignoring the I-17 shields)?  Because I can't.  The roads are particularly difficult to see at certain zoom levels (zoom 7 was particularly hard, because that's when the arterials appear, but everything looks the same, and the green and yellow aren't as distinct as the beige background that was there before Google started trying to show greenery).  Way zoomed in, arterials and freeways and freeway ramps all look the same too, which at that scale you can usually tell by context, but still, it looks ugly.  Google had me switched over to the new one last night, so yeah, I've poked around with it, and navigation is certainly harder than it was before.

There is a difference between enabling people to do things other than look at roads and making looking at roads harder.  Google is doing the latter.  After all, what is an interactive road atlas for, if not to look at roads?  Let's not forget that Google Maps began as a more browsable version of MapQuest.  It's ironic that one of their original key selling points (the ability to pan the map by dragging it with the mouse and zoom with the mouse wheel, rather than using search or the buttons on the side (which ties into another key selling point - not having onerous load times for panning/zooming the map!)) is made harder by recent changes!

Freeways, as a radically different type of road from surface streets with at-grades and driveways, deserve to pop out when looking at the map at a glance.  They are not the same as other arterials.  I don't get why Google doesn't understand this.

Quote from: LM117 on August 19, 2020, 09:15:25 AM
Quote from: vdeane on August 18, 2020, 08:34:21 PM
Well, Google is at it again.  Sure, the natural features look pretty, but the roads look ugly, and it's now even more difficult to pick out freeways cities than it was before (seriously, freeways and arterials have gone from being nearly the same color to being actually the same color).

I don't care for that, either. Plus, I still don't understand why the new 2020 Streetview images were taken with a potato. Sure, the pandemic has hit budgets pretty hard, but you'd think Google can still afford HD cameras. :pan:
I haven't seen much in the way of 2020 imagery, so I wouldn't know.  One thing to check, though, is whether it's actually Google imagery you're seeing.  They allow third party imagery, which is inevitably lower quality, and often which has priority over Google imagery for some reason even when the Google imagery is newer.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 19, 2020, 01:09:48 PM
Quote from: vdeane on August 19, 2020, 12:56:39 PMMeanwhile, on that Arizona image... can you tell which road is the freeway and which roads aren't on the new one (ignoring the I-17 shields)?  Because I can't.  The roads are particularly difficult to see at certain zoom levels (zoom 7 was particularly hard, because that's when the arterials appear, but everything looks the same, and the green and yellow aren't as distinct as the beige background that was there before Google started trying to show greenery).  Way zoomed in, arterials and freeways and freeway ramps all look the same too, which at that scale you can usually tell by context, but still, it looks ugly.  Google had me switched over to the new one last night, so yeah, I've poked around with it, and navigation is certainly harder than it was before.

I haven't been switched over yet.  My impression, based on the views available in the article (zoom locked), is that roads in general will be easier to pick out of the background, but there may still be a slight differentiation in shade between freeways and other arterials comparable to what exists now.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 19, 2020, 01:23:39 PM
Quote from: vdeane on August 19, 2020, 12:56:39 PM
After all, what is an interactive road atlas for, if not to look at roads?

I'd argue that isn't really what Google Maps is.  I bet most people just use it to find out where certain businesses are and the fastest way to get there from here.  They don't care if the road along the way is a freeway or not, they just care where to turn.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on August 19, 2020, 01:24:02 PM
Quote from: J N Winkler on August 19, 2020, 01:09:48 PM
Quote from: vdeane on August 19, 2020, 12:56:39 PMMeanwhile, on that Arizona image... can you tell which road is the freeway and which roads aren't on the new one (ignoring the I-17 shields)?  Because I can't.  The roads are particularly difficult to see at certain zoom levels (zoom 7 was particularly hard, because that's when the arterials appear, but everything looks the same, and the green and yellow aren't as distinct as the beige background that was there before Google started trying to show greenery).  Way zoomed in, arterials and freeways and freeway ramps all look the same too, which at that scale you can usually tell by context, but still, it looks ugly.  Google had me switched over to the new one last night, so yeah, I've poked around with it, and navigation is certainly harder than it was before.

I haven't been switched over yet.  My impression, based on the views available in the article (zoom locked), is that roads in general will be easier to pick out of the background, but there may still be a slight differentiation in shade between freeways and other arterials comparable to what exists now.

I can barely pick out freeways from arterials in the new one.

Edit; the new stuff isn't showing up for me now. It showed up this morning, weird.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 19, 2020, 08:23:26 PM
Quote from: J N Winkler on August 19, 2020, 01:09:48 PM
Quote from: vdeane on August 19, 2020, 12:56:39 PMMeanwhile, on that Arizona image... can you tell which road is the freeway and which roads aren't on the new one (ignoring the I-17 shields)?  Because I can't.  The roads are particularly difficult to see at certain zoom levels (zoom 7 was particularly hard, because that's when the arterials appear, but everything looks the same, and the green and yellow aren't as distinct as the beige background that was there before Google started trying to show greenery).  Way zoomed in, arterials and freeways and freeway ramps all look the same too, which at that scale you can usually tell by context, but still, it looks ugly.  Google had me switched over to the new one last night, so yeah, I've poked around with it, and navigation is certainly harder than it was before.

I haven't been switched over yet.  My impression, based on the views available in the article (zoom locked), is that roads in general will be easier to pick out of the background, but there may still be a slight differentiation in shade between freeways and other arterials comparable to what exists now.
I find the Arizona and Morocco images in the article to be indicative of my experience when I was briefly switched over last night.  The Mount Rainier example is cherry-picked from a zoom level and area where the new experience was optimized and does not match up with my reality.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 20, 2020, 02:17:24 PM
Quote from: J N Winkler on August 19, 2020, 01:09:48 PM
Quote from: vdeane on August 19, 2020, 12:56:39 PMMeanwhile, on that Arizona image... can you tell which road is the freeway and which roads aren't on the new one (ignoring the I-17 shields)?  Because I can't.  The roads are particularly difficult to see at certain zoom levels (zoom 7 was particularly hard, because that's when the arterials appear, but everything looks the same, and the green and yellow aren't as distinct as the beige background that was there before Google started trying to show greenery).  Way zoomed in, arterials and freeways and freeway ramps all look the same too, which at that scale you can usually tell by context, but still, it looks ugly.  Google had me switched over to the new one last night, so yeah, I've poked around with it, and navigation is certainly harder than it was before.

I haven't been switched over yet.  My impression, based on the views available in the article (zoom locked), is that roads in general will be easier to pick out of the background, but there may still be a slight differentiation in shade between freeways and other arterials comparable to what exists now.

This is kind of what I was seeing. Plus, and I feel like I'm on repeat when I say this: it really depends on your screen settings. To me, the new changes have improved contrast.

Quote from: vdeane on August 19, 2020, 12:56:39 PM
Meanwhile, on that Arizona image... can you tell which road is the freeway and which roads aren't on the new one (ignoring the I-17 shields)?  Because I can't.  The roads are particularly difficult to see at certain zoom levels (zoom 7 was particularly hard, because that's when the arterials appear, but everything looks the same, and the green and yellow aren't as distinct as the beige background that was there before Google started trying to show greenery).  Way zoomed in, arterials and freeways and freeway ramps all look the same too, which at that scale you can usually tell by context, but still, it looks ugly.  Google had me switched over to the new one last night, so yeah, I've poked around with it, and navigation is certainly harder than it was before.

There is a difference between enabling people to do things other than look at roads and making looking at roads harder.  Google is doing the latter.  After all, what is an interactive road atlas for, if not to look at roads?  Let's not forget that Google Maps began as a more browsable version of MapQuest.  It's ironic that one of their original key selling points (the ability to pan the map by dragging it with the mouse and zoom with the mouse wheel, rather than using search or the buttons on the side (which ties into another key selling point - not having onerous load times for panning/zooming the map!)) is made harder by recent changes!

Freeways, as a radically different type of road from surface streets with at-grades and driveways, deserve to pop out when looking at the map at a glance.  They are not the same as other arterials.  I don't get why Google doesn't understand this.

I can see a difference, yes. The freeway is thicker. Mostly because freeways have two strokes of parallel lines, and most arterials are shown as a single stroke. Subtle but important.

I would keep things as they are. Right now, surface roads that are colored yellow are basically as important to ordinary persons as a freeway, since both are meant to indicate those routes that can be used for interregional travel. In the Seattle area, yellow surface roads are only those that are extremely important to travel in the area. The vast majority of these are just as important as freeways.

In the US, I would shy away from separately colored freeways: unlike most countries, we truly have a disastrous way of classifying freeways, and standards seem to vary even state to state. It's easy enough to classify an interstate, but those are far from the only important freeways or roads in a city (although in New York, I know there are a lot of interstates, so your perspective may be skewed from mine slightly). Thus, rather than going to great lengths and deciding on a segment-by-segment basis "this is freeway" or "this is not freeway", and then spending thousands of hours defending your choices (as is often the case on OSM -- read: WA 500), it's simply easier to say "this is a major road" or "this is not a major road".

From the perspective of a GIS'er, my interest is not so much in what they classify as freeway, but actually what they classify as something qualifying for the yellow color. I personally feel like they've hit the nail on the head, although there's a couple roads I would highlight as yellow in my area that are currently white. Otherwise, I like what I see and I'm very excited to use the new Maps.

Quote from: vdeane on August 18, 2020, 08:34:21 PM
I wish there were a true competitor to Google Maps, but between street view, accurate drive times, the traffic layer, business information/photos/reviews, and the ability to set shaping points in directions, there's really nobody else that comes close.

To me, those additions (particularly business information, but many other things as well) have been made easier by reducing the level of detail given to the roadways. Maps cannot be all things to all users: Google has decided that their mapping service should be oriented towards someone interested in interactive mapping (traffic, business location, transit services); OSM is not good in this regard, as it is primarily designed for viewing. Google Maps was better for those simply interested in viewing a map without interacting, but the average Google Maps user expects more from them these days.

What I'm looking forward to from Google is greater geographic detail (not road detail). Viewing Mt Rainier on OSM versus Google Maps is a good example of how OSM can be far superior.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on August 20, 2020, 02:30:52 PM
Fun new bug in Google Maps in Android Auto. Randomly, it will just stop updating my position and freeze me in place until I unplug my phone and plug it back in to the cable.

Even more fun is a side effect of it. If I leave it alone and let the freeze stay long enough, the app thinks I am not moving and must be in "traffic", therefore showing traffic on whatever road I was on when it stopped updating.
Title: Re: Google Maps just fucking SUCKS now
Post by: mgk920 on August 20, 2020, 03:32:01 PM
Quote from: CNGL-Leudimin on July 28, 2020, 10:12:07 AM
Quote from: ozarkman417 on July 11, 2020, 01:27:16 PM
It appears Google has added a feature (or I'm just noticing it) to GSV to better locate businesses while in that mode. Of course, this is bound to be troublesome with outdated imagery or recent changes to the area.

A good example of this new feature:

(https://live.staticflickr.com/65535/50100691748_c56667a400.jpg)

They added it sometime in June. At the time I was cruising up and down Barcelona following the lines of their orthogonal bus network, and now it's a PITA to go through narrow streets. You almost have to go photo by photo in order not to click in a business. Historic Street View imagery doesn't have that feature.
Quote from: webny99 on July 27, 2020, 09:46:20 PM
Is it no longer possible to rotate Google Maps (i.e. rotate the map to so that a direction other than north is at the top) from a computer??

If so, that is a massive oversight, and I can't believe I didn't notice until now.

AFAIK it has never been possible to rotate the browser-based Google Maps on map mode.

Also, I'm finding ad pegs on aerial images that remain after I've turned labels off.  It is royally annoying when I'm trying to do research on what's in the images.  Also, yes, those business ID pins on streetview images are annoying when I'm trying to check the buildings and not the specific businesses that are in them.

I have so far found no way to turn those 'features' off.

:banghead:

Mike
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on August 27, 2020, 08:39:48 PM
Within the last week or so, I've finally started getting the new map style.  At first, I sometimes got the new style, and sometimes got the old one.  A week or two before the change, I noticed that bus icons and dark blue business icons were a darker shade of blue.  When I first got the new style, I thought it was A/B testing, but after a quick Google, I found out it's not.  I looked earlier in this thread, and it turns out it was discussed, but I missed that part.  I don't completely hate the new style, but I'm not a fan.  I like that the major roads aren't bright yellow, but the new orange is bright in a different way, and it's still a bit too much, especially on green backgrounds. The green everywhere is too much in my opinion.  If I were looking for a park, the greens are too similar to easily distinguish them.  The contrast between gray towns and green rural areas is jarring.  It's neat to be able to see vegetation, but that's a different type of map, so I'd prefer if it was a layer that could be turned on or off.

I've also noticed a couple glitches.  At certain zoom levels, some segments of streams and rivers connect points along the path to make a lake where none exists.  After this started happening, towns and lakes started doing a similar thing.  At certain zoom levels, the detail in boundaries is missing.  I'd expect this when zoomed out, but this glitch happens when I'm zoomed in enough to where a detailed border would be visible.

Earlier this afternoon, I noticed a new feature I like.  Intersections with stoplights have a stoplight icon on them.  I think I saw something like this in Asia a few years ago and thought it was neat.  I looked at a few local intersections to see how accurate the icons are, and found it wasn't 100% accurate.  This pair of stoplights (https://www.google.com/maps/@42.9341574,-76.5634692,3a,75y,337.97h,89.89t/data=!3m7!1e1!3m5!1swnurYBrYRYFDS5kJjDrtLg!2e0!6s%2F%2Fgeo1.ggpht.com%2Fcbk%3Fpanoid%3DwnurYBrYRYFDS5kJjDrtLg%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D300.53162%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192) is shown as a single light and this blinking light (https://www.google.com/maps/@43.0239625,-76.486442,3a,75y,53h,94.06t/data=!3m6!1e1!3m4!1s2-_MXCHq2ev0rQPmC_Cm3w!2e0!7i16384!8i8192) is shown as a stoplight.

On a side note, while getting Maps links for this post, it suddenly reverted to the old map style, but with the stoplight icons and new bus icon color.  I've also noticed that embeds and the card previews in search results still have the old style too.

EDIT: I just tried using WASD to move the map (Did that ever work?  I can't remember), and when I did, it started typing in the search box.  I thought maybe I accidentally typed a forward slash and that moved the focus to the search box like on YouTube, but it didn't.  I tried typing a question mark to see if that would do it, but it popped up a box with keyboard shortcuts I didn't know existed!  Also, it turns out that typing while your focus is on the map moves the focus to the search box and starts typing there.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 28, 2020, 12:50:32 PM
Quote from: Michael on August 27, 2020, 08:39:48 PM
The green everywhere is too much in my opinion.  If I were looking for a park, the greens are too similar to easily distinguish them.  The contrast between gray towns and green rural areas is jarring.  It's neat to be able to see vegetation, but that's a different type of map, so I'd prefer if it was a layer that could be turned on or off.

I agree.

On the other hand, some state/national park/forest boundaries are easier to identify now.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 28, 2020, 01:06:22 PM
Quote from: LM117 on August 19, 2020, 09:15:25 AM
Quote from: vdeane on August 18, 2020, 08:34:21 PM
Well, Google is at it again.  Sure, the natural features look pretty, but the roads look ugly, and it's now even more difficult to pick out freeways cities than it was before (seriously, freeways and arterials have gone from being nearly the same color to being actually the same color).

I don't care for that, either. Plus, I still don't understand why the new 2020 Streetview images were taken with a potato. Sure, the pandemic has hit budgets pretty hard, but you'd think Google can still afford HD cameras. :pan:
What images are you specifically referring to?
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 28, 2020, 01:07:46 PM
^

Regarding freeway vs. arterial, I usually will just turn on the "traffic" layer that makes it much easier to distinguish freeways over other roads. Much thicker lines.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 29, 2020, 09:37:28 PM
I finally got a good look at the new Google Maps today thanks to a maps.google.ca link.

Thoughts so far, based on about an hour of use:


  • the changing color scheme depending on scale is the first application of such that I'm aware of. No opinion yet. BUT...
  • the 'geographically-accurate' color background is a nice touch, though I'd like to know what the meaning is of grey vs non-grey when zoomed out. I assume city vs non-city, but there are discrepancies in my area.
  • roads are quite a bit easier to pick out now compared to before. The new background colors (when zoomed out) help a lot, and the increased saturation upon zooming in helps to maintain the contrast without colorful backgrounds
  • when zoomed out, freeways definitely seem to be a touch darker and have slightly thicker lines. I can personally tell them apart from yellow surface roads (although I maintain that telling them apart is not necessarily important).
  • the tribal reservation overlay is quite lovely.
  • parks are a shade darker than the grassy green that covers a lot of the map now. I can tell them apart quite easily.

Although the feature doesn't appear to have launched, I'm very excited to use the new detailed large-scale street maps. So far, the images I've seen are very reminiscent of Japanese Google Maps. I'd like to know if the company that provides all that detail to Google (Zenrin?) has helped them with this feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on August 29, 2020, 09:53:34 PM
At first I hated the new update, but it's sort of growing on me. The only real issue I've noticed is that it's more difficult to distinguish freeways/Interstates from regular state or US routes.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on August 29, 2020, 10:06:27 PM
Quote from: jakeroot on August 29, 2020, 09:37:28 PM
  • the tribal reservation overlay is quite lovely.

Except when it gets caught up in rez border quirks like this (https://www.google.pl/maps/@35.6715259,-108.3404771,9.04z/). I guess there's no way around that though.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 01, 2020, 04:02:23 PM
Quote from: STLmapboy on August 29, 2020, 10:06:27 PM
Quote from: jakeroot on August 29, 2020, 09:37:28 PM
  • the tribal reservation overlay is quite lovely.

Except when it gets caught up in rez border quirks like this (https://www.google.pl/maps/@35.6715259,-108.3404771,9.04z/). I guess there's no way around that though.

Especially since that is the border of the "Navajo Nation Off-Reservation Trust Land". Just really quirky lines.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on September 01, 2020, 04:35:37 PM
Quote from: jakeroot on September 01, 2020, 04:02:23 PM
Quote from: STLmapboy on August 29, 2020, 10:06:27 PM
Quote from: jakeroot on August 29, 2020, 09:37:28 PM
  • the tribal reservation overlay is quite lovely.

Except when it gets caught up in rez border quirks like this (https://www.google.pl/maps/@35.6715259,-108.3404771,9.04z/). I guess there's no way around that though.

Especially since that is the border of the "Navajo Nation Off-Reservation Trust Land". Just really quirky lines.

(Cough, cough)  Dawes Act. (https://en.wikipedia.org/wiki/Dawes_Act)
Title: Re: Google Maps just fucking SUCKS now
Post by: MCRoads on September 01, 2020, 05:24:01 PM
Anyone notice how they have added traffic signal icons to the map?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 01, 2020, 05:27:03 PM
Quote from: MCRoads on September 01, 2020, 05:24:01 PM
Anyone notice how they have added traffic signal icons to the map?

Yes. I think it's a good addition.

I checked one spot (Walgreens and back entrance to The Loop next to MA 213 exit 3) that contains full signal heads, but only flashes red and yellow. No signal on Google Maps. Good.
Title: Re: Google Maps just fucking SUCKS now
Post by: MCRoads on September 01, 2020, 05:44:45 PM
Apparently it has been a thing in Japan for a while now, but I don't browse there, so I can't say for sure.
Title: Re: Google Maps just fucking SUCKS now
Post by: paulthemapguy on September 01, 2020, 05:54:59 PM
I got the Google Maps update on mobile (Android phone), and trying to find my user content (My Maps) has become a nightmare.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 01, 2020, 06:27:43 PM
Quote from: J N Winkler on September 01, 2020, 04:35:37 PM
Quote from: jakeroot on September 01, 2020, 04:02:23 PM
Quote from: STLmapboy on August 29, 2020, 10:06:27 PM
Quote from: jakeroot on August 29, 2020, 09:37:28 PM
  • the tribal reservation overlay is quite lovely.

Except when it gets caught up in rez border quirks like this (https://www.google.pl/maps/@35.6715259,-108.3404771,9.04z/). I guess there's no way around that though.

Especially since that is the border of the "Navajo Nation Off-Reservation Trust Land". Just really quirky lines.

(Cough, cough)  Dawes Act. (https://en.wikipedia.org/wiki/Dawes_Act)

Thank you. I was wondering, but didn't take the time to search.

Quote from: MCRoads on September 01, 2020, 05:44:45 PM
Apparently it has been a thing in Japan for a while now, but I don't browse there, so I can't say for sure.

I've noticed it in NZ and Australia for a long time as well. Japan's implementation is nice because it shows the horizontal display preferred in most of Japan, with the right-hand drive left-to-right green-yellow-red configuration, rather than the opposite preferred in left-hand drive countries like the US.
Title: Re: Google Maps just fucking SUCKS now
Post by: stevashe on September 01, 2020, 11:45:44 PM
Quote from: 1 on September 01, 2020, 05:27:03 PM
Quote from: MCRoads on September 01, 2020, 05:24:01 PM
Anyone notice how they have added traffic signal icons to the map?

Yes. I think it's a good addition.

I checked one spot (Walgreens and back entrance to The Loop next to MA 213 exit 3) that contains full signal heads, but only flashes red and yellow. No signal on Google Maps. Good.

I noticed it about a month ago, but there was very spotty coverage back then. And I was perusing the map around Connecticut yesterday and did see some red/yellow flashers marked as traffic lights, unfortunately. Here's one example:
(https://i.imgur.com/kyQGYva.png) (https://imgur.com/a/ereJF2s)




Quote from: jakeroot on August 29, 2020, 09:37:28 PM
I finally got a good look at the new Google Maps today thanks to a maps.google.ca link.

Thoughts so far, based on about an hour of use:


  • the changing color scheme depending on scale is the first application of such that I'm aware of. No opinion yet. BUT...
  • the 'geographically-accurate' color background is a nice touch, though I'd like to know what the meaning is of grey vs non-grey when zoomed out. I assume city vs non-city, but there are discrepancies in my area.
  • roads are quite a bit easier to pick out now compared to before. The new background colors (when zoomed out) help a lot, and the increased saturation upon zooming in helps to maintain the contrast without colorful backgrounds
  • when zoomed out, freeways definitely seem to be a touch darker and have slightly thicker lines. I can personally tell them apart from yellow surface roads (although I maintain that telling them apart is not necessarily important).
  • the tribal reservation overlay is quite lovely.
  • parks are a shade darker than the grassy green that covers a lot of the map now. I can tell them apart quite easily.

Although the feature doesn't appear to have launched, I'm very excited to use the new detailed large-scale street maps. So far, the images I've seen are very reminiscent of Japanese Google Maps. I'd like to know if the company that provides all that detail to Google (Zenrin?) has helped them with this feature.

I got the update when opening maps on my computer today, overall it's a great improvement, and I agree with what your thoughts, Jake, though I am a bit annoyed about the same color scheme for freeways and main roads. I'd be interested to know why you don't think it's important since I do find it quite useful to be able to see a region's freeway system at a glance without having to look closely to spot minor differences in the lines (especially in an area with which I am not familiar). It was already somewhat difficult to tell them apart when they changed the colors a few years ago and made them have less contrast.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 02, 2020, 02:53:48 AM
Quote from: stevashe on September 01, 2020, 11:45:44 PM
I got the update when opening maps on my computer today, overall it's a great improvement, and I agree with what your thoughts, Jake, though I am a bit annoyed about the same color scheme for freeways and main roads. I'd be interested to know why you don't think it's important since I do find it quite useful to be able to see a region's freeway system at a glance without having to look closely to spot minor differences in the lines (especially in an area with which I am not familiar). It was already somewhat difficult to tell them apart when they changed the colors a few years ago and made them have less contrast.

My general argument was that "freeway" is just too loose of a term in the US to make it a special color. In most areas that I've seen, the yellow surface routes are just as important as freeways.

As an example, there's really no reason for WA-410 in Sumner to appear differently from WA-410 in Bonney Lake or Enumclaw. It's the same users for both roads, and the only difference is maybe 10 mph in speed limit, and the existence of on and off-ramps. Otherwise: bikes, tractors, and everyone else can still use the road. Things are different for many stretches of "Interstate", but then are we going to use an exclusive color for interstates? It gets complicated, and I feel this is a good compromise.

One thing worth pointing out: prior to this update, there were stretches of "freeway" colored more like surface roads, and surface roads incorrectly colored as freeways. This solves that completely, since "what is a freeway" varies way too often, even amongst users here (eg: US-395 south of Ritzville?? WA-8 west of Olympia??).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on September 02, 2020, 07:37:35 AM
So...since we couldn't perfectly color freeways and roads differently, we are just going to color them all the same?  That's not a solution.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on September 02, 2020, 09:01:26 AM
I browse Google Maps almost exclusively with traffic on, so I hadn't noticed that surface streets and freeways are now the same color.
I did notice the traffic signal icon, which is cool. It will be nice to know at a glance whether there is one at a given location.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on September 02, 2020, 09:59:08 AM
Quote from: jakeroot on September 02, 2020, 02:53:48 AM
My general argument was that "freeway" is just too loose of a term in the US to make it a special color. In most areas that I've seen, the yellow surface routes are just as important as freeways.

I strongly disagree with this. Most yellow surface routes I come upon are urban arterials that actually don't move that fast and have a lot of lights. Look at Atlanta for an example - there's a lot of yellow, but the only freeways are the interstates plus GA 400, 166, and 78 and 141 east of I-285.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 02, 2020, 10:13:11 AM
Quote from: stevashe on September 01, 2020, 11:45:44 PM
I am a bit annoyed about the same color scheme for freeways and main roads. I'd be interested to know why you don't think it's important since I do find it quite useful to be able to see a region's freeway system at a glance without having to look closely to spot minor differences in the lines (especially in an area with which I am not familiar).

I'd suggest that what I've bolded is not a common use of Google Maps, other than by roadgeeks.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 02, 2020, 01:02:42 PM
Quote from: US 89 on September 02, 2020, 09:59:08 AM
Quote from: jakeroot on September 02, 2020, 02:53:48 AM
My general argument was that "freeway" is just too loose of a term in the US to make it a special color. In most areas that I've seen, the yellow surface routes are just as important as freeways.

I strongly disagree with this. Most yellow surface routes I come upon are urban arterials that actually don't move that fast and have a lot of lights. Look at Atlanta for an example - there's a lot of yellow, but the only freeways are the interstates plus GA 400, 166, and 78 and 141 east of I-285.
Exactly.

Quote from: jakeroot on September 02, 2020, 02:53:48 AM
Quote from: stevashe on September 01, 2020, 11:45:44 PM
I got the update when opening maps on my computer today, overall it's a great improvement, and I agree with what your thoughts, Jake, though I am a bit annoyed about the same color scheme for freeways and main roads. I'd be interested to know why you don't think it's important since I do find it quite useful to be able to see a region's freeway system at a glance without having to look closely to spot minor differences in the lines (especially in an area with which I am not familiar). It was already somewhat difficult to tell them apart when they changed the colors a few years ago and made them have less contrast.

My general argument was that "freeway" is just too loose of a term in the US to make it a special color. In most areas that I've seen, the yellow surface routes are just as important as freeways.

As an example, there's really no reason for WA-410 in Sumner to appear differently from WA-410 in Bonney Lake or Enumclaw. It's the same users for both roads, and the only difference is maybe 10 mph in speed limit, and the existence of on and off-ramps. Otherwise: bikes, tractors, and everyone else can still use the road. Things are different for many stretches of "Interstate", but then are we going to use an exclusive color for interstates? It gets complicated, and I feel this is a good compromise.

One thing worth pointing out: prior to this update, there were stretches of "freeway" colored more like surface roads, and surface roads incorrectly colored as freeways. This solves that completely, since "what is a freeway" varies way too often, even amongst users here (eg: US-395 south of Ritzville?? WA-8 west of Olympia??).
Google has been getting worse with that over the years, especially since they seemed to adopt MapQuest's "freeway ends at last interchange, not the first at-grade" system at some point.  They should look at OSM, which tends to get it right (although not perfect - OSM has A-15 as a freeway to the border, when it should really downgrade to an arterial at the last at-grade).

At this point, Google won't let me go back to the old design, even by loading it in fresh incognito sessions multiple times until I get what I want (I tried over a dozen times this morning).  With that, I will no longer be able to use Google exclusively anymore.  I cannot get used to how freeways and arterials are identical at many zooms, and so close together that I have to practically squint to tell the difference at others.  That means I'll have to use OSM for browsing, and then drop into Google for street view, traffic, driving directions, and place info.  So inconvenient.

And to think I thought the last design was bad.  Now I'm practically pining for it.

Quote from: kphoger on September 02, 2020, 10:13:11 AM
Quote from: stevashe on September 01, 2020, 11:45:44 PM
I am a bit annoyed about the same color scheme for freeways and main roads. I'd be interested to know why you don't think it's important since I do find it quite useful to be able to see a region's freeway system at a glance without having to look closely to spot minor differences in the lines (especially in an area with which I am not familiar).

I'd suggest that what I've bolded is not a common use of Google Maps, other than by roadgeeks.
Still not a reason to get rid of the functionality.  And what does Google think people did with paper maps?  Functionality should never be removed by a product unless it's used by nobody (not "not many people", literally nobody) or is wholly redundant with other functionality (ie, the other functionality covers everything the old function could do just as well and with no loss of convenience or anything else, for anyone or any use case).
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 02, 2020, 01:05:56 PM
Quote from: vdeane on September 02, 2020, 01:02:42 PM
I cannot get used to how freeways and arterials are identical at many zooms, and so close together that I have to practically squint to tell the difference at others.

This has been the case for several years now.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 02, 2020, 01:17:15 PM
Quote from: 1 on September 02, 2020, 01:05:56 PM
Quote from: vdeane on September 02, 2020, 01:02:42 PM
I cannot get used to how freeways and arterials are identical at many zooms, and so close together that I have to practically squint to tell the difference at others.

This has been the case for several years now.
I've been able to tell them apart (although not as well as one once could) until this last update.  There was a difference in shade... muted from what it used to be, but still there.  That is gone now.  The thickness difference was also easier to see.  Google Maps is just an ugly sea of brownish yellow and green to my eyes with this last design.  The only upside I can think of to the new design is that one no longer needs to have their monitor brightness/contrast very precisely calibrated to see half the roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on September 02, 2020, 02:41:28 PM
Quote from: vdeane on September 02, 2020, 01:17:15 PM
Quote from: 1 on September 02, 2020, 01:05:56 PM
Quote from: vdeane on September 02, 2020, 01:02:42 PMI cannot get used to how freeways and arterials are identical at many zooms, and so close together that I have to practically squint to tell the difference at others.

This has been the case for several years now.

I've been able to tell them apart (although not as well as one once could) until this last update.  There was a difference in shade... muted from what it used to be, but still there.  That is gone now.  The thickness difference was also easier to see.  Google Maps is just an ugly sea of brownish yellow and green to my eyes with this last design.  The only upside I can think of to the new design is that one no longer needs to have their monitor brightness/contrast very precisely calibrated to see half the roads.

I've played around with my local area, which has been changed over and has a number of freeways (US 54-400 at both ends and K-254 near its west end) that become expressways or divided arterials.  There is indeed no longer a color distinction between freeways and non-freeways, but at zoom levels less than 16, breaks in control of access are indicated by outlining across the roadway that is more or less identical to the outlining used for freeway segments.  Most surface arterials continue to be shown as white.

Atlanta also seems to be similar.  I explored SR 400, which has its first at-grade intersection at SR 369 (Browns Bridge Road), and the outlining across the roadway is present there too.

As for consistency in what Google considers a freeway and non-freeway, I am not seeing much.  In the Wichita area, end of freeway for K-254 is shown at Rock Road (first at-grade intersection)--similar to SR 400 in Georgia--but east end of the Kellogg freeway (admittedly, still under construction with no clarity as to how K-Tag-only interchanges are to be handled) is shown at ramp terminals.  I don't know where Google is getting its information on limits of access control, but suspect it may not be collected on a consistent basis from state to state.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 02, 2020, 03:56:42 PM
Quote from: Rothman on September 02, 2020, 07:37:35 AM
So...since we couldn't perfectly color freeways and roads differently, we are just going to color them all the same?  That's not a solution.

It's not just "roads". We're coloring freeways and extremely important surface roads as yellow. It's not every surface road and freeway yellow. Important distinction.

Quote from: US 89 on September 02, 2020, 09:59:08 AM
Quote from: jakeroot on September 02, 2020, 02:53:48 AM
My general argument was that "freeway" is just too loose of a term in the US to make it a special color. In most areas that I've seen, the yellow surface routes are just as important as freeways.

I strongly disagree with this. Most yellow surface routes I come upon are urban arterials that actually don't move that fast and have a lot of lights. Look at Atlanta for an example - there's a lot of yellow, but the only freeways are the interstates plus GA 400, 166, and 78 and 141 east of I-285.

But, (A) even in Atlanta, there aren't that many yellow surface routes, and (B) those that are colored yellow, I'd argue are extremely important roads. Not necessarily for cross-region traffic, but important for the community in terms of how it connects areas not directly tied to freeways.

Looking at Salt Lake City, should Bangerter really have a different color than the 15 or 215 freeways? Should it change color every time it hits a signal? IMO, it is just as deserving of that yellow color as any other freeway in SLC. What exactly Google considers important enough for yellow surface routes, I couldn't say. That's probably a point of contention, I'll concede. But I still think this is the right approach.

Quote from: J N Winkler on September 02, 2020, 02:41:28 PM
As for consistency in what Google considers a freeway and non-freeway, I am not seeing much.  In the Wichita area, end of freeway for K-254 is shown at Rock Road (first at-grade intersection)--similar to SR 400 in Georgia--but east end of the Kellogg freeway (admittedly, still under construction with no clarity as to how K-Tag-only interchanges are to be handled) is shown at ramp terminals.  I don't know where Google is getting its information on limits of access control, but suspect it may not be collected on a consistent basis from state to state.

I would argue that this inconsistency is one of the key arguments against different colors for "freeways", since data quality can vary substantially from state to state. Never mind state to state differences in "what is a freeway". I feel that Google's attempts to find a middle ground have been hit and miss, and I feel that their new approach is better for users. Just my two cents.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 02, 2020, 03:59:54 PM
Quote from: vdeane on September 02, 2020, 01:02:42 PM
Quote from: kphoger on September 02, 2020, 10:13:11 AM
Quote from: stevashe on September 01, 2020, 11:45:44 PM
I am a bit annoyed about the same color scheme for freeways and main roads. I'd be interested to know why you don't think it's important since I do find it quite useful to be able to see a region's freeway system at a glance without having to look closely to spot minor differences in the lines (especially in an area with which I am not familiar).

I'd suggest that what I've bolded is not a common use of Google Maps, other than by roadgeeks.

Still not a reason to get rid of the functionality.  And what does Google think people did with paper maps?  Functionality should never be removed by a product unless it's used by nobody (not "not many people", literally nobody) or is wholly redundant with other functionality (ie, the other functionality covers everything the old function could do just as well and with no loss of convenience or anything else, for anyone or any use case).

Paper maps often used the same color for many of the roads, with the variation being how the line appears on the map (thick vs thin, dashed vs solid, etc). Freeways in this Seattle map from 1970 (below) are shown as dual strokes. This is not at all unlike how Google Maps shows freeways today, with two adjacent strokes.

(https://legacy.lib.utexas.edu/maps/world_cities/seattle.jpg) [(https://i.imgur.com/9bHdqgJ.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 02, 2020, 04:03:29 PM
jakeroot, look at the region bounded by I-81, I-90, I-87, and NY 17. Then look inside the Beltway in Maryland. Then between Miami and West Palm Beach. Some areas have WAY too many yellow roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 02, 2020, 04:21:00 PM
Quote from: 1 on September 02, 2020, 04:03:29 PM
jakeroot, look at the region bounded by I-81, I-90, I-87, and NY 17. Then look inside the Beltway in Maryland. Then between Miami and West Palm Beach. Some areas have WAY too many yellow roads.

It's very likely that the data Google is receiving for those areas meets their criteria for yellow. I couldn't tell you why this is.

At the very least, until Google refines their algorithm for what meets their standards for yellow (not super easy given the sheer number of data sources), freeways are still thicker, and do layer over surface routes. On this image, I can very clearly see which routes are "freeways":

(https://i.imgur.com/wGgpAdJ.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 02, 2020, 04:47:27 PM
But then take that view and compare it to a state DOT map at a similar scale and there's really no excuse for what Google's putting out–
(https://i.imgur.com/Abi2e8q.png)

I'll take the KDOT cartography every time, thanks. The only thing that Google Maps has going for it is its convenient zoomable interface (which OSM has too, so not a huge deal) and the integration of things like Street View. Cartographically, it's complete trash.

But I suspect that Google Maps development is being driven by the marketing department, not anyone with a GIS degree.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 02, 2020, 04:51:04 PM
Quote from: Scott5114 on September 02, 2020, 04:47:27 PM
But then take that view and compare it to a state DOT map at a similar scale and there's really no excuse for what Google's putting out–

(https://i.imgur.com/Abi2e8q.png)

I'll take the KDOT cartography every time, thanks. The only thing that Google Maps has going for it is its convenient zoomable interface (which OSM has too, so not a huge deal) and the integration of things like Street View. Cartographically, it's complete trash.

But I suspect that Google Maps development is being driven by the marketing department, not anyone with a GIS degree.

Why aren't you complaining that Kellogg and K-96 (freeways) are shown as the same color as K-254, K-15, S Broadway, and Southwest Blvd (not freeways)?
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on September 02, 2020, 07:03:58 PM
Quote from: jakeroot on September 02, 2020, 03:56:42 PM
Looking at Salt Lake City, should Bangerter really have a different color than the 15 or 215 freeways? Should it change color every time it hits a signal? IMO, it is just as deserving of that yellow color as any other freeway in SLC. What exactly Google considers important enough for yellow surface routes, I couldn't say. That's problem a point of contention, I'll concede. But I still think this is the right approach.

OK, Bangerter is maybe fine as it is, but it absolutely should not be a different color than any of the Mountain View Corridor (SR 85) - which Google doesn't even show as an arterial. And some surface streets are randomly upgraded - there's barely any difference between 126th South or 114th South (which are yellow) and 106th South or 90th South (which are not). Those are all just urban arterials that don't really resemble anything more than a semi-expressway at best. State Street really shouldn't be yellow if Redwood, 7th East, and Van Winkle (an expressway!) can't be as well. And so on.

Overall, my number one issue is that it's totally random what they decide should and shouldn't be worthy of a yellow road - and it has a massive impact on the user end. And the concept of what gets upgraded to yellow seems to be extremely inconsistent between urban areas (places like SLC have very little yellow surface road mileage, while places like Denver and Atlanta have significantly more). Compare Candler Road near Atlanta (https://goo.gl/maps/TLiFb1NoN6G2S2ds5) (a yellow road) with Pioneer Crossing near Salt Lake (https://goo.gl/maps/DpaF7MmzkiBeoGYt8) (not a yellow road). I don't get it.

There needs to be a better way to pick apart freeways, expressways, larger urban arterials, and smaller urban connecting routes on a map that's consistent from city to city. I don't know the answer to that question (though I'd guess it probably involves more colors for different grades of road). But whatever it is, Google is getting farther and farther from it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 02, 2020, 08:19:30 PM
Quote from: kphoger on September 02, 2020, 04:51:04 PM
Quote from: Scott5114 on September 02, 2020, 04:47:27 PM
But then take that view and compare it to a state DOT map at a similar scale and there's really no excuse for what Google's putting out–

(https://i.imgur.com/Abi2e8q.png)

I'll take the KDOT cartography every time, thanks. The only thing that Google Maps has going for it is its convenient zoomable interface (which OSM has too, so not a huge deal) and the integration of things like Street View. Cartographically, it's complete trash.

But I suspect that Google Maps development is being driven by the marketing department, not anyone with a GIS degree.

Why aren't you complaining that Kellogg and K-96 (freeways) are shown as the same color as K-254, K-15, S Broadway, and Southwest Blvd (not freeways)?

Older KDOT maps had a special red-and-black line for non-Interstate freeways. And I'm not sure why they stopped using it. But the current map is still way better than Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 03, 2020, 03:15:49 AM
Quote from: US 89 on September 02, 2020, 07:03:58 PM
Overall, my number one issue is that it's totally random what they decide should and shouldn't be worthy of a yellow road - and it has a massive impact on the user end.

Without quoting everything: I actually agree with most of what you're saying. There are clear inconsistencies that need to be tied up at some point. Although these issues with yellow vs non yellow have existed for some time. It just seems to be a bigger issue now that freeways are the same color (although they are not the same thickness and always show above surface roads -- an important point).

But as to your quote: I simply don't agree that the roads that are colored yellow vs non yellow are truly having a "massive impact" on those using Google Maps. There are inconsistencies between regions, but most people are only looking at their city, so that's not really a problem. And those that are looking at their city, are we really supposed to believe that the user is somehow having only half an experience thanks to too many yellow surface roads? Or that not being able to immediately recognize freeways is somehow ruining the experience?

No one here seems to recognize the purpose of Google Maps relative to something like OSM: most using Google Maps aren't just farting around looking at roads and complaining about colors. They're actually using the service to locate businesses, find directions, or mark stuff or whatever. These things have been made much faster and easier with recent updates. OSM is much better for "looking at roads" because of their classification system (which, true to real life, seems to vary from state to state -- don't tell me OSM is perfect) but without Street View, it's only half a service in my opinion.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 03, 2020, 09:56:28 AM
Quote from: Scott5114 on September 02, 2020, 08:19:30 PM
But the current map is still way better than Google Maps.

Other than little squares, how can you tell a freeway apart from a non-freeway on that map?  That's the whole problem people are having with Google Maps right now.

Broadway south of 47th has stoplights and doesn't even have a median–yet it's drawn the same color as Kellogg, which is a six-lane divided freeway.  That's not "way better than Google Maps".

(https://i.imgur.com/56GioJM.png)

(https://i.imgur.com/CzFgvqh.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 03, 2020, 10:47:29 AM
While I agree that the colors of freeway and non-freeway are hard to tell apart, I should point out that they aren't the exact same color.  For example, here I've illustrated where you can tell one color changes to the other.  (One of them is obscured by words.)

(https://i.imgur.com/9njYVYs.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 03, 2020, 11:21:41 AM
Quote from: vdeane on September 02, 2020, 01:02:42 PM
At this point, Google won't let me go back to the old design, even by loading it in fresh incognito sessions multiple times until I get what I want (I tried over a dozen times this morning).  With that, I will no longer be able to use Google exclusively anymore. 

Have you tried google.com/mymaps with the base map called 'Map'?  For me, at least, that still gives me the previous rendering.  Of course, it's only good for looking at, not for directions or anything.
Title: Re: Google Maps just fucking SUCKS now
Post by: Ben114 on September 03, 2020, 11:37:52 AM
There's only one thing that bugs me with the redesign. When in the "traffic" view, the new orange border for freeways is way too similar to the orange traffic color.

(https://i.imgur.com/RXsSMvi.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 03, 2020, 02:31:31 PM
Quote from: kphoger on September 03, 2020, 10:47:29 AM
While I agree that the colors of freeway and non-freeway are hard to tell apart, I should point out that they aren't the exact same color.  For example, here I've illustrated where you can tell one color changes to the other.  (One of them is obscured by words.)

(https://i.imgur.com/9njYVYs.png)

This is one point that is not getting enough attention. I can still tell them apart, even being the same color. The lines are not exactly the same: freeways are thicker, and layer above surface routes. They also have heavier borders when zoomed out.

I'm not even going to put an arrow on which are the freeways in these images. It's still that obvious to me. Subtle compared to making them like bright blue, but cartography is deeper than just a rainbow of colors.

(https://i.imgur.com/wPs8rID.png)

(https://i.imgur.com/iFkx5s8.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 03, 2020, 04:02:57 PM
Fine, then. I didn't ever want to have to do this. But it's come to this.
ODOT isn't the worst at something.

(https://i.imgur.com/xgWVot0.png)

Google is the ODOT of cartography. Yeah, I said it. Cause ODOT is actually better than Google at cartography. Pathetic that I can say that, but here we are.

Those Interstate shields are ugly as shit, and putting two numbers in one shield on duplexes is the bane of my existence. And I will never understand the decision to make two-lane roads be blue. But you know what? As ugly as the ODOT map is, it's actually easy to tell apart what type of road is what. So yeah, on this one, I like the organization that gave us the Craig County sign better than Google.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 03, 2020, 04:21:41 PM
^^^^
No offence: that is just not a good map unless the point of the map was to show freeways and expressways.

There is other stuff on the map, but it's hidden away in the background thanks to very distracting freeway lines.

Google Maps HAS to strike a balance between everything, since it's way more than a digital road atlas.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 03, 2020, 04:53:17 PM
Keep in mind that's also a PNG screenshot of a PDF, so there is aliasing.

It is a good map because the freeway lines are "distracting". There is a clear hierarchy of importance between the map symbols, and the eye is drawn to the most important ones. This is how maps are supposed to work. "Oklahoma City" is set with the biggest type because it is the most important city. Newcastle is much smaller because it's a smaller and unimportant city. That's not "hiding it away", it's de-emphasizing it to get it out of the way so that the more prominent features stick out better.

Of course, with the way things are going, in 2022 Google Maps is going to just display a plain grey square when you open it and someone on here will be like "I love the new Google Maps! It's so convenient that when I touch the map, the phone reads reviews for local plumbing businesses at full volume without any way of stopping it!"
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 03, 2020, 05:03:25 PM
Quote from: Scott5114 on September 03, 2020, 04:53:17 PM
It is a good map because the freeway lines are "distracting". There is a clear hierarchy of importance between the map symbols, and the eye is drawn to the most important ones. This is how maps are supposed to work. "Oklahoma City" is set with the biggest type because it is the mos

But not all maps are about viewing roads, Scott. My eyes are drawn to the freeways, and everything else drifts into the background. That is brilliant for a map of road networks, but not for a map that is also meant to show dozens of other things. That map from ODOT is about viewing roads; well done them. Google Maps is more than that. Google Maps will never look like that map, because Google Maps is more than just roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 03, 2020, 06:56:51 PM
I understand what you're saying, but I don't think it's relevant to the underlying issue here. If all the roads had to be the same shade of orange because ferries were using blue lines, and transit was using red lines, and walking paths were using purple–okay, then you'd have a point. But they're not. A typical video card can show 16,777,216 (2563) colors, so why must everything be orange?

Besides, if you have that many competing use cases, the better thing to do would be to create different tilesets that you can switch to, so that the user can choose what is important to them. It'd be really neat if you could press a Transit button and have all of NYC's subway lines mapped out in glorious detail, with only the most major streets shown to provide context of where they connect. Or a Bike button where roads with bike lanes are the big, bold ones and everything else falls away. (This would not be terribly difficult to do with GIS software. It would be processor intensive to initially render the tiles, but it would be an entirely automated process.)

But the most common use case for Google Maps is road transportation. This was an actual issue for me when I was in Spearman, Texas this past Saturday and was trying to figure out how to get from to FM 759 from the gas station that I was at. It was harder than it needed to be because while the line for FM 759 is slightly thicker than the others, it's the same shade of white as everything else in town. My solution was actually to get out of the car and walk around the gas station lot until I could spot a FM 759 sign.

I don't have to give them points for homogenizing their legend because they are trying to put too many things on the map. That just means that instead of doing one thing well, they are choosing to do a lot of things poorly.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 03, 2020, 07:06:55 PM
Quote from: Scott5114 on September 03, 2020, 06:56:51 PM
It'd be really neat if you could press a Transit button and have all of NYC's subway lines mapped out in glorious detail, with only the most major streets shown to provide context of where they connect.

Apple Maps actually does this.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 03, 2020, 08:36:56 PM
I think it's interesting that the people pushing "you can tell the freeways from the arterials just fine" always use pictures from zoom levels where the difference is at is maximum.  Still, that doesn't deny that it's much harder than it was (which was itself harder than it was before that).  And I would dispute the idea that it's impossible to both show the roads well and show everything else.  I mean, what actual problem does the new rendering solve?  It strikes me as a gimmick that doesn't really add functionality (are people looking for accurate features really using map view instead of satellite?) - and I don't think the roads need to be so homogeneous to make it work, either.

In any case, we now have a new issue.  Google has changed how they calculate drive times.  While it will help people doing drives in the near term, what if you're planning a trip for well into the future, once things go back to normal?  And after that, the new system still won't deal well with things like seasonal variation.  Google is sacrificing planning accuracy for immediate gains - and honestly, is a drive that goes faster than planned a problem?
https://www.cnbc.com/2020/09/03/covid-19-forced-google-maps-to-change-how-it-predicts-traffic.html
Title: Re: Google Maps just fucking SUCKS now
Post by: Kulerage on September 03, 2020, 08:42:03 PM
They should've just kept how it was c. 2018, where every road was orange, but freeways were a noticeably more red orange. Minimal change to how it is now, wouldn't hurt anyone.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 04, 2020, 10:37:47 AM
Quote from: vdeane on September 03, 2020, 08:36:56 PM
it's much harder than it was (which was itself harder than it was before that) ... I mean, what actual problem does the new rendering solve?

This is most certainly true.  I really do wonder why Google chose to make the colors more similar.  We can debate whether they're still decently easy to distinguish or not, but the fact remains that there was apparently a conscious decision to make them more similar.  What could possibly have prompted that decision?

Quote from: vdeane on September 03, 2020, 08:36:56 PM
And I would dispute the idea that it's impossible to both show the roads well and show everything else ... and I don't think the roads need to be so homogeneous to make it work, either.

This is also true.  I can concede that, several years ago, it was kind of difficult to pick businesses out on the map;  but, now, it's quite difficult to pick city streets out at close zoom levels–to the point that I sometimes wonder if a gap between businesses is a street or just a parking lot or just some vacant space.  There has to be a good middle ground, and I think this latest iteration has overshot the mark.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on September 04, 2020, 12:15:44 PM
Quote from: vdeane on September 03, 2020, 08:36:56 PMIn any case, we now have a new issue.  Google has changed how they calculate drive times.  While it will help people doing drives in the near term, what if you're planning a trip for well into the future, once things go back to normal?  And after that, the new system still won't deal well with things like seasonal variation.  Google is sacrificing planning accuracy for immediate gains - and honestly, is a drive that goes faster than planned a problem?

I'm not sure how much that adjustment will actually add to our current troubles:  broken is broken.  Google Maps will not give accurate drive times (or even routings) for itineraries that include a closure that will be lifted by the time the trip is undertaken, times quoted assume immediate departure since there is no way to specify a planned time for the trip, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 04, 2020, 12:29:54 PM
Quote from: J N Winkler on September 04, 2020, 12:15:44 PM
I'm not sure how much that adjustment will actually add to our current troubles:  broken is broken.  Google Maps will not give accurate drive times (or even routings) for itineraries that include a closure that will be lifted by the time the trip is undertaken, times quoted assume immediate departure since there is no way to specify a planned time for the trip, etc.

But how difficult would it be to add this?

(https://i.imgur.com/C4Jvm06.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on September 04, 2020, 12:39:59 PM
Quote from: kphoger on September 04, 2020, 12:29:54 PMBut how difficult would it be to add this?

(https://i.imgur.com/C4Jvm06.png)

I see your point--I hadn't actually realized that those options (as well as the ability to select departure time) had been added.  Has anything been done about the fact speeders are in the mix for averaging journey times?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 04, 2020, 12:55:00 PM
Quote from: J N Winkler on September 04, 2020, 12:39:59 PM
Has anything been done about the fact speeders are in the mix for averaging journey times?

I don't see that as a problem.  I figure Google Maps gives me the average travel time of people who use the roads.  If I'm slower than the prevailing speed, then I should add time;  if I'm faster than the prevailing speed, then I should subtract time.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 04, 2020, 08:49:15 PM
But how much time?  That's the thing - if your speed doesn't average out to the prevailing speed of traffic, it gets hard to estimate.  I've flirted with the idea of driving the speed limit instead of 5-7 over, but I'm stopped by two things every time I think of it:
-The unreasonably low freeway speed limits in the northeast (along with some surface roads, such as the Mid-Hudson Bridge)
-The fact that my currently spot-on Google Maps drive times would become significantly underestimated

IMO and overestimated time is far better than an underestimated time.




Meanwhile on the cartographic side, I've noticed something interesting: the new style looks much, much better on my laptop (Vista - the superhero (https://worm.fandom.com/wiki/Vista), not the operating system) than my desktop (Antares).  At the zoom levels where it's possible to differentiate freeways and arterials due to width, it is far, far easier to do so on Vista than Antares.  I'm not sure why - they both run the Cinnamon edition of Linux Mint 20 Ulyana, but Vista has a much higher DPI (resulting in a screen area that's at least 50% larger, even though the physical screen size is smaller).  Maybe it's the video cards (Antares uses a Nvidia card with proprietary drivers, though such doesn't increase the available screen resolution; Vista uses an integrated Intel card that has no need of proprietary drivers).  Maybe it's the ASUS monitor (which isn't that old, but maybe it's not as good as I thought).  Or maybe it's the Wretch (https://worm.fandom.com/wiki/Victoria_Dallon#The_Wretch).  I don't know.  Either way, a lot of design decisions (on a lot of websites - not just Google Maps) make a lot more sense on Vista's higher-DPI display.

One thing I don't like on either computer is how the ability to differentiate the two goes away as one zooms in, eventually going away entirely.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on September 04, 2020, 09:54:40 PM
Another new thing I spotted on Google Maps today: they're now marking where traffic lights are if you zoom in pretty close.

https://www.google.com/maps/@29.4822412,-95.4002892,65m/data=!3m1!1e3

I'm not too sure what I think about this. On one hand it's cool to see where they are without having to use street view, but on the other hand I can see it getting cluttered. What will they add next, stop signs?
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on September 04, 2020, 10:04:49 PM
Quote from: CoreySamson on September 04, 2020, 09:54:40 PM
Another new thing I spotted on Google Maps today: they're now marking where traffic lights are if you zoom in pretty close.

https://www.google.com/maps/@29.4822412,-95.4002892,65m/data=!3m1!1e3

I'm not too sure what I think about this. On one hand it's cool to see where they are without having to use street view, but on the other hand I can see it getting cluttered. What will they add next, stop signs?
I've already noticed the light feature; it works for some beacons also imo. It's not really helpful since you have to zoom in pretty close to see them; if you could toggle a light feature on/off and see them when zoomed out further than I (a big traffic signal geek) would be really interested.
Title: Re: Google Maps just fucking SUCKS now
Post by: Katavia on September 07, 2020, 08:51:37 PM
Pictured: Google Maps gets drunk and thinks NC 3 is also SR 1609.
(https://i.ibb.co/GRxtsTH/Screenshot-2020-09-07-at-8-36-54-PM.png)
Freeway colors and importance hierarchies are one thing, but I would think El Goog could at least get a route number straight? Clicking around on the main map correctly returns "NC 3". Street View also calls it "State Rd 1609", despite the fact that SR 1609 isn't assigned to any street in Cabarrus County whatsoever.
(https://i.ibb.co/f21nQBj/Screenshot-2020-09-07-at-8-40-07-PM.png)
https://goo.gl/maps/y53aWLxfEMocddU79 (https://goo.gl/maps/y53aWLxfEMocddU79)
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on September 12, 2020, 05:20:27 PM
In case anyone didn't know and wants to know, here is how you can blur out your home on street view:

1. Go to Google Maps and enter your home address

2. Enter into Street View mode by dragging the small yellow human-shaped icon, found in the bottom-right corner of the screen, onto the map in front of your house

3. With your house in view, click "Report a problem" in the bottom-right corner of the screen

4. Center the red box on your home, and select "My home" in the "Request blurring" field

https://mashable.com/article/how-to-blur-your-house-on-google-street-view/
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 12, 2020, 07:23:19 PM
Quote from: Plutonic Panda on September 12, 2020, 05:20:27 PM
In case anyone didn't know and wants to know, here is how you can blur out your home on street view:

1. Go to Google Maps and enter your home address

2. Enter into Street View mode by dragging the small yellow human-shaped icon, found in the bottom-right corner of the screen, onto the map in front of your house

3. With your house in view, click "Report a problem" in the bottom-right corner of the screen

4. Center the red box on your home, and select "My home" in the "Request blurring" field

https://mashable.com/article/how-to-blur-your-house-on-google-street-view/

Can I blur out Yankee Stadium in this way?
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on September 12, 2020, 08:31:39 PM
Quote from: 1 on September 12, 2020, 07:23:19 PM
Quote from: Plutonic Panda on September 12, 2020, 05:20:27 PM
In case anyone didn't know and wants to know, here is how you can blur out your home on street view:

1. Go to Google Maps and enter your home address

2. Enter into Street View mode by dragging the small yellow human-shaped icon, found in the bottom-right corner of the screen, onto the map in front of your house

3. With your house in view, click "Report a problem" in the bottom-right corner of the screen

4. Center the red box on your home, and select "My home" in the "Request blurring" field

https://mashable.com/article/how-to-blur-your-house-on-google-street-view/

Can I blur out Yankee Stadium in this way?

If the guy from Chicago can reroute all of UPS's mail to his apartment, I think blurring a landmark on Google Maps shouldn't be a problem. I don't even think anyone would look twice.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 12, 2020, 08:56:22 PM
Quote from: Plutonic Panda on September 12, 2020, 05:20:27 PM
In case anyone didn't know and wants to know, here is how you can blur out your home on street view:

Why would you want to, though? If you could go by my house on GSV now (it's actually inexplicably never been mapped) it's just an unremarkable house. If there's a big honking blur there, that attracts attention.

Besides, in my county (and most counties in Oklahoma) you can get photos of houses along with the full names of their owners off the county assessor's website.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on September 12, 2020, 09:49:55 PM
Quote from: Scott5114 on September 12, 2020, 08:56:22 PM
Quote from: Plutonic Panda on September 12, 2020, 05:20:27 PM
In case anyone didn't know and wants to know, here is how you can blur out your home on street view:

Why would you want to, though? If you could go by my house on GSV now (it's actually inexplicably never been mapped) it's just an unremarkable house. If there's a big honking blur there, that attracts attention.

Besides, in my county (and most counties in Oklahoma) you can get photos of houses along with the full names of their owners off the county assessor's website.
I suppose the same reason people live in gated communities. If someone really wants to get in they'll get in. Just an extra layer of security. Me personally, I'm not blurring out my house as I don't see the point.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 13, 2020, 12:18:21 AM
Except I don't think it's even a security measure. It's more like hanging a neon sign in your window that says "NOTHING TO SEE HERE".

Besides, I'd be more concerned with satellite view than Street View. Street View can't see anything that someone driving by couldn't see, whereas satellite view can see into fenced-off areas.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 13, 2020, 02:03:10 PM
I make a point of visiting homes that have been blurred to see what the hell is so fishy.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on September 13, 2020, 05:37:12 PM
What I hate about the blurring sometimes is that if someone requests a blur, the only GSV imagery available is the shitty 2007-2009 passbys but nothing from 2013-onward, even if the road was covered more recently. Back when Geoguessr worked well (before all the adblocker blockers and pay accounts), I saw a pretty major road that had the crappy imagery because there was one car on the road that had requested a blur. Sure enough, I went back to Google Maps itself and followed that road, crappy imagery throughout the road until the one blurry car drove onto/off of it, then great imagery again.

In typing the last words of that previous sentence, I wonder if in the future, people will request blurs on their house because they had something incendiary hanging off their front porch when GSV drove by, like say Ronald Thump paraphernalia...
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 13, 2020, 07:51:40 PM
I noticed something interesting: the new Google Maps symbology has brought back the distinction between toll roads and free roads for freeways.  Unfortunately, this distinction only exists when zoomed in closely.  Interestingly, freeways and arterials handle it oppositely - freeways become more wispy, while arterials have darker outlines.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on September 13, 2020, 09:05:43 PM
Quote from: jakeroot on September 13, 2020, 02:03:10 PM
I make a point of visiting homes that have been blurred to see what the hell is so fishy.

Ever find anything interesting?  Retired celebrities?  People on the sex offender list?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 14, 2020, 01:55:51 AM
Quote from: kkt on September 13, 2020, 09:05:43 PM
Quote from: jakeroot on September 13, 2020, 02:03:10 PM
I make a point of visiting homes that have been blurred to see what the hell is so fishy.

Ever find anything interesting?  Retired celebrities?  People on the sex offender list?

Old woman chasing me with a tire iron!

Actually never seen anything special. Which only makes me more curious as to what they think they're hiding by blurring their home. It's not like it's actually blurred in real life.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on September 14, 2020, 03:50:43 PM
Newest Street View right now that I can find is June 2020 (https://www.google.com/maps/@39.9520248,-75.1601432,3a,75y,150.18h,92.51t/data=!3m6!1e1!3m4!1sAF1QipP35UN1qulWaKquI5aiQrCY4Rrnx-_W3Q0Sm9DM!2e10!7i5504!8i2752/), and some of the user-submitted content is...not great.
Title: Re: Google Maps just fucking SUCKS now
Post by: briantroutman on September 17, 2020, 02:34:45 PM
Over the past few weeks, I've noticed that Google Maps now uses a light green background to denote what assumably are undeveloped or rural areas (not to be confused with the slightly darker green used for designated parks and forest areas). Developed or urban areas retain a gray background unless color coded for another purpose. But I've noticed some unusual inconsistencies (and downright inaccuracies) in how the gray/green colors are applied, and I'm wondering if anyone here knows what factors Google uses in determining what's urban vs. rural.

For example, the entirety of the City of Philadelphia is expectably color-coded as urban, and as you progress westward, so are all of the inner-ring suburbs inside of I-476 as well as the Borough of Media. Then from there, the background changes to green along a line that's precisely congruent with the eastern border of Middletown Township.

(https://live.staticflickr.com/65535/50353272082_6fbe0ec136_o.png)

Yet at the center, there's a gray area that corresponds to the CDP of Lima, PA. This despite the fact that the Lima CDP (arguably useless and out-of-date) includes undeveloped forested areas while other nearby developed areas (particularly along US 1) are color-coded green on Google Maps.

(https://live.staticflickr.com/65535/50353272092_e448dfd23d_o.png)

Elsewhere across the state:

The Borough of New Morgan (I was unaware of its existence until just now–population 71 and a landfill) is "urban", but the much better known Morgantown, with its commercial, industrial, and residential areas, is "rural".

(https://live.staticflickr.com/65535/50352466848_f7370eac1f_o.png)

A large region of heavily developed territory just west of the City of Allentown is "rural" .
(https://live.staticflickr.com/65535/50353190961_ef6924ba7d_o.png)

Overall, whatever system Google is using seems to place a great deal of importance on a municipality being a borough or city vs. a township (at least in Pennsylvania), as a great number of the gray "urban"  patches in the middle of rural nowhere tend to correspond with de-populated former towns that never relinquished their borough status. Or Disney-esque sham boroughs intended to circumvent legitimate governmental oversight, taxation, and control (SNPJ, Valley-Hi).

It also seems to place a great deal of importance on CDPs in determining urbanity, though not universally. Morgantown is a CDP yet still "rural"  according to Google Maps. So, too, are many of the CDP's west of Allentown (Wescosville, Dorneyville, etc.).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 17, 2020, 02:58:02 PM
First of all, great screenshots. Definitely the highest quality I've ever seen posted here. At least for those that are fans of drop shadows!

As to your point about inconsistencies: I mentioned this a while back as one of the main issues with the update:

Quote from: jakeroot on August 29, 2020, 09:37:28 PM

  • the 'geographically-accurate' color background is a nice touch, though I'd like to know what the meaning is of grey vs non-grey when zoomed out. I assume city vs non-city, but there are discrepancies in my area.

As someone who works with GIS and city boundaries more than frequently, I knew immediately that Google was not using cities to determine the grey areas. At least because in my area, I know the rough boundaries for most census-designated places, and not encompassed grey areas.

Whatever data they're using (it must be shapefiles from somewhere?), it must be fairly obscure, and they're mapping things either grey or green (or tan) depending on the outcome of the equation. I still have another year of GIS courses before I'm done, but I think I'll be able to get a solid answer once school starts back up and I can speak to my GIS professor about the inconsistencies on Google Maps.

For the record: while checking through shapefiles on the Pierce County, WA GIS data hub, I was running through all of the different boundary shapefiles. The first one that actually more-or-less lined up was "sheriff patrol blocks" but even those had inconsistencies. Google Maps has marked the WA-512 freeway as a border between grey and green in the Summit, WA area as an example, and the sheriff patrol blocks are one of the few things that have that freeway as a boundary.
Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on September 17, 2020, 07:41:54 PM
My work has me using a tracking/routing app that uses Wayz. 

Not a bad GPS app, but the Wayz app has a tendancy of popping up random I-65 icons on both other numb3red highways and even on railroad tracks!

And I live out in Colorado!!!
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 17, 2020, 07:49:24 PM
Quote from: thenetwork on September 17, 2020, 07:41:54 PM
My work has me using a tracking/routing app that uses Wayz. 

Not a bad GPS app, but the Wayz app has a tendancy of popping up random I-65 icons on both other numb3red highways and even on railroad tracks!

And I live out in Colorado!!!

That's because you're using a knockoff instead of the real app (Waze).
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on September 17, 2020, 10:37:15 PM
Quote from: 1 on September 17, 2020, 07:49:24 PM
Quote from: thenetwork on September 17, 2020, 07:41:54 PM
My work has me using a tracking/routing app that uses Wayz. 

Not a bad GPS app, but the Wayz app has a tendancy of popping up random I-65 icons on both other numb3red highways and even on railroad tracks!

And I live out in Colorado!!!

That's because you're using a knockoff instead of the real app (Waze).
And this knockoff uses numb3red highways.
Title: Re: Google Maps just fucking SUCKS now
Post by: briantroutman on September 17, 2020, 11:08:32 PM
Quote from: jakeroot on September 17, 2020, 02:58:02 PM
As to your point about inconsistencies: I mentioned this a while back as one of the main issues with the update:

Sorry I missed that–although it's good to know that it's been noticed. I came across a few articles (https://thenextweb.com/google/2020/08/18/google-maps-just-became-much-more-accurate-and-colorful/) that discuss the update to Google Maps, and they seem to suggest a system that's more sophisticated than the reality bears out:

QuoteGoogle says it was able to achieve the new colorings by leveraging a new color-mapping algorithm for its satellite imagery. It's pretty nuanced too, as the imagery can even distinguish between dense vegetation – say, a forest – patchier sections.

- - -

Quote from: jakeroot on September 17, 2020, 02:58:02 PM
First of all, great screenshots. Definitely the highest quality I've ever seen posted here. At least for those that are fans of drop shadows!

That's just the standard screen capture that's built into Macs (if you have one.) For years, ⇧ ⌘ 3 has been a full screen capture and ⇧ ⌘ 4 allows you to select a specific portion of the screen. But a fairly new addition is ⇧ ⌘ 5, which opens up a panel allowing you specify a specific window you want to capture (thus avoiding getting a glimpse of your desktop or any other windows in the capture). And as an added bonus, the capture includes the drop shadow (transparent) that normally would have fallen on whatever would have been behind it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on September 18, 2020, 12:22:40 AM
Quote from: briantroutman on September 17, 2020, 02:34:45 PM
The Borough of New Morgan (I was unaware of its existence until just now–population 71 and a landfill) is "urban", but the much better known Morgantown, with its commercial, industrial, and residential areas, is "rural".

https://youtu.be/8CAbFDt3Evs
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 18, 2020, 01:06:40 PM
Quote from: briantroutman on September 17, 2020, 11:08:32 PM
Quote from: jakeroot on September 17, 2020, 02:58:02 PM
First of all, great screenshots. Definitely the highest quality I've ever seen posted here. At least for those that are fans of drop shadows!

That's just the standard screen capture that's built into Macs (if you have one.) For years, ⇧ ⌘ 3 has been a full screen capture and ⇧ ⌘ 4 allows you to select a specific portion of the screen. But a fairly new addition is ⇧ ⌘ 5, which opens up a panel allowing you specify a specific window you want to capture (thus avoiding getting a glimpse of your desktop or any other windows in the capture). And as an added bonus, the capture includes the drop shadow (transparent) that normally would have fallen on whatever would have been behind it.

That's pretty neat. There are Windows programs that allow it, but I've never bothered with them. Still, pretty neat that it's all built-in with a Mac.

Quote from: briantroutman on September 17, 2020, 11:08:32 PM
Quote from: jakeroot on September 17, 2020, 02:58:02 PM
As to your point about inconsistencies: I mentioned this a while back as one of the main issues with the update:

Sorry I missed that–although it's good to know that it's been noticed. I came across a few articles (https://thenextweb.com/google/2020/08/18/google-maps-just-became-much-more-accurate-and-colorful/) that discuss the update to Google Maps, and they seem to suggest a system that's more sophisticated than the reality bears out:

QuoteGoogle says it was able to achieve the new colorings by leveraging a new color-mapping algorithm for its satellite imagery. It's pretty nuanced too, as the imagery can even distinguish between dense vegetation – say, a forest – patchier sections.

Damn! That's way more complex than I would have ever realized. Still, it seems like it misses the mark. I assume they'll keep working on the algorithm until mismatches are eliminated.

In my example before, the areas north of the WA-512 freeway are just as 'rural' as parts south of it, yet are marked as urban. To the naked eye, the division seems more east to west than north to south, with the freeway playing no role at all:

(https://i.imgur.com/7wTgj6g.png)

(https://i.imgur.com/gJZOjTU.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 18, 2020, 01:36:24 PM
Quote from: jakeroot on September 18, 2020, 01:06:40 PM
Damn! That's way more complex than I would have ever realized. Still, it seems like it misses the mark. I assume they'll keep working on the algorithm until mismatches are eliminated.

As it is now, it ticks off some box on Marketing's list. Given that it's not going to affect anyone's usage of the map the way a road data inaccuracy would, there's no reason to keep investing time and money into it but pride in the quality of the work...And we all know how Google feels about that. "Yeah, we got the green background on rural areas that Marketing wants. Not perfect, but who's gonna notice? Anyway, time to get back to figuring out how to break the interface again. Mitch, you ever get that patch that forces users to scroll with their toes working on iOS, or is it just Android-only?"
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 23, 2020, 08:40:07 PM
This looks interesting, though I would hope that it would be on the desktop too... the article only has app screenshots.
https://www.theverge.com/2020/9/23/21452661/google-maps-overlay-covid-transmission-risk-trends
Title: Re: Google Maps just fucking SUCKS now
Post by: Eth on September 23, 2020, 09:26:23 PM
Quote from: vdeane on September 23, 2020, 08:40:07 PM
This looks interesting, though I would hope that it would be on the desktop too... the article only has app screenshots.
https://www.theverge.com/2020/9/23/21452661/google-maps-overlay-covid-transmission-risk-trends

So at last we get the answer to the question "What will it take for Google Maps to finally display county lines?" A global pandemic.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 24, 2020, 09:20:55 PM
Has street view stopped working for anyone else?  Now, whenever I try to drop pegman anywhere, the area where the imagery should be is just black, and Maps is frozen with no way to get out.  Even the "report a problem" links don't work.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 24, 2020, 09:39:12 PM
Quote from: vdeane on September 24, 2020, 09:20:55 PM
Has street view stopped working for anyone else?  Now, whenever I try to drop pegman anywhere, the area where the imagery should be is just black, and Maps is frozen with no way to get out.  Even the "report a problem" links don't work.

It's working fine for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on September 24, 2020, 10:13:42 PM
Quote from: vdeane on September 24, 2020, 09:20:55 PM
Has street view stopped working for anyone else?  Now, whenever I try to drop pegman anywhere, the area where the imagery should be is just black, and Maps is frozen with no way to get out.  Even the "report a problem" links don't work.

Some Street Views are doing that, such as the promised CBS/Fox street in Michigan from another thread.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 25, 2020, 12:50:42 PM
Quote from: ErmineNotyours on September 24, 2020, 10:13:42 PM
Quote from: vdeane on September 24, 2020, 09:20:55 PM
Has street view stopped working for anyone else?  Now, whenever I try to drop pegman anywhere, the area where the imagery should be is just black, and Maps is frozen with no way to get out.  Even the "report a problem" links don't work.

Some Street Views are doing that, such as the promised CBS/Fox street in Michigan from another thread.
When I posted that it wasn't working for any.  Fortunately it's returned to normal.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on October 02, 2020, 08:46:30 AM
In better news, you can finally view 360 panos on the app!

(Also, is it just me, or are the rivers brighter?)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 02, 2020, 02:06:33 PM
Quote from: TheGrassGuy on October 02, 2020, 08:46:30 AM
In better news, you can finally view 360 panos on the app!

(Also, is it just me, or are the rivers brighter?)

I don't think I realized the panos weren't in there, but it's great to have them now. Particularly for countries where there is no Street View just yet.

I don't think the rivers have changed. Or I haven't noticed a change. I do recall water bodies getting darker near the shore at one point (sort of a gradient effect), but that effect appears to be gone (I think it was part of the previous design, and one thing I really liked about it).
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on October 02, 2020, 02:45:55 PM
In other good news...

You can see traffic lights again... if you zoom in close enough, one hundred freaking feet.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on October 03, 2020, 12:34:40 PM
Has anyone else noticed the horrid GSV quality on some really new shots? I was looking at I-10 east of Mobile yesterday and the picture dated from last September, but the quality was worse than every other picture taken in the area since 2008. It looks like the sun is messing with the new lenses Google is using, which is a problem I haven't encountered with shots taken 2-9 years ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on October 03, 2020, 01:10:33 PM
Quote from: CoreySamson on October 03, 2020, 12:34:40 PM
Has anyone else noticed the horrid GSV quality on some really new shots? I was looking at I-10 east of Mobile yesterday and the picture dated from last September, but the quality was worse than every other picture taken in the area since 2008. It looks like the sun is messing with the new lenses Google is using, which is a problem I haven't encountered with shots taken 2-9 years ago.

Yes. I've seen the purple striped images.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on October 03, 2020, 08:39:45 PM
This road (https://goo.gl/maps/tS718BgGuaDaf1Tv7) seems to have two names on Google. N119 is really just an internal identifier (visible in the road inventory); every unnumbered road has one. How did someone at Google find the identifier and think that was the real street name?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 03, 2020, 10:13:46 PM
Quote from: CoreySamson on October 03, 2020, 12:34:40 PM
Has anyone else noticed the horrid GSV quality on some really new shots? I was looking at I-10 east of Mobile yesterday and the picture dated from last September, but the quality was worse than every other picture taken in the area since 2008. It looks like the sun is messing with the new lenses Google is using, which is a problem I haven't encountered with shots taken 2-9 years ago.
I don't recall that issue being unique to newer street view.  Maybe Google finally got around to stripping out the older stuff that was like that.
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on October 07, 2020, 10:20:12 PM
Anybody else getting black screens on GSV? I'm using a VPN now so it's working. I think it may be a firewall thing.
Title: Re: Google Maps just fucking SUCKS now
Post by: Ben114 on October 17, 2020, 11:27:29 PM
This may not be the worst of all things, but thanks Google!

(https://i.imgur.com/JWahk9W.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on October 23, 2020, 06:53:09 PM
The blue lines in GSV are now a lighter color and more solid texture. Good or bad?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 23, 2020, 06:57:08 PM
Quote from: TheGrassGuy on October 23, 2020, 06:53:09 PM
The blue lines in GSV are now a lighter color and more solid texture. Good or bad?

I think anything that improves contrast is welcome, up to a point of course.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 23, 2020, 08:51:41 PM
I don't know if it's been mentioned, but at some zoom levels Google added more road types.  It's subtle, but there are differences between freeways/expressways and major/minor arterials for roughly zoom levels 7-9.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 25, 2020, 09:00:48 PM
Quote from: vdeane on October 23, 2020, 08:51:41 PM
I don't know if it's been mentioned, but at some zoom levels Google added more road types.  It's subtle, but there are differences between freeways/expressways and major/minor arterials for roughly zoom levels 7-9.

Could you possibly post a couple links? I'm not seeing any changes just yet. Still the same subtilty that I was noticing before.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 26, 2020, 12:49:33 PM
AB 2 is noticeable different on the expressway portion than the freeway portion: https://www.google.com/maps/@52.1310541,-113.1247283,7.71z

The roads between US 2 and the border should be showing up as noticeably thinner: https://www.google.com/maps/@48.4925746,-104.7816046,8.21z
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 26, 2020, 03:40:37 PM
Ahh yes, I see now.

Freeways were always more visible to me because the double strokes just made them easier to see at a smaller scale, but they do seem to have adopted some extra weights for some roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on December 04, 2020, 07:18:06 PM
Around mid-September, Google Maps got even more laggy than it had been over the past several months before.  Before mid-September, it was mostly Street View that would cause CPU spikes, but then panning and zooming the map started causing CPU spikes as well.  My CPU fan quickly sounded like a jet engine.  The computer I'm using was 13 years old (it recently turned 14), so I'm not expecting perfection, but the fact that Maps used to work fine, even after the new Maps was forced is annoying.  It got to the point where it became click, wait, click, wait and so on.  Just out of curiosity, I checked MapQuest, and that preforms better than Google Maps now!  I haven't noticed the CPU spikes lately, but I still have to deal with the click and wait if I don't use my iframe embed bookmarklet.

The CPU spikes occurred in my old version of Chrome and in Slimjet (a fork of Chrome that backports Chrome 50 and later to Windows XP).  I tried a Malwarebytes scan just in case I got something, and it was fine.  I also tried a VM with the same old version of Chrome as I normally use, and I got CPU spikes there too.  Also in mid-September, I noticed higher than normal CPU spikes on YouTube and even Google search was being glitchy.  I started looking at web frameworks to see if there was an update with one that could be causing my issues, and I found that Angular's past few releases correspond to the times I noticed that my CPU started spiking.  Since Angular is developed by Google and my issues are with Google sites, I suspect it's Angular causing the issues.  If I can find another hard drive, I'll have to put it in my computer and install the demo of Windows 10 to see what happens.  I'd be interested to see what happens with the same hardware but a newer OS with both my current browsers, and newer versions.

An additional annoyance is that since Google Maps is borderline unusable for me now, I haven't been able to enjoy the forum as much.  I like to look around the area of a Maps or Street View link that's posted, and that's basically impossible to do now.  It's gotten a bit better recently in my old version of Chrome, but the minimap is glitchy and I can't use the scroll wheel.  Using Slimjet fixes these issues, but Street View is horribly slow.

Here's a recent change I like: House numbers show up on the map when I'm zoomed in all the way.  I started noticing this about a month ago.  Obviously, you can right click a building to get its address, but it's easier with the numbers already on the map.

I've also finally figured out how to hide the business icons in Street View.  I used this filter in my ad blocker:
https://maps.gstatic.com/mapfiles/annotations/*
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 04, 2020, 08:39:56 PM
Quote from: Michael on December 04, 2020, 07:18:06 PM
I've also finally figured out how to hide the business icons in Street View.  I used this filter in my ad blocker:
https://maps.gstatic.com/mapfiles/annotations/*

Thanks! That is something that I've wanted for some time now.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on December 06, 2020, 01:26:12 AM
I've noticed that now in some cities (so far I've only seen it in New York City, San Francisco, and London) the roads have much more detail when you zoom in. The width and shape of the roads is more accurate, and it shows exactly where crosswalks and medians are.

Also, many major landmarks now have their own depictions instead of the standard icons.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on December 07, 2020, 01:31:34 AM
A somewhat recent update added more visible boundaries for Indian/Native American reservations and sovereign nations.

For example, here's the Puyallup Reservation:

(https://i.imgur.com/4GrDbK1.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 07, 2020, 02:19:37 AM
I'm not sure I'm seeing it. Is it the grey boundary to the south and west of Waller?
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on December 07, 2020, 02:30:30 AM
Quote from: Scott5114 on December 07, 2020, 02:19:37 AM
I'm not sure I'm seeing it. Is it the grey boundary to the south and west of Waller?

Yes, and it continues around to the northeast of Fife Heights and to Dash Point.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 07, 2020, 08:00:22 AM
That's not great symbology–without being told I would have never guessed it was a tribal reservation, and wasn't even sure it was meant to be a polygonal area and not, like, a few prominent railroads or something that intersected.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on December 07, 2020, 01:32:01 PM
Quote from: Scott5114 on December 07, 2020, 08:00:22 AM
That's not great symbology–without being told I would have never guessed it was a tribal reservation, and wasn't even sure it was meant to be a polygonal area and not, like, a few prominent railroads or something that intersected.

The previous version had no boundaries, and the version before that had a brown-tan color for them. I'm not sure which I prefer at this point.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 07, 2020, 04:59:27 PM
Quote from: Scott5114 on December 07, 2020, 08:00:22 AM
That's not great symbology–without being told I would have never guessed it was a tribal reservation, and wasn't even sure it was meant to be a polygonal area and not, like, a few prominent railroads or something that intersected.

One of the things that's always bothered me about Google Maps is that there is no legend.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 07, 2020, 08:23:47 PM
Quote from: Michael on December 04, 2020, 07:18:06 PM
Here's a recent change I like: House numbers show up on the map when I'm zoomed in all the way.  I started noticing this about a month ago.  Obviously, you can right click a building to get its address, but it's easier with the numbers already on the map.

I just noticed that today. It can be a bit glitchy, though, as seen where I-290 meets I-294 in the Chicago area:

(https://i.imgur.com/4W8WhPL.png)

(Maybe they're using old plats, from before the highways were constructed?)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2020, 01:00:21 PM
Quote from: Scott5114 on December 07, 2020, 08:00:22 AM
That's not great symbology–without being told I would have never guessed it was a tribal reservation, and wasn't even sure it was meant to be a polygonal area and not, like, a few prominent railroads or something that intersected.

If you zoom in another click, the name pops up in the traditional all-caps style used to label things like this:

(https://live.staticflickr.com/65535/50695796211_a22a2cf9e5_o.png)

(the black box is hiding my location since I'd rather not give away my exact address).

Quote from: CtrlAltDel on December 07, 2020, 04:59:27 PM
One of the things that's always bothered me about Google Maps is that there is no legend.

In my GIS program, we've discussed at-length how services like Google Maps differs from traditional maps. One of the major ways is a legend, as you mention. Among other things like map-maker information or a title.

But, we also discussed how Google Maps is, in many ways, intentionally different from those earlier services (like paper maps). For example, you really don't need a legend because, well, (A) there's too much on the map to have a reasonably-compact legend, and (B) due to 'A', you can simply click on the features you want to know more about.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 08, 2020, 01:05:22 PM
Quote from: CtrlAltDel on December 07, 2020, 08:23:47 PMMaybe they're using old plats, from before the highways were constructed?

I suspect the parcels have been left on the books following their acquisition as ROW for the highway since it would be a worthless expense to consolidate them.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 04:46:07 PM
Quote from: jakeroot on December 08, 2020, 01:00:21 PM
For example, you really don't need a legend because, well, (A) there's too much on the map to have a reasonably-compact legend, and (B) due to 'A', you can simply click on the features you want to know more about.

It doesn't really work, though, does it? I mean, no one knows exactly what a yellow road, for example, is supposed to be as opposed to a white or gray one, and you can't click on any of them to find out either. You also can't click on the forest green or the desert beige or whatever else. You're just supposed to know, and that's not a feature, that's the problem.

Also, there's really no need for the legend to be on the map itself. It can be hidden under an icon until clicked on.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2020, 05:17:17 PM
Quote from: CtrlAltDel on December 08, 2020, 04:46:07 PM
Quote from: jakeroot on December 08, 2020, 01:00:21 PM
For example, you really don't need a legend because, well, (A) there's too much on the map to have a reasonably-compact legend, and (B) due to 'A', you can simply click on the features you want to know more about.

It doesn't really work, though, does it? I mean, no one knows exactly what a yellow road, for example, is supposed to be as opposed to a white or gray one, and you can't click on any of them to find out either. You also can't click on the forest green or the desert beige or whatever else. You're just supposed to know, and that's not a feature, that's the problem.

Also, there's really no need for the legend to be on the map itself. It can be hidden under an icon until clicked on.

It is entirely reasonable to exclude a legend from a map if the map itself does a good enough job labelling its contents (through decent symbology). 90% of the stuff on the map is labelled at various zoom levels. The only things that aren't always labelled are ground colors, and those are usually easy enough to interpret on your own: pink for hospitals, beige for deserts, yellow-ish for business clusters, etc (these things can't always be effectively labelled).

Roads are always labelled, so I'm not sure your point. Most users don't need to know the exact legal definition of the road in question, and Google may not even have that information anyways. They could have a legend for roads, but each color is going to show a dozen different possibilities. The current Google Maps relies more on stroke width to help drivers interpret roadway importance; having a legend for that is simply not necessary, as most people know that the thicker strokes are more important roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2020, 05:19:44 PM
Unpopular opinion:

Why does Google Maps need to do everything? Why does it have to excel at everything?

Aren't there some things that it doesn't have to do?

And before anyone mentions it: just because its important to you, doesn't mean its important to everyone. And I would be inclined to assume Google knows their customer base better than we do.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 05:35:40 PM
Quote from: jakeroot on December 08, 2020, 05:17:17 PM
It is entirely reasonable to exclude a legend from a map if the map itself does a good enough job labelling its contents (through decent symbology).
This is precisely what we're disagreeing on, yes.

Quote from: jakeroot on December 08, 2020, 05:17:17 PM
The only things that aren't always labelled are ground colors, and those are usually easy enough to interpret on your own: pink for hospitals, beige for deserts, yellow-ish for business clusters, etc (these things can't always be effectively labelled).
All of which is perfect information for a legend.

Quote from: jakeroot on December 08, 2020, 05:17:17 PMMost users don't need to know the exact legal definition of the road in question, and Google may not even have that information anyways.
This is something of a red herring. I'm not necessarily interested in the legal definition of the road, I'm interested in the criteria behind its labeling on Google Maps. Google certainly has that information.

Quote from: jakeroot on December 08, 2020, 05:17:17 PM
They could have a legend for roads, but each color is going to show a dozen different possibilities. The current Google Maps relies more on stroke width to help drivers interpret roadway importance; having a legend for that is simply not necessary, as most people know that the thicker strokes are more important roads.
Thicker roads are more important, how? What it is that distinguishes the various thicknesses and colors of roads is not at all clear in the present situation, so much so that it's been argued time and again on this forum. A legend would clear this up.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2020, 05:52:33 PM
Quote from: CtrlAltDel on December 08, 2020, 05:35:40 PM
Quote from: jakeroot on December 08, 2020, 05:17:17 PM
It is entirely reasonable to exclude a legend from a map if the map itself does a good enough job labelling its contents (through decent symbology).
This is precisely what we're disagreeing on, yes.

You honestly think Google does a bad job labelling? Very well. To each their own.

Quote from: CtrlAltDel on December 08, 2020, 05:35:40 PM
Quote from: jakeroot on December 08, 2020, 05:17:17 PM
The only things that aren't always labelled are ground colors, and those are usually easy enough to interpret on your own: pink for hospitals, beige for deserts, yellow-ish for business clusters, etc (these things can't always be effectively labelled).
All of which is perfect information for a legend.

So we should create legend to label things that most users already understand? Legends are not a requirement for a map. I don't need a legend to tell me "beige = desert".

Quote from: CtrlAltDel on December 08, 2020, 05:35:40 PM
Quote from: jakeroot on December 08, 2020, 05:17:17 PM
Most users don't need to know the exact legal definition of the road in question, and Google may not even have that information anyways.
This is something of a red herring. I'm not necessarily interested in the legal definition of the road, I'm interested in the criteria behind its labeling on Google Maps. Google certainly has that information.

Then you should use OSM. They are the only digital mapping service that offers that (so far as I know). Why should Google offer this? You're telling me what you want, but not why you want it, nor even why it would be helpful.

The answers you seek may best be handled by directly reaching out to Google. My grandma doesn't need this information to find her way to Target.

Quote from: CtrlAltDel on December 08, 2020, 05:35:40 PM
Quote from: jakeroot on December 08, 2020, 05:17:17 PM
They could have a legend for roads, but each color is going to show a dozen different possibilities. The current Google Maps relies more on stroke width to help drivers interpret roadway importance; having a legend for that is simply not necessary, as most people know that the thicker strokes are more important roads.
Thicker roads are more important, how? What it is that distinguishes the various thicknesses and colors of roads is not at all clear in the present situation, so much so that it's been argued time and again on this forum. A legend would clear this up.

The solution you seek is not a legend but a better color scheme. I'm not going to argue further about Google Maps' color scheme, as it has (indeed) already been argued at-length in this thread.
Title: Re: Google Maps just fucking SUCKS now
Post by: BrianP on December 08, 2020, 05:53:46 PM
Quote from: jakeroot on December 08, 2020, 05:19:44 PM
Unpopular opinion:

Why does Google Maps need to do everything? Why does it have to excel at everything?

Aren't there some things that it doesn't have to do?

And before anyone mentions it: just because its important to you, doesn't mean its important to everyone. And I would be inclined to assume Google knows their customer base better than we do.
Yeah.  They realize that their customers are mostly just looking for destinations.  The customer enters the address or looks on the map for their destination.  They are not really interested in roads on the map for navigation.  They just ask google to navigate for them.  So in that context the roads are on the map to help find destinations. 

For example, you may be looking for the stadiums in Baltimore.  But you don't know where they are.  But you remember using I-395 to get there.  So you look for I-395 on the map.  And when you find that you look in the vicinity for the stadiums.  Then select a stadium and ask google to navigate you there.

Granted googling Camden Yards address would be easier if you know the name.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 06:09:46 PM
Quote from: jakeroot on December 08, 2020, 05:52:33 PM
You honestly think Google does a bad job labelling? Very well. To each their own.
At times, the map is unclear. This is why those arguments have arisen.

Quote from: jakeroot on December 08, 2020, 05:52:33 PM
Legends are not a requirement for a map.
For a good map, for a complete map, I would say they are.

Quote from: jakeroot on December 08, 2020, 05:52:33 PM
Then you should use OSM.
This thread is not about OSM.

Quote from: jakeroot on December 08, 2020, 05:52:33 PM
The answers you seek may best be handled by directly reaching out to Google.
If no one knows these answers, then it clearly seems that a legend would be useful.

Quote from: jakeroot on December 08, 2020, 05:52:33 PM
The solution you seek is not a legend but a better color scheme. I'm not going to argue further about Google Maps' color scheme, as it has (indeed) already been argued at-length in this thread.
I'm not sure why a legend would not help here.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 06:13:17 PM
On a different note, I don't think I've ever seen stitching off by quite so much before. There's no freeway within even a mile of there:

(https://i.imgur.com/DifthK7.png) (https://www.google.com/maps/@39.0918435,-84.5373073,608m/data=!3m1!1e3?)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2020, 07:07:47 PM
Quote from: CtrlAltDel on December 08, 2020, 06:09:46 PM
At times, the map is unclear. This is why those arguments have arisen.
How, specifically, are they unclear? Not being labelled does not make them unclear. That's the art of symbology, frankly.

Quote from: CtrlAltDel on December 08, 2020, 06:09:46 PM
For a good map, for a complete map, I would say [legends are required].
My professors have taught me otherwise; nearby schools also agree (https://www.wwu.edu/huxley/spatial/tut/what_all_maps_must_have.htm#:~:text=LEGEND%3A%20a%20legend%20defines%20the,type%2C%20weight%20and%20pattern%20represents.). Legends are not a requirement if the symbology is clear enough. Has it not occurred to you why digital maps so rarely include legends? OSM (as I'll mention below) is an example of one with a legend, but OSM has many different colors that Google Maps does not have, making a legend rather helpful as a result.

Quote from: CtrlAltDel on December 08, 2020, 06:09:46 PM
This thread is not about OSM.
Correct, it is about a mapping application for which its primary usage is not necessarily what you are asking of it.

I would point you to my standalone post above: Google Maps does not have to do everything. There are other mapping services that offer what you are looking for.

Quote from: CtrlAltDel on December 08, 2020, 06:09:46 PM
If no one knows these answers, then it clearly seems that a legend would be useful.
Quote from: CtrlAltDel on December 08, 2020, 06:09:46 PM
Quote from: jakeroot on December 08, 2020, 05:52:33 PM
The solution you seek is not a legend but a better color scheme. I'm not going to argue further about Google Maps' color scheme, as it has (indeed) already been argued at-length in this thread.
I'm not sure why a legend would not help here.
There are white and yellow roads. Great. We could put that in a legend, but what are they labelled? Even OSM keeps it as simple as either "motorway" or "main road".

Understanding why each road is symbolized the way it is does not necessarily help the end-user. It's clearly a complex process and likely there is no real answer for all situations. You seem to want something but I don't know if you truly understand the complexity behind your request.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 07:39:37 PM
Overall, in my view, a legend is important to maps for reasons of clarity, thoroughness, and consistency, and my responses to your comments are largely aimed at pointing out that you ignore or otherwise dismiss the ambiguities, and omissions, and aberrations that arise here and there with Google Maps. In seems then that your understanding of what makes a good map tolerates more uncertainty than mine does. With that in mind, I don't think there's any reason to go through your points one by one, since I would largely be repeating what I've already said.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 08, 2020, 07:56:39 PM
Quote from: bm7 on December 06, 2020, 01:26:12 AM
I've noticed that now in some cities (so far I've only seen it in New York City, San Francisco, and London) the roads have much more detail when you zoom in. The width and shape of the roads is more accurate, and it shows exactly where crosswalks and medians are.

That's one of the newly-announced features, indeed...but I don't see it yet on my end. Can you share a screenshot or two?
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 08:02:55 PM
Quote from: empirestate on December 08, 2020, 07:56:39 PM
Quote from: bm7 on December 06, 2020, 01:26:12 AM
I've noticed that now in some cities (so far I've only seen it in New York City, San Francisco, and London) the roads have much more detail when you zoom in. The width and shape of the roads is more accurate, and it shows exactly where crosswalks and medians are.

That's one of the newly-announced features, indeed…but I don't see it yet on my end. Can you share a screenshot or two?

Here you go:
(https://i.imgur.com/bU7Zu7e.png)

And while we’re at it, here’s a picture with some of those unique markers:
(https://i.imgur.com/udSveQI.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on December 08, 2020, 08:12:54 PM
Quote from: CtrlAltDel on December 08, 2020, 08:02:55 PM
Quote from: empirestate on December 08, 2020, 07:56:39 PM
Quote from: bm7 on December 06, 2020, 01:26:12 AM
I've noticed that now in some cities (so far I've only seen it in New York City, San Francisco, and London) the roads have much more detail when you zoom in. The width and shape of the roads is more accurate, and it shows exactly where crosswalks and medians are.

That's one of the newly-announced features, indeed...but I don't see it yet on my end. Can you share a screenshot or two?

Here you go:
(https://i.imgur.com/rEHrlpj.png)

And while we're at it, here's a picture with some of those unique markers:
(https://i.imgur.com/udSveQI.png)


Yeah, I just got it to appear by using a different browser. Odd that Google's own is the one that doesn't show the upgrade. ;-)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 08, 2020, 09:22:29 PM
I don't understand how tech companies roll out new features.  It seems like they intentionally drag it out as long as possible.  It just appeared to me today on Chrome.  As for the monuments, I don't mind the symbology, but the size is a bit large.

Quote from: CtrlAltDel on December 08, 2020, 07:39:37 PM
Overall, in my view, a legend is important to maps for reasons of clarity, thoroughness, and consistency, and my responses to your comments are largely aimed at pointing out that you ignore or otherwise dismiss the ambiguities, and omissions, and aberrations that arise here and there with Google Maps. In seems then that your understanding of what makes a good map tolerates more uncertainty than mine does. With that in mind, I don't think there's any reason to go through your points one by one, since I would largely be repeating what I've already said.
Keep in mind that Google doesn't even have a set standard for what roads are yellow and what roads aren't.  It's arbitrary and inconsistent.  Also keep in mind that the closest equivalent to Google Maps is not Rand McNally, but GPS.  Google certainly thinks of their service as being a web version of the latter, not the former.  And it's arguably always been that way, even if the symbology used to be more map-like.  MapQuest was arguably inspired by AAA TripTiks.  In the old days, it wasn't even practical to browse the map willy-nilly.  Being able to pan around (or zoom in/out with the mouse wheel) didn't even exist prior to Google Maps.  You had to click an arrow on the edge to have the map move a set distance.

Honestly, I'm not even sure how many people are looking closely enough at the maps to take notice of symbology that isn't intuitive (like the toll road markings, or reservations).  In a way, we're lucky Google is giving us what they do; they clearly see themselves as a company providing GPS directions and ways to search for business, not look at maps.  Tourist maps have traditionally not differentiated types of roads at all.
Title: Re: Google Maps just fucking SUCKS now
Post by: NJRoadfan on December 08, 2020, 09:58:52 PM
15 years and they still haven't added county boundaries to Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 08, 2020, 10:13:24 PM
Quote from: CtrlAltDel on December 08, 2020, 07:39:37 PM
Overall, in my view, a legend is important to maps for reasons of clarity, thoroughness, and consistency, and my responses to your comments are largely aimed at pointing out that you ignore or otherwise dismiss the ambiguities, and omissions, and aberrations that arise here and there with Google Maps. In seems then that your understanding of what makes a good map tolerates more uncertainty than mine does. With that in mind, I don't think there's any reason to go through your points one by one, since I would largely be repeating what I've already said.

I tend to ignore or otherwise dismiss claims about ambiguity because the complaints are largely rooted in the ridiculous assertion that Google Maps somehow needs to be everything to everyone. Any Google Maps design that needs a legend fails in its symbology and user-friendliness. Companies like Google, that pride themselves on strong UX design, would never let that happen.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on December 08, 2020, 10:15:21 PM
Quote from: NJRoadfan on December 08, 2020, 09:58:52 PM
15 years and they still haven't added county boundaries to Google Maps.

It specially annoys me that if I search a county, it shows the boundary, but the moment I zoom in to where I can make out buildings the line goes away.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on December 08, 2020, 10:29:49 PM
Quote from: jakeroot on December 08, 2020, 10:13:24 PM
Companies like Google, that pride themselves on strong UX design, would never let that happen.

Again, I disagree. Google drops "strong UX design" whenever it finds it can make a buck by doing so, like with the YouTube app, which used to continue playing videos after it closed, but now doesn't . . . unless you pay.


Honestly, I never thought anyone would be so dead set against having a legend accompany a map. I mean, it's not like Google would force you to look at the legend before you could use the map, or require you to take a quiz. It would be a small unobtrusive button that you could click on if you were confused. It would take up less space than the three — count 'em, three — icons they use for the photo bar:

(https://i.imgur.com/zT2v5to.png)

And it's not like a legend is some weird esoteric addon that only exists because Google is driven to be everything to everyone. It's a standard element of maps, of many sorts, and has been for a good long time.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 08, 2020, 11:58:59 PM
I have to agree that arguing for no legend is a strange hill to die on.

Regarding vdeane's point about their inconsistent symbology, they should fix that and then provide a legend -- even if it's just a simple reference page somewhere.  Doesn't have to be right there on the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 12:47:08 AM
Quote from: Rothman on December 08, 2020, 11:58:59 PM
I have to agree that arguing for no legend is a strange hill to die on.

It's not at all. Not providing a legend is not unusual in mapmaking. It's entirely dependent on the map itself and what symbology is otherwise used to depict map elements. If the elements and symbology are straightforward enough, there is no need to provide a legend.

Quote from: CtrlAltDel on December 08, 2020, 10:29:49 PM
And it's not like a legend is some weird esoteric addon that only exists because Google is driven to be everything to everyone. It's a standard element of maps, of many sorts, and has been for a good long time.

It's not as standard as you make it out to be. Map legends have been useful in the past because static maps do not have the ability to be manipulated on the fly by the user; I don't need Google Maps to tell me that this symbol against this color is a park because I can zoom in and clearly make out where it says it's a park.

The only two exceptions to this rule are:

(1) base map colors: Google Maps uses a few different colors, but the colors are based on real-life land cover (white for glacier/snow, beige for desert, green for forest or grassy areas) and should be easily interpreted by the user;
(2) road colors: there are only two anyway, with the main difference being thickness, layering, and at what point they become visible from different zoom levels.

Have your legend, fine. But I don't know what is supposed to populate that legend that isn't already clear enough from browsing the map itself.

You should draw up a quick concept to accompany your argument, or perhaps link to another digital mapping service that does have a legend as an example that Google could follow. OSM has a legend, as I've mentioned, but it does not show more than two road types (motorway and main roads) and there is no mention of the base map (OSM does not use "geographically-correct" base map colors like Google Maps).
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 09, 2020, 01:48:19 PM
Quote from: jakeroot on December 08, 2020, 05:52:33 PM
So we should create legend to label things that most users already understand? Legends are not a requirement for a map. I don't need a legend to tell me "beige = desert".

Yes, they should create a legend to label things that most users already understand.

The reason you understand that beige=desert is because you have the experience of having looked at other maps with a similar coloring system and a legend to tell you what they mean.

Show my sons a digital Google map, and they won't possess that same experience with paper legend-containing maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 02:18:22 PM
Quote from: kphoger on December 09, 2020, 01:48:19 PM
The reason you understand that beige=desert is because

...I'm a living, breathing human that also knows grass is green, and water is blue, and glaciers are white. I don't need a legend to tell me something obvious.

The colors of the environment are obvious to anyone who has ever looked outside a window. Those that haven't likely aren't Google Maps' target audience.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on December 09, 2020, 02:25:14 PM
Quote from: jakeroot on December 09, 2020, 02:18:22 PM
Quote from: kphoger on December 09, 2020, 01:48:19 PM
The reason you understand that beige=desert is because

...I'm a living, breathing human that also knows grass is green, and water is blue, and glaciers are white.

And protected areas are darker green than normal undeveloped land, and major roads are orange, and airports are light gray, and railroads are dark gray, and pedestrian paths are dark green, and hospitals are red, and shopping malls are orange, and state lines have a literal dashed line running through them...
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 02:26:29 PM
Here are two maps.

I want to be fair here: the map on the left (or top) 100% needs a legend. There are so many different colors there, I couldn't possibly understand them all from intuition alone. On the right (or bottom), the fairly-simple Google Maps really doesn't need a legend. There's only a few colors being used. If there was a need for a legend, it might be for the symbols for POIs, but not the colors.

(https://live.staticflickr.com/65535/50699009938_15ec044636_o.png)(https://live.staticflickr.com/65535/50699009928_0b0e451dc5_o.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 02:29:20 PM
Quote from: 1 on December 09, 2020, 02:25:14 PM
Quote from: jakeroot on December 09, 2020, 02:18:22 PM
Quote from: kphoger on December 09, 2020, 01:48:19 PM
The reason you understand that beige=desert is because

...I'm a living, breathing human that also knows grass is green, and water is blue, and glaciers are white.

And protected areas are darker green than normal undeveloped land, and major roads are orange, and airports are light gray, and railroads are dark gray, and pedestrian paths are dark green, and hospitals are red, and shopping malls are orange, and state lines have a literal dashed line running through them...

But most of those things are otherwise labelled. The original complaint was related to unlabeled colors like deserts or forests.

edit: legends are primarily used to label things that cannot always be labelled on the map itself. If you have an irregular shape on the map, in multiple places, it may not be possible to label that shape on the map itself, so you use a legend, repeat the pattern and then label it so users know what it means. But if that shape is large enough to be labelled directly, there really is no reason to also duplicate it on a legend.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on December 09, 2020, 04:24:28 PM
Quote from: jakeroot on December 09, 2020, 02:29:20 PM
edit: legends are primarily used to label things that cannot always be labelled on the map itself. If you have an irregular shape on the map, in multiple places, it may not be possible to label that shape on the map itself, so you use a legend, repeat the pattern and then label it so users know what it means. But if that shape is large enough to be labelled directly, there really is no reason to also duplicate it on a legend.

Disagree. Say, for example, I'm looking at a map with a few areas of green with the label "X National Park". There is another unlabeled green area - should I assume it's another national park? That would be the guess, except it turns out that was a National Recreation Area because nobody bothered to tell me green applied to all protected areas.

What Google has done lately that really bothers me is that such areas are NOT necessarily the same color...but only based on what kind of vegetation they think there is, not category. The various shades of brown or green change to a slightly different brown or green and it's really not obvious that this is supposed to represent a protected-area boundary. Meanwhile, Google Maps is useless to find where, say, Capitol Reef National Park is since it's impossible to tell it apart from neighboring national monuments, forests, and recreation areas.

If I look at northern Utah on Google, I see at least four shades of green. There's a general one that seems to refer to forested areas, but it also could just mean grass, seeing as it's used in some farming areas (how am I supposed to know?). Another appears to be that same category but in protected, and another but in Indian reservations. There is a fourth, darker greenish gray color that I have no idea what it is supposed to refer to. Likewise, how am I supposed to know the large gray area west of the Great Salt Lake refers to military land if I don't know that already? And I'm curious exactly what it refers to anyway, since there are a few separate areas of military land out there and I'm pretty sure their boundaries are a bit bigger than what Google shows.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 09, 2020, 04:39:47 PM
Quote from: jakeroot on December 08, 2020, 01:00:21 PM
Quote from: Scott5114 on December 07, 2020, 08:00:22 AM
That's not great symbology–without being told I would have never guessed it was a tribal reservation, and wasn't even sure it was meant to be a polygonal area and not, like, a few prominent railroads or something that intersected.

If you zoom in another click, the name pops up in the traditional all-caps style used to label things like this:

(https://live.staticflickr.com/65535/50695796211_a22a2cf9e5_o.png)

I wouldn't necessarily associate that name with the border since there's no visual association between the two.

Quote from: jakeroot on December 08, 2020, 01:00:21 PM
But, we also discussed how Google Maps is, in many ways, intentionally different from those earlier services (like paper maps). For example, you really don't need a legend because, well, (A) there's too much on the map to have a reasonably-compact legend, and (B) due to 'A', you can simply click on the features you want to know more about.

"It's a bad design, but it's intentionally bad, so it's okay!"



Just as an example of how the best-intentioned "intuitive" map designs can fail, check out this portion of my group's Dungeons & Dragons slippy map, designed by yours truly:
(https://i.imgur.com/ozQ0pVt.png)

The legend for this map basically apes the 2005—2006 KDOT map, which is one of my favorite maps of all time, and as such the background shading is meant to convey relief/approximate elevation (although I don't have the elevations nailed down in feet in the fictional setting, because it's not particularly relevant to the game mechanics):
(https://upload.wikimedia.org/wikipedia/commons/4/44/Kansas_official_transportation_map_legend.png)

I had thought that shaded relief maps were commonplace enough that I didn't need to explain that particular feature of the map to anyone. I also figured it would be pretty obvious as you scrolled around that the colors indicated elevation because the features in the northeast corner of the map are mountains (and are labeled as such at higher zoom levels).

Our DM (the person running the game) sent us on a mission to the town of Megantic (in about the center of the map snippet shown here), where we were to meet up with a dragon and obtain needed medical supplies from her. We get to the dragon, and it turns out she's a brass dragon...which is a desert species. The DM had, for months, been interpreting the shading as indicating vegetation levels, and thus the tan/light orange colors of the foothills of the mountains as desert! Then I felt the need to explain to her the elevation shading (and we just patched the monster manual so that in our game brass dragons are mountain-dwellers instead of desert-dwellers) ...but I'm still getting questions about the shading two years later.

Obviously a very low stakes and silly example, but never assume that an "intuitive" map legend will be interpreted correctly–because it won't!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 06:41:45 PM
I really don't have the time to argue about this anymore. So let me summarize the situation:

- I have asked at least a couple times for someone to draw up a conceptual legend for Google Maps. Nothing so far.

- I have asked for any examples of another digital mapping service legend that Google Maps could base a legend design on. Again, nothing so far.

What I am contuining to see is people here picking out specific situations where legends might be helpful. Maybe so! But then, I would continue to argue that improved symbology is the solution, not giving up and simply putting in a legend. For example, I do not like how they've designed the tribal nations. I would not put these on the map as it muddles the colors. I would prefer parks and forested/grass areas contrasted more strongly. Maybe a couple more things. But I would continue to advise against a legend since I have seen virtually no precedent of a legend in digital maps as, by and large, digital maps and paper maps are quite distantly related.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 09, 2020, 06:51:25 PM
Quote from: jakeroot on December 09, 2020, 06:41:45 PM
I really don't have the time to argue about this anymore. So let me summarize the situation:

- I have asked at least a couple times for someone to draw up a conceptual legend for Google Maps. Nothing so far.

- I have asked for any examples of another digital mapping service legend that Google Maps could base a legend design on. Again, nothing so far.


Given that no one is under obligation to provide either and neither is really pertinent to supporting either side of the argument, how you portray this as some sort of victory is illogical.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 06:59:21 PM
Quote from: Rothman on December 09, 2020, 06:51:25 PM
Given that no one is under to provide either and neither is really pertinent to supporting either side of the argument, how you portray this as some sort of victory is illogical.

Yeah, because precedent is totally illogical.

Google Maps introducing a legend would be a first for "consumer-level" mapping. Microsoft, MapQuest, Apple...no one else has a legend either. Do they all need it too?

I wanted a concept because I don't know what would be on the legend. I just wanted some examples of what people think it could look like.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 09, 2020, 07:02:20 PM


Quote from: jakeroot on December 09, 2020, 06:59:21 PM
Quote from: Rothman on December 09, 2020, 06:51:25 PM
Given that no one is under to provide either and neither is really pertinent to supporting either side of the argument, how you portray this as some sort of victory is illogical.

Yeah, because precedent is totally illogical.

Google Maps introducing a legend would be a first for "consumer-level" mapping. Microsoft, MapQuest, Apple...no one else has a legend either. Do they all need it too?

I wanted a concept because I don't know what would be on the legend. I just wanted some examples of what people think it could look like.

The thread is about Google Maps...
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 07:06:00 PM
Quote from: Rothman on December 09, 2020, 07:02:20 PM
The thread is about Google Maps...

Same tired argument. Yawn.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 09, 2020, 07:06:40 PM
Quote from: jakeroot on December 09, 2020, 07:06:00 PM
Quote from: Rothman on December 09, 2020, 07:02:20 PM
The thread is about Google Maps...

Same tired argument. Yawn.
Same nonsense?
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on December 09, 2020, 07:06:45 PM
Mapquest definitely used to have a legend.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2020, 07:24:07 PM
Quote from: Rothman on December 09, 2020, 07:06:40 PM
Quote from: jakeroot on December 09, 2020, 07:06:00 PM
Quote from: Rothman on December 09, 2020, 07:02:20 PM
The thread is about Google Maps...

Same tired argument. Yawn.
Same nonsense?

This thread is a memorial to Google's constant ability to set new lows, yet when asked to provide an example of a mapping service with proper symbology and legends...radio silence. Precedent is important.

Quote from: US 89 on December 09, 2020, 07:06:45 PM
Mapquest definitely used to have a legend.

Maybe. Still, they're part of the overall trend that digital maps do not have legends. OSM is really the only holdout, although for good reason as their maps are far more complex.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 10, 2020, 01:56:17 AM


Quote from: jakeroot on December 09, 2020, 07:24:07 PM
Quote from: Rothman on December 09, 2020, 07:06:40 PM
Quote from: jakeroot on December 09, 2020, 07:06:00 PM
Quote from: Rothman on December 09, 2020, 07:02:20 PM
The thread is about Google Maps...

Same tired argument. Yawn.
Same nonsense?

This thread is a memorial to Google's constant ability to set new lows, yet when asked to provide an example of a mapping service with proper symbology and legends...radio silence. Precedent is important.

Precedent?  So we can't do something that may have not been before?  And yet, as has been pointed out, MapQuest had a legend as Google's main rival back in the day?  I might still be using MapQuest if their vector set didn't go to pot...

It is quite legitimate to point out that a lack of legend is part of the reason why Google Maps suck. 

And, I also get annoyed by just blocks of green where you can't tell where one park ends and another begins...

Google Maps just could be better.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 10, 2020, 02:05:43 AM
Quote from: jakeroot on December 09, 2020, 06:41:45 PM
I really don't have the time to argue about this anymore. So let me summarize the situation:

- I have asked at least a couple times for someone to draw up a conceptual legend for Google Maps. Nothing so far.

Well, starting with the 2007 Kansas DOT legend (which is the same as the 2005 that I posted above, but with the relief shading eliminated, because it was causing red-green colorblindness problems) would be a solid starting point. Set the background color to a warm grey. For urban areas at higher zoom levels, use four different shades of the same color (probably cool greys, but yellows also work surprisingly well) to make adjacent municipalities distinguishable. Mark park areas in green, water in blue, military areas in pink, tribal areas in tan.

This isn't a complete treatment, but Google isn't paying me to do it, so doing spec work for them, where there is zero chance they'll actually listen to any suggestions, doesn't seem like a particularly good use of my time.

Google doesn't even have to implement the entire legend, but just something like marking freeways, tollways, and primary arterials as different colors, rather than all of them being various shades of the same color, would be a huge step up. There are no uses of red, green, or violet lines anywhere on the map.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 10, 2020, 09:44:45 AM
Quote from: jakeroot on December 09, 2020, 06:41:45 PM
- I have asked at least a couple times for someone to draw up a conceptual legend for Google Maps. Nothing so far.

You have to know what the symbols and colors represent in order to make a legend mock-up.  Considering that we keep finding exceptions to what we can only guess are the rules, it doesn't seem reasonable to expect us to produce one.

Example:  Beige and green swaths of land in my neck of the woods seem to be randomly assigned.  The only vague distinction I can make in real life is that, in areas marked by green, the farm fields tend to be slightly more verdant when seen in satellite view than those marked in beige.  But that's all dependent on the time of year the satellite imagery was taken.  I can plop the GSV pegman down in a beige section and see fields in every direction covered in green.  Considering that the green/beige color contrast is the most obvious part of the map, I'd say defining those colors would be Priority One in designing a legend for this area.  Yet I don't even know what they're supposed to represent.  Color of the ground cover?  Agriculture?  Vegetation?

Example:  What are white-colored roads?  I might assume they should perhaps be labeled "minor roads".  Yet right now I'm thinking of a multi-lane divided stretch of US-90 with an AADT over 8000 that's colored white–in the vicinity of two-lane US and state routes with less than half that AADT that are colored yellow.  In Guatemala, I can think of gravel roads colored yellow in the vicinity of paved roads colored white;  almost every national route is colored yellow, yet I can think of at least one counterexample.  How do you expect me to make a legend mock-up for road types, if I can't even figure out what criteria Google uses to differentiate them?

Quote from: jakeroot on December 09, 2020, 06:41:45 PM
I have seen virtually no precedent of a legend in digital maps as, by and large, digital maps and paper maps are quite distantly related.

How do you figure they're "distantly related"?  I'd say the precedent is paper maps.

Also, before internet maps, I remember using CD-ROM mapping software.  I can't recall if those programs had a legend.  Does anyone on here remember?  If they did, then those would be the true precursors of Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 10, 2020, 12:35:29 PM
Just a passing observation:  if Google doesn't use a legend, and thus doesn't have to commit to what a given symbol/design element actually means, then the errors are harder to see.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 10, 2020, 01:53:06 PM
Quote from: Rothman on December 10, 2020, 01:56:17 AM
[clipped]

Obviously Google can do what it wants, but it would be odd to introduce a legend at this point, this many years later, despite have less complexity in its symbology than it had 10 years ago (if I recall correctly). Still, I agree that Google could do better. I'm just not sure we agree on how to accomplish that.

Quote from: Scott5114 on December 10, 2020, 02:05:43 AM
[clipped]

I think this is actually a good start. But I think whatever proposal we might "draw up" here, we also have to consider that Google Maps should, if possible, match the rest of Google's design language. Google has the rather unenviable task of trying to balance their design language against a map design that makes sense. I think it's harder to achieve than we may be giving them credit for.

Quote from: kphoger on December 10, 2020, 09:44:45 AM
[clipped]

Your post actually highlights a point I was trying to make before, and which vdeane (kind of) agreed with, which is that Google doesn't seem to have their symbology quite nailed down just yet. There are many exceptions to each rule to the point where I'm not confident that Google could make a legend that wasn't very basic.

That said, here's a quick mockup of a legend. Roads are difficult since the rules seem to vary from city to city:

(https://live.staticflickr.com/65535/50703379726_be9dd71c47_o.png)

Quote from: J N Winkler on December 10, 2020, 12:35:29 PM
Just a passing observation:  if Google doesn't use a legend, and thus doesn't have to commit to what a given symbol/design element actually means, then the errors are harder to see.

You're not wrong.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 10, 2020, 03:13:19 PM
Quote from: J N Winkler on December 10, 2020, 12:35:29 PM
Just a passing observation:  if Google doesn't use a legend, and thus doesn't have to commit to what a given symbol/design element actually means, then the errors are harder to see.

Quote from: jakeroot on December 10, 2020, 01:53:06 PM
Google doesn't seem to have their symbology quite nailed down just yet.

It's just my armchair opinion, but I bet Google has their symbology nailed down perfectly well.  That is to say, I bet Google employees have access to a map legend, and a lot of the variances we see are actually misclassification errors–either the product of user input error or auto-generated data.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 10, 2020, 03:40:00 PM
Quote from: jakeroot on December 10, 2020, 01:53:06 PM
I think this is actually a good start. But I think whatever proposal we might "draw up" here, we also have to consider that Google Maps should, if possible, match the rest of Google's design language. Google has the rather unenviable task of trying to balance their design language against a map design that makes sense. I think it's harder to achieve than we may be giving them credit for.

If your "design language" (i.e. branding) interferes with the actual use of a product, then that design language needs to go, or at least be confined to the UI and leave the actual map alone. Making marketing considerations like design language take precedence over usability is a hallmark of corporate software design, and is one of the reasons I use the stuff as little as possible. (The Art of Unix Programming by Eric S. Raymond is basically my lodestar for what software design should look like.)

Having ambiguous symbols that are different enough that you can tell they're meant to be different, but similar enough it's hard to tell at a glance that they are different, is bad design. It's like that old vexillological maxim, be distinctive or be related. Avoid duplicating other symbols, but use similarities to show connections.

If I were product manager of Google Maps, I would jettison the existing legend wholesale in favor of something more usable (like the KDOT-derived legend), then mysteriously have just gone out to lunch every time anyone from Marketing wanted to meet with me to talk about "design language".
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 10, 2020, 05:22:09 PM
Quote from: kphoger on December 10, 2020, 03:13:19 PM
It's just my armchair opinion, but I bet Google has their symbology nailed down perfectly well.  That is to say, I bet Google employees have access to a map legend, and a lot of the variances we see are actually misclassification errors–either the product of user input error or auto-generated data.

There's definitely a "legend", or at least a set of design standards by which things are to be classified. It's just possible that they don't release it because they're fully aware that there are inconsistencies between each city. For instance, the meaning of a yellow road in one city versus another might actually be correct in both cases based on the data that Google has (probably sourced from the city, county, or state), but users would have no way of knowing this. So rather than saying "yellow means everything from this to this" and "white means anything from this to this", they just totally hide it and let the user decide the reasoning themselves.

As an example, a six lane road in my area would be very major, but it would not necessarily be in places like Los Angeles or Phoenix. So a six lane road with a 40 mph speed limit in Los Angeles might be colored white, but in my area it really should be colored yellow. Perhaps both scenarios would be colored yellow if the limit were 50 mph? So many variables, really.

OSM is perfect for this because each city basically has its own set of users editing things and can decide, on a case by case basis, which roads should be classified and why. Google really just has a team and mainly relies on outside data. So yeah, there's going to be inconsistencies perhaps to the level that they are better off just hiding the legend.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 10, 2020, 05:29:49 PM
Quote from: Scott5114 on December 10, 2020, 03:40:00 PM
Quote from: jakeroot on December 10, 2020, 01:53:06 PM
I think this is actually a good start. But I think whatever proposal we might "draw up" here, we also have to consider that Google Maps should, if possible, match the rest of Google's design language. Google has the rather unenviable task of trying to balance their design language against a map design that makes sense. I think it's harder to achieve than we may be giving them credit for.

If your "design language" (i.e. branding) interferes with the actual use of a product, then that design language needs to go, or at least be confined to the UI and leave the actual map alone. Making marketing considerations like design language take precedence over usability is a hallmark of corporate software design, and is one of the reasons I use the stuff as little as possible. (The Art of Unix Programming by Eric S. Raymond is basically my lodestar for what software design should look like.)

Having ambiguous symbols that are different enough that you can tell they're meant to be different, but similar enough it's hard to tell at a glance that they are different, is bad design. It's like that old vexillological maxim, be distinctive or be related. Avoid duplicating other symbols, but use similarities to show connections.

If I were product manager of Google Maps, I would jettison the existing legend wholesale in favor of something more usable (like the KDOT-derived legend), then mysteriously have just gone out to lunch every time anyone from Marketing wanted to meet with me to talk about "design language".

I think Google actually does a decent job with their map design in terms of keeping it within a certain design language relative to their other programs. The problem seems to be that the contrast between certain parts of the map is considered strong enough by Google, but perhaps not by others. And in fact, perhaps not by quite a lot of people.

From doing some Googling, there is this help article for Google Maps (https://support.google.com/maps/answer/3092439#pinlet) that actually lists a ton of different details about the colors and symbols. Some of you should definitely take a look at this!

From looking through it, they don't address the road colors, and they don't address the colors of the map itself, but they do dive into some of the lines and also some of the colors of symbols (orange vs blue vs green, etc). There's actually quite a bit of contrast in the symbols themselves, but the colors of the map (road lines, base map, topography) may need the bulk of the work from here on out. Some high-contrast variant might actually be a cool idea, if they wanted to try that out. I wouldn't need to use it, but others might.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 10, 2020, 05:54:15 PM
Quote from: jakeroot on December 10, 2020, 05:29:49 PM
From doing some Googling, there is this help article for Google Maps (https://support.google.com/maps/answer/3092439#pinlet) that actually lists a ton of different details about the colors and symbols. [...] From looking through it, they don't address the road colors, and they don't address the colors of the map itself, but they do dive into some of the lines and also some of the colors of symbols (orange vs blue vs green, etc). There's actually quite a bit of contrast in the symbols themselves, but the colors of the map (road lines, base map, topography) may need the bulk of the work from here on out.

Herein lies the problem–I barely use those symbols at all. They are most useful if you are browsing around the map to see what kind of businesses are around a certain area (say, you're staying at a hotel soon and you want to see what's nearby your room). If that's not your use case–and I'd imagine it's not for most people in most situations–those symbols are clutter; most users probably want to find the location of a certain business (and thus use search) or calculate a route.

For these sorts of use cases, a strong base map helps. Thus, I find myself preferring OpenStreetMap for pretty much anything that relies on the base map, and only use Google Maps now for use cases where satellite or street view imagery would be helpful. I hardly ever need to look up the location of businesses, mostly because I don't have any money.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 10, 2020, 06:21:05 PM
Quote from: Scott5114 on December 10, 2020, 05:54:15 PM
Herein lies the problem–I barely use those symbols at all. They are most useful if you are browsing around the map to see what kind of businesses are around a certain area (say, you're staying at a hotel soon and you want to see what's nearby your room). If that's not your use case–and I'd imagine it's not for most people in most situations–those symbols are clutter; most users probably want to find the location of a certain business (and thus use search) or calculate a route.

I believe jakeroot has already expressed (several pages back) his opinion that he disagrees with that fundamentally.  He assumes most users are using the site for purposes just like your hotel scenario.  And, besides, wanting to "find the location of a certain business" means you're wanting to find one of those little symbols on the map.

Really, I'm open to the possibility that the way an average roadgeek uses Google Maps is not the way an average person uses it.

Quote from: jakeroot on December 10, 2020, 05:29:49 PM
From looking through it, they don't address the road colors, and they don't address the colors of the map itself, ...

So they don't address the two most obvious things on the map, the things that everyone notices immediately.  (or at least used to notice immediately, back before city streets all but disappeared)
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on December 10, 2020, 07:44:29 PM
Yeah, we're totally missing the point here. 999 out of 1000 people don't inspect US route termini or look to see if the map shows the new freeway upgrade to Highway XX. The overwhelming majority of people use it for directions or finding businesses. With that being said, an inaccurate map is not a good map so it's important that Google gets the details right. But most people do not use Google Maps the way we do.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 10, 2020, 10:19:24 PM
Quote from: kphoger on December 10, 2020, 06:21:05 PM
Quote from: Scott5114 on December 10, 2020, 05:54:15 PM
Herein lies the problem–I barely use those symbols at all. They are most useful if you are browsing around the map to see what kind of businesses are around a certain area (say, you're staying at a hotel soon and you want to see what's nearby your room). If that's not your use case–and I'd imagine it's not for most people in most situations–those symbols are clutter; most users probably want to find the location of a certain business (and thus use search) or calculate a route.

I believe jakeroot has already expressed (several pages back) his opinion that he disagrees with that fundamentally.  He assumes most users are using the site for purposes just like your hotel scenario.  And, besides, wanting to "find the location of a certain business" means you're wanting to find one of those little symbols on the map.

Right, but when you want to find the location of a certain business, you don't go to the map and pan around until you find it. You go to the search bar and type in "Wet Pets By Steve" or whatever and then there's a big red pin on it that overrides the colorful icons.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on December 10, 2020, 10:53:36 PM
Quote from: kphoger on December 10, 2020, 06:21:05 PM
Really, I'm open to the possibility that the way an average roadgeek uses Google Maps is not the way an average person uses it.

I don't see you couldn't be open to that possibility. For as long as I can remember, I've never thought that I use maps with the same frequency, or for the same reasons, or in the same way as an average person.


Quote from: Scott5114 on December 10, 2020, 10:19:24 PM
Right, but when you want to find the location of a certain business, you don't go to the map and pan around until you find it. You go to the search bar and type in "Wet Pets By Steve" or whatever and then there's a big red pin on it that overrides the colorful icons.

Oh, this might be another roadgeek oddity. How you described it is certainly how most normal people would do it - and in fact might be the only way they could do it - but if I already know where the business is, I'm absolutely panning all the way!
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 11, 2020, 03:37:12 AM
Quote from: webny99 on December 10, 2020, 10:53:36 PM
Oh, this might be another roadgeek oddity. How you described it is certainly how most normal people would do it - and in fact might be the only way they could do it - but if I already know where the business is, I'm absolutely panning all the way!

If I already know where the business is...I type the address in, like "200 N. Main Street" or whatever. Not a typical thing most people would do, but it guards against things like there being several businesses with similar names (or one business with several locations), or a misspelled name, or the business not being added to Google Maps yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on December 11, 2020, 09:48:23 AM
Quote from: Scott5114 on December 11, 2020, 03:37:12 AM
Quote from: webny99 on December 10, 2020, 10:53:36 PM
Oh, this might be another roadgeek oddity. How you described it is certainly how most normal people would do it - and in fact might be the only way they could do it - but if I already know where the business is, I'm absolutely panning all the way!

If I already know where the business is...I type the address in, like "200 N. Main Street" or whatever. Not a typical thing most people would do, but it guards against things like there being several businesses with similar names (or one business with several locations), or a misspelled name, or the business not being added to Google Maps yet.

I was referring more to cases where I know the location in general terms ("southeast corner of intersection X", "far end of plaza Y", etc.) and could find it easily on the map, but don't necessarily know the exact address. There's only a handful of businesses that I could give you that for; my local McDonald's and Dunkin Donuts aren't even among them!
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 11, 2020, 12:44:02 PM
Quote from: webny99 on December 10, 2020, 10:53:36 PM
Oh, this might be another roadgeek oddity. How you described it is certainly how most normal people would do it - and in fact might be the only way they could do it - but if I already know where the business is, I'm absolutely panning all the way!
I know I definitely pan the map around a lot more than anyone else I know.  Most people seem to use search even for places that they know.

I definitely use the business icons when planning roadtrips, looking around where I'd stop for lunch, gas, hotels, etc. and just see what's around.  Or I'll just browse around for fun.

Quote from: Scott5114 on December 11, 2020, 03:37:12 AM
If I already know where the business is...I type the address in, like "200 N. Main Street" or whatever. Not a typical thing most people would do, but it guards against things like there being several businesses with similar names (or one business with several locations), or a misspelled name, or the business not being added to Google Maps yet.
If you start typing in the name, once Google figures out you're typing the name of a business, it will change the drop-down from towns to business locations with much of the address visible.

That said, usually when I'm clicking on businesses it isn't even for directions - it's to look up their hours, website, menu, or to look at photos or reviews.  Or just browsing to see what's around approximate target points for roadtrip stops for lunch, lodging, etc. as mentioned above.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 11, 2020, 01:35:00 PM
Quote from: Scott5114 on December 10, 2020, 10:19:24 PM

Quote from: kphoger on December 10, 2020, 06:21:05 PM

Quote from: Scott5114 on December 10, 2020, 05:54:15 PM
Herein lies the problem–I barely use those symbols at all. They are most useful if you are browsing around the map to see what kind of businesses are around a certain area (say, you're staying at a hotel soon and you want to see what's nearby your room). If that's not your use case–and I'd imagine it's not for most people in most situations–those symbols are clutter; most users probably want to find the location of a certain business (and thus use search) or calculate a route.

I believe jakeroot has already expressed (several pages back) his opinion that he disagrees with that fundamentally.  He assumes most users are using the site for purposes just like your hotel scenario.  And, besides, wanting to "find the location of a certain business" means you're wanting to find one of those little symbols on the map.

Right, but when you want to find the location of a certain business, you don't go to the map and pan around until you find it. You go to the search bar and type in "Wet Pets By Steve" or whatever and then there's a big red pin on it that overrides the colorful icons.

Says who?  Or, rather, who says that's how I use Google Maps?

In general, if I already know the name of the business, then I probably already know where it is too.  However...

If my wife is driving during a road trip and she wants to know what services are at the exit 10 miles down the Interstate, then I open up Google Maps for that area and zoom in.  I then tell her what's available.

If I'm planning a trip and want to know where to stop for lunch along the way, then I estimate what part of the state we'll be in around that time, and scroll along the highway, looking to see what restaurants are in which towns.

If my family is trying to decide where to go out to eat, but we want to make sure we aren't forgetting about an option, then both my wife and I zoom in on several restaurant-heavy neighborhoods and make sure nothing jumps out at us that we hadn't thought of yet.

If I'm staying with company and need to run to the grocery store, but our hosts aren't home at the time, then I open Google Maps and look for the nearest grocery store icon (and if I can't find one nearby, then I just search for "grocery stores").
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on December 11, 2020, 10:44:38 PM
Quote from: kphoger on December 11, 2020, 01:35:00 PM
Says who?  Or, rather, who says that's how I use Google Maps?

That's the royal You. As in not you, Kyle P. Hoger, but phrased so as to convey the general sentiment "I don't think this is a typical use case for J. Random Mouthbreather," in much the same way as someone might say "You don't eat peanut butter straight out of the jar!" (which my wife would argue with if I said so to her).

I think roadgeeks are more comfortable panning and browsing maps by eye than the average user, is what I'm saying.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on December 12, 2020, 10:05:13 AM
Quote from: Scott5114 on December 11, 2020, 10:44:38 PM

Quote from: kphoger on December 11, 2020, 01:35:00 PM
Says who?  Or, rather, who says that's how I use Google Maps?

That's the royal You. As in not you, Kyle P. Hoger, but phrased so as to convey the general sentiment "I don't think this is a typical use case for J. Random Mouthbreather," in much the same way as someone might say "You don't eat peanut butter straight out of the jar!" (which my wife would argue with if I said so to her).

I think roadgeeks are more comfortable panning and browsing maps by eye than the average user, is what I'm saying.

Hmm, I was figuring plenty of non-roadgeek types would be more likely to use it the way I was outlining.  My wife, for example, is not a roadgeek, yet that's the say she uses Google Maps.  I've noticed she's actually not very good at or used to entering the name or address of a place.
Title: Re: Google Maps just fugging SUCKS now
Post by: CNGL-Leudimin on December 14, 2020, 07:52:38 AM
For one day the thread title isn't valid (BTW, for this post I've ammended it as approved by Tarsdorf, Austria on November 17 :sombrero:). Most Mr. Google services are down at the moment, and Google Maps is about the only thing still running now (well, along with web search), at least in my area of the world, IDK what is happening in the USA. Now that is something.
Title: Re: Google Maps just fugging SUCKS now
Post by: hotdogPi on December 14, 2020, 07:56:17 AM
Quote from: CNGL-Leudimin on December 14, 2020, 07:52:38 AM
For one day the thread title isn't valid (BTW, for this post I've ammended it as approved by Tarsdorf, Austria on November 17 :sombrero:). Most Mr. Google services are down at the moment, and Google Maps is about the only thing still running now (well, along with web search), at least in my area of the world, IDK what is happening in the USA. Now that is something.

It's mostly western Europe, but there seems to be a few spots much farther east, as well as a straight line from New York City to Buffalo. I can access it just fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on December 14, 2020, 01:43:36 PM
When I am on the road, I don't feel how I use Google Maps is strongly dominated by my identity as a road enthusiast.  For example, when I am staying in a motel, I often search for "breakfast near me" to get an idea of which coffee shops, 24-hour restaurants, etc. are acceptable to me and within walking distance of where I am staying.  If I don't find any, I then search for Denny's, IHOP, and independently-owned establishments (usually in that order) until I find one that is reasonably accessible by car.

It is mainly when I am comfortable, with good Internet access and no need to try to read a screen in sun, that I use Google Maps to explore road layouts, signing, and other features of roadgeek interest.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on December 21, 2020, 11:15:48 AM
Google Maps has seemed glacially slow the past few days when switching between map and satellite view or when trying to turn off the blue lines you click to enter Street View.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 21, 2020, 04:38:13 PM
That it does.  And it often will need a reload to get the labels back after switching out of satellite view or street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 21, 2020, 05:09:53 PM
Quote from: 1995hoo on December 21, 2020, 11:15:48 AM
Google Maps has seemed glacially slow the past few days when switching between map and satellite view or when trying to turn off the blue lines you click to enter Street View.

What platform? Seems about normal speed for me at the moment.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on December 22, 2020, 03:33:02 AM
Same for me, no noticeable change in speed. However I check for the labels being gone after coming out of Street View.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 22, 2020, 07:43:30 PM
I'm on Chrome/Linux, but I also wonder if the issue might be geographic, given that both of us who have it are in east coast states.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on January 02, 2021, 04:48:47 PM
I-169 has returned (again). 99 percent sure it still isn't signed.

https://www.google.com/maps/@36.9882045,-87.5978495,59535m/data=!3m1!1e3
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 02, 2021, 06:20:56 PM
Quote from: I-55 on January 02, 2021, 04:48:47 PM
I-169 has returned (again). 99 percent sure it still isn't signed.

https://www.google.com/maps/@36.9882045,-87.5978495,59535m/data=!3m1!1e3

I feel like this might be acceptable. It is legally I-169 and there are "Future I-169" signs along the route. But most importantly, Google still shows it as "Pennyrile Pkwy" which is all that would normally be shown. So they're jumping the gun ahead of KYTC by actually showing the 169 shield, but it's not like a huge mistake.

Then again, if there are still things that need to be upgraded before showing I-169 on signage (perhaps that interchange with the Hopkinsville ring road?), then it may be wise to hide the shield until those upgrades are done.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on January 03, 2021, 12:40:10 AM
Yeah Google does jump the gun with new interstates. I-69 has existed in Memphis for a while now according to Google:
https://www.google.com/maps/@35.1006492,-90.0333052,13z
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on January 05, 2021, 09:10:34 AM
When I exit street view on Google Chrome, the road labels disappear unless you zoom in close.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on January 13, 2021, 11:44:16 AM
Quote from: TheGrassGuy on January 05, 2021, 09:10:34 AM
When I exit street view on Google Chrome, the road labels disappear unless you zoom in close.

Or out.

Really frustrating.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on January 16, 2021, 08:31:34 AM
Does anyone else have this problem? In Chrome, go into street view anywhere, look up towards the sky and zoom in any amount, then exit street view. For me this crashes the tab with an out of memory error every single time.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 16, 2021, 02:07:44 PM
Quote from: bm7 on January 16, 2021, 08:31:34 AM
Does anyone else have this problem? In Chrome, go into street view anywhere, look up towards the sky and zoom in any amount, then exit street view. For me this crashes the tab with an out of memory error every single time.

I wasn't able to repeat this. I tried Chrome and Edge.

Quote from: TheGrassGuy on January 05, 2021, 09:10:34 AM
When I exit street view on Google Chrome, the road labels disappear unless you zoom in close.

I think this has since been fixed. I did notice this issue myself for a while.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 16, 2021, 09:28:45 PM
Quote from: bm7 on January 16, 2021, 08:31:34 AM
Does anyone else have this problem? In Chrome, go into street view anywhere, look up towards the sky and zoom in any amount, then exit street view. For me this crashes the tab with an out of memory error every single time.
I didn't crash to the point where it would give the "Aw, Snap" error, but it did freeze on black when I tried it and I had to refresh the page.  The URL had the coordinates set to NaN (not a number), so I'm guessing it confuses Google Maps about where you are.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheStranger on January 16, 2021, 09:31:03 PM
Two weeks after it opened to traffic, and over a year and a half after the first segment to Manila was completed, the Skyway Stage 3 still does not appear at all in Google Maps except as under-construction segments.

https://www.google.com/maps/place/Quezon+City,+Metro+Manila,+Philippines/@14.6839253,120.9921501,12z/data=!3m1!4b1!4m5!3m4!1s0x3397ba0942ef7375:0x4a9a32d9fe083d40!8m2!3d14.6760413!4d121.0437003

In comparison, OpenStreetMap has had the new expressway on its maps for months, even when the portion north of Manila had been finished but not opened yet.  One can even use OSM to get directions to places where the Skyway is suggested as a route.

https://www.openstreetmap.org/relation/106569
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on January 16, 2021, 10:26:59 PM
Quote from: vdeane on January 16, 2021, 09:28:45 PM
I didn't crash to the point where it would give the "Aw, Snap" error, but it did freeze on black when I tried it and I had to refresh the page.  The URL had the coordinates set to NaN (not a number), so I'm guessing it confuses Google Maps about where you are.

This happens probably every 4th or 5th time I exit street view. Annoys the hell out of me.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on January 18, 2021, 10:33:08 AM
Quote from: jakeroot on January 16, 2021, 02:07:44 PM

Quote from: TheGrassGuy on January 05, 2021, 09:10:34 AM
When I exit street view on Google Chrome, the road labels disappear unless you zoom in close.

I think this has since been fixed. I did notice this issue myself for a while.

It's not fixed on my end, at least.  I still have the issue.

Quote from: vdeane on January 16, 2021, 09:28:45 PM

Quote from: bm7 on January 16, 2021, 08:31:34 AM
Does anyone else have this problem? In Chrome, go into street view anywhere, look up towards the sky and zoom in any amount, then exit street view. For me this crashes the tab with an out of memory error every single time.

I didn't crash to the point where it would give the "Aw, Snap" error, but it did freeze on black when I tried it and I had to refresh the page.  The URL had the coordinates set to NaN (not a number), so I'm guessing it confuses Google Maps about where you are.

And I generally try to avoid doing things that are expected to "crash" anything on my computer.  Call me crazy, but I don't sniff people's fingers when they say too, either!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 19, 2021, 02:08:57 AM
Quote from: kphoger on January 18, 2021, 10:33:08 AM
Quote from: jakeroot on January 16, 2021, 02:07:44 PM

Quote from: TheGrassGuy on January 05, 2021, 09:10:34 AM
When I exit street view on Google Chrome, the road labels disappear unless you zoom in close.

I think this has since been fixed. I did notice this issue myself for a while.

It's not fixed on my end, at least.  I still have the issue.

I just started noticing it again since my post. I think I jinxed myself.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on January 19, 2021, 08:02:50 AM
Quote from: TheStranger on January 16, 2021, 09:31:03 PM
Two weeks after it opened to traffic, and over a year and a half after the first segment to Manila was completed, the Skyway Stage 3 still does not appear at all in Google Maps except as under-construction segments.

https://www.google.com/maps/place/Quezon+City,+Metro+Manila,+Philippines/@14.6839253,120.9921501,12z/data=!3m1!4b1!4m5!3m4!1s0x3397ba0942ef7375:0x4a9a32d9fe083d40!8m2!3d14.6760413!4d121.0437003

In comparison, OpenStreetMap has had the new expressway on its maps for months, even when the portion north of Manila had been finished but not opened yet.  One can even use OSM to get directions to places where the Skyway is suggested as a route.

https://www.openstreetmap.org/relation/106569

(laughs in China) :) :) :)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 19, 2021, 12:56:11 PM
Heck, Google still doesn't have the easternmost part of A-410 marked properly.  They put the mainline in, but none of the new ramps are shown.
Title: Re: Google Maps just fucking SUCKS now
Post by: Caps81943 on January 20, 2021, 03:24:02 PM
Quote from: jakeroot on January 19, 2021, 02:08:57 AM
Quote from: kphoger on January 18, 2021, 10:33:08 AM
Quote from: jakeroot on January 16, 2021, 02:07:44 PM

Quote from: TheGrassGuy on January 05, 2021, 09:10:34 AM
When I exit street view on Google Chrome, the road labels disappear unless you zoom in close.

I think this has since been fixed. I did notice this issue myself for a while.

It's not fixed on my end, at least.  I still have the issue.

I just started noticing it again since my post. I think I jinxed myself.

Yeah I think the issue's back. Hopefully it doesn't take as long to fix this time.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 20, 2021, 08:21:19 PM
Back?  It never left for me, even if it did go from happening all the time to happening a good chunk of the time.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on January 20, 2021, 08:31:52 PM
It happens on Firefox too.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on January 21, 2021, 01:21:34 PM
Quote from: vdeane on January 20, 2021, 08:21:19 PM
Back?  It never left for me, even if it did go from happening all the time to happening a good chunk of the time.

Yeah, same :-(
Title: Re: Google Maps just fucking SUCKS now
Post by: TheStranger on January 22, 2021, 03:42:01 AM
I actually mentioned it earlier (Google Maps not showing any of Skyway Stage 3 even though the mainline is now fully open from Buendia Avenue in Makati to NLEX in Balintawak) and this played out in real life for someone attempting to use Google Maps to navigate around Makati:

https://www.skyscrapercity.com/threads/metro-manila-skyway.1492516/post-171663482
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 29, 2021, 02:57:21 PM
How many of you guys have seen the updated base map that is shown in a couple cities? Right now, I can see it in the original three cities mentioned by Google last year (San Francisco, New York, London) but no other so far. I only just got the update. Basically, far more detailed, showing very exact road widths, crosswalk locations, medians, etc.

Right away? Far more Japanese like than I originally expected. If I recall correctly, Google bought the company that originally made maps like this for the Japanese market; this must be their way of finally carrying that technology over.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on January 30, 2021, 08:38:15 PM
I can see it. Looks good, but I don't ever need maps of SF or NYC, so it's not much use to me at the moment.
Title: Re: Google Maps just fucking SUCKS now
Post by: briantroutman on January 30, 2021, 09:23:07 PM
I've done some brief peeking around New York on the Google Maps iOS app, and I must say that I'm less than impressed with the new imagery.

While crosswalks seem to be fairly consistently represented–in my brief searches–the "exact"  street geometry appears to be far from that. Sidewalks appear and disappear in a manner that's not consistent with the ground reality. Features such as medians and sidewalks have gashes cut into them for no apparent reason–again, not reflective of reality.

For those of you familiar with Adobe Illustrator: It's like they did and auto-trace of satellite images. Some features are outlined well, and others are horribly botched and for no apparent reason. 
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 31, 2021, 02:54:53 PM
Quote from: briantroutman on January 30, 2021, 09:23:07 PM
For those of you familiar with Adobe Illustrator: It's like they did and auto-trace of satellite images. Some features are outlined well, and others are horribly botched and for no apparent reason.

If it was as easy as tracing satellite imagery, I'm sure we'd have a lot more than three cities.

Whatever the technology: there's going to be growing pains, including occasional inaccuracies. If the issues persist for another five years...well, Google needs to get their shit together by that point.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on February 12, 2021, 09:36:28 PM
Google appears to have let B&V cam's vastly inferior GSV imagery start to take over a lot of areas, sometimes with no option for old street view because it just won't show up. Why are they just allowing a downgrade? The quality of B&V's GSV is horrible. Granted, it's better than 07-09 GSV, but still.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on February 13, 2021, 11:43:18 AM
Sometimes when I try to leave satellite, it goes back to satellite.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 13, 2021, 02:08:19 PM
Quote from: TheGrassGuy on February 13, 2021, 11:43:18 AM
Sometimes when I try to leave satellite, it goes back to satellite.

That's happened to me occasionally for a long time.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 13, 2021, 09:07:59 PM
Quote from: index on February 12, 2021, 09:36:28 PM
Google appears to have let B&V cam's vastly inferior GSV imagery start to take over a lot of areas, sometimes with no option for old street view because it just won't show up. Why are they just allowing a downgrade? The quality of B&V's GSV is horrible. Granted, it's better than 07-09 GSV, but still.
Unfortunately they sometimes default to B&V even when the Google imagery is newer.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on February 15, 2021, 08:30:21 PM
Quote from: TheGrassGuy on February 13, 2021, 11:43:18 AM
Sometimes when I try to leave satellite, it goes back to satellite.

I've finally found a solution to that problem.  When you go back to regular map, don't immediately adjust the scale or press any buttons for a second or two.  That must have been what was tripping me up for months now.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 16, 2021, 04:59:51 PM
When Google Maps' language is set to French (works in any mirror), the Arabian city of Ha'il shows up as Grêle (https://www.google.es/maps/@27.5105325,41.7062087,11.45z?hl=fr), which is French for "hail"... as in the stony ice precipitation. And it has been that way for a long time. It doesn't happen in Spanish, as it shows correctly as Hail (https://www.google.es/maps/@27.5105325,41.7062087,11.45z?hl=es) instead of Granizo.
Title: Re: Google Maps just fucking SUCKS now
Post by: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 17, 2021, 02:51:40 AM
Quote from: CNGL-Leudimin on February 16, 2021, 04:59:51 PM
When Google Maps' language is set to French (works in any mirror), the Arabian city of Ha'il shows up as Grêle (https://www.google.es/maps/@27.5105325,41.7062087,11.45z?hl=fr), which is French for "hail"... as in the stony ice precipitation.

That's hilarious.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 17, 2021, 09:00:03 PM
Quote from: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
I suspect they stopped driving during the pandemic.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on February 17, 2021, 09:00:20 PM
Quote from: CNGL-Leudimin on February 16, 2021, 04:59:51 PM
When Google Maps' language is set to French (works in any mirror), the Arabian city of Ha'il shows up as Grêle (https://www.google.es/maps/@27.5105325,41.7062087,11.45z?hl=fr), which is French for "hail"... as in the stony ice precipitation.

That explains why the METAR aviation reporting code for hail is GR...
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 17, 2021, 09:02:50 PM
Quote from: vdeane on February 17, 2021, 09:00:03 PM
Quote from: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
I suspect they stopped driving during the pandemic.

I found one for October 2020 in Boston proper.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on February 17, 2021, 09:07:03 PM
I've found a lot of March 2020 footage in Florida, but that's the newest I've seen.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 17, 2021, 09:14:52 PM
Quote from: 1 on February 17, 2021, 09:02:50 PM
Quote from: vdeane on February 17, 2021, 09:00:03 PM
Quote from: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
I suspect they stopped driving during the pandemic.

I found one for October 2020 in Boston proper.
From Google, or third party?  There's 2020 footage in Kingston, but it's from 360 Tour Gallery.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 17, 2021, 09:16:21 PM
Quote from: vdeane on February 17, 2021, 09:14:52 PM
Quote from: 1 on February 17, 2021, 09:02:50 PM
Quote from: vdeane on February 17, 2021, 09:00:03 PM
Quote from: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
I suspect they stopped driving during the pandemic.

I found one for October 2020 in Boston proper.
From Google, or third party?  There's 2020 footage in Kingston, but it's from 360 Tour Gallery.

https://www.google.com/maps/@42.3515518,-71.1202901,3a,75y,270.22h,89.31t/data=!3m6!1e1!3m4!1s9xS8YSbTzO32vtluBdhs7g!2e0!7i16384!8i8192
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 17, 2021, 09:40:22 PM
Quote from: 1 on February 17, 2021, 09:16:21 PM
Quote from: vdeane on February 17, 2021, 09:14:52 PM
Quote from: 1 on February 17, 2021, 09:02:50 PM
Quote from: vdeane on February 17, 2021, 09:00:03 PM
Quote from: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
I suspect they stopped driving during the pandemic.

I found one for October 2020 in Boston proper.
From Google, or third party?  There's 2020 footage in Kingston, but it's from 360 Tour Gallery.

https://www.google.com/maps/@42.3515518,-71.1202901,3a,75y,270.22h,89.31t/data=!3m6!1e1!3m4!1s9xS8YSbTzO32vtluBdhs7g!2e0!7i16384!8i8192
Interesting.  That has to be the only piece of post-COVID street view from Google I've seen in the US.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 18, 2021, 12:59:07 AM
Quote from: vdeane on February 17, 2021, 09:40:22 PM
Quote from: 1 on February 17, 2021, 09:16:21 PM
Quote from: vdeane on February 17, 2021, 09:14:52 PM
Quote from: 1 on February 17, 2021, 09:02:50 PM
Quote from: vdeane on February 17, 2021, 09:00:03 PM
Quote from: Lyon Wonder on February 17, 2021, 12:32:18 AM
IMO, Google has been slacking off with their street view since the last updates (at least in the midwest) were in 2019 just before the COVID pandemic.
I suspect they stopped driving during the pandemic.

I found one for October 2020 in Boston proper.
From Google, or third party?  There's 2020 footage in Kingston, but it's from 360 Tour Gallery.

https://www.google.com/maps/@42.3515518,-71.1202901,3a,75y,270.22h,89.31t/data=!3m6!1e1!3m4!1s9xS8YSbTzO32vtluBdhs7g!2e0!7i16384!8i8192
Interesting.  That has to be the only piece of post-COVID street view from Google I've seen in the US.

Depending on your cutoff, there are quite a few areas with March 2020 imagery: Los Angeles (https://goo.gl/maps/p2A7uGbm3qGs3qmz7), Lake Tahoe (https://goo.gl/maps/wRnnE3542KBCdgxV9), and Phoenix (https://goo.gl/maps/QStPXXvE7xvzhYrv9)

Bay Area (https://goo.gl/maps/GgqyitquTe74xozA6) proper also has quite a lot of recent shots (my link is Oct 2020, same as the Boston example above).
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 18, 2021, 05:08:04 AM
France has also a lot of post-"end of the World (as we knew it)" imagery. I first found such recent imagery there.

Spain, on the other hand, is still in 2019. Normally they update Street View in Spain around this time of the year.
Title: Re: Google Maps just fucking SUCKS now
Post by: Katavia on February 18, 2021, 08:53:04 AM
Quote from: vdeane on February 13, 2021, 09:07:59 PM
Quote from: index on February 12, 2021, 09:36:28 PM
Google appears to have let B&V cam's vastly inferior GSV imagery start to take over a lot of areas, sometimes with no option for old street view because it just won't show up. Why are they just allowing a downgrade? The quality of B&V's GSV is horrible. Granted, it's better than 07-09 GSV, but still.
Unfortunately they sometimes default to B&V even when the Google imagery is newer.
B&V? Not familiar with anything w/ that acronym, is it the program where El Goog's allowing 3rd-party images to show up on GSV?
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 18, 2021, 09:00:42 AM
Quote from: Katavia on February 18, 2021, 08:53:04 AM
Quote from: vdeane on February 13, 2021, 09:07:59 PM
Quote from: index on February 12, 2021, 09:36:28 PM
Google appears to have let B&V cam's vastly inferior GSV imagery start to take over a lot of areas, sometimes with no option for old street view because it just won't show up. Why are they just allowing a downgrade? The quality of B&V's GSV is horrible. Granted, it's better than 07-09 GSV, but still.
Unfortunately they sometimes default to B&V even when the Google imagery is newer.
B&V? Not familiar with anything w/ that acronym, is it the program where El Goog's allowing 3rd-party images to show up on GSV?

I don't know what the acronym stands for, but there are two bad types of new imagery. This is one of them:
https://www.google.com/maps/@42.3748203,-70.9863082,3a,75y,306.32h,80.7t/data=!3m6!1e1!3m4!1sJLaXFQJIThE--7HHVykqTg!2e0!7i16384!8i8192
which is worse than 07-09 imagery.
The other is this:
https://goo.gl/maps/pZ1gEmXhka6iCcKM6
which isn't quite as bad as the first link. Somehow the other direction is from the same year and month but has no problems.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 18, 2021, 10:27:30 AM
Quote from: US 89 on February 17, 2021, 09:00:20 PM
That explains why the METAR aviation reporting code for hail is GR...

Whence does it actually derive?

My mind immediately goes to Spanish.  HAIL = GRANIZA
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 18, 2021, 02:02:30 PM
Quote from: 1 on February 18, 2021, 09:00:42 AM
Quote from: Katavia on February 18, 2021, 08:53:04 AM
Quote from: vdeane on February 13, 2021, 09:07:59 PM
Quote from: index on February 12, 2021, 09:36:28 PM
Google appears to have let B&V cam's vastly inferior GSV imagery start to take over a lot of areas, sometimes with no option for old street view because it just won't show up. Why are they just allowing a downgrade? The quality of B&V's GSV is horrible. Granted, it's better than 07-09 GSV, but still.
Unfortunately they sometimes default to B&V even when the Google imagery is newer.
B&V? Not familiar with anything w/ that acronym, is it the program where El Goog's allowing 3rd-party images to show up on GSV?

I don't know what the acronym stands for, but there are two bad types of new imagery. This is one of them:
https://www.google.com/maps/@42.3748203,-70.9863082,3a,75y,306.32h,80.7t/data=!3m6!1e1!3m4!1sJLaXFQJIThE--7HHVykqTg!2e0!7i16384!8i8192
which is worse than 07-09 imagery.
The other is this:
https://goo.gl/maps/pZ1gEmXhka6iCcKM6
which isn't quite as bad as the first link. Somehow the other direction is from the same year and month but has no problems.

I'd say that first imagery is quite good, apart from that it was uploaded sideways.

The second one seems to be the camera trying to compensate for low lighting conditions?

I googled out the rear end for "B&V". Seems like one of those acronyms that a few people use but no one else knows what it means.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 18, 2021, 02:33:36 PM
Quote from: jakeroot on February 18, 2021, 02:02:30 PM

Quote from: 1 on February 18, 2021, 09:00:42 AM

Quote from: Katavia on February 18, 2021, 08:53:04 AM

Quote from: vdeane on February 13, 2021, 09:07:59 PM

Quote from: index on February 12, 2021, 09:36:28 PM
Google appears to have let B&V cam's vastly inferior GSV imagery start to take over a lot of areas, sometimes with no option for old street view because it just won't show up. Why are they just allowing a downgrade? The quality of B&V's GSV is horrible. Granted, it's better than 07-09 GSV, but still.

Unfortunately they sometimes default to B&V even when the Google imagery is newer.

B&V? Not familiar with anything w/ that acronym, is it the program where El Goog's allowing 3rd-party images to show up on GSV?

I don't know what the acronym stands for, but there are two bad types of new imagery. This is one of them:
https://www.google.com/maps/@42.3748203,-70.9863082,3a,75y,306.32h,80.7t/data=!3m6!1e1!3m4!1sJLaXFQJIThE--7HHVykqTg!2e0!7i16384!8i8192
which is worse than 07-09 imagery.
The other is this:
https://goo.gl/maps/pZ1gEmXhka6iCcKM6
which isn't quite as bad as the first link. Somehow the other direction is from the same year and month but has no problems.

I'd say that first imagery is quite good, apart from that it was uploaded sideways.

The second one seems to be the camera trying to compensate for low lighting conditions?

I googled out the rear end for "B&V". Seems like one of those acronyms that a few people use but no one else knows what it means.

From what I can tell, "B&V Cam" is just a Google user whose imagery exists on Google Maps.

Go to the link below, and you can clearly see that "B&V Cam" is just the source's screen name.  It's obvious now, but it wasn't obvious back in 2018.

Quote from: Mr. Matté on May 27, 2018, 06:12:53 PM
Interestingly enough, I've noticed recently along the PA Turnpike that there's some kind of new photo sphere appearing along it. It's called "B&V Cam" and the imagery is from April this year (example from the new I-95 interchange (https://www.google.com/maps/@40.128384,-74.8872101,3a,65.7y,104.19h,90.93t/data=!3m8!1e1!3m6!1sAF1QipO0jxImzxM9JIrd-yfw2eu-0pwwNX-IUgbmO6Mu!2e10!3e11!6shttps:%2F%2Flh5.googleusercontent.com%2Fp%2FAF1QipO0jxImzxM9JIrd-yfw2eu-0pwwNX-IUgbmO6Mu%3Dw203-h100-k-no-pi1.6279323-ya30.160109-ro-5.719576-fo100!7i2508!8i1254?hl=en-US)). The area by the tunnel doesn't appear to be on GM yet but it apparently can go through tunnels since the bubbles appear on the EB Fort Littleton ramp.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on February 18, 2021, 07:47:26 PM
Quote from: kphoger on February 18, 2021, 10:27:30 AM
Quote from: US 89 on February 17, 2021, 09:00:20 PM
That explains why the METAR aviation reporting code for hail is GR...

Whence does it actually derive?

My mind immediately goes to Spanish.  HAIL = GRANIZA

Appears to actually be French, although Spanish is also a Romance language and naturally has a lot of similar words. France was pretty influential in the early days of aviation - just look at all the words for parts of airplanes that are obviously French in origin: fuselage, empennage, nacelle, aileron...

French also gave us the METAR codes for graupel/snow pellets (GS, grésil) and mist/light fog (BR, brume), among others.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on February 19, 2021, 11:25:56 AM
Got a new laptop, and now minor roads are a nearly unreadable blotch of white.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 19, 2021, 11:26:31 AM
Quote from: TheGrassGuy on February 19, 2021, 11:25:56 AM
Got a new laptop, and now minor roads are a nearly unreadable blotch of white.

Adjust your brightness and contrast settings.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on March 14, 2021, 07:09:43 PM
It's not the most egregious of flaws, but there's currently a bit of I-35 missing between Austin and Waco at certain zoom levels:

(https://i.imgur.com/pZP3HSv.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on March 16, 2021, 10:41:25 AM
Quote from: CtrlAltDel on March 14, 2021, 07:09:43 PM
It's not the most egregious of flaws, but there's currently a bit of I-35 missing between Austin and Waco at certain zoom levels:

(https://i.imgur.com/pZP3HSv.png)

Saw that with I-80 in PA too recently.

Also, anyone else notice that you can now get a picture of an image just by clicking on it in GSV? Not sure whether this is a good thing or a bad thing.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on March 19, 2021, 10:02:00 AM
Google maps now has dark mode, and while I use dark mode on most other apps, I think I will stay on light mode for this one.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on March 19, 2021, 10:20:18 AM
Quote from: briantroutman on January 30, 2021, 09:23:07 PM
I've done some brief peeking around New York on the Google Maps iOS app, and I must say that I'm less than impressed with the new imagery.

While crosswalks seem to be fairly consistently represented–in my brief searches–the "exact"  street geometry appears to be far from that. Sidewalks appear and disappear in a manner that's not consistent with the ground reality. Features such as medians and sidewalks have gashes cut into them for no apparent reason–again, not reflective of reality.

For those of you familiar with Adobe Illustrator: It's like they did and auto-trace of satellite images. Some features are outlined well, and others are horribly botched and for no apparent reason. 

Yeah, it's OK I guess, but not as impressive as I'd hoped. I was expecting Zenrin-like quality, since that's what they've had in Japan for many years now. In fact, you can get much better detail and accuracy with NYC's own GIS planimetry, and it's free.

Yes, one hopes the new map style will mature and improve over time, but of course it's always disappointing when some "new" feature is already inferior to what has previously been available (cf. my theory of technological regression).
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on March 19, 2021, 11:57:37 AM
Quote from: US 89 on February 18, 2021, 07:47:26 PM
Quote from: kphoger on February 18, 2021, 10:27:30 AM
Quote from: US 89 on February 17, 2021, 09:00:20 PM
That explains why the METAR aviation reporting code for hail is GR...

Whence does it actually derive?

My mind immediately goes to Spanish.  HAIL = GRANIZA

Appears to actually be French, although Spanish is also a Romance language and naturally has a lot of similar words. France was pretty influential in the early days of aviation - just look at all the words for parts of airplanes that are obviously French in origin: fuselage, empennage, nacelle, aileron...

French also gave us the METAR codes for graupel/snow pellets (GS, grésil) and mist/light fog (BR, brume), among others.

I can confirm that any of the ones not from English specifically come from French.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on March 19, 2021, 02:03:23 PM
Quote from: ozarkman417 on March 19, 2021, 10:02:00 AM
Google maps now has dark mode, and while I use dark mode on most other apps, I think I will stay on light mode for this one.

I've been using it for about a week. Not sure what I think of it just yet. It isn't quite as easy to read in bright daylight, but it's much better on the eyes at night for sure.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on March 27, 2021, 08:47:08 AM
I feel like the blue lines for GSV sort of override each other. Just try getting Pegman onto the lower deck of the Bay Bridge in San Francisco to get an idea of what I mean.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on March 27, 2021, 09:29:47 PM
Quote from: TheGrassGuy on March 27, 2021, 08:47:08 AM
I feel like the blue lines for GSV sort of override each other. Just try getting Pegman onto the lower deck of the Bay Bridge in San Francisco to get an idea of what I mean.
Hey I've tried that too!  :sombrero: Another beef I have with the blue lines is that it will always put you on a minor side road or photosphere instead of the road you are trying to click on.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on March 28, 2021, 02:14:48 AM
Quote from: CoreySamson on March 27, 2021, 09:29:47 PM
Quote from: TheGrassGuy on March 27, 2021, 08:47:08 AM
I feel like the blue lines for GSV sort of override each other. Just try getting Pegman onto the lower deck of the Bay Bridge in San Francisco to get an idea of what I mean.
Hey I've tried that too!  :sombrero: Another beef I have with the blue lines is that it will always put you on a minor side road or photosphere instead of the road you are trying to click on.

I don't think it always does, but it can happen. At least for me.

Quote from: jakeroot on March 19, 2021, 02:03:23 PM
Quote from: ozarkman417 on March 19, 2021, 10:02:00 AM
Google maps now has dark mode, and while I use dark mode on most other apps, I think I will stay on light mode for this one.

I've been using it for about a week. Not sure what I think of it just yet. It isn't quite as easy to read in bright daylight, but it's much better on the eyes at night for sure.

Update: had to switch back to auto day/night mode. Dark mode was too dark during the day, at least on my phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on March 30, 2021, 10:02:06 AM
Quote from: CoreySamson on March 27, 2021, 09:29:47 PM
Another beef I have with the blue lines is that it will always put you on a minor side road or photosphere instead of the road you are trying to click on.

Minor side road:  I can't complain too much about that one, because how does Google know which road I meant to look at?  It's just being more accurate than I was when I dropped the pegman.  Of course, knowing exactly where to drop the pegman to begin with seems to be more of an art than a science.

Photosphere:  This really aggravates me.  Especially because, most of the time, I was zoomed out enough to not even know there was a photosphere there at all.  If it isn't even visible on the screen, then Google should know I didn't want it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Michael on April 06, 2021, 03:25:29 PM
I just went to Google Maps and the layer selection square is now a popout menu, similar to how it was in the last version of classic Maps.  I like it, since it'll be much easier than having to open the side menu and then selecting a layer from there.  It behaves more like the phone app does.  I'm not sure if I got the new design as part of an A/B test since my old version of Chrome doesn't have it.  Ideally, map/satellite/terrain would be three buttons like Maps had a long time ago, but I'll take what I can get.  When classic Maps combined the three buttons into one I hated it, but it's still better than having to use a side menu each time.  I can't help but imagine a car blinker designed like that.  First, open your blinker menu, then select from left, right, or 4-ways.  That sounds pretty stupid.




I recently tried an old version of Chromium I forgot I had kicking around, and that solved all the performance issues I've been having with Maps.  It's version 49, so it's new enough to not glitch out like my old version of Chrome.  I thought it was old enough to be using GPU acceleration on Windows XP, but it's not.  I also considered my adblocker slowing things down, but turning it off didn't make a difference.  I guess it'll remain a mystery.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on April 15, 2021, 04:30:26 PM
If you click on a business, the blue lines for street view no longer show up.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on April 15, 2021, 05:37:56 PM
Quote from: TheGrassGuy on April 15, 2021, 04:30:26 PM
If you click on a business, the blue lines for street view no longer show up.

Is that what it is? I had noticed the blue lines intermittently not showing up, but hadn't associated it with clicking on a business (or presumably any other POI). It is annoying!
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on April 26, 2021, 08:12:48 AM
Quote from: webny99 on April 15, 2021, 05:37:56 PM
Quote from: TheGrassGuy on April 15, 2021, 04:30:26 PM
If you click on a business, the blue lines for street view no longer show up.

Is that what it is? I had noticed the blue lines intermittently not showing up, but hadn't associated it with clicking on a business (or presumably any other POI). It is annoying!
It's fixed now.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on May 15, 2021, 04:04:48 PM
Does Google Maps still suck? It works fine for me every time.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on May 21, 2021, 05:01:56 PM
Yet more incorrect info on Google Maps; They think Northwest Creek in the Town of East Hampton, New York is part of the Peconic River too.

https://www.google.com/maps/@41.0045204,-72.258092,3266m/data=!3m1!1e3?hl=en


And there doesn't seem to be any way to correct this. Even if there was, they still include the Peconic River in more waterways that were corrected.


Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on May 21, 2021, 05:19:06 PM
As much as you might hate google maps, apple maps is even worse.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 41 on May 29, 2021, 09:15:34 PM
Going back to the beginning of this thread, the new Google Maps is better than the "Classic" GM was now and it's not even close. When they first launched it though it was a disaster.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 29, 2021, 09:46:33 PM
They still don't allow as many routing points as the old Google Maps did.  In fact, I'm pretty sure they've decreased even further over the years.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on May 30, 2021, 12:13:14 AM
Quote from: vdeane on May 29, 2021, 09:46:33 PM
They still don't allow as many routing points as the old Google Maps did.  In fact, I'm pretty sure they've decreased even further over the years.
Yep.  ^This.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on May 30, 2021, 05:03:09 AM
Quote from: US 41 on May 29, 2021, 09:15:34 PM
Going back to the beginning of this thread, the new Google Maps is better than the "Classic" GM was now and it's not even close. When they first launched it though it was a disaster.

No, it's still worse, it just has more irrelevant data to mask the fact that it sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on May 30, 2021, 12:27:51 PM
Quote from: Scott5114 on May 30, 2021, 05:03:09 AM
Quote from: US 41 on May 29, 2021, 09:15:34 PM
Going back to the beginning of this thread, the new Google Maps is better than the "Classic" GM was now and it's not even close. When they first launched it though it was a disaster.

No, it's still worse, it just has more irrelevant data to mask the fact that it sucks.
What made "classic gm" better?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 30, 2021, 12:29:12 PM
I actually use the business info, so I want everything to be usable, both the road stuff and the other stuff.  If that means the map has to be less "simple", fine, I'm not really a fan of the trend in computing to "simplify" and dumb down everything anyways.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on May 31, 2021, 01:57:57 AM
Quote from: Roadgeekteen on May 30, 2021, 12:27:51 PM
Quote from: Scott5114 on May 30, 2021, 05:03:09 AM
Quote from: US 41 on May 29, 2021, 09:15:34 PM
Going back to the beginning of this thread, the new Google Maps is better than the "Classic" GM was now and it's not even close. When they first launched it though it was a disaster.

No, it's still worse, it just has more irrelevant data to mask the fact that it sucks.
What made "classic gm" better?

Rather than the data being rendered on the fly like it is now, it was pre-rendered and stored as image tiles on the Google Maps server. So when you panned around the map, all it had to do was download the images and display them. It was much less resource-intensive.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 31, 2021, 10:53:30 AM
Quote from: Scott5114 on May 31, 2021, 01:57:57 AM
Quote from: Roadgeekteen on May 30, 2021, 12:27:51 PM
Quote from: Scott5114 on May 30, 2021, 05:03:09 AM
Quote from: US 41 on May 29, 2021, 09:15:34 PM
Going back to the beginning of this thread, the new Google Maps is better than the "Classic" GM was now and it's not even close. When they first launched it though it was a disaster.

No, it's still worse, it just has more irrelevant data to mask the fact that it sucks.
What made "classic gm" better?

Rather than the data being rendered on the fly like it is now, it was pre-rendered and stored as image tiles on the Google Maps server. So when you panned around the map, all it had to do was download the images and display them. It was much less resource-intensive.
On the other hand, such systems are prone to the "missing tile problem" where all the tiles download except the one you specifically want to look at.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on May 31, 2021, 02:41:58 PM
Quote from: vdeane on May 31, 2021, 10:53:30 AM
Quote from: Scott5114 on May 31, 2021, 01:57:57 AM
Quote from: Roadgeekteen on May 30, 2021, 12:27:51 PM
Quote from: Scott5114 on May 30, 2021, 05:03:09 AM
Quote from: US 41 on May 29, 2021, 09:15:34 PM
Going back to the beginning of this thread, the new Google Maps is better than the "Classic" GM was now and it's not even close. When they first launched it though it was a disaster.

No, it's still worse, it just has more irrelevant data to mask the fact that it sucks.
What made "classic gm" better?

Rather than the data being rendered on the fly like it is now, it was pre-rendered and stored as image tiles on the Google Maps server. So when you panned around the map, all it had to do was download the images and display them. It was much less resource-intensive.
On the other hand, such systems are prone to the "missing tile problem" where all the tiles download except the one you specifically want to look at.

I have a custom map on my own webserver using the Leaflet JavaScript library to implement such a system. I have never had a tile go missing, and my server, well, to be honest, kind of sucks. I suspect that there's some combination of issues here: perhaps Leaflet does some sort of error-checking and forces a reload of tiles whose HTTP requests time out or are otherwise undisplayable, connection speeds are simply better than they were in 2014, and/or Google's tile rendering routine was buggy (or maybe just-in-time enough) in such a way that it caused tiles to sometimes not load.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 31, 2021, 08:15:02 PM
That mention of Leaflet is interesting.  I remember there were times when the OSM tiles would display just fine in TM but OSM itself was having issues.

I'm not sure if I've had issue with OSM recently; maybe they've improved things over there.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on June 06, 2021, 05:25:14 AM
In Lowell, MA, Aiken St. changes into Aiken Ave. Google Maps has it changing in the wrong spot (but not by much). I sent a correction, and they published it. Now, the entire road is labeled Aiken Ave., which is worse than before.
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on June 15, 2021, 12:34:10 AM
When I use Street View to explore roads and get to a red light, it never changes.  It just stays red forever.  I end up having to run the light.  I don't understand why they don't fix that.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 15, 2021, 12:57:07 AM
Quote from: wxfree on June 15, 2021, 12:34:10 AM
When I use Street View to explore roads and get to a red light, it never changes.  It just stays red forever.  I end up having to run the light.  I don't understand why they don't fix that.
Street view also never changes seasons! How strange...
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 15, 2021, 01:12:33 PM
Quote from: wxfree on June 15, 2021, 12:34:10 AM
When I use Street View to explore roads and get to a red light, it never changes.  It just stays red forever.  I end up having to run the light.  I don't understand why they don't fix that.

Yeah, well said! Google Maps fucking blows! I cannot believe they haven't fixed this simple problem.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 15, 2021, 01:14:39 PM
A more real complaint but I wish google would upgrade their imagery on very rural roads like US 50 and US 6 in Nevada.
Title: Re: Google Maps just fucking SUCKS now
Post by: jp the roadgeek on June 15, 2021, 01:15:42 PM
One positive: they FINALLY corrected the CT 31 shields north of US 44 to be state route shields instead of county route ones :clap:
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on June 15, 2021, 01:17:17 PM
Quote from: Roadgeekteen on June 15, 2021, 01:14:39 PM
A more real complaint but I wish google would upgrade their imagery on very rural roads like US 50 and US 6 in Nevada.
Yeah, their imagery is going downhill in most rural areas.  Wonder if they've figured out that StreetView is just a money-suck.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 15, 2021, 01:27:05 PM
Quote from: Rothman on June 15, 2021, 01:17:17 PM
Yeah, their imagery is going downhill in most rural areas.

In most cases, you can just spin the view around to see the uphill direction.
Title: Re: Google Maps just fucking SUCKS now
Post by: cjw2001 on June 15, 2021, 01:30:31 PM
Quote from: kphoger on June 15, 2021, 01:27:05 PM
Quote from: Rothman on June 15, 2021, 01:17:17 PM
Yeah, their imagery is going downhill in most rural areas.

In most cases, you can just spin the view around to see the uphill direction.

:bigass: :-D :D :clap:
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 15, 2021, 01:33:30 PM
Quote from: Rothman on June 15, 2021, 01:17:17 PM
Quote from: Roadgeekteen on June 15, 2021, 01:14:39 PM
A more real complaint but I wish google would upgrade their imagery on very rural roads like US 50 and US 6 in Nevada.
Yeah, their imagery is going downhill in most rural areas.  Wonder if they've figured out that StreetView is just a money-suck.
They update most interstates and more urban areas. How does streetview make money?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 15, 2021, 01:38:07 PM
Quote from: Roadgeekteen on June 15, 2021, 01:33:30 PM
How does streetview make money?

By being part of Google.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 15, 2021, 01:39:50 PM
Quote from: kphoger on June 15, 2021, 01:38:07 PM
Quote from: Roadgeekteen on June 15, 2021, 01:33:30 PM
How does streetview make money?

By being part of Google.
How does Streetview make Google money?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on June 15, 2021, 01:48:13 PM
Quote from: Roadgeekteen on June 15, 2021, 01:39:50 PM
Quote from: kphoger on June 15, 2021, 01:38:07 PM
Quote from: Roadgeekteen on June 15, 2021, 01:33:30 PM
How does streetview make money?

By being part of Google.
How does Streetview make Google money?
Data collection, viewership...
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 15, 2021, 01:50:59 PM
Quote from: Roadgeekteen on June 15, 2021, 01:39:50 PM

Quote from: kphoger on June 15, 2021, 01:38:07 PM

Quote from: Roadgeekteen on June 15, 2021, 01:33:30 PM
How does streetview make money?

By being part of Google.

How does Streetview make Google money?

By being part of Google Maps.  Google knows what you search for on Google Maps and feeds you advertisements accordingly.  Also, businesses can pay a premium to use their corporate logo on the map.  If GSV gets you to use Google, then it helps Google make money.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on June 16, 2021, 05:13:42 PM
Google moved the layers down to the bottom of the page. Rather than clicking the three bars in the top left, I have to click the button at the bottom that used to be "satellite". Of course, if you click that button now, it still takes you to the satellite view. So instead I have to hold my mouse over the button briefly to then select my desired layer. 
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 16, 2021, 06:15:51 PM
Quote from: ozarkman417 on June 16, 2021, 05:13:42 PM
Google moved the layers down to the bottom of the page. Rather than clicking the three bars in the top left, I have to click the button at the bottom that used to be "satellite". Of course, if you click that button now, it still takes you to the satellite view. So instead I have to hold my mouse over the button briefly to then select my desired layer.

This was a good change. Less clicks for a commonly-accessed feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 16, 2021, 09:06:16 PM
I like it overall, though it will take getting used to as I'm so accustomed to the layers being in the left menu.  It is annoying, however, to have an extra click to get at things like the COVID info; seems like there aren't so many layers that they couldn't have put them in.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on June 17, 2021, 09:50:50 AM
I see they also did not fix the toggle setting not being retained for labels in Satellite view. This regression goes back a number of years now.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on June 17, 2021, 10:22:59 AM
Huh? I can disable labels on Satellite view, and has always been that way. Now, disabling the globe format, which earlier required one click, now it takes two.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 17, 2021, 11:29:22 AM
Quote from: CNGL-Leudimin on June 17, 2021, 10:22:59 AM
Now, disabling the globe format, which earlier required one click, now it takes two.

Noticed that shortly after my post above.

Foot, meet mouth. :-/
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on June 17, 2021, 12:41:13 PM
Quote from: CNGL-Leudimin on June 17, 2021, 10:22:59 AM
Huh? I can disable labels on Satellite view, and has always been that way. Now, disabling the globe format, which earlier required one click, now it takes two.
Interesting... globe view has been disabled by default for me for a while now, to the point where I often forgot it's there.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 17, 2021, 01:27:25 PM
Quote from: empirestate on June 17, 2021, 09:50:50 AM
I see they also did not fix the toggle setting not being retained for labels in Satellite view. This regression goes back a number of years now.

Quote from: CNGL-Leudimin on June 17, 2021, 10:22:59 AM
Huh? I can disable labels on Satellite view, and has always been that way. Now, disabling the globe format, which earlier required one click, now it takes two.

If I go to satellite and turn off labels, and then go to street view, labels reappear when I get back out of street view.  Similarly, if I go to satellite, and then switch to terrain (or whatever map type), labels reappear when I get back to satellite again.  This has been true for quite some time, and it annoys me.
Title: Re: Google Maps just fucking SUCKS now
Post by: Caps81943 on June 17, 2021, 01:33:03 PM
Another thing I've noticed lately is a new street view layer - alongside traditional street view and photosphere like before, they now have "Photo Path," essentially user-driven street view.

In every single case I've seen (admittedly not a ton), "Photo Path" has been AWFUL, but at least it only shows up if there's no traditional street view or photosphere series for the road.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on June 18, 2021, 09:18:19 AM
Quote from: CNGL-Leudimin on June 17, 2021, 10:22:59 AM
Huh? I can disable labels on Satellite view, and has always been that way.

Yeah, but is your selection retained? Or do you have to disable the labels each and every time you enter satellite view?
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 18, 2021, 11:41:01 AM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.
Probably the pandemic slowing things down.
Title: Re: Google Maps just fucking SUCKS now
Post by: stevashe on June 18, 2021, 11:54:18 AM
Quote from: Roadgeekteen on June 18, 2021, 11:41:01 AM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.
Probably the pandemic slowing things down.

That, and they never post streetview images right away, at least in my experience. I remember seeing a streetview car go by in October a few years ago but having to wait until the spring to see the images featuring my car be posted.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 18, 2021, 12:05:49 PM
Quote from: stevashe on June 18, 2021, 11:54:18 AM
Quote from: Roadgeekteen on June 18, 2021, 11:41:01 AM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.
Probably the pandemic slowing things down.

That, and they never post streetview images right away, at least in my experience. I remember seeing a streetview car go by in October a few years ago but having to wait until the spring to see the images featuring my car be posted.
It seems like they did a big dump last fall and a big dump 2 falls ago, we will probably get another one later this year.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 18, 2021, 03:02:33 PM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.

Parts of the Bay Area have May 2021 imagery (https://goo.gl/maps/vUaGhyBZBSMY1FoN9). But then Google is headquartered in the area, so go figure.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 18, 2021, 05:57:45 PM
Quote from: jakeroot on June 18, 2021, 03:02:33 PM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.

Parts of the Bay Area have May 2021 imagery (https://goo.gl/maps/vUaGhyBZBSMY1FoN9). But then Google is headquartered in the area, so go figure.
Good. I'm always worried that google will stop updating street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on June 19, 2021, 06:46:40 PM
Quote from: Roadgeekteen on June 15, 2021, 01:14:39 PM
A more real complaint but I wish google would upgrade their imagery on very rural roads like US 50 and US 6 in Nevada.

For the two tourists planning vacations and the 17 road geeks planning interstates there that click on them every year?
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on June 19, 2021, 07:20:08 PM
Quote from: Roadgeekteen on June 18, 2021, 11:41:01 AM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.
Probably the pandemic slowing things down.
Google lists the states and counties they're visiting for StreetView tours on their site (https://www.google.com/streetview/explore/) (scroll down a bit to see the list).
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 19, 2021, 09:34:36 PM
Quote from: kkt on June 19, 2021, 06:46:40 PM
Quote from: Roadgeekteen on June 15, 2021, 01:14:39 PM
A more real complaint but I wish google would upgrade their imagery on very rural roads like US 50 and US 6 in Nevada.

For the two tourists planning vacations and the 17 road geeks planning interstates there that click on them every year?
Many people know that US 50 is the loneliest road in America and might want to see what it's like. Also it's nice to have all roads have at least 1 high definition image.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on June 20, 2021, 02:33:13 AM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.

They don't have any imagery for my section of my neighborhood. And it's not a new neighborhood; it was built in 1976. Google just hasn't ever bothered to drive around here.

Their satellite imagery of downtown Oklahoma City is woefully out-of-date too. OKC built a major park and a brand new convention center and it's all just bare dirt on satellite view. At least it shows up on Street View being close enough to completion that it's recognizable.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 20, 2021, 12:06:38 PM
Quote from: Scott5114 on June 20, 2021, 02:33:13 AM
Quote from: STLmapboy on June 18, 2021, 11:35:52 AM
Wish they'd take the GSV cars for another comprehensive whirl again. Most US places have imagery from 2019, it seems like. Newest I can find is November 2020. If anyone has anything newer, please link it.

They don't have any imagery for my section of my neighborhood. And it's not a new neighborhood; it was built in 1976. Google just hasn't ever bothered to drive around here.

Their satellite imagery of downtown Oklahoma City is woefully out-of-date too. OKC built a major park and a brand new convention center and it's all just bare dirt on satellite view. At least it shows up on Street View being close enough to completion that it's recognizable.
My town is very well covered, with all roads having good quality imagery. But some towns are poorly covered.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on June 27, 2021, 08:32:41 PM
I've noticed now that Google Maps has 'private' roads, like driveways and gated communities, marked in a dark grey color. Annoyingly however, you now can't access street view for any of those private roads where it was available before. And to make things worse, there are a lot of roads that are incorrectly marked as private.
Title: Re: Google Maps just fucking SUCKS now
Post by: jamess on June 29, 2021, 02:42:12 PM
Quote from: bm7 on June 27, 2021, 08:32:41 PM
I've noticed now that Google Maps has 'private' roads, like driveways and gated communities, marked in a dark grey color. Annoyingly however, you now can't access street view for any of those private roads where it was available before. And to make things worse, there are a lot of roads that are incorrectly marked as private.

Yeah my mom lives in a gated community and they had streetview before. Now its gone.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 29, 2021, 02:56:57 PM
Quote from: jamess on June 29, 2021, 02:42:12 PM
Quote from: bm7 on June 27, 2021, 08:32:41 PM
I've noticed now that Google Maps has 'private' roads, like driveways and gated communities, marked in a dark grey color. Annoyingly however, you now can't access street view for any of those private roads where it was available before. And to make things worse, there are a lot of roads that are incorrectly marked as private.

Yeah my mom lives in a gated community and they had streetview before. Now its gone.
Stupid privacy
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 29, 2021, 03:07:12 PM
I checked a bunch of gated communities in suburban Tacoma: no street view.

But I don't remember checking if they had them before, so... IDK.

I don't remember that dark grey color before, and it seems to match one-to-one with "private roads", and I can't find a single stretch that has street view imagery.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on June 29, 2021, 06:23:17 PM
Why is Google redoing the Street View in big cities every single year when some places with no coverage (or 2007 imagery) deserves it more?
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on June 29, 2021, 06:29:36 PM
Quote from: LilianaUwU on June 29, 2021, 06:23:17 PM
Why is Google redoing the Street View in big cities every single year when some places with no coverage (or 2007 imagery) deserves it more?
I've been asking this very question for a while now.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on June 29, 2021, 06:34:16 PM
With that said, one of the baffling omissions in my province is Route 132 between route 287 and Route de Kamouraska (https://www.google.ca/maps/dir/47.5664382,-69.8661885/47.5025938,-69.9378947/@47.5032494,-69.9394011,17z/data=!4m9!4m8!1m5!3m4!1m2!1d-69.9378947!2d47.5025938!3s0x4cbefa276a1f187b:0xba89e081e3db2879!1m0!3e0?hl=en).
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on June 29, 2021, 07:08:42 PM
Quote from: LilianaUwU on June 29, 2021, 06:23:17 PM
Why is Google redoing the Street View in big cities every single year when some places with no coverage (or 2007 imagery) deserves it more?

Given that it's Google, the answer somehow is advertising. So, my guess is that they update more frequently in areas with more businesses.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on June 29, 2021, 07:11:51 PM
Quote from: CtrlAltDel on June 29, 2021, 07:08:42 PM
Quote from: LilianaUwU on June 29, 2021, 06:23:17 PM
Why is Google redoing the Street View in big cities every single year when some places with no coverage (or 2007 imagery) deserves it more?

Given that it's Google, the answer somehow is advertising. So, my guess is that they update more frequently in areas with more businesses.

brb becoming a business magnate in the middle of nowhere
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on June 29, 2021, 09:56:22 PM
Quote from: LilianaUwU on June 29, 2021, 06:34:16 PM
With that said, one of the baffling omissions in my province is Route 132 between route 287 and Route de Kamouraska (https://www.google.ca/maps/dir/47.5664382,-69.8661885/47.5025938,-69.9378947/@47.5032494,-69.9394011,17z/data=!4m9!4m8!1m5!3m4!1m2!1d-69.9378947!2d47.5025938!3s0x4cbefa276a1f187b:0xba89e081e3db2879!1m0!3e0?hl=en).

Major highways in NY that need coverage:
* Almost all of NY-7B
* NY-7 from I-88 exit 4 to Belden
* US-11 from Beers Rd just north of Glen Castle to I-81 exit 7, from around Itaska to Whitney Point, a few miles north of Messengerville, and near Sandfordville
* NY-26 from Whitney Point to Upper Lisle
* NY-34 from Reniff Rd to Van Etten, and from Spencer to Newfield Depot Rd / CR 130
* NY-34B from King Ferry to Fleming
* NY-41 from Greene to Smithville Flats, and a few miles north of Willet
* NY-41A from NY-359 to Hencoop Rd
* NY-52 around Lake Huntington
* NY-79 from NY-227 to Applegate Corner, and from Whitney Point to Chenango Forks
* NY-90 from King Ferry to Genoa
* NY-146 west of Nash Rd
* All of NY-235
* All of NY-421 (TBF it's like the remotest state route in NY)
* NY-430 north of Titus Rd
* NY-443 west of Drebitko Rd and Cook Rd
* NY-990V east of Prattsville Rd / CR 39 (TBF it's just a reference route undergoing an identity crisis)
Title: Re: Google Maps just fucking SUCKS now
Post by: jamess on June 30, 2021, 07:57:11 PM
Quote from: jakeroot on June 29, 2021, 03:07:12 PM
I checked a bunch of gated communities in suburban Tacoma: no street view.

But I don't remember checking if they had them before, so... IDK.

I don't remember that dark grey color before, and it seems to match one-to-one with "private roads", and I can't find a single stretch that has street view imagery.

My understanding was if the vehicle could get in, they would. The first round of streetview images by my moms was when the second phase was under construction, so the gates were open from 8-4 every day. The second round was probably when the gate was open because someone else had come in.

That is, while the arterial had an update every year or two, the gated community had two passes in 10 years. But now those are completely gone.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on June 30, 2021, 10:00:27 PM
Quote from: jamess on June 30, 2021, 07:57:11 PM
Quote from: jakeroot on June 29, 2021, 03:07:12 PM
I checked a bunch of gated communities in suburban Tacoma: no street view.

But I don't remember checking if they had them before, so... IDK.

I don't remember that dark grey color before, and it seems to match one-to-one with "private roads", and I can't find a single stretch that has street view imagery.

My understanding was if the vehicle could get in, they would. The first round of streetview images by my moms was when the second phase was under construction, so the gates were open from 8-4 every day. The second round was probably when the gate was open because someone else had come in.

That is, while the arterial had an update every year or two, the gated community had two passes in 10 years. But now those are completely gone.

Some of the gated communities I checked had open gates when the street view vehicle went by, but there is no imagery within the gates. I would have assumed that, at least from time to time, the GSV vehicle would have entered the communities, but there is no evidence of that. At least now.
Title: Re: Google Maps just fucking SUCKS now
Post by: mgk920 on June 30, 2021, 10:08:49 PM
They recently (up?)graded their desktop site to change how you can toggle between 'labels = 'ON'' and 'labels = 'OFF'' in their satellite images.  Not really an upgrade in that it is still the same number of clicks to do it (it should be one).

Mike
Title: Re: Google Maps just fucking SUCKS now
Post by: wxfree on June 30, 2021, 11:39:37 PM
The mobile application has offline maps available, which I like, since I see no reason to use mobile data to load maps when I save them with my home connection.  I have a very inexpensive data plan, because I have a very good connection at home, so even though I always have more than I need, I try not to waste mobile data.  The maps expire, which is reasonable, since Google doesn't want people complaining about the low accuracy of maps that are 15 years old.  Previously, they expired every 30 days, which isn't a problem for me, except that the automatic update feature only worked on maps that I used with whatever frequency Google considered to be adequate.  I might expect a map to be there, but since I hadn't used it in several months, Google thought it was too unimportant to update, even though I told it to keep it updated.

Now the maps expire after a year, which is much more reasonable.  Except that the maps now disappear well before expiring.  I have no idea why.  After much less than a year, the area of maps I downloaded is no longer available.  Originally I had a huge area of maps selected to have available at all times.  That didn't work since I usually don't use the program and it wouldn't automatically update maps I didn't use.  But I could just update all of them every month, and that worked, for a while.  Now the maps have an expiration date of one year after downloading, but the actual time when they disappear is unknown, so I can't count on it at all.  Now I just try to remember to update any map I may want on the day I want it.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on June 30, 2021, 11:54:28 PM
I tried that unofficially before a trip to Mt. Rainier.  National Parks are notoriously bad about not allowing cell towers, so I visited some trails by Paradise on my mobile at home before heading there in person.  Strangely, a half mile away from the tourist facilities, I was getting enough of a signal for location services to locate me on the map.  I left Timeline on, but the rest of the trip east of Paradise was just a dashed line the rest of the way to Ohanapecosh.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on July 01, 2021, 11:22:13 AM
Quote from: ErmineNotyours on June 30, 2021, 11:54:28 PM
Strangely, a half mile away from the tourist facilities, I was getting enough of a signal for location services to locate me on the map.

I don't think you need cell signal for GPS functionality to work. If I'm out in the sticks with no service, my GPS app will give me accurate lat/lon and elevation, and the little blue "current location" dot will still appear on Google Maps... but the map tiles won't load.
Title: Re: Google Maps just fucking SUCKS now
Post by: DeaconG on July 01, 2021, 01:14:46 PM
Quote from: US 89 on July 01, 2021, 11:22:13 AM
Quote from: ErmineNotyours on June 30, 2021, 11:54:28 PM
Strangely, a half mile away from the tourist facilities, I was getting enough of a signal for location services to locate me on the map.

I don't think you need cell signal for GPS functionality to work. If I'm out in the sticks with no service, my GPS app will give me accurate lat/lon and elevation, and the little blue "current location" dot will still appear on Google Maps... but the map tiles won't load.

As long as those GPS sats stay in Clarke orbit (and the US military doesn't get cute), and youre outside, you'll get a signal.
Title: Re: Google Maps just fucking SUCKS now
Post by: ErmineNotyours on July 01, 2021, 11:19:01 PM
Quote from: US 89 on July 01, 2021, 11:22:13 AM
Quote from: ErmineNotyours on June 30, 2021, 11:54:28 PM
Strangely, a half mile away from the tourist facilities, I was getting enough of a signal for location services to locate me on the map.

I don't think you need cell signal for GPS functionality to work. If I'm out in the sticks with no service, my GPS app will give me accurate lat/lon and elevation, and the little blue "current location" dot will still appear on Google Maps... but the map tiles won't load.

I'm pretty sure my device doesn't have real GPS, but triangulates its location from known cell towers and hot spots.  Which is fine, since you need to have your own carrier's signal or wi-fi for it to actually draw the maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on July 02, 2021, 12:55:09 AM
Quote from: ErmineNotyours on June 30, 2021, 11:54:28 PM
I tried that unofficially before a trip to Mt. Rainier.  National Parks are notoriously bad about not allowing cell towers, so I visited some trails by Paradise on my mobile at home before heading there in person.  Strangely, a half mile away from the tourist facilities, I was getting enough of a signal for location services to locate me on the map.  I left Timeline on, but the rest of the trip east of Paradise was just a dashed line the rest of the way to Ohanapecosh.

A couple of years ago, Mt. Rainier National Park discovered there was a lot of room in the attic of the new visitor center - enough that cell phone antennas could be installed without being visible.  After a period of consideration of how that would change the visitor experience, they decided to go ahead and install the antennas.  I think it's probably a good thing overall.  Being able to get a signal could help someone in trouble get help before it turned into a disaster.  Also the people staying at the Inn will appreciate being able to make calls from their rooms instead of walking to the "telephone room" off the lobby.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on July 03, 2021, 12:43:31 PM
Re: street view on restricted access/private roads, a small section of Normandy Rd in Middletown, NJ still has street view.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on July 03, 2021, 01:14:19 PM
Anyone else have this issue with Google Street View not loading properly?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 03, 2021, 02:25:26 PM
Quote from: sprjus4 on July 03, 2021, 01:14:19 PM
Anyone else have this issue with Google Street View not loading properly?

I've had issues trying to drop the peg-man, and having it get all laggy. I have to reload the page.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on July 03, 2021, 02:35:35 PM
Quote from: jakeroot on July 03, 2021, 02:25:26 PM
Quote from: sprjus4 on July 03, 2021, 01:14:19 PM
Anyone else have this issue with Google Street View not loading properly?

I've had issues trying to drop the peg-man, and having it get all laggy. I have to reload the page.
Same here for the past couple days, usually have to reload 2-3 times to get it to respond. Quite annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 03, 2021, 06:09:44 PM
Heck, just getting Google Maps to load without causing my phone to go to sleep is now evidently a challenge.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 03, 2021, 09:01:20 PM
I've been having issues with the mini-map in street view often not loading.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 03, 2021, 09:19:04 PM
Quote from: vdeane on July 03, 2021, 09:01:20 PM
I've been having issues with the mini-map in street view often not loading.

I have also noticed this.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on July 03, 2021, 09:40:51 PM
Google maps is prone to freeze occasionally.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on July 03, 2021, 09:51:48 PM
Quote from: vdeane on July 03, 2021, 09:01:20 PM
I've been having issues with the mini-map in street view often not loading.
Same. Google Maps has just gotten slower and slower with more and more issues. :sleep:
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 03, 2021, 10:26:45 PM
Quote from: sprjus4 on July 03, 2021, 09:51:48 PM
Quote from: vdeane on July 03, 2021, 09:01:20 PM
I've been having issues with the mini-map in street view often not loading.
Same. Google Maps has just gotten slower and slower with more and more issues. :sleep:
It doesn't even run properly on my work computer anymore.  I have to reload the page every couple minutes due to freezes.  Since it's only the work computer and desktop applications still render as well as ever, though, part of me wonders if it's everyone remoting in to their machines due to work from home choking off the network bandwidth.  I guess I'll find out next week, when everyone's back in the office three days per week (instead of the one day per week we're at now, especially since I anticipate almost everyone being in the office Tuesday/Wednesday/Thursday).
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 07, 2021, 01:04:49 PM
Quote from: jakeroot on July 03, 2021, 02:25:26 PM
Quote from: sprjus4 on July 03, 2021, 01:14:19 PM
Anyone else have this issue with Google Street View not loading properly?

I've had issues trying to drop the peg-man, and having it get all laggy. I have to reload the page.

The same thing is happening to me. It's driving me crazy. It's slightly better on Chrome, but on Firefox, it is frustratingly slow.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on July 14, 2021, 11:30:33 AM
PA-579 and I-840 construction only show up without Globe View.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 14, 2021, 11:31:48 AM
Quote from: TheGrassGuy on July 14, 2021, 11:30:33 AM
PA-579 and I-840 construction only show up without Globe View.

Different views having different satellite imagery isn't anything new, is it?
Title: Re: Google Maps just fucking SUCKS now
Post by: jamess on July 15, 2021, 04:07:39 PM
Having a lot of issues with streetview.

I grab the little man, the roads turn blue, and then it doesnt matter where I click, nothing happens
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on July 15, 2021, 04:35:02 PM
Google My Maps does not have street view, which is annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on July 15, 2021, 04:45:17 PM
Quote from: jamess on July 15, 2021, 04:07:39 PM
Having a lot of issues with streetview.

I grab the little man, the roads turn blue, and then it doesnt matter where I click, nothing happens

I've had that issue the past few weeks as well. Not all the time, but intermittently.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on July 16, 2021, 05:29:13 PM
The "Street View won't open" thing has been happening to me as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on July 16, 2021, 05:32:57 PM
It works for me, though I have to wait about 20 seconds after I release my left mouse button over the road I want to view for it to enter Street View.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 16, 2021, 05:39:17 PM
I have been having excellent luck with refreshing. Fixes every single issue ... until it eventually reoccurs shortly thereafter :-P
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 17, 2021, 01:32:23 AM
Quote from: ozarkman417 on July 16, 2021, 05:32:57 PM
It works for me, though I have to wait about 20 seconds after I release my left mouse button over the road I want to view for it to enter Street View.

I don't know if I would call that working.  :spin:
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 23, 2021, 06:15:16 PM
The COVID-19 layer on Google Maps displays data at the county level, meaning that it literally took a fucking plague to get Google to let you actually see county lines on Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on July 25, 2021, 07:50:25 PM
Quote from: Scott5114 on July 23, 2021, 06:15:16 PM
The COVID-19 layer on Google Maps displays data at the county level, meaning that it literally took a fucking plague to get Google to let you actually see county lines on Google Maps.

To piggy-back on that sentiment, why is there such an apparent aversion among all of the web-based mapping services to providing just a good, general-purpose planimetric base map? I mean, all that's really missing at this point is a comprehensive dataset of administrative boundaries, which any of the traditional mapmakers would have included without a single thought to the contrary.
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on July 25, 2021, 08:38:43 PM
This is jacked up. wtf

https://www.google.com/maps/@35.688191,-78.8420963,16.96z
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 25, 2021, 08:55:53 PM
Quote from: tolbs17 on July 25, 2021, 08:38:43 PM
This is jacked up. wtf

https://www.google.com/maps/@35.688191,-78.8420963,16.96z

What are you complaining about? While there might be issues with the road itself, that's not Google's fault.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 25, 2021, 08:56:19 PM
Quote from: empirestate on July 25, 2021, 07:50:25 PM
Quote from: Scott5114 on July 23, 2021, 06:15:16 PM
The COVID-19 layer on Google Maps displays data at the county level, meaning that it literally took a fucking plague to get Google to let you actually see county lines on Google Maps.

To piggy-back on that sentiment, why is there such an apparent aversion among all of the web-based mapping services to providing just a good, general-purpose planimetric base map? I mean, all that's really missing at this point is a comprehensive dataset of administrative boundaries, which any of the traditional mapmakers would have included without a single thought to the contrary.

Thus why I use OpenStreetMap anytime I need general geographic information not related to routing or imagery. I've been told the boundaries aren't 100% accurate, but they are at least usable. I wouldn't put money down on anything depending on that data, but it's generally helpful enough for answering most "does this road enter that county" type questions.
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on July 25, 2021, 08:58:11 PM
Quote from: 1 on July 25, 2021, 08:55:53 PM
Quote from: tolbs17 on July 25, 2021, 08:38:43 PM
This is jacked up. wtf

https://www.google.com/maps/@35.688191,-78.8420963,16.96z

What are you complaining about? While there might be issues with the road itself, that's not Google's fault.
It's under construction and there's two ramps going in the same direction.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on July 26, 2021, 12:53:30 AM
Notice how one of them is marked as "closed" ? Also, what if that's the configuration? How is Google wrong?
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on July 26, 2021, 05:11:32 AM
Quote from: sprjus4 on July 26, 2021, 12:53:30 AM
Notice how one of them is marked as "closed" ? Also, what if that's the configuration? How is Google wrong?
Because they have 2 ramps going in the same direction!
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on July 26, 2021, 10:20:19 AM
Quote from: Scott5114 on July 25, 2021, 08:56:19 PM
Thus why I use OpenStreetMap anytime I need general geographic information not related to routing or imagery. I've been told the boundaries aren't 100% accurate, but they are at least usable. I wouldn't put money down on anything depending on that data, but it's generally helpful enough for answering most "does this road enter that county" type questions.

I used to use Mapquest and/or Bing for county line questions, but neither shows lower-tier boundaries. As I recall, though, Yahoo Maps used to show those, at least for incorporated places. And of course, most DOTs publish a set of general highway maps that show all the basics.

On the other hand, even the venerable USGS has pulled away from including boundaries as a standard layer on their current generation of maps. At least their stated reason is that there isn't yet an accurate nationwide dataset of sufficient cartographic quality (and no, TIGER data doesn't fit that bill).
Title: Re: Google Maps just fucking SUCKS now
Post by: JoePCool14 on July 26, 2021, 10:50:05 AM
(Meta) I'm probably going to get some flack for this, but can we please change the title of thread to remove the unnecessary profanity? I don't like constantly seeing this thread with its title in my feed. It doesn't need to be there. It just makes other people ask what kind of website I'm on.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 26, 2021, 12:38:12 PM
Quote from: tolbs17 on July 26, 2021, 05:11:32 AM
Quote from: sprjus4 on July 26, 2021, 12:53:30 AM
Notice how one of them is marked as "closed" ? Also, what if that's the configuration? How is Google wrong?
Because they have 2 ramps going in the same direction!
It's a construction configuration.  North Carolina is probably doing some work that necessitated a temporary ramp.  Would you rather Google just pretend the regular ramp never existed and not show it?  That's what they used to do, once they decided to become real-time accurate.  I remember when a huge chunk of I-70 across Colorado was deleted from existence due to a landslide.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on July 26, 2021, 01:38:32 PM
Quote from: tolbs17 on July 26, 2021, 05:11:32 AM
Because they have 2 ramps going in the same direction!
Quote from: sprjus4 on July 26, 2021, 12:53:30 AM
Notice how one of them is marked as "closed" ? Also, what if that's the configuration? How is Google wrong?
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on July 26, 2021, 02:56:38 PM
Quote from: vdeane on July 26, 2021, 12:38:12 PM
Quote from: tolbs17 on July 26, 2021, 05:11:32 AM
Quote from: sprjus4 on July 26, 2021, 12:53:30 AM
Notice how one of them is marked as "closed" ? Also, what if that's the configuration? How is Google wrong?
Because they have 2 ramps going in the same direction!
It's a construction configuration.  North Carolina is probably doing some work that necessitated a temporary ramp.  Would you rather Google just pretend the regular ramp never existed and not show it?  That's what they used to do, once they decided to become real-time accurate.  I remember when a huge chunk of I-70 across Colorado was deleted from existence due to a landslide.
no
Quote from: sprjus4 on July 26, 2021, 01:38:32 PM
Quote from: tolbs17 on July 26, 2021, 05:11:32 AM
Because they have 2 ramps going in the same direction!
Quote from: sprjus4 on July 26, 2021, 12:53:30 AM
Notice how one of them is marked as "closed" ? Also, what if that's the configuration? How is Google wrong?
oh. I see.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 27, 2021, 11:00:18 AM
Quote from: tolbs17 on July 26, 2021, 02:56:38 PM
oh. I see.

Think before you type.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 27, 2021, 07:10:29 PM
Quote from: kphoger on July 27, 2021, 11:00:18 AM
Quote from: tolbs17 on July 26, 2021, 02:56:38 PM
oh. I see.

Think before you type.
It's a bit late in suggesting this correction.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on July 28, 2021, 06:15:10 PM
https://goo.gl/maps/DUhxvYdTZUusFEYZ9

They may suck, but I admire their dedication to update GSV while fording roads underwater during an ocean storm.
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on August 09, 2021, 05:37:03 PM
A few changes I noticed today regarding alternate routes of major highways. One good and one bad.

Bad: https://www.google.com/maps/@42.9882796,-89.3876359,12z
From a distance, Google only shows this segment of US-14 (the north/south freeway in the middle) as "US-18 Alternate", which makes no sense. Even less so because it's not as if US-18 is significantly more important than US-14. In fact, it really plays second fiddle to US-151 along that concurrency.

Good: https://www.google.com/maps/@43.3665169,-89.3927615,15.32z
On this segment of US-51 there is written text that denotes it as the alternate route for I-39/90/94, which it is. However, from a distance only the US-51 shield shows up.
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on August 09, 2021, 05:42:09 PM
Quote from: JoePCool14 on July 26, 2021, 10:50:05 AM
(Meta) I'm probably going to get some flack for this, but can we please change the title of thread to remove the unnecessary profanity? I don't like constantly seeing this thread with its title in my feed. It doesn't need to be there. It just makes other people ask what kind of website I'm on.
+1
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 09, 2021, 06:33:38 PM
I'm tired of the overlaid coloring in the background.  Can't tell if it's terrain or parkland because even if it's the latter, half the time you can't find the label.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on August 15, 2021, 11:43:45 AM
GSV Impossible Challenge #2: Put Pegman inside St Martin-in-the-Fields.

(Also, for official GSV imagery that looks like custom imagery for a change, try going to The Serpentine in Kensington Gardens.)
Title: Re: Google Maps just fucking SUCKS now
Post by: english si on August 15, 2021, 12:59:03 PM
Quote from: Rothman on August 09, 2021, 06:33:38 PMI'm tired of the overlaid coloring in the background.  Can't tell if it's terrain or parkland because even if it's the latter, half the time you can't find the label.
In my area, which is dominated by protected area, it's a total mess to see anything else that's meant to be green (woodland, golf courses, etc) as they are in the protected area and so the background is green anyway.
Quote from: TheGrassGuy on August 15, 2021, 11:43:45 AM(Also, for official GSV imagery that looks like custom imagery for a change, try going to The Serpentine in Kensington Gardens.)
The Serpentine is in Hyde Park. Which goes back to Rothman's point about park labels being rather hidden.

GSV in London is often awkward. There's the many buildings they've done 'see inside' for, there's the user contributions, there's the zig-zagging in squares, covering all the paths in major parks and other major footpaths. The Serpentine seems to be like a building 'see inside', but also part of the Royal Parks coverage.

I did initially think they did Olympic Venue coverage back in 2012, hence why they had a pedalo trip in the Serpentine covered (they did outdoor swimming there), but they didn't. It would have been something worth doing. They do have some random offices in what was the Press Centre, and also the Gym in the Aquatics Centre, as part of their 'see inside' stuff. They did St Pancras (https://www.google.co.uk/maps/@51.5304159,-0.1256908,2a,75y,126.08h,101.14t/data=!3m6!1e1!3m4!1ssU2I6yQmRjU5HgHEr6mkvQ!2e0!7i13312!8i6656?hl=en) in the ~100-day (?) window in 2012 between unveiling the rings there, and having to take them down at the end of the games as the rings are a trademark.
Title: Google Earth updates
Post by: jakeroot on August 18, 2021, 03:28:50 AM
Noticed some pretty big changes for Google Earth lately (starting maybe a month or two ago, with big changes recently):

First, some layers have "outdated" labels:

* Borders and Labels (Outdated)
* Places (Outdated)
* Roads (Outdated)

However, all three have been replaced by identical layers (apart from roads which now has "...and Transportation" tacked on) that have much newer information that appears to be loaded directly in from Google Maps.

The new 'transportation' addition means that rail lines, etc are visible.

The roads themselves look much more like how they look in Google Maps, which makes for some odd results when 3D is enabled ("terrain" must be checked). If it's not clear (see the originals on Flickr), the road lines start to disappear when 3D imagery is turned on:

(https://live.staticflickr.com/65535/51386763250_00ba2be948_b.jpg)
Google Earth w/ 3D (https://flic.kr/p/2mhSAqJ) by Jacob Root (https://www.flickr.com/photos/62537709@N03/), on Flickr

(https://live.staticflickr.com/65535/51386002608_1ff00fc24b_b.jpg)
Google Earth no 3D (https://flic.kr/p/2mhNGjd) by Jacob Root (https://www.flickr.com/photos/62537709@N03/), on Flickr


There is definitely some big changes that have to occur under-the-hood before Google Earth (Desktop) is fully up to speed with current info from Google Maps, especially trying to get it to work in 3D. But it's great to have more current data, since Earth was sorely out of date.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 19, 2021, 05:55:16 PM
Is Google Maps broken for anyone else?  Can't get driving directions at all, no matter the origin and destination.

(https://live.staticflickr.com/65535/51390194160_983d381b5f_k.jpg) (https://flic.kr/p/2mibbjm)
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 19, 2021, 06:18:18 PM
Huh, I am having the same issue. Worked fine earlier today (can't remember exactly when I last used it).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 19, 2021, 06:21:42 PM
The world is in chaos!
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 19, 2021, 06:25:01 PM
Working okay for me at the moment.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 19, 2021, 06:43:17 PM
Quote from: jakeroot on August 19, 2021, 06:25:01 PM
Working okay for me at the moment.

Driving directions?

Still broken for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 19, 2021, 06:48:21 PM
But...now it works.  That's too bad.  I wanted chaos.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 19, 2021, 06:52:29 PM
Quote from: Rothman on August 19, 2021, 06:48:21 PM
But...now it works.  That's too bad.  I wanted chaos.

Now slow but functional for me as well.

I think there's more than enough chaos without Google Maps down.  :meh: :coffee:
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 19, 2021, 07:49:06 PM
It was broken earlier for me as well... but as been said recently, it works now.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 21, 2021, 04:56:40 PM
Google appears to have removed the display of points when using the measure tool.  This makes it impossible to move or remove points, severely reducing the functionality of the tool.  WTF, Google?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 21, 2021, 08:45:15 PM
Quote from: vdeane on August 21, 2021, 04:56:40 PM
Google appears to have removed the display of points when using the measure tool.  This makes it impossible to move or remove points, severely reducing the functionality of the tool.  WTF, Google?

100% chance that's a bug.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on August 21, 2021, 09:27:37 PM
Quote from: vdeane on August 21, 2021, 04:56:40 PM
Google appears to have removed the display of points when using the measure tool.  This makes it impossible to move or remove points, severely reducing the functionality of the tool.  WTF, Google?

So I don't have the points either, but (for me at least) the points appear to be there but invisible, because I can drag but not remove points. When I drag, the points appear but disappear as soon as I stop dragging. I can right click and clear the measurement completely but not remove a specific point.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on August 21, 2021, 10:42:27 PM
Quote from: SectorZ on August 21, 2021, 09:27:37 PM
Quote from: vdeane on August 21, 2021, 04:56:40 PM
Google appears to have removed the display of points when using the measure tool.  This makes it impossible to move or remove points, severely reducing the functionality of the tool.  WTF, Google?

So I don't have the points either, but (for me at least) the points appear to be there but invisible, because I can drag but not remove points. When I drag, the points appear but disappear as soon as I stop dragging. I can right click and clear the measurement completely but not remove a specific point.

I just tried and had no issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 21, 2021, 10:42:41 PM
Quote from: SectorZ on August 21, 2021, 09:27:37 PM
Quote from: vdeane on August 21, 2021, 04:56:40 PM
Google appears to have removed the display of points when using the measure tool.  This makes it impossible to move or remove points, severely reducing the functionality of the tool.  WTF, Google?

So I don't have the points either, but (for me at least) the points appear to be there but invisible, because I can drag but not remove points. When I drag, the points appear but disappear as soon as I stop dragging. I can right click and clear the measurement completely but not remove a specific point.
Are you sure you're actually dragging the existing points and not just adding new ones?  I tried to drag the existing ones with how it's displayed, but couldn't figure out how.  I just kept getting new ones.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on August 21, 2021, 10:46:49 PM
Quote from: vdeane on August 21, 2021, 10:42:41 PM
Quote from: SectorZ on August 21, 2021, 09:27:37 PM
Quote from: vdeane on August 21, 2021, 04:56:40 PM
Google appears to have removed the display of points when using the measure tool.  This makes it impossible to move or remove points, severely reducing the functionality of the tool.  WTF, Google?

So I don't have the points either, but (for me at least) the points appear to be there but invisible, because I can drag but not remove points. When I drag, the points appear but disappear as soon as I stop dragging. I can right click and clear the measurement completely but not remove a specific point.
Are you sure you're actually dragging the existing points and not just adding new ones?  I tried to drag the existing ones with how it's displayed, but couldn't figure out how.  I just kept getting new ones.

Yeah I can still drag. Odd how I'm not having issues with it.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 22, 2021, 06:53:27 AM
I can only add new points.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on August 22, 2021, 09:24:14 AM
Quote from: thspfc on August 09, 2021, 05:42:09 PM
Quote from: JoePCool14 on July 26, 2021, 10:50:05 AM
(Meta) I'm probably going to get some flack for this, but can we please change the title of thread to remove the unnecessary profanity? I don't like constantly seeing this thread with its title in my feed. It doesn't need to be there. It just makes other people ask what kind of website I'm on.
+1

Not against the forum rules, so there's no justification for a mod to change it, and the OP is no longer active on the forum.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 23, 2021, 02:00:50 PM
Quote from: Scott5114 on August 22, 2021, 09:24:14 AM
Not against the forum rules, so there's no justification for a mod to change it, and the OP is no longer active on the forum.

So he wouldn't be around to object if it were changed without a specific rules-based justification?   ;-)
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 23, 2021, 02:54:52 PM
Quote from: kphoger on August 23, 2021, 02:00:50 PM
Quote from: Scott5114 on August 22, 2021, 09:24:14 AM
Not against the forum rules, so there's no justification for a mod to change it, and the OP is no longer active on the forum.

So he wouldn't be around to object if it were changed without a specific rules-based justification?   ;-)

Kind of what I was thinking as well...

If enough of us object to the title, maybe we should just start a new thread.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 23, 2021, 02:56:41 PM
...with the word 'bleeping' in there instead.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on August 23, 2021, 06:35:44 PM
I support keeping the thread title the way it is. In fact, fuck.

Edit: I know it's not something to scream at a high function or a job interview but I will never understand why some people get so worked up over four letter Anglo Saxon words. It's hilarious but frustrating at the same time. Lord knows it's gotten me in trouble more than once. I guess I ought to just conform and wash my mouth with some soap. Maybe that'll do it.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 23, 2021, 06:52:57 PM
Meanwhile, I don't get how some people can't understand that some language is socially inappropriate in mixed company.

Obviously, some words convey more coarse, boorish intensity than others:  I mean, that's half the reason our language has so many synonyms to begin with, isn't it?  The most timid of language is most appropriate to use in all contexts.  Some other, stronger language might be appropriate between co-workers at a staff meeting but not around children at a daycare.  And other, more vulgar language simply shouldn't be used publicly except quite judiciously under extreme circumstances.

Saying "it's just a word" completely ignores the function that language serves in culture.  Sure, I get it that sometimes language like 'just fucking sucks' or 'total and absolute shit' conveys just the force of emotion that you intend to convey–but that doesn't necessarily mean it's appropriate to use in a public setting.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on August 23, 2021, 06:58:11 PM
Quote from: kphoger on August 23, 2021, 06:52:57 PM
Meanwhile, I don't get how some people can't understand that some language is socially inappropriate in mixed company.

Obviously, some words convey more coarse, boorish intensity than others:  I mean, that's half the reason our language has so many synonyms to begin with, isn't it?  The most timid of language is most appropriate to use in all contexts.  Some other, stronger language might be appropriate between co-workers at a staff meeting but not around children at a daycare.  And other, more vulgar language simply shouldn't be used publicly except quite judiciously under extreme circumstances.

Saying "it's just a word" completely ignores the function that language serves in culture.  Sure, I get it that sometimes language like 'just fucking sucks' or 'total and absolute shit' conveys just the force of emotion that you intend to convey–but that doesn't necessarily mean it's appropriate to use in a public setting.
I suppose when a perfectly valid and rather great point is made about something and the person listening would rather become irate if profanity was used is perplexing to me. Let's have a rocket scientist explain why we need to go to Mars and expand our species but get made he said the f word when discussing why he is annoyed with those that say "we need to feed the children first."

You know the terms and conditions on this website. Don't like the profanity then leave. At least I'm told that in the opposition direction when I left Jim's group on Facebook for saying the word "shit." Of course I am always open to a public and civil discussion on it. To me it is just a word and we as a species need to move and evolve over getting mad at words like fuck or thinking they are only appropriate in certain situations.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 23, 2021, 07:11:10 PM
Quote from: Plutonic Panda on August 23, 2021, 06:58:11 PM
You know the terms and conditions on this website. Don't like the profanity then leave.

Huh?  Something can be inappropriate but not against the rules.

It's kind of like if my son were reading online articles for homework and the author had decided some profanity or raunchy similes would make his article more punchy.  Yeah, such might not be against the terms and rules of the publication, but it's still in bad taste.

Do keep in mind that it's not always only the intended audience who sees things you type.  Those of us with kids at home sometimes browse the forum at home, and our kids can walk by and read what you type.  Those of us who get on the forum at work might have a co-worker or boss read the open tab when coming over to our desk to talk about something.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 23, 2021, 07:12:48 PM
I support changing the title. While it's not as bad as the three swear words on this forum that actually get censored (four if you count two variants of the same word), or the one in the thread that had to be retitled recently, it's still bad, and it stays in your browser history.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on August 23, 2021, 07:18:26 PM
Quote from: kphoger on August 23, 2021, 07:11:10 PM
Quote from: Plutonic Panda on August 23, 2021, 06:58:11 PM
You know the terms and conditions on this website. Don't like the profanity then leave.

Huh?  Something can be inappropriate but not against the rules.
I was more or less referring to how it usually goes when someone uses profanity in a forum or group when the rules clearly state you aren't supposed to. I am part of tons of Facebook groups so I don't go through every rule and apparently in FreewayJim group you aren't supposed to use profanity. I used one profanity word(shit) in a post of nearly 1000 characters and wasn't given a chance to correct it just had it deleted and told not to use profanity which prompted me to post about it. Jim decided to leave that one up(which contained profanity yet again which told me what I needed to know about him) and was dog piled with comments like "don't like it leave," which I did.

If you got kids at home seeing a thread title with the word fuck and are worried it'll influence them to use it, I feel sorry for you. If your kid is actually one that doesn't use profanity behind your back then what is the worry? I fail to see the issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 23, 2021, 07:26:58 PM
Quote from: Plutonic Panda on August 23, 2021, 07:18:26 PM
I was more or less referring to how it usually goes when someone uses profanity in a forum or group when the rules clearly state you aren't supposed to. I am part of tons of Facebook groups so I don't go through every rule and apparently in FreewayJim group you aren't supposed to use profanity.

Why wouldn't you just assume that a group disallows it?  That seems more commonsense to me.  I mean, I would assume that.  Until I saw other members using such language, that is.

Quote from: Plutonic Panda on August 23, 2021, 07:18:26 PM
If you got kids at home seeing a thread title with the word fuck and are worried it'll influence them to use it, I feel sorry for you. If your kid is actually one that doesn't use profanity behind your back then what is the worry? I fail to see the issue.

Do you have kids?  I try to teach my sons how to speak respectfully and appropriately.  The more casual profanity they hear or read, the more it is reinforced to them that it's acceptable to use that language.  That's how people learn language, after all:  picking up on what everyone else is doing.

Personally, foul language isn't something that has really come up in our family.  I recently overheard my youngest son use a swear word (he's six), but I didn't give him the benefit of a reaction, so nothing came of it.  But my point is that my wife and I like to be able to choose what they see and hear and read at different points in their development (sex scenes in a movie? foul language in a Netflix show? drug use? etc, etc), and I'm sure we're not alone.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on August 23, 2021, 07:39:08 PM
I don't have kids.

But I don't assume really assume it's appropriate to use foul language anywhere especially in front of women and children just that I think it's ridiculous for others to get angry at those who do.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheHighwayMan3561 on August 23, 2021, 08:01:18 PM
Quote from: 1 on August 23, 2021, 07:12:48 PM
I support changing the title. While it's not as bad as the three swear words on this forum that actually get censored (four if you count two variants of the same word), or the one in the thread that had to be retitled recently, it's still bad, and it stays in your browser history.

Unless you're using the forum on a work computer, why does this matter?
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on August 23, 2021, 09:35:03 PM
We have no rules against profanity on this forum, by the consensus of the staff. We aren't going to enforce any rules against profanity on this forum. If you're concerned about someone seeing a word on your screen and judging you about it, either stop hanging out around assholes that look on your screen without your permission, or install a browser extension that filters it on your end.

I used to have a coworker that would always very obviously look at whatever was on your screen when she entered the room. I got in the habit of either hitting Win+D to minimize all windows whenever she approached, or alt-tabbing to a text file discussing goings-on in Quindaro, in the hopes of setting up a dilemma where she would either ask what the hell I was writing about and tip off that she was spying on me, or have to wonder exactly who she was trapped in the same room with for the next nine hours.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 23, 2021, 09:58:41 PM
Quote from: Scott5114 on August 23, 2021, 09:35:03 PM
hitting Win+D to minimize all windows

Wow, thanks for the tip. I honestly can't believe I've made it this far in life without knowing this was a thing!
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on August 23, 2021, 10:23:45 PM
Quote from: webny99 on August 23, 2021, 09:58:41 PM
Quote from: Scott5114 on August 23, 2021, 09:35:03 PM
hitting Win+D to minimize all windows

Wow, thanks for the tip. I honestly can't believe I've made it this far in life without knowing this was a thing!

Another useful one is Win+L, which locks the desktop, and Win+R, which brings up the Run dialog (useful for quickly running system utilities like charmap).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 23, 2021, 10:24:40 PM
Looks like the change to the measurement tool is intentional and likely won't be fixed: https://support.google.com/maps/thread/122238475/why-can-i-not-drag-points-on-the-measure-distance-feature?hl=en

It would seem that it's time to find another place to measure distances on maps.  Earth doesn't display intermediate distances (a problem when I'm trying to location tag photos on my site), and other sites vary between similar and not having such a tool at all.  Right now the best bet would appear to be Yandex (https://yandex.com/maps/?ll=-75.553925%2C42.951341&z=8.69), but it's optimized for Europe and can't be set for miles - only km, requiring conversion for all measurements.  It also doesn't display the distances on the line, but one can get the distance to any intermediate point, so you can just put a point where you want it.

Quote from: TheHighwayMan394 on August 23, 2021, 08:01:18 PM
Quote from: 1 on August 23, 2021, 07:12:48 PM
I support changing the title. While it's not as bad as the three swear words on this forum that actually get censored (four if you count two variants of the same word), or the one in the thread that had to be retitled recently, it's still bad, and it stays in your browser history.

Unless you're using the forum on a work computer, why does this matter?
For the record, some people do in fact browse this forum at work during breaks.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 23, 2021, 10:39:43 PM
Quote from: Scott5114 on August 23, 2021, 10:23:45 PM
Another useful one is Win+L, which locks the desktop

Yes, that one I did know about and use quite frequently. :D



Quote from: vdeane on August 23, 2021, 10:24:40 PM
Quote from: TheHighwayMan394 on August 23, 2021, 08:01:18 PM
Quote from: 1 on August 23, 2021, 07:12:48 PM
I support changing the title. While it's not as bad as the three swear words on this forum that actually get censored (four if you count two variants of the same word), or the one in the thread that had to be retitled recently, it's still bad, and it stays in your browser history.
Unless you're using the forum on a work computer, why does this matter?
For the record, some people do in fact browse this forum at work during breaks.

Yes, myself included, and for that reason among others, I support shifting discussion to a new thread if the name isn't going to be changed (and notice how I've handled the title on my last several posts here).
Title: Re: Google Maps just fucking SUCKS now
Post by: TheHighwayMan3561 on August 23, 2021, 10:52:44 PM
Quote from: webny99 on August 23, 2021, 10:39:43 PM
Quote from: vdeane on August 23, 2021, 10:24:40 PM
Quote from: TheHighwayMan394 on August 23, 2021, 08:01:18 PM
Quote from: 1 on August 23, 2021, 07:12:48 PM
I support changing the title. While it's not as bad as the three swear words on this forum that actually get censored (four if you count two variants of the same word), or the one in the thread that had to be retitled recently, it's still bad, and it stays in your browser history.
Unless you're using the forum on a work computer, why does this matter?
For the record, some people do in fact browse this forum at work during breaks.

Yes, myself included, and for that reason among others, I support shifting discussion to a new thread if the name isn't going to be changed (and notice how I've handled the title on my last several posts here).

I think you and vdeane both missed my point, which is if you're concerned about getting in trouble at work for this, you shouldn't be visiting this forum during work.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on August 23, 2021, 11:48:07 PM
Quote from: webny99 on August 23, 2021, 10:39:43 PM
Yes, myself included, and for that reason among others, I support shifting discussion to a new thread if the name isn't going to be changed (and notice how I've handled the title on my last several posts here).

See, but that would be a duplicate thread, so my job then would be to merge that thread into this one...

Quote from: TheHighwayMan394 on August 23, 2021, 10:52:44 PM
I think you and vdeane both missed my point, which is if you're concerned about getting in trouble at work for this, you shouldn't be visiting this forum during work.

This. I also can't imagine an employer that is totally cool with you using company resources to browse websites for personal use, but only if they don't say "fuck" on them anywhere.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on August 23, 2021, 11:51:18 PM
Quote from: Scott5114 on August 23, 2021, 11:48:07 PM
Quote from: TheHighwayMan394 on August 23, 2021, 10:52:44 PM
I think you and vdeane both missed my point, which is if you're concerned about getting in trouble at work for this, you shouldn't be visiting this forum during work.

This. I also can't imagine an employer that is totally cool with you using company resources to browse websites for personal use, but only if they don't say "fuck" on them anywhere.

And in the rare case that they do I'm sure you could just avoid this thread. I viewed this thread often on my school computer when I was in HS and no one gave a hoot.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 24, 2021, 12:08:59 PM
Quote from: I-55 on August 23, 2021, 11:51:18 PM
gave a hoot

Thank you.   :awesomeface:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 24, 2021, 03:45:03 PM
I'll try and avoid profanity here, but do use it as an intensifier here and there. So, in a way, I do appreciate the forum being more lax about the rules. But like swearing in real life, there are good and bad places to use it, and not everyone is good at it. For this thread, I don't like that it's attached to every. single. post.

Maybe the rule is "no profanity in thread subjects"?

I do find it quite difficult to imagine someone walking by a computer and being taken aback by the visibility of a swear word. Considering all of the awful things someone can say, do, and share on the internet, we really shouldn't be too alarmed by the occasional f-word.

I don't think this website is one of those places that should be avoided at the workplace, or really any other place. But like any site, it's best to keep it to yourself. If someone insists on peering over your shoulder, then they really ought to temper their reactions. It's not their business to police the websites you use, as long as the website isn't professedly forbidden by your administration or workplace.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on August 24, 2021, 05:39:27 PM
re. profanity in title:

I want to point out that the title is entirely appropriate for the original purpose of the thread, but not for its current purpose. Back when the thread was created, Google changed Maps from a good tool to a buggy, laggy mess that hardly worked. Everyone was pissed off, and justifiably so. But today the thread has become simply the Google Maps thread, talking about its quirks and complaining (but not ranting) about design changes. If someone new read the title without noticing the recent content of the thread, he or she would think that we still absolutely abhor Google Maps' interface (I'm pretty sure we don't). Just wanted to mention that.

That being said, even though I would like to see the profanity removed, overall it's not a big issue and shouldn't really be a priority for the forum to change.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 24, 2021, 06:56:31 PM
For the record, Google Maps still sucks.
Title: Re: Google Maps just fucking IS ALTOGETHER OBJECTIONABLE now
Post by: empirestate on August 24, 2021, 09:23:48 PM
Quote from: JoePCool14 on July 26, 2021, 10:50:05 AM
(Meta) I'm probably going to get some flack for this, but can we please change the title of thread to remove the unnecessary profanity? I don't like constantly seeing this thread with its title in my feed. It doesn't need to be there. It just makes other people ask what kind of website I'm on.

I'm on board. I've edited my subject line accordingly.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 24, 2021, 10:06:44 PM
Quote from: empirestate on August 24, 2021, 09:23:48 PM
Quote from: JoePCool14 on July 26, 2021, 10:50:05 AM
(Meta) I'm probably going to get some flack for this, but can we please change the title of thread to remove the unnecessary profanity? I don't like constantly seeing this thread with its title in my feed. It doesn't need to be there. It just makes other people ask what kind of website I'm on.

I'm on board. I've edited my subject line accordingly.


For some reason when I read your version of the title (probably because "now" got bumped to another line, so I didn't see it at first), it suddenly occurred to me that the curse word could be read as a verb instead of an adverb. ...
Title: Re: Google Maps just fucking IS ALTOGETHER OBJECTIONABLE now
Post by: Plutonic Panda on August 24, 2021, 11:39:53 PM
Quote from: empirestate on August 24, 2021, 09:23:48 PM
Quote from: JoePCool14 on July 26, 2021, 10:50:05 AM
(Meta) I'm probably going to get some flack for this, but can we please change the title of thread to remove the unnecessary profanity? I don't like constantly seeing this thread with its title in my feed. It doesn't need to be there. It just makes other people ask what kind of website I'm on.

I'm on board. I've edited my subject line accordingly.
Thank you kind sir.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on August 25, 2021, 02:02:53 AM
Quote from: kphoger on August 23, 2021, 07:26:58 PM
Do you have kids?  I try to teach my sons how to speak respectfully and appropriately.  The more casual profanity they hear or read, the more it is reinforced to them that it's acceptable to use that language.  That's how people learn language, after all:  picking up on what everyone else is doing.

Coincidentally, I stumbled onto this (https://preview.redd.it/er2xmj9p5bj71.jpg?width=773&auto=webp&s=637262bec8566eaa9288bd910f4abde3b619d6d4) earlier today. (NSFW)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 25, 2021, 04:25:17 PM
Quote from: SafeSpeeder on August 25, 2021, 04:05:29 PM
1st Amendment Right.

I don't think anyone is suggesting government censorship.
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on August 25, 2021, 04:26:30 PM
Quote from: SafeSpeeder on August 25, 2021, 04:05:29 PM
LOL who cares? 1st Amendment Right.


I'm shocked that you don't actually understand what the 1st Amendment means.
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on August 25, 2021, 06:22:42 PM
Quote from: SafeSpeeder on August 25, 2021, 06:11:25 PM
As long as you are not threatening an illegal action, encouraging criminal activity, you can say whatever you want to anyone. Profanity certain isn't one of those two.


Well you are wrong. Lies aren't protected speech for instance.

And anyway none of this applies to a moderated Internet forum which is a private business and can set the rules it wants.

The 1st amendment only protects an individual against action from the federal government, and was applied to the states via the 14th amendment.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on August 25, 2021, 06:22:59 PM
Quote from: SafeSpeeder on August 25, 2021, 06:11:25 PM
As long as you are not threatening an illegal action, encouraging criminal activity, you can say whatever you want to anyone. Profanity certain isn't one of those two.

Nope. I suggest you read the text of the actual amendment.

Quote from: United States Constitution, Amendment ICongress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.

Note underlined portion. This originally only applied to the federal government. The Supreme Court has since used the Due Process Clause in the 14th amendment to extend this, and it now applies to state and local governments and their various agencies. It does not apply to private entities.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on August 25, 2021, 10:46:59 PM
And now after not having issues with it, I am having the measuring tool bug. Go figure.
Title: Re: Google Maps just fucking PERFORMS FELLATIO ON UNSPECIFIED RECIPIENTS now
Post by: empirestate on August 25, 2021, 10:49:05 PM
Quote from: SafeSpeeder on August 25, 2021, 06:26:23 PM
Well obviously, any individual entity can set their own speech rules but that doesn't automatically make profanity a bad thing.

Exactly. Nothing whatsoever to do with the First Amendment.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on August 25, 2021, 11:40:40 PM
^^^^
Why did I google the second word in all caps? I have regerts.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 25, 2021, 11:51:55 PM
This thread got derailed.  Irrelevant posts to the topic of Google Maps should be deleted.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on August 26, 2021, 01:25:18 PM
Quote from: I-55 on August 25, 2021, 11:40:40 PM
^^^^
Why did I google the second word in all caps? I have regerts.
I wouldn't try lemonparty if I were you.
Title: Why do people care about this thread's title so much?
Post by: SkyPesos on August 26, 2021, 04:23:14 PM
It seems like the dots for the endpoints and angles for the measure tool are back! It was super annoying without it. Only noticed it after I was done measuring my fictional NYC subway line, as I was so used to having it, and forgot that it was gone for the past few days.
(https://i.imgur.com/Br84JRb.png?1)
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on August 26, 2021, 04:34:05 PM
Quote from: SafeSpeeder on August 25, 2021, 06:26:23 PM
Well obviously, any individual entity can set their own speech rules but that doesn't automatically make profanity a bad thing.

Please provide a list of why profanity can be a good thing.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 26, 2021, 04:44:02 PM
I have rarely had a problem with google maps.  Occasionally it takes time to adjust to change when they update it, although I use it primarily if not exclusively for my maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 26, 2021, 04:49:17 PM
Quote from: jeffandnicole on August 26, 2021, 04:34:05 PM
Please provide a list of why profanity can be a good thing.

The argument seems to go like this:

Quote from: hbelkins on July 22, 2021, 06:46:04 PM
If you're not literate enough to converse without cursing, well, I don't know what to say to you. There is absolutely no point that cannot be made without resorting to profanity.

Quote from: Scott5114 on July 22, 2021, 07:37:56 PM
As someone who prides myself on my abilities with the written word, choosing to eliminate fucking from my vocabulary makes about as much sense as a painter eliminating orange from their palette would.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheHighwayMan3561 on August 26, 2021, 04:56:37 PM
Quote from: kphoger on August 26, 2021, 04:49:17 PM
Quote from: jeffandnicole on August 26, 2021, 04:34:05 PM
Please provide a list of why profanity can be a good thing.

The argument seems to go like this:

Quote from: hbelkins on July 22, 2021, 06:46:04 PM
If you're not literate enough to converse without cursing, well, I don't know what to say to you. There is absolutely no point that cannot be made without resorting to profanity.

Quote from: Scott5114 on July 22, 2021, 07:37:56 PM
As someone who prides myself on my abilities with the written word, choosing to eliminate fucking from my vocabulary makes about as much sense as a painter eliminating orange from their palette would.

I can articulate an argument with language akin to a Ph.D. dissertation. I can also spew fucks and shits like there's no tomorrow. These things aren't mutually exclusive.
Title: Re: Google Maps just fucking SUCKS now
Post by: TXtoNJ on August 26, 2021, 05:11:32 PM
Quote from: SkyPesos on August 26, 2021, 04:23:14 PM
It seems like the dots for the endpoints and angles for the measure tool are back! It was super annoying without it. Only noticed it after I was done measuring my fictional NYC subway line, as I was so used to having it, and forgot that it was gone for the past few days.
(https://i.imgur.com/Br84JRb.png?1)

Fixed for me too
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on August 26, 2021, 05:12:12 PM
Quote from: TheHighwayMan394 on August 26, 2021, 04:56:37 PM
Quote from: kphoger on August 26, 2021, 04:49:17 PM
Quote from: jeffandnicole on August 26, 2021, 04:34:05 PM
Please provide a list of why profanity can be a good thing.

The argument seems to go like this:

Quote from: hbelkins on July 22, 2021, 06:46:04 PM
If you're not literate enough to converse without cursing, well, I don't know what to say to you. There is absolutely no point that cannot be made without resorting to profanity.

Quote from: Scott5114 on July 22, 2021, 07:37:56 PM
As someone who prides myself on my abilities with the written word, choosing to eliminate fucking from my vocabulary makes about as much sense as a painter eliminating orange from their palette would.

I can articulate an argument with language akin to a Ph.D. dissertation. I can also spew fucks and shits like there's no tomorrow. These things aren't mutually exclusive.


Agreed.  But I also know my audience.  And I am not going "spew fucks and shits" in a forum where I think it will make people uncomfortable.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on August 26, 2021, 07:17:10 PM
Back to the actual topic plus the profanity(sorry I couldn't help myself) I run maps on iOS and my only major complaint is on the customized maps there isn't a way to edit them. The pictures section of an added point/shape only shows the first picture added and won't enlarge others; it's annoying.

I also wish they'd differentiate freeways from non-freeways better. They still haven't added the OKC streetcar network either despite me emailing them multiple times about they only show the stations. I like in Apple Maps when you zoom out far it'll show the national Amtrak network. Google won't.
Title: Re: Google Maps SUCKS now
Post by: jakeroot on August 26, 2021, 07:37:34 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

Interesting. I tried searching for about ten different towns of various sizes, and it only ever shows the outline. I don't get any point, be it pointing to the centroid of the polygon or some town centre.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on August 26, 2021, 07:43:24 PM
Quote from: Plutonic Panda on August 26, 2021, 07:17:10 PM
I also wish they'd differentiate freeways from non-freeways better. They still haven't added the OKC streetcar network either despite me emailing them multiple times about they only show the stations. I like in Apple Maps when you zoom out far it'll show the national Amtrak network. Google won't.

It's probably the fault of the operating agency, as they are the ones submitting data to Google through GTFS.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 26, 2021, 07:56:40 PM
Quote from: Bruce on August 26, 2021, 07:43:24 PM
Quote from: Plutonic Panda on August 26, 2021, 07:17:10 PM
I also wish they'd differentiate freeways from non-freeways better. They still haven't added the OKC streetcar network either despite me emailing them multiple times about they only show the stations. I like in Apple Maps when you zoom out far it'll show the national Amtrak network. Google won't.

It's probably the fault of the operating agency, as they are the ones submitting data to Google through GTFS.

No. The data is just fine. The issue is that there are three road categories that have identical colors. From most to least important, they are freeway, one that's widely used outside the US but rarely used inside the US (for a US example, the MA 2 freeway west of I-495 is of this type), and major surface road.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 26, 2021, 08:23:31 PM
Quote from: SkyPesos on August 26, 2021, 04:23:14 PM
It seems like the dots for the endpoints and angles for the measure tool are back! It was super annoying without it. Only noticed it after I was done measuring my fictional NYC subway line, as I was so used to having it, and forgot that it was gone for the past few days.
(https://i.imgur.com/Br84JRb.png?1)
Hallelujah!  I can get the idea behind hiding the points - it does look nicer - but there needs to be a way to manipulate the points that have already been placed.  Perhaps they could have it display like it did before the fix, but have the points appear when mousing over the line?
Title: Re: Google Maps just fucking SUCKS now
Post by: cl94 on August 26, 2021, 08:28:40 PM
Quote from: SEWIGuy on August 26, 2021, 05:12:12 PM
But I also know my audience.  And I am not going "spew fucks and shits" in a forum where I think it will make people uncomfortable.

You obviously don't know your fuckin' audience.
Title: Re: Google Maps just fucking CREATES A REGION OF NEGATIVE PRESSURE now
Post by: Duke87 on August 26, 2021, 08:39:56 PM
Quote from: vdeane on August 26, 2021, 08:23:31 PM
Hallelujah!  I can get the idea behind hiding the points - it does look nicer - but there needs to be a way to manipulate the points that have already been placed.  Perhaps they could have it display like it did before the fix, but have the points appear when mousing over the line?

Just checked it and the distance measurement tool is back to normal here too.

So... we may never know how intentional or not that brief loss of function was.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 26, 2021, 09:14:54 PM
I can communicate with cursing like a sailor or refraining from cursing altogether, I am articulate enough with and without profanity.  I just choose to use no or very little / mild profanity most of the time.

Also, I have the ability to conduct myself in one of three ways.

I can act like an intellectual, using legalese (the language of attorneys) and making myself look almost as enlightened as my younger brother and my first cousin but not quite (their IQ is at least 10 points higher than mine, they really are brilliant), which, not to boast, I am of slightly above average intelligence.  There are very few areas of knowledge I know more than them.  Geography and transportation infrastructure is one of them.

Or I can try to blend in with "normal people".

Or I can REALLY dumb myself down and pass myself off as an absolute moron.

Usually, I try to choose my audience on which of said three ways on how to conduct myself, to make them comfortable.
Title: Re: Google Maps just FUCKING sucks now
Post by: NE2 on August 26, 2021, 10:08:54 PM
Quote from: Daniel Fiddler on August 26, 2021, 09:14:54 PM
Or I can REALLY dumb myself down and pass myself off as an absolute moron.
This tends to work best on aaroads, especially in fictional.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 26, 2021, 10:22:59 PM
Quote from: NE2 on August 26, 2021, 10:08:54 PM
Quote from: Daniel Fiddler on August 26, 2021, 09:14:54 PM
Or I can REALLY dumb myself down and pass myself off as an absolute moron.
This tends to work best on aaroads, especially in fictional.

If you feel this way about people planning fictional highways, why in God's name are you on a road forum?

Or are you just saying you think I am an idiot?

Not that I really give a shit from a 13 year old who has not really experienced life yet.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 26, 2021, 10:32:12 PM
^ He's not actually 13. And it's NE2, I wouldn't expect much with his comments or take them seriously.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 26, 2021, 10:40:28 PM
Quote from: sprjus4 on August 26, 2021, 10:32:12 PM
^ He's not actually 13. And it's NE2, I wouldn't expect much with his comments or take them seriously.

Yeah, I don't mind him calling me an idiot.  Although I do have a problem with him believing EVERYONE who posts fictional highways is an idiot.

Some plans are actually quite impressive.  Especially Skypesos's and Roadgeekteen's for their age.  I do believe Roadgeekteen does not have a full grasp of how expensive / unfeasible / unpractical (and in some places impossible) some of his bridges / tunnels would be, but hey, he just turned 18, it's not like he has a masters in civil engineering.  As much as I would LOVE to see a tunnel between Florida and Cuba (I don't think it could be built between Key West and Havana, US 1 over the keys can't even be 4 laned in places, much less interstate-ized), I know it can't be done, not only because of the 90+ mile distance, the Florida Straits are 3,000+ feet deep at the shortest distance across and 500 feet deep a bit further east where the crossing would be longer, approximately 120 miles long.

I'm nowhere near done with my planned rerouted Interstates.  I am still working on them, and other maps.  :)
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on August 26, 2021, 10:58:20 PM
According to Google Maps, these three interstates mysteriously have a gap in route now
(https://i.imgur.com/LTKdEk7.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 26, 2021, 11:00:16 PM
Quote from: SkyPesos on August 26, 2021, 10:58:20 PM
According to Google Maps, these three interstates mysteriously have a gap in route now
(https://i.imgur.com/LTKdEk7.png)

Map is unclickable, although I think I know where that is.  That's in Illinois isn't it, east of St. Louis, yes?
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 26, 2021, 11:23:27 PM
Quote from: jakeroot on August 26, 2021, 07:37:34 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

Interesting. I tried searching for about ten different towns of various sizes, and it only ever shows the outline. I don't get any point, be it pointing to the centroid of the polygon or some town centre.

I think it's different in NY and other states where everything is incorporated. The town outline almost never shows up unless the town is the only thing with that name; if there's a same-name village or same-name hamlet, it will default to that.

In some cases, you can get the town outline to show, but only if you specify "Town of..." as opposed to just the town name. And cases where there is a same-name hamlet are the worst, because there is no way whatsoever to get the outline. The towns of Walworth, Marion, and Tyre, NY, are some examples that fall into this category, but those are just three of many.

This inconsistency has been driving me batty as I work on compiling updated 2020 census numbers for every town in the state... but I suppose such is the downfall of everything in the state being incorporated.
Title: Re: Google Maps SUCKS now
Post by: hotdogPi on August 27, 2021, 06:58:47 AM
Quote from: webny99 on August 26, 2021, 11:23:27 PM
Quote from: jakeroot on August 26, 2021, 07:37:34 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

Interesting. I tried searching for about ten different towns of various sizes, and it only ever shows the outline. I don't get any point, be it pointing to the centroid of the polygon or some town centre.

I think it's different in NY and other states where everything is incorporated. The town outline almost never shows up unless the town is the only thing with that name; if there's a same-name village or same-name hamlet, it will default to that.

In some cases, you can get the town outline to show, but only if you specify "Town of..." as opposed to just the town name. And cases where there is a same-name hamlet are the worst, because there is no way whatsoever to get the outline. The towns of Walworth, Marion, and Tyre, NY, are some examples that fall into this category, but those are just three of many.

This inconsistency has been driving me batty as I work on compiling updated 2020 census numbers for every town in the state... but I suppose such is the downfall of everything in the state being incorporated.

Not an issue in Massachusetts, since only cities and towns are incorporated, there's no overlap, and there are no duplicate names. To make sure, I checked Andover, which has a CDP of the same name, and it still gave me the outline of the town. For some reason, the example image gave me a pond. Andover is famous for several things, and it shows something that exists in every town.
Title: Re: Google Maps just performs FELLATIO now
Post by: kphoger on August 27, 2021, 12:09:36 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

But did any of those use to show up with outlines?  If not, then there's no "now" to go along with the "sucks" part of your complaint.

In the states I'm usually searching in, unincorporated communities and CDPs tend to show up with just a pin and no boundaries, while actual villages/towns/cities show up with boundaries.  However, there are counterexamples:  unincorporated Greenwich, KS (https://goo.gl/maps/ej4utRNuDtijidz16), and unincorporated Future City, IL (https://goo.gl/maps/j59cGeBjRTQnAY5h6), show up with boundaries, for example.

Quote from: Daniel Fiddler on August 26, 2021, 10:22:59 PM

Quote from: NE2 on August 26, 2021, 10:08:54 PM

Quote from: Daniel Fiddler on August 26, 2021, 09:14:54 PM
Or I can REALLY dumb myself down and pass myself off as an absolute moron.

This tends to work best on aaroads, especially in fictional.

If you feel this way about people planning fictional highways, why in God's name are you on a road forum?

Uh, one might assume he's here to talk about actual roads.  Did you ever consider that might actually be the "normal" reason to be on this forum?
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on August 27, 2021, 12:26:57 PM
Quote from: Daniel Fiddler on August 26, 2021, 11:00:16 PM
Quote from: SkyPesos on August 26, 2021, 10:58:20 PM
According to Google Maps, these three interstates mysteriously have a gap in route now
(https://i.imgur.com/LTKdEk7.png)

Map is unclickable, although I think I know where that is.  That's in Illinois isn't it, east of St. Louis, yes?
Yes. I'll call the I-70 one the "Vandalia gap" , as according to google maps, that's around the point where I-70 now abruptly ends and all traffic are dumped onto US 40. :sombrero:
Title: Re: Google Maps just sucking DUCKS now
Post by: jakeroot on August 27, 2021, 12:31:51 PM
Quote from: kphoger on August 27, 2021, 12:09:36 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

But did any of those use to show up with outlines?  If not, then there's no "now" to go along with the "sucks" part of your complaint.

In the states I'm usually searching in, unincorporated communities and CDPs tend to show up with just a pin and no boundaries, while actual villages/towns/cities show up with boundaries.  However, there are counterexamples:  unincorporated Greenwich, KS (https://goo.gl/maps/ej4utRNuDtijidz16), and unincorporated Future City, IL (https://goo.gl/maps/j59cGeBjRTQnAY5h6), show up with boundaries, for example.

Interesting. When I search for CDPs and unincorporated communities here in Washington State, I still get outlines.

In fact, it took me to search for "Tyre, NY" to get a pin for any community.

Simple explanation may well be that Google simply does not possess boundary data for every "community" (CDP, town, city, village, etc).

edit: "Newhalem, WA" gives me a pin. First place I could find in WA that did not have a boundary associated with it. Took me to click on the name on the map to discover this.

edit 2: It seems that everything labelled "unincorporated community" will give me a pin. Everything else gets a full boundary. Evidently there are no boundaries associated with unincorporated communities. Otherwise I'm sure Google would show it.

edit 3: for comparison, CDPs in WA like Summit or Spanaway will absolutely give boundaries. Apparently there is boundary data for CDPs but not unincorporated communities.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 12:39:25 PM
Quote from: kphoger on August 27, 2021, 12:09:36 PM
unincorporated Greenwich, KS (https://goo.gl/maps/ej4utRNuDtijidz16), and unincorporated Future City, IL (https://goo.gl/maps/j59cGeBjRTQnAY5h6), show up with boundaries, for example.

Quote from: jakeroot on August 27, 2021, 12:31:51 PM
edit 2: It seems that everything labelled "unincorporated community" will give me a pin. Everything else gets a full boundary. Evidently there are no boundaries associated with unincorporated communities. Otherwise I'm sure Google would show it.

Did you click on my counterexamples, then?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 27, 2021, 12:45:34 PM
Quote from: kphoger on August 27, 2021, 12:09:36 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

But did any of those use to show up with outlines?  If not, then there's no "now" to go along with the "sucks" part of your complaint.

In the states I'm usually searching in, unincorporated communities and CDPs tend to show up with just a pin and no boundaries, while actual villages/towns/cities show up with boundaries.  However, there are counterexamples:  unincorporated Greenwich, KS (https://goo.gl/maps/ej4utRNuDtijidz16), and unincorporated Future City, IL (https://goo.gl/maps/j59cGeBjRTQnAY5h6), show up with boundaries, for example.

Quote from: Daniel Fiddler on August 26, 2021, 10:22:59 PM

Quote from: NE2 on August 26, 2021, 10:08:54 PM

Quote from: Daniel Fiddler on August 26, 2021, 09:14:54 PM
Or I can REALLY dumb myself down and pass myself off as an absolute moron.

This tends to work best on aaroads, especially in fictional.

If you feel this way about people planning fictional highways, why in God's name are you on a road forum?

Uh, one might assume he's here to talk about actual roads.  Did you ever consider that might actually be the "normal" reason to be on this forum?
I don't know about the specific examples, but I know I've seen town outlines in NY before, and now I don't.  It seems like Google is prioritizing hamlet areas over the actual incorporated towns to a far greater extent now than it once did.

Then there are the oddballs, like Québec City which only gets a pin for some reason (and I think it always did, too, despite being an incorporated city with boundaries).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 27, 2021, 12:52:22 PM
Quote from: kphoger on August 27, 2021, 12:39:25 PM
Quote from: kphoger on August 27, 2021, 12:09:36 PM
unincorporated Greenwich, KS (https://goo.gl/maps/ej4utRNuDtijidz16), and unincorporated Future City, IL (https://goo.gl/maps/j59cGeBjRTQnAY5h6), show up with boundaries, for example.

Quote from: jakeroot on August 27, 2021, 12:31:51 PM
edit 2: It seems that everything labelled "unincorporated community" will give me a pin. Everything else gets a full boundary. Evidently there are no boundaries associated with unincorporated communities. Otherwise I'm sure Google would show it.

Did you click on my counterexamples, then?

I did, but I was more referring to my discoveries within Washington State (which I did not make clear -- my bad).

Nevertheless, based on your counterexamples, it seems that Google will show boundaries if it happens to have the data, but otherwise does not. Why they have data on, say, Greenwich, KS I do not know.

In fact, given everything in this thread, it seems there is no hard and fast rule. Google either has boundary data or it doesn't. Full stop.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 12:54:04 PM
Quote from: vdeane on August 27, 2021, 12:45:34 PM
I don't know about the specific examples, but I know I've seen town outlines in NY before, and now I don't.

Quote from: jakeroot on August 27, 2021, 12:52:22 PM
Nevertheless, based on your counterexamples, it seems that Google will show boundaries if it happens to have the data, but otherwise does not. Why they have data on, say, Greenwich, KS I do not know.

And yet I doubt Google lost the data for the boundaries |vdeane| has noticed disappear.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on August 27, 2021, 12:59:19 PM
In my local area, there are a couple of ways in which Google Maps' presentation of township boundaries is squirrelly.

All of our named townships are PLSS survey townships six miles on a side.  (This is not always the case for Kansas counties in general--Shawnee County, for example, has irregularly shaped named townships.)  Thus, the starting expectation is that a Google search on any township will return a square.  In actuality, it returns the polygon that results from the subtraction of areas that belong to an incorporated municipality that the Census Bureau considers governmentally independent.  Thus, for Attica Township (the next one west from where I live), we get the following:

Attica Township minus Wichita (https://www.google.com/maps/place/Attica,+KS/@37.6930103,-97.600291,12z/data=!3m1!4b1!4m5!3m4!1s0x87bad92bd2c17ca3:0xa86fb9cf9b9bd5d8!8m2!3d37.7059374!4d-97.5355555)

Although both Wichita and Goddard are incorporated municipalities, only the former is considered governmentally independent.  (Sedgwick County has just two cities that are so designated:  Wichita and Bel Aire.)

Also, if you search for Wichita Township, not to be confused with the city of Wichita, you get no meaningful result.  The Wikipedia article for Sedgwick County maintains that it used to exist but does so no longer.  I am not sure what definition of "exists" the editors rely on since it is still available on the county GIS site for searching for plat maps--it is basically the square delimited by Meridian Avenue, 29th Street North, Woodlawn Boulevard, and Pawnee Avenue--though it is completely subsumed by the city of Wichita except for a small tongue of Eastborough (an enclave founded in 1937 as a tax dodge and itself also an incorporated municipality in Kansas).
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 27, 2021, 02:46:56 PM
Quote from: kphoger on August 27, 2021, 12:54:04 PM
And yet I doubt Google lost the data for the boundaries |vdeane| has noticed disappear.

That is very interesting. I had started writing my reply before she posted hers, so I only saw it briefly right before I posted my own reply. I truly have no explanation for what Google is doing.

Quote from: J N Winkler on August 27, 2021, 12:59:19 PM
Also, if you search for Wichita Township, not to be confused with the city of Wichita, you get no meaningful result.  The Wikipedia article for Sedgwick County maintains that it used to exist but does so no longer.  I am not sure what definition of "exists" the editors rely on since it is still available on the county GIS site for searching for plat maps--it is basically the square delimited by Meridian Avenue, 29th Street North, Woodlawn Boulevard, and Pawnee Avenue--though it is completely subsumed by the city of Wichita except for a small tongue of Eastborough (an enclave founded in 1937 as a tax dodge and itself also an incorporated municipality in Kansas).

Assuming some form of automation was used to gather the GIS data, I truly do have to wonder if kphoger's idea of Google losing data may actually be accurate. It seems incredibly unlikely, but I don't see how we can't rule it out.

There could also be a bug preventing the boundaries from being called up.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 02:58:35 PM
Quebec City really is an interesting one.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 27, 2021, 03:03:44 PM
Barre VT does show (the city), even though there's a town with the same name adjacent to it. Same with Rutland.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 27, 2021, 03:04:02 PM
Quote from: vdeane on August 27, 2021, 12:45:34 PM
Quote from: kphoger on August 27, 2021, 12:09:36 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

But did any of those use to show up with outlines?  If not, then there's no "now" to go along with the "sucks" part of your complaint.

In the states I'm usually searching in, unincorporated communities and CDPs tend to show up with just a pin and no boundaries, while actual villages/towns/cities show up with boundaries.  However, there are counterexamples:  unincorporated Greenwich, KS (https://goo.gl/maps/ej4utRNuDtijidz16), and unincorporated Future City, IL (https://goo.gl/maps/j59cGeBjRTQnAY5h6), show up with boundaries, for example.

Quote from: Daniel Fiddler on August 26, 2021, 10:22:59 PM

Quote from: NE2 on August 26, 2021, 10:08:54 PM

Quote from: Daniel Fiddler on August 26, 2021, 09:14:54 PM
Or I can REALLY dumb myself down and pass myself off as an absolute moron.

This tends to work best on aaroads, especially in fictional.

If you feel this way about people planning fictional highways, why in God's name are you on a road forum?

Uh, one might assume he's here to talk about actual roads.  Did you ever consider that might actually be the "normal" reason to be on this forum?
I don't know about the specific examples, but I know I've seen town outlines in NY before, and now I don't.  It seems like Google is prioritizing hamlet areas over the actual incorporated towns to a far greater extent now than it once did.

Then there are the oddballs, like Québec City which only gets a pin for some reason (and I think it always did, too, despite being an incorporated city with boundaries).

I enjoy talking about both actual and fictional roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 03:10:25 PM
Quote from: Daniel Fiddler on August 27, 2021, 03:04:02 PM
I enjoy talking about both actual and fictional roads.

Which is all well and good.  But you are, after all, the one who asked "why in God's name" someone who doesn't live in fantasyland is "on a road forum".

It's sort of like asking, If you feel this way about people playing fantasy football, why in God's name are you a football player?
Title: Re: Google Maps just performs FELLATIO now
Post by: webny99 on August 27, 2021, 03:15:18 PM
Quote from: kphoger on August 27, 2021, 12:09:36 PM
Quote from: webny99 on August 26, 2021, 07:08:28 PM
Back to the actual topic minus the profanity, one thing that frustrates me is when you search for a town (or township, as they're called in some states), and a little red pin comes up at the so-called town center (or even worse, the town hall) instead of a red outline of the entire town. Aaargh! Of course I'm not looking for an intersection here, I want boundaries!

But did any of those use to show up with outlines?  If not, then there's no "now" to go along with the "sucks" part of your complaint.

Oh, I'm not sure, considering I haven't been using Google Maps since its inception.  :)
I strongly suspect this has always been the case, but I was using "now" in the sense of "right now / presently".

(Side note: is it use to or used to? I can't keep it straight.)
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 27, 2021, 03:17:25 PM
Quote from: kphoger on August 27, 2021, 03:10:25 PM
Quote from: Daniel Fiddler on August 27, 2021, 03:04:02 PM
I enjoy talking about both actual and fictional roads.

Which is all well and good.  But you are, after all, the one who asked "why in God's name" someone who doesn't live in fantasyland is "on a road forum".

It's sort of like asking, If you feel this way about people playing fantasy football, why in God's name are you a football player?

I apologize. I did not think my statement would be interpreted that way.

What I was asking was why he thought people planning / discussing fictional highways were imbeciles (which I do believe I should defend everyone who does), unless he merely thought I was actually an imbecile (which I don't mind being called) or acting like one (which I admit I frequently do act like one).
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 27, 2021, 03:22:08 PM
Quote from: kphoger on August 27, 2021, 03:10:25 PM
It's sort of like asking, If you feel this way about people playing fantasy football, why in God's name are you a football player?

Eh... I'm not sure about that comparison. Plenty of real football players are annoyed by fantasy football, in part because it leads to players being treated like objects/commodities rather than actual real people.

And with that said, plenty of real roadgeeks are probably annoyed by fictional highways, too. Not everyone follows or even pays attention to the fictional board, and some only do so mostly just to provide a dose of reality for everyone's fantasies.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 27, 2021, 03:30:57 PM
Quote from: webny99 on August 27, 2021, 03:22:08 PM
Quote from: kphoger on August 27, 2021, 03:10:25 PM
It's sort of like asking, If you feel this way about people playing fantasy football, why in God's name are you a football player?

Eh... I'm not sure about that comparison. Plenty of real football players are annoyed by fantasy football, in part because it leads to players being treated like objects/commodities rather than actual real people.

And with that said, plenty of real roadgeeks are probably annoyed by fictional highways, too. Not everyone follows or even pays attention to the fictional board, and some only do so mostly just to provide a dose of reality for everyone's fantasies.

Most of my "fictional highways"  are changing route numbers to fit the grid better and more appropriate, reasonable, and prudent speed limits and minimums.  What upgrades and new terrain routes I suggest may cost a few hundred million, however, they are feasible.  No interstates out to the middle of nowhere or 100+ mile long bridges and tunnels.  Not saying FritzOwl and Roadgeekteen aren't visionaries, they indubitably are, they just need a jolt of reality.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 03:32:17 PM
Quote from: webny99 on August 27, 2021, 03:15:18 PM
(Side note: is it use to or used to? I can't keep it straight.)

Well "used" and "did use" are grammatically equivalent.  Therefore, it should be Did you use to but You used to.

Quote from: webny99 on August 27, 2021, 03:22:08 PM

Quote from: kphoger on August 27, 2021, 03:10:25 PM
It's sort of like asking, If you feel this way about people playing fantasy football, why in God's name are you a football player?

Eh... I'm not sure about that comparison. Plenty of real football players are annoyed by fantasy football, in part because it leads to players being treated like objects/commodities rather than actual real people.

And with that said, plenty of real roadgeeks are probably annoyed by fictional highways, too. Not everyone follows or even pays attention to the fictional board, and some only do so mostly just to provide a dose of reality for everyone's fantasies.

It sounds like you just agreed with my comparison.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on August 27, 2021, 03:50:21 PM
Quote from: kphoger on August 27, 2021, 03:32:17 PM
Quote from: webny99 on August 27, 2021, 03:22:08 PM

Quote from: kphoger on August 27, 2021, 03:10:25 PM
It's sort of like asking, If you feel this way about people playing fantasy football, why in God's name are you a football player?

Eh... I'm not sure about that comparison. Plenty of real football players are annoyed by fantasy football, in part because it leads to players being treated like objects/commodities rather than actual real people.

And with that said, plenty of real roadgeeks are probably annoyed by fictional highways, too. Not everyone follows or even pays attention to the fictional board, and some only do so mostly just to provide a dose of reality for everyone's fantasies.

It sounds like you just agreed with my comparison.

I thought you were saying that the football question would be a weird question to ask. I thought it was a perfectly reasonable question.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 03:52:41 PM
Yeah, I was.

Someone not liking fantasy football shouldn't preclude his playing football.

Someone not liking fictional highways shouldn't preclude his participation on a roadgeek forum.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on August 27, 2021, 03:58:43 PM
Quote from: webny99 on August 27, 2021, 03:15:18 PM
....

(Side note: is it use to or used to? I can't keep it straight.)

The latter. (https://brians.wsu.edu/2016/05/19/use-to/)
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 27, 2021, 04:01:15 PM
Quote from: kphoger on August 27, 2021, 03:52:41 PM
Yeah, I was.

Someone not liking fantasy football shouldn't preclude his playing football.

Someone not liking fictional highways shouldn't preclude his participation on a roadgeek forum.

I concur.  Everyone liking roads should be able to participate in the forum.  I am just saying that people should not imply that EVERYONE who plans fictional highways are imbeciles. I don't give a shit if someone calls me one, hell, I insult myself all the time.  It's when people berate an entire group I defend them.  He is entitled to his opinion.  Although everyone is welcome to participate here as far as I am concerned and should be cordial, and I apologize if you felt I was not.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 27, 2021, 04:05:16 PM
Quote from: 1995hoo on August 27, 2021, 03:58:43 PM

Quote from: webny99 on August 27, 2021, 03:15:18 PM
....

(Side note: is it use to or used to? I can't keep it straight.)

The latter. (https://brians.wsu.edu/2016/05/19/use-to/)

It depends. (https://www.merriam-webster.com/words-at-play/is-it-used-to-or-use-to)
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on August 27, 2021, 04:28:11 PM
Quote from: SkyPesos on August 26, 2021, 10:58:20 PM
According to Google Maps, these three interstates mysteriously have a gap in route now
(https://i.imgur.com/LTKdEk7.png)

There are some pretty big gaps in Texas as well:

(https://i.imgur.com/W6A6wLu.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 27, 2021, 04:39:25 PM
In other news, I-42 is now complete between Morehead City and Raleigh.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daniel Fiddler on August 27, 2021, 05:02:30 PM
Quote from: sprjus4 on August 27, 2021, 04:39:25 PM
In other news, I-42 is now complete between Morehead City and Raleigh.

It's not completely freeway though.  It's mostly freeway.  Unless google maps has not updated itself.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on August 27, 2021, 05:10:17 PM
Quote from: sprjus4 on August 27, 2021, 04:39:25 PM
In other news, I-42 is now complete between Morehead City and Raleigh.
And I-69. There was a new interchange planned for I-69 and I-465 on the south side of Indy, but I guess Google got exclusive info that INDOT did some changes here, so they rolled with it  :bigass:
Quote from: SkyPesos on July 24, 2021, 12:22:25 AM
Looks like Google Maps have I-69 labels on IN 37 between Martinsville and I-465 now even though it's incomplete  :-D
(https://i.imgur.com/QvtpsHy.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 27, 2021, 07:51:01 PM
Quote from: Daniel Fiddler on August 27, 2021, 05:02:30 PM
Quote from: sprjus4 on August 27, 2021, 04:39:25 PM
In other news, I-42 is now complete between Morehead City and Raleigh.

It's not completely freeway though.  It's mostly freeway.  Unless google maps has not updated itself.
It's not complete, there's still long stretches of non-freeway. But Google shows it as such, a full freeway.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on August 27, 2021, 07:51:31 PM
Quote from: SkyPesos on August 27, 2021, 05:10:17 PM
Quote from: sprjus4 on August 27, 2021, 04:39:25 PM
In other news, I-42 is now complete between Morehead City and Raleigh.
And I-69. There was a new interchange planned for I-69 and I-465 on the south side of Indy, but I guess Google got exclusive info that INDOT did some changes here, so they rolled with it  :bigass:
Quote from: SkyPesos on July 24, 2021, 12:22:25 AM
Looks like Google Maps have I-69 labels on IN 37 between Martinsville and I-465 now even though it's incomplete  :-D
(https://i.imgur.com/QvtpsHy.png)
Google isn't listing it as "I-69"  anymore, but it is still a freeway.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 27, 2021, 08:29:50 PM
Quote from: kphoger on August 27, 2021, 12:54:04 PM
Quote from: vdeane on August 27, 2021, 12:45:34 PM
I don't know about the specific examples, but I know I've seen town outlines in NY before, and now I don't.

Quote from: jakeroot on August 27, 2021, 12:52:22 PM
Nevertheless, based on your counterexamples, it seems that Google will show boundaries if it happens to have the data, but otherwise does not. Why they have data on, say, Greenwich, KS I do not know.

And yet I doubt Google lost the data for the boundaries |vdeane| has noticed disappear.

Sorry, playing catch up here with all the activity in this thread:

Town boundaries in New York do show up, but only if there's no same-name village, hamlet, or CDP. In other words, ironically, they only work if you search for the place. Hardly any place that you'd click organically on the map provides the outline, aside from actual cities (of which there's only 62 in the entire state), and a few select suburban towns, such as Brighton and Irondequoit.* But if you use the search function, Perinton, NY works just fine, and so does Galen, NY - as those particular names only refer to the town.

Personally, I haven't particularly noticed that this has gotten worse recently, but maybe it's just happened over time. But I definitely recall being frustrated by this quite some time ago - at least 1-2 years, if not longer. (And of course, I freely acknowledge that I use Google Maps for looking up municipalities way more than your average person... and probably even way more than your average person on this forum.)




*Oh, and villages. Villages show up just fine. But they're also irrelevant as far as Census population data is concerned, since their population is factored in to whatever town they're located in, so I don't normally have much use for them.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 27, 2021, 08:44:15 PM
Quote from: 1 on August 27, 2021, 03:03:44 PM
Barre VT does show (the city), even though there's a town with the same name adjacent to it. Same with Rutland.

This happens in NY, as well. Batavia, Lockport, and Canandaigua, NY, are all cities with adjacent same-named towns, and the city outlines do show up.

And surprisingly, if you search "Town of [insert town name]" for any of the above, the actual town outline will show up, complete with the hole in the middle where the city is located.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 27, 2021, 09:22:32 PM
It sounds to me like the Californians running Google Maps may be slightly confused at how municipalities work in New York, and the algorithms are not correctly processing town vs village vs city, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: billpa on August 29, 2021, 02:08:49 PM
Reminds me of Rand McNally with their metropolitan maps. The central cities are white and the suburban areas sort of a soft yellow/ gold. Suburban cities of a certain size get their own color but for some reason large (in many cases much larger) towns and townships do not.

Pixel 2

Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 30, 2021, 08:30:43 AM
Quote from: billpa on August 29, 2021, 02:08:49 PM
Reminds me of Rand McNally with their metropolitan maps. The central cities are white and the suburban areas sort of a soft yellow/ gold. Suburban cities of a certain size get their own color but for some reason large (in many cases much larger) towns and townships do not.

That's cartographically traditional. Towns/townships are generally treated as unincorporated area, regardless of their governmental status, because they are thought of as minor civil divisions, distinct from incorporated places like cities, villages, boroughs etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: billpa on August 30, 2021, 09:56:50 AM
It makes no sense.  Townships with close to 100k population with a formal government, police department, public works dept, etc. are 'unincorporated' but small cities with a few thousand are 'proper' municipalities?
Title: Re: Google Maps just fucking SUCKS now
Post by: TXtoNJ on August 30, 2021, 04:20:57 PM
Quote from: billpa on August 30, 2021, 09:56:50 AM
It makes no sense.  Townships with close to 100k population with a formal government, police department, public works dept, etc. are 'unincorporated' but small cities with a few thousand are 'proper' municipalities?


It doesn't. Really, there should be a distinction between CSA/PSA, MSA, and municipalities.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 30, 2021, 05:43:00 PM
Quote from: billpa on August 30, 2021, 09:56:50 AM
It makes no sense.  Townships with close to 100k population with a formal government, police department, public works dept, etc. are 'unincorporated' but small cities with a few thousand are 'proper' municipalities?

Mmm...not exactly. The comparison (again, cartographically) isn't between "unincorporated" and "proper", but rather between an areal subdivision of land (i.e., a town that is the subdivision of a county that is a subdivision of a state), and a concentrated settlement (i.e., a city or village, something that may be large or small, but generally has a centralized and relatively dense population).

So in that sense, a town can be just as "proper" an entity as a county or a state, while at the same time being no more comparable to a city or village than a state or a county would be.

Now of course, are there situations where this distinction gets very blurry, and do cartographers sometimes twist themselves into pretzels to depict them? Instead of answering yes or no, I'll just respond with "New Jersey." :-)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 30, 2021, 05:51:09 PM
Quote from: empirestate on August 30, 2021, 05:43:00 PM
Quote from: billpa on August 30, 2021, 09:56:50 AM
It makes no sense.  Townships with close to 100k population with a formal government, police department, public works dept, etc. are 'unincorporated' but small cities with a few thousand are 'proper' municipalities?

Mmm...not exactly. The comparison (again, cartographically) isn't between "unincorporated" and "proper", but rather between an areal subdivision of land (i.e., a town that is the subdivision of a county that is a subdivision of a state), and a concentrated settlement (i.e., a city or village, something that may be large or small, but generally has a centralized and relatively dense population).

So in that sense, a town can be just as "proper" an entity as a county or a state, while at the same time being no more comparable to a city or village than a state or a county would be.

Now of course, are there situations where this distinction gets very blurry, and do cartographers sometimes twist themselves into pretzels to depict them? Instead of answering yes or no, I'll just respond with "New Jersey." :-)

This may be the case in New York, but it is definitely not the case in Massachusetts or New Hampshire.

In this map below, the ones in all caps are cities. There's no geographical difference between cities and towns.

(https://www.sec.state.ma.us/cis/cispdf/City_Town_Map.pdf)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 30, 2021, 06:03:06 PM
fixed link...

Quote from: 1 on August 30, 2021, 05:51:09 PM
In this map below, the ones in all caps are cities. There's no geographical difference between cities and towns.

https://www.sec.state.ma.us/cis/cispdf/City_Town_Map.pdf
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on August 30, 2021, 06:07:35 PM
Quote from: jakeroot on August 30, 2021, 06:03:06 PM
fixed link...

Quote from: 1 on August 30, 2021, 05:51:09 PM
In this map below, the ones in all caps are cities. There's no geographical difference between cities and towns.

https://www.sec.state.ma.us/cis/cispdf/City_Town_Map.pdf

The image shows for me, despite ending in pdf.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 30, 2021, 08:22:33 PM
Quote from: 1 on August 30, 2021, 05:51:09 PM
This may be the case in New York, but it is definitely not the case in Massachusetts or New Hampshire.

In New England, to a greater or lesser extent, minor civil divisions and incorporated places (I'm using Census terminology, but the USGS works similarly) are virtually indistinguishable. However, the distinction isn't completely absent everywhere.

In Connecticut, for example, unincorporated towns still legally exist, even where they are completely coterminous with incorporated cities–which is in every case save one (Groton). Connecticut also has sub-town level incorporated boroughs, and Vermont likewise has villages.

While Massachusetts (and Rhode Island) no longer has any unincorporated areas, some mapmakers have treated towns there, as elsewhere in New England, as "unincorporated" areas, to maintain the NY-style distinction between less centrally populated areas (towns) and denser ones (cities).

New Hampshire, Vermont and Maine all do also have varying amounts of bona-fide unincorporated territory, with Maine being about half composed of it.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on August 30, 2021, 08:39:46 PM
And then there are the high tax and low tax portions of Rome and Saratoga Springs.
Title: Re: Google Maps SUCKS now
Post by: webny99 on August 30, 2021, 09:41:52 PM
Quote from: 1 on August 30, 2021, 06:07:35 PM
Quote from: jakeroot on August 30, 2021, 06:03:06 PM
fixed link...

Quote from: 1 on August 30, 2021, 05:51:09 PM
In this map below, the ones in all caps are cities. There's no geographical difference between cities and towns.

https://www.sec.state.ma.us/cis/cispdf/City_Town_Map.pdf

The image shows for me, despite ending in pdf.

The image isn't showing for me. I wouldn't have even known there was something there if you hadn't referenced it.
Title: Re: Google Maps just fucking SUCKS now
Post by: dlsterner on August 30, 2021, 10:56:57 PM
Quote from: webny99 on August 30, 2021, 09:41:52 PM
Quote from: 1 on August 30, 2021, 06:07:35 PM
Quote from: jakeroot on August 30, 2021, 06:03:06 PM
fixed link...

Quote from: 1 on August 30, 2021, 05:51:09 PM
In this map below, the ones in all caps are cities. There's no geographical difference between cities and towns.

https://www.sec.state.ma.us/cis/cispdf/City_Town_Map.pdf

The image shows for me, despite ending in pdf.

The image isn't showing for me. I wouldn't have even known there was something there if you hadn't referenced it.

Appears to be browser dependent.  The image shows correctly for me using Safari (my normal browser), but it does not show up when I tried both Firefox and Chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on August 31, 2021, 02:15:21 AM
Quote from: NE2 on August 30, 2021, 08:39:46 PM
And then there are the high tax and low tax portions of Rome and Saratoga Springs.

And Oneida.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 31, 2021, 12:28:14 PM
Quote from: dlsterner on August 30, 2021, 10:56:57 PM
Quote from: webny99 on August 30, 2021, 09:41:52 PM
Quote from: 1 on August 30, 2021, 06:07:35 PM
Quote from: jakeroot on August 30, 2021, 06:03:06 PM
fixed link...

Quote from: 1 on August 30, 2021, 05:51:09 PM
In this map below, the ones in all caps are cities. There's no geographical difference between cities and towns.

https://www.sec.state.ma.us/cis/cispdf/City_Town_Map.pdf

The image shows for me, despite ending in pdf.

The image isn't showing for me. I wouldn't have even known there was something there if you hadn't referenced it.

Appears to be browser dependent.  The image shows correctly for me using Safari (my normal browser), but it does not show up when I tried both Firefox and Chrome.

No access to Safari but does not work on any browser that I have installed (Edge, Chrome, Firefox). (Windows 10)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on August 31, 2021, 02:25:19 PM
Quote from: jakeroot on August 31, 2021, 12:28:14 PM
No access to Safari but does not work on any browser that I have installed (Edge, Chrome, Firefox). (Windows 10)

I just tried it in IE as well (because I figure there's a 50% chance not a single person on here even uses that browser anymore), and it doesn't render on IE either.  At least has a broken image icon, though, so there's at least some clue something's missing.

(https://i.imgur.com/2uFPPtD.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: johndoe on September 04, 2021, 01:45:37 PM
As Google maps seems to get more and more advertisements I'm looking for alternative sites/apps.  I'd like to be able to view live traffic on both Chrome and Android.  Personally I don't love Waze as I never turn my "location" on for mobile...so it's a pain to view live traffic.  The color scheme isn't really very intuitive either.  Sometimes it feels like certain zoom levels on Google make it less "ad-intrusive"...thoughts?
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 04, 2021, 01:55:47 PM
openstreetmap.org

Wikipedia but a map, essentially. Doesn't have satellite or street view, but it does have county lines and the ability to edit out inaccuracies.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 04, 2021, 02:07:52 PM
I use the app "OSMAnd" when I'm cycling. Helps me find the least-hilly routes here in my very hilly city. Naturally uses OSM as its base map.

Never used it for navigating by car, but it's definitely a feature. But I think, like others, it would want location. I don't know if it has traffic, but it does have a lot of other options for adjusting the map display.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 04, 2021, 02:17:14 PM
I mean, you can always pan manually to your area of interest if you don't want to turn location on.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on September 04, 2021, 03:51:30 PM
Google maps transit tab pales in comparison to Apple maps. I thought at least all US light rail and metro system lines would be shown in Google maps, but nope...
(https://imgur.com/oTf4doN.jpg?1)
(https://imgur.com/jO7DnVE.jpg?1)
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 04, 2021, 06:47:41 PM
Quote from: SkyPesos on September 04, 2021, 03:51:30 PM
Google maps transit tab pales in comparison to Apple maps. I thought at least all US light rail and metro system lines would be shown in Google maps, but nope...


There is a Transit layer that displays lines (but this only works for cities with proper GTFS feeds sent to Google).

(https://i.imgur.com/95NMcp0.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 04, 2021, 06:58:11 PM
Quote from: Bruce on September 04, 2021, 06:47:41 PM
Quote from: SkyPesos on September 04, 2021, 03:51:30 PM
Google maps transit tab pales in comparison to Apple maps. I thought at least all US light rail and metro system lines would be shown in Google maps, but nope...


There is a Transit layer that displays lines (but this only works for cities with proper GTFS feeds sent to Google).

(https://i.imgur.com/95NMcp0.png)

Apple Maps shows Amtrak for the entire US.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on September 04, 2021, 07:07:40 PM
Quote from: 1 on September 04, 2021, 06:58:11 PM
Apple Maps shows Amtrak for the entire US.
Also national railways in some European countries. Here's the rail lines shown with Apple's transit layer in a part of Europe. It gets more detailed when zoomed in further.
(https://i.imgur.com/cBvGntZ.jpg?1)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on September 04, 2021, 07:18:00 PM
Wait, why is Milano in Italian but Rome in English? My Apple Maps doesn't do that.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on September 05, 2021, 05:51:55 PM
Quote from: johndoe on September 04, 2021, 01:45:37 PM
As Google maps seems to get more and more advertisements I'm looking for alternative sites/apps.  I'd like to be able to view live traffic on both Chrome and Android.  Personally I don't love Waze as I never turn my "location" on for mobile...so it's a pain to view live traffic.  The color scheme isn't really very intuitive either.  Sometimes it feels like certain zoom levels on Google make it less "ad-intrusive"...thoughts?

There's a way to turn off businesses at least on Google My Maps, but I can't remember what it is.

I also sometimes use WeGo maps, which has the advantage of coloring freeways in an easily distinguishable color.

https://wego.here.com
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on September 06, 2021, 04:24:28 AM
Quote from: SafeSpeeder on September 05, 2021, 05:56:02 PM
I've been having trouble recently loading the traffic on the app. It used to be instant now takes up to 5 minutes. Traffic is usually far worse than indicated as well, but to be fair they do do a good job updating it every few minutes for increased accuracy. Personally Prefer Waze
Waze has been my go to as of late for routing, especially on long distance trips. Given I'm going to have Waze running regardless for incidents, police, etc., might as well just use the routing their anyways as opposed to having Google Maps in the background as well.

I'll use Google Maps generally for planning purposes in advance, but once actually going, I'll usually just put it in Waze.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on September 06, 2021, 04:54:05 PM
Interestingly, you can now turn off labels on the map, not just satellite view:

(https://i.imgur.com/6bgwLXq.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 08, 2021, 01:38:45 PM
Quote from: CtrlAltDel on September 06, 2021, 04:54:05 PM
Interestingly, you can now turn off labels on the map, not just satellite view:

I can't help but think it's a mistake based on the option being greyed out. Why it remains clickable...that I don't know.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on September 09, 2021, 01:15:38 AM
Quote from: Scott5114 on August 23, 2021, 11:48:07 PM
Quote from: webny99 on August 23, 2021, 10:39:43 PM
Yes, myself included, and for that reason among others, I support shifting discussion to a new thread if the name isn't going to be changed (and notice how I've handled the title on my last several posts here).

See, but that would be a duplicate thread, so my job then would be to merge that thread into this one...

Quote from: TheHighwayMan394 on August 23, 2021, 10:52:44 PM
I think you and vdeane both missed my point, which is if you're concerned about getting in trouble at work for this, you shouldn't be visiting this forum during work.

This. I also can't imagine an employer that is totally cool with you using company resources to browse websites for personal use, but only if they don't say "fuck" on them anywhere.

:clap:
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on September 10, 2021, 03:07:07 PM
Just another complaint about city labels on Google Maps.  Can't for the life of me get Greeley, Colorado to show up, despite the fact it's one of the larger cities in the country (pop > 100,000).  I know this happens often for significant cities with Google Maps, but it's still freakin' annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on September 10, 2021, 04:25:37 PM
Works for me on zoom level 8.

(https://i.imgur.com/6oP5y1b.png)

I've noticed that some other map programs have weird choices in city selection. Mapbox (which overlays OSM data) tends to omit Everett in favor of Marysville, for example.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 10, 2021, 05:15:16 PM
Quote from: Rothman on September 10, 2021, 03:07:07 PM
Just another complaint about city labels on Google Maps.  Can't for the life of me get Greeley, Colorado to show up, despite the fact it's one of the larger cities in the country (pop > 100,000).  I know this happens often for significant cities with Google Maps, but it's still freakin' annoying.

In addition to Bruce, it also shows up for me.

Quote from: Bruce on September 10, 2021, 04:25:37 PM
I've noticed that some other map programs have weird choices in city selection. Mapbox (which overlays OSM data) tends to omit Everett in favor of Marysville, for example.

Likely relates to the map options chosen. I can repeat what you're describing but not in every style. In some, Everett and Marysville and visually identical (same font size and weight), but in others ('Streets' for instance) it is displayed with both a larger size and weight. Doesn't explain why Everett would disappear in favor of Marysville for a few zoom levels, but the issue can be rectified from what I can tell.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on September 10, 2021, 11:51:30 PM
It came back for me after leaving the site and returning.  Makes me wonder what triggers the lack of a city label and if there is some glitch when zooming.  It's not the only location where I've found a missing label.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 11, 2021, 08:35:55 PM
There was an earlier discussion on newest Street View.

Here in Tacoma and the southern Puget Sound, there's quite a lot of new imagery from July 2021.

Example: https://goo.gl/maps/vfyGLXEPZZNpH9dU9
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on September 11, 2021, 08:44:29 PM
Something I don't get is why California gets new imagery every year, yet many roads (such as US highways in the West) still have 2007/08 imagery... I do know that Google is California-based, but with the budget they have, you'd think they could afford going back to, say, US 14 in Wyoming every now and then!
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on September 11, 2021, 08:51:28 PM
Quote from: LilianaUwU on September 11, 2021, 08:44:29 PM
Something I don't get is why California gets new imagery every year, yet many roads (such as US highways in the West) still have 2007/08 imagery... I do know that Google is California-based, but with the budget they have, you'd think they could afford going back to, say, US 14 in Wyoming every now and then!
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

In other parts of Cincinnati, the reconstructed I-75 between exits 13 and 14 got new imagery from right after when the project was finished in late 2020
(https://i.imgur.com/Z2pkKas.png?1)
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 11, 2021, 09:57:11 PM
Quote from: SkyPesos on September 11, 2021, 08:51:28 PM
Quote from: LilianaUwU on September 11, 2021, 08:44:29 PM
Something I don't get is why California gets new imagery every year, yet many roads (such as US highways in the West) still have 2007/08 imagery... I do know that Google is California-based, but with the budget they have, you'd think they could afford going back to, say, US 14 in Wyoming every now and then!
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

Do you one better–my street was built in 1976 and it still doesn't have imagery! And I'm smack dab in the middle of the third-largest city in the state, and can see the state's largest university from my roof...not like I'm out in the sticks or anything.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 12, 2021, 12:00:55 AM
Quote from: SkyPesos on September 11, 2021, 08:51:28 PM
Quote from: LilianaUwU on September 11, 2021, 08:44:29 PM
Something I don't get is why California gets new imagery every year, yet many roads (such as US highways in the West) still have 2007/08 imagery... I do know that Google is California-based, but with the budget they have, you'd think they could afford going back to, say, US 14 in Wyoming every now and then!
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

In other parts of Cincinnati, the reconstructed I-75 between exits 13 and 14 got new imagery from right after when the project was finished in late 2020
(https://i.imgur.com/Z2pkKas.png?1)

Unrelated, but the "Donatos Pizza" location on the map only just allowed me to realize that the Donatos pizza I've been seeing on Red Robin menus is actually a chain and not something invented by them.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on September 12, 2021, 09:54:41 AM
Quote from: Scott5114 on September 04, 2021, 01:55:47 PM
openstreetmap.org

Wikipedia but a map, essentially. Doesn't have satellite or street view, but it does have county lines and the ability to edit out inaccuracies.
Will it allow me to track the distance of specific roads? Because I tried to use Google's tool for that and it kept dragging me all over the place and prevented me from erasing roads I didn't want to add.


Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on September 12, 2021, 10:25:23 AM
Quote from: jakeroot on September 12, 2021, 12:00:55 AM
Quote from: SkyPesos on September 11, 2021, 08:51:28 PM
Quote from: LilianaUwU on September 11, 2021, 08:44:29 PM
Something I don't get is why California gets new imagery every year, yet many roads (such as US highways in the West) still have 2007/08 imagery... I do know that Google is California-based, but with the budget they have, you'd think they could afford going back to, say, US 14 in Wyoming every now and then!
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

In other parts of Cincinnati, the reconstructed I-75 between exits 13 and 14 got new imagery from right after when the project was finished in late 2020
(https://i.imgur.com/Z2pkKas.png?1)

Unrelated, but the "Donatos Pizza" location on the map only just allowed me to realize that the Donatos pizza I've been seeing on Red Robin menus is actually a chain and not something invented by them.

Donato's is a pizza chain which started in Columbus, OH.  For a thin crust pizza that is cut into short strips, it's not bad.
Title: Re: Google Maps SUCKS now
Post by: webny99 on September 12, 2021, 11:45:05 AM
Quote from: Scott5114 on September 11, 2021, 09:57:11 PM
Quote from: SkyPesos on September 11, 2021, 08:51:28 PM
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

Do you one better–my street was built in 1976 and it still doesn't have imagery! And I'm smack dab in the middle of the third-largest city in the state, and can see the state's largest university from my roof...not like I'm out in the sticks or anything.

If it's just one street, that's pretty odd, but if it's the entire neighborhood, maybe it could be that there's a neighborhood association or something preventing Street View?  There was an entire neighborhood in my area that didn't have Street View for the longest time before finally getting it in 2019, and it didn't have anything to do with the age of the neighborhood - plenty of newer developments and the adjacent main roads had their Street View refreshed several times over in that period.

Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on September 12, 2021, 01:14:22 PM
Quote from: webny99 on September 12, 2021, 11:45:05 AMIf it's just one street, that's pretty odd, but if it's the entire neighborhood, maybe it could be that there's a neighborhood association or something preventing Street View?  There was an entire neighborhood in my area that didn't have Street View for the longest time before finally getting it in 2019, and it didn't have anything to do with the age of the neighborhood - plenty of newer developments and the adjacent main roads had their Street View refreshed several times over in that period.

I would be more likely to believe the private street/gated community explanation if Scott's house were built after 1980, when Clean Water Act implementation created incentives for developers to offload enhanced responsibilities for drainage onto homeowners' associations.

I did take a look at Norman with the StreetView availability layer turned on (i.e., Pegman clicked rather than clicked and dragged to a location on the map).  The arterials and collectors all seem to have StreetView, but there are random examples of neighborhood roads that have no StreetView, seemingly with no rhyme or reason (e.g., one cul-de-sac in a neighborhood has StreetView while the next doesn't).
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on September 12, 2021, 01:45:54 PM
Quote from: webny99 on September 12, 2021, 11:45:05 AM
Quote from: Scott5114 on September 11, 2021, 09:57:11 PM
Quote from: SkyPesos on September 11, 2021, 08:51:28 PM
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

Do you one better–my street was built in 1976 and it still doesn't have imagery! And I'm smack dab in the middle of the third-largest city in the state, and can see the state's largest university from my roof...not like I'm out in the sticks or anything.

If it's just one street, that's pretty odd, but if it's the entire neighborhood, maybe it could be that there's a neighborhood association or something preventing Street View?  There was an entire neighborhood in my area that didn't have Street View for the longest time before finally getting it in 2019, and it didn't have anything to do with the age of the neighborhood - plenty of newer developments and the adjacent main roads had their Street View refreshed several times over in that period.

Nope, no HOA, no gated community (I don't have the patience for such things, so I rejected any houses that had those when I was looking for a house to buy). I live on a corner lot, and the collector street running beside my house just got GSV coverage this past February, so my house is at least visible on GSV. But the street out front, that is named in my address and has a better view of the front elevation of my house, has no coverage. As J.N. mentions, it's apparently random which of the various culs-de-sac in my neighborhood have coverage; there's even one where the GSV car apparently stopped coverage halfway through without reaching the cul-de-sac for some reason.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on September 12, 2021, 03:45:39 PM
Quote from: SkyPesos on September 11, 2021, 08:51:28 PM
There's a set of exit ramps on I-71 near Kings Island (pretty much everything except the NB exit and SB entrance) opened in 2018 that still doesn't have street view imagery.

In other parts of Cincinnati, the reconstructed I-75 between exits 13 and 14 got new imagery from right after when the project was finished in late 2020
(https://i.imgur.com/Z2pkKas.png?1)
Just a bit north of this interchange, an August 2021 imagery (https://www.google.com/maps/@39.3586504,-84.2792469,3a,55.4y,268.11h,88.6t/data=!3m6!1e1!3m4!1sddqtlxh0zuubhCuufZHAlA!2e0!7i16384!8i8192) of the reconfigured OH 741 and Kings Mill Rd intersection. Nice seeing this one on GSV, as I haven't seen this project in person despite living so close to there (before college started of course).

Unrelated note, sort of disappointed that a doghouse was chosen over an FYA, but that's Ohio's roads for ya  :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: Great Lakes Roads on September 12, 2021, 04:53:23 PM
I also found some recent streetview from July 2021 in Grand Rapids.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on September 12, 2021, 06:19:29 PM
Spain has plenty of 2021 imagery now as well.

In addition it appears the largest gap in Europe (otherwise known as Germany) is closing soon...
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 12, 2021, 06:32:27 PM
Quote from: CNGL-Leudimin on September 12, 2021, 06:19:29 PM
In addition it appears the largest gap in Europe (otherwise known as Germany) is closing soon...

What makes you say that? Every time I hear that Germany is getting new imagery, it never comes to fruition.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on September 13, 2021, 06:53:26 AM
The appearance of (old) official imagery along some Autobahnen, e.g. A3 between the Ruhr area and Frankfurt. I cannot recall it being available earlier.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 14, 2021, 04:49:11 PM
Quote from: CNGL-Leudimin on September 13, 2021, 06:53:26 AM
The appearance of (old) official imagery along some Autobahnen, e.g. A3 between the Ruhr area and Frankfurt. I cannot recall it being available earlier.

Ehhh, that strikes me as a bit too anecdotal. Plus, nothing legal in Germany has changed that would benefit Google in terms of taking new imagery. Germans didn't like it then and it seems to me that they don't like it now, and I'm sure they would challenge the return of imagery (or the addition of new imagery, new or old) almost immediately.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 14, 2021, 09:26:10 PM
They are driving (https://www.google.com/streetview/explore/#sv-headed) in Germany, though I could have sworn I've seen that in past years and it's never resulted in imagery appearing.  That said, it does somehow feel like finding autobahn sections with coverage is easier than it used to be.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on September 14, 2021, 10:25:48 PM
Quote from: vdeane on September 14, 2021, 09:26:10 PM
They are driving (https://www.google.com/streetview/explore/#sv-headed) in Germany, though I could have sworn I've seen that in past years and it's never resulted in imagery appearing.  That said, it does somehow feel like finding autobahn sections with coverage is easier than it used to be.

Indeed, I have seen Germany appear in that list, but it never shows up. I think it may be them gathering data (in the same manner as Street View is used elsewhere), just without the public side of the imagery.

edit: confusing grammar.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on September 15, 2021, 07:02:03 AM
Before someone says the new Autobahn coverage has disappeared, so has done the newer sections of A-21 in Spain. The imagery is actually still there (just checked A-21), and the blue lines are expected to return in a few days. The same happened with Slovenia when that country was released years ago, so it's nothing new.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on September 18, 2021, 12:48:39 AM
This has been really annoying me on GSV recently; the restaurant and attractions popups. I just want to look at a road, and even clicking on a part a good distance away from the label, it still pops up the restaurant, which I have no interest in. Clicking in the green circle still triggers the restaurant popup.
(https://i.imgur.com/LNn7Ksl.png?1)
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on September 18, 2021, 01:24:02 AM
QC-132 between QC-287 and Route de Kamouraska still has no Street View as of the latest round of imagery (last month!!) This baffles me.

(https://i.imgur.com/DprUBcO.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on September 26, 2021, 08:35:15 PM
I just updated to iOS 15 and wow the new Apple Maps is amazing as far as detail from non satellite imagery goes in the city. Only is it's limited to LA and NYC but I'm sure it'll be expand. It only Apple would out do Google on imagery updates and implement street view. They have the money.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on October 03, 2021, 09:31:31 PM
It's annoying that central Oklahoma City aerial imagery has not been updated since 2017.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on October 03, 2021, 09:35:01 PM
Now let's see which mapping program will have the new I-49 Bella Vista Bypass shown first. So far, Google, Apple and Bing are all losing.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on October 03, 2021, 10:42:47 PM
So, Google listened to my request of covering something that wasn't covered... but they covered the wrong branch of the intersection. Ugh.

(https://i.imgur.com/iUX1WiE.png)

(https://i.imgur.com/K1uVvpk.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on October 03, 2021, 11:17:12 PM
Quote from: Plutonic Panda on October 03, 2021, 09:31:31 PM
It's annoying that central Oklahoma City aerial imagery has not been updated since 2017.

I've mentioned that elsewhere on the forum in the past. It's especially awful since there has been so much development in that area, much of which is geared toward out-of-towners, like the convention center.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on October 03, 2021, 11:34:02 PM
Quote from: Scott5114 on October 03, 2021, 11:17:12 PM
Quote from: Plutonic Panda on October 03, 2021, 09:31:31 PM
It's annoying that central Oklahoma City aerial imagery has not been updated since 2017.

I've mentioned that elsewhere on the forum in the past. It's especially awful since there has been so much development in that area, much of which is geared toward out-of-towners, like the convention center.
And what's weird is that before the latest update Google was actually pretty good about regularly updating the aerial imagery in OKC. I had noticed they were updating it at least once a year for a cool minute while other cities would go 2 to 3 years without it being updated. Of course this was all before 2017 and it hasn't been updated since. Of course you can go to the county assessor from Oklahoma City and see the imagery there.

I'm not an accountant so it would need to be simplify but I would really like to know the cost of keeping imagery updated around the world as I imagine it's not cheap. But Google conform partnerships with agencies like Oklahoma county where they have imagery as recent as last month available.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 10, 2021, 07:55:53 PM
Looks like Google is no longer showing county-level data on their COVID-19 layer.  This significantly reduces the functionality of that layer, even from a purely COVID perspective.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on October 11, 2021, 11:21:32 AM
Quote from: vdeane on October 10, 2021, 07:55:53 PM
Looks like Google is no longer showing county-level data on their COVID-19 layer.  This significantly reduces the functionality of that layer, even from a purely COVID perspective.

Best thing I like about that layer is that it shows county lines.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on October 11, 2021, 07:00:43 PM
I wish I could be as maniacally devoted to anything as much as Google is to their incomprehensible insistence in not showing counties on their map.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on October 11, 2021, 07:44:41 PM
Quote from: vdeane on October 10, 2021, 07:55:53 PM
Looks like Google is no longer showing county-level data on their COVID-19 layer.  This significantly reduces the functionality of that layer, even from a purely COVID perspective.

Maybe it's a glitch. I can still see them.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on October 11, 2021, 09:08:26 PM
It just reappeared for me.  Let's hope it stays that way.  Not having a way to view county lines without searching on Google is an annoyance, but my larger complaint was over not being able to view county-level COVID case data.  That "X cases per 100k people" number is only available on Google and the NY Times... and I don't have a subscription to the NY Times, so accessing it there is really annoying (especially as the map requires JavaScript enabled, and I have Chrome set to block JavaScript on the NY Times, and there's no "enable just this one time" button).
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on October 11, 2021, 09:13:54 PM
Private browsing in Safari works for me. (No need to disable anything.)
Title: Re: Google Maps just ####### SUCKS now
Post by: Rover_0 on October 18, 2021, 02:54:03 PM
I don't know how many years later, and I still can't quite forgive Google Maps for removing the "snap to road"  feature when drawing a line along a road. Is there an option like this in Google Earth or another map program?

Also, is there any way you can put a label/road name onto a line on Google Maps or Google Earth?

(Sorry for the questions–I thought they were close enough to warrant asking here.)

Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on October 19, 2021, 06:10:03 PM
TFW your neighborhood gets privated and you can't see your house anymore on Google Street View :(
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on October 23, 2021, 05:51:06 PM
Quote from: LilianaUwU on October 03, 2021, 10:42:47 PM
So, Google listened to my request of covering something that wasn't covered... but they covered the wrong branch of the intersection. Ugh.

(https://i.imgur.com/iUX1WiE.png)

(https://i.imgur.com/K1uVvpk.jpg)

They finally did it.

(https://i.imgur.com/Lj0CAPT.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jeffandnicole on November 13, 2021, 12:13:33 PM
I do believe Google Maps is getting worse. I don't know if it's taking bad information from the public, or it's just not generating proper data. Today when I was looking at a route from Delaware to New Jersey and selected the no tolls option, it wanted me to skip all the bridges from the Delaware Memorial Bridge up to the Trenton Makes Bridge. There are no tolls crossing into New Jersey at any of these bridges, so it should have directed me to take the most direct route via the Delaware Memorial.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on November 13, 2021, 01:32:47 PM
The My Maps app dissolution and transfer to the web was sloppily done.  Now, if you have a shared map open, it is almost impossible to get rid of it if accessing maps from Google Maps on a desktop.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on November 16, 2021, 10:57:00 AM
Apple maps updated with two new roads that opened last week (US 35 in WV and Opportunity Corridor in Cleveland), while Google maps hasn't as of now. So much for the most used map when it can't even be the first to update with new roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.
Title: Re: Google Maps SUCKS now
Post by: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.

I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on December 07, 2021, 06:35:17 PM
Quote from: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.

I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.
I know, what the heck happened to "scanning" distance? :angry:
Guess we're back to the old days where only steps using the arrows were allowed :popcorn:
Title: Re: Google Maps just fucking SUCKS now
Post by: stevashe on December 08, 2021, 08:32:00 PM
Quote from: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.
I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.

I just came to this thread specifically to see if anyone else had this issue recently, so I am certain that this is a new problem. Yes, it has always (or at least for a long time) defaulted to the nearest point if you aim too far ahead, but as of about a week ago, the distance you're able to move was drastically reduced. So, either a recent update broke something, or they purposely reduced the amount you can move in streetview with each click. Either way, I hope this is fixed soon.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on December 08, 2021, 08:46:59 PM
Quote from: stevashe on December 08, 2021, 08:32:00 PM
Quote from: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.
I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.

I just came to this thread specifically to see if anyone else had this issue recently, so I am certain that this is a new problem. Yes, it has always (or at least for a long time) defaulted to the nearest point if you aim too far ahead, but as of about a week ago, the distance you're able to move was drastically reduced. So, either a recent update broke something, or they purposely reduced the amount you can move in streetview with each click. Either way, I hope this is fixed soon.

I can confirm that this happened to me too. It gets super annoying when I'm trying to find something and get forced to go at a snail's pace.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 09, 2021, 11:55:38 AM
Quote from: LilianaUwU on December 08, 2021, 08:46:59 PM
Quote from: stevashe on December 08, 2021, 08:32:00 PM
Quote from: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.
I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.

I just came to this thread specifically to see if anyone else had this issue recently, so I am certain that this is a new problem. Yes, it has always (or at least for a long time) defaulted to the nearest point if you aim too far ahead, but as of about a week ago, the distance you're able to move was drastically reduced. So, either a recent update broke something, or they purposely reduced the amount you can move in streetview with each click. Either way, I hope this is fixed soon.

I can confirm that this happened to me too. It gets super annoying when I'm trying to find something and get forced to go at a snail's pace.

So far, mine will move to wherever the circle on the screen is floating, but if I point too far away from the current position, an "X" appears on the ground, usually a few car lengths away, and that's where I end up instead. That said, I do seem to remember being able to move like a half-mile at a time if I wanted. But frankly, I did that more often accidentally than intentionally, so it seems possible they disabled that feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on December 10, 2021, 03:33:47 PM
Yep, things have been slowed down. I used to routinely reach 400 km/h (~250 mph) when cruising on Street View, now I'll be lucky if I reach 200 km/h (~125 mph). Thus, my trips will require at least double the time to complete, so good bye doing 300 miles at once like I did in the past. However I've discovered this only happens with the newest images.
Title: Re: Google Maps just fucking SUCKS now
Post by: GCrites on December 10, 2021, 08:36:52 PM
Quote from: LilianaUwU on December 08, 2021, 08:46:59 PM
Quote from: stevashe on December 08, 2021, 08:32:00 PM
Quote from: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.
I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.

I just came to this thread specifically to see if anyone else had this issue recently, so I am certain that this is a new problem. Yes, it has always (or at least for a long time) defaulted to the nearest point if you aim too far ahead, but as of about a week ago, the distance you're able to move was drastically reduced. So, either a recent update broke something, or they purposely reduced the amount you can move in streetview with each click. Either way, I hope this is fixed soon.

I can confirm that this happened to me too. It gets super annoying when I'm trying to find something and get forced to go at a snail's pace.

What's funny is I determined it was doing it while I was clicking through a construction zone. So I was like.

"Oh, it's slowed down due to the construction.

When I get out it will speed back up.

Wait, why would it do that?

Does it take more pictures in the construction because the car is driving slower?

We'll see once we get out of the construction.

Hmm nope, still slow.

Maybe it's my computer?"
Title: Re: Google Maps just fucking SUCKS now
Post by: STLmapboy on December 12, 2021, 01:18:58 AM
Quote from: LilianaUwU on December 08, 2021, 08:46:59 PM
Quote from: stevashe on December 08, 2021, 08:32:00 PM
Quote from: webny99 on December 07, 2021, 07:55:42 AM
Quote from: bm7 on December 07, 2021, 12:34:51 AM
Quote from: Caps81943 on December 07, 2021, 12:27:16 AM
Anyone having trouble traveling down roads? If I click farther than, maybe, 5 clicks ahead, it defaults to just the one click in front of me.
It's always been like that as far as I can remember. You just have to make sure not to click too far down the road. And sometimes the angle of the road line to move forwards is different than it is in the actual image, so you might have to adjust where you're clicking between different captures.
I've always had issues with trying to click too far down the road, but it's gotten worse recently. Sometimes clicks that used to move a normal distance will now only move a tiny distance.

I just came to this thread specifically to see if anyone else had this issue recently, so I am certain that this is a new problem. Yes, it has always (or at least for a long time) defaulted to the nearest point if you aim too far ahead, but as of about a week ago, the distance you're able to move was drastically reduced. So, either a recent update broke something, or they purposely reduced the amount you can move in streetview with each click. Either way, I hope this is fixed soon.

I can confirm that this happened to me too. It gets super annoying when I'm trying to find something and get forced to go at a snail's pace.

Same here. Seems to happen in urban areas more and in newer imagery.

Google Maps keeps finding new and exciting ways to fuck up.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on December 12, 2021, 06:02:00 AM
I remember a few years ago, I was halfway through the Giro d'Italia route when suddenly I couldn't advance as far as I could, instead being forced to go photo by photo. They fixed that a while afterwards.
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on December 14, 2021, 02:08:00 PM
When trying to go on US-64 west, google maps puts the street view on the eastbound traffic.

https://www.google.com/maps/@35.8340957,-78.3131934,3a,47y,317.27h,83.22t/data=!3m7!1e1!3m5!1skv6h64oBldqRQApUmPUeGA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3Dkv6h64oBldqRQApUmPUeGA%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D24.089464%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192

wtf
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on December 14, 2021, 03:07:59 PM
Quote from: tolbs17 on December 14, 2021, 02:08:00 PM
When trying to go on US-64 west, google maps puts the street view on the eastbound traffic.

https://www.google.com/maps/@35.8340957,-78.3131934,3a,47y,317.27h,83.22t/data=!3m7!1e1!3m5!1skv6h64oBldqRQApUmPUeGA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3Dkv6h64oBldqRQApUmPUeGA%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D24.089464%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192

wtf
That's a very annoying bug I've encountered many times on GSV (in Houston especially). I'll be surfing along the Gulf freeway, then all of a sudden, it throws me to the HOV lane, the feeder, or even the main lanes in the other direction, claiming it's "I-45" when in fact it is not. It seems to be most prevalent when you have separated travel lanes fairly close to each other, as in your example.

Another extremely annoying thing about GSV is that there's no way to "lock" the time the GSV photos were taken on the "time machine" in the top left corner. As an example, let's say I want to look at the new TX-288 toll lanes on GSV. I'm looking at some April 2021 imagery, but then I click the next step and it reverts to 2016 imagery or something like that. Or maybe I want to see how a road looked in 2012, and it keeps reverting back to 2019 imagery. Worst of all, I've discovered the default is sometimes not the newest imagery when you're clicking around (but maybe that's a separate complaint). I wish that you could lock your imagery to "April 2021" or whatever to avoid this.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on December 14, 2021, 03:41:38 PM
Quote from: CoreySamson on December 14, 2021, 03:07:59 PM
Quote from: tolbs17 on December 14, 2021, 02:08:00 PM
When trying to go on US-64 west, google maps puts the street view on the eastbound traffic.

https://www.google.com/maps/@35.8340957,-78.3131934,3a,47y,317.27h,83.22t/data=!3m7!1e1!3m5!1skv6h64oBldqRQApUmPUeGA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3Dkv6h64oBldqRQApUmPUeGA%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D24.089464%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192

wtf
That's a very annoying bug I've encountered many times on GSV (in Houston especially). I'll be surfing along the Gulf freeway, then all of a sudden, it throws me to the HOV lane, the feeder, or even the main lanes in the other direction, claiming it's "I-45" when in fact it is not. It seems to be most prevalent when you have separated travel lanes fairly close to each other, as in your example.

Another extremely annoying thing about GSV is that there's no way to "lock" the time the GSV photos were taken on the "time machine" in the top left corner. As an example, let's say I want to look at the new TX-288 toll lanes on GSV. I'm looking at some April 2021 imagery, but then I click the next step and it reverts to 2016 imagery or something like that. Or maybe I want to see how a road looked in 2012, and it keeps reverting back to 2019 imagery. Worst of all, I've discovered the default is sometimes not the newest imagery when you're clicking around (but maybe that's a separate complaint). I wish that you could lock your imagery to "April 2021" or whatever to avoid this.
Seconded!
Title: Re: Google Maps just fucking SUCKS now
Post by: GCrites on December 14, 2021, 08:55:58 PM
^Been just grinning and bearing it as I click through.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on December 14, 2021, 09:05:34 PM
I gotta say I agree with Corey, but it would be hard to lock to one specific year if coverage is lacking on one road or the other. Perhaps it could be locked to a specific year unless there's no coverage in that year?
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on December 20, 2021, 04:46:01 PM
It appears that this does not take you anywhere - https://www.google.com/maps/@30.0925732,-95.0181836,14.71z
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on December 20, 2021, 04:48:35 PM
Quote from: tolbs17 on December 20, 2021, 04:46:01 PM
It appears that this does not take you anywhere - https://www.google.com/maps/@30.0925732,-95.0181836,14.71z
The road isn't built yet. I have no idea why Google is marking it as of now. It will eventually form a loop of Houston.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on December 24, 2021, 04:41:05 AM
The roads are just a bit off around this park in Nuevo Loredo:

(https://i.imgur.com/N4omPAp.jpeg)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on December 24, 2021, 04:10:31 PM
There seems to be a pretty jarring line in the satellite imagery, as though there is something missing. I suppose that would be the explanation?
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on December 24, 2021, 07:48:37 PM
Not sure if you guys can see it, but some of the ramps are showing as white instead of orange.

https://www.google.com/maps/@35.9586787,-77.7875554,17.42z
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on December 28, 2021, 08:50:21 AM
Quote from: CoreySamson on December 20, 2021, 04:48:35 PM
Quote from: tolbs17 on December 20, 2021, 04:46:01 PM
It appears that this does not take you anywhere - https://www.google.com/maps/@30.0925732,-95.0181836,14.71z
The road isn't built yet. I have no idea why Google is marking it as of now. It will eventually form a loop of Houston.

You see this in China all the time. :D
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 28, 2021, 12:43:09 PM
One thing that's annoying (though probably not really new) is that, while there is a way to filter search results by when something will be open, there's no way to filter out places without confirmed holiday hours when doing so.  It's really annoying when you're trying to find places that will be open around a holiday to be pulling up nothing by "holiday hours might differ".  Especially when the search results are hardly comprehensive to begin with (a search for "pizza" for example, routinely leaves off more than half the pizza places in the area around here).  May as well just hunt and peck.
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on January 01, 2022, 02:02:33 PM
I already reported to Google about the inaccurate drawing of the realigned US-52, but still nothing has happened.

https://www.google.com/maps/@36.2021828,-80.2999564,1517m/data=!3m1!1e3
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 02, 2022, 02:42:35 PM
Quote from: tolbs17 on January 01, 2022, 02:02:33 PM
I already reported to Google about the inaccurate drawing of the realigned US-52, but still nothing has happened.

https://www.google.com/maps/@36.2021828,-80.2999564,1517m/data=!3m1!1e3

I wouldn't get too hung up on alignments when there is active construction. It's pretty often inaccurate simply because the alignments can/do shift with some frequency.
Title: Re: Google Maps just fucking SUCKS now
Post by: Molandfreak on January 02, 2022, 08:16:17 PM
Quote from: jakeroot on January 02, 2022, 02:42:35 PM
Quote from: tolbs17 on January 01, 2022, 02:02:33 PM
I already reported to Google about the inaccurate drawing of the realigned US-52, but still nothing has happened.

https://www.google.com/maps/@36.2021828,-80.2999564,1517m/data=!3m1!1e3

I wouldn't get too hung up on alignments when there is active construction. It's pretty often inaccurate simply because the alignments can/do shift with some frequency.
Yeah, unfortunately, this is the sort of thing that will resolve itself, but it could take weeks. When US 14 was moved to an expressway east of Owatonna, MN in the fall, both the new and old alignments were shown with big yellow lines for a couple of weeks. It'll be fixed eventually.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on January 07, 2022, 02:19:47 PM
The reduced speed thing is being fixed now. Some sections are now back to normal and allowing cruise speeds of up to 400 km/h (~250 mph) again, others still not.
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on January 13, 2022, 09:12:40 PM
An amazing glitch.

https://www.google.com/maps/@39.6688631,-75.6815905,3a,75y,210.18h,86.17t/data=!3m7!1e1!3m5!1sQDry1HFPAscfN25-7dTxfQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DQDry1HFPAscfN25-7dTxfQ%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D196.0428%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on January 13, 2022, 09:33:14 PM
Quote from: tolbs17 on January 13, 2022, 09:12:40 PM
An amazing glitch.

https://www.google.com/maps/@39.6688631,-75.6815905,3a,75y,210.18h,86.17t/data=!3m7!1e1!3m5!1sQDry1HFPAscfN25-7dTxfQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DQDry1HFPAscfN25-7dTxfQ%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D196.0428%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192

Seems like the camera fell off. I've seen this happen in a few places.
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on January 13, 2022, 09:41:45 PM
Quote from: LilianaUwU on January 13, 2022, 09:33:14 PM
Quote from: tolbs17 on January 13, 2022, 09:12:40 PM
An amazing glitch.

https://www.google.com/maps/@39.6688631,-75.6815905,3a,75y,210.18h,86.17t/data=!3m7!1e1!3m5!1sQDry1HFPAscfN25-7dTxfQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DQDry1HFPAscfN25-7dTxfQ%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D196.0428%26pitch%3D0%26thumbfov%3D100!7i16384!8i8192

Seems like the camera fell off. I've seen this happen in a few places.
Yeah it seems like that was accidental.
Title: Re: Google Maps just fucking SUCKS now
Post by: Caps81943 on January 16, 2022, 11:11:48 AM
A weird direction quirk I found that could actually be somewhat consequential:

At least for me, no matter what, getting directions from Dulles Airport takes you out the weird back roads of the airport rather than straight out VA-267 like you should go. Examples:
https://www.google.com/maps/dir/38.9531239,-77.4476525/Natural+History+Museum,+Constitution+Avenue+Northwest,+Washington,+DC/@38.9475717,-77.4417235,13.6z/data=!3m1!5s0x89b7b79bb840648d:0xff95595edb25b99b!4m13!4m12!1m0!1m5!1m1!1s0x89b7b798ecb5b2c7:0xc7edf0c4a86f75af!2m2!1d-77.0260654!2d38.8912662!2m3!6e0!7e2!8j1642331400!3e0

https://www.google.com/maps/dir/38.9531239,-77.4476525/Leesburg,+VA/@39.0388031,-77.5765612,12z/data=!3m2!4b1!5s0x89b7b79bb840648d:0xff95595edb25b99b!4m13!4m12!1m0!1m5!1m1!1s0x89b617dc7ff52a9b:0xc3ca6f9e657976e8!2m2!1d-77.5704422!2d39.1241676!2m3!6e0!7e2!8j1642331400!3e0

https://www.google.com/maps/dir/38.9531239,-77.4476525/Manassas,+VA/@38.9510439,-77.4532216,14.44z/data=!4m13!4m12!1m0!1m5!1m1!1s0x89b65b80d465d68b:0x83529b5eb6fbe752!2m2!1d-77.4752667!2d38.7509488!2m3!6e0!7e2!8j1642331400!3e0

You have to manually reroute it on the freeway in order to use 267. All of these odd directions add 3-4 minutes and a mile to the trip...why is that the default?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on January 16, 2022, 11:19:56 AM
I blame Google's botch of preferring "fuel efficient" routes.  It's been a disaster.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on January 24, 2022, 12:33:22 PM
Couple updates I've recently noticed that arguably improve Google Maps:

(1) South Korea now has vector mapping, previously it was a low resolution alternative that looked awful. Street View imagery is still pretty sparse outside the capitol.

(2) Highly-detailed street maps, first launched in SF and NYC, have now reached other markets. Locally, Seattle now has the new detailed street maps, although none of the neighboring cities do just yet (and probably won't for a while).
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on January 24, 2022, 12:55:42 PM
Quote from: jakeroot on January 24, 2022, 12:33:22 PM
Couple updates I've recently noticed that arguably improve Google Maps:

(1) South Korea now has vector mapping, previously it was a low resolution alternative that looked awful. Street View imagery is still pretty sparse outside the capitol.

(2) Highly-detailed street maps, first launched in SF and NYC, have now reached other markets. Locally, Seattle now has the new detailed street maps, although none of the neighboring cities do just yet (and probably won't for a while).
The detail of the NYC streets is pretty cool.
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on January 24, 2022, 12:59:05 PM
I've noticed the detailed streets too. I think it's a cool feature. I believe it's only for larger cities though, as I checked other smaller cities, but didn't see the feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: thspfc on January 24, 2022, 01:02:38 PM
Quote from: BlueOutback7 on January 24, 2022, 12:59:05 PM
I've noticed the detailed streets too. I think it's a cool feature. I believe it's only for larger cities though, as I checked other smaller cities, but didn't see the feature.
Neither Chicago nor LA have them yet. Long ways to go.
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on January 24, 2022, 02:54:25 PM
Quote from: thspfc on January 24, 2022, 01:02:38 PM
Quote from: BlueOutback7 on January 24, 2022, 12:59:05 PM
I've noticed the detailed streets too. I think it's a cool feature. I believe it's only for larger cities though, as I checked other smaller cities, but didn't see the feature.
Neither Chicago nor LA have them yet. Long ways to go.

Boston's got it. Not Philly or DC, though.

EDIT: Also Dallas.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on January 25, 2022, 08:18:47 AM
And not only in the USA. Madrid has them too.
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on January 25, 2022, 08:20:36 AM
Atlanta is still missing out. They don't have it yet either.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on February 12, 2022, 09:32:16 PM
Quote from: CNGL-Leudimin on January 07, 2022, 02:19:47 PM
The reduced speed thing is being fixed now. Some sections are now back to normal and allowing cruise speeds of up to 400 km/h (~250 mph) again, others still not.
I'm still seeing this glitch everywhere on GSV (except for a random surface street in College Station, weird). It happens for imagery of any age. Anyone else still seeing this (or is my computer just really slow)?

I'm really hoping it's not a permanent QoL change so people don't overshoot their clicks. Someone (who doesn't generally care for GSV or roads at all) was showing me something on GSV the other day and she didn't like how slow it is compared to how it used to be, so apparently the problem is noticeable enough for average people to see.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 12, 2022, 11:13:58 PM
I've been getting usual speeds. Could be you have a cached copy on your computer–does Ctrl+Shift+R or Ctrl+F5 fix it?
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on February 18, 2022, 08:42:52 PM
I was just printing directions from Google Maps which for some reason was telling us to "Get on FL-589 Toll S from Elgin Blvd and Barclay Ave."

YOU CAN NOT GET ONTO FL-589-TOLL FROM ELGIN BOULEVARD!!!!

https://youtu.be/k1g8WCA7mJk

And now my bad imitation of Jim Morrison is done.


Title: Re: Google Maps just fucking SUCKS now
Post by: Max Rockatansky on February 18, 2022, 09:03:59 PM
^^^

Wait, you still print directions?  Wasn't that more of a Map Quest kind of thing?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 18, 2022, 09:39:22 PM
For whatever reason, Google is refusing to route on a portion of I-95 NB in Maryland (between MD 216 and MD 32).  Meanwhile, no closure is being shown in the traffic layer.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on February 18, 2022, 11:05:56 PM
Quote from: Max Rockatansky on February 18, 2022, 09:03:59 PM
^^^

Wait, you still print directions?  Wasn't that more of a Map Quest kind of thing?
No, Google Maps can be printed too.

Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 18, 2022, 11:16:34 PM
Quote from: D-Dey65 on February 18, 2022, 11:05:56 PM
Quote from: Max Rockatansky on February 18, 2022, 09:03:59 PM
^^^

Wait, you still print directions?  Wasn't that more of a Map Quest kind of thing?
No, Google Maps can be printed too.
When Mobile Google Maps can handle edit points, then I will give this mockery heed.  But for now, Google Maps sucks on that regard, so printing has its advantages still, if you want to follow a specific route.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 18, 2022, 11:25:36 PM
Quote from: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?
It's a tad more complicated than that on a countrywide county clinching trip. :D
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 18, 2022, 11:30:51 PM
Quote from: Rothman on February 18, 2022, 11:25:36 PM
Quote from: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?
It's a tad more complicated than that on a countrywide county clinching trip. :D

only if you're a coward
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on February 19, 2022, 12:33:03 AM
Quote from: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?

This is exactly how I handle any sort of trip I take on my own, whether it's a clinchdrive or a legitimate road trip. If my scribbled directions run over the entire front and back of the post-it note, it expands onto a piece of lined paper.
Title: Re: Google Maps just fucking SUCKS now
Post by: webny99 on February 19, 2022, 01:23:14 PM
Quote from: vdeane on February 18, 2022, 09:39:22 PM
For whatever reason, Google is refusing to route on a portion of I-95 NB in Maryland (between MD 216 and MD 32).  Meanwhile, no closure is being shown in the traffic layer.

Hmm, I'm noticing this as well. Strangely, it will allow you to route on I-95 between MD 216 and the rest area, but not between the rest area and MD 32 under any circumstance. It's almost like it doesn't even know there's a road there; using anywhere on that stretch as your destination defaults to I-95 SB.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on February 19, 2022, 09:33:47 PM
Quote from: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?

I sketch a map of the route on a piece of paper with the routes labeled.  I could get away without that, but it makes it easier to remember what I'm supposed to be doing so I don't usually have to look at the directions while I'm driving.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 20, 2022, 11:35:41 AM
Quote from: kkt on February 19, 2022, 09:33:47 PM
Quote from: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?

I sketch a map of the route on a piece of paper with the routes labeled.  I could get away without that, but it makes it easier to remember what I'm supposed to be doing so I don't usually have to look at the directions while I'm driving.

That's what I do too.
Title: Re: Google Maps just fucking SUCKS now
Post by: HighwayStar on February 20, 2022, 06:55:08 PM
Quote from: Scott5114 on February 18, 2022, 11:23:30 PM
You mean you all don't just scribble down on a post-it note "9 W/62 N/44 E/37 W/81 S/152 W" or whatever?

I do that, if I don't just memorize it outright. And actually you can do that with an atlas rather than Google maps to achieve road warrior gold status.  :coffee:
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 20, 2022, 08:28:51 PM
An atlas? Only if you're feeling lazy. Guess I have road warrior platinum status then, which requires obtaining maps through the mail (PDFs or shapefiles will do in a pinch) from the actual DOT.
Title: Re: Google Maps just SUCKS now
Post by: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. I was reminded why last May, when my phone died on the way home from a day trip to the Catskills. We were near Middleburgh, and I had to use on my atlas to find my way back to the Thruway. I ended up following NY 145 to NY 10, but found out after the fact that NY 30>NY 30A>NY 162 would have saved close to ten minutes. It wasn't a big deal, but it was getting late at night and I certainly would have taken the shorter/faster route (and likely less winding/hilly than NY 10 too, plus avoiding Canajoharie) if I had been able to use Google Maps.
Title: Re: Google Maps just SUCKS now
Post by: HighwayStar on February 20, 2022, 10:29:24 PM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. I was reminded why last May, when my phone died on the way home from a day trip to the Catskills. We were near Middleburgh, and I had to use on my atlas to find my way back to the Thruway. I ended up following NY 145 to NY 10, but found out after the fact that NY 30>NY 30A>NY 162 would have saved close to ten minutes. It wasn't a big deal, but it was getting late at night and I certainly would have taken the shorter/faster route (and likely less winding/hilly than NY 10 too, plus avoiding Canajoharie) if I had been able to use Google Maps.

Eh, I find that Google only finds the faster way sometimes, and it is prone to optimistic assumptions. And sometimes it does stupid things that no one would ever actually do (such as advising me to go through an airport as a shortcut, never mind that it was $5 to go through it).
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on February 21, 2022, 02:16:29 AM
Quote from: eejit on February 20, 2022, 10:29:24 PM
Eh, I find that Google only finds the faster way sometimes, and it is prone to optimistic assumptions. And sometimes it does stupid things that no one would ever actually do (such as advising me to go through an airport as a shortcut, never mind that it was $5 to go through it).
If you're talking about DFW, lots of people do that.
Title: Re: Google Maps just fucking SUCKS now
Post by: HighwayStar on February 21, 2022, 02:19:16 AM
Quote from: NE2 on February 21, 2022, 02:16:29 AM
Quote from: eejit on February 20, 2022, 10:29:24 PM
Eh, I find that Google only finds the faster way sometimes, and it is prone to optimistic assumptions. And sometimes it does stupid things that no one would ever actually do (such as advising me to go through an airport as a shortcut, never mind that it was $5 to go through it).
If you're talking about DFW, lots of people do that.

To save 1 minute? I don't think so. Maybe at rush hour or if there was an accident, but this was not even going to save an appreciable amount of time. No one would do that.
Title: Re: Google Maps just fucking SUCKS now
Post by: sprjus4 on February 21, 2022, 02:21:31 AM
^ Apparently enough people they increased the toll to $6 for quickly passing traffic.

https://www.dallasnews.com/business/airlines/2019/07/30/dfw-airport-upping-fee-to-6-for-pass-through-drivers-using-it-as-a-shortcut/

QuoteDFW International Airport officials plan to raise the fees for drivers who cut through the airport to save time.

The rate for pass-through commuters spending less than 8 minutes on airport property would increase to $6 starting Oct. 1, up from $4.

"This is to discourage drivers that cut through the airport to save time," DFW Airport CFO Chris Poisatte said.

Poisatte said airport roads, built and maintained with airport revenues and fees from airlines, are not intended to be a toll road for frustrated commuters.

DFW International Airport's board will vote on the proposal Thursday.

Last year, about 2,500 commuters a day cut through the airport, presumably to save time during busy rush-hour congestion between communities north and south of the property.

By the airport's estimations, they make about $3.6 million a year on pass-through commuters. Raising the fee by 50% would raise another $1.8 million if the higher rates don't scare away drivers.

"The rates are increasing so DFW can continue to improve upon parking and roadway infrastructures," airport spokeswoman Cynthia Vega said.

Any vehicle that enters the airport pays a fee, whether it's locals picking up passengers, ride-share drivers or those who park there.

Drivers that stay from 0 to 8 minutes pay $4, while those on the property 8 to 30 minutes only pay $2. For those remaining on-site between 30 minutes and 2 hours, it's $3.

Those fees come from airport estimates on how long it takes to pick up and drop off passengers. Drivers on property less than 8 minutes, they presume, are only cutting through.

The price hike on pass-through drivers is the only parking and toll fee increase planned for the upcoming year.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 21, 2022, 08:50:43 AM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. I was reminded why last May, when my phone died on the way home from a day trip to the Catskills. We were near Middleburgh, and I had to use on my atlas to find my way back to the Thruway. I ended up following NY 145 to NY 10, but found out after the fact that NY 30>NY 30A>NY 162 would have saved close to ten minutes. It wasn't a big deal, but it was getting late at night and I certainly would have taken the shorter/faster route (and likely less winding/hilly than NY 10 too, plus avoiding Canajoharie) if I had been able to use Google Maps.
Paper maps don't take up that much space.  Put 'em in the door.

Kids these days... ;D
Title: Re: Google Maps just SUCKS now
Post by: webny99 on February 21, 2022, 09:24:58 AM
Quote from: HighwayStar on February 21, 2022, 02:19:16 AM
Quote from: NE2 on February 21, 2022, 02:16:29 AM
Quote from: eejit on February 20, 2022, 10:29:24 PM
Eh, I find that Google only finds the faster way sometimes, and it is prone to optimistic assumptions. And sometimes it does stupid things that no one would ever actually do (such as advising me to go through an airport as a shortcut, never mind that it was $5 to go through it).
If you're talking about DFW, lots of people do that.

To save 1 minute? I don't think so. Maybe at rush hour or if there was an accident, but this was not even going to save an appreciable amount of time. No one would do that.

$6 is still nothing compared to some of the NY bridge tolls or the rates on Ontario's 407 ETR. If there's any congestion on the other routes, there's probably plenty of people who think it's worth it.

In any case that's a very unique situation. Most airports don't have exits on both ends, so they can't be used as a cut-through. I would hardly call that evidence that Google Maps "does stupid things" - if anything, it's a counterpoint to Maps "only find[ing] the fastest way sometimes".
Title: Re: Google Maps just SUCKS now
Post by: webny99 on February 21, 2022, 09:26:41 AM
Quote from: Rothman on February 21, 2022, 08:50:43 AM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. ...
Paper maps don't take up that much space.  Put 'em in the door.

Kids these days... ;D

Oh, it's not the storage space that's the issue. It's how big and clumsy they are when they're unfolded and you're actually trying to use them.  :D
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on February 21, 2022, 09:32:49 AM
Quote from: HighwayStar on February 21, 2022, 02:19:16 AM
Quote from: NE2 on February 21, 2022, 02:16:29 AM
Quote from: eejit on February 20, 2022, 10:29:24 PM
Eh, I find that Google only finds the faster way sometimes, and it is prone to optimistic assumptions. And sometimes it does stupid things that no one would ever actually do (such as advising me to go through an airport as a shortcut, never mind that it was $5 to go through it).
If you're talking about DFW, lots of people do that.

To save 1 minute? I don't think so. Maybe at rush hour or if there was an accident, but this was not even going to save an appreciable amount of time. No one would do that.


I've done it before when an accident pretty much shut down another route.  But yeah driving through is also a lot slower speed limit wise on top of the toll. 
Title: Re: Google Maps just SUCKS now
Post by: HighwayStar on February 21, 2022, 01:42:11 PM
Quote from: webny99 on February 21, 2022, 09:26:41 AM
Quote from: Rothman on February 21, 2022, 08:50:43 AM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. ...
Paper maps don't take up that much space.  Put 'em in the door.

Kids these days... ;D

Oh, it's not the storage space that's the issue. It's how big and clumsy they are when they're unfolded and you're actually trying to use them.  :D

I guess you need a bigger car then.
Though, you can use a couple panels of the map rather than the whole thing in most cases.
Title: Re: Google Maps just SUCKS now
Post by: hotdogPi on February 21, 2022, 01:50:57 PM
Quote from: HighwayStar on February 21, 2022, 01:42:11 PM
I guess you need a bigger car then.

But you want to ban all SUVs. (https://www.aaroads.com/forum/index.php?topic=28884.msg2589759#msg2589759)
Title: Re: Google Maps just SUCKS now
Post by: HighwayStar on February 21, 2022, 02:54:00 PM
Quote from: 1 on February 21, 2022, 01:50:57 PM
Quote from: HighwayStar on February 21, 2022, 01:42:11 PM
I guess you need a bigger car then.

But you want to ban all SUVs. (https://www.aaroads.com/forum/index.php?topic=28884.msg2589759#msg2589759)

Yes, because they don't even provide much interior room, just wasted weight and height without increasing interior room. My sedan is more spacious than any SUV I have ever been in.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 21, 2022, 03:33:01 PM
Quote from: webny99 on February 21, 2022, 09:26:41 AM
Quote from: Rothman on February 21, 2022, 08:50:43 AM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. ...
Paper maps don't take up that much space.  Put 'em in the door.

Kids these days... ;D

Oh, it's not the storage space that's the issue. It's how big and clumsy they are when they're unfolded and you're actually trying to use them.  :D

Kick Grandma out at the rest area. "Out of the way, Grams, I've gotta look at the map!"
Title: Re: Google Maps just fucking SUCKS now
Post by: TheHighwayMan3561 on February 21, 2022, 06:46:08 PM
Quote from: Scott5114 on February 21, 2022, 03:33:01 PM
Quote from: webny99 on February 21, 2022, 09:26:41 AM
Quote from: Rothman on February 21, 2022, 08:50:43 AM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. ...
Paper maps don't take up that much space.  Put 'em in the door.

Kids these days... ;D

Oh, it's not the storage space that's the issue. It's how big and clumsy they are when they're unfolded and you're actually trying to use them.  :D

Kick Grandma out at the rest area. "Out of the way, Grams, I've gotta look at the map!"

"Hey Fozzie, who's driving?"
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on February 21, 2022, 08:22:50 PM
Quote from: sprjus4 on February 21, 2022, 02:21:31 AM
https://www.dallasnews.com/business/airlines/2019/07/30/dfw-airport-upping-fee-to-6-for-pass-through-drivers-using-it-as-a-shortcut/

QuotePoisatte said airport roads, built and maintained with airport revenues and fees from airlines, are not intended to be a toll road for frustrated commuters.

The same is essentially true of all the NYS parkways, and yet here we are. :spin:
Title: Re: Google Maps just SUCKS now
Post by: Rothman on February 21, 2022, 11:03:07 PM
Quote from: HighwayStar on February 21, 2022, 02:54:00 PM
Quote from: 1 on February 21, 2022, 01:50:57 PM
Quote from: HighwayStar on February 21, 2022, 01:42:11 PM
I guess you need a bigger car then.

But you want to ban all SUVs. (https://www.aaroads.com/forum/index.php?topic=28884.msg2589759#msg2589759)

Yes, because they don't even provide much interior room, just wasted weight and height without increasing interior room. My sedan is more spacious than any SUV I have ever been in.

This gets us back to the comments made on HighwayStar's Ultimate Road Trip Mobile... :D
Title: Re: Google Maps just fucking SUCKS now
Post by: tolbs17 on February 22, 2022, 09:12:02 PM
Seems like they used Victory lane as an I-40 west exit ramp.

https://www.google.com/maps/@35.811419,-80.8545215,16.79z
Title: Re: Google Maps just SUCKS now
Post by: webny99 on February 22, 2022, 09:24:54 PM
Quote from: tolbs17 on February 22, 2022, 09:12:02 PM
Seems like they used Victory lane as an I-40 west exit ramp.

https://www.google.com/maps/@35.811419,-80.8545215,16.79z

Temporarily, yes... (https://www.google.com/maps/@35.8118264,-80.8488065,3a,28.6y,266.57h,85.1t/data=!3m6!1e1!3m4!1sJfvRjcVT2S9FqrMPCLkzkA!2e0!7i16384!8i8192)
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on March 11, 2022, 07:57:46 PM
IDK if good or bad, but Google Maps just made the Appalachian Trail a "park" officially
Title: Re: Google Maps just fucking SUCKS now
Post by: empirestate on March 11, 2022, 09:54:03 PM
Quote from: TheGrassGuy on March 11, 2022, 07:57:46 PM
IDK if good or bad, but Google Maps just made the Appalachian Trail a "park" officially

I'd say that's good, since it sits on official parkland.
Title: Re: Google Maps just fucking SUCKS now
Post by: skluth on March 12, 2022, 11:58:17 AM
Don't know where else to post this. If you take SUCKS part out of the title, you get this Google Street View (https://nypost.com/2022/03/10/couple-caught-having-roadside-sex-in-google-street-view-pics/) from Australia.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on March 12, 2022, 12:35:08 PM
Quote from: skluth on March 12, 2022, 11:58:17 AM
Don't know where else to post this. If you take SUCKS part out of the title, you get this Google Street View (https://nypost.com/2022/03/10/couple-caught-having-roadside-sex-in-google-street-view-pics/) from Australia.

Nothin' spices up your travels like a roadside quickie. :coffee:
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on March 12, 2022, 12:37:27 PM
Quite odd to see a new story from a "reputable" source about something that happened so long ago:

Oldest story I can find, Apr 2013: https://web.archive.org/web/20160304134338/http://hypervocal.com/culture/2013/google-street-view-australia-sexy/
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on March 12, 2022, 05:45:07 PM
Quote from: Rothman on February 21, 2022, 08:50:43 AM
Quote from: webny99 on February 20, 2022, 10:11:51 PM
I'm used to traveling with others + luggage + limited car space on road trips, in which case I could never deal with foldable maps. I generally bring at atlas along, but use Google Maps when I need to when off the main highways. I was reminded why last May, when my phone died on the way home from a day trip to the Catskills. We were near Middleburgh, and I had to use on my atlas to find my way back to the Thruway. I ended up following NY 145 to NY 10, but found out after the fact that NY 30>NY 30A>NY 162 would have saved close to ten minutes. It wasn't a big deal, but it was getting late at night and I certainly would have taken the shorter/faster route (and likely less winding/hilly than NY 10 too, plus avoiding Canajoharie) if I had been able to use Google Maps.
Paper maps don't take up that much space.  Put 'em in the door.

Kids these days... ;D

My door is full of paper maps.  Cold dead fingers....
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on March 12, 2022, 05:55:27 PM
I've also picked up free paper maps where I can and am still sad that WSDOT never bothered to continue their program (even a PDF online would be nice). The replacement from ScenicWA is fine but not exactly great.
Title: Re: Google Maps just fucking SUCKS now
Post by: skluth on March 12, 2022, 07:28:45 PM
Quote from: Bruce on March 12, 2022, 05:55:27 PM
I've also picked up free paper maps where I can and am still sad that WSDOT never bothered to continue their program (even a PDF online would be nice). The replacement from ScenicWA is fine but not exactly great.
By now every state DOT should have the data sets of their highways that could build an interactive ArcGIS map. I know a few states have done this. It shouldn't be difficult for a state to build one that could even print out custom maps; it would only cost the state two or three summer interns.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on March 13, 2022, 12:57:49 AM
Quote from: skluth on March 12, 2022, 07:28:45 PM
Quote from: Bruce on March 12, 2022, 05:55:27 PM
I've also picked up free paper maps where I can and am still sad that WSDOT never bothered to continue their program (even a PDF online would be nice). The replacement from ScenicWA is fine but not exactly great.
By now every state DOT should have the data sets of their highways that could build an interactive ArcGIS map. I know a few states have done this. It shouldn't be difficult for a state to build one that could even print out custom maps; it would only cost the state two or three summer interns.

I'm more concerned about leaving archiveable materials for future researchers. A printed map with online copies is a fixed document that can be reliably sourced to a certain point in time, while an interactive map is so much harder to archive properly.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on March 15, 2022, 01:39:59 PM
Quote from: Bruce on March 13, 2022, 12:57:49 AM
Quote from: skluth on March 12, 2022, 07:28:45 PM
Quote from: Bruce on March 12, 2022, 05:55:27 PM
I've also picked up free paper maps where I can and am still sad that WSDOT never bothered to continue their program (even a PDF online would be nice). The replacement from ScenicWA is fine but not exactly great.
By now every state DOT should have the data sets of their highways that could build an interactive ArcGIS map. I know a few states have done this. It shouldn't be difficult for a state to build one that could even print out custom maps; it would only cost the state two or three summer interns.

I'm more concerned about leaving archiveable materials for future researchers. A printed map with online copies is a fixed document that can be reliably sourced to a certain point in time, while an interactive map is so much harder to archive properly.

As I'm sure you're well aware, this has already become a headache with newspaper archives. The News Tribune (in Tacoma) stopped archiving scanned copies of their newspapers in the 1990s, opting for digital only. They only switched back to full page scans a few years ago. While the text is there and, in some ways, easier to search, being able to search through an entire scanned newspaper definitely has its advantages.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on March 18, 2022, 12:41:01 PM
Is Google Maps failing to load data for anyone else?
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on March 18, 2022, 12:47:22 PM
Quote from: vdeane on March 18, 2022, 12:41:01 PM
Is Google Maps failing to load data for anyone else?

Yes. It's been a problem all morning.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 18, 2022, 12:50:04 PM
Quote from: CtrlAltDel on March 18, 2022, 12:47:22 PM
Quote from: vdeane on March 18, 2022, 12:41:01 PM
Is Google Maps failing to load data for anyone else?

Yes. It's been a problem all morning.
Yep.  Same here.  But only through a desktop browser.  Mobile's fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: 02 Park Ave on March 18, 2022, 01:02:14 PM
Quote from: Rothman on March 18, 2022, 12:50:04 PM
Quote from: CtrlAltDel on March 18, 2022, 12:47:22 PM
Quote from: vdeane on March 18, 2022, 12:41:01 PM
Is Google Maps failing to load data for anyone else?

Yes. It's been a problem all morning.
Yep.  Same here.  But only through a desktop browser.  Mobile's fine.


It is not loading data on my desk-top nor on my i-pad.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 18, 2022, 01:04:21 PM
Quote from: 02 Park Ave on March 18, 2022, 01:02:14 PM
Quote from: Rothman on March 18, 2022, 12:50:04 PM
Quote from: CtrlAltDel on March 18, 2022, 12:47:22 PM
Quote from: vdeane on March 18, 2022, 12:41:01 PM
Is Google Maps failing to load data for anyone else?

Yes. It's been a problem all morning.
Yep.  Same here.  But only through a desktop browser.  Mobile's fine.


It is not loading data on my desk-top nor on my i-pad.
Well...I guess when I move away from already downloaded maps, I'm not getting anything but a base map.  Awesome.

So yeah, it sucks.
Title: Re: Google Maps just fucking SUCKS now
Post by: jmacswimmer on March 18, 2022, 02:16:27 PM
MDOT's CHART website even has a disclaimer about it at the moment:

(https://i.ibb.co/Y21czYC/Google.jpg) (https://ibb.co/p2MftG7)
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on March 18, 2022, 02:27:39 PM
Google Maps appears to fully be back up.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on March 20, 2022, 12:38:17 AM
Quote from: jakeroot on March 15, 2022, 01:39:59 PM

As I'm sure you're well aware, this has already become a headache with newspaper archives. The News Tribune (in Tacoma) stopped archiving scanned copies of their newspapers in the 1990s, opting for digital only. They only switched back to full page scans a few years ago. While the text is there and, in some ways, easier to search, being able to search through an entire scanned newspaper definitely has its advantages.

The News Tribune was added a few months ago to Newspapers.com, with full pages from the 1890s to the early 2000s.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on March 22, 2022, 10:10:25 PM
Google maps directions really sucked when I was in Texas the past week

- Half of the time, it doesn't tell me which exit it is from a freeway. Skips that step and tells me to turn left from the frontage road even when I was still on the freeway
- When it does mark it as an exit from a freeway without exit numbers, it sometimes says "exit to [frontage road name]" instead of the perpendicular road name denoted on the BGS. That's as useful as not telling me anything.
- On the contrary, exit ramps have been marked as "right turns" on the GPS more than once.
- Lane markings aren't correct sometimes either. For example, it only showed one left turn lane at an intersection when there were really two.
- Had me make a random U-turn on a freeway (I ignored it of course)
- Doesn't distinguish between toll roads and toll roads that are only for people with a certain transponder.
- Highway designation error:
(https://i.imgur.com/3rb5i3k.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: HighwayStar on March 23, 2022, 10:47:57 AM
Quote from: SkyPesos on March 22, 2022, 10:10:25 PM
Google maps directions really sucked when I was in Texas the past week

- Half of the time, it doesn't tell me which exit it is from a freeway. Skips that step and tells me to turn left from the frontage road even when I was still on the freeway
- When it does mark it as an exit from a freeway without exit numbers, it sometimes says "exit to [frontage road name]" instead of the perpendicular road name denoted on the BGS. That's as useful as not telling me anything.
- On the contrary, exit ramps have been marked as "right turns" on the GPS more than once.
- Lane markings aren't correct sometimes either. For example, it only showed one left turn lane at an intersection when there were really two.
- Had me make a random U-turn on a freeway (I ignored it of course)
- Doesn't distinguish between toll roads and toll roads that are only for people with a certain transponder.
- Highway designation error:
(https://i.imgur.com/3rb5i3k.jpg)

Texas roads are really too good for Google Maps in many cases. Its easier to just put down the computer and navigate the system with its Texas U turns, etc. by intuition and signage.

Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on March 23, 2022, 08:44:23 PM
Quote from: HighwayStar on March 23, 2022, 10:47:57 AM
Quote from: SkyPesos on March 22, 2022, 10:10:25 PM
Google maps directions really sucked when I was in Texas the past week

- Half of the time, it doesn't tell me which exit it is from a freeway. Skips that step and tells me to turn left from the frontage road even when I was still on the freeway
- When it does mark it as an exit from a freeway without exit numbers, it sometimes says "exit to [frontage road name]" instead of the perpendicular road name denoted on the BGS. That's as useful as not telling me anything.
- On the contrary, exit ramps have been marked as "right turns" on the GPS more than once.
- Lane markings aren't correct sometimes either. For example, it only showed one left turn lane at an intersection when there were really two.
- Had me make a random U-turn on a freeway (I ignored it of course)
- Doesn't distinguish between toll roads and toll roads that are only for people with a certain transponder.
- Highway designation error:
(https://i.imgur.com/3rb5i3k.jpg)

Texas roads are really too good for Google Maps in many cases. Its easier to just put down the computer and navigate the system with its Texas U turns, etc. by intuition and signage.
Except Texas doesn't have exit numbers on a lot of non-interstate freeways (and I think they should, but whatever). Easier to remember a single number than a long road name, if I'm not going to use a GPS in unfamiliar territory.
Title: Re: Google Maps just fucking SUCKS now
Post by: HighwayStar on March 23, 2022, 09:10:02 PM
Quote from: SkyPesos on March 23, 2022, 08:44:23 PM
Quote from: HighwayStar on March 23, 2022, 10:47:57 AM
Quote from: SkyPesos on March 22, 2022, 10:10:25 PM
Google maps directions really sucked when I was in Texas the past week

- Half of the time, it doesn't tell me which exit it is from a freeway. Skips that step and tells me to turn left from the frontage road even when I was still on the freeway
- When it does mark it as an exit from a freeway without exit numbers, it sometimes says "exit to [frontage road name]" instead of the perpendicular road name denoted on the BGS. That's as useful as not telling me anything.
- On the contrary, exit ramps have been marked as "right turns" on the GPS more than once.
- Lane markings aren't correct sometimes either. For example, it only showed one left turn lane at an intersection when there were really two.
- Had me make a random U-turn on a freeway (I ignored it of course)
- Doesn't distinguish between toll roads and toll roads that are only for people with a certain transponder.
- Highway designation error:
(https://i.imgur.com/3rb5i3k.jpg)

Texas roads are really too good for Google Maps in many cases. Its easier to just put down the computer and navigate the system with its Texas U turns, etc. by intuition and signage.
Except Texas doesn't have exit numbers on a lot of non-interstate freeways (and I think they should, but whatever). Easier to remember a single number than a long road name, if I'm not going to use a GPS in unfamiliar territory.

While I agree on the need for numbers (and actually signing those roads as interstates or at least US routes), having to remember Preston Road or Spring Creek Parkway is not really that problematic to me. However where numbers do become an issue are for things like Belt Line Road, which intersects the same tollway more than once, making it possible to take the wrong Belt Line Road exit.
Nevertheless I find Texas one of the easier states to navigate without GPS
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on March 24, 2022, 03:08:34 PM
Google Maps has BUS I-90 through Spearfish signed as BUS US 90.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on March 24, 2022, 06:24:09 PM
Quote from: jlam on March 24, 2022, 03:08:34 PM
Google Maps has BUS I-90 through Spearfish signed as BUS US 90.

:banghead:
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on March 30, 2022, 02:11:16 AM
Is Google Maps running very choppy for anyone else?
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on March 30, 2022, 10:28:54 PM
I've been trying to use Google Street View to find this billboard along I-75;

(https://upload.wikimedia.org/wikipedia/commons/thumb/f/f9/Adult_%282135896193%29.jpg/640px-Adult_%282135896193%29.jpg)

I have some vague memories of the billboard, and this thing could've been anywhere north of Exit 329 and south of Exit 374. So I've been trying to check using the views from 2007 focusing on rural areas outside of Ocala. The trouble is, it keeps shifting from the northbound lanes to the southbound lanes and I can't get back to the northbound lanes. And when it's not doing that, it suddenly starts going backwards when I'm trying to go forwards. So because of these defects, I still can't find the exact location.

Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 30, 2022, 10:31:41 PM
I-270 in Denver wasn't marked earlier today.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on March 30, 2022, 11:41:07 PM
Quote from: Rothman on March 30, 2022, 10:31:41 PM
I-270 in Denver wasn't marked earlier today.
And it still isn't (at least on mobile)
Title: Re: Google Maps just SUCKS now
Post by: webny99 on March 31, 2022, 08:52:22 AM
Quote from: Roadgeekteen on March 30, 2022, 02:11:16 AM
Is Google Maps running very choppy for anyone else?

It is on mobile (has been for a few days, seemingly), but it's fine on my laptop.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on March 31, 2022, 11:45:56 AM
Quote from: Rothman on March 30, 2022, 10:31:41 PM
I-270 in Denver wasn't marked earlier today.

Like the little yellow lines were gone or just the shields?
Title: Re: Google Maps just fucking SUCKS now
Post by: FrCorySticha on March 31, 2022, 12:35:00 PM
I'm seeing I-270 marked only as US 36, while I-25 is also marked I-270:

(https://i.imgur.com/OmpEVId.png?1)
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on March 31, 2022, 01:13:51 PM
Quote from: Rothman on March 30, 2022, 10:31:41 PM
I-270 in Denver wasn't marked earlier today.

I just logged onto Google Maps and saw this. That’s very odd.

Also, why is MA 128 from Peabody to Gloucester not marked either. It’s just marked as Yankee Division Highway
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 05, 2022, 11:26:47 AM
Google Maps labels are entirely broken. Many of them in a given region are the same (e.g. twenty places all named Georgetown), sometimes cut off in the middle of a word or even the middle of a letter.
Title: Re: Google Maps just SUCKS now
Post by: webny99 on April 05, 2022, 02:36:52 PM
Quote from: 1 on April 05, 2022, 11:26:47 AM
Google Maps labels are entirely broken. Many of them in a given region are the same (e.g. twenty places all named Georgetown), sometimes cut off in the middle of a word or even the middle of a letter.

Is this still the case? I haven't had any issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: JayhawkCO on April 05, 2022, 02:46:41 PM
I-270 still doesn't exist. I kind of wish it didn't as it's my least favorite highway.
Title: Re: Google Maps just fucking SUCKS now
Post by: Bruce on April 05, 2022, 04:44:55 PM
The schedule explorer for transit directions was quietly dropped a few months ago. I used the feature a lot when traveling extensively by transit before the pandemic, so it's awful to see it gone.

https://bgr.com/tech/google-silently-dumps-schedule-explorer-from-google-maps/
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 07, 2022, 01:51:38 AM
Quote from: Bruce on April 05, 2022, 04:44:55 PM
The schedule explorer for transit directions was quietly dropped a few months ago. I used the feature a lot when traveling extensively by transit before the pandemic, so it's awful to see it gone.

https://bgr.com/tech/google-silently-dumps-schedule-explorer-from-google-maps/

This seems like an odd choice, I find it hard to believe it wasn't utilized; I didn't use transit a ton but I loved that feature when I did.
Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on April 07, 2022, 12:20:29 PM
Quote from: JayhawkCO on April 05, 2022, 02:46:41 PM
I-270 still doesn't exist. I kind of wish it didn't as it's my least favorite highway.

And oddly enough, thanks to CDOT's practice of signing multiplexes ONLY if they absolutely, positively have to, there is little to no mention of US-36 along that same stretch in the real world.
Title: Re: Google Maps just fucking SUCKS now
Post by: ozarkman417 on April 07, 2022, 12:32:54 PM
a pretty dangerous set of curves, especially for an interstate (https://www.google.com/maps/@38.5436957,-90.4339954,19.33z)
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 07, 2022, 04:46:17 PM
Quote from: ozarkman417 on April 07, 2022, 12:32:54 PM
a pretty dangerous set of curves, especially for an interstate (https://www.google.com/maps/@38.5436957,-90.4339954,19.33z)

I can just imagine the warning sign:
(https://i.imgur.com/1qsSpd4.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 07, 2022, 05:21:31 PM
 :-D
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on April 08, 2022, 01:01:43 AM
Quote from: thenetwork on April 07, 2022, 12:20:29 PM
Quote from: JayhawkCO on April 05, 2022, 02:46:41 PM
I-270 still doesn't exist. I kind of wish it didn't as it's my least favorite highway.

And oddly enough, thanks to CDOT's practice of signing multiplexes ONLY if they absolutely, positively have to, there is little to no mention of US-36 along that same stretch in the real world.

Hell, CDOT signs would have you thinking US 36 begins at that I-25 interchange (https://goo.gl/maps/cNVGFh2DMMDwzn4X9).
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 13, 2022, 11:37:45 AM
Quote from: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.

Working for me still. Sure hope that doesn't break, scrolling with the mouse wheel is an indispensable feature.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 13, 2022, 11:56:29 AM
Quote from: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.

It happened for me once. Reloading the page twice fixed it.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 13, 2022, 12:48:47 PM
Quote from: jakeroot on April 13, 2022, 11:37:45 AM
Quote from: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.

Working for me still. Sure hope that doesn't break, scrolling with the mouse wheel is an indispensable feature.

Hmm.  Maybe it's my computer for some reason.  Thank you!
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 13, 2022, 12:52:52 PM
No, it happened to me again after I posted above.

Safari 15.3.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on April 13, 2022, 01:09:56 PM
Works for me just fine.  Just tested it in Chrome, Firefox, Internet Explorer (no longer supported by Google), and Edge.
Title: Re: Google Maps just fucking SUCKS now
Post by: dlsterner on April 13, 2022, 07:59:21 PM
Quote from: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.

Yes, it happened to me as well.  It looks like it might be browser dependent.

I normally use Safari (15.3) and my mouse wheel quit working last night for zoom.  Quit Safari, loaded Firefox (98.0.2) and the mouse wheel seems to work fine.  Went back to Safari, mouse wheel worked for about a minute, then quit (the mouse wheel, not Safari itself).

What browser are you using?
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 13, 2022, 08:37:33 PM
Quote from: dlsterner on April 13, 2022, 07:59:21 PM
Quote from: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.

Yes, it happened to me as well.  It looks like it might be browser dependent.

I normally use Safari (15.3) and my mouse wheel quit working last night for zoom.  Quit Safari, loaded Firefox (98.0.2) and the mouse wheel seems to work fine.  Went back to Safari, mouse wheel worked for about a minute, then quit (the mouse wheel, not Safari itself).

What browser are you using?

Safari.
Not too excited about having to install another browser just to make Google Maps work.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on April 13, 2022, 08:48:43 PM
Bugs like this (e.g. measure distance tool a few months ago) typically get fixed within 3 days or even earlier.
Title: Re: Google Maps just fucking SUCKS now
Post by: dlsterner on April 13, 2022, 10:15:53 PM
Quote from: kkt on April 13, 2022, 08:37:33 PM
Quote from: dlsterner on April 13, 2022, 07:59:21 PM
Quote from: kkt on April 13, 2022, 11:32:32 AM
In Google Maps the scroll wheel used to zoom in or out.  Has anyone else noticed that it has stopped doing that?  I can still zoom in or out by clicking on the + or - buttons in the corner.

Yes, it happened to me as well.  It looks like it might be browser dependent.

I normally use Safari (15.3) and my mouse wheel quit working last night for zoom.  Quit Safari, loaded Firefox (98.0.2) and the mouse wheel seems to work fine.  Went back to Safari, mouse wheel worked for about a minute, then quit (the mouse wheel, not Safari itself).

What browser are you using?

Safari.
Not too excited about having to install another browser just to make Google Maps work.

I wouldn't be either, as I have my Safari configuration just right, as far as bookmarks and the like.

But as 1 suggested above, these are the kind of bugs that are usually fixed pretty quickly, so I will try to tough it out.
Title: Re: Google Maps just fucking SUCKS now
Post by: dlsterner on April 13, 2022, 11:12:16 PM
OK, here is an update on the Google Maps & scroll wheel problem when using Safari ...

It's not just us - there is a lot of chatter online about this not working for the past day or so.  The consensus seems to point to a Google issue where it isn't playing nice with Safari.

There is a workaround mentioned:

-   If your "Develop" menu in the menu bar is not visible, make it visible by going to "Preferences"->"Advanced".  There is a check box to turn on the "Develop" menu.
-   At the "User Agent" sub-menu (2nd one in the "Develop" menu) change the User Agent from Safari to Firefox or Chrome.  (You will still be running Safari, but it will lie to anyone who asks and say it is Firefox/Chrome)

The scroll wheel should now work.  Please note that this fix is a "Band-Aid" and that hopefully it will get fixed for real (presumably by Google).  In the long term, you will want to keep it at Safari.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on April 13, 2022, 11:13:38 PM
Why the fuck would you check the browser string to see if you can take away a feature?
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on April 14, 2022, 12:09:03 AM
Quote from: Scott5114 on April 13, 2022, 11:13:38 PMWhy the fuck would you check the browser string to see if you can take away a feature?

In some cases I've seen it used seemingly to deny resources to tools like wget and curl that are designed to support unattended downloading.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on April 14, 2022, 12:48:19 AM
Quote from: J N Winkler on April 14, 2022, 12:09:03 AM
Quote from: Scott5114 on April 13, 2022, 11:13:38 PMWhy the fuck would you check the browser string to see if you can take away a feature?

In some cases I've seen it used seemingly to deny resources to tools like wget and curl that are designed to support unattended downloading.

That's even sillier, because it presupposes there's a broad base of potential users out there that know enough about the command line to successfully compose and execute a curl command, but have never been exposed to documentation of the --user-agent flag.
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on April 14, 2022, 01:02:48 AM
Quote from: dlsterner on April 13, 2022, 11:12:16 PM
OK, here is an update on the Google Maps & scroll wheel problem when using Safari ...

It's not just us - there is a lot of chatter online about this not working for the past day or so.  The consensus seems to point to a Google issue where it isn't playing nice with Safari.

There is a workaround mentioned:

-   If your "Develop" menu in the menu bar is not visible, make it visible by going to "Preferences"->"Advanced".  There is a check box to turn on the "Develop" menu.
-   At the "User Agent" sub-menu (2nd one in the "Develop" menu) change the User Agent from Safari to Firefox or Chrome.  (You will still be running Safari, but it will lie to anyone who asks and say it is Firefox/Chrome)

The scroll wheel should now work.  Please note that this fix is a "Band-Aid" and that hopefully it will get fixed for real (presumably by Google).  In the long term, you will want to keep it at Safari.

Hey, what do you know, it works!  I changed it to advertise I'm using Firefox, and quit and restarted Safari, and now my zoom wheel is back.  Thank you!

Yes, for tech companies sabatoging each other for no obvious reason is part of the game.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on May 12, 2022, 05:37:14 PM
I'm noticing that freeways and major arterials have a new, more opaque yellow color on satellite views at certain zoom levels:

(https://imgur.com/j5b9KeU.jpg)

Thoughts?
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on May 13, 2022, 10:08:09 AM
I noticed a glitch when it comes to Street View on iOS. When I go to drop a pin on a road, the Street View image won't appear. But it will appear sometimes. In this case I have to press Street View in the map details menu. Anyone else having this problem?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 13, 2022, 11:32:19 AM
Quote from: CoreySamson on May 12, 2022, 05:37:14 PM
I'm noticing that freeways and major arterials have a new, more opaque yellow color on satellite views at certain zoom levels:

(https://imgur.com/j5b9KeU.jpg)

Thoughts?

I was waiting to see if someone would notice this too (if it was just me or what). So far, I like it.

Quote from: BlueOutback7 on May 13, 2022, 10:08:09 AM
I noticed a glitch when it comes to Street View on iOS. When I go to drop a pin on a road, the Street View image won't appear. But it will appear sometimes. In this case I have to press Street View in the map details menu. Anyone else having this problem?

I usually notice this after I've had a Google Maps tab open for a while.
Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on May 13, 2022, 01:05:19 PM
This has been happening for a while:

* search for a certain city or location
* go exploring on street view, often several miles distant
* press Escape to open map or satellite view in the spot you are now
* Google Maps moves you back to the original search spot instead
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on May 13, 2022, 01:19:16 PM
In Street View, I've noticed that the black square in the top left corner where the address and historical imagery slider is will sometimes not display the address at all, instead showing a default "Google" as the address. Not a big deal, but still an odd bug.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 13, 2022, 01:32:07 PM
Quote from: kurumi on May 13, 2022, 01:05:19 PM
This has been happening for a while:

* search for a certain city or location
* go exploring on street view, often several miles distant
* press Escape to open map or satellite view in the spot you are now
* Google Maps moves you back to the original search spot instead

This has been happening to me too, and I hate it.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 13, 2022, 01:41:45 PM
Oh yeah, I've been hating both of those issues lately.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on May 13, 2022, 06:15:58 PM
Quote from: kurumi on May 13, 2022, 01:05:19 PMThis has been happening for a while:

* search for a certain city or location

* go exploring on street view, often several miles distant

* press Escape to open map or satellite view in the spot you are now

* Google Maps moves you back to the original search spot instead

+1 for me on this issue, too.  X'ing out the search result avoids this problem, but that extra step is a hassle.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on May 13, 2022, 06:27:35 PM
Quote from: LilianaUwU on May 13, 2022, 01:19:16 PM
In Street View, I've noticed that the black square in the top left corner where the address and historical imagery slider is will sometimes not display the address at all, instead showing a default "Google" as the address. Not a big deal, but still an odd bug.

And it will display the name of a business if in front of it. Odd.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on May 17, 2022, 04:24:06 PM
Quote from: Scott5114 on April 14, 2022, 12:48:19 AM
Quote from: J N Winkler on April 14, 2022, 12:09:03 AM
Quote from: Scott5114 on April 13, 2022, 11:13:38 PMWhy the fuck would you check the browser string to see if you can take away a feature?

In some cases I've seen it used seemingly to deny resources to tools like wget and curl that are designed to support unattended downloading.

That's even sillier, because it presupposes there's a broad base of potential users out there that know enough about the command line to successfully compose and execute a curl command, but have never been exposed to documentation of the --user-agent flag.

I've been thinking about this a little, and I suspect there is no one single motivation for resorting to user-agent checking.  I've observed the following:

*  Server responds to a request with a HTTP 400- or 500-series error (some variant of "You're not getting what you're asking for") if there is no user-agent header, but supplies actual content when such a header is present.  (This is common but by no means universal for the contracting platforms and EDMSes highway agencies use for distributing construction plans.)

*  Request hangs when sent with a user-agent header corresponding to an obsolete browser version, but returns actual content when the header references a current browser version or no user-agent header is used.  (I often see this with newspaper websites.)

In many cases, particularly the ones involving news sites, I think the user-agent header is used as a tool to avoid legal liability for providing content that is not accessible.

Recent versions of browsers like Firefox and Chrome have network listeners that track page loads and allow individual requests to be copied as curl invocations that include all headers.  When I use this functionality to write code for unattended downloading using either curl or wget, I try to keep things simple by pruning wget and curl invocations back to just the headers that are actually necessary for the request to go through.  In several cases I've found that it's actually the Accept-Language header that makes the difference (not, surprisingly, Accept or Accept-Encoding).  I've had one script break when, after several months of smooth runs, the server started demanding a different capitalization pattern for XMLHttpRequest headers.  In at least one case, a server wouldn't accept wget --post-data={postdata} or wget --post-file={path to file with postdata}, but would accept wget --method=POST --data={postdata} (method had to be explicitly specified).  In another, the server demanded use of the HTTP DELETE method (which I had never heard of!).
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 19, 2022, 11:59:18 AM
Quote from: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.

Mine seems to assume I go at least 15 mph over the limit at all times. I assume this because, after doing so, I arrive at exactly the ETA.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on May 19, 2022, 12:29:33 PM
Quote from: jakeroot on May 19, 2022, 11:59:18 AM
Quote from: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.

Mine seems to assume I go at least 15 mph over the limit at all times. I assume this because, after doing so, I arrive at exactly the ETA.
The ETA adjusts as you travel.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on May 19, 2022, 12:41:16 PM
I've actually found that the Google Maps estimate doesn't like speed limits higher than about 70 mph.

For example, I can plot a trip on the Kansas Turnpike–speed limit 75 mph–that shows 100% green in the Traffic overlay, yet the math invariably works out to about 71 or 72 mph average.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 19, 2022, 12:48:39 PM
Quote from: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.
Yeah, I think so too.  What I'm wondering is if one of those times is the time for where it assumes you don't exceed the speed limit at any point - ie, not assuming you're going to go 65 in a 55 because that's what the Waze data has for the historical data for that section of road for that time/day.  The time Google quotes for "leave now" assumes that you're going to be going the speed of the historical traffic data, regardless of whether it goes faster or slower than the limit (I'm usually right on with my 5-7 over, but there are places where it seems to be too optimistic for my driving patterns, and obviously all the times would be wrong if I ever were to start adhering exactly to the limit, which I probably would if NY ever adopted 70 mph limits on rural freeways, especially if NJ, MA, VT, and the rest of NH did too).

This is all for planning future roadtrips on the desktop version, of course.  I only use the directions for trip planning travel time estimation and not turn by turn directions, so I have no idea what it would do for that.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 19, 2022, 05:50:40 PM
Quote from: Rothman on May 19, 2022, 12:29:33 PM
Quote from: jakeroot on May 19, 2022, 11:59:18 AM
Quote from: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.

Mine seems to assume I go at least 15 mph over the limit at all times. I assume this because, after doing so, I arrive at exactly the ETA.
The ETA adjusts as you travel.

My apologies for not being specific, but I was referring to situations where the ETA does not change from start to finish. Which is surprisingly common from my experience. Or at the very least, it's within a minute or two.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on May 19, 2022, 05:51:49 PM
Quote from: jakeroot on May 19, 2022, 05:50:40 PM
Quote from: Rothman on May 19, 2022, 12:29:33 PM
Quote from: jakeroot on May 19, 2022, 11:59:18 AM
Quote from: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.

Mine seems to assume I go at least 15 mph over the limit at all times. I assume this because, after doing so, I arrive at exactly the ETA.
The ETA adjusts as you travel.

My apologies for not being specific, but I was referring to situations where the ETA does not change from start to finish. Which is surprisingly common from my experience. Or at the very least, it's within a minute or two.
I haven't ever had it not change, even on short trips.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on May 19, 2022, 05:56:03 PM
Quote from: Rothman on May 19, 2022, 05:51:49 PM
Quote from: jakeroot on May 19, 2022, 05:50:40 PM
Quote from: Rothman on May 19, 2022, 12:29:33 PM
Quote from: jakeroot on May 19, 2022, 11:59:18 AM
Quote from: Scott5114 on May 18, 2022, 09:33:21 PM
Quote from: vdeane on May 18, 2022, 09:28:52 PM
Just curious, is there any knowledge on how the range of drive times for the "depart at" feature with directions is calculated?  I'm wondering if the long one, or at least the "arrive at" time (often but not always matching the long one) is the one where you don't drive faster than the speed limit, because the one it quotes for the "leave now" feature definitely isn't.

I think it uses historical Waze data to calculate the approximate drive time depending on past traffic patterns for the specified time of day.

Mine seems to assume I go at least 15 mph over the limit at all times. I assume this because, after doing so, I arrive at exactly the ETA.
The ETA adjusts as you travel.

My apologies for not being specific, but I was referring to situations where the ETA does not change from start to finish. Which is surprisingly common from my experience. Or at the very least, it's within a minute or two.
I haven't ever had it not change, even on short trips.

It's about 50/50 for me, being within a minute of the original ETA at least.

But, for the sake of my explanation, let's assume that ETA is irrelevant. Waze still seems to assume that it will take me, say, eight minutes to go ten miles, even if the speed limit is 60.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 22, 2022, 09:29:23 PM
Is the COVID-19 layer no longer displaying for anyone else?  It's still on the list, and they still have the thing on the bottom with some numbers, but the map overlay seems to be gone.
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on May 22, 2022, 09:59:56 PM
Quote from: vdeane on May 22, 2022, 09:29:23 PM
Is the COVID-19 layer no longer displaying for anyone else?  It's still on the list, and they still have the thing on the bottom with some numbers, but the map overlay seems to be gone.

It's not working for me either. Must be some kind of bug.
Title: Re: Google Maps just fucking SUCKS now
Post by: doorknob60 on May 25, 2022, 11:29:05 AM
They broke Street View again. A lot of areas it will only let you move one frame at a time, making it painfully slow to get around. Doesn't always happen, but it's happening a lot. I seem to recall this being a problem months ago, then it got fixed. Hope they fix it again.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on May 25, 2022, 12:22:24 PM
Yep. I was finishing the Giro d'Italia route, and man, it was a real PITA the last days (on top of the reduced speed). They have updated Street View a few days ago in the countries they don't continuously update, and like always they broke it. Another thing is that my computer would somehow crash after a while, but I found that is more of a Firefox issue because I switched to Chrome and all went fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: Molandfreak on June 02, 2022, 10:53:08 PM
I mean, I suppose this is US 224 ALT... (https://www.google.com/maps/@41.0536105,-81.6533801,5175m/data=!3m1!1e3)  :confused:
(https://upload.wikimedia.org/wikipedia/en/9/9d/To_Northbound_OH_SR_21_from_Eastbound_I-76.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Caps81943 on June 22, 2022, 08:41:17 PM
The slow traveling and bad snapping have been UNBEARABLE today.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on June 30, 2022, 11:13:49 PM
Anyone else have issues with GSV moving you in random directions on each click now? Very difficult to even look at the area around a road when it can either move you to the left or right on another road or move you backwards when you want to go forward.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on June 30, 2022, 11:21:30 PM
Quote from: SkyPesos on June 30, 2022, 11:13:49 PM
Anyone else have issues with GSV moving you in random directions on each click now? Very difficult to even look at the area around a road when it can either move you to the left or right on another road or move you backwards when you want to go forward.

Yup. Between that and the slow as hell scrolling, it's kind of getting to the point where it's faster to move along by repeatedly dropping the pin and exiting out until you get the view you want. A true failure of software design.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on July 01, 2022, 09:00:19 AM
Quote from: Scott5114 on June 30, 2022, 11:21:30 PM

Quote from: SkyPesos on June 30, 2022, 11:13:49 PM
Anyone else have issues with GSV moving you in random directions on each click now? Very difficult to even look at the area around a road when it can either move you to the left or right on another road or move you backwards when you want to go forward.

Yup. Between that and the slow as hell scrolling, it's kind of getting to the point where it's faster to move along by repeatedly dropping the pin and exiting out until you get the view you want. A true failure of software design.

I have good luck zooming in on the little corner-map and just clicking a different spot on the blue line.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 08, 2022, 08:17:11 PM
Remember that glitch that removed the points from measuring distance?  It's back, but it seems like this time they're still there and can be interacted with, they're just not visible the way they were before.  Mouse over the line and the tooltip will change when you're on a point, so they can still be moved/removed despite being invisible.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on July 09, 2022, 01:43:49 AM
I have no idea if this has been mentioned in this 94-page topic, as there is no board function that searches an individual topic.

In the past year, I've noticed more and more "new" street view imagery that's almost unusable. Wikipedia has a couple of items that may be relevant:


  • 2017: On September 5, Google announced that they are improving the quality of the street view panoramic photo, revamping its mapping vehicles with all-new high-resolution camera systems and artificial intelligence to capture even better imagery. The new Google cars have been seen in various American cities since March 2017, as well as in Japan since August. The first images taken with the new generation of cameras were available online on September 13.
  • October 2017: The makers of the Insta360 Pro announce the certification of the first "Street View auto ready" camera for US$3500; it uses six lenses for a 360º view and comes with Stitcher software. In addition to purchase, the camera rig is also available to qualified entities as part of the Google loaner program, with 50 cameras available to loan, making possible Google Street View imagery coverage of more places that Google might not visit, and to entities for whom a purchase is impractical or impossible.

There's a lot of imagery in which the roof of the car carrying the camera is visible, and which is super over-compressed and washed out. I'm wondering if this is the 2017 "improved" technology. In Google Earth, this imagery doesn't even respond to navigation clicks. In Google Maps, it looks like this:

https://goo.gl/maps/xP5pN4MXppqJBfPK8 (https://goo.gl/maps/xP5pN4MXppqJBfPK8)

This isn't always new imagery where formerly there was none. Sometimes, it duplicates older imagery which is beautiful, and once you land on the bad imagery, you can't get back to the good imagery without exiting and re-entering.

Some imagery shot from more portable cameras, perhaps from the Insta360 gear, is completely cockeyed, rotating around a non-vertical axis:

https://goo.gl/maps/GVe9D5STFM4HC6XH9 (https://goo.gl/maps/GVe9D5STFM4HC6XH9)

It's almost as if there's a competition to see how bad they can make this.


Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on July 09, 2022, 02:09:54 AM
Quote from: kphoger on July 01, 2022, 09:00:19 AM
Quote from: Scott5114 on June 30, 2022, 11:21:30 PM

Quote from: SkyPesos on June 30, 2022, 11:13:49 PM
Anyone else have issues with GSV moving you in random directions on each click now? Very difficult to even look at the area around a road when it can either move you to the left or right on another road or move you backwards when you want to go forward.

Yup. Between that and the slow as hell scrolling, it's kind of getting to the point where it's faster to move along by repeatedly dropping the pin and exiting out until you get the view you want. A true failure of software design.

I have good luck zooming in on the little corner-map and just clicking a different spot on the blue line.

I haven't. What tends to happen is that the little person turns around and then I have to rotate it. Sometimes I get lucky, but it's not as common as you'd hope.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 09, 2022, 06:51:21 AM
Quote from: pderocco on July 09, 2022, 01:43:49 AM
as there is no board function that searches an individual topic

Using the search feature while inside a thread will search that thread only.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 09, 2022, 05:25:01 PM
Quote from: pderocco on July 09, 2022, 01:43:49 AM
I have no idea if this has been mentioned in this 94-page topic, as there is no board function that searches an individual topic.

In the past year, I've noticed more and more "new" street view imagery that's almost unusable. Wikipedia has a couple of items that may be relevant:


  • 2017: On September 5, Google announced that they are improving the quality of the street view panoramic photo, revamping its mapping vehicles with all-new high-resolution camera systems and artificial intelligence to capture even better imagery. The new Google cars have been seen in various American cities since March 2017, as well as in Japan since August. The first images taken with the new generation of cameras were available online on September 13.
  • October 2017: The makers of the Insta360 Pro announce the certification of the first "Street View auto ready" camera for US$3500; it uses six lenses for a 360º view and comes with Stitcher software. In addition to purchase, the camera rig is also available to qualified entities as part of the Google loaner program, with 50 cameras available to loan, making possible Google Street View imagery coverage of more places that Google might not visit, and to entities for whom a purchase is impractical or impossible.

There's a lot of imagery in which the roof of the car carrying the camera is visible, and which is super over-compressed and washed out. I'm wondering if this is the 2017 "improved" technology. In Google Earth, this imagery doesn't even respond to navigation clicks. In Google Maps, it looks like this:

https://goo.gl/maps/xP5pN4MXppqJBfPK8 (https://goo.gl/maps/xP5pN4MXppqJBfPK8)

This isn't always new imagery where formerly there was none. Sometimes, it duplicates older imagery which is beautiful, and once you land on the bad imagery, you can't get back to the good imagery without exiting and re-entering.

Some imagery shot from more portable cameras, perhaps from the Insta360 gear, is completely cockeyed, rotating around a non-vertical axis:

https://goo.gl/maps/GVe9D5STFM4HC6XH9 (https://goo.gl/maps/GVe9D5STFM4HC6XH9)

It's almost as if there's a competition to see how bad they can make this.



That's not Google imagery.  That's some third party called "PTOWN HACKS Provincetown Guide".  Third party imagery can be a crapshoot but is worse than Google's most of the time, which is why I don't understand why Google seems to favor it.  It seems like if there is any third party imagery in an area, Google will prefer it over its own, even if its own is newer, and because the sequencing of images isn't exactly the same, it can be offset from Google's, which makes it hard to switch out of.  Third party imagery can be great if Google hasn't gone somewhere or hasn't been somewhere recently, but it sucks the rest of the time.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr_Northside on July 15, 2022, 01:31:44 PM
Quote from: SkyPesos on June 30, 2022, 11:13:49 PM
Anyone else have issues with GSV moving you in random directions on each click now? Very difficult to even look at the area around a road when it can either move you to the left or right on another road or move you backwards when you want to go forward.

I still notice this on occasion  (especially in densely crowded areas).   The navigation can sink to levels as clunky as the Bing street-view equivalent at times.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 02, 2022, 07:02:03 AM
Route numbers/shields are missing on my Android version of Google Maps now.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on August 04, 2022, 02:11:23 AM
Quote from: Rothman on August 02, 2022, 07:02:03 AM
Route numbers/shields are missing on my Android version of Google Maps now.

Could be a cache problem. Perhaps rebooting your phone might help. Or maybe they come from a different server, and it was down for a while.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 04, 2022, 06:48:20 AM


Quote from: pderocco on August 04, 2022, 02:11:23 AM
Quote from: Rothman on August 02, 2022, 07:02:03 AM
Route numbers/shields are missing on my Android version of Google Maps now.

Could be a cache problem. Perhaps rebooting your phone might help. Or maybe they come from a different server, and it was down for a while.

They're back now.  I think it may have had something to do with the public transportation layer.  Found that Google Maps had turned it on for some reason; flipping it off brought the shields back, I think.  Either that or the last problem with the server you mentioned.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 04, 2022, 12:44:02 PM
The transit layer does indeed cause the shields to disappear.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on August 25, 2022, 11:40:16 PM
"No Street View imagery available here."

I've been getting this annoying popup as of the past day or two even if just trying to advance one sphere forward and I know GSV imagery exists.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 27, 2022, 09:10:35 AM
I noticed that it's now possible to see older streetview images on the android app. Before that, you had to do it with a browser. Took long enough.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 27, 2022, 01:27:05 PM
Quote from: LM117 on August 27, 2022, 09:10:35 AM
I noticed that it's now possible to see older streetview images on the android app. Before that, you had to do it with a browser. Took long enough.

I've also noticed this. I think it rolled out, at least to iOS devices, in late July. It's been awesome being able to research something on-the-spot rather than having to wait until getting home.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on August 27, 2022, 03:51:20 PM
They have also filled the last gap without Street View along US 2 in Montana. Now if they could fix the last few places in which one is still forced to go through all frames and increase the distance one can click to the old one...
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on August 27, 2022, 09:28:58 PM
Quote from: jakeroot on August 27, 2022, 01:27:05 PM
Quote from: LM117 on August 27, 2022, 09:10:35 AM
I noticed that it's now possible to see older streetview images on the android app. Before that, you had to do it with a browser. Took long enough.

I've also noticed this. I think it rolled out, at least to iOS devices, in late July. It's been awesome being able to research something on-the-spot rather than having to wait until getting home.

I think the android version was more recent than that, because I didn't see it until about a week ago. Then again, I wasn't looking for it and stumbled across it by accident. Either way, I'm not complaining. :coffee:
Title: Re: Google Maps just fucking SUCKS now
Post by: Molandfreak on September 19, 2022, 02:17:52 PM
Why did Google feel the need to apply the name "Blues Highway"  to all of US 61? I guess that would be understandable in Mississippi since they have those goofy blue signs with that name, but nobody north of Missouri knows 61 as the blues highway...
Title: Re: Google Maps just fucking SUCKS now
Post by: kirbykart on September 19, 2022, 02:21:52 PM
Quote from: Molandfreak on September 19, 2022, 02:17:52 PM
Why did Google feel the need to apply the name "Blues Highway"  to all of US 61? I guess that would be understandable in Mississippi since they have those goofy blue signs with that name, but nobody north of Missouri knows 61 as the blues highway...
Another weird thing Google does is when a US route is concurrent with an Interstate, and you go into StreetView on it, it often says the US Route Number and not the Interstate Number for some reason.
Title: Re: Google Maps just fucking SUCKS now
Post by: NE2 on September 19, 2022, 08:53:49 PM
Currently I-40 is not shown as a freeway just east of the TX/NM line (easiest to notice if you have traffic on and zoom out enough). Which is technically correct...
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 20, 2022, 01:25:25 PM
Quote from: NE2 on September 19, 2022, 08:53:49 PM
Currently I-40 is not shown as a freeway just east of the TX/NM line (easiest to notice if you have traffic on and zoom out enough). Which is technically correct...

So did that bee in |Bobby5280|'s bonnet finally get the better of him, or what?   :)
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on October 05, 2022, 03:00:11 PM
Latest Google Maps complaint:  if you change to satellite view and then open the "Map details" pane, you can't uncheck "Labels" anymore (the blue check mark does not clear when you click on it).
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on October 05, 2022, 08:45:39 PM
Quote from: J N Winkler on October 05, 2022, 03:00:11 PM
Latest Google Maps complaint:  if you change to satellite view and then open the "Map details" pane, you can't uncheck "Labels" anymore (the blue check mark does not clear when you click on it).
Yep, this is a big annoyance.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on October 05, 2022, 10:21:05 PM
https://goo.gl/maps/Wo55tU6MDmsZWxVY9

Is it my tablet or what, but I can't advance east under the building on US 40 in Baltimore.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on October 05, 2022, 10:45:54 PM
Quote from: Rothman on October 05, 2022, 08:45:39 PM
Quote from: J N Winkler on October 05, 2022, 03:00:11 PM
Latest Google Maps complaint:  if you change to satellite view and then open the "Map details" pane, you can't uncheck "Labels" anymore (the blue check mark does not clear when you click on it).
Yep, this is a big annoyance.

Not seeing it. Mac OS 12.6, Chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on October 05, 2022, 11:27:29 PM
Quote from: jakeroot on October 05, 2022, 10:45:54 PM
Quote from: Rothman on October 05, 2022, 08:45:39 PM
Quote from: J N Winkler on October 05, 2022, 03:00:11 PM
Latest Google Maps complaint:  if you change to satellite view and then open the "Map details" pane, you can't uncheck "Labels" anymore (the blue check mark does not clear when you click on it).
Yep, this is a big annoyance.

Not seeing it. Mac OS 12.6, Chrome.
It's just an additonal click to find where to turn the labels off.  Used to be easier to find.
Title: Re: Google Maps just fucking SUCKS now
Post by: kirbykart on October 06, 2022, 09:29:38 AM
Quote from: roadman65 on October 05, 2022, 10:21:05 PM
https://goo.gl/maps/Wo55tU6MDmsZWxVY9

Is it my tablet or what, but I can't advance east under the building on US 40 in Baltimore.

I've noticed that sometimes GSV doesn't have imagery under low clearances like this.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 06, 2022, 10:57:54 AM
Quote from: J N Winkler on October 05, 2022, 03:00:11 PM
Latest Google Maps complaint:  if you change to satellite view and then open the "Map details" pane, you can't uncheck "Labels" anymore (the blue check mark does not clear when you click on it).

The blue checkmark clears just fine for me, and labels disappear when I do so.

(https://i.imgur.com/EyFKbNe.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on October 06, 2022, 11:41:48 AM
Something that makes no sense to me: I went to use Google Maps to get walking directions and a time estimate. I zoomed in on the area I wanted because I didn't know the address of either the place of origin or the destination, so I planned just to click on each one. When I clicked on the first location, selected "Directions from here," and then clicked on the walking man icon, it immediately zoomed way the heck out to a 10-mile radius. Yet when I seek driving directions, even local ones to get a sense for what traffic conditions are, it stays zoomed in close at the level I had selected. What good is that? What's the point of doing that? Aren't most people looking for walking directions more likely to look for something within a mile or two maximum, and aren't most people opting between walking and driving more likely to walk for a shorter distance and drive for something longer?
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on October 06, 2022, 12:24:56 PM
Quote from: kphoger on October 06, 2022, 10:57:54 AM
Quote from: J N Winkler on October 05, 2022, 03:00:11 PM
Latest Google Maps complaint:  if you change to satellite view and then open the "Map details" pane, you can't uncheck "Labels" anymore (the blue check mark does not clear when you click on it).

The blue checkmark clears just fine for me, and labels disappear when I do so.

(https://i.imgur.com/EyFKbNe.jpg)

It doesn't work for me on Firefox, but it does work for me on Chrome.

One of the things I used to like was that it did work even for the regular map, without the aerials. And my first thought was that that was what they were trying to "fix," but they just went too far.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 06, 2022, 12:28:20 PM
Quote from: CtrlAltDel on October 06, 2022, 12:24:56 PM
It doesn't work for me on Firefox, but it does work for me on Chrome.

Ahhh.  I was using Edge.  Just tried it in Firefox, and it didn't work for me in that browser either.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on October 06, 2022, 01:04:44 PM
Quote from: kphoger on October 06, 2022, 12:28:20 PM
Quote from: CtrlAltDel on October 06, 2022, 12:24:56 PMIt doesn't work for me on Firefox, but it does work for me on Chrome.

Ahhh.  I was using Edge.  Just tried it in Firefox, and it didn't work for me in that browser either.

I just tried it in Chrome and did indeed get it to work:

(https://i.imgur.com/28BVYVb.png)

It does look like a browser-specific JavaScript incompatibility.  It also surfaces in Firefox regardless of path taken to the desired end state, which can be (1) click on view control (toggle satellite/map view) --> choose "More" --> click "Labels" or (2) hover on view control --> choose "More" --> click satellite view icon (changes "Labels" from grayed out to active) --> click "Labels."
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on October 06, 2022, 01:11:56 PM
Quote from: J N Winkler on October 06, 2022, 01:04:44 PM


:bigass:  By the way, well played, sir.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on October 06, 2022, 10:11:46 PM
Currently, Google Maps names the entire former Putnam Division of the New York Central Railroad in Westchester County as the "South County Trailway" from Van Cortlandt Park in the Bronx to NY 118 in Baldwin Place.

https://www.google.com/maps/@41.345148,-73.7546689,210m/data=!3m1!1e3?hl=en

I'm pretty sure north of NY 119 in Elmsford, it's called the "North County Trailway."

BTW, I was looking up the Putnam Trail at the time after checking out the Southeast Metro-North railroad station, and imagining how much fun that must be.


Title: Re: Google Maps just fucking SUCKS now
Post by: kirbykart on October 07, 2022, 10:06:25 AM
Very near me, all the online mapping services bypassed the village of Cattaraugus by sending drivers down Catt CR 76, Lovers Lane Road. Now I am pleasantly surprised because I recently looked up directions on Google Maps and they did not use this awful road. Why do you even need to bypass a village of 1,000? And also Bing Maps routes you through Cattaraugus now, which is surprising because they always love to send you out of the way on random backroads.
Cattaraugus, NY (https://goo.gl/maps/owXV8ri8CTjXPAdS6)
Google doesn't have StreetView of Lovers Lane Road, but I can assure you it is an awful road, it goes out of the way and is not worth what you get out of it.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on October 07, 2022, 05:56:40 PM
https://www.google.com/maps/@40.2807818,-76.6639312,16.96z
They seem to have West Chocolate Avenue applied to US 422 after US 422 leaves West Chocolate for the expressway that leads into US 322.

I believe all rural parts of US 422 in PA ( or the eastern segment anyway) are the Benjamin Franklin Highway.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on October 15, 2022, 11:00:19 AM
For some reason, Google Maps thinks this street in Port Jefferson Station, New York is part of "State Highway 25A."
https://www.google.com/maps/@40.9332188,-73.0455032,3a,75y,355.89h,83.64t/data=!3m6!1e1!3m4!1s2Ma0-JVlJLUWDJd6fUy7nw!2e0!7i16384!8i8192?hl=en
But it's just Columbia Street.


Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on October 15, 2022, 10:39:38 PM
Wonder if there was a bad data import from some ancient database or something. They're now showing OK 122, which was decommissioned in 1966.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on October 16, 2022, 01:29:44 AM
Hardly a new issue... there are a whole host of "state highways" in Utah and especially Nevada that were decommissioned long ago but are still marked on Google Maps. I don't trust any of their route designations in Nevada without confirming with another source.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on October 16, 2022, 07:53:50 AM
Quote from: US 89 on October 16, 2022, 01:29:44 AM
Hardly a new issue... there are a whole host of "state highways" in Utah and especially Nevada that were decommissioned long ago but are still marked on Google Maps. I don't trust any of their route designations in Nevada without confirming with another source.
Heh.  Las Vegas state shields on Google Maps drive me nuts.  Definitely have to consult elsewhere.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on October 16, 2022, 08:45:36 AM
Quote from: US 89 on October 16, 2022, 01:29:44 AM
Hardly a new issue... there are a whole host of "state highways" in Utah and especially Nevada that were decommissioned long ago but are still marked on Google Maps. I don't trust any of their route designations in Nevada without confirming with another source.
Yeah, but that street was never a state highway.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on October 16, 2022, 09:33:16 AM
Quote from: D-Dey65 on October 16, 2022, 08:45:36 AM
Quote from: US 89 on October 16, 2022, 01:29:44 AM
Hardly a new issue... there are a whole host of "state highways" in Utah and especially Nevada that were decommissioned long ago but are still marked on Google Maps. I don't trust any of their route designations in Nevada without confirming with another source.
Yeah, but that street was never a state highway.
When has that ever stopped Google Maps from marking a street with a shield?

I just went through some travel planning in Virginia where I found half-a-dozen errors of a similar sort.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on October 16, 2022, 11:39:26 AM
Quote from: Rothman on October 16, 2022, 07:53:50 AM
Quote from: US 89 on October 16, 2022, 01:29:44 AM
Hardly a new issue... there are a whole host of "state highways" in Utah and especially Nevada that were decommissioned long ago but are still marked on Google Maps. I don't trust any of their route designations in Nevada without confirming with another source.
Heh.  Las Vegas state shields on Google Maps drive me nuts.  Definitely have to consult elsewhere.

It's not even just Vegas (which, to be fair, has a state route landscape that changes ridiculously quickly). It's the little roads out in the middle of nowhere that changed hands years and years ago that really get me. Say you're driving north on US 93 from Ely to the 93A split. Google says you'll junction SR 490, SR 486, SR 893, and SR 489 along the way...but only 490 is legitimate.
Title: Re: Google Maps just fucking SUCKS now
Post by: CoreySamson on October 16, 2022, 01:41:53 PM
Quote from: Scott5114 on October 15, 2022, 10:39:38 PM
Wonder if there was a bad data import from some ancient database or something. They're now showing OK 122, which was decommissioned in 1966.
It's also showing OK 124... which was decommissioned in 1970. I actually clinched the route retrospectively last week and there is no signage or anything suggesting that a state highway once was routed there.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on October 21, 2022, 01:28:51 AM
Quote from: Rothman on October 16, 2022, 09:33:16 AM
Quote from: D-Dey65 on October 16, 2022, 08:45:36 AM
Quote from: US 89 on October 16, 2022, 01:29:44 AM
Hardly a new issue... there are a whole host of "state highways" in Utah and especially Nevada that were decommissioned long ago but are still marked on Google Maps. I don't trust any of their route designations in Nevada without confirming with another source.
Yeah, but that street was never a state highway.
When has that ever stopped Google Maps from marking a street with a shield?

I just went through some travel planning in Virginia where I found half-a-dozen errors of a similar sort.
'
And I remember when they added a New York State Route 495 shield to a cul-de-sac off of a service road between Medford and Yaphank. Here they just show the name "State Highway 25A" along the street and in the address box.

Okay, here's something else; I've been trying to make them realize a certain rest area along I-20 in South Carolina has an official designation, and despite the SCDOT website showing that name, they refuse to recognize it as evidence.

Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on December 04, 2022, 09:12:43 AM
Hoo boy. More Google Maps errors in New York, this time in Sears Corners.

New York State Route 312's eastern terminus is a NY 22 in Sears Corners. However according to Google, it continues onto a dead-end street which serves as the entrance to the Valley View Town Centre.
https://www.google.com/maps/@41.4282327,-73.5774848,838m/data=!3m1!1e3?hl=en


Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on December 13, 2022, 08:19:46 PM
At some point, Google stopped displaying the proper street names for the on-road section of the Empire State Trail with "Empire State Trl (https://www.google.com/maps/@42.7374628,-73.695711,16.5z)".
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 02, 2023, 09:38:17 PM
Anyone notice that the numbers next to the measure distance tool are now way too small to read?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 02, 2023, 09:44:58 PM
Quote from: vdeane on February 02, 2023, 09:38:17 PM
Anyone notice that the numbers next to the measure distance tool are now way too small to read?

Not seeing this. All is normal on my end (MacOS, Chrome 109.0.5414.119).
Title: Re: Google Maps just fucking SUCKS now
Post by: IowaTraveler on February 02, 2023, 10:21:43 PM
Quote from: vdeane on February 02, 2023, 09:38:17 PM
Anyone notice that the numbers next to the measure distance tool are now way too small to read?

Yeah, I just noticed that this morning. I normally use Waterfox, but the problem also occurred in when I tested it in Chrome, so it doesn't seem to be a browser-specific issue.

Another recent change that I noticed a few days ago is that they've updated the UI for looking at older Streetview images, so that the preview images are lined up across the bottom of the screen instead of in a timeline near the top left corner.
Title: Re: Google Maps just fucking SUCKS now
Post by: flan on February 02, 2023, 11:30:14 PM
Quote from: IowaTraveler on February 02, 2023, 10:21:43 PM
Another recent change that I noticed a few days ago is that they've updated the UI for looking at older Streetview images, so that the preview images are lined up across the bottom of the screen instead of in a timeline near the top left corner.

And of course when you try to get rid of that annoying bar at the bottom, it moves you back to the newest streetview capture.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 02, 2023, 11:31:39 PM
Also, it's in reverse chronological order, which is odd when going left to right.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 03, 2023, 12:38:33 PM
Quote from: jakeroot on February 02, 2023, 09:44:58 PM
Quote from: vdeane on February 02, 2023, 09:38:17 PM
Anyone notice that the numbers next to the measure distance tool are now way too small to read?

Not seeing this. All is normal on my end (MacOS, Chrome 109.0.5414.119).
For me it's happening at both work (Windows 10/Chrome) and at home (Linux Mint/Vivaldi).  It's not every time, but it's often enough that it's not worth it to screen for it and keep trying with new incognito windows until I get one that doesn't.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on February 03, 2023, 03:34:40 PM
Quote from: vdeane on February 03, 2023, 12:38:33 PM
Quote from: jakeroot on February 02, 2023, 09:44:58 PM
Quote from: vdeane on February 02, 2023, 09:38:17 PM
Anyone notice that the numbers next to the measure distance tool are now way too small to read?

Not seeing this. All is normal on my end (MacOS, Chrome 109.0.5414.119).
For me it's happening at both work (Windows 10/Chrome) and at home (Linux Mint/Vivaldi).  It's not every time, but it's often enough that it's not worth it to screen for it and keep trying with new incognito windows until I get one that doesn't.

That change happened to me while I was using it. I measured something and it was totally fine, and then I moved somewhere else to measure something else, and it was different.
Title: Re: Google Maps just fucking SUCKS now
Post by: CovalenceSTU on February 03, 2023, 08:51:55 PM
Quote from: flan on February 02, 2023, 11:30:14 PM
Quote from: IowaTraveler on February 02, 2023, 10:21:43 PM
Another recent change that I noticed a few days ago is that they've updated the UI for looking at older Streetview images, so that the preview images are lined up across the bottom of the screen instead of in a timeline near the top left corner.
And of course when you try to get rid of that annoying bar at the bottom, it moves you back to the newest streetview capture.
Even worse is that following a link to old Street View doesn't show the bar, but if you open and close it it will take you to the latest one. :rolleyes:
Title: Re: Google Maps just fucking SUCKS now
Post by: TheGrassGuy on February 12, 2023, 09:27:31 AM
At least:

1. Now when you click on a road/street as a destination (e.g. "I-95" or "Fifth Ave"), it now highlights the whole road/street despite Baidu Maps having had this feature for ages already

2. They've been very good at updating old info. Like, the rest of I-840 now has GSV despite it being finished VERY recently
Title: Re: Google Maps just fucking SUCKS now
Post by: MultiMillionMiler on February 12, 2023, 10:27:43 AM
I've had this trouble where it fails to load the color coded traffic data, multiple times in the same hour. Also, sometimes when planning routes, it alters the end point by itself and gives a very awkward route that doesn't make much logical sense.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 12, 2023, 03:30:18 PM
Quote from: TheGrassGuy on February 12, 2023, 09:27:31 AM
2. They've been very good at updating old info. Like, the rest of I-840 now has GSV despite it being finished VERY recently

Not entirely true. They haven't done the new N52 between Marange Silvange and Rombas in Northeastern France yet despite having been open since last May.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 12, 2023, 03:31:34 PM
Quote from: CNGL-Leudimin on February 12, 2023, 03:30:18 PM
Quote from: TheGrassGuy on February 12, 2023, 09:27:31 AM
2. They've been very good at updating old info. Like, the rest of I-840 now has GSV despite it being finished VERY recently

Not entirely true. They haven't done the new N52 between Marange Silvange and Rombas in Northeastern France yet despite having been open since last May.
There's a ton of old stuff they haven't updated.    Not sure why Grass said what he did.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on February 15, 2023, 04:03:50 AM
Quote from: Rothman on February 12, 2023, 03:31:34 PM
Quote from: CNGL-Leudimin on February 12, 2023, 03:30:18 PM
Quote from: TheGrassGuy on February 12, 2023, 09:27:31 AM
2. They've been very good at updating old info. Like, the rest of I-840 now has GSV despite it being finished VERY recently

Not entirely true. They haven't done the new N52 between Marange Silvange and Rombas in Northeastern France yet despite having been open since last May.
There's a ton of old stuff they haven't updated.    Not sure why Grass said what he did.
Dare I mention the US highways in Montana/Idaho with 2007 imagery?
Title: Re: Google Maps just fucking SUCKS now
Post by: invincor on February 15, 2023, 08:46:51 AM
I've grown to prefer Apple Maps over Google Maps because it's turn-by-turn driving instructions are more pro-active.  Frequently the instructions from Google Maps come 5 to 10 seconds too late, whereas Apple Maps is saying things like "go past this light, but then at the next one turn left" right on time. 

There is, however, one area I'm not sure of it with.  Traffic.   I can look at Google Maps and see that it's always got its eye on the traffic situation, whereas I can't always tell with Apple Maps.  But then, I'm not often driving in high traffic areas, so I'm not sure. 

Has anyone here done a good comparison of the two when it comes to getting you around or through high traffic?
Title: Re: Google Maps just fucking SUCKS now
Post by: IowaTraveler on February 15, 2023, 09:05:38 AM
Quote from: LilianaUwU on February 15, 2023, 04:03:50 AM
Quote from: Rothman on February 12, 2023, 03:31:34 PM
Quote from: CNGL-Leudimin on February 12, 2023, 03:30:18 PM
Quote from: TheGrassGuy on February 12, 2023, 09:27:31 AM
2. They've been very good at updating old info. Like, the rest of I-840 now has GSV despite it being finished VERY recently

Not entirely true. They haven't done the new N52 between Marange Silvange and Rombas in Northeastern France yet despite having been open since last May.
There's a ton of old stuff they haven't updated.    Not sure why Grass said what he did.
Dare I mention the US highways in Montana/Idaho with 2007 imagery?

Dare I mention the section of US 6 near the Colorado/Nebraska border that still hasn't been imaged by GSV?
(It's also worth mentioning the section of US 34 near the Colorado/Nebraska border that wasn't imaged for the first time until August 2022.)

An example that's closer to home for me is that nearly all of Iowa's county roads still had 2008 and 2009 GSV imagery for the longest time, until Google finally started another round of comprehensive imaging in 2021. It's gotten to the point now that the majority of Iowa's county roads have updated GSV imagery (Which has been a godsend for trip planning), but there's still a sizable chunk with grainy 2008-09 images.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 15, 2023, 11:15:32 PM
Why does Google Maps route Yuma to Dallas via Albuquerque rather than El Paso? The southern route is 79 miles shorter.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 15, 2023, 11:38:55 PM
Quote from: Scott5114 on February 15, 2023, 11:15:32 PM
Why does Google Maps route Yuma to Dallas via Albuquerque rather than El Paso? The southern route is 79 miles shorter.
I-20 has a closure, silly man.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 15, 2023, 11:52:37 PM
Quote from: Rothman on February 15, 2023, 11:38:55 PM
Quote from: Scott5114 on February 15, 2023, 11:15:32 PM
Why does Google Maps route Yuma to Dallas via Albuquerque rather than El Paso? The southern route is 79 miles shorter.
I-20 has a closure, silly man.


Any local bypass would be shorter than 79 miles.....
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 16, 2023, 06:48:48 AM
Quote from: Scott5114 on February 15, 2023, 11:52:37 PM
Quote from: Rothman on February 15, 2023, 11:38:55 PM
Quote from: Scott5114 on February 15, 2023, 11:15:32 PM
Why does Google Maps route Yuma to Dallas via Albuquerque rather than El Paso? The southern route is 79 miles shorter.
I-20 has a closure, silly man.


Any local bypass would be shorter than 79 miles.....
Sure, but whenever an obvious direct route is not chosen by Google Maps, one should check it for incidents, for that is the most likely cause of an unexpected routing.
Title: Re: Google Maps just fucking SUCKS now
Post by: MultiMillionMiler on February 16, 2023, 11:32:13 AM
I literally go by the color codes, the more green in the route, the better. Even it's a much longer route. I'd rather drive for an even longer amount of total time without traffic than in even a little traffic for a shorter amount of time.
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on February 16, 2023, 04:20:16 PM
Quote from: IowaTraveler on February 15, 2023, 09:05:38 AM
Dare I mention the section of US 6 near the Colorado/Nebraska border that still hasn't been imaged by GSV?
(It's also worth mentioning the section of US 34 near the Colorado/Nebraska border that wasn't imaged for the first time until August 2022.)

Parts of US 2 in Northeastern Montana also lacked Street View until that date. I bet that last section of US 6 will fall some time in 2023.

I also remember Western North Carolina being a hole in Street View coverage until 2016 or so.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 16, 2023, 06:33:27 PM
Quote from: MultiMillionMiler on February 16, 2023, 11:32:13 AM
I literally go by the color codes, the more green in the route, the better. Even it's a much longer route. I'd rather drive for an even longer amount of total time without traffic than in even a little traffic for a shorter amount of time.

This shows your inexperience with long (300+ mile) road trips. Because it takes time to cover distance, traffic conditions are likely to change (jams cleared, new jams developed in different place) by the time you reach the affected area. As such, it makes the most sense to choose your route based on clear conditions and only route around recurring bottleneck areas.
Title: Re: Google Maps just fucking SUCKS now
Post by: 1995hoo on February 17, 2023, 09:33:37 AM
Here is something I don't understand:

I asked Google Maps for directions to Carter—Finley Stadium (outdoor NHL game there tomorrow night). While I know where the stadium is, I wanted a traffic estimate given the rainy weather. Google Maps says the traditional I-95/I-85 route is the fastest and the amount of time is an amount I know to be roughly the norm from when I lived in Durham 25 years ago. The first alternate it gives has you exit in Richmond onto I-195, then use the Powhite Parkway and US-360 to South Boston, then US-501 south to Durham. It shows that route as a bit over an hour longer and it says, "Crashes on I-95S causing 58-min delay." How does that make any sense at all? Wouldn't the route that uses I-95 and I-85 take longer than the normal travel time if there were an hour-long delay somewhere on I-95, given that the alternate route overlaps with the most direct route between DC and Richmond? (Put differently, if the crashes on I-95 were to the south of the I-195 exit, then the I-95/I-85 route should take an hour longer than specified.)

Does Google Maps just have some weird way of explaining the delays?
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on February 17, 2023, 02:03:13 PM
What is it with Google Maps on iOS not showing Street View? Every time I try to click on a road to see GSV, it won't appear. Anyone else having this issue?
Title: Re: Google Maps just fucking SUCKS now
Post by: MultiMillionMiler on February 17, 2023, 03:23:59 PM
Quote from: BlueOutback7 on February 17, 2023, 02:03:13 PM
What is it with Google Maps on iOS not showing Street View? Every time I try to click on a road to see GSV, it won't appear. Anyone else having this issue?

Yes actually, but only with certain roads. I was trying to look at some in Nevada it was having trouble loading that square to click on GSV. I had a similar issue with Germany trying to view Autobahn stretches and if only worked if I clicked in a major city. I thought these were satellite based but maybe there's not enough signals reaching those areas, or they are using actual pictures and not satellites.
Title: Re: Google Maps just fucking SUCKS now
Post by: pianocello on February 18, 2023, 08:52:50 AM
Quote from: MultiMillionMiler on February 17, 2023, 03:23:59 PM
I had a similar issue with Germany trying to view Autobahn stretches and if only worked if I clicked in a major city. I thought these were satellite based but maybe there's not enough signals reaching those areas, or they are using actual pictures and not satellites.

Just a note, that's more likely an effect of Google publishing almost no Street View footage in Germany due to privacy rules.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 18, 2023, 09:53:36 PM
What is this, a measuring tool for ants?
(https://i.imgur.com/YmXfqzE.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: wanderer2575 on February 19, 2023, 11:20:46 AM
Quote from: BlueOutback7 on February 17, 2023, 02:03:13 PM
What is it with Google Maps on iOS not showing Street View? Every time I try to click on a road to see GSV, it won't appear. Anyone else having this issue?

I've been having this issue on my desktop PC for the past few days.  I click on a point on a route and the little box pops up as usual, but instead of the thumbnail image to click to go into Street View all I get is the gray image indicating that no SV is available.  Any ideas?
Title: Re: Google Maps just fucking SUCKS now
Post by: kirbykart on February 20, 2023, 01:24:58 PM
I've been noticing that too. I have to apply the Street View layer to actually see the Streetview.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on March 13, 2023, 05:59:02 PM
Is it just me or is google maps running really slow lately?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 13, 2023, 07:37:45 PM
Quote from: Roadgeekteen on March 13, 2023, 05:59:02 PM
Is it just me or is google maps running really slow lately?
It was for me earlier today.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on April 07, 2023, 10:07:16 PM
Google Maps has designated Interstate 69 north to Interstate 465, despite not being anywhere close to Interstate standard.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 12, 2023, 08:32:05 PM
Anyone else dealing with the annoying sidebar on the left?  I used to be able to get away from it by closing and reopening incognito windows until GM would load without it, but that no longer works.
Title: Re: Google Maps just fucking SUCKS now
Post by: flan on April 12, 2023, 08:35:16 PM
I found if you click on the 'saved' tab then it lets you collapse the whole thing, but then the search bar goes away too.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on April 12, 2023, 08:46:07 PM
For me, clicking "saved" brings up a sign-in prompt.  Clicking the three bars brings up a menu.  Clicking the white space does nothing.  The arrow button to the side that used to appear with previous attempts of pushing a sidebar and collapsed it doesn't appear.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on April 13, 2023, 10:43:02 PM
I also have that small sidebar. I have not found any way to close it.

I do not understand the concept behind it. There is nothing on it that wasn't available via the original menu button. Except now there is this giant vertical white bar.

Stupid. :pan:
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on April 13, 2023, 10:44:54 PM
Just block it with uBlock Origin or any adblocker that allows picking elements to block.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on April 14, 2023, 02:27:50 PM
Technically, you can go to a specific location (click on or type an address), then collapse the whole side panel.  I realize that's not ideal, but it does hide the bar.
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on April 14, 2023, 09:05:43 PM
Not directly linked to this thread but it's worth to mention there's a thread on Skyscraperpage talking about how out of date is your city on Google maps.
https://skyscraperpage.com/forum/showthread.php?t=254440
Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on April 14, 2023, 09:06:14 PM
Here's Google Maps on Firefox for the past several days. Each highway gets a distinctive pattern instead of a route marker.
(https://i.imgur.com/umncMtS.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on April 14, 2023, 09:19:42 PM
Quote from: kurumi on April 14, 2023, 09:06:14 PM
Here's Google Maps on Firefox for the past several days. Each highway gets a distinctive pattern instead of a route marker.
(weird bug)
Weird, I'm on Firefox too and it doesn't do that.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on April 15, 2023, 08:22:44 AM
Quote from: kurumi on April 14, 2023, 09:06:14 PM
Here's Google Maps on Firefox for the past several days. Each highway gets a distinctive pattern instead of a route marker.
(https://i.imgur.com/umncMtS.png)


I see Scotland on that map.  They're probably just different tartans.
Title: Re: Google Maps just fucking SUCKS now
Post by: FrCorySticha on April 15, 2023, 10:38:35 AM
Quote from: kurumi on April 14, 2023, 09:06:14 PM
Here's Google Maps on Firefox for the past several days. Each highway gets a distinctive pattern instead of a route marker.
(https://i.imgur.com/umncMtS.png)

Not seeing that here either. Might need to clear your cache if you haven't already.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 15, 2023, 10:58:29 AM
Quote from: LilianaUwU on April 13, 2023, 10:44:54 PM
Just block it with uBlock Origin or any adblocker that allows picking elements to block.

I tried that. It leaves an empty black vertical bar. Which is admittedly an improvement. That said, further exploration shows that it also blacks out any directions that it gives you.

I've also noticed that the width of the window is a factor and that it won't appear if the window is too narrow.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on April 15, 2023, 02:06:25 PM
Quote from: CtrlAltDel on April 15, 2023, 10:58:29 AM
Quote from: LilianaUwU on April 13, 2023, 10:44:54 PM
Just block it with uBlock Origin or any adblocker that allows picking elements to block.

I tried that. It leaves an empty black vertical bar. Which is admittedly an improvement. That said, further exploration shows that it also blacks out any directions that it gives you.

I've also noticed that the width of the window is a factor and that it won't appear if the window is too narrow.
If it blocks the directions, you blocked the wrong part. Unblock it, get directions, then try blocking it again and you can make sure you're only getting rid of the sidebar and not the directions as well.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on April 15, 2023, 08:03:41 PM
Quote from: CtrlAltDel on April 15, 2023, 10:58:29 AM
It leaves an empty black vertical bar. Which is admittedly an improvement.

How is that an improvement?  Isn't the same amount of the map covered up either way?
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on April 15, 2023, 08:26:47 PM
Quote from: kphoger on April 15, 2023, 08:03:41 PM
Quote from: CtrlAltDel on April 15, 2023, 10:58:29 AM
It leaves an empty black vertical bar. Which is admittedly an improvement.

How is that an improvement?  Isn't the same amount of the map covered up either way?

If you prefer dark mode, having a black bar would be less visually intrusive than a white bar.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on April 16, 2023, 11:37:40 AM
Quote from: kphoger on April 15, 2023, 08:03:41 PM
Quote from: CtrlAltDel on April 15, 2023, 10:58:29 AM
It leaves an empty black vertical bar. Which is admittedly an improvement.

How is that an improvement?  Isn't the same amount of the map covered up either way?

Well, it's not only the map being covered up that bothers me.


Quote from: bm7 on April 15, 2023, 02:06:25 PM
Quote from: CtrlAltDel on April 15, 2023, 10:58:29 AM
Quote from: LilianaUwU on April 13, 2023, 10:44:54 PM
Just block it with uBlock Origin or any adblocker that allows picking elements to block.

I tried that. It leaves an empty black vertical bar. Which is admittedly an improvement. That said, further exploration shows that it also blacks out any directions that it gives you.

I've also noticed that the width of the window is a factor and that it won't appear if the window is too narrow.

If it blocks the directions, you blocked the wrong part. Unblock it, get directions, then try blocking it again and you can make sure you're only getting rid of the sidebar and not the directions as well.

Yes, that is a good plan and one I should have thought of on my own. That said, I tried it, and it worked, but when I came back this morning, it had reverted somehow to the new standard. So, there's some dynamic process here which furthers my annoyance.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on May 30, 2023, 07:23:57 PM
The sidebar is now optional:
(https://i.imgur.com/Z9F4wLS.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on May 30, 2023, 08:53:15 PM
Now if only they could fix the measure distance tool so that one could add points in the middle again.
Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on May 30, 2023, 11:49:07 PM
Quote from: kphoger on April 15, 2023, 08:22:44 AM
Quote from: kurumi on April 14, 2023, 09:06:14 PM
Here's Google Maps on Firefox for the past several days. Each highway gets a distinctive pattern instead of a route marker.
(https://i.imgur.com/umncMtS.png)


I see Scotland on that map.  They're probably just different tartans.

The problem went away with a Firefox update. Now it's just a Canterbury Tale.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on June 05, 2023, 08:26:50 PM
(https://i.imgur.com/ip66Ayt.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on June 05, 2023, 09:40:16 PM
Thing is, he's right.

Imagine if paper road maps had white roads outlined in light gray lines on a very light gray background. Everyone would think the printer was running out of ink.

But this isn't unique to Google. Some time around a quarter century ago, that became the accepted style, for the "lesser" roads, in everybody's maps. Bing does. Mapquest does. OpenStreetMaps does. Mapillary does. Here Wego does. TomTom does. The old MSS&T software did. They all suck.

DeLorme at least sold Topo USA for desktop/laptop that used contrasty colors. It sucked for other reasons.

So what color should roads be? How about black? Is black good for you? Pavement is black, or blacker than the lines on these maps, so you'd think that choice might have occurred to someone, somewhere along the line. The background should be white, or pale colors indicating park land or city/town extents.

If they provided a choice, it would be interesting to see how many people would switch.
Title: Re: Google Maps just fucking SUCKS now
Post by: J N Winkler on June 07, 2023, 01:35:40 PM
I find my color and contrast preferences depend on what I am trying to do.  If I'm hunting for the shortest routing (in either distance or time) between two points, it helps to have the roads sort of fade into the background.  If I'm looking at an unfamiliar country and trying to get a sense of how its motorway system is structured (as I have been doing recently with the Netherlands, having just downloaded the more than 100,000 sign images in its signing database (https://www.aaroads.com/forum/index.php?topic=29746.0)), it is inconvenient not to be able to view that road class at higher contrast.

One solution--which I do not expect ever to receive development effort, because it does not contribute to the corporate goal of profiting through ads--would be to make the colors for all displayed features fully user-adjustable, with the ability to define different color profiles for different purposes.
Title: Re: Google Maps just fucking SUCKS now
Post by: SkyPesos on June 19, 2023, 10:12:35 AM
LA Metro's Regional Connector opened a couple of days ago, and Google Maps still haven't updated their transit layer yet, and even didn't give transit directions involving the Reginal Connector until a day or two after opening. Apple maps updated both within an hour of it opening.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on June 29, 2023, 04:06:59 PM
I don't know what Google did, but for about a month now Google Maps has been painfully slow to the point of unusability on Firefox. Everything else works fine. On Chrome it is perfectly fine, maybe even better than it used to be now. This reeks of antitrust-type fuckery. I've had to use Chrome for everything Maps-related for a while, and I hate using Chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on June 29, 2023, 04:10:39 PM
I noticed yesterday that N. West Street, here in Wichita, gained an additional 3 miles by overlapping with W 21st Street.

(https://i.imgur.com/eRK1cph.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: therocket on June 29, 2023, 08:23:49 PM
Quote from: index on June 29, 2023, 04:06:59 PM
I don't know what Google did, but for about a month now Google Maps has been painfully slow to the point of unusability on Firefox. Everything else works fine. On Chrome it is perfectly fine, maybe even better than it used to be now. This reeks of antitrust-type fuckery. I've had to use Chrome for everything Maps-related for a while, and I hate using Chrome.
Firefox user here: It works perfectly fine
Title: Re: Google Maps just fucking SUCKS now
Post by: index on June 30, 2023, 04:25:29 AM
Quote from: therocket on June 29, 2023, 08:23:49 PM
Quote from: index on June 29, 2023, 04:06:59 PM
I don't know what Google did, but for about a month now Google Maps has been painfully slow to the point of unusability on Firefox. Everything else works fine. On Chrome it is perfectly fine, maybe even better than it used to be now. This reeks of antitrust-type fuckery. I've had to use Chrome for everything Maps-related for a while, and I hate using Chrome.
Firefox user here: It works perfectly fine

For you, maybe. A chat I am in with two other people who use Firefox + Google Maps to look at roads have complained of the same issue.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 01, 2023, 07:44:23 AM
Quote from: index on June 30, 2023, 04:25:29 AM
Quote from: therocket on June 29, 2023, 08:23:49 PM
Quote from: index on June 29, 2023, 04:06:59 PM
I don't know what Google did, but for about a month now Google Maps has been painfully slow to the point of unusability on Firefox. Everything else works fine. On Chrome it is perfectly fine, maybe even better than it used to be now. This reeks of antitrust-type fuckery. I've had to use Chrome for everything Maps-related for a while, and I hate using Chrome.
Firefox user here: It works perfectly fine

For you, maybe. A chat I am in with two other people who use Firefox + Google Maps to look at roads have complained of the same issue.

Firefox on Mac user here, no issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on July 02, 2023, 06:48:39 PM
I've had the same problem on my desktop machine, and eventually switched my default to Edge (which is Chrome). However the slowness wasn't limited to Google Maps, it was present on some other sites too. Yet Firefox with the exact same config is still fine on my laptop.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on July 04, 2023, 10:40:39 AM
Quote from: pderocco on July 02, 2023, 06:48:39 PM
I've had the same problem on my desktop machine, and eventually switched my default to Edge (which is Chrome). However the slowness wasn't limited to Google Maps, it was present on some other sites too. Yet Firefox with the exact same config is still fine on my laptop.

I am using my laptop for the first time in about four months (I am selling my desktop as I no longer need it) and it looks like Google Maps on Firefox is messed up on there as well. I guess I'm just going to have to totally get used to using Chrome for Google Maps. I'm no stranger to having to open up Chrome for stuff every now and then anyway. So many websites only design and test for Chromium-based browsers and Safari, and don't care for anything else. So annoying.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 04, 2023, 10:41:56 AM
I don't think this is "only testing for Chromium-based browsers and Safari"; I think it's Google intentionally throttling Firefox to get people to switch to Chrome. They did that with Internet Explorer about a decade ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on July 04, 2023, 10:45:13 AM
Quote from: 1 on July 04, 2023, 10:41:56 AM
I don't think this is "only testing for Chromium-based browsers and Safari"; I think it's Google intentionally throttling Firefox to get people to switch to Chrome. They did that with Internet Explorer about a decade ago.

Well, yeah, I did bring up that possibility when I originally posted about this issue. In that post I was speaking in a more general sense about how non-Chromium users get shafted all the time.
Title: Re: Google Maps just fucking SUCKS now
Post by: Chris on July 04, 2023, 11:00:46 AM
I use Firefox and also noticed Google Maps is relatively slow. Not 'unusable', but it takes a few seconds to load Google Maps. I have a fiber-optic internet connection so that's definitely not the bottleneck.
Title: Re: Google Maps just fucking SUCKS now
Post by: cstp3103 on July 04, 2023, 11:00:34 PM
yeah, Maps still works on Firefox for me, but it's noticeable slower to the point that if I'm only using Maps I'll just use Chrome instead
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 05, 2023, 06:27:45 AM
I guess this bears repeating: I use Google Maps + Firefox regularly, and I have noticed zero lag compared to using Chrome.

The difference to the rest of you, maybe, is that I use a Mac. I think 1 also does.

I did notice poor performance on Safari; Google Maps would eventually stop loading, and I would have to either reload or close the tab entirely.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on July 05, 2023, 06:44:43 AM
Quote from: jakeroot on July 05, 2023, 06:27:45 AM
The difference to the rest of you, maybe, is that I use a Mac. I think 1 also does.

While I use a Mac, I also use Safari, so I can't join the Firefox comparison. No issues on Safari, though.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 09, 2023, 06:50:25 PM
Had this fun time savings pop up on a recent trip.  Minutes away and yet I could get over an hour in savings...

(https://live.staticflickr.com/65535/53034872654_38d9995609_k.jpg) (https://flic.kr/p/2oNvzW7)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 09, 2023, 07:03:57 PM
Quote from: Rothman on July 09, 2023, 06:50:25 PM
Had this fun time savings pop up on a recent trip.  Minutes away and yet I could get over an hour in savings...

(https://live.staticflickr.com/65535/53034872654_38d9995609_k.jpg) (https://flic.kr/p/2oNvzW7)

I think it's saying that the whole trip (from wherever the blue line starts) has a three minute difference right there at the end depending on which route you take.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 09, 2023, 07:38:48 PM


Quote from: jakeroot on July 09, 2023, 07:03:57 PM
Quote from: Rothman on July 09, 2023, 06:50:25 PM
Had this fun time savings pop up on a recent trip.  Minutes away and yet I could get over an hour in savings...

(https://live.staticflickr.com/65535/53034872654_38d9995609_k.jpg) (https://flic.kr/p/2oNvzW7)

I think it's saying that the whole trip (from wherever the blue line starts) has a three minute difference right there at the end depending on which route you take.

Haven't had it expressed like this before, since it typically takes the total time into account and only displays the difference.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on July 10, 2023, 02:39:13 AM
Quote from: Rothman on July 09, 2023, 07:38:48 PM
Quote from: jakeroot on July 09, 2023, 07:03:57 PM
Quote from: Rothman on July 09, 2023, 06:50:25 PM
Had this fun time savings pop up on a recent trip.  Minutes away and yet I could get over an hour in savings...

(https://live.staticflickr.com/65535/53034872654_38d9995609_k.jpg) (https://flic.kr/p/2oNvzW7)

I think it's saying that the whole trip (from wherever the blue line starts) has a three minute difference right there at the end depending on which route you take.

Haven't had it expressed like this before, since it typically takes the total time into account and only displays the difference.

There is some combination of screens you have to go through to get it, but I've had it happen before. It is needlessly confusing, it should operate more like a traditional GPS where it only shows time remaining. Though to be fair, I think that's normally what happens.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on July 10, 2023, 03:46:47 AM
Quote from: J N Winkler on June 07, 2023, 01:35:40 PM
One solution--which I do not expect ever to receive development effort, because it does not contribute to the corporate goal of profiting through ads--would be to make the colors for all displayed features fully user-adjustable, with the ability to define different color profiles for different purposes.

I believe this is theoretically possible with OSM, though quite labor- and resource-intensive.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on July 24, 2023, 09:27:23 AM
https://goo.gl/maps/4wEvTQZdtDBJXRwSA
What the heck is this? You can't see the road as the center is beyond distortion.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daisy Rahman on July 25, 2023, 09:22:01 AM
Google Maps never works for me as a navigator. In 8 cases out of 10, he leads the route through a dead end or to where there is no turn.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 25, 2023, 11:00:16 AM
Quote from: Daisy Rahman on July 25, 2023, 09:22:01 AM
Google Maps never works for me as a navigator. In 8 cases out of 10, he leads the route through a dead end or to where there is no turn.
8 out of 10?  I mean, it certainly has its drawbacks per all the information in this thread, but I've been using it for navigation for years and only think this has happened to me twice out of hundreds of trips.

One of those times was in Alabama, where I suspected something was going to go awry.  When the dirt road became a two-track and then I came a cross a locked gate, I sent in the photo and they updated their map and routing accordingly.

...

On a tangent, there was once I asked a question through their feedback mechanism ("This road looks like it connects on satellite view, but the map says it doesn't?") and they just updated it to allow the connection without checking reality.  Some DOT had recently blocked off the road in question permanently for whatever reason (complete with curbing and plantings).
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on July 25, 2023, 10:46:39 PM
Quote from: roadman65 on July 24, 2023, 09:27:23 AM
https://goo.gl/maps/4wEvTQZdtDBJXRwSA
What the heck is this? You can't see the road as the center is beyond distortion.
Looks like the imagery got turned 90 degrees. If you "look" what appears to be upwards at the sky, then you can navigate "normally".

I've never seen that with the official Street View, but I've seen it in some secondary crappy Street View that are provided by users with crappy 360VR cameras on their cars. And a lot of the individual 360VR images represented by blue dots open up pointing in some seemingly random direction.
Title: Re: Google Maps just fucking SUCKS now
Post by: therocket on July 31, 2023, 01:46:06 AM
Quote from: roadman65 on July 24, 2023, 09:27:23 AM
https://goo.gl/maps/4wEvTQZdtDBJXRwSA
What the heck is this? You can't see the road as the center is beyond distortion.
The Google Street View camera fell over
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 31, 2023, 06:57:39 AM
Just has to be said, yet again, after 18 years of Google Maps, that,

1) It still would be nice to have county lines on it without relying upon a third-party developer

2) That the mobile version would recognize via points.  Shoot, I'd take the mobile version just taking the static directions created on a desktop, rather than full via point functionality.

I'll be back to repeat this in five years when Google Maps still doesn't have the functionality...
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on July 31, 2023, 09:37:41 AM
Street View is now in Germany!
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on July 31, 2023, 09:45:14 AM
Quote from: vdeane on July 31, 2023, 09:37:41 AM
Street View is now in Germany!
Hm.  So much for papiere, bitte...
Title: Re: Google Maps just fucking SUCKS now
Post by: Stephane Dumas on July 31, 2023, 02:10:11 PM
There's sometimes I wonder if Google Maps have some bias toward one region vs another?
For example: west of Sherbrooke, sectors of Rock Forest and St-Élie d'Orford  https://www.google.com/maps/@45.3873386,-71.9804783,6140m/data=!3m1!1e3?entry=ttu vs ACME Mapper. https://www.google.com/maps/@45.3873386,-71.9804783,6140m/data=!3m1!1e3?entry=ttu

Compared to this view of A-85 southeast of Rivière-du-Loup https://www.google.com/maps/@47.7695984,-69.442694,2938m/data=!3m1!1e3?entry=ttu who was updated more often than ACME Mapper. https://www.google.com/maps/@47.7695984,-69.442694,2938m/data=!3m1!1e3?entry=ttu

Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on August 01, 2023, 02:23:13 AM
Quote from: vdeane on July 31, 2023, 09:37:41 AM
Street View is now in Germany!

I already posted a image from there in the Guess the Country thread while it was being rolled out :sombrero:.
Title: Re: Google Maps just fucking SUCKS now
Post by: flan on August 02, 2023, 12:52:14 AM
Now street view has moved that black info box in the corner from the upper left to the upper right to make room for a search bar. If you are using satellite imagery, go to street view, and use the search function, you will be moved back to 'map' instead of 'satellite'. They also got rid of the arrow button to leave street view so now there's just a weird empty black space in that box.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 02, 2023, 06:57:59 AM
Updated my home location on the mobile version and lost the shortcut home button under the search bar.  Idiotic.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hunty2022 on August 02, 2023, 06:59:28 AM
Quote from: CNGL-Leudimin on August 01, 2023, 02:23:13 AM
Quote from: vdeane on July 31, 2023, 09:37:41 AM
Street View is now in Germany!

I already posted a image from there in the Guess the Country thread while it was being rolled out :sombrero:.

I might have as well, in January.  :sombrero:
Title: Re: Google Maps just fucking SUCKS now
Post by: CNGL-Leudimin on August 02, 2023, 09:51:07 AM
But that was from the old, blurry imagery courtesy of the rage back in the day that made Google not to release any new photos for 13 years, known as "Blurmany" and now gone.
Quote from: flan on August 02, 2023, 12:52:14 AM
Now street view has moved that black info box in the corner from the upper left to the upper right to make room for a search bar. If you are using satellite imagery, go to street view, and use the search function, you will be moved back to 'map' instead of 'satellite'. They also got rid of the arrow button to leave street view so now there's just a weird empty black space in that box.

It took me a while to notice there's now a cross at the top right corner besides the box. I though the only way out now was by zooming out.
Title: Re: Google Maps just fucking SUCKS now
Post by: Daisy Rahman on August 04, 2023, 05:22:04 AM
Quote from: Rothman on July 25, 2023, 11:00:16 AM
Quote from: Daisy Rahman on July 25, 2023, 09:22:01 AM
Google Maps never works for me as a navigator. In 8 cases out of 10, he leads the route through a dead end or to where there is no turn.
8 out of 10?  I mean, it certainly has its drawbacks per all the information in this thread, but I've been using it for navigation for years and only think this has happened to me twice out of hundreds of trips.

One of those times was in Alabama, where I suspected something was going to go awry.  When the dirt road became a two-track and then I came a cross a locked gate, I sent in the photo and they updated their map and routing accordingly.

...

On a tangent, there was once I asked a question through their feedback mechanism ("This road looks like it connects on satellite view, but the map says it doesn't?") and they just updated it to allow the connection without checking reality.  Some DOT had recently blocked off the road in question permanently for whatever reason (complete with curbing and plantings).


I don't know how it turns out, but it is. So I use google maps to view the streets or search for different objects. But as a navigator, it's no good for me.
Title: Re: Google Maps just fucking SUCKS now
Post by: chrismarion100 on August 06, 2023, 04:10:51 AM
I have noticed that some of the street view in my area were updated this past month (aka like two roads) but didn't even bother updating the street view that are 14 years old now or cover the parts of town that they didn't cover areas that they haven't covered. At least now when going down street view we have new 2023 street view then turn into 2008 street view but stay on the same road.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hunty2022 on August 06, 2023, 09:21:33 AM
Quote from: chrismarion100 on August 06, 2023, 04:10:51 AM
I have noticed that some of the street view in my area were updated this past month (aka like two roads) but didn't even bother updating the street view that are 14 years old now or cover the parts of town that they didn't cover areas that they haven't covered. At least now when going down street view we have new 2023 street view then turn into 2008 street view but stay on the same road.

They updated many roads in my county with July 2023 street view. A few of those roads were stuck with 2009 street view before. Some of the roads still are.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on August 07, 2023, 08:59:55 PM
It still puts me on roads I don't want to go on when I drag my line, then it doesn't let me erase them. I was trying to see how long it would take to drive from Spring Hill to a certain movie theater in Ocala via Inglis, and it forced me onto a side road between US 41 and FL 40 north of Rainbow Springs. Then it wouldn't let me delete that side road.
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on August 09, 2023, 05:20:48 PM
I just noticed that they have the University/Asher/Roosevelt/Broadway/Broadway route in Little Rock and North Little Rock signed as Business Loop 30. This road hasn't been BL 30 for several decades. They correctly show the rerouting of US 70 between the I-30/430 interchange and the Asher/University intersection from a couple of years ago, but they have US 70 between I-430 and the Asher/Roosevelt intersection as AR 5, which is not correct as AR 5 ends at I-430. University Avenue isn't a state highway at all anymore since US 70 was rerouted. I wonder where Google gets its data from.
Title: Re: Google Maps just fucking SUCKS now
Post by: bugo on August 13, 2023, 12:10:34 AM
Quote from: Scott5114 on April 13, 2022, 11:13:38 PM
Why the fuck would you check the browser string to see if you can take away a feature?

Because it's an Apple product.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 13, 2023, 03:14:03 PM
Quote from: bugo on August 13, 2023, 12:10:34 AM
Quote from: Scott5114 on April 13, 2022, 11:13:38 PM
Why the fuck would you check the browser string to see if you can take away a feature?

Because it's an Apple product.
Not just Apple.  Vivaldi sends out a Chrome user agent everywhere instead of having its own because otherwise many sites (especially Google) would break otherwise.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on August 13, 2023, 04:05:44 PM
Quote from: D-Dey65 on August 07, 2023, 08:59:55 PM
It still puts me on roads I don't want to go on when I drag my line, then it doesn't let me erase them. I was trying to see how long it would take to drive from Spring Hill to a certain movie theater in Ocala via Inglis, and it forced me onto a side road between US 41 and FL 40 north of Rainbow Springs. Then it wouldn't let me delete that side road.
Was there a road closure? That's usually the cause of that in my experience.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on August 23, 2023, 07:01:32 AM
For the past few months, Google Maps has started assuming that if you searched for directions for a location that you've visited it, although it doesn't add it to your timeline.  Still, you get notifications to contribute a review of the places if you just idly consider a trip.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 23, 2023, 06:12:15 PM
Quote from: Rothman on August 23, 2023, 07:01:32 AM
For the past few months, Google Maps has started assuming that if you searched for directions for a location that you've visited it, although it doesn't add it to your timeline.  Still, you get notifications to contribute a review of the places if you just idly consider a trip.

Yes, I've noticed this too. It's particularly confusing after a late night out, and the next day Maps asks if you want to contribute a review. But you're sure you didn't visit the place...but then you're also not sure since it was a "late night out".

Related minor issue: things are so tightly packed here in Japan, Maps isn't always sure of which place you visited. You'll spend an hour in one place, and the next day it asks you to review the place next door. Oops.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 27, 2023, 09:31:41 PM
Looks like Google is pushing Globe View again.  After a long while of it being off by default, now I randomly get it on by default again.  I think I prefer the instant street view that I get with it off (rather than the animation that happens with it on).
Title: Re: Google Maps just fucking SUCKS now
Post by: CovalenceSTU on August 27, 2023, 10:20:11 PM
Looks like Google Maps now includes the search term when you share a shortlink, which is a bit annoying as catching up on the forums now fills my recent search history.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on August 28, 2023, 12:34:17 PM
Quote from: CovalenceSTU on August 27, 2023, 10:20:11 PM
Looks like Google Maps now includes the search term when you share a shortlink, which is a bit annoying as catching up on the forums now fills my recent search history.
Stuff like that is why I browse Google Maps in incognito mode.
Title: Re: Google Maps just fucking SUCKS now
Post by: Echostatic on August 31, 2023, 06:29:31 PM
My default map view has completely changed. Now looks like this:

(https://i.imgur.com/Xcki8q6.png)

I checked in the layers menu to see if I had accidentally enabled some kind of new look, but nope; this is (seemingly) the actual look of the map now. Here's some more screenshots:

(https://i.imgur.com/eRnCzyI.png)

(https://i.imgur.com/3CzCK1X.png)

I guess the color orange went out of style.

In cities with the more detailed zoom view, this is the new look:

(https://i.imgur.com/TseL47o.png)

The old view remains in Google My Maps. For comparison:

(https://i.imgur.com/9ANliYK.png)

My opinions closely align with the title of this thread.

EDIT: The new traffic view actually looks pretty nice... but overall this update is a clear downgrade.

(https://i.imgur.com/MV7h4Lf.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on August 31, 2023, 07:26:36 PM
Nothing's changed on my end, I'm guessing either it's just startin' to be rolled out, or they're doing A/B testing of it and your in the group that's getting to test the new design.

Personally, I don't hate it.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on August 31, 2023, 08:10:55 PM
It looks like a new thing they're doing to make it look a bit more like Apple Maps:

https://9to5google.com/2023/08/31/google-maps-new-colors/
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on August 31, 2023, 09:20:45 PM
Wow, this looks great. Well done, Google.

I'm not able to explore the new look on any of my devices, but I hope I get to soon. Looks like a great contrast improvement over the current design.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on September 01, 2023, 02:03:35 AM
I'm not seeing it either. But from those screen caps, it looks like they've made the small streets darker, to contrast better with the background. White streets with light gray borders against a very light gray background seems like a boneheaded design. I hope this shows up on the Android phone version, because I need the higher contrast while driving. But I wouldn't mind even higher contrast than this. Remember paper maps? Black lines against a white background? Worked pretty well.
Title: Re: Google Maps just fucking SUCKS now
Post by: SectorZ on September 01, 2023, 09:01:09 AM
In the new design, the light green shading for what I presume is forest is very haphazardly placed compared to reality, at least in my neck of the woods.
Title: Re: Google Maps just fucking SUCKS now
Post by: StogieGuy7 on September 01, 2023, 09:27:36 AM
Quote from: SectorZ on September 01, 2023, 09:01:09 AM
In the new design, the light green shading for what I presume is forest is very haphazardly placed compared to reality, at least in my neck of the woods.

That vegetation shading bears very little resemblance to reality. The "prairie peninsula" that extends from Illinois into NW Indiana is shown as the same sort of forest as the pine woods of the Carolina lowcountry.  :-D

Meanwhile, the St. Louis area is depicted as being more open than central Illinois which, again, is a joke. So, I'm not sure what the cartographers at the Goog were thinking here. They have their vegetated areas all mixed up. Just use the hybrid mode and all this horribleness is forgotten. 
Title: Re: Google Maps just fucking SUCKS now
Post by: GCrites on September 01, 2023, 10:43:13 AM
Yeah it's like the amount of tree cover the U.S. had before the Mayflower.
Title: Re: Google Maps just fucking SUCKS now
Post by: StogieGuy7 on September 01, 2023, 11:28:14 AM
Quote from: GCrites80s on September 01, 2023, 10:43:13 AM
Yeah it's like the amount of tree cover the U.S. had before the Mayflower.

But it's so wrong that we cannot even say that.  They have places like the I-80 corridor in Illinois (a place that is flat and wide open) with thicker vegetation than much of the southeast! It's not even a matter of color-coding gone awry or them depicting what no longer is.  No, the shading contour outlines are just wrong in a lot of areas. They don't resemble reality and seem decorative more than informative. 
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on September 01, 2023, 02:02:48 PM
Quote from: StogieGuy7 on September 01, 2023, 11:28:14 AM
Quote from: GCrites80s on September 01, 2023, 10:43:13 AM
Yeah it's like the amount of tree cover the U.S. had before the Mayflower.

But it's so wrong that we cannot even say that.  They have places like the I-80 corridor in Illinois (a place that is flat and wide open) with thicker vegetation than much of the southeast! It's not even a matter of color-coding gone awry or them depicting what no longer is.  No, the shading contour outlines are just wrong in a lot of areas. They don't resemble reality and seem decorative more than informative.
I wonder if it's just based on satellite imagery. The average farm field in Illinois is more green than those in southern Georgia, for instance.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on September 01, 2023, 04:40:24 PM
Quote from: bm7 on September 01, 2023, 02:02:48 PM
Quote from: StogieGuy7 on September 01, 2023, 11:28:14 AM
Quote from: GCrites80s on September 01, 2023, 10:43:13 AM

Yeah it's like the amount of tree cover the U.S. had before the Mayflower.

But it's so wrong that we cannot even say that.  They have places like the I-80 corridor in Illinois (a place that is flat and wide open) with thicker vegetation than much of the southeast! It's not even a matter of color-coding gone awry or them depicting what no longer is.  No, the shading contour outlines are just wrong in a lot of areas. They don't resemble reality and seem decorative more than informative.

I wonder if it's just based on satellite imagery. The average farm field in Illinois is more green than those in southern Georgia, for instance.

I believe it is, at least with respect to the orange design.
(https://i.imgur.com/HAMImeX.gif)
Title: Re: Google Maps just fucking SUCKS now
Post by: thenetwork on September 04, 2023, 02:45:30 PM
Quote from: Echostatic on August 31, 2023, 06:29:31 PM
My default map view has completely changed. Now looks like this:

(https://i.imgur.com/Xcki8q6.png)

I checked in the layers menu to see if I had accidentally enabled some kind of new look, but nope; this is (seemingly) the actual look of the map now. Here's some more screenshots:

(https://i.imgur.com/eRnCzyI.png)

(https://i.imgur.com/3CzCK1X.png)

I guess the color orange went out of style.

In cities with the more detailed zoom view, this is the new look:

(https://i.imgur.com/TseL47o.png)

The old view remains in Google My Maps. For comparison:

(https://i.imgur.com/9ANliYK.png)

My opinions closely align with the title of this thread.

EDIT: The new traffic view actually looks pretty nice... but overall this update is a clear downgrade.

(https://i.imgur.com/MV7h4Lf.png)

Google Maps just switched over to the new look on my devices over the weekend...
Title: Re: Google Maps just fucking SUCKS now
Post by: Amaury on September 05, 2023, 03:48:14 AM
Roads are still yellow in satellite view, which is what I use; however, entrance/exit ramps, which were previously also yellow, now use a dark blue-gray. And this is for all ramps, whether from a city/town to freeway or freeway-to-freeway, such as the I-82 and I-84 interchange or I-82 and I-90 interchange.
Title: Re: Google Maps just fucking SUCKS now
Post by: JoePCool14 on September 05, 2023, 09:41:15 AM
I have the new Google Maps style on my work computer this morning. I still wish mapping sites would provide the option for grayscale or using various colors for different roads. I don't like everything being a shade of gray. There isn't enough contrast between road types to my liking. I do like the improved contrast between road and background.

I will say that the new traffic colors look nice though.
Title: Re: Google Maps just fucking SUCKS now
Post by: intelati49 on September 05, 2023, 11:03:07 AM
Quote from: JoePCool14 on September 05, 2023, 09:41:15 AM
I have the new Google Maps style on my work computer this morning. I still wish mapping sites would provide the option for grayscale or using various colors for different roads. I don't like everything being a shade of gray. There isn't enough contrast between road types to my liking. I do like the improved contrast between road and background.

I will say that the new traffic colors look nice though.
I agree with the grayscale.

There's a way to fix the curmudgeons complaints though. Give them (us?) the options to fiddle with the colors. OSMAnd is my go to for browsing.

The routing options/traffic is just so useful, so I still use maps as my "GPS"

Was reading the Ars article from a week ago and was wondering the feel here.

https://arstechnica.com/?p=1965118
Title: Re: Google Maps just fucking SUCKS now
Post by: andrepoiy on September 14, 2023, 09:08:20 AM
Mine has changed now

(https://i.imgur.com/AtYBtm4.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 14, 2023, 11:13:25 AM
Quote from: pderocco on September 01, 2023, 02:03:35 AM
But from those screen caps, it looks like they've made the small streets darker, to contrast better with the background. White streets with light gray borders against a very light gray background seems like a boneheaded design.

Agreed.  Worst part of the most recent iteration.  Looking forward to actually being able to see streets again.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on September 14, 2023, 01:08:40 PM
It's very inconsistent as well. Some areas all of the roads are a readable width, but in others most of them are of the barely discernible 1 pixel wide variety.

(https://i.imgur.com/4CNuJow.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 14, 2023, 08:23:16 PM
The new style of Google Maps reminds me of the old style near-monochrome Jimapco maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on September 15, 2023, 01:43:21 PM
Quote from: Echostatic on August 31, 2023, 06:29:31 PM
(https://i.imgur.com/eRnCzyI.png)

I feel the blue is too close to the green to be readily visible. That was one thing that was good about the orange.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on September 15, 2023, 08:33:18 PM
I got the new design briefly today (I browse Google Maps in incognito, so changes tend not to stick around until Google rolls them out to everyone).  It seems like it's even harder to tell the difference between freeways and arterials in the new design and the place markers look a little odd on it as well; they clash with the new color scheme.
Title: Re: Google Maps just fucking SUCKS now
Post by: jt4 on September 16, 2023, 09:20:36 AM
I just noticed today that Google is marking industrial areas in this beige color that reminds me of the desert colors they use out west. I noticed it on the new map design, then logged out and saw it was on the old one too. Coloring "entertainment areas" or whatever's in that light orange color makes sense to me, but why highlight industrial areas in a near-identical color?

(https://i.imgur.com/7w3XzPv.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on September 18, 2023, 12:19:23 PM
– Hey, man...  Google Maps sucks.  The distinction between colors isn't consistent.  What's the point of having different colors for different kinds of roads if you can't reliably tell what kind of road it is by the color?

Google Maps switches all the roads to grey.

– Hey man...  Google Maps sucks.  They don't have different colors for different kinds of roads.
Title: Re: Google Maps just fucking SUCKS now
Post by: Plutonic Panda on October 20, 2023, 12:04:48 AM
What does Google maps use to determine road closures and when they will reopen? Because it seems like every time I click on a road closure and it says road will reopen on this date they're almost always wrong.
Title: Re: Google Maps just fucking SUCKS now
Post by: andrepoiy on October 20, 2023, 01:47:52 AM
Quote from: Plutonic Panda on October 20, 2023, 12:04:48 AM
What does Google maps use to determine road closures and when they will reopen? Because it seems like every time I click on a road closure and it says road will reopen on this date they're almost always wrong.

I know that Waze is one of the sources, and a lot of closures on Waze are added manually
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on October 21, 2023, 10:33:51 PM
I just noticed that it's not showing any closure at all for the northernmost 4.5 miles of CA-39, which has been closed since 1978. They used to show a closure, with some notation indicating it will be closed until (something like) "11:59pm Oct 31, 2028".

I've always found them pretty untrustworthy. I'm now looking at the closures in Inyo County, CA, which includes Death Valley, and they had the entire eastern section of CA-190, plus CA-136, closed for months. Then, they finally opened CA-190 but CA-136 up to Lone Pine was still closed. Now, CA-136 is open and the part of CA-190 that goes south of Owens Lake is shown as closed. I just drove by on US-395 earlier today, and didn't see any closure signs, although I didn't turn down either road to verify.

By the way, Owens Lake is full of water. Never seen it that way before.
Title: Re: Google Maps just fucking SUCKS now
Post by: D-Dey65 on October 24, 2023, 08:18:16 PM
They're still making it difficult to edit the timeline. I wanted to add a site that I went to last week and they won't let me add it. Even two years ago when I was in NYC and I took a trip our to Brooklyn, they ignored the fact that I also went to Lower Manhattan after that. Why?

Title: Re: Google Maps just fucking SUCKS now
Post by: kurumi on November 01, 2023, 12:05:03 AM
I just noticed lane markings for Los Angeles, as Apple Maps has for some cities. On further research, apparently 4 cities are supported: SF, LA, NYC, and Seattle. Here's the 101/Potrero/Cesar Chavez interchange in SF: https://maps.app.goo.gl/oPoJ9nXn6mLsJomZ8

Still sucks if you're looking somewhere else (/rant)

Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on November 16, 2023, 08:20:25 PM
Google Maps switched to its new look on my computer around lunch today. Still normal on mobile.
Title: Re: Google Maps just fucking SUCKS now
Post by: kirbykart on November 16, 2023, 10:01:24 PM
I also got the new color pallette today.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 16, 2023, 11:04:26 PM
I can only get it via private browsing mode, but that's a change from a couple weeks ago. Seems to be rolling out a bit more widely now.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 17, 2023, 11:10:32 PM
Just had another round of edits rejected by Google because they "couldn't verify" them. Even when pasting sources for my changes when making the edits and sometimes when the evidence is literally on their own god damn satellite map.

There was this one road I was trying to fix that was all over the place, far away from where it actually was, named incorrectly on the map, and had a few nonexistent roads branching off of it. The correct shape of the road was literally on their own satellite imagery. Yet still, it was rejected because apparently they couldn't verify it was accurate.

They seriously need to bring back the old community mapping thing. Ever since they removed it things have been so much slower to actually update. There's some parts of town here that are like five years out of date, and of course my edits are rejected for those too even when Google's own satellite info confirms what I've changed.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on November 17, 2023, 11:24:28 PM
They're pretty bad about fixing reported errors. I reported some on the new CA-58 bypass of Hinkley CA, once they opened that stretch of freeway. There were four roads between the two new exits (Lenwood and Hinkley Rds) that were shown as crossing the freeway somehow. Over two years, I reported the error at least three times, and was ignored. Recently, I noticed they had fixed two of the roads, but Mountain View and Summerset are still shown as crossing the freeway. I could forgive them for a while, because it took them a long time to get their own aerial imagery of that stretch, but they have it now, although it's only visible in Google Earth with the time slider turned on.
https://maps.app.goo.gl/vH6qXGzK4EMG7W6WA (https://maps.app.goo.gl/vH6qXGzK4EMG7W6WA)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on November 18, 2023, 06:24:39 AM
They've typically accepted mine. I don't know what's different.
Title: Re: Google Maps just fucking SUCKS now
Post by: LM117 on November 18, 2023, 06:44:43 AM
Quote from: kirbykart on November 16, 2023, 10:01:24 PM
I also got the new color pallette today.

Got it yesterday on my mobile app after updating it. I hate it.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on November 18, 2023, 09:44:43 AM
I got the new color update yesterday. So far, my one big complaint is that it's really hard to see non-major roads in areas with the green backgrounds, especially dark green areas like national forests.

I do like it better in urban areas, and I like the higher prominence of Indian Reservations as those boundaries could be hard to track down or even see on previous versions.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on November 18, 2023, 07:44:41 PM
Google Maps has only twice accepted my fixes (neither of which were particularly important). They extended a road directly through a park in my hometown without reason. I have suggested a reversion of this change three times, and they haven't fixed it.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 19, 2023, 02:10:54 AM
Not too big a fan of the new color update. It would be less so if they returned the differentiation between freeways and major surface roads. I also feel like it would pose accessibility issues for certain people due to the low contrast.
Title: Re: Google Maps just fucking SUCKS now
Post by: epzik8 on November 20, 2023, 08:08:53 AM
Quote from: index on November 19, 2023, 02:10:54 AM
Not too big a fan of the new color update. It would be less so if they returned the differentiation between freeways and major surface roads. I also feel like it would pose accessibility issues for certain people due to the low contrast.

The wonders of AI...
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on November 20, 2023, 06:45:50 PM
The new colors are awful.  Why in the world did they think this was an improvement?
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 20, 2023, 09:05:48 PM
I think we got the big rollout, since I keep getting the new colors no matter how many incognito windows I launch.  And yeah, I agree on them being awful.  I appreciate how the local roads are easier to see, but it's a bigger departure in terms of color than usual and as a result the business labels clash horribly with everything else.  Plus is just looks old fashioned to someone familiar with Jimapco and the monochrome design they used ~15-20 years ago.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 20, 2023, 11:17:12 PM
Yeah, the roll-out has been completed for me, all of my devices are utilizing it now.

So far, I think the new colors are excellent. It's a big improvement from before, especially with the traffic overlay enabled, which no longer has conflicting colors.

There also seems to be new symbology that isn't just color. Parking lots (diagonal lines) and certain sections of park path (when zoomed in, you can see they are dotted) are things I notice right away.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on November 21, 2023, 06:07:21 AM
Quote from: jakeroot on November 20, 2023, 11:17:12 PM
Yeah, the roll-out has been completed for me, all of my devices are utilizing it now.

So far, I think the new colors are excellent. It's a big improvement from before, especially with the traffic overlay enabled, which no longer has conflicting colors.

There also seems to be new symbology that isn't just color. Parking lots (diagonal lines) and certain sections of park path (when zoomed in, you can see they are dotted) are things I notice right away.
Conflicting colors?  I never had a hard time with that on the routes.

Discerning which parks were what -- that was and still is annoying.  Zooming in on my phone briefly shows more boundaries for half a millisecond, and then it all becomes mush.  Blech.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on November 21, 2023, 08:40:56 AM
This is the first day I've gotten the new colours, for both my phone and computer. Overall I'm happy with the update, it's so much easier to see local roads than before (the previous white on light grey was always hard to see). However, I think a darker shade of grey for freeways would make them easier to distinguish from other highways.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 21, 2023, 12:39:14 PM
Quote from: Rothman on November 21, 2023, 06:07:21 AM
Quote from: jakeroot on November 20, 2023, 11:17:12 PM
Yeah, the roll-out has been completed for me, all of my devices are utilizing it now.

So far, I think the new colors are excellent. It's a big improvement from before, especially with the traffic overlay enabled, which no longer has conflicting colors.

There also seems to be new symbology that isn't just color. Parking lots (diagonal lines) and certain sections of park path (when zoomed in, you can see they are dotted) are things I notice right away.
Conflicting colors?  I never had a hard time with that on the routes.

Discerning which parks were what -- that was and still is annoying.  Zooming in on my phone briefly shows more boundaries for half a millisecond, and then it all becomes mush.  Blech.
I don't recall conflicting colors on the traffic either.  I don't know what it is, but the new traffic actually seems kinda cartoonish for some reason.

EDIT: As do the driving directions.
Title: Re: Google Maps just fucking SUCKS now
Post by: index on November 21, 2023, 04:19:04 PM
Quote from: epzik8 on November 20, 2023, 08:08:53 AM
Quote from: index on November 19, 2023, 02:10:54 AM
Not too big a fan of the new color update. It would be less so if they returned the differentiation between freeways and major surface roads. I also feel like it would pose accessibility issues for certain people due to the low contrast.

The wonders of AI...

I don't get it. What exactly do you mean
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on November 21, 2023, 10:04:57 PM
One nice thing is that when you zoom way in with aerial imagery enabled, it fades out the lines so that you can see the striping and the road surface condition. The old version didn't do that. Old Google Earth did, but that disappeared when they did a major rev a year or two ago. I hope it comes back in Google Earth, too.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on November 22, 2023, 12:22:13 AM
Quote from: vdeane on November 21, 2023, 12:39:14 PM
Quote from: Rothman on November 21, 2023, 06:07:21 AM
Quote from: jakeroot on November 20, 2023, 11:17:12 PM
Yeah, the roll-out has been completed for me, all of my devices are utilizing it now.

So far, I think the new colors are excellent. It's a big improvement from before, especially with the traffic overlay enabled, which no longer has conflicting colors.

There also seems to be new symbology that isn't just color. Parking lots (diagonal lines) and certain sections of park path (when zoomed in, you can see they are dotted) are things I notice right away.
Conflicting colors?  I never had a hard time with that on the routes.

Discerning which parks were what -- that was and still is annoying.  Zooming in on my phone briefly shows more boundaries for half a millisecond, and then it all becomes mush.  Blech.
I don't recall conflicting colors on the traffic either.  I don't know what it is, but the new traffic actually seems kinda cartoonish for some reason.

EDIT: As do the driving directions.

The orange traffic color (middle-level jam or something) conflicted with the yellow-orange arterial route color. The new blue/grey color scheme no longer shares any colors with the traffic legend.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hunty2022 on November 22, 2023, 08:52:19 AM
My Google maps app finally updated to the new colors. I did find a huge patch with the old colors, which disappeared when I moved away from it.

(https://i.postimg.cc/1tZkPDbz/IMG-6604.jpg)

I'm pretty sure I still have some old google maps tabs on my computer with the old colors.
Title: Re: Google Maps just fucking SUCKS now
Post by: seicer on November 22, 2023, 11:04:09 AM
Quote from: epzik8 on November 20, 2023, 08:08:53 AM
Quote from: index on November 19, 2023, 02:10:54 AM
Not too big a fan of the new color update. It would be less so if they returned the differentiation between freeways and major surface roads. I also feel like it would pose accessibility issues for certain people due to the low contrast.

The wonders of AI...

AI has nothing to do with the changing of the color scheme on Google Maps.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on November 23, 2023, 10:20:46 PM
So far, I mostly like the new colors on my phone, because in most places the lesser roads show up better against the background. That was always my biggest beef with not only Google, but Bing and MapQuest too: almost impossible to see the tiny roads. On a desktop or laptop, it's less an issue, because you're not trying to look at it while driving, with the light from the sun, vehicles, signals, or signage constantly shifting.

But, as others have noted, there's still the issue that there is no color-coding of the kinds of roads. Color paper maps usually used different colors for minor roads, divided non-freeways, freeways, and toll roads. However, the new traffic display seems to put the traffic colors right on top of the road, where the old map put them along the left and right edges so you could always see the underlying line color.
Title: Re: Google Maps just fucking SUCKS now
Post by: bzakharin on November 23, 2023, 10:57:42 PM
Did they have different colors for toll roads before? I don't seem to recall, but they're different now. This is only visible at higher zoom levels and sems pretty fine-grained. For example, at https://www.google.com/maps/@39.5807841,-74.4572356,17.71z?entry=ttu you can see the Northbound Garden State Parkway is marked as toll past exit 50, since that's the last exit before the toll barrier.
Title: Re: Google Maps just fucking SUCKS now
Post by: Roadgeekteen on November 26, 2023, 09:24:17 PM
The new google maps colors are so ass
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on November 27, 2023, 05:23:01 PM
I just spent a few days driving around the SF Bay Area, and was using the new Google Maps on my phone extensively. I think it's a definite improvement, especially when looking at it in a moving car, including at night when the phone screen is dimmed. I also think it could be improved more, but it's a step in the right direction.
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on November 28, 2023, 09:35:16 AM
 (https://i.imgur.com/79hNa8w.jpg)



Quote from: Hunty2022 on November 22, 2023, 08:52:19 AM
My Google maps app finally updated to the new colors. I did find a huge patch with the old colors, which disappeared when I moved away from it.

My Google Maps on my iPad has the opposite problem where there's a patch of the new colors surrounded by the old colors. However my phone has since updated fully to the new colors.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on November 28, 2023, 09:44:28 AM
Wait, how is 95 clear? This is current (tail end of rush hour), right?
Title: Re: Google Maps just fucking SUCKS now
Post by: Amaury on November 28, 2023, 07:16:27 PM
Does anyone know why Google Maps doesn't show the boundary lines for all communities? I thought maybe it only showed boundary lines for cities and towns, but not census-designated places and unincorporated communities. However, that's not the case, as it will show boundary lines for cities, towns, CDPs, and UICs, though in the case of the latter two, it's not all of them for some reason.

For example, Ronald, Washington, is a UIC and has a boundary line: https://maps.app.goo.gl/w9ahEs7Np2Wc4Bdd9 Dryden, Washington, is also a UIC, but has no boundary line: https://maps.app.goo.gl/i7VqUkPw9qMf2DyMA

Similarly, for example, Parker, Washington, is a CDP and has boundary line: https://maps.app.goo.gl/QhpPfpwTWaK1Dxz37 Donald, Washington, is also a CDP, but has no boundary line: https://maps.app.goo.gl/XqRzBnjZehuvuv4X6
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on November 30, 2023, 12:41:16 AM
I don't know the answer, but in poking around I found myself wishing I could hold Ctrl down while clicking town names to turn multiple boundaries on at the same time. Doesn't work that way, though. But in Google Earth, you simply select a layer to turn them all on.

I notice that Boston MA has a boundary, but some of the sections of it have their own boundaries, like Brighton and Allston.

Back to the "sucks now" topic: when I'm clicking these things, I see that the programmers insisted on making it zoom in to whatever I've selected. I wish they'd stop trying to be so "helpful".
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on November 30, 2023, 08:11:49 AM
Not all of the neighborhoods of Boston can have boundaries because they're not defined. Allston and Brighton have their own ZIP codes, defining their boundaries that way.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on November 30, 2023, 04:11:43 PM
Has anyone else noticed the distance tool isn't straight smooth? I don't remember seeing this issue before:
(https://i.imgur.com/sxq9kEE.png)

Even zooming in doesn't fix it:
(https://i.imgur.com/OZvFKGY.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on November 30, 2023, 04:15:47 PM
Quote from: Hunty2022 on November 22, 2023, 08:52:19 AM
My Google maps app finally updated to the new colors. I did find a huge patch with the old colors, which disappeared when I moved away from it.

I got a glimpse of the old colours while flying over western NY a few days ago. I checked today and it shows the new colours.

(https://i.imgur.com/e7LsWGtl.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: JayhawkCO on November 30, 2023, 04:36:00 PM
Quote from: 7/8 on November 30, 2023, 04:11:43 PM
Has anyone else noticed the distance tool isn't straight? I don't remember seeing this issue before:

Mine only has one kink in it. Guessing maybe it's trying to approximate a great circle?
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on November 30, 2023, 04:40:00 PM
Quote from: JayhawkCO on November 30, 2023, 04:36:00 PM
Quote from: 7/8 on November 30, 2023, 04:11:43 PM
Has anyone else noticed the distance tool isn't straight? I don't remember seeing this issue before:

Mine only has one kink in it. Guessing maybe it's trying to approximate a great circle?

Yes, I should've said "smooth", not "straight". It should be a great circle, but it used to not have noticeable kinks.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on November 30, 2023, 07:50:26 PM
Quote from: JayhawkCO on November 30, 2023, 04:36:00 PM
Quote from: 7/8 on November 30, 2023, 04:11:43 PM
Has anyone else noticed the distance tool isn't straight? I don't remember seeing this issue before:

Mine only has one kink in it. Guessing maybe it's trying to approximate a great circle?
Note that 7/8 is in globe view, so there should be no approximating - it should appear straight to us on the map.  This happens even outside of globe view - what used to be a nice round arc is now noticeably a series of lines.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on November 30, 2023, 09:45:44 PM
Quote from: 7/8 on November 30, 2023, 04:15:47 PM
Quote from: Hunty2022 on November 22, 2023, 08:52:19 AM
My Google maps app finally updated to the new colors. I did find a huge patch with the old colors, which disappeared when I moved away from it.

I got a glimpse of the old colours while flying over western NY a few days ago. I checked today and it shows the new colours.

(https://i.imgur.com/e7LsWGtl.jpg)

I expect that the new and old tiles have the same URL, and the old one happened to be in the browser's cache still.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on December 01, 2023, 01:13:35 AM
It seems they also use a yellow-ish color for highways when looking at satellite view.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on December 01, 2023, 01:15:34 AM
I get the new colors when I go to the website, but as soon as I zoom in or out it reverts to old colors.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on December 01, 2023, 10:19:06 PM
They have different tiles for different zoom levels, too, so that's understandable. Clear your browser cache, and I doubt you'll see any old colors any more.
Title: Re: Google Maps just fucking SUCKS now
Post by: CovalenceSTU on December 05, 2023, 02:11:06 PM
Right now I have the new colors, but the major roads turn yellow again if I switch to satellite view.


Does anyone else have a problem with edits simply not showing up? I twice tried fixing a road that was realigned 15 years ago and got the confirmation email both times, but when I go to my contributions it simply isn't there. I only have one edit (assigning OR-501 to the Alsea-Deadwood Highway) and it was rejected despite appearing on official documents and GSV.
Title: Re: Google Maps just fucking SUCKS now
Post by: Amaury on December 05, 2023, 10:48:59 PM
It is not possible to add custom colors to Google Maps? I did a search a couple weeks ago and saw something that said you go to edit map and do it there, but either it's wrong or it's outdated and it was removed.

I was wanting to make maps of my drives and highlight the drive there as one color and the drive back as another. I would like to do it as one map, but I can always just do two separate maps, one for the drive there and one from the drive back if this is not possible. Sometimes I come back a different way than go there.

For example, my drive to Thompson Falls, Montana, in October 2021 was:
There: https://maps.app.goo.gl/xHUDmMsDYtoztK2i9
Back: https://maps.app.goo.gl/mXsrnntZzdyGu2ns7

I can, of course, do it all as one, there's just no way for me to show which one is the trip there and which one is the trip back: https://maps.app.goo.gl/x3jexifkLZwukpWJ9
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on December 05, 2023, 11:09:22 PM
Route markers have disappeared, except when actively navigating a route on my phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: US 89 on December 05, 2023, 11:23:20 PM
Quote from: Rothman on December 05, 2023, 11:09:22 PM
Route markers have disappeared, except when actively navigating a route on my phone.

This happened to me once. Make sure your transit layer is off.
Title: Re: Google Maps just fucking SUCKS now
Post by: GCrites on December 09, 2023, 11:40:49 AM
I never really liked the old colors. Looked too much like salad.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on December 12, 2023, 08:04:55 PM
It's really slow to load, as well as to zoom in and out, since the new redesign. Text is occasionally garbled, which appears to be some mixture of text overlap when changing the zoom values. Everything is so...muddled green for half the US. Colors seem to work a little better in night mode.

The only improvement I've noticed is that if you just search for a singular route by name and/or number, it will try to highlight its entire length in blue. Kind of helpful for this hobby, and maybe helpful if one is looking for a road name, but without a specific address or building number to go with the road name.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on December 12, 2023, 10:15:23 PM
Quote from: formulanone on December 12, 2023, 08:04:55 PM
It's really slow to load, as well as to zoom in and out, since the new redesign. Text is occasionally garbled, which appears to be some mixture of text overlap when changing the zoom values. Everything is so...muddled green for half the US. Colors seem to work a little better in night mode.

The only improvement I've noticed is that if you just search for a singular route by name and/or number, it will try to highlight its entire length in blue. Kind of helpful for this hobby, and maybe helpful if one is looking for a road name, but without a specific address or building number to go with the road name.

I'm not seeing any of the problems in your first paragraph, and I'm not seeing the feature in your second paragraph, either in a browser or in the Google Maps app on my Pixel 3 XL. If I seach for a road, I see a pushpin at what looks like its exact midpoint. And this is post-redesign in both.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on December 13, 2023, 07:28:41 PM
Ever since the redesign, GSV hasn't been working for me. Whenever I try to drop Pegman on a road, he returns to his little square. I can still enter GSV by right-clicking the roads, but that doesn't work for the photospheres. All links to GSV still work.
Title: Re: Google Maps just fucking SUCKS now
Post by: formulanone on December 14, 2023, 05:22:47 PM
Quote from: pderocco on December 12, 2023, 10:15:23 PM
Quote from: formulanone on December 12, 2023, 08:04:55 PM
It's really slow to load, as well as to zoom in and out, since the new redesign. Text is occasionally garbled, which appears to be some mixture of text overlap when changing the zoom values. Everything is so...muddled green for half the US. Colors seem to work a little better in night mode.

The only improvement I've noticed is that if you just search for a singular route by name and/or number, it will try to highlight its entire length in blue. Kind of helpful for this hobby, and maybe helpful if one is looking for a road name, but without a specific address or building number to go with the road name.

I'm not seeing any of the problems in your first paragraph, and I'm not seeing the feature in your second paragraph, either in a browser or in the Google Maps app on my Pixel 3 XL. If I seach for a road, I see a pushpin at what looks like its exact midpoint. And this is post-redesign in both.

I'm using Chrome on my work laptop, which is hampered by 8GB (refresh coming soon). Zoom speed seems to have good days and bad days, wasn't sure if happening elsewhere; yet no other pages seem affected.

Seems to be a lot more fluid and no garbled text on my phone.
Title: Re: Google Maps just fucking SUCKS now
Post by: davewiecking on December 15, 2023, 10:14:30 AM
I officially hate how it's now a few extra steps to get into Street View on the iPad version. When it works at all.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hunty2022 on January 11, 2024, 10:37:48 PM
Google Maps turned US 211 in Page County, VA into US 221 for a few days. When I checked to see if it was still there just now, it was turned back into US 211.
Title: Re: Google Maps just fucking SUCKS now
Post by: Mr. Matté on January 13, 2024, 06:55:13 AM
More of a visual only thing, but when moving within Street View, after making the click/keystroke that would execute the location change, it seems in the past few days like there's a jump in the picture before the animation of going to the intended location. Really annoying if I'm doing multiple moves in a row.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on January 13, 2024, 03:10:13 PM
I actually have a positive thing to report: it is now possible to use the measure distance tool to get distances in miles without the length being over a mile now!  Somewhat.  It still defaults to feet if the length is less than a mile, but if you zoom out enough, the total length reported on the map will switch.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on February 07, 2024, 02:04:50 PM
For some reason, when I zoom in at Highway 5 and 6 in Hamilton, ON, two interchange ramps show up (which don't exist in real life). And as far as I know, there is no plan for these to be built (someone correct me if I'm wrong).
(https://i.imgur.com/kytVl4S.png)

Left image: https://www.google.ca/maps/@43.3128635,-79.9186477,16.77z?entry=ttu (https://www.google.ca/maps/@43.3128635,-79.9186477,16.77z?entry=ttu)
Right image: https://www.google.ca/maps/@43.3127016,-79.9185347,17.06z?entry=ttu (https://www.google.ca/maps/@43.3127016,-79.9185347,17.06z?entry=ttu)

Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on February 07, 2024, 10:40:37 PM
At least there's no Street View on them.

I see that they don't appear if you turn on aerial imagery. I suspect someone at Google was messing around with their editing tools, and accidentally updated the public database.
Title: Re: Google Maps just fucking SUCKS now
Post by: epzik8 on February 09, 2024, 06:45:23 PM
Quote from: 7/8 on February 07, 2024, 02:04:50 PM
For some reason, when I zoom in at Highway 5 and 6 in Hamilton, ON, two interchange ramps show up (which don't exist in real life). And as far as I know, there is no plan for these to be built (someone correct me if I'm wrong).
(https://i.imgur.com/kytVl4S.png)

Left image: https://www.google.ca/maps/@43.3128635,-79.9186477,16.77z?entry=ttu (https://www.google.ca/maps/@43.3128635,-79.9186477,16.77z?entry=ttu)
Right image: https://www.google.ca/maps/@43.3127016,-79.9185347,17.06z?entry=ttu (https://www.google.ca/maps/@43.3127016,-79.9185347,17.06z?entry=ttu)

Google Maps is definitely possessed by something at this point.
Title: Re: Google Maps just fucking SUCKS now
Post by: I-55 on February 14, 2024, 04:03:36 PM
I've seen new satellite imagery drop in several locations (notably I-69 in Martinsville) with the lowest dpi I've seen in the contiguous US. The image quality is similar to northern Alberta. That or the'ye layering images on top of each other
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 14, 2024, 07:17:51 PM
Quote from: I-55 on February 14, 2024, 04:03:36 PM
I've seen new satellite imagery drop in several locations (notably I-69 in Martinsville) with the lowest dpi I've seen in the contiguous US. The image quality is similar to northern Alberta. That or the'ye layering images on top of each other

We also got some new imagery here in Japan, though it's just the imagery Google Earth has had for some time now (though only accessible through the historical imagery slider).

Likewise, also not the best quality. Though I thought it was more of a localized issue, most satellite imagery here is not super high quality.
Title: Re: Google Maps just fucking SUCKS now
Post by: CovalenceSTU on February 14, 2024, 07:33:05 PM
Quote from: I-55 on February 14, 2024, 04:03:36 PM
I've seen new satellite imagery drop in several locations (notably I-69 in Martinsville) with the lowest dpi I've seen in the contiguous US. The image quality is similar to northern Alberta. That or the'ye layering images on top of each other
That is some abysmal quality, on Earth Pro the date keeps flipping between 10/1/2023 and 4/10/2013 but neither of those dates (or the imagery itself) exist in the historical slider, even when zoomed out.

I also noticed the the newest batch of quality imagery seems to have overwritten the last one when zoomed in, it happened in Astoria with 10/2018 showing 8/2023 imagery (thankful it finally updated though) and in your location with 9/2021 showing 9/2023.
Title: Re: Google Maps just fucking SUCKS now
Post by: Hunty2022 on February 14, 2024, 10:47:28 PM
Quote from: I-55 on February 14, 2024, 04:03:36 PM
I've seen new satellite imagery drop in several locations (notably I-69 in Martinsville) with the lowest dpi I've seen in the contiguous US. The image quality is similar to northern Alberta. That or the'ye layering images on top of each other

New satellite imagery has also appeared in part of Virginia, including my hometown of Ruckersville. I can finally see the new configuration of US 33 east of US 29 in satellite view.
Title: Re: Google Maps just fucking SUCKS now
Post by: 7/8 on February 16, 2024, 04:15:45 PM
Has anyone tried opening Google Maps incognito? Here's two screenshots (I'm using Firefox):
(https://i.imgur.com/kevGUSs.png)

The colours are the old ones, and the shields are cursed.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 16, 2024, 04:24:55 PM
Quote from: 7/8 on February 16, 2024, 04:15:45 PM
Has anyone tried opening Google Maps incognito? Here's two screenshots (I'm using Firefox):
(https://i.imgur.com/kevGUSs.png)

The colours are the old ones, and the shields are cursed.

I've been using it in Incognito mode (Edge) all day.  The colors are still the new ones, and the shields are not cursed.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on February 16, 2024, 05:41:02 PM
I think a lot of these problems have to do with stale data in the cache.

As to I-69 in Martinsville, it looks fine to me in both Maps and Earth. Not the absolute best imagery, but I can easily see all the lane markings. Earlier imagery in Earth is somewhat sharper until you go back to 8/2010. But the reason they make this slightly inferior imagery from 9/2023 the default is that it shows the new grade separated interchanges needed to bring this up to Interstate standards, while everything before that doesn't.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on February 16, 2024, 05:53:41 PM
By the way, have they signed I-69 through Indianapolis, or along I-465 east or west of the city? Google doesn't say.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on February 16, 2024, 06:01:22 PM
Quote from: pderocco on February 16, 2024, 05:53:41 PM
By the way, have they signed I-69 through Indianapolis, or along I-465 east or west of the city? Google doesn't say.
I-69 will be designated along I-465 east of the city (I'm not sure whether it will be signed), but that won't happen until the future interchange of I-465 & I-69 SB opens. Give it a couple years.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 16, 2024, 06:52:55 PM
Quote from: 7/8 on February 16, 2024, 04:15:45 PM
Has anyone tried opening Google Maps incognito? Here's two screenshots (I'm using Firefox):
(https://i.imgur.com/kevGUSs.png)

The colours are the old ones, and the shields are cursed.

I don't advise this unless you live somewhere that you speak the language, or have a VPN...

(https://live.staticflickr.com/65535/53533977975_686014bcbd_o.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on February 16, 2024, 07:16:50 PM
I just tried browsing Google Maps incognito (both .com and .ca) and it's normal. However, I'm using Chrome, so they've probably fine-tuned it. Probably solely a Firefox issue.

Funnily enough, Street View only works on Edge for me; still not Chrome.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 16, 2024, 07:18:14 PM
Looks normal on Safari.

Street View is also fine.
Title: Re: Google Maps just fucking SUCKS now
Post by: cjw2001 on February 16, 2024, 09:08:39 PM
Quote from: jlam on February 16, 2024, 06:01:22 PM
Quote from: pderocco on February 16, 2024, 05:53:41 PM
By the way, have they signed I-69 through Indianapolis, or along I-465 east or west of the city? Google doesn't say.
I-69 will be designated along I-465 east of the city (I'm not sure whether it will be signed), but that won't happen until the future interchange of I-465 & I-69 SB opens. Give it a couple years.
Target date for project completion is end of 2024.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on February 16, 2024, 10:59:57 PM
I use Google Maps almost exclusively in incognito (exception is if I want to leave a business review) and I've never had cursed shields.  I did use it to get the old map style while the transition was happening, but that hasn't worked in ages.  I do get the old style via API windows (like 511 sites), though.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on February 16, 2024, 11:18:16 PM
Quote from: cjw2001 on February 16, 2024, 09:08:39 PM

Quote from: jlam on February 16, 2024, 06:01:22 PM

Quote from: pderocco on February 16, 2024, 05:53:41 PM

By the way, have they signed I-69 through Indianapolis, or along I-465 east or west of the city? Google doesn't say.


I-69 will be designated along I-465 east of the city (I'm not sure whether it will be signed), but that won't happen until the future interchange of I-465 & I-69 SB opens. Give it a couple years.


Target date for project completion is end of 2024.


Right. I was basing that estimate on projects in NC. I forgot that Indiana actually wants to complete these projects.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 17, 2024, 12:28:45 AM
Quote from: jlam on February 16, 2024, 07:16:50 PM
I just tried browsing Google Maps incognito (both .com and .ca) and it's normal. However, I'm using Chrome, so they've probably fine-tuned it. Probably solely a Firefox issue.

Funnily enough, Street View only works on Edge for me; still not Chrome.

I cannot comment on the Street View issue (that's pretty bizarre) but I was using Firefox in my screenshot (notice it says "Private Browsing" and not "Incognito", the latter being Chrome-lingo) and did not have any issues.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on February 17, 2024, 12:55:38 AM
Only Pegman doesn't work. I can still enter GSV using the double-click "What's Here?" method, but that only works with Google-mandated imagery. The panorama shots, photo trails, and other user-submitted imagery don't do anything when I try entering it. I could switch to Edge for my Google Maps activity, but that doesn't sit right.
Title: Re: Google Maps just fucking SUCKS now
Post by: fwydriver405 on February 17, 2024, 10:06:03 PM
Quote from: 7/8 on February 16, 2024, 04:15:45 PM
Has anyone tried opening Google Maps incognito? Here's two screenshots (I'm using Firefox):
(https://i.imgur.com/kevGUSs.png)

The colours are the old ones, and the shields are cursed.


(https://i.ibb.co/cXHjNzL/Screenshot-2024-02-17-at-14-22-40-0800.png) (https://ibb.co/7N5qG74) (https://i.ibb.co/17fRryk/Screenshot-2024-02-17-at-19-01-35-0800.png) (https://ibb.co/LYz9xj3)

I'm getting the same thing with the "cursed" shields, but with the new colour scheme. Brave 1.61.120 on two Mac computers (2019 MBP 16" macOS 13.6.4 / Windows 11 23H2, and a 2018 Mac mini on macOS 14.3.1 / Windows 10 22H2), on both the ".com" and ".ca" domains.

Notice this happens when:
- Brave Shields are turned on, when signed in
- This happens in both normal mode (signed in) and incognito (signed out). It does not happen with Shields on when signed out.
- Happens on two out of my four Google accounts signed in (two personal, affected, and two school, unaffected)
- Doesn't happen on Firefox or Safari, also signed in on normal mode or signed out in Private Browsing
- Street View still works normally on all three browsers
- Cookies and cache were cleared on Brave on both computers, but it still persists after signing in.

Suspect it might be a domain Brave Shields is blocking, as the "cursed" shields problem goes away when I disable it, and/or as another user suggested, could be some stale data in the cache:

Quote from: pderocco on February 16, 2024, 05:41:02 PM
I think a lot of these problems have to do with stale data in the cache.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on February 18, 2024, 11:45:48 AM
I just pulled up Google Maps in Chrome (while logged in to my Google account) and the shields do look a little funky (just not as broken as in 7/8's and fwydriver405's examples). The fonts look a little big/displaced:

(https://i.postimg.cc/zDK1mwRf/Screenshot-2024-02-18-9-42-02-AM.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Molandfreak on February 27, 2024, 03:09:09 AM
Are shields not appearing at all for anyone else now?
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 27, 2024, 03:30:02 AM
Quote from: Molandfreak on February 27, 2024, 03:09:09 AM
Are shields not appearing at all for anyone else now?

No problems to report on my end.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 27, 2024, 06:47:04 AM
Quote from: Molandfreak on February 27, 2024, 03:09:09 AM
Are shields not appearing at all for anyone else now?
They only appear at specific zoom levels and I think that's gotten worse over the past couple of months.
Title: Re: Google Maps just fucking SUCKS now
Post by: fwydriver405 on February 27, 2024, 12:29:27 PM
Quote from: jlam on February 18, 2024, 11:45:48 AM
I just pulled up Google Maps in Chrome (while logged in to my Google account) and the shields do look a little funky (just not as broken as in 7/8's and fwydriver405's examples). The fonts look a little big/displaced:

Update on my end, I found out that turning off "Block Fingerprinting" or "Aggressively Block Fingerprinting" to "Allow Fingerprinting" on Brave Shields seems to makes the cursed shields go away... wonder if blocking fingerprinting breaks some parts of Google Maps functionality (some people also had smooth zoom issues too from what I read (https://github.com/brave/brave-browser/issues/28938)).
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on February 27, 2024, 03:11:24 PM
 (https://i.imgur.com/HdRkQFg.jpeg)

Is there any reason why Street View isn't available on the Verrazano Bridge in NYC? This is on iOS
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on February 27, 2024, 03:14:51 PM
Quote from: BlueOutback7 on February 27, 2024, 03:11:24 PM
Is there any reason why Street View isn't available on the Verrazano Bridge in NYC? This is on iOS

I believe it's the same reason as the GWB: security.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 27, 2024, 03:26:33 PM
Quote from: BlueOutback7 on February 27, 2024, 03:11:24 PM
Is there any reason why Street View isn't available on the Verrazano Bridge in NYC? This is on iOS

Here's your thread:  https://www.aaroads.com/forum/index.php?topic=2753.0

Or this one:  https://misc.transport.road.narkive.com/SPicR2JG/verrazano-narrows-bridge-no-photography
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on February 27, 2024, 04:49:50 PM
Quote from: kphoger on February 27, 2024, 03:26:33 PM
Quote from: BlueOutback7 on February 27, 2024, 03:11:24 PM
Is there any reason why Street View isn't available on the Verrazano Bridge in NYC? This is on iOS

Here's your thread:  https://www.aaroads.com/forum/index.php?topic=2753.0

Or this one:  https://misc.transport.road.narkive.com/SPicR2JG/verrazano-narrows-bridge-no-photography

Oh God. The pooing is cool guy...
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on February 27, 2024, 05:23:54 PM
Quote from: kphoger on February 27, 2024, 03:26:33 PM
Here's your thread:  https://www.aaroads.com/forum/index.php?topic=2753.0

Quote from: rickmastfan67 on April 29, 2010, 08:22:51 PM
And here's a shot that you wouldn't be able to get normally. :)
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fimg.photobucket.com%2Falbums%2Fv645%2Frickmastfan67%2FInterstates%2FPA%2FPA-576%2FImg_0869s.jpg&hash=b8674149e5253b1986e577b0ba72d4622772ecf5)

lmfao
Thanks, Photobucket.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on February 27, 2024, 07:00:07 PM
Quote from: jlam on February 27, 2024, 03:14:51 PM
Quote from: BlueOutback7 on February 27, 2024, 03:11:24 PM
Is there any reason why Street View isn't available on the Verrazano Bridge in NYC? This is on iOS

I believe it's the same reason as the GWB: security.
More like paranoia.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on February 27, 2024, 10:36:36 PM
Quote from: LilianaUwU on February 27, 2024, 07:00:07 PM
Quote from: jlam on February 27, 2024, 03:14:51 PM
Quote from: BlueOutback7 on February 27, 2024, 03:11:24 PM
Is there any reason why Street View isn't available on the Verrazano Bridge in NYC? This is on iOS

I believe it's the same reason as the GWB: security.
More like paranoia.
As a co-worker of mine said today, "We must panic."
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 28, 2024, 09:54:06 AM
Quote from: SEWIGuy on February 27, 2024, 04:49:50 PM
Oh God. The pooing is cool guy...

OK, set me straight here.  I thought |NE2| started the 'pooing is cool' thing.  Am I wrong about that?
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on February 28, 2024, 10:18:24 AM
Quote from: kphoger on February 28, 2024, 09:54:06 AM
Quote from: SEWIGuy on February 27, 2024, 04:49:50 PM
Oh God. The pooing is cool guy...

OK, set me straight here.  I thought |NE2| started the 'pooing is cool' thing.  Am I wrong about that?


On MTR, its was that Tim dude from Cincinnati.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 28, 2024, 10:20:39 AM
Quote from: SEWIGuy on February 28, 2024, 10:18:24 AM

Quote from: kphoger on February 28, 2024, 09:54:06 AM

Quote from: SEWIGuy on February 27, 2024, 04:49:50 PM
Oh God. The pooing is cool guy...

OK, set me straight here.  I thought |NE2| started the 'pooing is cool' thing.  Am I wrong about that?

On MTR, its was that Tim dude from Cincinnati.

Thanks!  I have been schooled.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 28, 2024, 11:36:33 AM
Quote from: SEWIGuy on February 28, 2024, 10:18:24 AM
Quote from: kphoger on February 28, 2024, 09:54:06 AM
Quote from: SEWIGuy on February 27, 2024, 04:49:50 PM
Oh God. The pooing is cool guy...

OK, set me straight here.  I thought |NE2| started the 'pooing is cool' thing.  Am I wrong about that?


On MTR, its was that Tim dude from Cincinnati.

That Tim dude is on the forum, as well, you know...
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on February 28, 2024, 12:03:37 PM
Quote from: Scott5114 on February 28, 2024, 11:36:33 AM
Quote from: SEWIGuy on February 28, 2024, 10:18:24 AM
Quote from: kphoger on February 28, 2024, 09:54:06 AM
Quote from: SEWIGuy on February 27, 2024, 04:49:50 PM
Oh God. The pooing is cool guy...

OK, set me straight here.  I thought |NE2| started the 'pooing is cool' thing.  Am I wrong about that?


On MTR, its was that Tim dude from Cincinnati.

That Tim dude is on the forum, as well, you know...

Yeah, I recall seeing him a couple of times. He's less ubiquitous here.
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 28, 2024, 12:07:11 PM
Somehow I don't know who it is, and it seems like I'm the only one who doesn't know. I've always thought it to be the user currently on the Kentucky side of the state line, but I might be wrong.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 28, 2024, 12:12:18 PM
Quote from: 1 on February 28, 2024, 12:07:11 PM
Somehow I don't know who it is, and it seems like I'm the only one who doesn't know. I've always thought it to be the user currently on the Kentucky side of the state line, but I might be wrong.

Does this help?

(https://i.imgur.com/6hRMgBu.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 28, 2024, 12:13:58 PM
I've always heard the mtr user as Tom from Ohio, though. Tim isn't Tom, and Kentucky isn't Ohio.
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on February 28, 2024, 12:14:50 PM
Quote from: 1 on February 28, 2024, 12:07:11 PM
Somehow I don't know who it is, and it seems like I'm the only one who doesn't know. I've always thought it to be the user currently on the Kentucky side of the state line, but I might be wrong.

No you are correct. Greater Cincy, but on the Kentucky side.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 28, 2024, 12:24:02 PM
Tim Brown, a.k.a. bandit957

(https://i.imgur.com/cHMqvHh.jpg)
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on February 28, 2024, 12:33:58 PM
So are Tim Brown and Tom from Ohio the same person or not?
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 28, 2024, 12:46:21 PM
Quote from: 1 on February 28, 2024, 12:33:58 PM
So are Tim Brown and Tom from Ohio the same person or not?

I don't know the answer to that, but I doubt it.  I was never on m/t/r.  A couple of people on here do know, however.

For what it's worth, Daniel Moraseski "outed himself" on here (https://www.aaroads.com/forum/index.php?topic=14965.msg2049049#msg2049049) as TFO, but I lean toward not believing him.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 28, 2024, 02:45:16 PM
Tim and Tom are different people.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on February 29, 2024, 10:48:22 AM
Quote from: SEWIGuy on February 27, 2024, 04:49:50 PM
Oh God. The pooing is cool guy...

There's a book about him.

(https://i.imgur.com/BoEhmUk.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on February 29, 2024, 06:22:22 PM
Mr Brown writing about poo is oddly humorous.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on February 29, 2024, 07:35:24 PM
Quote from: jakeroot on February 29, 2024, 06:22:22 PM
Mr Brown writing about poo is oddly humorous.

You might even say it bips.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheHighwayMan3561 on March 01, 2024, 05:42:10 PM
Quote from: 1 on February 28, 2024, 12:33:58 PM
So are Tim Brown and Tom from Ohio the same person or not?

I know who Tom from Ohio is, but will not reveal it (other than that he is also a long-time member you will know).
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on March 01, 2024, 06:29:44 PM
Wow...  so...  it's been interesting digging through old m.t.r. threads.  I wasn't around during the m.t.r. days, so maybe I'm the only one who didn't know this:  NE2 went to MIT?
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 01, 2024, 06:43:13 PM
Quote from: kphoger on March 01, 2024, 06:29:44 PM
Wow...  so...  it's been interesting digging through old m.t.r. threads.  I wasn't around during the m.t.r. days, so maybe I'm the only one who didn't know this:  NE2 went to MIT?
Don't believe everything you read.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on March 01, 2024, 06:52:50 PM
Quote from: Rothman on March 01, 2024, 06:43:13 PM

Quote from: kphoger on March 01, 2024, 06:29:44 PM
Wow...  so...  it's been interesting digging through old m.t.r. threads.  I wasn't around during the m.t.r. days, so maybe I'm the only one who didn't know this:  NE2 went to MIT?

Don't believe everything you read.

Seems legit.  I'm seeing both defunct and restricted links to webpages with his name on the mit.edu site, the New York Times citing him as a student at MIT, etc.
Title: Re: Google Maps just fucking SUCKS now
Post by: MATraveler128 on March 04, 2024, 02:07:21 PM
I hate that Google had to put those square ads on maps. I get that it's Google and they thrive off of ads, but some places I can't even write reviews on if there's an ad on them. Like I tried to write a review on a local Wendy's but it had an ad on the site with no option to review it because of said ad.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.
Title: Re: Google Maps just fucking SUCKS now
Post by: LilianaUwU on March 04, 2024, 04:37:00 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.
Meanwhile, dead end streets in California get two cars at the same time.
Title: Re: Google Maps just fucking SUCKS now
Post by: TheHighwayMan3561 on March 04, 2024, 04:42:06 PM
Quote from: LilianaUwU on March 04, 2024, 04:37:00 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.
Meanwhile, dead end streets in California get two cars at the same time.

With Google based in California that probably makes more sense for something dumb like that to happen.
Title: Re: Google Maps just fucking SUCKS now
Post by: JayhawkCO on March 04, 2024, 04:55:34 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

You know there are still state highways in other places with zero coverage, including 2008 coverage, yeah? I've been on that stretch you've linked to. There aren't many cars period, much less GSV cars.
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on March 04, 2024, 04:57:13 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

Is it any different?
Title: Re: Google Maps just fucking SUCKS now
Post by: JayhawkCO on March 04, 2024, 05:00:14 PM
Quote from: SEWIGuy on March 04, 2024, 04:57:13 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

Is it any different?

Less pixelated.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 04, 2024, 05:20:35 PM
I hate the new blue.  Mob-rule still uses the old colors with the old zoom levels for labels.  The old way is much easier to read.
Title: Re: Google Maps just fucking SUCKS now
Post by: epzik8 on March 04, 2024, 05:20:41 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

I was going to say the same about US 50 and US 219 in western Maryland (in a tourist area, while not heavily populated) as for a long time they only had imagery from 2008. I just checked and they finally went back in 2022 and 2023. Nonetheless, 14 years between GSV drive-throughs isn't very forgivable if you ask me.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on March 04, 2024, 05:26:53 PM
Quote from: JayhawkCO on March 04, 2024, 04:55:34 PM

Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

You know there are still state highways in other places with zero coverage, including 2008 coverage, yeah? I've been on that stretch you've linked to. There aren't many cars period, much less GSV cars.

Ha!  I grew up one county away, and even I haven't been on that stretch of road.
Title: Re: Google Maps just fucking SUCKS now
Post by: roadman65 on March 04, 2024, 05:30:10 PM
Quote from: SEWIGuy on March 04, 2024, 04:57:13 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

Is it any different?

The quality of the images are. Not the land, as unlike Florida will not get developed here anytime soon.
Title: Re: Google Maps just fucking SUCKS now
Post by: JayhawkCO on March 04, 2024, 05:41:47 PM
Quote from: kphoger on March 04, 2024, 05:26:53 PM
Quote from: JayhawkCO on March 04, 2024, 04:55:34 PM

Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

You know there are still state highways in other places with zero coverage, including 2008 coverage, yeah? I've been on that stretch you've linked to. There aren't many cars period, much less GSV cars.

Ha!  I grew up one county away, and even I haven't been on that stretch of road.

I was clinching all of Colorado's mileage, so obviously I had to cross the Kansas border a couple of times to make it official, and K-27 is so close to the border that I'd use that to double back instead of just turning around at the border.
Title: Re: Google Maps just fucking SUCKS now
Post by: jlam on March 04, 2024, 05:46:47 PM
Quote from: Rothman on March 04, 2024, 05:20:35 PM
I hate the new blue.  Mob-rule still uses the old colors with the old zoom levels for labels.  The old way is much easier to read.
Not a problem for me if I try to evade it hard enough. My Apple products still use the old colors.




Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.

That segment is literally the only road in Kansas I've been on (though it was a clinch-motivated trip)
Title: Re: Google Maps just fucking SUCKS now
Post by: kkt on March 04, 2024, 07:06:55 PM
Quote from: TheHighwayMan394 on March 04, 2024, 04:42:06 PM
Quote from: LilianaUwU on March 04, 2024, 04:37:00 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.
Meanwhile, dead end streets in California get two cars at the same time.

With Google based in California that probably makes more sense for something dumb like that to happen.

Probably training a new camera car driver.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on March 04, 2024, 07:42:38 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.
That's happened in much more scenic locations. When they began Street View, it looks like their sent their cars, with their crappy cameras, to capture lots of America the Beautiful. Ever since then, given a choice between going back for better imagery and going someplace new, they opt for the latter.
Title: Re: Google Maps just fucking SUCKS now
Post by: bicyclehazard on March 04, 2024, 07:49:59 PM
I have been using openstreetmap.org It lets you save a map.
Title: Re: Google Maps just fucking SUCKS now
Post by: Max Rockatansky on March 04, 2024, 07:51:20 PM
Quote from: bicyclehazard on March 04, 2024, 07:49:59 PM
I have been using openstreetmap.org It lets you save a map.

As if I ever needed additional selling on never using openstreetmap.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on March 04, 2024, 08:29:40 PM
Quote from: Max Rockatansky on March 04, 2024, 07:51:20 PM
Quote from: bicyclehazard on March 04, 2024, 07:49:59 PM
I have been using openstreetmap.org It lets you save a map.

As if I ever needed additional selling on never using openstreetmap.
I wish there was a way to get OSM cartography with the Google Maps driving directions, street view, and business info (photos/reviews/etc.).  The Google Maps cartography has been annoying me lately; the only thing I like about it over OSM is that it shades where businesses of consumer interest are, making it easier to find food and the like without resorting to search.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on March 04, 2024, 09:06:36 PM
Quote from: bicyclehazard on March 04, 2024, 07:49:59 PM
It lets you save a map.

What does this mean?  Is this meaningfully different than using Google My Maps?
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on March 05, 2024, 08:47:35 AM
Quote from: pderocco on March 04, 2024, 07:42:38 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
https://maps.app.goo.gl/AChMSVGzzKT3VA1u7
You mean no one's recaptured this part of K-27 since 08. 16 years and no drive by. Come on.
That's happened in much more scenic locations. When they began Street View, it looks like their sent their cars, with their crappy cameras, to capture lots of America the Beautiful. Ever since then, given a choice between going back for better imagery and going someplace new, they opt for the latter.

Right. They aren't going to head back to places that rarely have changed. The neighborhood I once lived in hasn't seen an update since 2012. Why would they go back there?

Yet we have people here claim this "is not very forgivable." I mean...its a free service.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on March 05, 2024, 05:41:30 PM
Quote from: SEWIGuy on March 05, 2024, 08:47:35 AM
Quote from: pderocco on March 04, 2024, 07:42:38 PM
Quote from: roadman65 on March 04, 2024, 04:33:55 PM
That's happened in much more scenic locations. When they began Street View, it looks like their sent their cars, with their crappy cameras, to capture lots of America the Beautiful. Ever since then, given a choice between going back for better imagery and going someplace new, they opt for the latter.

Right. They aren't going to head back to places that rarely have changed. The neighborhood I once lived in hasn't seen an update since 2012. Why would they go back there?
The 2012 imagery is decent quality. The 2007-2009 imagery is so bad you can barely make out the speed limit signs; forget about reading street signs, house numbers, business names, or seeing the road surface quality. It's practically useless imagery. So if it's in a particularly scenic area which many people are likely to want to view, they should prioritize updating it.
Title: Re: Google Maps just fucking SUCKS now
Post by: SEWIGuy on March 05, 2024, 07:09:35 PM
Why do you think people use street view? My guess...idle curiosity...to get familiar with the area you are traveling to...to see where their family, friends and co-workers live...

None of these really apply to an out of the way rural highway in Kansas.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on March 05, 2024, 08:23:02 PM
Quote from: SEWIGuy on March 05, 2024, 07:09:35 PM
Why do you think people use street view? My guess...idle curiosity...to get familiar with the area you are traveling to...to see where their family, friends and co-workers live...

None of these really apply to an out of the way rural highway in Kansas.

Then why did they bother to send the GSV car there in the first place, even for crappy imagery?

As to updating that imagery, I'm talking about "particularly scenic areas". I spend quite a bit of time using GSV to see what the roads and views are like in rural places that I might like to explore, and then I go and explore them. But I live in the Southwest, which has more than its share of spectacular scenery, much of which I can visit on a weekend, some even on a day trip. I suspect many people use GSV in that way. But the really old imagery isn't useful for that, and as far as I can see, isn't useful for anything much.
Title: Re: Google Maps just fucking SUCKS now
Post by: kphoger on March 06, 2024, 09:51:26 AM
Quote from: pderocco on March 05, 2024, 08:23:02 PM
As to updating that imagery, I'm talking about "particularly scenic areas". I spend quite a bit of time using GSV to see what the roads and views are like in rural places that I might like to explore ... But the really old imagery isn't useful for that ...

How is it not useful for that?  I can get a good feel for the scenery from that '08 imagery.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on March 06, 2024, 05:47:52 PM
Well, you have to do a lot of mental interpolation. But when you look at a beautiful view in the 2007 imagery, it looks ugly as sin, and unless you do a lot of compensation, you wouldn't want to go there based on what you saw.

There is a more recent form of GSV imagery that I've seen in various places, which comes from really low-quality cameras driven around by other companies. For instance, in my erstwhile hometown Provincetown MA, there's a lot of it, although they recently replaced it with newer good imagery on the major Commercial St. The back streets are still ugly, though. This was captured by a company called PTown Hacks, an LGBT travel guide company:

https://maps.app.goo.gl/LZMhR3txm2F3neUC6 (https://maps.app.goo.gl/LZMhR3txm2F3neUC6)

[Redacted what appears to have been a joke that didn't go over well with the audience. -S.]
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on March 06, 2024, 06:39:46 PM
TBF, the 3rd Party street view imagery is often done via 360° cameras, the quality of which isn't the best on lower-end & cheaper ones.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 06, 2024, 09:33:26 PM
Quote from: freebrickproductions on March 06, 2024, 06:39:46 PM
TBF, the 3rd Party street view imagery is often done via 360° cameras, the quality of which isn't the best on lower-end & cheaper ones.
And yet, Google accepts it.
Title: Re: Google Maps just fucking SUCKS now
Post by: seicer on March 06, 2024, 10:14:59 PM
I wonder if the older imagery is being deliberately degraded to save on storage space as newer imagery is added. I distinctly remember seeing clear images that date to 2008 just a few years back, but now those images are mostly illegible.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 06, 2024, 10:33:12 PM
Quote from: seicer on March 06, 2024, 10:14:59 PM
I wonder if the older imagery is being deliberately degraded to save on storage space as newer imagery is added. I distinctly remember seeing clear images that date to 2008 just a few years back, but now those images are mostly illegible.
I dunno.  Looking at my older digital photos is eye-opening to see how much progress has been made.
Title: Re: Google Maps just fucking SUCKS now
Post by: jakeroot on March 06, 2024, 10:48:11 PM
I highly doubt Google is short on storage space.
Title: Re: Google Maps just fucking SUCKS now
Post by: Scott5114 on March 06, 2024, 10:59:22 PM
Quote from: seicer on March 06, 2024, 10:14:59 PM
I wonder if the older imagery is being deliberately degraded to save on storage space as newer imagery is added. I distinctly remember seeing clear images that date to 2008 just a few years back, but now those images are mostly illegible.

The 2008 imagery was mostly done with the potato-quality cameras, but there were a few areas where they were testing clearer ones at that time.
Title: Re: Google Maps just fucking SUCKS now
Post by: freebrickproductions on March 06, 2024, 11:04:24 PM
Quote from: Scott5114 on March 06, 2024, 10:59:22 PM
Quote from: seicer on March 06, 2024, 10:14:59 PM
I wonder if the older imagery is being deliberately degraded to save on storage space as newer imagery is added. I distinctly remember seeing clear images that date to 2008 just a few years back, but now those images are mostly illegible.

The 2008 imagery was mostly done with the potato-quality cameras, but there were a few areas where they were testing clearer ones at that time.

I suspect it's also that screens are much larger now, especially in terms of the number of pixels they hold, and it appears that street view blows-up the images to fit the screen.
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on March 06, 2024, 11:23:58 PM
Perhaps storage space can be an issue in the camera, but I doubt on the servers. But I suppose in a car, it could be connected to a box of M.2 drives.

When I see lousy imagery of a nice place, I find myself wishing they'd send me to photograph it. Personally, I'd love to drive a GSV car around in the mountains, or in quaint towns, or charming cities, or anyplace beautiful, as long as they paid all my expenses. That would be like a free vacation. But I suspect there is a huge surplus of people who'd like to do that. Driving around grimy industrial areas, boring suburbs, slums, endless farm roads in the Great Plains, not so much.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 07, 2024, 01:04:14 PM
Quote from: pderocco on March 06, 2024, 11:23:58 PM
Perhaps storage space can be an issue in the camera, but I doubt on the servers. But I suppose in a car, it could be connected to a box of M.2 drives.

When I see lousy imagery of a nice place, I find myself wishing they'd send me to photograph it. Personally, I'd love to drive a GSV car around in the mountains, or in quaint towns, or charming cities, or anyplace beautiful, as long as they paid all my expenses. That would be like a free vacation. But I suspect there is a huge surplus of people who'd like to do that. Driving around grimy industrial areas, boring suburbs, slums, endless farm roads in the Great Plains, not so much.

"I'll drive your camera car, but only where others want to, too, rather than where you decide to send me."
Title: Re: Google Maps just fucking SUCKS now
Post by: pderocco on March 07, 2024, 10:58:00 PM
Quote from: Rothman on March 07, 2024, 01:04:14 PM
Quote from: pderocco on March 06, 2024, 11:23:58 PM
Perhaps storage space can be an issue in the camera, but I doubt on the servers. But I suppose in a car, it could be connected to a box of M.2 drives.

When I see lousy imagery of a nice place, I find myself wishing they'd send me to photograph it. Personally, I'd love to drive a GSV car around in the mountains, or in quaint towns, or charming cities, or anyplace beautiful, as long as they paid all my expenses. That would be like a free vacation. But I suspect there is a huge surplus of people who'd like to do that. Driving around grimy industrial areas, boring suburbs, slums, endless farm roads in the Great Plains, not so much.

"I'll drive your camera car, but only where others want to, too, rather than where you decide to send me."

For me, it's just an idle fantasy. I'm not exactly looking for a job.
Title: Re: Google Maps just fucking SUCKS now
Post by: CtrlAltDel on March 09, 2024, 12:56:52 AM
An interesting thing happened to me just a moment ago, when the distances and endpoints remained on the screen after I cleared a measurement.

(https://i.imgur.com/2NcYxNN.png)
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 09, 2024, 03:04:15 PM
Quote from: CtrlAltDel on March 09, 2024, 12:56:52 AM
An interesting thing happened to me just a moment ago, when the distances and endpoints remained on the screen after I cleared a measurement.

(https://i.imgur.com/2NcYxNN.png)
That happened to me yesterday.
Title: Re: Google Maps just fucking SUCKS now
Post by: vdeane on March 09, 2024, 03:05:10 PM
I think Google just put in place some anti-adblocking tech on Google Maps.  I've noticed the past couple days I've had to downgrade my browser's blocking to "block trackers" from "block trackers and ads" in order to get business information to display when I click on one; the column was all black if I didn't.
Title: Re: Google Maps just fucking SUCKS now
Post by: Rothman on March 12, 2024, 09:18:24 AM
Google says to get to Orient Point on Long Island from central NY, one should take the Cross Sound Ferry to save five minutes over taking a NYC bridge.

Something tells me it isn't taking the ferry schedule into account correctly...
Title: Re: Google Maps just fucking SUCKS now
Post by: hotdogPi on March 15, 2024, 09:03:27 AM
I've noticed this for a few weeks now.

If the Transit layer is on, the measure tool won't allow dragging or removing points; attempting to do either creates a new point.
Title: Re: Google Maps just fucking SUCKS now
Post by: bm7 on March 15, 2024, 01:43:33 PM
Quote from: 1 on March 15, 2024, 09:03:27 AM
I've noticed this for a few weeks now.

If the Transit layer is on, the measure tool won't allow dragging or removing points; attempting to do either creates a new point.

This has been happening to me too, but I never use the transit layer.