[antirez]

Both works but perhaps using TCP port 30001 makes more sense in the context of a serious project:

1. Simpler to upgrade to a distributed setup.

2. Format is stable but with enough pre-parsed information, like the coordinates which are hard to extract.

3. The process doing the data collection can avoid to die together with dump1090 in case of crashes or USB errors. You just need a script to restart dump1090, and the ability to reconnect in the other side.

However I don't remember exactly how the SBS1 port data are ready-to-use exactly, and if there is too much work to do compared to just parsing the raw text output of the program.

[ihuman]

Do you mean 30002 (raw output over TCP)? I'm trying to get data out of dump1090, not feed it data. If that's the case, I'd still have to write my own decoder to process the raw adsb packets.

[antirez]

I mean 30003, that outputs things like:

MSG,4,,,738065,,,,,,,,420,179,,,0,,0,0,0,0 MSG,3,,,738065,,,,,,,35000,,,34.81609,34.07810,,,0,0,0,0

[ihuman]

That's what I've done in the past; I was just wondering if there was a better way.

[antirez]

I think one could open yet another port and output a JSON entry per line with much more information, and just don't care about the old standards.