Originally Posted by
canadiancow
It's preposterous to expect indoor location tracking to work unless you're the one installing beacons. And if AC is installing beacons, they're clearly either not working, or they're not advertising the capabilities properly. Telling someone it will take them 30 minutes to get from the Cafe to D26 without a "our system sucks" or "this is highly inaccurate unless you flip this switch" is just disingenuous.
I'm going through the Cafe on Friday. I'll try it and report back. If it's inaccurate for me, too, then I'll diagnose it and see if I can narrow it down to something to do with inaccurate location data vs an inaccurate map in the app. An easy enough test. If you think it's a beacon issue, I'll test that. The accuracy of beacons are negatively affected by whether Bluetooth and Precise Location are enabled.
And Scott, a reminder -- 5G DAS installations are almost surely the purview of the airport, just as it is with cell towers & service. If there is a consistent problem with people's locations being significantly off at certain places in Pearson, you can't really hold that against Air Canada... they're just a tenant. Plus, location accuracy is network-specific. Bell, Telus, Rogers and Freedom all vary in their DAS coverage of Pearson. This can affect the quality of location information coming into the phone.
Originally Posted by
canadiancow
I have a decade of experience working on Android apps, including working on the Android team at Google. I'm familiar with how it works.
And I was part of a team building WAP/WML capabilities in 2000-2001, and testing it in (among other weird places) the bowels of the Atlanta airport. Painful days. Been at this a long time myself.