pedro2555
commented
5 years ago Allow me to discuss this further.
Our Scope
A shorter version of it is as follows:
All ATIS text and recordings are intended to be as close, as is possible on VATSIM, to the real ATIS provided by NAV Portugal at the respective airfields.
However the decision the scope of this project shall not change.
AFV
Audio For Vatsim is a fantastic introduction to the network. It is a gigantic technical challenge, and I'm sure those involved are extremely proud so far. But that is not to say everything is perfect.
One of those things is poor support for the fragmented ATIS systems between the vACCs.
AFV ATIS
Section 6.6 of the AFV User Guide specifies the ATIS system operation, in very crude detail.
The AFV ATIS server will synthesise the voice ATIS from the generated ATIS text.
The only information we are given at this point is that AFV ATIS server will synthesise voice from our text. Without much information how exactly that is done.
Conclusion
At this point in time is not clear how the AFV ATIS Server is supposed to behave without time consuming observations.
It is my understanding that the current AFV system is insufficient, in regard to ATIS broadcasts, for a wide number of cases throughout the vACCs. As such, modifications are expected in the near future to AFV ATIS.
Yet, there is no indication of the direction of those changes or feedback protocols with those responsible for the various, fragment, ATIS systems in use. Further more, the supposition of changes in the near future, is entirely my own, and should be viewed as an informed guess.
The wise decision then, is to wait and see.
In the Mean Time
Controllers are advised to decide on their own, as far as this project is concerned. The following could be said:
- Connect the ATIS as you normally do. The text version suffers no change, the audio version is not provided by this project.
- Use alternative ATIS systems. They suffer the exact same as this project. One may find that a specific product works better with AFV ATIS Server than another.
- Do not connect an ATIS. Personally I believe this is best way forward, and from my casual observations I may not be the only one, as there are various airports operating without an ATIS system. Pilots can obtain the same METAR they would have had in the ATIS with vPilot commands (.metar ICAO). Controllers can inform the pilots of their expected approach and expected vacate/departure positions for non familiar pilots.
Final Notes
This isn't ideal, by any means, but the current system is insufficient. And VATSIM should discuss this with the various vACCs. I stress this project is not affiliated with any vACC, although I'm available to participate in such discussions if they ever occur.
This is a great opportunity to de-fragment the current ecosystem, while providing a top notch expectations to pilots. Since, as it was true with AFV, there is no expectation drawn from the previous system.
This project is provided under the terms of GNU GPL v2. Portugal vACC is there fore completely free to change it as they see fit. With the only condition that they must make those changes available to this project.
prryplatypus
We need to keep current format in case they allow recorded ATIS again. In the meanwhile, we need to convert the abbreviations into plain text to correctly support AFV implementation.