Ah yes I meant raw. Sorry about that! Everything else is perfectly understandable. If UAT is going to be used, programs like VRS and such should understand UAT data as it does contain a lot more info than most ADS-B and 1090mhz data generally, and like you said you lose info in the translation down to the most common level. However I see this as coming very slow, as UAT is only supported in the United States for now. For now, this translation works to just get the planes on my VRS map… a basestation output would be VERY helpful so custom scripting wouldn’t be needed, not that running one command is hard for now.
FYI, this is the final command you want to run. The other one I had I slipped “fork” option in accidentally, which ran a new socat process. After a few days I had a hundred or so socat processes, which sent my Pi’s CPU close to 70C 
I also added a loop. Simply follow Step #1 above to compile uat2esnt, then write this file somewhere. chmod u+x it, and you’re good! It will output AVR Beast data on port 30977 in this example.
#!/bin/bash
while true
do
socat -u tcp4-connect:127.0.0.1:30978,forever,interval=5 STDOUT | /home/pi/builds/dump978/uat2esnt | socat -u STDIN tcp4-listen:30977,forever,interval=5
sleep 1
done