Comment on page
This document aims to guide you through:
...whilst also building a basic understanding of Docker.
- ADS-B reception via
- Feeder containers to feed your preferred services
- Local visualisation of ADS-B and MLAT data with
These are deployed (in conjunction with RTL-SDR hardware) as follows:
To explain the flowchart above:
- ADS-B transmissions are received via the 1090MHz antenna and RTL-SDR dongle
- The RTL-SDR dongle device is mapped through to a
ultrafeedercontainer, this container's function is to decode the ADS-B transmissions and makes them available via several protocols (BaseStation, Beast, BeastReduce, raw, VRS)
- There are then three feeder containers:
- Flight data is visualised using
tar1090, presenting a web interface allowing you to view the flight data received by you set-up in real time.
There are other feeder packages available (eg: Plane.watch, OpenSky Network, Radarbox, etc) that you may wish to consider too. They are all explained in this document.
There are also other visualisation packages available (eg: FlightAirMap/VirtualRadarServer/Grafana) that you may wish to consider, however keep in mind that these may require more horsepower than a humble Raspberry Pi can provide.
tar1090is very lightweight which is why it is recommended here.
All of the containers in this guide will run on:
linux/amd64("modern" Intel/AMD PCs/servers)
linux/arm/v7(Most Raspberry Pis operating systems)
linux/arm64(Raspberry Pis running 64-bit operating systems)
This mix of architectures allows you to run this set-up this on almost any Linux machine.
If there's another feeder you'd like added as a container, please reach out to me via the methods outlined below.
Following this guide is not very hard, but it does require some familiarity with the command line, editing files, and some patience as you work through the details. If you are looking for an easier option, the How To Get Help section introduces the adsb.im Feeder Image which is designed to make things even easier.