Just use the adsbexchange image, it can feed fr24 / fa if you so desire. https://www.adsbexchange.com/how-to-feed/adsbx-custom-pi-image/
I'd recommend it like this and getting the data from the locally replicated data:...
Their devices don't provide the raw data in a format useful to us. Not sure they provide the raw data at all.
If someone else does it, it'll get numbers added to it. But no it's not an issue.
Yeah i do understand the request but i can't help you. The microADSB receiver doesn't give timestamps and just has very bad reception. No...
The adsbexchange image doesn't support microADSB. Use the rtl-sdr, it's better anywy.
You'll have to set the position once you are at location for MLAT to work. ADS-B will work regardless. You'll need a hotspot for the pi to join...
Use the adsbexchange image or this guide: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver There is no zadig driver on...
That's probably harmless. Try updating via the webinterface, see if it changes anything.
It shouldn't grow indefinitely ... just some fragmentation causing a bit of growth. The adsbx image is deployed to some locations where access is...
That's two services ... i'm just saying you could get away with one of the services with one just passing data to the other. Actually...
That's not a feature i support for home installs. You can probably add --write-json-globe-index but that will change a lot of other behaviours...
Technically adsbexchange-feed and readsb services are somewhat redundant on the image.
There are way too many waypoints to display them all. Check the high and low level IFR map layers ...
Besides the existing map layers you can select, there is no such feature.
Separate names with a comma.
