[FEATURE] Port/Connection for radar/external viewer.

[Skipper-is]

Feature Description
Addition of a connection or protocol available to external viewers, such as a radar program, that would allow a view of the flights etc, without having to mirror the login process and pretend to be a client (a-la YS-QRadar).

How would this function work?
Could either be implemented within the standard client login process, where a truncated login process is used - eg:
login request with username "radar" and a version of 0 - bypasses all the other stuff like verifying aircraft lists, and just sends the necessary stuff.
Or:
Could implement a separate API, that is possibly able to take a GET request, and send the relevant info as JSON.
Why is this feature important?
Could allow quite a bit of functionality, from live webmaps of servers, to radars, to stats tracking.

[NodokaHanamura]

I know we already plan to implement clientside radar for ATC and AWACS, but I do agree having an API for headless 'agents' to access to a server with authentication would be something we can do as a good idea.

[Skipper-is]

Would also be a good tool for the server status pages to ping the server