Closed kebekus closed 2 years ago
PS: For an example, search for "Skövde".
Relates to #88
This is an issue with the source openAIR file and it should be fixed there (in the file) in the next airspace import that is done directly via the version2 webapp. Another solution would be to adjust the migration script (v1 -> v2) which is currently used to migrate data from v1 -> v2. But this will not reliably extract airspace types from strings since there are too many variations in names (that, once again, are defined in openAIR files...).
Dear all,
the TIA and TIZ airspaces that exist in Scandinavia are misclassified as "OTHER" even though "TIA" and "TIZ" explicitly exist as possible entries for the "type" field.
Perhaps it might make sense to tweak the importer to look for the string "TIA" and "TIZ" in the airspace name?
Best,
Stefan.