it's not a bug, it's a feature.
Google Maps Hacks
41–50 of 397 posts
Re: Google Maps Hacks
#42Wow, I never actually stopped to think about the way Google determines traffic but it seems so obvious now. This is a very simple but cool trick, I'd expect to see something like this in an action movie where people need to reroute an important car to a particular street. Anyone have any idea how often this data is updated? So if the guy runs through a street with a cart and it turns red, when will it show up as clea…
I guess an important piece (conveniently left out of this story) is that it does not work if there are other cars on the road, as these cars quickly invalidate the data coming from the slow cart.
But wouldn't that other car be classified as error?
Re: Google Maps Hacks
#43A 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.
Re: Google Maps Hacks
#44Cool trick - I wonder how much of the cell tower's capacity he is hogging too?
Re: Google Maps Hacks
#45I expect Google to start weighing user data by some notion of account credibility. It’s a problem that extends beyond maps.
They can start with reviews, where this is much more important and commonly misused thing - and they still don't care. At all.
So, nope :).
Re: Google Maps Hacks
#46Earlier quoted context omitted.
Pretty easy to train some ML network to differentiate between transport modes, assuming the device has a accelerometer / gyroscope / whatever.
Not really that easy with just IMU sensors, I’d assume ? I did one project in school (albeit a simple SVM based model) to classify walking vs running (and so on) and ambiguity was still there. Stationary vs. Walking was easy to draw a hyper plane in between, not Running. I still find it a difficult problem to get into, after 5 years. Perhaps ANN models might work better? Although my heart is still at Hidden MM states…
Do you have the code for your classification project? It would be great to see it on github or something.
Re: Google Maps Hacks
#47This is a hack in an older, juvenile sense of the word, the sense that found cars on top of MIT buildings and football fans holding up cards that spell "we suck" in aggregate. I might be getting older but "hack" these days seems to just mean "go to work" or even "go to work on the weekend".
Come on
Re: Google Maps Hacks
#48Cool trick - I wonder how much of the cell tower's capacity he is hogging too?
No more than two buses, it's only a 100 phones.
Re: Google Maps Hacks
#49Wow, I never actually stopped to think about the way Google determines traffic but it seems so obvious now. This is a very simple but cool trick, I'd expect to see something like this in an action movie where people need to reroute an important car to a particular street. Anyone have any idea how often this data is updated? So if the guy runs through a street with a cart and it turns red, when will it show up as clea…
I guess an important piece (conveniently left out of this story) is that it does not work if there are other cars on the road, as these cars quickly invalidate the data coming from the slow cart.
I always assumed an average was performed over instantaneous velocity that fall in network segments. So, it would depend on the relative magnitude and the edge count on the graph in question you wanted to manipulate.
For a long very straight road represented as a single edge, I would assume if you had 100 actual cars, you'd get an average of the manipulated data rate and the real flow rate.
Re: Google Maps Hacks
#50I am happy to realize that it is Artistically possible to disrupt Google Map