We have converted these to georeferenced compressed TIFF files and put them here:

https://www.dropbox.com/s/y4dgawl0j5hbrke/Charlotte_Harbor_TIF.zip?dl=0

We generally deliver data as GEOTIFF files now as they are georeferenced, well compressed (lossless), and quickly imported into any GIS software.

The problem was, the files were originally run and projected by TNC Florida (our project was designed to utilize previous work completed), and they chose the projection of NAD83 Florida West.  We did not reproject their raster files and ASC files do not carry their projection with them, thus resulting in the confusion.

Hope this is useful -- please let us know if you have any other questions or concerns!

-- Jonathan & Marco

Thanks for the heads up -- we will look at this issue tomorrow.

Best -- Jonathan

We're up to Build 239

Editable Max Fetch for Marsh -- Marsh horizontal erosion rates will now be applied when this editable marsh fetch has been exceeded for each marsh cell (previously this was hard-wired at 9km and this value will be loaded into older SLAMM6 simulations.).  This may be edited on a subsite by subsite basis.  This parameter is not relevant if the wave-energy erosion submodel is being utilized.

Also the "Last year of simulation variable" is always utilized even if "run specific years" is selected.  The interface was modified to make this more clear.

Now on GitHub https://github.com/WarrenPinnacle/SLAMM6.7

Editable Max Fetch Threshold for Marsh Erosion -- Marsh horizontal erosion rates will now be applied when an editable marsh fetch has been exceeded for each marsh cell (previously this was hard-wired at 9km and this value will be loaded as a default into older SLAMM6 simulations.).  The threshold may be edited on a subsite by subsite basis.  (This parameter is not relevant if the wave-energy erosion submodel is being utilized.)

We meant to add this as a feature of SLAMM 6.7 initially, but got so caught up in the new fancy wave power formulation that we forgot to modify the basic model.

Also -- the "Last year of simulation" variable is always utilized even if "run specific years is selected."  The interface was modified to make this more clear.

Have you examined the users guide?  The input required is cell-specific flooding heights in units of NAVD88.  If you only have current storm surge height SLR will be added to it.  If you have SLR-specific maps those can also be accommodated though the file naming convention is rather inflexible.

What is your specific question?  Probably it would be best to start with the storm surge data that you have available and consider how to process that into the required raster format. 

More recent NWI shapefiles do not specifically identify dry land; dry land registers as "no-data" in the NWI dataset (as it are not wetlands!).  (Historic data sometimes used the "U" designation for upland.)

Because of this, dry land needs to be manually added using the "turn blank to dry land" button.  For that to work, optimization needs to be turned off in the file setup window.  Also elevation data need to be present as it is how the model discerns dry land from open water when adding dry land.  Another option is to use the "fill cells" feature, but dry land usually bleeds into open ocean in that case.

Hope this is helpful -- send a screen capture or more information if not, please.  Best -- Jonathan

SLAMM 6.7 is now on GitHub!

https://github.com/WarrenPinnacle/SLAMM6.7

Build 236 is now available with a few minor bug fixes:

• Connectivity to inland-open water was inadvertently considered equivalent to connectivity to tidal water.  That has been corrected.
• Conversion from SLB files to ASC files was fixed

The 64-bit installer is here:  https://github.com/WarrenPinnacle/SLAMM6.7/tree/master/INSTALL

An updated version of SLAMM 6.7 is posted on the release page today (3-2-2017).  Build #234.

The errors fixed are:

• Fixed an interface bug in which histograms were not displaying properly in "classic SLAMM category mode"
• Fixed a bug in which calculation of elevation statistics could cause Range-Check-Error in "classic SLAMM category mode"
• Fixed a bug in which GIS outputs could be out of sequence in "classic SLAMM category mode" (especially tidal swamp)
• Corrected wording in Tech Doc -- tidal fresh marsh converts to irregularly flooded marsh not "transitional marsh" in "California" mode.
• Added units to wind-rose input (10 meter, 10 minute avgs.)

Sorry about the delay in response.  

This was an error in SLAMM 6.7 output to GIS files.  

It has been fixed in a maintenance output that I'm posting today. See http://warrenpinnacle.com/SLAMMFORUM/index.php?topic=201.0

Thanks!

I am not an ArcMap user but I'd guess that you need to use a 64 bit operating system and more RAM if you can upgrade your computer.  It is good that RAM is inexpensive as SLAMM and GIS software tends to use a lot of memory!  That is more important, generally, than CPU speed at this point. 

Hello.  The steps are basically as follows:

1. Get the NWI shape-file
2. Add an integer field to the NWI dbf file called SLAMMCODE for ecample
3. Use the latest xls crosswalk to fill in the fields of the SLAMMCODE based on the NWI code
4. Convert the shapefile to raster using the SLAMMCODE as the basis
5. Always QA/QC and ground-truth the conversion.  The NWI is not perfect, the crosswalk is not perfect and sometimes there is ambiguity between Cowardin classes and SLAMM codes.

Now, we can and have provided additional assistance on individual steps, so let us know if and when you are getting stuck.

Also, see this thread:  http://warrenpinnacle.com/SLAMMFORUM/index.php?topic=255.0

SLAMM is not compatible with TIFF files at this point.  Hopefully soon as we are expanding direct GIS-file integration.  However, for now, you must export to ESRI ASCII Rasters.  Please see

http://desktop.arcgis.com/en/arcmap/10.3/tools/conversion-toolbox/raster-to-ascii.htm

and also see pages 79-80 of this document

http://warrenpinnacle.com/prof/SLAMM6/SLAMM_6.7_Technical_Documentation.pdf

Good luck!  -- Jonathan

Thanks -- I have looked at the numbers and they are indeed different (of course).

What I cannot do is verify why, unless I have your SLAMM6 projects, I'm afraid.  Right now I suspect it is something to do with the connectivity options on the Execute screen (whether to average 4 or 8 cells, for example, or whether to use the min or mean cell elevations. 

One thing we did when creating 6.7 was to verify output against the previous version.  Which was version 6.6 (internal version).  So the difference could be between 6.2 and 6.6.  If you send me your SLAMM6 files I'll have a better chance to track this down.

Best regards -- Jonathan

Yes, we'll look into this and get back to you shortly!  -- Jonathan

Thanks for this question.  It's a good one.  I'll answer now quickly and let Marco fill in any details I've missed:

General steps are:

• 1. take your wetland polygon shapefile and add a SLAMMCLASS column to the associated database (dbf)
• 2. assign SLAMM classes using the NWI-to-SLAMM crosswalk -- The latest version delivered with SLAMM 6.7 is SLAMM Cowardin NWI code lookup_10.xlsx
• 3. QA/QC your resulting polygons in GIS and ensure that the crosswalk works for your site.  This is an important step.  There are sometimes ambiguities between estuarine beach and tidal flat in the NWI code that you will want to correct.  Due to these ambiguities the crosswalk may also assign mangrove or cypress swamp in areas where they do not exist.  Use Table 4 of the Technical Documentation to assist you.
• 4. Convert the resulting shapefile to a raster with the precise dimensions as the elevation/slope raseter.  Be sure that the projection of these rasters has the units of "meters" rather than feet

Marco -- any advice that I missed?