Airspace positioning and altitude calculation issues

[Scumi]

Describe the bug a) Airspace position does not align between barogram and map. b) Airspace altitude is not correctly displayed and also taken incorrectly for airspace violation.

A violation was shown in the flight upload form and can be seen in the barogram, but not on the same position on the map. It also appears to me, that the airspace is always provided in feet (also shown on the map) despite my personal setting being metric. I guess that leads to the altitude violation.

To Reproduce Steps to reproduce the behavior:

1. Go to https://beta.weglide.org/flights/9336
2. Review flight path, altitude and airspace on map and baro at
   • 12:26:18 (lower airspace boundary should be 1981m instead of feet)
   • 12:42:00

Expected behavior a) Consistent airspaces in barogram and map view. b) Correct calculation and display of airspace altitudes.

Screenshots

Device (please complete the following information):

• Device: PC
• OS: Linux
• Browser: Firefox

[frantzheld]

I have the guess, that the map displays the old airspace (before 09.11.2020), while for the barogram the new one is used (after opening BER airport).

I have the same issue at this flight: https://beta.weglide.org/flights/10601

On the map (old airspace) there is no airspace violation, since the outer ring starts at FL65 (1981m). Nevertheless it seems like an violation in the barogram.

Same flight section with seeyou and the new airspace: The displayed airspace violation (red) corresponds to the weglide barogram airspace.

[frantzheld]

The label "Berlin C 1981.2ft/3048ft", which should be "Berlin C 1981m/3048m" seems to be another independent issue.

[samuel-git]

@moldhouse we should unify airspace-tile altitude units and update them too.

[tisoen]

I've just spotted something else that might be related:

Describe the bug Airspace altitudes seem to be AGL in the barogram where they should be AMSL. (Also the values are in m and the units in ft as mentioned by frantzheld)

To Reproduce

• View a flight close to an airspace
• Look at the airspace indication in the barogram and notice it doesn't match the MSL altitude on the map

Expected behavior Consistent airspaces in barogram and map view regarding altitude, maybe due to a AGL/AMSL error.

Screenshots Notice the airspace upper border is slightly above 2000 m AMSL instead of slightly below (Terrain height is around 120 m at this location)

Device (please complete the following information): Device: PC OS: Windows 10 Browser: Google Chrome 87

[moldhouse]

We adjust airspace altitude provided in FL based on QNH of the flight. I suspect this to be the reason for this shift.

[moldhouse]

We have deployed the new airspace tiles. If you empty your cache, the airspace on the map and the provided altitude should now be correct.