... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Elevation data completion bug
#1
Hi

First of all thanks for such a useful piece of software - it's one of my go-to programs.

Not sure if this is the right place to report a bug but here goes:  I have my preferences set to statute.  I loaded a track containing elevaton in metres, these were displayed correctly in feet. However when I then applied auto-complete to elevations, RC read the elevations - in metres - from the data source and applied them *without* converting; so 2306ft (703m in the original file) became 786ft instead of 786m.  

I'm on v2.17 BTW.

If I could bolt on a feature rquest as well, it would be great if the units for elevation could be selected independently of the units for distance, as I generally want to see distance in miles and elevation in metres.

Thanks
Reply
#2
(11.07.2016, 21:12)snowtracks Wrote: If I could bolt on a feature rquest as well, it would be great if the units for elevation could be selected independently of the units for distance, as I generally want to see distance in miles and elevation in metres.

Is there a particular reason for doing so or just your peculiarity?

Grüße,
Ilmari
Reply
#3
Ilmari, I live in the UK.  We measure distances in miles but our maps (Ordnance Survey maps are the maps mostly used for outdoor activities) have had elevations in metres for many years.  To be fair they also have kilometer grid squares and I have nothing against kilometers but I generally think in miles.  Also I ski in mainland europe so again am used to metres for elevation in skiing, walking etc.  I don't think it's that strange a request :-)   But the main thing is the bug really - as yours has been the only response I am not sure if I have raised this in the right place.  Maybe I'll try raising via the program again - I wasn't sure that worked the first time I tried.

[Edit] BTW this bug explains another post I have just come across - http://forum.routeconverter.com/thread-1984.html
Reply
#4
Dear snowtracks,

I guess I found the bug: completed elevation and speed data wasn't converted to the statute or nautic unit systems.

I've just uploaded a new prerelease which should fix this bug. Please test and report!
--
Christian
Reply
#5
(17.07.2016, 14:38)routeconverter Wrote: Dear snowtracks,

I guess I found the bug: completed elevation and speed data wasn't converted to the statute or nautic unit systems.

I've just uploaded a new prerelease which should fix this bug. Please test and report!

Hi Christian

Just gave the online edition a whirl and that seems to work fine, thank you.  That's saved me quite a lot of work as I had already done quite a lot of work on a number of tracks - filling in missing segments, removing superfluous points etc - so being able to just update the elevations instead of reworking the tracks all over again with the options set to metric was appreciated!

Thanks again
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)