Lastly: these settings can lead to a higher battery consumption, but it's up to you to choose the best compromise between a 'real time (and high accuracy)' response, or battery savings.Įdit : I have also a third hint. Honestly the real speed of your GPS can vary (and depends) on the hardware fitted into the device on which the app is running, and if you are 'open-air', but, at least, with these settings you can obtain the fastest response time. With these settings I can monitor the speed and the position of a car running > 100Km/H. In this case the GPS can respond as fast as possible. Second, is to set the TimeInterval to 1000 (milliseconds). I don't understand your code placing ALL the hole distance Blocks in the LocationChanged event so I agree with that is a possible issue.ĭear seen that the solution has been already given, but since you ask for further optimizations, I can suggest you two hiints.įIrst, to set the LocationSensor Distance to 0, This means that the minimum distance to raise a new LocationChanged event is 0, and therefore the speed at which the GPS is responding, is not filtered by a certain amount of meters: in other words, the GPS doesn't wait that the distance bwetween two fixes is greater than 'x' meters to issue the event. There is a bug in the DistanceToLineString and there may be an issue with DistanceToPoint, see Distance on Map point point and point to line not equal - #3 by SteveJG. Make sure you set Screen1.AskForPermission to Permission FineLocation.

It might be time for MIT to consider updating the satellites it can use to obtain a satellite fix.

Google Maps uses multiple constellations that might improve their reported location precision. Keep in mind the MIT Location sensor probably uses only the US satellite constellations when determining location. I suspect that these use different values since Google introduced the fused Provider.Įdit: preliminary tests indicates these yield the same values.

You might have better results using the orange Lat/Lon block in the LocationChanged event. Suggest you try setting Provider to gps When you set the gps, immediately LockProvider when using devices >Android11 (as is your Pixel)Īlso, I suspect using the green Lat/Lon blocks might introduce issues. when i use the app by it is up to 100 of meters off

Google my maps app