Live data from Hacker News

Google Maps Hacks

simonweckert.com

281–290 of 397 posts

Re: Google Maps Hacks

#281

Earlier quoted context omitted.

How did you fix that? I’ve been wondering how google and the others differentiate between cars on the free vs express lanes.

That's quite easy and there are different ways to do it, the first that comes to mind is using location history.

In audio processing you deal with spikes using one or two averaging filters with different time constants for rise/fall.

You can also do it with a PID approach

Re: Google Maps Hacks

#282

Earlier quoted context omitted.

This is my common complaint with Waze and most driving apps - they optimize for "least time," not "least anguish". I would almost always prefer to spend an extra 5 minutes on my "normal" route (that I have on auto-pilot) instead of saving that 5 minutes by taking confusingly-named side-streets with lots of left turns onto other busy side-streets. I don't know if Apple Maps really gets this any better to be honest.

> with Waze and most driving apps - they optimize for "least time," not "least anguish" It's my impression that Google Maps does the latter; Waze is known for taking wild routes that are nominally faster. I'm not sure that I see a basis for complaint, as they're just offering a choice of different route objectives to optimize for (I know people who explicitly use Waze because they prefer its aggressive optimization t…

I travel to new cities often and usually rent a car from the airport. In most cities around the world, there is dedicated signage pointing out the access to the airport on every major approach it. I would say half the time Google wants to take me on a different route on some back road that is not meant to be the public access to the airport, which creates the extra mental overhead of having to ignore the gigantic "AIRPORT - EXIT HERE" signs all along the way. It even does this at SFO, presumably an airport that the very people who work on Google Maps use, where it always wants to exit the interstate one exit before the sign for the airport and take city streets instead. The worst experience I've had of this was in Denver, where it directed me onto a country road that circled the airport property and then ended at a temporary road closure. That is, Google's "5 seconds faster than the main, signed route" optimization wasn't even an actual route to the airport!

Re: Google Maps Hacks

#283

Earlier quoted context omitted.

This is my common complaint with Waze and most driving apps - they optimize for "least time," not "least anguish". I would almost always prefer to spend an extra 5 minutes on my "normal" route (that I have on auto-pilot) instead of saving that 5 minutes by taking confusingly-named side-streets with lots of left turns onto other busy side-streets. I don't know if Apple Maps really gets this any better to be honest.

Sorry for the minor comment but I noticed this part: "side-streets with lots of left turns onto other busy side-streets" Now I live in Europe, presumably you live in the US (sorry if that's wrong). Is there any particular difficulties with doing left turns compared to right turns where you live?

Roads can be very wide in the US, it is not uncommon for cities to have 6 or 8 lane roads at-grade (i.e. not expressways). So when turning left, one must turn across 3 or 4 lanes of oncoming traffic, instead of just one as when turning right.

Re: Google Maps Hacks

#284

Earlier quoted context omitted.

I wish it had a “no left turns” feature like they have for avoiding tolls.

I wish cities had roundabouts instead of intersections, so that would not be a problem :)

I hate roundabouts. I live in France, and we have them everywhere. They're a huge clusterfuck that does not win any time, and when misused can be a lot more dangerous than a properly planned intersection. Of all the accidents I've driven past on my daily drives, all of them happened on roundabouts. I hate them.

Re: Google Maps Hacks

#285

An interesting "red but no traffic" phenomenon is in Iceland, with roads which are next to scenery viewing points. The roads are mostly empty in this country, but everyone must've slowed down when they saw the breathtaking scenery, and would pull into the viewing point's parking spot to stop and take pictures. On Google Maps these areas were marked red. On another navigation related topic; I was using Waze in a high-…

This happens on NY 73, which is a road in the Adirondack High Peaks region between the highway and Lake Placid. It’s legit — even though cars are parked, you still need to slow down! I usually avoid Google maps for traveling in areas that I don’t know. It takes you off on stupid routes that save marginal time (if any) too much. Waze is good for interstate travel, but IMO Apple is better for giving you the “right”, lo…

So a theory I've had for a bit now... Google maps doesn't optimize for ease of travel, or time, or anything like that - it optimizes for engagement, like every other Google product. And how would you do that with a maps product? By making routes too complicated to memorize, too specialized (back streets, etc) to generalize, and then changing things up often to prevent a route from becoming second nature anyways.

Which feels like a lot of what people complain Google Maps does...

Re: Google Maps Hacks

#286
post #112

Earlier quoted context omitted.

I don't know what the tipping point is, but it'd probably take more than one. I've commuted through backed up/stopped/solid red sections on a motorcycle where I just get to lane-split and cruise through, and it'd still stay red.

I think Google uses phone sensors to tell motorbikes apart form cars. Pretty simple tech: cars don't lean. Which makes it all the more infuriating that Google Maps still has huge flaws when it comes to motorbike navigation.

> I think Google uses phone sensors to tell motorbikes apart form cars

While they could, I doubt they do... do you have evidence of this?

Re: Google Maps Hacks

#287

An interesting "red but no traffic" phenomenon is in Iceland, with roads which are next to scenery viewing points. The roads are mostly empty in this country, but everyone must've slowed down when they saw the breathtaking scenery, and would pull into the viewing point's parking spot to stop and take pictures. On Google Maps these areas were marked red. On another navigation related topic; I was using Waze in a high-…

There is a popular road in a relatively rural part of the SF Bay area for bicycling and on the weekends it appears to have traffic due to the slower speed of the numerous cyclists. There isn't actually more traffic. Google then sends cars on a winding narrow hilly alternate route.

Re: Google Maps Hacks

#288

A similar problem happens during unusual big snowfalls in the country or in the mountains. The primary roads turn red because the cars are going really slow cz there is 50cm of snow. So maps redirects you to secondary roads, where there is nobody and even more snow.

I like zooming out on google maps and you can see the red areas of the freeways shows where its snowing and matches the weather map.

Re: Google Maps Hacks

#289
Geez, those second-hand phones look nicer than what I am using now :(

edit: And why wouldn't a bus with 50 people all with smartphones have the same effect?

Post reply on HN