tommi, thanks for help. Thanks for silly questions and also for changes in manual. Whole wiki is free to use and free to edit, so feel free

to change everything you find useful. There is always way to revert changes back in case, something will be "bad".
I changed automatic calibration, so it now use SRTM data if they're available, otherwise use normal measured GPS altitude. I'm sure this will need some testing, to make sure it works correctly, so take next release versions as "Altitude testing version". There is always possibility to fill recorded track with offline altitude data (in case measured altitude will be completely wrong), so I'm not worry too much.
To some of your comments:
"This sounds like if I record a track from A to B that the correction might change during the record of the track due to different Geoid altitude of A and B." - that's correct in case you travel longer distance. Anyway changes aren't too big on bike ... check this map
http://www.esri.com/news/arcuser/0703/g ... id3_lg.jpg where are visible changes all around the world. Values are from -100 to around +50 metres.
"What does "during usage" mean? During track recording?"
yes also during a long track recording. And don't worry, there should not be any huge change after calibration, but Locus should spread new calibration into next few minutes so there will be fluent movement of altitude from previous calibration value to new ... we'll see how this will work
@sherman: do you know any site that offer METAR data for the whole world? I'm not able to find any. Only some local