This has nothing to do with CORS. There is no need for this header.
This should address a change requested by Ramon (@kx1t)
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
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>
With the limit of 100 callsigns per API call, sending these
requests every second should create a more responsive experience
while still not overloading the server.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Never send more than 100 callsigns to the route server. If there
are more queued up (for example on an aggregator when the user
zooms out), they are sent in batches of 100 callsigns every 10
seconds.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
These were proxied by adsbexchange to not load down the orignal servers
due to many users. Now they limited the proxy to their website.
I have some words for Dan who sold adsbexchange and the new bean
counters but i think avid readers can imagine.
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>
