This space could be added back if we don't use a table to lay out this section like is done in the "Signal" section but I'm not sure what side effects that might have
Feedback was to show routes that seem implausible and simply clearly mark them.
Hopefully two leading questionmarks is sufficient.
I haven't figured out how to add a link to a page where people could suggest an
update for the data.
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>
* Update layers.js
Pretty sure this - while only an ID and not used anywhere - should be ukawacs and not uka2awacs. Looks like a copy/paste that wasn't properly edited
* Update layers.js
Adding line (with credit comment) to pull in the German AWACS orbit areas
* Add files via upload
Adding German AWACS orbits from https://github.com/olithissen/AwacsOrbitsDE
* Update layers.js
Add line to pull in Dutch AWACS orbits geojson data
* Update layers.js
Added comment for NL AWACS zone data source
* Add files via upload
Geojson data for NL AWACS Orbit areas
* Add files via upload
Add Polish AWACS Orbit area data
* Update layers.js
Add line to pull in Polish AWACS geojson data file
* Update early.js
I am hugely OCD.
* Update NL_Mil_AWACS_Orbits.geojson
Added missing coordinate to json file, thanks to the Dutch Ministry of Defense pointing out that I am an idiot via email
Co-authored-by: wiedehopf <wiedehopf@users.noreply.github.com>
* Update layers.js
Pretty sure this - while only an ID and not used anywhere - should be ukawacs and not uka2awacs. Looks like a copy/paste that wasn't properly edited
* Update layers.js
Adding line (with credit comment) to pull in the German AWACS orbit areas
* Add files via upload
Adding German AWACS orbits from https://github.com/olithissen/AwacsOrbitsDE
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.
