Wow, I’m impressed with the documentation
I will read it , there are things I can learn from, I was never good in writing down, all in the memory but now that I’m getting older I have to write things down.
actually I removed all USB and receiving parts as this fork is really only intended to connect to another source and show the map etc.
In fact I have another part that gets it into docker and runs it from my Synology NAS which connects then to the real receiving PI (or other source).
The HTML part added and changed can be taken and put into the standard dump1090-fa in order to get the instrument view only…
(3) Cloned source code from github.com/bm98/dump1090
git clone https://github.com/bm98/dump1090.git
(4) Swapped html folder of dump1090-fa ver 3.6.2 by cloned public_html folder of dump1090-fa/bm ver 22.214.171.124
#FIRST renamed existing html folder to html-orig to preserve it
sudo mv /usr/share/dump1090-fa/html /usr/share/dump1090-fa/html-orig
#Next copied folder public_html from bm98's cloned code with name html
sudo cp -r ~/dump1090/public_html /usr/share/dump1090-fa/html
(5) Cleared browser cache (Ctrl+Shift+Delete) and Reloaded brower (Ctrkl+F5)
a. above FL200 everybody is using QNE (std setting 29.92’’ Hg or 1013.2 hpa) baro altimeter setting (actually upon passing trans.alt - departure aerodrome till trans. level - arrival irport).
in this figure it shows 1010hpa so either aircraft setting wrong or more likely data presentation issue (more likely). so maybe change the code for all above FL200 to display 1013.2hpa / 29.92’’
a) to be corrected - not so familiar with this topic, so I have printed what was received …
b) is an issue when no heading is available, then the compass is not drawn but the bug must then not be shown. The position of the bug is because the hidden compass is north up per default.
And yes the data received is seldom complete - may be I have to show when it is not available in order to know it in the first place.
The data does tend to be patchy, it depends on both what the transponders support & what the local SSRs are interrogating for. For the FMS/MCP & QNH settings, exactly what is reported is very vague in the spec and each transponder/avionics combination seems to do it differently, so YMMV.
no worries. altimeter setting is used for vertical separation between flights. the standard setting 1013 is been used above transition altitude ~5000’ above airport elevation, (eg. highest airport La Paz 13334’ has a trans.alt of 18000’) so safe to assume above FL200 (20000’) altimeter setting is always 1013.2hpa or 29.92’'hg, steady, climbing, descending flight.
ED1: I modified /usr/share/dump1090-fa/html/gp-altitude.js as follows
after line BARO = Math.round(BARO);
///*** use QNE 1013 if altitude >= FL200 ////////////
if (alt_geo > 19999);
BARO = Math.round("1013.25");
Short note - the Github has now a merge from the latest skyview build so you may enjoy the latest FA work in addition to the instrument panel.
There is also a new aircraft database (backup!! then delete and then add all new files in db) which is derived from a BaseStation archive (12-Sep-2018 from flightairmap.com - Thanks a lot for providing the files!!)
To get it it would be best to update to 3.6.3 and then go along the guidance already mentioned in this thread.
There is one file for worldwide Navaids and one for Airports (a lot…) I found in public domain.
(Open data @ OurAirports)
You may have to reduce the entries to a reasonable number in your region I think.
This would involve a notepad++ editor and some patience… and delete only full lines…
http://geojson.io has the ability to load the file and display the contents - it also complains if the file is malformed.
I loaded all Navaids - though it takes quite some time to load - firefox complained a bit but then it worked.
I have still to figure out how to load such files into the Skyview …
I use the modified Skyview by user @akissack that provides a lot of flexibility.
I get the navdata from AIP or Skyvector (less accurate if you point the cross-hairs over a navaid to get the coords) and edit the relevant .geojson files. It’s a lot of work, even for a small FIR like Greece !
Al’s fetures at here
ED1 unable to incorporate your glass-panel in Al’s code as yet.