Hi, I like the stats that this project generates and the way it presents that information. This being an optional add-on with adsb.im is nice. One thing I would like to see under the "Record Holders" section is to see what the farthest and nearest aircraft your ADS-B site is able to detect.
One of the projects I've made (since it feeds off of the dump1090/readsb json) handles detecting these exceptional cases:
It of course, isn't as pretty, but I feel like this project is capable of doing something similar.
In terms of determining the nearest aircraft, this requires more calculation since just using the distance stat isn't as accurate (e.x. a plane at 40000ft right over your location is farther away than one at 2000ft 0.2nmi away). Implementing a "nearest aircraft" stat would require a Line-of-Sight calculation which is the method I use in my aforementioned project for its plane selection algorithm. The calculation itself is easy to do, however, I'm not sure doing this would be within the scope of this project.
One drawback that I can think of when determining the farthest aircraft is handling cases when there there's a combined feed (e.g. an adsb.im setup with multiple sites), in which case detecting the farthest aircraft wouldn't make much sense. Additionally, when trying to determine a "farthest" aircraft is the need to do some basic filtering for aircraft that have glitchy/jumpy GPS positions (e.g. general aviation). In my experience, I've had to do this in my own code as to not have meaningless results from planes that report a location of 0N, 0E on one data packet and back to its correct location the next.
Hence, adding this type of stat tracking should be an optional setting for the end user.
Hi, I like the stats that this project generates and the way it presents that information. This being an optional add-on with adsb.im is nice. One thing I would like to see under the "Record Holders" section is to see what the farthest and nearest aircraft your ADS-B site is able to detect.
One of the projects I've made (since it feeds off of the dump1090/readsb json) handles detecting these exceptional cases:
It of course, isn't as pretty, but I feel like this project is capable of doing something similar.
In terms of determining the nearest aircraft, this requires more calculation since just using the distance stat isn't as accurate (e.x. a plane at 40000ft right over your location is farther away than one at 2000ft 0.2nmi away). Implementing a "nearest aircraft" stat would require a Line-of-Sight calculation which is the method I use in my aforementioned project for its plane selection algorithm. The calculation itself is easy to do, however, I'm not sure doing this would be within the scope of this project.
One drawback that I can think of when determining the farthest aircraft is handling cases when there there's a combined feed (e.g. an adsb.im setup with multiple sites), in which case detecting the farthest aircraft wouldn't make much sense. Additionally, when trying to determine a "farthest" aircraft is the need to do some basic filtering for aircraft that have glitchy/jumpy GPS positions (e.g. general aviation). In my experience, I've had to do this in my own code as to not have meaningless results from planes that report a location of 0N, 0E on one data packet and back to its correct location the next.
Hence, adding this type of stat tracking should be an optional setting for the end user.