airspace data needs update

[bomilkar]

I just noticed that airspace data for Germany is outdated. For instance EDR138, EDR144, EDR147.
How can this be updated to avoid false alarms?

[pyrog]

The airspaces are imported manually into the server database. See: skylines/INSTALL.mapserver.md

💡 I suggest to use CI for reloading automatically the DB when airspace_list.txt is updated.

[bomilkar]

I don't know what triggered the original email below, however the
"aispace_list.txt" references a 2 year old airspace file for Germany
which is really outdated. (I don't know about the other countries.)

Who can change the list and replace the entry for de to:
http://www.daec.de/fileadmin/user_upload/files/2012/fachbereiche/luftraum/DAeC_Germany_Week22_2016.txt

Cheers,
Ronald

Am 31.10.2016 um 22:52 schrieb pyrog:

The airspaces are imported manually into the server database. See:
skylines/INSTALL.mapserver.md
https://github.com/skylines-project/skylines/blob/master/INSTALL.mapserver.md

💡 I suggest to use CI for reloading automatically the DB when
airspace_list.txt
https://github.com/skylines-project/skylines/blob/master/mapserver/airspace/airspace_list.txt
is updated.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#435 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT54V5NvUx1khevKTTk-AvMWEmQMxZ6Lks5q5mMtgaJpZM4JeOQt.

[pyrog]

I could do that, but it is better to parse the "up to date" (?) list from xcsoar-data-repository (See #538)

[TobiasLohner]

💡 I suggest to use CI for reloading automatically the DB when airspace_list.txt is updated.

As written in #538 I don't recommend automation for updating airspaces.

[pyrog]

The automation could be "send email to admins to build manually airspaces" 😉

Also, the automation could just check the files to be imported. See XCSoar/xcsoar-data-repository#53