Ok, something is definitely going on. Last night, all three of my development PC's were returning latitude and longitude to 6 decimal places of accuracy. Tonight, just running the same build from last night is returning rounded whole numbers. Can't even say rounded to the nearest whole number because 33.306262 is now just 38 and its not just one one machine, all three are now returning the same bad values.
Geolocator geoLocater = new Geolocator() {DesiredAccuracy = PositionAccuracy.High };
Geoposition position = await geoLocater.GetGeopositionAsync();
At first I thought maybe there was some change (that I don't remember making) that was causing it but nope, that's the data coming back straight from the call to GetGeopositionAsync (as you can see below).
I'm trying to dig through the rash of MS updates that likely ran last night to see if any of them may be the cause. I'm open to suggestions if anyone has seen this behavior in the past.
Question
+Biscuits Brown MVC
Ok, something is definitely going on. Last night, all three of my development PC's were returning latitude and longitude to 6 decimal places of accuracy. Tonight, just running the same build from last night is returning rounded whole numbers. Can't even say rounded to the nearest whole number because 33.306262 is now just 38 and its not just one one machine, all three are now returning the same bad values.
Geolocator geoLocater = new Geolocator() {DesiredAccuracy = PositionAccuracy.High }; Geoposition position = await geoLocater.GetGeopositionAsync();At first I thought maybe there was some change (that I don't remember making) that was causing it but nope, that's the data coming back straight from the call to GetGeopositionAsync (as you can see below).
I'm trying to dig through the rash of MS updates that likely ran last night to see if any of them may be the cause. I'm open to suggestions if anyone has seen this behavior in the past.
Link to comment
Share on other sites
2 answers to this question
Recommended Posts