Auto-ingest airspace data for FR (France)

[reskume]

No description provided.

[reskume]

Not yet implemented. Source must provide OpenAIR extended format before automated data ingestion can be implemented.

[llauner]

Hi @reskume
https://github.com/planeur-net/airspace
Is now providing OpenAIR extended format.
Direct access to the file is here: https://planeur-net.github.io/airspace/france.txt

The file is also including the bird protection areas (updated every month).

Could you give details on your plans to auto-ingest data from this file ?
Thanks

[reskume]

Hi @llauner

the plans to auto-ingest the repo are still oon our todo-list - and I would love to do that! Last time the missing extended format was a showstopper. With this out of the way, I can have another try. But one thing still remains a pain. There are overlapping airspaces that, afair and please correct me if I'm wrong, are actually not part of the French airspace: for example area near Bale, Geneva. Is this still the case? I know it is no problem if the file is used in "isolation" and is the only one on a flight computer. But the time it is integrated into a bigger dataset that also contains the neighbor airspaces, it gets messy real quick.

If those airspaces still exist in the file, I could think of some possible ways to handle this:

• easiest one: remove non-french airspaces. But this ma be no options since it will reduce UX for people that solely use this airspace file.
• move non-french airspaces to the bottom of the file so that a tool can drop this section of the file when reading it.
• tag each airspace somehow (instead of moving them to the bottom) so that the tool can drop it

Can you think of some other ways to achieve this? Or maybe it isn't even necessary at all...

Cheers,

Stephan

[llauner]

I'll look at the file and see about the overlapping airspaces...