This layer contains detailed outlines of Maryland counties. The Maryland land county boundaries were built using political county boundaries and the National Hydrology Data (NHD). Land boundaries are a key geographic featue in our mapping process.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Last Updated: UnknownFeature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PhysicalBoundaries/FeatureServer/0

State of Maryland municipality boundary dataset.Maryland Department of Planning (MDP) maps annexations from municipalities. This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:MUN_NAME (Municipality Name): Name of Municipality located in Maryland.RESOLUTION_NUMBER (Resolution Number): Local Municipality Annexation Resolution Number.ANNEXATION_DATE (Annexation Date) (DD/MM/YYYY): The Annexation Date field shows when there's been a change in the boundary. This date is known as the “Effective Date” from the municipality. The date 1/1/1997 is used as a default date of when annexation changes were first indicated in the GIS layer and not necessarily of when it was actually annexed. If there's a date of 1/1/1997, it can be assumed that the annexation occurred on this date or before. For example, for Baltimore City, the city boundary was determined hundreds of years ago. Other than that default date, the date will show when the property was annexed. ACRES (GIS Acres): GIS calculated acresJURSCODE (Jurisdiction Code) – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester).

This layer contains the boundaries and IDs of the Maryland tax maps produced by Maryland Department of Planning. Tax maps, also known as assessment maps, property maps or parcel maps, are a graphic representation of real property showing and defining individual property boundaries in relationship to contiguous real property.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/2

Esri ArcGIS Online (AGOL) Hosted Feature Layer which provides access to the MDOT SHA County Boundaries data product.MDOT SHA County Boundaries data consists of polygon geometric features which represent the geographic area & extent (boundary) of each County throughout the State of Maryland. MDOT SHA County Boundaries data is used by various transportation business units throughout the Maryland Department of Transportation (MDOT), as well as many other Federal, State, & local government agencies. This data is key to understanding the geographic area & extent of each County throughout the State of Maryland. MDOT SHA County Boundaries data is updated & published on an As-Needed basis as this data does not frequently or regularly change. For additional information, contact the MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

The Traffic Volume Maps show the Annual Average Daily Traffic (AADT) numbers displayed at various locations on Maryland's roadways. Traffic counts are reported as the number of vehicles expected to pass a given location. This is an average day of the year for all traffic-counting stations in the state. Traffic volume data is collected from more than 8,700 Program Count stations and 91 Automatic Traffic Recorders (ATRs) located throughout Maryland.Program Count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday, respectively. The ATR and toll count data is collected on a continuous basis. The toll station data is provided by Maryland Transportation Authority.Traffic Volume Maps are updated and published annually in March. Please see the Traffic Volume Map Introduction (PDF, ~148 kb) and ATR and Toll Locations (PDF, ~32 kb) for more information about the Traffic Volume Maps.The entire current Maryland Traffic Volume Map (~9.4 MB) is available as a PDF file.Traffic Volume Maps from previous years back to 1980 are available as PDF files.Please Note: The PDF file sizes for the Traffic Volume Maps vary. It may take a few seconds or a few minutes to display.MDOT SHA Website

Esri ArcGIS Online (AGOL) Feature Layer which provides access to the MDOT SHA County Flood Statistics MapsMDOT SHA County Flood Statistics Maps data consists of polygon geometric features which represent the geographic extent of each Maryland County with an available MDOT SHA County Flood Statistics Map. Users of this layer should consume the URL contained within each pop-up to access the MDOT SHA County Flood Statistics Map.MDOT SHA County Flood Statistics Maps data is owned & maintained by the MDOT SHA OPPE Innovative Planning & Performance Division (IPPD).For more information related to the maps, contact MDOT SHA OPPE Innovative Planning & Performance Division (IPPD):Email: IPPD@mdot.maryland.govFor more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Geographic Extent: SANDY_Restoration_DE_MD_QL2 Area of Interest covers approximately 3.096 square miles. Lot #5 contains the full project area Dataset Description: The SANDY_Restoration_DE_MD_QL2 project called for the Planning, Acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1. The data was developed based on a horizontal projection/datum of State Plane Zone Maryland (1900), NAD83, feet and vertical datum of NAVD1988 (GEOID12A), feet. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.2 Files formatted to 3842 individual 1500m x 1500m tiles, and corresponding Intensity Images and Bare Earth DEMs tiled to the same 1500m x 1500m schema, and Breaklines in ESRI shapefile format. Ground Conditions: LiDAR was collected in Winter 2013 / Spring 2014, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 78 QA control points and 99 Land Cover control points that were used to calibrate the LIDAR to known ground locations established throughout the SANDY_Restoration_DE_MD_QL2 project area.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Caroline/MD_caroline_aspect_m/ImageServer

In 1984, the General Assembly enacted the Chesapeake Bay Critical Area Act to regulate development, manage land use and conserve natural resources on land in those areas designated as Critical Area. For this document, the Critical Area is all land and water areas within 1,000 feet of the tidal waters' edge or from the landward edge of adjacent tidal wetlands and the lands under them. Georeferenced digital data files of the critical Area have been produced for Baltimore City and the 16 Maryland counties with land located within the Critical Area. The digital maps produced for each jurisdiction are polygons depicting the Critical Area and the land use classifications recognized by the Chesapeake Bay Critical Area Commission (CBCAC). Each jurisdiction is a separate file. The data were produced from hard copy parcel maps originally submitted by the counties as part of the requirements for developing their Critical Area Program. For the purpose of the Mdimap web service the Critical Area Data is displayed by two data layers, one general layer and one layer showing the available critical area data for local towns.This data set represents the Department of Natural Resources interpretation of the location and extent of the Critical Area; however, the digital maps are not recognized as the "official" maps. In accordance with Subsection 8-1807(a) of the Critical Area Act, the Critical Area consists of (1) All waters and lands under the Chesapeake Bay and its tributaries to the head of tide as indicated on the State wetland maps, and all State and private wetlands designated under Environment Article, Title 16, annotated Code of Maryland; (2) All land and water areas within 1,000 feet beyond the landward boundaries of State or private wetlands and the of tides designated under Environment Article, Article 16, Annotated Code of Maryland; and (3) Modification to these areas through inclusions or exclusions proposed by local jurisdictions and approved by Commission as specified in Natural Resources Article, Subsection 8-1807, annotated Code of Maryland. These maps are hard copy maps that cannot be exactly replicated in a digital format; therefore, some interpretation was necessary to create the digital line. Hard copy maps depicting the official Critical Area boundary line are available for review at the Chesapeake Bay Critical Area Commission, and at most local planning and zoning departments. The Department of Natural Resources makes no warranty, expressed or implied, as to the use or appropriateness of Spatial Data, and there are no warranties of merchantability or fitness for a particular purpose or use. The intended use is for general information and planning purposes. It is not intended to be used to determine the exact location of the Critical Area boundary on a specific parcel or to determine the acreage within the Critical Area on a specific site. The information contained in Spatial Data is from publicly available sources, but no representation is made as to the accuracy or completeness of Spatial Data. The Department of Natural Resources shall not be subject to liability for human error, error due to software conversion, defect, or failure of machines, or any material used in the connection with the machines, including tapes, disks, CD-ROMs or DVD-ROMs and energy. The Department of Natural Resources shall not be liable for any lost profits, consequential damages, or claims against the Department of Natural Resources by third parties. The liability of the Department of Natural Resources for damage regardless of the form of the action shall not exceed any distribution fees that may have been paid in obtaining Spatial Data.There were many parties involved in producing Maryland's Critical Area data and the key parties will be listed. Each county and city (listed below) produced a hard copy map and submitted the map to the Chesapeake Bay Critical Area Commission (CBCAC) for approval. Through Coastal Zone Management grants, CBCAC digit

This GIS dataset contains growth tier maps adopted by local (county and municipal) jurisdictions under SB236. Data are generally collected from county and municipal jurisdictions by the Maryland Department of Planning (Planning) or digitized by Planning in coordination with local jurisdictions. For more information about SB236, see Planning’s Septics Law Implementation Website at https://planning.maryland.gov/Pages/OurWork/SB236Implementation.aspxThis document describes standard operating procedures for aggregating growth tier map GIS data. These procedures may not apply to historical data (i.e. records for which both the SRC_DATE and GIS_SRC fields are blank). For example, Planning may have realigned historical data from local jurisdictions to parcel polygon boundaries or used different procedures to represent municipal tiers when municipalities concurred with county tier maps.Planning generally requests updated GIS data once a jurisdiction notifies Planning that a growth tier map has been amended. Aggregated data may be outdated or incomplete if Planning has not yet received or processed GIS updates from jurisdictions. Planning generally does not alter geometries received from the local jurisdictions except to divide municipal tiers at the county boundary (see JURSCODE field description). This dataset may contain overlap where multiple jurisdictions designate tiers in the same area.Fields include:JURSCODE – MdProperty Viewjurisdiction code (four-letter county or Baltimore City code). For tiers designated by counties, this is the jurisdiction responsible for designating the growth tier. For tiers designated by municipalities, this is the jurisdiction in which the growth tier is physically located. Municipal tiers that cross counties are divided at the county boundary so this field can be populated. See the MUNI field for the municipality responsible for designating a municipal tier.County – Full name of the jurisdiction represented by the JURSCODE.MUNI – The name of the municipality responsible for designating the tier. This field will be blank (‘ ‘) if the tier has been designated by a county. The MUNI field is formatted consistently with municipality names in the Planning’s municipal boundary datasets. When municipalities adopt tier maps by concurring with county tiers instead of submitting tier data independently, the MUNI field remains blank within the entire county tier map dataset. Depending on internal needs, an independent municipal tier dataset may or may not be generated by Planning and included within the aggregated tiers.TIER – Growth tier identifier used by the source jurisdiction and standardized as Tier 1, Tier 1A, Tier 2, Tier 2A, Tier 3, and Tier 4. May include additional alphabetical annotations used by the jurisdictions such as Tier 2B. If the TIER_CODE field is 99, the TIER field retains the descriptor provided by the jurisdiction, which may be a blank or null value.TIER_CODE – Integer field containing the growth tier standardized by Planning: 1 (Tier I); 11 (Tier IA or any other annotated version of Tier I, such as IB, etc.); 2 (Tier II), 22 (Tier IIA or any other annotated version of Tier II, such as IIB, etc.); 3 (Tier III); 4 (Tier IV); 44 (Areas annotated as Tier IVA for municipal greenbelts or any other annotated version of Tier IV); 99 – Areas included in the jurisdiction’s growth tier GIS data that are not assigned a tier, such as rights-of-way or water.Adopt_Date – Date growth tier map was adopted or amended. When a local jurisdiction updates its growth tier map, Planning generally requests a comprehensive GIS update to replace all existing data for the jurisdiction.Acres – GIS acres calculated by Planning in NAD83 Meters (EPSG 26985)GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information Planning obtained, which concatenates the JURSCODE field (or MUNI field for municipal tier maps), followed by a space, followed by the name of the shapefile or feature class received from the jurisdiction. Field contains “MDP” if tiers were digitized by Planning, and is blank (‘ ‘) for historical data.SRC_DATE (GIS Source Date) – The date (YYYYMMDD) the GIS data were obtained by Planning from the local jurisdiction. If the month or day is unknown, the date is YYYY0000. If Planning digitized the growth tier map in coordination with a local jurisdiction, this should be the date Planning’s edits are verified by the jurisdiction. This field will be blank (‘ ’) if Planning’s edits have not been verified or if the dataset is historical and the source is unknown.NOTE – Text field containing additional notes about the dataLast Updated: 7/26/2023This is a Maryland Department of Planning hosted service. Find more information on https://imap.maryland.govMap Service Link: https://mdpgis.mdp.state.md.us/arcgis/rest/services/PlanningCadastre/Septic_Growth_Tiers/MapServer

1 in.= 600 feet Tax Map index of Anne Arundel County

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

Tabulates acres by land use category as of 2018 for each of Maryland’s 23 counties and Baltimore City. Derived from the Maryland Department of Planning’s 2018 Statewide Land Use Dataset (2024 Edition). Given methodology changes, this dataset is not comparable with MDP’s previous Land Use Land Cover products and should not be used to assess change over time.

This is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. In 1984 - the General Assembly enacted the Chesapeake Bay Critical Area Act to regulate development - manage land use and conserve natural resources on land in those areas designated as Critical Area. For this document - the Critical Area is all land and water areas within 1000 feet of the tidal waters' edge or from the landward edge of adjacent tidal wetlands and the lands under them. Georeferenced digital data files of the critical Area have been produced for Baltimore City and the 16 Maryland counties with land located within the Critical Area. The digital maps produced for each jurisdiction are polygons depicting the Critical Area and the land use classifications recognized by the Chesapeake Bay Critical Area Commission (CBCAC). Each jurisdiction is a separate file. The data were produced from hard copy parcel maps originally submitted by the counties as part of the requirements for developing their Critical Area Program. For the purpose of the Mdimap web service the Critical Area Data is displayed by two data layers - one general layer and one layer showing the available critical area data for local towns.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Environment/MD_CriticalAreas/FeatureServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

This layer contains data concerning the location and characteristics of bedrock, mappable geologic units, within Washington county. This geodatabase contains geologic data from Washington County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Washington County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

This is the County Boundary layer for Anne Arundel County, Maryland.

From the site: "This map includes short descriptions of geologic units and a cross section showing the distribution of geologic units under the earth’s surface. Among other uses, the map will provide users with a better understanding of the distribution, depths and thickness of Marcellus Shale. This map will be especially useful in showing the interplay between geologic formations and groundwater availability and quality.

The map updates geologic information to be consistent with adjacent states, redefines boundaries between formations from the previous maps, and updates the subsurface geologic cross section based on new review of geologic cores and geophysical logs. The geologic information is available to users in Geographic Information System (GIS) format. A printable PDF version is also available. At this time we do not plan to offer a printed version of this map. The map is about 36 inches high by 60 inches wide when printed. If you do not have access to a large-format printer you can take the PDF file to a desktop publisher or office supply store and have it printed.

This product was assembled at a scale of 1:100,000. Using the map or data a smaller scale, such as 1:60,000 or 1:24,000, can result in serious positional errors. All data, information, and maps are provided "as is" without warranty or any representation of accuracy, timeliness of completeness. The burden for determining accuracy, completeness, timeliness, merchantability and fitness for or the appropriateness for use rests solely on the user. Maryland Department of Natural Resources makes no warranties, express or implied, as to the use of the information obtained here. There are no implied warranties of merchantability or fitness for a particular purpose. The user acknowledges and accepts all limitations."

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

This layer contains data concerning the location and characteristics of unconsolidated Quaternary deposits within Frederick county. This geodatabase contains geologic data from Frederick County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Frederick County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

This layer contains data concerning the location and characteristics of contacts and faults within Frederick county. This geodatabase contains geologic data from Frederick County, Maryland. Data from several geologic quadrangles and two regional scale geologic maps were incorporated into the regional scale geologic feature classes in this geodatabase. Because of the scale of this map, some features were generalized slightly from the quad scale data. Additionally, some corrections were made for accuracy, such as edge matching to resolve "border faults". The source data for this map and geodatabase come from maps published by the Maryland Geological Survey from 2001 to the present, as well as one map published in cooperation with the United States Geological Survey. The source maps are Buckeystown (2001), Catoctin Furnace (2004), Frederick (2004), New Windsor (2004), Point of Rocks (2004), Walkersville (2004), Woodsboro (2004), Middletown (2005), Union Bridge (2006), Funkstown (2009), Keedysville, Shepherdstown, Charlestown, and Harpers Ferry (2009), Myersville and Smithsburg (2009), Hagerstown (2013), Mason and Dixon (2013), Clear Spring and Hedgesville (2014), Williamsport (2014), Blue Ridge Summit (2021, in review), Emmitsburg and Taneytown (2021, in review), all 1:24000 quadrangle scale, as well as portions of two regional maps: Geologic Map of Garrett, Allegany, and Western Washington Counties, Maryland (2013), and Geologic Map of the Frederick 30' x 60' Quadrangle, Maryland, Virginia, and West Virginia (USGS, 2007). The GIS data from the referenced maps were mosaiced in Arc Map, corrected for accuracy across quad boundaries, merged to form a continuous dataset and clipped to the extent of Frederick County. Feature level metadata are included, which contain field descriptions for each feature class. This is a small scale dataset, appropriate for 1:100,000 regional scale. Quad scale data are suggested for display or analysis that requires a larger scale. This dataset is prepared for compliance with the USGS GeMS database standard. Last Updated: 06/01/2022

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the Universal Transverse Mercator Zone 18 North. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000. Coastal study data as defined in FEMA Gudelines and Specifications, Appendix D: Guidance for Coastal Flooding Analyses and Mapping, submitted as a result of a coastal study. Appendix D notes that a variety of analytical methodologies may be used to establish Base (1-percent-annual-chance) Flood Elevations (BFEs) and floodplains throughout coastal areas of the United States. Appendix D itemizes references for the methodologies currently in use by FEMA for specific coastal flood hazards, provides general guidance for documentation of a coastal flood hazard analysis, specifies flood hazard analysis procedures for the Great Lakes coasts, and outlines intermediate data submissions for coastal flood hazard analyses with new storm surge modeling and revised stillwater flood level (SWFL). (Source: FEMA Guidelines and Specs, Appendix D Guidance for Coastal Flooding Analyses and Mapping, Section D.1)