Unexpected behavior: parsing cloud data

[brotherJ4mes]

Hi thanks for this great tool!

I just wanted to point out something that I found pretty unintuitive: A METAR message with "CLR" (indicating no clouds) is treated the same as a message with no reported cloud information.

In my particular use case, I was converting CLR|FEW|SCT|BKN|OVC to approximate numeric values (0, 25%, 50%, etc.) when I discovered that the resulting object's clouds attribute will be empty for "CLR". I would expect CLR to be in the description of clouds quantity. Especially since the same thing occurs if no cloud strings are present in the METAR code. I was able to easily work around this by parsing the original METAR message for these strings with basic regular expression matches.

I'm no METAR expert so perhaps I'm misunderstanding something but I would think (beyond my use case) the end user would want to make a distinction between the two cases:

• clear skies (essentially 0% cloud cover)
• missing cloud information (unknown cloud cover / NA)

[mivek]

Hello @brotherJ4mes

Thank you for your interest in the project.
The CLR was forgotten when implementing the parsing of the cloud layers. I will add it and publish a new version.

[mivek]

Hello @brotherJ4mes

The fix is available in version 1.10.2 of the project

[brotherJ4mes]

Thanks so much for fixing this! (I pip upgraded the package and it's working great)