Visualizing NECOFS Inundation Forecast

[tshyka]

No description provided.

[ebridger]

This catalog seems to have the forecasts for BOSTON, HAMPTON, SCITUATE, MASSBAY updated daily.
http://www.smast.umassd.edu:8080/thredds/catalog/models/fvcom/NECOFS/Forecasts/catalog.html

[rsignell-usgs]

Step 1 complete: I have added the Hampton, Scituate, and Boston datasets to the UGRID-compliant forecast catalog here:
http://www.smast.umassd.edu:8080/thredds/forecasts.html
Next step is getting them into ncWMS2 or sci-wms.

[rsignell-usgs]

I dropped the DAP endpoint for Boston in my ncWMS2 server at
http://gamone.whoi.edu/ncWMS
http://gamone.whoi.edu/ncWMS/Godiva3.html
and it worked, but I'm guessing this isn't exactly what you want?

Looks like elevation is the water level or land level (when dry), and perhaps it's really the wet cells that are important:

So you might have to make your own displays, but at least the data is available!

[tshyka]

That's great that the data is available. If possible I think we would ideally like to mimic what the NHC is doing for visualizing storm surge forecasts and use a color ramp to show the forecasted height of water above the ground and then show the normal coastal water level with light blue.

[rsignell-usgs]

I used this notebook
http://nbviewer.jupyter.org/gist/rsignell-usgs/9ed505dc53fd7b0765ce675836c5ec58
to read water and depth levels from the SMAST NECOFS Hampton FVCOM forecast and created a new categorical variable in the output netcdf file (actually, I just overwrote the wavelength variable, figuring nobody cares about the dominant surface wave wavelength -- everyone just looks at the significant wave height and wave period).

If you make a categorical variable following the ncWMS2 specifications, you can serve it via WMS.

Here it is visualized in Godiva3 (go to http://gamone.whoi.edu/ncWMS/Godiva3.html, select the "Inundation_hampton" dataset, then the "wlen" variable):

Kind of boring because there isn't much going on right now, but wait until the next storm!

This is cool because you can just do these kind of categorical maps with fancy labels without using any fancy GIS stuff.

This could be useful for vulnerability indices, warning regions, or anything where different discrete levels or thresholds are involved.

[rsignell-usgs]

@tshyka , if this is deemed useful, we can refine this a bit and get Chen set up with code to do this automagically.

[tshyka]

This does seem very useful. Eric and Riley have you had a chance to look at this?

[rsignell-usgs]

@tshyka , you mean @ebridger and @youngmorse? 🤓

[tshyka]

@rsignell-usgs , thanks for the cyber grammar correction. It's no longer dotting your i and crossing your t but making sure you know where the @ is @.

[ebridger]

Very cool @rsignell-usgs. Can't wait to see this with a street map base layer.

[rsignell-usgs]

@ebridger, your wish is my command! 😁

Because it's WMS, it works in TerriaJS (Try it yourself!), so we can have nice street map layer and whatever else we want to put on there. There's currently an issue with the legend, however, that I'm trying to resolve (it's missing):