Filter Track Limitation Seems Odd

Former Member over 11 years ago

I usually like to filter my hiking tracks by distance, removing anything that is 1 foot or less in length. I noticed not only is there a puzzling limitation on the Distance filter, but it is also a bizarre number range. If, for example, you set the Distance filter to 3 ft and click "OK", a message appears stating the valid range is from 3.28083989501312 to 164041.994750656. See a screen grab below...

Is this a bug? I noticed the DEFAULT value comes up as "3" when you first run the program... but even that number is invalid! I couldn't find another post on this issue in the forums, but this is kind of an irritating limitation for me. Any help?

0 BTLAAKE over 11 years ago

I’ll take a stab.

The range values are not really bizarre. The calculations done behind the scene are much less of a pain if the physical parameters and constants are in consistent units and always done in the same consistent units. In the case of the GPS system, distance is in meters, time is in seconds and angles are in radians. This will lead to area in square meters, speed in meters/second, and angular velocities in radians/second etc. Calculations and results will bein these units and converted to user units prior to display.

The range you see translates to 1 meter to 50,000 meters in the units that will actually be used to within the calculations.

I would consider it a bug when the programmers preload a value that is outside the range of accepted values.

In truth, the program probably has the default as 1 and the units will be in meters. When converted for a user, it should result in the correct value, however, the value is being truncated or converted to an integer prior to being sent to the output device (computer screen). Which I also consider a bug.