inlcude all labels in correction
use form to change altimeter
adjust baro correct formula
provide documentation for the formula source
old formula was off by 2 ft at 10k ft and 6 ft at 40k ft.
was mostly about citing the formula source
This is a special case for a tar1090 instance that shows the combined output of
multiple readsb instances (like in a stage2 instance of the adsb.im feeder
image).
This tries once to download a multiOutline.json file and remembers if it exists
or if it should use the outline.json file instead. In the update loop it simply
checks for a third format where points is an array of arrays. And then loops
over that outer array - which in the case of the regular output.json is simply
an array with just one entry.
The additional overhead is negligible, the additional feature is really cool
(once you have the code to create merged outlines).
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
new heatmap query option:
significant slowdown / experimental
enable filtering by type code / type description / hex / DB flags /
military / registration / country of registration / data source
This allows an obvious way from the map display to go back to
a web UI that can configure a feeder setup.
Off by default.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
As requested by the API server maintainer, this will keep unresolved
callsigns queued until the previous API request has been completed.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This collects the callsigns in question in batches - the first one
after 5 seconds, after that every 10 seconds, and calls a (configurable)
backend server. This server can be run locally or a public server can be
used - right now this is configured for api.adsb.lol.
The feature is turned off by default.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Prior calculation of the top-left corner location of the infoBox could
result in negative values, placing the element (partially) out of view.
Also, positioning was inconsistent, depending on whether left/right or
above/below the plane marker.
With this change, the size of the infoBox is taken info account when
calculating the relative position, and it ensured that the values would
not be less than zero.
