Output JSON_FULL over TCP/UDP?

[shawaj]

In the docs, regarding the TCP client, it has the JSON output:

https://docs.aiscatcher.org/configuration/output/TCP-client/

Is it possible to configure this to output the fully decoded JSON output (same as -o 5) in some way?

I noticed the MQTT can do this using JSON_FULL but this doesn't seem to work with the TCP or UDP output from what I can see?

Or is there a different way to force this?

[shawaj]

Just found this... #324 (reply in thread)

So can I guess I can use AIS-catcher -P 192.168.1.235 4002 JSON_FULL on?

[jvde-github]

yes, that works and should be added to the documentation, it works for -S, -P and -u

[shawaj]

@jvde-github in the comment here #324 (reply in thread)

You mention JSON ON but JSON_FULL on

I am guessing capitalisation doesn't matter for either of these? And from testing I noticed that JSON true worked as well - is that also the case for JSON_FULL?

Happy to add some notes to docs etc.

And thanks for the fantastic software! Getting great range in the gulf due to ducting (after doing some heat-management - saw the CPU go over 95 degrees today in the full sun lol)

[jvde-github]

Hi, it is case insensitive indeed. Either can use JSON on/off (to get the equivalent of -o 3) and JSON_FULL on/off (to get the equivalent of -o 5). You can either use on/off or true/false, but to be honest in the documentation I always use on/off to not overhelm users.

If you have time and energy to add to the documentation, would be highly appreciated. Otherwise happy to do so over the weekend.

Thanks! Jasper