search

wmo-registers / code-manuals

content upload processes for the manuals on codes
Creative Commons Zero v1.0 Universal
0 stars 7 forks source link

New Code Lists for AIRMET and VAA #44

Open braeckel opened 8 years ago

braeckel commented 8 years ago

As previously discussed, for IWXXM 2.0 (operational recommended ICAO practice starting in November 2016, software development currently underway) there is an urgent need for new WMO Codes to be publicly available in http://codes.wmo.int. This particular issue relates to two of the three new products in IWXXM: AIRMET, Volcanic Ash Advisory (VAA), and Tropical Cyclone Advisory (TCA).

For each register I've included a suggested location, but it is possible that I've missed an existing BUFR table that has the required information.

AIRMET http://codes.wmo.int/49-2/AirWxPhenomena - (ICAO Annex 3/ WMO No. 49-2 Appendix 6 Section 2.1):

http://codes.wmo.int/49-2/WeatherCausingVisibilityReduction - 0-20-025 is close but not quite correct - ICAO Annex 3/ WMO No. 49-2 Appendix 6 Section 2.1 under SFC VIS:

VAA http://codes.wmo.int/49-2/AviationColourCode - ICAO Annex 3/WMO No. 49-2 Appendix 2 Table A2-1:

marqh commented 8 years ago

Hello @braeckel

I am very happy to help with the upload process for this content. I can work up the details and push the results to our test instance as required for you.

However, I do not have authority on the content, this has to be approved by the relevant WMO contacts.

@6a6d74 please may you advise on this content request and consider who within WMO would be required to provide input on the fine details of this, names, URIs etc and sign off the results as ready to publish

thank you mark

marqh commented 8 years ago

hello @braeckel @6a6d74

I have prepared content, based on this information, which is encoded on this Pull Request: #48

Please may you look at the content https://github.com/wmo-registers/code-manuals/pull/48/files and let me know if anything is clearly wrong or poorly described

If these are reasonable, I can upload the content to our test system for wider review, please let me know your thoughts.

mark

braeckel commented 8 years ago

Hi @marqh @6a6d74

I've looked at the content and it looks good, but there are two things worth considering.

First, it may be worth putting in an official ICAO or WMO human-readable definition for the Aviation Colour Codes (RED, YELLOW, etc.). I just contacted ICAO to see if there is a document which defines these codes authoritatively since they don't appear to be defined in Annex 3 / WMO No. 49-2. I will provide official definitions once they have been found, hopefully in the next day or two.

Second - for WeatherCausingVisibilityReduction some of the contents may already be defined in WMO Codes, and rather than re-defining codes they could simply point to the existing code entries. For example, WeatherCausingVisibilityReduction has 'RA', which is also defined and presumably the same concept in http://codes.wmo.int/306/4678. It may be appropriate to implement WeatherCausingVisibilityReduction in a similar manner to http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather, which simply points to register items in code table 4678.

braeckel commented 8 years ago

With regards to the volcanic aviation colour codes, it appears that these are defined in ICAO Annex 15. I was not able to find any WMO references to these terms, so a fresh question might be whether and how these should be hosted in the WMO registry. Here are the definitions from Annex 15:

GREEN Volcano is in normal, non-eruptive state.

Or, after a change from a higher alert level: Volcanic activity considered to have ceased, and volcano reverted to its normal, non-eruptive state.

YELLOW Volcano is experiencing signs of elevated unrest above known background levels.

Or, after a change from higher alert level: Volcanic activity has decreased significantly but continues to be closely monitored for possible renewed increase.

ORANGE Volcano is exhibiting heightened unrest with increased likelihood of eruption.

Or, volcanic eruption is underway with no or minor ash emission [specify ash-plume height if possible].

RED Eruption is forecasted to be imminent with significant emission of ash into the atmosphere likely.

Or, eruption is underway with significant emission of ash into the atmosphere [specify ash-plume height if possible].

marqh commented 8 years ago

Hello @braeckel

I have updated the colour codes with descriptions, as you have sourced, this is on #48

mark

marqh commented 7 years ago

Hello @braeckel

i am happy to report that these code lists are adopted and published

https://codes.wmo.int/49-2/AirWxPhenomena https://codes.wmo.int/49-2/AviationColourCode https://codes.wmo.int/49-2/WeatherCausingVisibilityReduction

please follow up if there are problems with these

mark

braeckel commented 7 years ago

Hi @marqh,

thanks for populating this information. I've checked over all the new entries and they all look correct to me, with one exception. If you look at OCNL_TS in https://codes.wmo.int/49-2/AirWxPhenomena the name is different (shorthand instead of full description) from all the other entries in this register. Please change the name of "OCNL_TS" to "Occasional thunderstorms" to match the other entries in this table.

With regards to https://codes.wmo.int/49-2/WeatherCausingVisibilityReduction it appears that there is no relationship to the concepts in http://codes.wmo.int/306/4678. For example, I believe https://codes.wmo.int/49-2/WeatherCausingVisibilityReduction/RA is analogous to http://codes.wmo.int/306/4678/RA. An existing register example that does this is http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather, which simply points to register items in code table 4678. This is more of a policy question, just confirming that the current approach is preferred from the broader Codes Registry perspective.

Aaron

marqh commented 7 years ago

Hi @braeckel

Please change the name of "OCNL_TS" to "Occasional thunderstorms" to match the other entries in this table. this is fixed now http://codes.wmo.int/49-2/AirWxPhenomena/OCNL_TS

we will be adding relations between entities in a semantic manner in the future, and migrating some of the current entries to follow this newer pattern

I will make a start with these ones as soon as I can. May I ask you to re-interpret 'is analogous to' for me in this case.

would you say

There are places where this difference is crucial for the registry, in this case I'm not sure it is so crucial and I am also not sure which interpretation I find more useful

your thoughts on this are very much appreciated

mark

braeckel commented 7 years ago

Thanks @marqh.

Ultimately the semantic relationships seem to be a judgement call and both interpretations could be considered correct. However, I would be a bit more comfortable with the first interpretation ("rain in the context of causing visibility reduction a more narrow concept than the second, which is rain"). If, however, this ends up causing undesirable registry implications I would be comfortable with either interpretation.

On Thu, Jan 26, 2017 at 6:55 AM, marqh notifications@github.com wrote:

Hi @braeckel https://github.com/braeckel

Please change the name of "OCNL_TS" to "Occasional thunderstorms" to match the other entries in this table. this is fixed now http://codes.wmo.int/49-2/AirWxPhenomena/OCNL_TS

we will be adding relations between entities in a semantic manner in the future, and migrating some of the current entries to follow this newer pattern

I will make a start with these ones as soon as I can. May I ask you to re-interpret 'is analogous to' for me in this case.

would you say

There are places where this difference is crucial for the registry, in this case I'm not sure it is so crucial and I am also not sure which interpretation I find more useful

your thoughts on this are very much appreciated

mark

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/wmo-registers/code-manuals/issues/44#issuecomment-275393372, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgcQdHRE3GQh17bZ16OsfIqaNpAhuO5ks5rWKXUgaJpZM4IxXmv .

marqh commented 7 years ago

@braeckel I prefer the former too. I will conduct some further investigations and see if we can get to agreement and implement this

much obliged mark