I was watching a plane of interest today and was storing the information into a database. As I've noted here before, I'm using dump1090-af. Looking at the data I was getting from my pi, even though I was seeing reasonable positions of the aircraft in FA's SkyView, the lat lon data I was getting from /dump1090-fa/data/aircraft.json were all identical. Is this the FA MLAT problem that has been discussed here? If so, I'm ready to move on! How can I get the real fixes? I still want to feed Flight Aware and Adsbexchange, of course. I have an idling Raspberry Pi on hand. If I want to feed both do I need set up parallel hardware?
You get MLAT results from both services, that can result in positions jumping around. Or you will have an extra anonymous target with a hex starting with ~ displayed, that's FA anonymized MLAT results. And please, SkyView is just their name for the dump1090-fa webinterface. What do you mean the data was identical, compared to what? If you have tar1090 running it's just using the aircraft.json from /run/dump1090-fa. dump1090-fa doesn't do any filtering, that's all done server side at FA. Which i explained in the other post. Wasn't that other post your reason to post? I have no clue if you have adsbexchange setup correctly, so no clue if you're getting adsbexchange mlat results. Also please educate yourself and try to understand the data flows. While the following is an FA page, it's a good diagram. https://flightaware.com/adsb/piaware/about adsbexchange scripts will get data from port 30005, feed that and use it for MLAT. they will also put MLAT results into port 30004, which you then see in the dump1090-fa webinterface.
