#8 Start altitude limit sometimes fail

[Arne Martin Güettler]

Hi, thanks for condor2nav, I find it very helpful for use with XCSoar.

However, the start altitude limitation has a few problems. First of all it is specified as AGL, while it should be MSL. It is MSL in Condor. The same goes for finish limitation.

However, specifying the limitation in XCSoar is a bit unproductive in the first place. Condor allows you to start by climbing out the top of the start sector, while XCSoar does not (at least not for the "start line" start method which condor2nav uses for the 180 start sectors commonly used in Condor). That means in Condor you can start by climbing above the minimum altitude while inside the start sector. In XCSoar you won't be started until you cross the start line, but if you started out the top in Condor, then you will be above the start altitude limitation by the time you reach the start line, and XCSoar won't start the task at all.

So I think it's better to not specify the start height limit in XCSoar at all. The consequences of XCSoar not starting the task at all is much worse than the time being a few seconds or minutes wrong when you start out the top.

I think XCSoar allows starting out the top of the start sector for Cylinder and BGA start sectors, but those don't usually correspond with the start type used in Condor, so can't always be used.