--forward-mlat to affect SBS/port 30003 output as well.

[Wilm0r]

(I was hoping to file a bug first to ask why this may be a bad idea, but this seems to be disabled.)

I'm having various things scrape the SBS/port 30003 output to do graphing etc, and only now realised that MLAT data isn't included there. Is there any reason why the --forward-mlat flag so far did not include that channel? If not, is this a sensible PR?

I'm running this version here now and it produces the expected output, now including the various GA planes flying around here.

[mutability]

It is deliberately disabled because there is no way to indicate in the output that the position is a synthetic position, not real ADS-B data from the aircraft. In the past this has caused problems with this data then being fed to aggregators (piaware, etc) that don't want to see synthetic data.

Please consider using a different data format - the port 30003 format is very legacy and has all sorts of problems.

[Wilm0r]

Ahh, thanks for the detail! I didn't know some people were still feeding from port 30003.

Please consider using a different data format - the port 30003 format is very legacy and has all sorts of problems.

Hmm, for me it has always been the most friendly and easy one to parse, the other ones being more raw or even binary. Is there another one that already went through enough processing that I can just grep out coordinates?

[mutability]

If you're interested in snapshot of aircraft state, rather than a strictly message-by-message feed, then look at the json files that dump1090 writes (in particular aircraft.json).

If you do need message-by-message data then keep in mind that ADS-B is a messy protocol where the receiver actually needs to be stateful, you can't just look at individual messages in isolation..

[Wilm0r]

Just ran into https://github.com/junzis/pyModeS which looks promising. No mention of mlat (recognising which messages contain mlat-derived data) but let's start digging. Thanks :)