Live data from Hacker News

Apple Maps claims it's 29,905 miles away

mathstodon.xyz

61–70 of 153 posts

Re: Apple Maps claims it's 29,905 miles away

#61

Earlier quoted context omitted.

Possibly it was using WPS keyed to the ferry's WiFi and didn't consider the possibility that the ferry itself could move out of where it was registered (ie, the port)?

I drove away from the ferry and passed lots of WiFi APs on the way, presumably it should have figured out the new location pretty quick with WPS.

Perhaps the car is programmed to ignore all external signals for a while if it detects significant disagreement for a prolonged time, as might have happened if it had access to both WPS and GPS during the ferry ride. In such cases it would be safe to assume that something is being spoofed, and fall back to INS.

Re: Apple Maps claims it's 29,905 miles away

#63
post #60
post #44

Earlier quoted context omitted.

That's no excuse for disbelieving GPS for extended periods of time. Google Maps gets it right: it tried to keep you on road, but only for a few tens of seconds. After that, if you are in the middle of uncharted territory, it'll show the marker there. (This is probably because Google Maps can be used for walking/biking too)

>(This is probably because Google Maps can be used for walking/biking too) Please don't do that. The map is simply not good enough and does not have enough context (road quality, terrain, trail difficulty) for anything but very causal activity. Even then I highly recommend to use a proper map, electronic or paper.

yeah I'm not gonna open some paid trail map or buy a paper map so I can walk across my local city park and give my friends a pin to find me...

Re: Apple Maps claims it's 29,905 miles away

#64
post #36

Earlier quoted context omitted.

I had a Volvo XC90 that “jumped” off the interstate and onto a parallel mountain road east of Knoxville. It did its best to track along those roads and somehow made its way into North Carolina. But even when I was back in Chicago, it was still stuck in NC trying to find a way off those mountain roads. Dozens of on/off cycles did nothing. I disconnected the battery overnight and that didn’t work. At the next service a…

My dad used to have a crappy aftermarket GPS in his car that did the same thing. It would get lost dozens of miles away, and then hundreds of miles away. The explanation I found online at the time was that a GPS receiver needs to download data about the exact orbits of all GPS satellites from time to time. Satellites slowly lose altitude and change their orbits. Up-to-date information is constantly broadcasted by eve…

There's no way a modern smart phone or car relies on those ephemeris transmissions. They all just get it from the internet, which takes less than a second. That's one of the reasons why a smart phone has a reliable GPS fix basically instantly after being booted up, while old-school offline GPS units needed minutes to get a fix.

Re: Apple Maps claims it's 29,905 miles away

#65

While we're on the subject of maps-related bugs, I was recently borrowing a new Tesla Model Y and took it on a RORO ferry. After the crossing, the car’s GPS was convinced I was still at the port where I had departed from. I restarted it a couple of times, but nothing. I drove off using Waze on my phone instead of the car's navigation. The map on the car kept moving relative to the direction I was driving, so the navi…

One hypothesis I can offer is that your car could not, for whatever reason, use assisted gps to download the almanach which relies on mobile networks. Gps devices that download the almanac via gps itself can take up to twelve hours (in higher latitudes i think)!

Re: Apple Maps claims it's 29,905 miles away

#66
post #34

While we're on the subject of maps-related bugs, I was recently borrowing a new Tesla Model Y and took it on a RORO ferry. After the crossing, the car’s GPS was convinced I was still at the port where I had departed from. I restarted it a couple of times, but nothing. I drove off using Waze on my phone instead of the car's navigation. The map on the car kept moving relative to the direction I was driving, so the navi…

My guess would be: 1. Car entered ferry, loses GPS 2. Car entered dead reconning mode used for tunnels and such 3. Car left ferry, acquired GPS Then either: 4a. Location via dead reconning vasty disagreed with GPS because the car doesn't know about the ferry's movements, triggering some kind of failsafe. Or: 4b. There's just a plain old bug in the condition to switch back to GPS and maybe people haven't noticed becau…

My local roro ferry drops you off pretty close to downtown. If you don't get a good fix as you get off the boat before you get into the urban canyon, satnav is pretty hopeless for a few minutes.

Doesn't usually take 5 hours to figure out where it is though. At least not on my vehicles, even the one that's always getting confused.

Re: Apple Maps claims it's 29,905 miles away

#67
post #56
post #54

The most annoying thing about iPhone Maps for me is the inaccuracy of the direction indicator. I've googled and it doesn't seem to be a universal complaint even though I've experienced this on multiple devices over the years even after following instructions to re-calibrate multiple times. Maybe I've just been unlucky. It intensely frustrating to use maps for direction finding while walking or cycling when the app is…

That's a phone compass problem no? Perhaps the specific way you're holding the phone is confusing for the algorithm?

[dead]

Re: Apple Maps claims it's 29,905 miles away

#68
post #19

Earlier quoted context omitted.

You wouldn't imagine ... I have seen API calls you people wouldn’t believe. Requests hanging off the edge of the load balancer, Ethernet tubes glittering in the dark. Latency logs reporting some API calls that took longer than the age of the universe. Their means and percentiles burning on the shoulders of weekly reports. Plot points dying at the edge of y axis ... like tears in the rain.

Time to reboot

Indeed and Voigt-Kampf the signed from the unsigned, dynamic types from static.

Re: Apple Maps claims it's 29,905 miles away

#69
post #59

While we're on the subject of maps-related bugs, I was recently borrowing a new Tesla Model Y and took it on a RORO ferry. After the crossing, the car’s GPS was convinced I was still at the port where I had departed from. I restarted it a couple of times, but nothing. I drove off using Waze on my phone instead of the car's navigation. The map on the car kept moving relative to the direction I was driving, so the navi…

> On a vaguely related note, driving 3000 kilometers through Europe in an electric car was surprisingly nice. Having done a number of multiple-thousand km trips in Europe in an EV (not a Tesla, nobody buys those anymore) — it's amusing how non-EV muggles think this is somehow an ordeal. It's just fine! There are drawbacks: you do have to use your brain and plan ahead more than you do when burning dinosaurs. But I fou…

[flagged]

Re: Apple Maps claims it's 29,905 miles away

#70
post #34

While we're on the subject of maps-related bugs, I was recently borrowing a new Tesla Model Y and took it on a RORO ferry. After the crossing, the car’s GPS was convinced I was still at the port where I had departed from. I restarted it a couple of times, but nothing. I drove off using Waze on my phone instead of the car's navigation. The map on the car kept moving relative to the direction I was driving, so the navi…

My guess would be: 1. Car entered ferry, loses GPS 2. Car entered dead reconning mode used for tunnels and such 3. Car left ferry, acquired GPS Then either: 4a. Location via dead reconning vasty disagreed with GPS because the car doesn't know about the ferry's movements, triggering some kind of failsafe. Or: 4b. There's just a plain old bug in the condition to switch back to GPS and maybe people haven't noticed becau…

It probably doesn't do dead reckoning even in tunnels

And maybe the system sucks to get the GPS almanac if badly desynced

Post reply on HN