0

Warning/Advisory displaying as an underlay?

William DePriest

October 17, 2019 17:24

Completed

Follow

I've noticed that for the past several weeks(?) any watch, warning, or advisory for several counties in Maryland (Anne Arundel - MDZ014 for example) is displayed incorrectly. It looks almost like it is being painted as an underlay, as you can see it around the coastline. Currently a Wind Advisory is in effect, with surrounding zones painted correctly, while Anne Arundel (and a few others) are not.

• Facebook
• Twitter
• LinkedIn

7 comments

• 
  Ryan Hickman April 04, 2020 17:29 Official comment

   

  I'm not quite understanding what the issue is here. Are you selecting the second checkbox in the GRx Placefile Manager? Is it possibly your opacity settings?

  We're not deliberately making anything an "underlay" and that's actually not even possible with placefiles. Is the issue that some look different than others? It could be due to there being 2 "zone matches" for the same county/zone which is definitely something we can look into.

  Feel free to email me directly with any additional information you can provide. I'm happy to look into this and get it resolved for you as we've recently been reworking our zone database to automatically update every quarter with the changes at NOAA/NWS.

• 0
  
  William DePriest April 01, 2020 12:49

  Hi, I just wanted to see if there has been any progress on this. The bug persists, and can be seen in the attached image.

• 0
  
  William DePriest April 04, 2020 19:35

  Hi Ryan,

  Thanks for the reply. In the image above, the county just to the north (where Annapolis is) of the one in green is also under a coastal flood advisory. As displayed, only the coastal portions of the county are highlighted. The entire county should be painted like the one to the south of it. There are several others around that seem to have the same issue.

• 0
  
  Ryan Hickman April 04, 2020 20:46

   

  I see what's happening. The zone database has two separate entries since the polygon is so complex. I'll be testing some solutions throughout the weekend to see if I can't get this resolved.

  Thanks for your patience.

• 0
  
  Ryan Hickman April 04, 2020 20:52

   

  Correction: I've made a change which I believe will fix this right now. I need to confirm the updated zone database has complete coverage but this should fix things.

• 0
  
  William DePriest April 04, 2020 20:55

  Excellent! Thanks Ryan!

• 0
  
  William DePriest April 04, 2020 23:34

  Hi Ryan,

  I just confirmed that the advisory is displaying correctly now. Thanks again for such a quick solution!