17 thoughts on “New MLAT Regions!”

  1. That means a german receiver is no longer talking to a czech receiver? Just an example, but that’s the consequence I think?


  2. Yes. This method is a bit crude. However if you prefer to be in a different region, we can do that manually. Based on the large number of receivers I’m seeing in Western Europe (mainly UK and Netherlands) and Eastern US, we may need to further subdivide those regions, or overlay geographic regions depending on receiver range.

    If anyone has any ideas, let me know.


    1. Looks like some receivers are down since the new mlat structure. My 2nd station “EDDS” doesn’t report to adsbexchange anymore. FA works fine. Reboot didn’t help.


    1. Thanks Dan, can you confirm if the Western Europe region is still struggling as I can see the receiver icons but no coverage data?

  3. I set up a receiver specifically to cover the N/E of Germany. Now, I do not want to only be connected to receivers either in Poland OR in western Germany, I need to be contributing to both parts – because N/E Germany is a sparsely covered region. My station does not show any coverage west of it, anymore. This is not acceptable. It is paramount that my receiver adds to coverage of N/E Germany, specifically the military noise zone, ED-R 401 MVPA NE, which is half way decided now, by the new MLAT scheme. Up until now, this zone has been covered by receivers in Poland, east and west Germany, maybe some in Sweden, too. The new solution seems like a complete breakdown in MLAT coverage for this zone, compared to coverage before. Possible?

  4. Please draw the line eastern/western Europe somewhere around Polands eastern border. Otherwise coverage for Germany gets cut in half, with Berlin actually being in Eastern Europe. Ever since this cut off from all western receivers was established, MLAT is somewhat erratic and aircraft tracks are all over the place. It is a complete degradation of coverage. I invested into a good receiver because I wanted to up the MLAT coverage of N/E Germany, now it´s actually being massively degraded. Thanks!

  5. Yes. If it is worse than what we had on the other server, I may just put it back where it was. Even though there is no coverage data, it should still be plotting MLAT planes in Europe…

  6. OK, I just fell back to the other server, kept the regions, but moved back to the other server. Things _seem_ to be running better, but we won’t know until traffic kicks up tomorrow.

    It would seem that 16x 2.6 Ghz CPUs does not work as well as 4x 4.0 Ghz CPUs. I think there must be something single-threaded in there. I will investigate breaking up the regions onto different servers and getting higher clock-speed chips instead of just more cores.

  7. Thanks Dan, looks like the old server if doing ok now that Europe has woken up as I can at least see some coverage data plotted 🙂

  8. Still heavily loaded. Some users still probably having trouble connecting.

    Will provision another server shortly.


    1. 2 hours ago I upgraded from image 1.1 to 1.2! Before I was offline 95% of the day.
      Now, I don’t have any problems with the connection. Is there a difference between these 2 images that could cause these connecting problems?


  9. OK everyone, I brought another server online tonight that should hopefully address the issues. Also, the “dividing line” has been moved to +4 deg lon.

    All of you with issues in Germany and Poland due to the dividing line should be OK now. Also, with the addition of the new server, I am hopeful the load during the day should be better. We’ll find out in a few hours.


  10. Would you be able to overlap regions a bit?

    Like West, Midwest/Central, East?

    Currently you have these.
    Western US/Canada and Hawaii (Lon: -179 to -102)
    Eastern US/Canada and South America (Lon: -101 to -29)

    Could have a smaller region like Midwest/Central that overlaps?
    Say -105 to -99 that feeds both regions?

  11. Yes, but which receivers to you assign to which region in the overlap space?

    A receiver can only be in one region, unless they run two mlat-client processes.

Leave a Reply

Your email address will not be published. Required fields are marked *