Here is to inaugurate the forum with a request by email that I am pushing here to turn it public, with the Captain's consent.
CaptB wrote:I'd like to suggest a feature, not a burning request but an idea for the future.
One of the nice things in Euroscope is that I can see which ATC stations are online. It is a great tool that provides awareness of the surrounding ATC which unlike the real world, in our simulated environment can change dynamically. Without being aware of who is online it would be difficult to build a structure that works together hand in hand in regards to handoffs and coordination.
Here are my thoughts:
Use/scrape fgcom.flightgear.org frequency/station data.
Filter out data based on a relevant frequency list, and...
Filter out data based on callsign suffix ( _AP _TW etc. to exclude pilots )
By the way, shall we move this discussion to the forum, or stay here?
For me there are two pieces of answer, depending on what part of the "Euroscope" sentence is addressed.
see which ATC stations are online.
Unfortunately the FGMS protocol will NOT allow such thing, by design. It only sends you packets from the other connected clients that are in your 100 NM range. The workaround I see would be to interact with the mpserver12 tracker or something. Such feature could be useful for clearance del's, knowing if an airspace on the way is controlled or not, or to suggest destinations to pilots wanting ATC interaction...
Yet arguably:
- sessions announced on lenny64 are more appropriate;
- ATC-pie is a realistic radar first, things requiring full world knowledge are better addressed using online tools (mpmap02, mpserver12...).
To be discussed.
tool that provides awareness of the surrounding ATC
Now if you are only interested in SURROUNDING controllers, my answer will relate to WW's strip exchange server, enabling what he calls "FPL handoffs". Connected ATCs' positions are known so the server can inform them of ATCs in their 180 NM range if I remember well, enabling a minimum of 20 NM for hand over.
I have always promised handovers in ATC-pie, and so far considered that WW's server was the way to go because probably the only reasonable solution to allow ATCs to work together regardless of their software choice. So that would give you the feature you want.
Yet for this to happen, I need to work out the interaction as O-R/ATC-pie philosophies are a little different w.r.t. strips. You can see my detail comments on the project wish list page but in summary: WW's server has the notion of "ownership" of a contact, OpenRadar then preventing taking ownership of a strip if it is owned by anyone else, whereas ATC-pie lets ATC manage his/her strips and link them to radar contacts freely. So I need to work out a design and check with WW (perhaps he'll as happily discuss this here) against the actual behaviour of his server before releasing anything.