Field elevation not taken into consideration

[TilBlechschmidt]

When filtering reachable locations, the field elevation is not taken into consideration at all. While the error is reasonably small at less than 100ft in the HH region, it is a critical error which causes wrong indications!

[TilBlechschmidt]

The elevation differences in the area covered so far are within 133ft at the extremes. While this is a non-negligible amount, calculating the range profiles for each different elevation would increase the overall computational complexity by the factor of the locations covered. While certainly possible, the simulation lag does not seem worth it and thus the better solution would be to simply inform users about this in advance. This way, the user can factor in a reasonable amount of headroom.

The picture below depicts the terrain elevation across most of the current service area:

Available here.

This decision may be revised at a later date.