airspace list is inconsitent with the map

[bomilkar]

I look at airspace/airspace_list.txt and compare the airspace file for Germany listed here with what I see on the SkyLines map. The two are not consistent.

Example: look at airspace C around Munich airport EDDM (north east corner) and compare that with what is listed in airspace/airspace_list.txt: https://www.daec.de/fileadmin/user_upload/files/2020/Fachbereiche/Luftraum_und_Flugbetrieb/20200428_Airspace_Germany_DAeC.txt

How is consitency achieved between airspace/airspace_list.txt and the map display in SkyLines??

[Turbo87]

How is consitency achieved between airspace/airspace_list.txt and the map display in SkyLines??

the data still needs to be manually imported into the database, which unfortunately takes a bit of time and has in the past been failing from time to time.

[bomilkar]

Understand. So I guess https://github.com/skylines-project/skylines/issues/2154 is a mute point.

[bomilkar]

Here is an other issue: Airspace structures change over time. For instance airspace C around Munich has changed significantly as of March 2020. Or ED-R138A replaced ED-R138 a couple of years ago. When I review a flight from 2015 today it is displayed with today's airspace structure. Is that an esoteric point? And if not, should it keep a history of airspace structures (changes are usually effective towards the end of March) or should it just show no airspace structure at all if it knows the structure it has doesn't apply to the flight?

Does airspace/airspace_list.txt need an effective date?

[Turbo87]

it would be nice to have that, yes. but also quite difficult to implement.

[bomilkar]

I'll put it on my ToDo list for after the season. @Turbo87 , can you elaborate what you do when you "manually import into the database".

[Turbo87]

it's running https://github.com/skylines-project/skylines/blob/master/skylines/commands/import_/airspace.py through the manage.py tool in the root directory