Icing layer issues with GPilot Web

Is a fix in the works for GPilot Web concerning it misinterpreting the icing forecast raw gridded binary files; swapping Trace & Severe/Extreme?

I have several screenshot samples of Web iOS in conflict, but unable to upload the images. I use AWC Icing as the tie breaker and GPilot iOS is correct.

The misidentification is easy to understand as to how an error in programing could occur in that v2 of the table added intensities, those additions, the numeric values did not represent the intensity scale of icing.

GRIBv2 Code Table 4.207

Code Figure	Meaning
0	None
1	Light
2	Moderate
3	Severe
4	Trace
5	Heavy
6-191	Reserved
192-254	Reserved for Local Use
255	Missing

0 Michael Reamy 10 days ago

The last portion of the last sentence would be better worded as...

..."the numeric values did not represent a linear increase of the intensity scale of icing." The original scale was 0 through 3, None to Severe. With the GRIBv2 change, Trace became 4 and Heavy became 5 on the scale. The original code table sequence could not be be changed, they had to go to code 4 and 5. GPilot iOS accounted for the change as did AWC and many other presentations. I suggest these last two are swapped in the coding of GPilot Web.

0 Michael Reamy 2 days ago

The issue with the Garmin Pilot Web Trace vs. Heavy icing layers has been resolved.