The SLAMM salinity module is somewhat woefully underdocumented.  This is partially on purpose as it is somewhat experimental in nature.  However, we have more faith in the model after having recently successfully calibrated it to spatial salinity data in all five major Georgia estuaries.  Nonetheless it remains a "steady-state" salinity module and not a hydrodynamic model which is the consensus state of the art.

There are many additional data requirements as well as a requirement to carefully define the geometry of the salt wedge.  A "classic salt wedge" estuary is required for the model to be valid.  You need bathymetry data for all water sources in the model domain.  I bet that's the reason for your NODATA responses. 

If you are still interested in trying to apply the model after all those caveats, I'll try to start to work up a rough users manual for its implementation. 

We have also recently developed multiple linkages to external salinity models (one linkage by raster maps and one by river mile) so that may also be an option for your project if you want to apply a more general and typical salinity model.

Best regards

This is an excellent question.

The best data we have found and used so far is historical shoreline change data (under conditions of minimal SLR, as SLR inundation effects are considered to be independent of erosion effects within the SLAMM model).  In some projects we have separated out the coastline into many "subsites" with different baseline erosion rates that are assumed to continue into the future.  Even in this circumstance you are generally applying an average erosion rate to a beach rather than predicting which specific cells will disappear.

I would caution against using the Bruun rule, which applies to the "ocean beach" category only, as many researchers have abandoned this in favor of extrapolating forward with historical erosion rates.  The erosion formulation in SLAMM is quite simple and could stand to be replaced by a more mechanistic model in the future but we are searching for the best choice to implement there.  You can turn off the Bruun rule in the "Execute" window.

One more note, marsh and swamp erosion is only assumed to occur at the marsh and swamp to open water interface (fringing tidal flats and beaches are assumed protective, at least until they have eroded away).  Also, marsh and swamp erosion is only assumed to occur in locations with adequate wave setup (the current assumption is 9km of fetch).  So if you have shoreline change data for marshes and swamps, you don't want to average erosion rates where erosion is occurring and erosion is not occuring, but rather use measured erosion rates in locations where erosional loss is actually occurring as the model will then apply these rates only in areas where erosion is predicted to occur.

Finally, I recommend a sensitivity analysis in which low and high erosion rates are tested and the results are compared to get an idea of the model-result uncertainty as a result of uncertainty in erosion rates.

If you have suggestions for how to improve this rather simple model, we'll be happy to hear them!   

Best regards

In page 37 of SLAMM 6.2 Technical Documentation, the map of Predicted Mean Tide Level Salinities for Port Susan Bay looks great. In my case, areas of estuarine water in the salinity raster are NODATA. Any suggestions?

I would be much appreciate it if someone can kindly share a picture about how to set the freshwater boundary and pathway.

Thanks!

Ok. Thanks Jonathan,

Another question. If there is no accretion/erosion data for my region how do we go about field collecting the data to put in to SLAMM? Is there a technique/s (or references) you suggest for collecting these parameters- marsh, swamp and tidal falt erosion rates, and salt marsh, brackish marsh and tidal fresh accretion rates?

Caroline

Very helpful! Many thanks!

The non null and positive value of the dike grid file is the elevation assigned to that particular cell, no matter the value from the DEM. In other words, if the cell area is covering the dike, its assigned elevation is from the dike grid file, otherwise it is from the DEM. If your dike heights data are from the ground level, then you should first add the elevation of the ground (may be from the DEM) so that dike elevations are from the NAVD88 zero and then  create a new dike grid file.

Once the elevations are assigned, the usual elevation adjustments occur to refer elevation to MSL, account for subsidence, historic SLR, etc.

Hope it helps,
Marco

I am a little confused about the new dike file. For a grid identified as dike, what is the relationship between its value in the dike location raster and that in the DEM file? Thanks.

I don't think we found any data for that region and probably used rough model defaults as a result.  -- J

Hi Jonathan,

I am doing some SLAMM modeling near Eastport Maine (on the Passamaquoddy Indian Reservation). I read the Moosehorn and Petit Manan NWR reports to find local parameters. The closest accretion data I could find was in Cobscook Bay from the referenced journal article in the NWR studies by Goodman et. al. Nowhere in the reports does it say where the erosion rate parameters are from. Marsh, swamp and tidal flat erosion respectively used throughout the subsites are 1.8, 1 and 0.5 m/yr. Where did these come from? I am assuming they are for this local region?  Thanks.

Caroline

Derivation from LiDAR or from dike construction specifications or related data layers.  Unfortunately we have no data for SF bay.  Best regards -- Jonathan