<p>Yes, in your example, the group should have been omitted. From the <a href="http://www.wmo.int/pages/prog/www/WMOCodes/WMO306_vI1/VolumeI.1.html" rel="nofollow noreferrer">WMO Publication No. 306 - Manual On Codes - Volume I.1 - Part A</a>, Section A, FM 12 SYNOP:</p>

<blockquote>
  <p>12.2.7 <em>Group</em> 8N<sub>h</sub>C<sub>L</sub>C<sub>M</sub>C<sub>H</sub></p>
  
  <p>12.2.7.1 This group shall be omitted in the following cases:</p>
  
  <p>(a) When there are no clouds (N = 0);</p>
  
  <p>(b) When the sky is obscured by fog and/or other meteorological phenomena (N = 9);</p>
  
  <p>(c) When the cloud cover is indiscernible for reasons other than (b) above, or observation is not made (N = /).</p>
</blockquote>

<p>metaf2xml tries to stick to the <em>Manual</em> but tolerates deviations, so the group is recognized but marked as invalid.</p>

CC BY-SA 4.0
2018-05-27T06:12:14.700Z
For questions about or things not working in metaf2xml there's always the [ticket system](https://sourceforge.net/p/metaf2xml/_list/tickets) for the project at SourceForge.
Thomas
CC BY-SA 4.0
2018-05-26T13:55:18.477Z
2018-05-27T06:10:53.163Z
2018-05-27T06:10:53.163Z
Thomas
<p>SYNOP code (see <a href="http://weather.unisys.com/wxp/Appendices/Formats/SYNOP.html" rel="nofollow noreferrer">http://weather.unisys.com/wxp/Appendices/Formats/SYNOP.html</a>) has a field for describing cloud types by different levels, given as "8NCCC" (see link for further info, Cloud type information). And there is a program for converting SYNOP to XML, <a href="http://metaf2xml.sourceforge.net/" rel="nofollow noreferrer">http://metaf2xml.sourceforge.net/</a>, which in most cases seems to work. However, when the cloud code is "80000", which IMO is correct for a cloudless sky, then the program says "invalidFormat". So does anybody know if "80000" is correct or not?</p>

<p>Edit:
"AAXX 11003 63658 32970 00905 10207 20060 38860 48492 80000 333 58002 555 10130"
Real life example showing that total cloud cover in previous section is also 0. Does this mean that when <code>total cloud cover = 0</code> is already given, then the section about cloud types is anyway meaningless?</p>

CC BY-SA 3.0
2018-04-12T13:01:23.840Z
There us also total cloud cover in part 'Nddff', perhaps the converting system is smart enough to yell error if these two informations aren't in agreement.
Communisty
<synoptic>
Cloudless sky in synop message?
kakk11
# Cloudless sky in synop message?

(Asked by: username_0 on 2018-04-12)

SYNOP code (see <http://weather.unisys.com/wxp/Appendices/Formats/SYNOP.html>) has a field for describing cloud types by different levels, given as "8NCCC" (see link for further info, Cloud type information). And there is a program for converting SYNOP to XML, <http://metaf2xml.sourceforge.net/>, which in most cases seems to work. However, when the cloud code is "80000", which IMO is correct for a cloudless sky, then the program says "invalidFormat". So does anybody know if "80000" is correct or not?

Edit:
"AAXX 11003 63658 32970 00905 10207 20060 38860 48492 80000 333 58002 555 10130"
Real life example showing that total cloud cover in previous section is also 0. Does this mean that when `total cloud cover = 0` is already given, then the section about cloud types is anyway meaningless?

**Tags:** synoptic

> **Comments:**
> **username_1**: There us also total cloud cover in part 'Nddff', perhaps the converting system is smart enough to yell error if these two informations aren't in agreement.  

---

## 1 answers

### Answer by username_2 on 2018-05-26. Score: 2 | Accepted answer

Yes, in your example, the group should have been omitted. From the [WMO Publication No. 306 - Manual On Codes - Volume I.1 - Part A](http://www.wmo.int/pages/prog/www/WMOCodes/WMO306_vI1/VolumeI.1.html), Section A, FM 12 SYNOP:

> 12.2.7 *Group* 8NhCLCMCH
>
> 12.2.7.1 This group shall be omitted in the following cases:
>
> (a) When there are no clouds (N = 0);
>
> (b) When the sky is obscured by fog and/or other meteorological phenomena (N = 9);
>
> (c) When the cloud cover is indiscernible for reasons other than (b) above, or observation is not made (N = /).

metaf2xml tries to stick to the *Manual* but tolerates deviations, so the group is recognized but marked as invalid.

> **Comments:**
> **username_2**: For questions about or things not working in metaf2xml there's always the [ticket system](https://sourceforge.net/p/metaf2xml/_list/tickets) for the project at SourceForge.  

---

