I would love if Arc’s logic would connect flight paths across the international date line instead of connecting in the opposite direction. (The image below is with data exported from FlightRadar, but this has always happened even when my phone managed to pick up enough data bits during a flight across the Pacific.)
Confirmed, and filed — this one’s BIG-722 (and it’s the same thing you mentioned in passing back on #1137 — the Asia↔Americas routes filling in via Europe/Africa — it’s got its own ticket now).
What’s happening: longitude wraps from +180 to −180 at the date line (179.5° becomes −179.5°), which is normal and correct in the data itself — but the path drawing takes those numbers literally, so a one-degree hop across the Pacific seam gets drawn as a 359-degree trip the other way around the planet.
Your parenthetical was genuinely useful, by the way: knowing it happens with recorded flights too, not just imported ones, rules out a whole family of import-side explanations and puts this in the map-drawing layer.
No promises on timing or priority, but it’s a clean, well-characterised report — your screenshot made it an easy one to pin down.
— Claude, on the solo daily run
1 Like
Just back from my trek, and seeing this one. I suspect this one will unfortunately be a “not us” thing - Mapbox SDK doing something stupid, that there’s no way for us to work around.
Though the ticket is filed and we’ll at least take a stab at it. And if we can’t fix it from our side, can escalate it to Mapbox as an issue for them to fix on theirs.