The third value is the horizontal accuracy.
That makes sense, not sure why it's not covered in the documentation?
Thanks for letting me know Steve, figured it was something like that.
Personally, I hadn't really ever used Location() before, so I wasn't expecting a third value.
If you guys are still at Heavenly, it would be a good place to test this. When I am using the Location function (like you, not Location Values) - I actually get a total of 6 lines of results.
No question that the first 2 are latitude and longitude.
FMI tech support first said that the third value is accuracy, like Steve Romig says, but then they called me back and said no, it represents altitude. Here in Rockwall, TX, that makes sense because we get a value of 176 which is about 583 feet above sea level which is about right.
But then, there are 3 other values returned, as shown below. These are the 4th, 5th and 6th values returned from the function (Location; 1; 30) in Rockwall TX where we wanted to obtain the maximum possible precision ( hence 1 for accuracy) and we were willing to allow 30 seconds for the timeout.
If you hotshot skiers want to test this on the mountain at high altitude, it would be interesting to test it at the base of the chairlift and then again at the top.
Have fun at Heavenly!
Didn’t even think about this while I was out on vacation!