Metadata
GeoLibrary
GeoNetwork
GeoRSS-GML
Login / Register
Send to a friendBookmark on DeliciousBookmark on DiggBookmark on FacebookBookmark on StumbleUpon
Logo

hurr_surge_inun_MHT

FGDC XML
Logical Consistency Report Because of the large tidal range along the Maine coast, two SLOSH models were run for this study. One model calculated hurricane surge elevations assuming that peak storm surge arrived coincident with mean tide, and the other calculated hurricane surge elevations assuming that peak storm surge arrived coincident with mean high tide. The SLOSH model calculates the hurricane surge elevation that would result from over 500 combinations of hurricane category, landfall location, forward speed, and direction.Hurricane Category. One of the earlier guides developed to describe the potential stormsurge generated by hurricanes is the Saffir/Simpson Hurricane Scale, which assigns aHurricane Category according to the maximum sustained wind speed within thehurricane. It was developed by Herbert Saffir, Dade County, Florida, ConsultingEngineer, and Dr. Robert H. Simpson, former Director of the National Hurricane Center.A condensed version of the Saffir/Simpson Hurricane Scale is shown in the table below.Saffir/Simpson Hurricane ScaleCategory Maximum SustainedWind Speed (mph)1 74-952 96-1103 111-1304 131-1555 > 155FEMA Flood Zone Coincidence: The FEMA 100- and 500-year flood zones may depictareas beyond the hurricane surge inundation areas where coastal or inland flooding maybe expected. FEMA Flood zones were not available in electronic format for Knox andLincoln Counties.
Completeness Report The entire extent of coastal Maine that could expect to be inundated by hurricane storm surge under worst case conditions. Two Hurricane Surge Inundation GIS layers were developed from this effort one each for the mean tide and the mean high tide scenarios.
Horizontal Positional Accuracy Report Users of the Hurricane Surge Inundation Maps should recognize that there are accuracy limitations inherent to each of the data sources used to create the maps. The SLOSH model hurricane surge elevations have an accuracy of +/- 20%. The elevation data has a vertical accuracy of approximately +/- 7' and a horizontal accuracy of approximately +/- 25'. The basemap data, such as the shoreline, roads, rivers, streams, and schools, has a horizontal accuracy of approximately +/- 25'. Therefore, the maps should be used as a general guide, rather than an absolute representation, as to which areas can expect to be inundated (flooded) by worst-case hurricane storm surge for a particular hurricane category. In addition, users should note that there may be areas that are not shown to be inundated by hurricane surge, but are in fact surrounded by hurricane surge. Those areas may become isolated by hurricane surge.
Horizontal Positional Accuracy Value 8
Horizontal Positional Accuracy Explanation The elevation data has a vertical accuracy of approximately +/- 7' and a horizontal accuracy of approximately +/- 25'. The basemap data, such as the shoreline, roads, rivers, streams, and schools, has a horizontal accuracy of approximately +/- 25'.
Vertical Positional Accuracy Report Users of the Hurricane Surge Inundation Maps should recognize that there are accuracy limitations inherent to each of the data sources that was used to create the maps. The SLOSH model hurricane surge elevations have an accuracy of +/- 20%. The elevation data has a vertical accuracy of approximately +/- 7' and a horizontal accuracy of approximately +/- 25'. The basemap data, such as the shoreline, roads, rivers, streams, and schools, has a horizontal accuracy of approximately +/- 25'. Therefore, the maps should be used as a general guide, rather than an absolute representation, as to which areas can expect to be inundated (flooded) by worst-case hurricane storm surge for a particular hurricane category. In addition, users should note that there may be areas that are not shown to be inundated by hurricane surge, but are in fact surrounded by hurricane surge. Those areas may become isolated by hurricane surge.
Vertical Positional Accuracy Value 2
Vertical Positional Accuracy Explanation The SLOSH model hurricane surge elevations have an accuracy of +/- 20%. The elevation data has a vertical accuracy of approximately +/- 7'.
Time of Day Unknown
Source Citation Abbreviation slosh
Source Scale Denominator 24000
Type of Source Media stable-base material (mylar)
Beginning Date 19480101
Beginning Time Unknown
Ending Date Present
Ending Time Unknown
Source Currentness Reference publication date
Source Citation Abbreviation 24k
Source Contribution coast, rivers, roads, streams
Type of Source Media online
Beginning Date 19790701
Beginning Time Unknown
Ending Date Present
Ending Time Unknown
Source Citation Abbreviation 30mdem
Source Scale Denominator 24000
Type of Source Media online
Beginning Date 19480101
Beginning Time Unknown
Ending Date 20050822
Ending Time Unknown
Source Currentness Reference source dates
Source Citation Abbreviation metwp24
Source Contribution towns
Process Description Obtained SLOSH (Sea, Lake and Overland Surge from Hurricanes) model output from the National Hurricane Center. The data was provided in ArcView shapefile format as a polygon shapefile. The polygon shapefile represented the Penobscot Bay SLOSH Basin. Each polygon contained eight attributes. The attributes represented the water surface elevation (in feet) that would occur from the worst-case hurricane surge within each polygon for hurricane categories 1 through 4, and also for scenarious where the peak hurricane surge arrived coincident with 1) mean tide, and 2) mean high tide (the antecedent tide level). The shapefile was in a Geographic NAD 27 horizontal coordinate system.
Process Description Projected the source polygon shapefile from Geographic NAD 27 to UTM Zone 19 NAD 83 meters.
Process Description Overlaid the SLOSH polygon shapefile on top of a shapefile of the Maine GIS 1:24K coastline, and deleted many of the polygons that fell far offshore, as these were not necessary for further analysis. The polygons that were important for the creation of a hurricane sure layer were those polygons seaward of the shoreline, but in the immediate vicinity of the shoreline, and those polygons that were landward of the shoreline.
Process Description Use XTools to create a point shapfile of the centroids of the polygons.
Process Description Created eight point shapefiles from the previous point shapefile, each representing the eight permutations of Category 1 through 4 hurricane surge, and the scenarios of hurricane surge arriving coincident with 1) mean tide, and 2) mean high tide. Within each of the eight shapefiles, deleted records that contained values of "99.9" for the represented permutation, which represented areas that were not flooded in the SLOSH model runs.
Process Description The resulting eight shapefiles covered a large spatial extent - all of coastal Maine. Therefore, the eight shapefiles were divided into five sub areas along the Maine coast to facilitate interpolation of the points. This resulted in 40 shapefiles.
Process Description Interpolated each of the resulting 40 point shapefiles to produce interpolated raster surfaces (ArcInfo Grids) representing the hurricane surge water elevation for each particular hurricane scenario. Used IDW interpolation, with the following parameters: power = 2, Search radius type: Variable, Number of points: 6. Used a cell size of 10 meters to facilitate interpolation, as smaller cell sizes proved to be too computationally intensive. This resulted in 40 raster grids representing the eight permutations of hurricane category and antecedent tide level, for the five sub areas. This completed the preparation of the water surface grids. The next step was to prepare the land surface grids.
Process Description Downloaded land surface elevation data from the USGS Seamless Data Distribution System (SDDS). The downloaded data consisted of the 1/3 arc second National Elevation Dataset. The data was in ArcInfo Grid format, had vertical units of meters, and was in a Geographic NAD 83 horizontal coordinate system. Downloaded this data in several pieces due to the size constraints imposed by the SDDS website, and later merged them together (see subsequent process steps) to cover the five sub areas along the Maine coast.
Process Description Projected each of the downloaded USGS DEM's from Geographic NAD 83 to UTM Zone 19 NAD 83 meters.
Process Description Converted the vertical units of each of the projected DEM Grids from meters to feet by multiplying the Grid "Value" by 3.280839895.
Process Description Merged the DEM Grids to create land surface grids that covered each of the five sub areas along the Maine coast. This completed the preparation of the land surface elevation grids. The next step was to subtract the land surface grids from the water surface grids to create rasters depicting which areas would and would not be flooded (inundated) by worst case hurricane surge for each of the two antecedent tide scenarios. See subsequent process steps.
Process Description Created inundation grids or lattices (called ilats here for "inundation lattices") for each of two the antecedent tide conditions (mean tide and mean high tide) and each of the five sub areas (designated a through e) along the Maine coast (for a total of ten inundation grids) by running the following AML (Arc Macro Language) program:/* Run from D:\MaineHES1204\Inun/* Run from Gridsetcell 10/* asetwindow 343340 4757118 423884 4879210ilathi_a = con(d:\mainehes1204\slosh\c1hi_a - d:\mainehes1204\dems\dem_a > 0, 1, ~d:\mainehes1204\slosh\c2hi_a - d:\mainehes1204\dems\dem_a > 0, 2, ~d:\mainehes1204\slosh\c3hi_a - d:\mainehes1204\dems\dem_a > 0, 3, ~d:\mainehes1204\slosh\c4hi_a - d:\mainehes1204\dems\dem_a > 0, 4)ilatmean_a = con(d:\mainehes1204\slosh\c1mean_a - d:\mainehes1204\dems\dem_a > 0, 1, ~d:\mainehes1204\slosh\c2mean_a - d:\mainehes1204\dems\dem_a > 0, 2, ~d:\mainehes1204\slosh\c3mean_a - d:\mainehes1204\dems\dem_a > 0, 3, ~d:\mainehes1204\slosh\c4mean_a - d:\mainehes1204\dems\dem_a > 0, 4)/* bsetwindow 420525 4833538 475922 4925056ilathi_b = con(d:\mainehes1204\slosh\c1hi_b- d:\mainehes1204\dems\dem_b> 0, 1, ~d:\mainehes1204\slosh\c2hi_b- d:\mainehes1204\dems\dem_b> 0, 2, ~d:\mainehes1204\slosh\c3hi_b- d:\mainehes1204\dems\dem_b> 0, 3, ~d:\mainehes1204\slosh\c4hi_b- d:\mainehes1204\dems\dem_b> 0, 4)ilatmean_b= con(d:\mainehes1204\slosh\c1mean_b- d:\mainehes1204\dems\dem_b> 0, 1, ~d:\mainehes1204\slosh\c2mean_b- d:\mainehes1204\dems\dem_b> 0, 2, ~d:\mainehes1204\slosh\c3mean_b- d:\mainehes1204\dems\dem_b> 0, 3, ~d:\mainehes1204\slosh\c4mean_b- d:\mainehes1204\dems\dem_b> 0, 4)/* csetwindow 473811 4833891 575376 4973627ilathi_c= con(d:\mainehes1204\slosh\c1hi_c- d:\mainehes1204\dems\dem_c> 0, 1, ~d:\mainehes1204\slosh\c2hi_c- d:\mainehes1204\dems\dem_c> 0, 2, ~d:\mainehes1204\slosh\c3hi_c- d:\mainehes1204\dems\dem_c> 0, 3, ~d:\mainehes1204\slosh\c4hi_c- d:\mainehes1204\dems\dem_c> 0, 4)
Process Description Ran the following aml program to set the nodata values of the raster = "10" prior to running the ArcInfo Grid "Fill" command./* Run from D:\MaineHES1204\Inun/* Run from Gridsetcell 10setwindow maxofset10hi_a = con(isnull(ilathi_a), 10, ilathi_a)set10hi_b = con(isnull(ilathi_b), 10, ilathi_b)set10hi_c = con(isnull(ilathi_c), 10, ilathi_c)set10hi_d = con(isnull(ilathi_d), 10, ilathi_d)set10hi_e = con(isnull(ilathi_e), 10, ilathi_e)set10mean_a = con(isnull(ilatmean_a), 10, ilatmean_a)set10mean_b = con(isnull(ilatmean_b), 10, ilatmean_b)set10mean_c = con(isnull(ilatmean_c), 10, ilatmean_c)set10mean_d = con(isnull(ilatmean_d), 10, ilatmean_d)set10mean_e = con(isnull(ilatmean_e), 10, ilatmean_e)
Process Description Converted each of the ten inundation grids to polygon shapefiles in preparation of clipping them to the Maine Office of GIS (MEGIS) 1:24K "METWP" (Maine Townships) polygon shapefile.
Process Description Selected polygons from the "METWP" polygon shapefile that intersected the Category 4, Mean High Tide Scenario inundation polygon shapefile, and exported that subset to a new shapefile. This shapefile constituted the flooding that extended furthest inland out of the ten inundation shapefiles. Then polygons were dissolved to remove boundaries at town lines.
Process Description Clipped each of the ten inundation shapefiles to the subset, dissolved version of "METWP" polygon shapefile.
Process Description Converted each of the ten clipped polygon inundation shapefiles into rasters (grids).
Process Description Ran the following AML program to set the nodata values of the rasters (which after the clip are the values seaward of the coastline) = "0" prior to running the ArcInfo Grid "Fill" command./* Run from D:\MaineHES1204\Inun/* Run from Gridsetcell 10setwindow maxofset0hi_a = con(isnull(cliphi_a), 0, cliphi_a)set0hi_b = con(isnull(cliphi_b), 0, cliphi_b)set0hi_c = con(isnull(cliphi_c), 0, cliphi_c)set0hi_d = con(isnull(cliphi_d), 0, cliphi_d)set0hi_e = con(isnull(cliphi_e), 0, cliphi_e)set0mean_a = con(isnull(clipmean_a), 0, clipmean_a)set0mean_b = con(isnull(clipmean_b), 0, clipmean_b)set0mean_c = con(isnull(clipmean_c), 0, clipmean_c)set0mean_d = con(isnull(clipmean_d), 0, clipmean_d)set0mean_e = con(isnull(clipmean_e), 0, clipmean_e)
Process Description Ran the ArcInfo Grid "Fill" command to fill any "sinks" or depressions in the inundation grids. These would occur in areas that are low, but which have higher ground between their location and the coast which would prevent coastal surge from reaching the area. In previous process steps, the land areas were set to "10", and ocean and river areas were set to "0". In between, the inundation was coded as 1 thorugh 4 according to hurricane category. Therefore, the "Fill" command ensures that all flooding "flows" from high ground to low ground, or from 10 to 4, 3, 2, 1, and 0. The AML program is below./* Run from D:\MaineHES1204\Inun/* Run from Gridsetcell 10fill set0hi_a fillhi_a sinkfill set0hi_b fillhi_b sinkfill set0hi_c fillhi_c sinkfill set0hi_d fillhi_d sinkfill set0hi_e fillhi_e sinkfill set0mean_a fillmean_a sinkfill set0mean_b fillmean_b sinkfill set0mean_c fillmean_c sinkfill set0mean_d fillmean_d sinkfill set0mean_e fillmean_e sink
Process Description Ran the following AML program to set the areas that had been set to "0" or "10" prior to the filling operation back to "nodata"./* Run from D:\MaineHES1204\Inun/* Run from Gridsetcell 10finalhi_a = setnull(fillhi_a == 10 or fillhi_a == 0, fillhi_a)finalhi_b = setnull(fillhi_b == 10 or fillhi_b == 0, fillhi_b)finalhi_c = setnull(fillhi_c == 10 or fillhi_c == 0, fillhi_c)finalhi_d = setnull(fillhi_d == 10 or fillhi_d == 0, fillhi_d)finalhi_e = setnull(fillhi_e == 10 or fillhi_e == 0, fillhi_e)finalmean_a = setnull(fillmean_a == 10 or fillmean_a == 0, fillmean_a)finalmean_b = setnull(fillmean_b == 10 or fillmean_b == 0, fillmean_b)finalmean_c = setnull(fillmean_c == 10 or fillmean_c == 0, fillmean_c)finalmean_d = setnull(fillmean_d == 10 or fillmean_d == 0, fillmean_d)finalmean_e = setnull(fillmean_e == 10 or fillmean_e == 0, fillmean_e)
Process Description Merged the five inundation grids (a through e) for the Mean Tide scenario together to form one inundation grid that covered all of coastal Maine for the Mean Tide Scenario. Merged the five inundation grids (a through e) for the Mean High Tide scenario together to form one inundation grid that covered all of coastal Maine for the Mean High Tide Scenario. Used the ArcInfo Workstation Grid command "merge" to do this. This resulted in one inundation grid for the Mean Tide Scenario and one inundation grid for the Mean High Tide Scenario.
Process Description Converted the two inundation grids to polygon shapefiles called hurrsurge_mt for "Hurricane Surge - Mean Tide scenario" and hurrsurge_mht (Hurricane Surge - Mean High Tide scenario"). This completed the preparation of the two Hurricane Surge Inundation shapefiles.
Contact Organization U.S. Army Corps of Engineers, New England District
Contact Position Geospatial Data and Systems Point of Contact
Address Type mailing and physical address
Address 696 Virginia Road
City Concord
State or Province MA
Postal Code 01742
Country USA
Contact Voice Telephone 978-318-8647
Contact Facsimile Telephone 978-318-8080
Direct Spatial Reference Method Vector
SDTS Point and Vector Object Type G-polygon
Point and Vector Object Count 393443
[smcaptur]  false
Grid Coordinate System Name 
UTM Zone Number 19
Scale Factor at Central Meridian 0.9996
Longitude of Central Meridian -69
Latitude of Projection Origin 0
False Easting 500000
False Northing 0
Planar Coordinate Encoding Method 
Abscissa Resolution 0.000512
Ordinate Resolution 0.000512
Planar Distance Units m
Horizontal Datum Name North American Datum of 1983
Ellipsoid Name Geodetic Reference System 80
Semi-major Axis 6378137
Denominator of Flattening Ratio 298.257
Altitude Datum Name National Geodetic Vertical Datum of 1929
Altitude Distance Units feet
Entity Type Label Hurr_Surge_Inun_MHT
Entity Type Definition polygon feature class
Entity Type Definition Source Environmental Systems Research Institute, Inc. (ESRI)
Attribute Label Category
Attribute Definition Hurricane Category associated with the hurricane surge limit of that polygon
Attribute Definition Source National Hurricane Center SLOSH Model
Beginning Date of Attribute Values 
Entity and Attribute Overview Each polygon is assigned a category number, which indicates the hurricane category, according to the Saffir-Simpson scale, at which the area would be flooded by hurricane surge.
Entity and Attribute Detail Citation Each polygon contains a hurricane category ranging from 1 to 4, according to the Saffir-Simpson scale.The ArcView shapefile and ArcGIS geodatabase formats, commonly used for Maine GIS data, carry default identifiers and attributes that are software generated and/or important for internal recordkeeping. These are listed here to avoid repetition for every layer, and may not be repeated in the attribute descriptions and definitions of each layer. Common software generated identifiers and attributes in Maine GIS data include: FID (feature identifier), Shape (feature geometry), OBJECTID and SHAPE_lengt. In addition, most GIS formats will carry fields for PERIMETER, AREA and/or LENGTH according to feature geometry. These fields are typically available by default, with the units based on coordinate system or projection units of GIS data. Most GIS software packages also provide a means to calculate these values. It is important to test any columns containing PERIMETER, AREA or LENGTH values before using them for analysis purposes. These important values can be carried from format to format and become out-dated. Verify that the values are correct. Also, in your GIS software, please view the properties of data layers for the map units used to calculate these fields, and for the units set for display purposes.
Entity and Attribute Overview Each polygon is assigned a category number, which indicates the hurricane category, according to the Saffir-Simpson scale, at which the area would be flooded by hurricane surge.
Entity and Attribute Detail Citation Each polygon contains a hurricane category ranging from 1 to 4, according to the Saffir-Simpson scale.The ArcView shapefile and ArcGIS geodatabase formats, commonly used for Maine GIS data, carry default identifiers and attributes that are software generated and/or important for internal recordkeeping. These are listed here to avoid repetition for every layer, and may not be repeated in the attribute descriptions and definitions of each layer. Common software generated identifiers and attributes in Maine GIS data include: FID (feature identifier), Shape (feature geometry), OBJECTID and SHAPE_lengt. In addition, most GIS formats will carry fields for PERIMETER, AREA and/or LENGTH according to feature geometry. These fields are typically available by default, with the units based on coordinate system or projection units of GIS data. Most GIS software packages also provide a means to calculate these values. It is important to test any columns containing PERIMETER, AREA or LENGTH values before using them for analysis purposes. These important values can be carried from format to format and become out-dated. Verify that the values are correct. Also, in your GIS software, please view the properties of data layers for the map units used to calculate these fields, and for the units set for display purposes.
Contact Organization (MEGIS) Maine Office of Geographic Information Systems
Contact Person GIS Coordinator
Contact Position GIS Coordinator
Address Type mailing address
Address State House Station 174
City Augusta
State or Province ME
Postal Code 04333-0174
Country USA
Contact Voice Telephone 207 624-7700
Contact Facsimile Telephone 207 287-3842
Hours of Service Monday through Friday 0800 - 1700 EST
Resource Description http://megis.maine.gov/catalog/
Distribution Liability Users must assume responsibility to determine the usability of this data for their purposes. Although these data have been processed successfully on a computer system at the Maine Office of Geographic Information Systems, no warranty expressed or implied is made by MEGIS regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. Neither the Maine Office of Geographic Information Systems, nor any of its contributors, is liable for misuse of the data, for damage, for transmission of viruses, or for computer contamination through the distribution of these data sets.
Format Name ESRI Shapefile
Format Version Number ARC Version 9.x
Format Specification ArcView Shapefile Format
Format Information Content MEGIS has made all vector layers, in the Maine GIS Internet Data Catalog, available in ESRI's ArcView shapefile format. A shapefile is a simple non-topological format that stores the geometry and attribute information for a set of geographic features as a set of vector (point, line, polygon) coordinates. Shapefiles draw quickly and directly in ArcView, ArcGIS, ArcExplorer. Shapefiles are a compatible data type for many other types of GIS software. Three files are fundamental to each shapefile: .shp stores the feature geometry (shape and location information); .shx stores the index of the feature geometry; .dbf a dBASE (TM) file stores the attribute information for the features. Other index files may be created to help speed analysis and query: these file formats are .sbn .sbx .ain .aix .fbn and .fbx. In addition you may find projection .prj, and metadata .xml, files associated with shapefiles.
File Decompression Technique Data available from this website is in .zip compressed format. WinZip is a Windows based, PKZip-compatible compression utility. You will need a program like this to extract the data.
[accinstr]  These data are available to Internet browsers for download from the Maine GIS Internet Data Catalog - http://megis.maine.gov/catalog/Data available from this website is in .zip compressed format. WinZip is a Windows based, PKZip-compatible compression utility. You will need a program like this to extract the data.If you are not already a GIS user, free software for viewing these files is available from Environmental Systems Research Institute, Inc. (ESRI) - www.esri.com
[smdistty]  1
Fees Data may be downloaded from Maine GIS Internet Data Catalog at no charge.
Turnaround Data is available for immediate download from the Maine GIS Internet Data Catalog.
Technical Prerequisites If you are not already a GIS user, free software for viewing these files is available from Environmental Systems Research Institute, Inc. (ESRI) http://www.esri.com/
Beginning Date 20051201
Ending Date Present
Contact Organization Maine Office of Geographic Information Systems
Contact Position GIS Coordinator
Address Type mailing address
Address State House Station 174
City Augusta
State or Province ME
Postal Code 04333-0174
Country USA
Contact Voice Telephone (207) 624-7700
Contact Facsimile Telephone (207) 287-3842
Hours of Service Monday through Friday 0800 - 1700 EST
Distribution Liability Users must assume responsibility to determine the usability of this data for their purposes.
Format Name ARCSDE
Format Version Number ArcSDE 9.x
Format Information Content Oracle 9i
[accinstr]  Please contact the Maine Office of GIS (MEGIS) for access instructions.
[smdistty]  1
Fees Access is available through Maine's wide area network; WAN users may contact the Maine Office of Information Technology, Maine Office of Geographic Information Systems (MEGIS) for a login.
Powered by GeoNetworks
View Disclaimer