-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interesting Planes #24
Comments
Thank you for raising this 'issue' - the data will be very useful. I hope you find something in my list that you finds useful. |
I'd love to see the DirtBox planes (US and other countries!) as its own separate list. (Note that you can still also have it in any other lists -- nothing says that these lists need to be unique!) The DirtBox concept closely fits what I originally designed Plane-Alert for -- detecting planes of people and organizations that evoke discussions about the ethics of the powers-that-be :) |
Also -- @jamesBNR are you the person who wrote the Chrome plugin for tar1090 -- if so -- THANK YOU -- it's something I use on a daily basis. |
@kx1t yes that's me. On a related note: the list of of dirtboxes came to me from a redditor. Here's the spreadsheet for that, which contains more data than I use: https://docs.google.com/spreadsheets/d/1z3gEODujLqIHhoKRxGuUrTA7n2gVX535_1dJCgVMDxY/edit?usp=sharing |
I'm here for this. 👍 |
Splitting the lists down by category (of which there are 40+) instead of the 4 civ, pol, gov, and mil is high on my list of priorities. The next update includes more gov stuff too, and with the this addition (when I get the time to process it) will only make it more pressing. I'll have a think about the best way to proceed (and if you have any suggestions I'd welcome them). |
Hey guys. I updated the repository to automatically generate the 'derivative' database files on the main branch using a new GitHub action (see https://github.com/sdr-enthusiasts/plane-alert-db/actions/runs/4322447262). @Sportsbadger, I can revert my changes if they interfere with your old method of generating these files. Just let me know. The old files are found at https://github.com/sdr-enthusiasts/plane-alert-db/tree/main/_bin for comparison. I will remove them if you like the new action. For now, I added the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/plane-alert-twitter-blocked.csv file to include the planes that cause Twitter accounts to be banned. This file and the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/plane-alert-twitter-blocked-images.csv file can then be used by people who have the tweet functionality disabled. Should we also include the planes given by @jamesgott1 in #24 (comment) in this file or are there some that can go into the main database? |
Okay, I checked the planes in #24 (comment), and it appears the following (677) of the (807) are not yet in the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/plane-alert-db.csv database. I also checked the database found in the newest version of RadarAtlas, and based on that (2210) of the (2393) planes are missing. You can check this yourself by running the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/scripts/check_james_planes.py script. |
No description provided.
The text was updated successfully, but these errors were encountered: