Open ladewig opened 1 year ago
Thanks,
Am trying to work out what the correct registered_owner_operator_flag_code
should be, do you happen to know?
I assume you intend that field to hold the three letter designator that get assigned to operators (https://www.faa.gov/air_traffic/publications/atpubs/cnt_html/chap3_section_3.html)?
If so, for this owner I assume it would be null. Cavern Aviation LLC doesn’t show up on the list of FAA’s 3 letter designators.
Those only get assigned to airlines and other operators and other operators as far as I understand. Regular owners of aircraft wouldn’t request or be granted those.
From: Jack Wills @.> Sent: Wednesday, January 11, 2023 7:21 PM To: mrjackwills/adsbdb @.> Cc: Scott Ladewig @.>; Author @.> Subject: Re: [mrjackwills/adsbdb] [DATA] Type returned for operator code for a87f4d (Issue #11)
Thanks,
Am trying to work out what the correct registered_owner_operator_flag_code should be, do you happen to know?
— Reply to this email directly, view it on GitHubhttps://github.com/mrjackwills/adsbdb/issues/11#issuecomment-1379688676, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEUJJJQLAA3U53IJSYMFHBDWR5L55ANCNFSM6AAAAAATV5ZKIU. You are receiving this because you authored the thread.Message ID: @.**@.>>
Thank you kindly for that information! I can easily incorporate that faa table/data into the database, and then (attempt) to nullify all the incorrect entries
I’d look at using the Mictronics.de operator db. You can look up operators by hex with that. It's licensed under Open Data Commons Attribution License.
Then one you want is: Complete database for old readsb (non protocol buffer version). Can download at: https://www.mictronics.de/aircraft-database/export.php
From: Jack Wills @.> Sent: Wednesday, January 11, 2023 7:30 PM To: mrjackwills/adsbdb @.> Cc: Scott Ladewig @.>; Author @.> Subject: Re: [mrjackwills/adsbdb] [DATA] Type returned for operator code for a87f4d (Issue #11)
Thank you kindly for that information! I can easily incorporate that faa table/data into the database, and then (attempt) to nullify all the incorrect entries
— Reply to this email directly, view it on GitHubhttps://github.com/mrjackwills/adsbdb/issues/11#issuecomment-1379695415, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEUJJJW345MR7IJEXNTGSQDWR5NBRANCNFSM6AAAAAATV5ZKIU. You are receiving this because you authored the thread.Message ID: @.***>
Again, amazing, I have a big list somewhere of datasets that I need to look into, but don't think this one is on it so far.
I have local branch to fix various airline problems, at the moment they are not stored in the database as efficiently as they could be
There's a submitted issue on github to be able to return both icao and iata callsigns to the user, but as ever, got distracted by other things/projects, even though I went through a laborious process to extract, search, and detail, all the icao/iata callsigns codes that I could find
Url of request https://api.adsbdb.com/v0/aircraft/a87f4d
Why was the data wrong The ICAO type (E50P) is being returned for the registered_owner_operator_flag_code.
Additional context