-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iwxxm.sch bugs involving SIGMET.SIGMETPosition-2 and SIGMET.SIGMETEvolvingCondition-5 #293
Comments
The following are proposed changes to the two schematron rules:
|
It was noticed that some States were not coding the example in the APAC SIGMET Guide mentioned in #250 correctly: While iwxxm:TropicalCycloneSIGMET/iwxxm:analysisCollection has a multiplicity of [0..*], in this case there shall only be one iwxxm:analysisCollection describing the TC positions and their associated CB clouds. The remaining descriptions after "AND" in the TAC message shall be coded under iwxxm:supplementaryAnalysisCollection. It is therefore further proposed to include a new schematron rule to enforce the use of only one iwxxm:analysisCollection in a iwxxm:TropicalCycloneSIGMET:
|
https://github.com/wmo-im/iwxxm/wiki/TT-AvData-Teleconference-2022-Dec-09 notes:
|
Describe the bug
SIGMET.SIGMETPosition-2 and SIGMET.SIGMETEvolvingCondition-5 in iwxxm.sch of IWXXM Version 2012-2 triggered incorrectly when a TC SIGMET report is being encapsulated in a COLLECT construct.
To Reproduce
The example (https://gist.github.com/blchoy/0d28a25aaf91ef41cb1e3b8c593a48db) created by encapsulating sigmet-A6-2-TC.xml in a COLLECT construct cannot pass the schematron check of iwxxm.sch.
Expected behavior
The example should pass the checks of the two schematron rules.
Screenshots
Not applicable.
Desktop (please complete the following information):
Not applicable.
Additional context
Not applicable.
The text was updated successfully, but these errors were encountered: