I completely agree with you that the current implementation has its limits. I see the same, particularly, as I mentioned when the wind shifts and traffic patterns change. You end up with a sea of the same color.
Iām not sure thereās any way to avoid this completely. Iām going to try running it against the log of the data to see if that helps. objās suggestion is a good one for signal strength, but it doesnāt show you traffic lanes, which is what the original heatmap was supposed to do.
Fixed bug that caused elevation labels to display under the heatmap layer. Labels zIndex are now tied to the markers.
Changed default layering of aircraft markers. Higher altitude markers now overlay lower altitude markers. (Google default is further South markers overlay those further North)
Amended Range Poly code to only use new (less than 5 seconds old) data to try and avoid bogus elevations.
*Note 1: Iāve run like this for a number of days now and not seen any bogus results. YMMV! *
Note 2: With these changes the range polygons will take a lot longer to build up, particularly in the USA where ADS-B / non MLAT data is a small percentage of the total.
Note 3: Iāve left in the UseMlatDataForRange option to use MLAT data in range polygons in config.js, but Iāve changed the default to false. I strongly recommend not using MLAT data for elevation range plots.
Added option to toggle on/off a fill for the ranges
For those running Firefox, a simple refresh will not get the updated files to load.
enter
about:config
in the URL Address. Then search for the key
browser.cache.check_doc_frequency
and set it to 1. Then a simple refresh will work
0 ā Check for a new version of a page once per session (a session starts when the first application window opens and ends when the last application window closes).
1 - Check for a new version every time a page is loaded.
2 ā Never check for a new version ā always load the page from cache.
3- Check for a new version when the page is out of date. (Default)
Maybe related, I found that the internal webserver of dump1090 does not really work well with larger files (anything over 42KB seems to be troublesome in my case).
The connections get dropped before the whole contents of a file has been sent over. I had to change to using an external webserver to get it working.
By the way, it would be simple to make any other data available in the label. I chose altitude because it was the major dynamic variable that isnāt visible. Position is what the map is for, and speed can be seen by the movement of the icon. Altitude is shown very roughly by color, but I wanted a better figure for aircraft in landing and take off patterns. Everything else, such as flight number etc., is pretty much static data.
Would it be useful to allow any other variables to be shown in the label? Which?
My request would be for custom maps (in a standalone file so it can be easily re-added after updates) and custom colors for planes and range rings, also in a standalone file. I made one at SnazzyMaps and added it to my Dump1090 setup, but itās a little bit of a pain to keep re-adding it after updates:
That already all exists! custom map types, range colors, and plane colors are all defined in the config.js file. You should never update that file, just add any new entries.
I have built a PiAware and have it up and running sweetly. Yesterday I managed to log in to the device using PUTTY and add a feed for FR24 - quite an accomplishment for me!
Now, despite knowing nothing about Linux and jsons, I would like to try and get max range rings onto my screen. First question - will I be able to do this with the stock PiAware installation, or do I have to install the Mutability version?
Secondly, how does one copy a file (the heywhatsthat.json) from my pc to the Raspberry Pi - can Putty do this?
You can start with a clean and fresh Raspbian Jessie installation or you can use the image that is provided. Both options are easy and once up and running, you can install FR24 client just like you did before (use your existing share code).
During installation of dump1090-mutability, you have the option to specify the heywhatsthat ID and the json file will be downloaded automatically.
If you run into any difficulties, just shout. Someone here will help you.
As an alternative you could start feeding to PlanePlotter by assigning port 3005 and IP of your Piaware device to it. Having had that done you would take the advantage of PPās range rings which look like in my attached print screen.
Yes but the question was about the expected (theoretical) range that is derived from heywhatsthat.com. That is only available in the dump1090-mutability map.