sgofferj / tak-adsb-id

A collection of interesting ADSB ICAO hexids for ADSB to CoT feeders.

TAK ADSB ID collection

Overview

This is a collection of specific ICAO hexids to make ATAK/WinTAK SA displays more meaningful. The idea is to use them in the middleware which feeds ADSB data as CoT objects into a TAK server. I started out with Finland but pull requests are welcome. In April 2023, I also added countries.json which classifies ICAO hexid ranges. Together with the cotdb, those 2 files should allow for at least an IFF classification.

Friendly, hostile, neutral?

I classify the aircraft from the point of view of somebody living in Finland. Finland is not at war with anybody at this point in time, so at the moment I do not classify any aircraft as hostile. If you feel, some aircraft should be classified as hostile, please download the files and use the search and replace function on your local copy. Civilian aircraft are classified based on their country of registration because it's not always possible to figure out who is actually operating a certain aircraft at any moment in time.

Update 2022-04-26: Due to the Ukraine conflict and the changes in Finnish foreign policy, I reclassified all Russian and Belarusian planes as "hostile".

Other stuff

To assist middlewares with displaying special civilian aircraft, I am developing some conventions for the source files:

• EMS aircraft will have their operator field in the format "EMS (operator)".
• SAR aircraft will have their operator field in the format "SAR (operator)".
• Law enforcement aircraft will have their operator field in the format "LEO (operator)".

json

Since release 162458ZFEB23 the releases also contain a json file (cotdb.json) which should make integration of the data in 3rd party middleware fairly easy. The format is:

{
  "aircraft": [
    {
      "hexid": "3dd55c",
      "cot": "a-n-A-C-H",
      "reg": "D-HBAY",
      "type": "BK117B2",
      "operator": "EMS (ADAC)"
    },
    { ... }
  ]
}

The second available JSON format (cotdb_indexed.json) is

{
  "3dd55c":["a-n-A-C-H","D-HBAY","BK117B2","EMS (ADAC)"],
  "3dd652":["a-n-A-C-H","D-HBKK","BK117B2","EMS (ADAC)"]
}

Contributing

Please feel free to contribute to the list! Ideally, you would submit a pull request, but you can also open an issue. Please keep in mind what I wrote above under "Friendly, hostile, neutral?".

Issues

I will try to handle issues fast but this is a hobby, I have a family and a busy work day, so please don't expect wonders!

License

This repo is published under the Creative Commons Attribution-ShareAlike 4.0 International License.

tak-adsb-id's Issues

CI pipeline

Create a CI pipeline which creates a single database files from all the separate country/type.txt files.

Added support within AirCOT, and thus AirTAK, ADSBCOT, ADSBXCOT, etc

It's been a long-time coming, but I finally added support for TAK-ADSB-ID to AirCOT v2.0.0, which is a library used by most of my other aircraft-to-tak gateways, including AirTAK, ADSBCOT, etc...

To use TAK-ADSB-ID, a user needs to set KNOWN_CRAFT config variable to your .json file, and they're good to go.

https://github.com/snstac/aircot