search

vatis-project / vatis-archive

Virtual Automated ATIS Generator for VATSIM
https://docs.vatis.clowd.io
GNU General Public License v3.0
38 stars 20 forks source link

Variable wind shows incorrectly #144

Open YuchenChien opened 1 year ago

YuchenChien commented 1 year ago

> ZHHH DEP ATIS D 1400Z DEP RWY 04L. CTN SEGREGATED OPERATION WIND 110 DEG 03 MPS 070V140 DEG 070V140 CAVOK T 29 /DP 21 QNH 1007 HPA TRANSITION ALTITUDE 3000 M RPT RECEIPT OF ATIS D ON ZHHHDEP

_WIND {wind_dir} DEG {wind_spd} MPS {wind_vmin}V{windvmax} DEG

The formatting had been modified as below, as real as possible to the real-life D-ATIS. You can easily track the variable wind formatting 070V140 DEG 070V140 , I couldn't find the solution to remove the last 070V140.

YuchenChien commented 1 year ago

or any solutions to show it as WIND 110 DEG 03 MPS 070V140 DEG ?

justinshannon commented 1 year ago

Can you upload the Composite configuration file (export it) so I can see how you currently have it formatted?

YuchenChien commented 1 year ago

Unfortunately, I didn't save it. Standby ; (

YuchenChien commented 1 year ago

Can you upload the Composite configuration file (export it) so I can see how you currently have it formatted?

composite.txt

YuchenChien commented 1 year ago

In this case, there's always showing "DEG" although no variable direction, I don't think it is the best method to realize it ; ( Could you teach me that how to achieve the format as WIND 110 DEG 03 MPS 070V140 DEG whatever the variable direction shows or not.

justinshannon commented 1 year ago

Sorry for the confusion. vATIS will automatically append the variable direction, so there's no need to add it to the Standard template. The Standard template is only meant to change the format of the standard wind portion (e.g. 11002MPS).

What you should do is first remove {wind_vmin}V{wind_vmax} DEG from the Standard template. Then change the Variable Direction template to {wind_vmin}V{wind_vmax} DEG. This should yield your desired formatting.

YuchenChien commented 1 year ago

Sorry for the confusion. vATIS will automatically append the variable direction, so there's no need to add it to the Standard template. The Standard template is only meant to change the format of the standard wind portion (e.g. 11002MPS).

What you should do is first remove {wind_vmin}V{wind_vmax} DEG from the Standard template. Then change the Variable Direction template to {wind_vmin}V{wind_vmax} DEG. This should yield your desired formatting.

Sounds good, thanks.

YuchenChien commented 1 year ago

Sorry for the confusion. vATIS will automatically append the variable direction, so there's no need to add it to the Standard template. The Standard template is only meant to change the format of the standard wind portion (e.g. 11002MPS).

What you should do is first remove {wind_vmin}V{wind_vmax} DEG from the Standard template. Then change the Variable Direction template to {wind_vmin}V{wind_vmax} DEG. This should yield your desired formatting.

BTW, can I modify it through UI? Must I modify it through the exported file?

justinshannon commented 1 year ago

It can be customized through the UI. https://docs.vatis.clowd.io/#/client?id=formatting

YuchenChien commented 1 year ago

In this case, there's always showing "DEG" although no variable direction, I don't think it is the best method to realize it ; ( Could you teach me that how to achieve the format as WIND 110 DEG 03 MPS 070V140 DEG whatever the variable direction shows or not.

OMG, is it such a bug with the UI? My system is Win10 64bit image

justinshannon commented 1 year ago

Something funky on your end. The UI displays fine on my computer.

YuchenChien commented 1 year ago

Something funky on your end. The UI displays fine on my computer.

Hi, I have another question to ask.

Some airports or TMA areas need a specific QNH value. Could you please add a variable, which will use a QNH value of another airport.

For example, in Shanghai TMA area, it's busy with 2 major airports, ZSSS and ZSPD. Pilots need to set their QNH as ZSPD while the altitude above 900M (3000 ft) in the TMA airspace, whatever the destination is ZSPD or ZSSS. In this case, the realistic D-ATIS has such a sentence QNH OF SHANGHAI TERMINAL CONTROL AREA ****.

So the problem is, the QNH value of ZSSS and ZSPD may different. e.g. QNH of ZSSS is 1013, while QNH of ZSPD is 1014. If I am online as ZSSS, the QNH of TMA is not exact, even wrong.

YuchenChien commented 1 year ago

ZSPD ATIS F 1030Z EXPECT 17R ILS APPROACH 16L ILS APPROACH ARR RWY 17R AND 16L. DEP RWY 17L AND 16R. CTN WHEN AIRBORNE ALL DEPARTING A/C SHALL CTC SHA APP W/O INSTRUC APP FREQ 122.8 QNH OF SHANGHAI TERMINAL CONTROL AREA 1010 WIND 150 DEG 05 MPS VIS 9999 BKN 003M T 19 /DP 17 QNH 1010 HPA RPT RECEIPT OF ATIS F ON ZSPD

The current METAR is ZSPD 201030Z 15005MPS 9999 BKN013 19/17 Q1010 NOSIG For the realistic D-ATIS as following, is it possible to convert 013 to 390 or 400 (1300ft * 0.3) IMG_7044

justinshannon commented 1 year ago

ZSPD ATIS F 1030Z EXPECT 17R ILS APPROACH 16L ILS APPROACH ARR RWY 17R AND 16L. DEP RWY 17L AND 16R. CTN WHEN AIRBORNE ALL DEPARTING A/C SHALL CTC SHA APP W/O INSTRUC APP FREQ 122.8 QNH OF SHANGHAI TERMINAL CONTROL AREA 1010 WIND 150 DEG 05 MPS VIS 9999 BKN 003M T 19 /DP 17 QNH 1010 HPA RPT RECEIPT OF ATIS F ON ZSPD

The current METAR is ZSPD 201030Z 15005MPS 9999 BKN013 19/17 Q1010 NOSIG For the realistic D-ATIS as following, is it possible to convert 013 to 390 or 400 (1300ft * 0.3)

This is already possible if you enable the Convert cloud layer altitude to metric option in the cloud formatting options.

YuchenChien commented 1 year ago

ZSPD ATIS F 1030Z EXPECT 17R ILS APPROACH 16L ILS APPROACH ARR RWY 17R AND 16L. DEP RWY 17L AND 16R. CTN WHEN AIRBORNE ALL DEPARTING A/C SHALL CTC SHA APP W/O INSTRUC APP FREQ 122.8 QNH OF SHANGHAI TERMINAL CONTROL AREA 1010 WIND 150 DEG 05 MPS VIS 9999 BKN 003M T 19 /DP 17 QNH 1010 HPA RPT RECEIPT OF ATIS F ON ZSPD

The current METAR is ZSPD 201030Z 15005MPS 9999 BKN013 19/17 Q1010 NOSIG For the realistic D-ATIS as following, is it possible to convert 013 to 390 or 400 (1300ft * 0.3)

This is already possible if you enable the Convert cloud layer altitude to metric option in the cloud formatting options.

I had done before. It convert as above.

YuchenChien commented 1 year ago

It seemed that the BKN013 had been converted to BKN003 ; (

justinshannon commented 1 year ago

How is it read by the voice ATIS? Should vATIS automatically append the word "meters" after the cloud layer height? For example, "THREE HUNDRED AND NINETY METERS"?

YuchenChien commented 1 year ago

How is it read by the voice ATIS? Should vATIS automatically append the word "meters" after the cloud layer height? For example, "THREE HUNDRED AND NINETY METERS"?

Let me check, standby.

YuchenChien commented 1 year ago

How is it read by the voice ATIS? Should vATIS automatically append the word "meters" after the cloud layer height? For example, "THREE HUNDRED AND NINETY METERS"?

I can hardly hear the voice ATIS, there's no sound heard.

YuchenChien commented 1 year ago

But I'm sure that the Convert cloud layer altitude to metric has been enabled.

justinshannon commented 1 year ago

I am fixing the cloud layer metric conversion.

I'm asking whether I should have vATIS automatically include the word "meters" after the cloud height. Otherwise, it will just speak "THREE HUNDRED AND NINETY" in the voice ATIS.

YuchenChien commented 1 year ago

I am fixing the cloud layer metric conversion.

I'm asking whether I should have vATIS automatically include the word "meters" after the cloud height. Otherwise, it will just speak "THREE HUNDRED AND NINETY" in the voice ATIS.

I cannot hear anything ; (

justinshannon commented 1 year ago

I am fixing the cloud layer metric conversion. I'm asking whether I should have vATIS automatically include the word "meters" after the cloud height. Otherwise, it will just speak "THREE HUNDRED AND NINETY" in the voice ATIS.

I cannot hear anything ; (

This is just a question if I should have vATIS add the word "meters" after the cloud height, because currently it does not.

justinshannon commented 1 year ago

Something funky on your end. The UI displays fine on my computer.

Hi, I have another question to ask.

Some airports or TMA areas need a specific QNH value. Could you please add a variable, which will use a QNH value of another airport.

For example, in Shanghai TMA area, it's busy with 2 major airports, ZSSS and ZSPD. Pilots need to set their QNH as ZSPD while the altitude above 900M (3000 ft) in the TMA airspace, whatever the destination is ZSPD or ZSSS. In this case, the realistic D-ATIS has such a sentence QNH OF SHANGHAI TERMINAL CONTROL AREA ****.

So the problem is, the QNH value of ZSSS and ZSPD may different. e.g. QNH of ZSSS is 1013, while QNH of ZSPD is 1014. If I am online as ZSSS, the QNH of TMA is not exact, even wrong.

Could it be useful to have a separate {altimeter} variable that allows you to specify the ICAO code for any airport you want? For instance, by using {altimeter|zsss} or {altimeter|zspd}, you would receive the QNH value for the chosen airport.

YuchenChien commented 1 year ago

I am fixing the cloud layer metric conversion. I'm asking whether I should have vATIS automatically include the word "meters" after the cloud height. Otherwise, it will just speak "THREE HUNDRED AND NINETY" in the voice ATIS.

I cannot hear anything ; (

This is just a question if I should have vATIS add the word "meters" after the cloud height, because currently it does not.

Aha, sorry for my misunderstanding. It doesn't require it I think, thanks.

YuchenChien commented 1 year ago

Something funky on your end. The UI displays fine on my computer.

Hi, I have another question to ask. Some airports or TMA areas need a specific QNH value. Could you please add a variable, which will use a QNH value of another airport. For example, in Shanghai TMA area, it's busy with 2 major airports, ZSSS and ZSPD. Pilots need to set their QNH as ZSPD while the altitude above 900M (3000 ft) in the TMA airspace, whatever the destination is ZSPD or ZSSS. In this case, the realistic D-ATIS has such a sentence QNH OF SHANGHAI TERMINAL CONTROL AREA ****. So the problem is, the QNH value of ZSSS and ZSPD may different. e.g. QNH of ZSSS is 1013, while QNH of ZSPD is 1014. If I am online as ZSSS, the QNH of TMA is not exact, even wrong.

Could it be useful to have a separate {altimeter} variable that allows you to specify the ICAO code for any airport you want? For instance, by using {altimeter|zsss} or {altimeter|zspd}, you would receive the QNH value for the chosen airport.

Great! That's the best solution I wanted.

YuchenChien commented 1 year ago

ZSPD ATIS F 1030Z EXPECT 17R ILS APPROACH 16L ILS APPROACH ARR RWY 17R AND 16L. DEP RWY 17L AND 16R. CTN WHEN AIRBORNE ALL DEPARTING A/C SHALL CTC SHA APP W/O INSTRUC APP FREQ 122.8 QNH OF SHANGHAI TERMINAL CONTROL AREA 1010 WIND 150 DEG 05 MPS VIS 9999 BKN 003M T 19 /DP 17 QNH 1010 HPA RPT RECEIPT OF ATIS F ON ZSPD

The current METAR is ZSPD 201030Z 15005MPS 9999 BKN013 19/17 Q1010 NOSIG For the realistic D-ATIS as following, is it possible to convert 013 to 390 or 400 (1300ft * 0.3) IMG_7044

And I've tried the format CLOUD XXX, when the condition is NSC or some abstract cloud condition, it should be NSC only.

YuchenChien commented 1 year ago

For another request, could you please add an option for "CAVOK" in the "ICAO formatting“? Because of the form, I'd like to take "CAVOK" only instead of "VIS CAVOK".

RudiZhang commented 8 months ago

Something funky on your end. The UI displays fine on my computer.

Hi, I have another question to ask. Some airports or TMA areas need a specific QNH value. Could you please add a variable, which will use a QNH value of another airport. For example, in Shanghai TMA area, it's busy with 2 major airports, ZSSS and ZSPD. Pilots need to set their QNH as ZSPD while the altitude above 900M (3000 ft) in the TMA airspace, whatever the destination is ZSPD or ZSSS. In this case, the realistic D-ATIS has such a sentence QNH OF SHANGHAI TERMINAL CONTROL AREA ****. So the problem is, the QNH value of ZSSS and ZSPD may different. e.g. QNH of ZSSS is 1013, while QNH of ZSPD is 1014. If I am online as ZSSS, the QNH of TMA is not exact, even wrong.

Could it be useful to have a separate {altimeter} variable that allows you to specify the ICAO code for any airport you want? For instance, by using {altimeter|zsss} or {altimeter|zspd}, you would receive the QNH value for the chosen airport.

I think {altimeter|zsss} or {altimeter|zspd} was not included in beta15?