Contribute to mlat.uk

Welcome! This guide is for anyone who wants to help improve the mlat.uk network. Even if you only have basic Docker knowledge, you can get started quickly.

Any changes you make to your feeder are done so at your own risk. mlat.uk accepts no responsibility for any problems caused by applying any of the information on this page.

Please contact me if you want to contribute and have any trouble with the below instructions, as this information is still a work in progress!
Email me at [email protected]

Contents

• Why Contribute
• Docker Setup
• ADSB.im Integration
• AIS-Catcher Integration
• Advanced Configuration
• Privacy

Why Contribute

By running a feeder client, you help improve aircraft coverage across the UK and real-time vessel tracking via AIS. All contributions are independent and non-commercial.

Docker Setup

If you want to run a dedicated Docker client, you can use the below docker-compose.yml file. This assumes you already have a working knowledge of Docker and docker-compose. This method only shares aircraft data.

Docker Compose

Create a file called docker-compose.yml with the following content:

services:
  mlatuk-client:
    image: myromeo/mlatuk-client:latest
    container_name: mlatuk-client
    network_mode: "adsb_default"  # <-- change to the Docker network your feeder container is on
    restart: always
    environment:
      - BEASTHOST=ultrafeeder      # <-- change to the hostname of your local BEAST feeder

Then run:

docker compose up -d

This will start your feeder client and keep it running in the background. Experienced users may modify environment variables or network settings to match their local setup.

ADSB.im Integration

If you use ADSB.im, follow these steps:

1. Go to your ADSB.im setup page.
2. Switch to the Settings > Expert tab.
3. Find the field for Ultrafeeder arguments, usually the top left.
4. Paste the following string and press submit:

adsb,feed.mlat.uk,30004,beast_reduce_plus_out;mlathub,feed.mlat.uk,30104,beast_reduce_plus_out;

Once configured, ADSB.im will forward your anonymous data to feed.mlat.uk. No need to install a separate client.

AIS-Catcher Integration

If you want to contribute vessel data via AIS, you can use AIS-Catcher as an example. The data is sent to feed.mlat.uk on port 5001.

Using Docker Compose:

Add the folling argument to your docker-compose file

- UDP_FEEDS=feed.mlat.uk:50001

Or using the command line:

-u feed.mlat.uk 50001

This will forward your AIS vessel data directly to mlat.uk. Ensure your network allows outbound UDP traffic to port 50001.

Once running, your vessel data will appear on the mlat.uk map alongside aircraft data, providing a combined real-time view.

Advanced Feeder Configuration

This section is for advanced users who want to directly configure a feeder to send data to feed.mlat.uk. Only attempt this if you are familiar with your feeder’s configuration options.

Recommended settings:

• Protocol: BEAST
• Output format: beast_reduce_plus_out

Endpoints:

• ADSB: adsb,feed.mlat.uk,30004,beast_reduce_plus_out;
• MLATHUB: mlathub,feed.mlat.uk,30104,beast_reduce_plus_out;
• AIS: feed.mlat.uk:50001

Testing or forwarding ADS-B and MLAT with net connector:

Please note I have not tested these settings, please let me know if they work!

Net Connect:

• ADSB: --net-connector feed.mlat.uk,30004,beast_reduce_plus_out
• MLAT: --net-connector feed.mlat.uk,30104,beast_reduce_plus_out

Ensure your feeder has network connectivity to feed.mlat.uk and that any firewall or NAT rules allow outbound traffic to ports 30004, 30104, and 50001 for AIS.

To check if your feeder is online, visit our feeders page . The end of your public IP is shown as your IP for identification.

Privacy

We do not log any personally identifiable information. This ensures all contributions remain private while still helping improve mlat.uk coverage.