Adapt WX info text to vATIS sensitivities
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
The payload names no source file, so first find where the WX info text is assembled before it is pasted into vATIS APT CONDs. Then check how the listed cases are handled: units like 3MM and 100PCT need a space, Y3 needs a TWY prefix, 01L needs RWY, and colons and double spaces must be removed. Done means these rewrites are applied and the wiki's formatting rules are met. The issue asks for the rules without defining their scope, so confirm the intended behaviour with the maintainers first.
Written by the indexing model from the issue text.
Description
To avoid common errors in ATIS, use some rewrite rules on the WX info that you typically copy-paste into vATIS APT CONDs.
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Now that winter has arrived, here is a reminder to check ATIS contents and output carefully, especially when runway surface conditions are included, as vATIS is quite sensitive. If unsure of the output, always listen to the ATIS by adding the ATIS station in AFV/Trackaudio.
Be familiar with the formatting as described on the vATIS wiki page: https://wiki.vatsim-scandinavia.org/books/gen-k9C/page/vatis
Some examples:
- 3MM or 100PCT will NOT be recognised correctly, so make sure there is a space after the number: 3 MM / 100 PCT 👍
- Y3 will be read out as "why three", whereas TWY Y3 will be read out as "taxiway yankee three"
- 01L must be preceded by "RWY" for the ATIS to read it correctly, i.e. RWY 01L 👍
- Colons ( : ) and double spaces ( ) causes text after the symbol to be ignored, so make sure to remove any colons/double spaces.
- At ESSA, the DEP ATIS should include conditions for the DEP RWY only and ARR ATIS should have conditions for the ARR RWY only. Make sure the format is correct, i.e. RWY 01L SCC 5 5 5 👍 (NOT just "01L SCC 5 5 5" 👎 )
If you have any questions, don't hesitate to reach out. 🙂
<@&759791336978907136> <@&759788985458360370> <@&759789037107675136> <@&759789034263412736>
- Dominant language
- Vue
- Stars
- 13
- Forks
- 7
- Avg merge
- 23h 1m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from minsulander/vatiris
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
minsulander/vatiris#194 ·
-
Add foreign ED+EK areas to AUP parserPossibly taken @maxlk96 claimed this 2 days ago. Openenhancement
minsulander/vatiris#195 · 1 assignee ·
-
bug
Difficulty 3/5 Half a day Newbie friendliness 45/100
minsulander/vatiris#185 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 18/100
minsulander/vatiris#184 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
minsulander/vatiris#183 ·
All issues in minsulander/vatiris
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
marmelab/atomic-crm#401 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Deltares/webgl-streamline-visualizer#83 ·
Maintainers usually reply within 1 day
-
level2 nsoc26
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
GauravKarakoti/SecureFlow#1486 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mfreed7/xslt_polyfill#58 ·