Quote from: Menion on April 11, 2022, 14:22:04on the left is shown, on the right the data is not shown
What exactly is the problem with the WMS map in this post? When I play with it, all seems to work correctly.
opacity 100% on on the left, on right nothing
if we have more than one layer wich is the order?
and if we use also sat map as layer?
Quote from: Menion on April 11, 2022, 14:22:04I think the only sensor you can count on is the phone's gps, currently there are points that are not taken into consideration due to the filters so the speed data should be calculated as the distance from the last known point and the current point and the time elapsed between their detection.
Recorded speed > this is an old problem with detection of the "not moving" behavior. You are correct that the app currently simply records a speed value received from the GNSS unit. What should be done is to, based on the device sensors (or by attached speed sensor), register movement and based on this modify speed values. The task to do.
Currently I believe point A is detected with a speed of 10Km / h then one stops and so B, C ... F are discarded, then it starts again with G but it is detected when you are already moving again at 10km / h for this reason I think Locus assumes, at the point where one has remained stationary, a speed of 10 km / h.
For me it would be more logical that the speed was determined by the distance and time between A and G as it is an information not altered by the missing points like speed in the point.
It will not reach 0, but it will always be closer to 0 than 10.