Shunsuke Yamabe 1162075 Posted August 25, 2014 at 11:09 AM Posted August 25, 2014 at 11:09 AM First of all, thank you very much for your offering such a helpful application. vATIS worked fine, but I have only one request about QNH. vATIS seems to interpret "Q1013" on the METAR as "QNH 1013", and "A2991" as "ALTIMETER 2991". In some countries including Japan, raw METAR text reports QNH in hPa. But ATC and ATIS reports in inches, and hPa-value is never used. Thus, we always have to calculate 2991 + (QNH - 1013)*3 to report altimeter. For example, if the METAR is following, ATC and ATIS sais "QNH 2991 inches" (not ALTIMETER, but QNH usually ). "RJTT 251000Z 09006KT 9999 -SHRA FEW020 BKN070 27/22 Q1013". By the circomestances of these, I would like to request and suggest 1. Function to convert QNH(hPa) on the METAR text to ALTIMETER(inches) 2. It would be very nice if "QNH XXXX INCHES" format were available. Of course I understand these are problems of special regions, but I would really appreciate it if you could take these into consideration. _________________ VATSIM JAPAN Shunsuke Yamabe (I1/P1) Link to comment Share on other sites More sharing options...
Bradford Lee Posted August 25, 2014 at 11:50 AM Posted August 25, 2014 at 11:50 AM Haven't tested it myself, but I think you should be able to edit the calculated ATIS text to add the word "inches" where needed. As far as vATIS reading QNH but not being able to do the math to convert to altimeter, again until a fix is released see if you can manually change the text after doing the math. Brad Lee ZJX ARTCC Link to comment Share on other sites More sharing options...
Justin Shannon Posted August 25, 2014 at 04:18 PM Posted August 25, 2014 at 04:18 PM Thank you for your suggestions, Shunsuke. I'm just going to cut to the chase: I have no plans on adding special parsing rules. vATIS was built with the purpose of simulating the real world D-ATIS system used throughout the United States. There are way too many different parsing and configuration options to take into account when making a non-US ATIS as accurate and realistic and possible. Considering this, if you're looking for a true realistic and more accurate ATIS, I suggest you use Euroscope, which gives you way more control with the ATIS. If I start adding feature X, then someone will want feature Y...and pretty soon the application will become just too bloated and difficult to maintain. @Brad: no, it's not possible to edit the TTS text output. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Recommended Posts