Lost_in_translation
3rd December 2008, 08:19 AM
Hi,
I read a lot of threads about GPS-lag on the Diamond, and found no such effect on my device. Finally, I remembered one thing which I learned about GPS-devices a long time ago:
Most of them use a feature called "static navigation" which effects the behaviour at slow speeds or stand-still, especially when walking. This is a feature which the developers of the devices may choose to activate, but it is usually not at the user's discretion to enable or disable.
When static navigation is active, the device will give less information when it moves at low speeds, typically at least up to 6km/h (ca. 4mph). Above this fixed speed, it behaves normal, under this speed, it will not give speed- or directiondata, and will often average the location data, so not every movement will be reported to the software.
When static navigation is not enabled, the reading tends to "jump" when the device is standing still, like in front of a traffic light. I remember my first receiver which had no static navigation, and when I stood at a crossing, the software would reroute after some seconds. The reason: My GPS showed me on the wrong lane and in the wrong direction, and the software believed that I was on the wrong road and had to reroute.
While static navigation is a little annoying for pedestrians, it is a blessing for people who use their devices in a car or on a bike. Here, it will smoothen the operation with road-bound software a lot.
Fwiw: I can experience the same thing. When I move by foot, the reading in Google Maps will lag a little, however when I'm on my cycle or in my car, the reading is very accurate. I have no real problem with the lag in GMM, and prefer a device which works well with Route 66.
Have fun!
I read a lot of threads about GPS-lag on the Diamond, and found no such effect on my device. Finally, I remembered one thing which I learned about GPS-devices a long time ago:
Most of them use a feature called "static navigation" which effects the behaviour at slow speeds or stand-still, especially when walking. This is a feature which the developers of the devices may choose to activate, but it is usually not at the user's discretion to enable or disable.
When static navigation is active, the device will give less information when it moves at low speeds, typically at least up to 6km/h (ca. 4mph). Above this fixed speed, it behaves normal, under this speed, it will not give speed- or directiondata, and will often average the location data, so not every movement will be reported to the software.
When static navigation is not enabled, the reading tends to "jump" when the device is standing still, like in front of a traffic light. I remember my first receiver which had no static navigation, and when I stood at a crossing, the software would reroute after some seconds. The reason: My GPS showed me on the wrong lane and in the wrong direction, and the software believed that I was on the wrong road and had to reroute.
While static navigation is a little annoying for pedestrians, it is a blessing for people who use their devices in a car or on a bike. Here, it will smoothen the operation with road-bound software a lot.
Fwiw: I can experience the same thing. When I move by foot, the reading in Google Maps will lag a little, however when I'm on my cycle or in my car, the reading is very accurate. I have no real problem with the lag in GMM, and prefer a device which works well with Route 66.
Have fun!