Shorelines of the southeastern Florida (FLse) coastal region used in shoreline change analysis

Frequently anticipated questions:

• What does this data set describe?
  1. How might this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How might this data set be cited?
   U.S. Geological Survey, 2017, Shorelines of the southeastern Florida (FLse) coastal region used in shoreline change analysis: data release DOI:10.5066/F74X55X7, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

   Online Links:

   • https://doi.org/10.5066/F74X55X7
   • https://www.sciencebase.gov/catalog/item/58b89108e4b01ccd5500c2f3
   • https://www.sciencebase.gov/catalog/file/get/58b89108e4b01ccd5500c2f3

   This is part of the following larger work.
   Kratzmann, M.G., Himmelstoss, E.A., and Thieler, E.R., 2017, National Assessment of Shoreline Change— A GIS compilation of Updated Vector Shorelines and Associated Shoreline Change Data for the Southeast Atlantic Coast: data release DOI:10.5066/F74X55X7, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://doi.org/10.5066/F74X55X7
   • https://www.sciencebase.gov/catalog/item/58055f50e4b0824b2d1c1ee7

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -80.617140
   East_Bounding_Coordinate: -80.016852
   North_Bounding_Coordinate: 28.375447
   South_Bounding_Coordinate: 25.664506
   

3. What does it look like?
4. Does the data set describe conditions during a particular time period?

   Beginning_Date:

   Ending_Date: 1999

   Currentness_Reference:

   ground condition

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: vector digital data
   

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • String (811)
   2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
      
7. How does the data set describe geographic features?

   FLse_shorelines

   Vector shorelines (Source: U.S. Geological Survey)

   FID

   Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: Esri) Coordinates defining the features.

   RouteID

   Route identification value assigned to individual lidar shoreline line segments. A unique cross-shore profile identification value is stored at each vertex of the lidar route and serves as a common attribute to the shoreline uncertainty table (FLse_shorelines_uncertainty.dbf). (Source: U.S. Geological Survey)

   Value	Definition
   0	Short integer field where zeros are "no data" and automatically filled in for the remaining shoreline polylines not derived from lidar.

   Date_

   Date of shoreline position; date of survey as indicated on source material. A default date of 07/01 was assigned to shorelines where only the year was known (month and day unknown). Using July, the mid-point month of the calendar year, minimizes the potential offset to the actual shoreline date by a maximum of six months. (Source: U.S. Geological Survey) Character string of length 10

   Uncy

   Estimate of shoreline position uncertainty. Actual shoreline position is within the range of this value (plus or minus, meters). The historic shoreline uncertainty values incorporate measurement uncertainties associated with mapping methods and materials for historical shorelines, the geographic registration of shoreline position, and shoreline digitizing. The uncertainty of the High Water Line (HWL) at an individual transect was determined by using positional uncertainty information stored along the shoreline route. The HWL uncertainty was added to the historic shoreline uncertainty stored in the shoreline attribute table during the DSAS rate calculation process to better account for uncertainty at individual transects alongshore as opposed to using a regionally averaged value. This was done using linear referencing that interpolates a value based on data stored in the FLse_shorelines_uncertainty dBase file (.dbf) at a specific transect/shoreline intersect alongshore. The lidar shoreline position uncertainty is also stored in the associated shorelines_uncertainty.dbf file and values are interpolated at specific transect/shoreline intersections using the same linear referencing method. The lidar uncertainty attribute field was filled with null values while residing in the geodatabase. Upon exporting the shoreline feature class to a shapefile for publication, the null values in the lidar uncertainty field were automatically converted to zero values. (Source: U.S. Geological Survey)

   Value	Definition
   0	Zeros are "no data" and serve as place fillers for the lidar shorelines. Actual uncertainty values for lidar are stored in shoreline uncertainty dBase (.dbf) file.

   Source

   Agency or agencies that provided shoreline feature or the data source used (e.g. T-sheet) to digitize shoreline feature. (Source: U.S. Geological Survey)

   Value	Definition
   USGS	U.S. Geological Survey
   NOAA	National Oceanic and Atmospheric Administration
   FLDEP	Florida Department of Environmental Protection

   Source_b

   Type of data used to create shoreline. (Source: U.S. Geological Survey)

   Value	Definition
   lidar	Light detection and ranging (lidar).
   T or TP with number	NOAA/NOS topographic survey sheet (T- or TP-sheet) with associated registry number
   [data source]; [region source file]	[data source] is NOAA/NOS topographic survey sheet (T- or TP-sheet) with associated registry number, or other data source; [region source] identifies file name downloaded from FLDEP

   Year_

   Four digit year of shoreline (Source: U.S. Geological Survey)

   Range of values
   Minimum:	1851
   Maximum:	1999

   Default_D

   Differentiates between shorelines that have known month and day attributes and those that use the default value of 07/01 when only the year is known. (Source: U.S. Geological Survey)

   Value	Definition
   0	Shoreline month and day are known.
   1	Shoreline month and day are unknown and default value of 07/01 was used.

   Location

   Location of shoreline with respect to wave energy exposure. An open ocean coast is directly exposed to ocean waves and is typically characterized by higher wave energy. A sheltered coast is not directly exposed to ocean waves and is characterized by lower wave energy. This shoreline dataset only includes open ocean locations. (Source: U.S. Geological Survey)

   Value	Definition
   open ocean	Shoreline on a coast with open ocean wave exposure.

   Shape_Leng

   Length of feature in meter units (UTM zone 17N, WGS 84) (Source: Esri)

   Range of values
   Minimum:	16.32
   Maximum:	51903.83
   Units:	meters

   Entity_and_Attribute_Overview:

   The entity and attribute information provided here describes the tabular data associated with the dataset. Please review the individual attribute descriptions for detailed information.

   Entity_and_Attribute_Detail_Citation: U.S. Geological Survey
   

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • U.S. Geological Survey
2. Who also contributed to the data set?
3. To whom should users address questions about the data?
   U.S. Geological Survey

   Attn: E.A. Himmelstoss

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 (voice)

   508-547-2310 (FAX)

   ehimmelstoss@usgs.gov

Why was the data set created?

How was the data set created?

1. From what previous works were the data drawn?
2. How were the data generated, processed, and modified?

   Date: 06-Oct-2008 (process 1 of 13)

   An operational Mean High Water (MHW) shoreline was extracted from the lidar surveys within MATLAB v7.6 using a method similar to the one developed by Stockdon et al. (2002). Shorelines were extracted from cross-shore profiles which consist of bands of lidar data 2 m wide in the alongshore direction and spaced every 20 m along the coast. For each profile, the seaward sloping foreshore points were identified and a linear regression was fit through them. The regression was evaluated at the operational MHW elevation to yield the cross-shore position of the MHW shoreline. If the MHW elevation was obscured by water points, or if a data gap was present at MHW, the linear regression was simply extrapolated to the operational MHW elevation. A lidar positional uncertainty associated with this point was also computed. The horizontal offset between the datum-based lidar MHW shoreline and the proxy-based historical shorelines nearly always acts in one direction and the "bias" value was computed at each profile (Ruggiero and List, 2009). In addition an uncertainty associated with the bias was also computed, which can also be thought of as the uncertainty of the HWL shorelines due to water level fluctuations. Repeating this procedure at successive profiles generated a series of X,Y points that contain a lidar positional uncertainty, a bias, and a bias uncertainty value. Ruggiero, P. and List, J.H., 2009. Improving Accuracy and Statistical Reliability of Shoreline Position and Change Rate Estimates. Journal of Coastal Research: v.25, n.5, pp.1069-1081. Stockdon, H.F., Sallenger, A.H., List, J.H., and Holman, R.A., 2002. Estimation of Shoreline Position and Change using Airborne Topographic Lidar Data: Journal of Coastal Research, v.18, n.3, pp.502-513. Person who carried out this activity:
   

   Amy Farris

   U.S. Geological Survey

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 (voice)

   508-457-2310 (FAX)

   afarris@usgs.gov

   Date: 24-Mar-2010 (process 2 of 13)

   The lidar data were collected in projected coordinates (WGS 84 UTM zone 17N). The series of operational MHW points extracted from the cross-shore lidar profiles were converted into a calibrated route shapefile for use in ArcGIS using a Python script. The script generates a point shapefile, converts it to a polyline-M file, saves the uncertainty information in an accessory dBase (.dbf) file and finally generates a calibrated route for the newly-created polyline-M file. Calibration is based on the unique and sequential profile ID value provided with the point data and stored as the M-value. This value is also stored as an attribute in the uncertainty .dbf file and is used as the common attribute field linking the shoreline route file (FLse_shorelines.shp) to the uncertainty table (FLse_shorelines_uncertainty.dbf) storing the lidar positional uncertainty, the bias correction value, and the uncertainty of the bias correction for each point of the original lidar data. During the rate calculation process DSAS uses linear referencing to retrieve the uncertainty and bias values stored in the associated table. Visually identified HWL-type proxy shorelines are virtually never coincident with datum-based MHW-type shorelines. In fact, HWL shorelines are almost universally estimated to be higher (landward) on the beach profile than MHW shorelines. Not accounting for this offset will cause shoreline change rates to be biased toward slower shoreline retreat, progradation rather than retreat, or faster progradation than in reality (for the typical case where datum-based shorelines are more recent data than the proxy-based shoreline dates), depending on actual changes at a given site. Ruggiero, Peter, and List, J.H., 2009, Improving accuracy and statistical reliability of shoreline position and change rate estimates: Journal of Coastal Research, v. 25, no. 5, p. 1069–1081. Ruggiero, Peter, Kaminsky, G.M., and Gelfenbaum, Guy, 2003, Linking proxy-based and datum-based shorelines on high-energy coastlines—Implications for shoreline change analyses: Journal of Coastal Research, special issue 38, p. 57–82. For a detailed explanation of the method used to convert the lidar shoreline to a route, please refer to "Appendix 2- A case study of complex shoreline data" in the DSAS user guide: Himmelstoss, E.A. 2009. "DSAS 4.0 Installation Instructions and User Guide" in: Thieler, E.R., Himmelstoss, E.A., Zichichi, J.L., and Ergul, Ayhan. 2009. Digital Shoreline Analysis System (DSAS) version 4.0 - An ArcGIS extension for calculating shoreline change: U.S. Geological Survey Open-File Report 2008-1278. https://woodshole.er.usgs.gov/project-pages/DSAS/version4/images/pdf/DSASv4_3.pdf Person who carried out this activity:
   

   E.A. Himmelstoss

   U.S. Geological Survey

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 x2262 (voice)

   508-457-2310 (FAX)

   ehimmelstoss@usgs.gov

   Date: 2012 (process 3 of 13)

   Data from the previously-published National Assessment of Shoreline Change study for the Southeast Atlantic (USGS Open-File Report 2005-1401 and USGS Open-File Report 2005-1326) were used as the starting point for the project's continued efforts to compile as many quality shorelines as possible for the region. Digital shorelines, if available from another agency, were acquired. This process step and all subsequent process steps were performed by the same person - M.G. Kratzmann. Person who carried out this activity:
   

   M.G. Kratzmann

   U.S. Geological Survey

   384 Woods Hole Road

   Woods Hole, MA
   

   USA

   508-548-8700 (voice)

   508-457-2310 (FAX)

   mkratzmann@usgs.gov

   Date: 2012 (process 4 of 13)

   Digitized shorelines were downloaded in vector format from the NOAA Historical Shoreline Survey Viewer, currently available as a Google Earth KMZ (https://nosimagery.noaa.gov/images/shoreline_surveys/noaa_shoreline_surveys.kmz). The extracted shorelines are digitized vectors of the mean high water (MHW) position derived from the scanned and georeferenced T-sheet raster imagery that NOAA also manages. Although NOAA labels historical shorelines as MHW, they are proxy-based and therefore considered HWL for the purposes of shoreline change rate calculation with the proxy-datum bias correction. The modern lidar shoreline used in the analysis is datum-based, not proxy-based, and designated as operational MHW which reflects this difference. NOAA topographic survey sheets (T-sheets) and shorelines were quality checked and edited where necessary. Edgematching was corrected when discovered. This process step started in 2012 and was completed in 2013.

   Date: 2012 (process 5 of 13)

   Additional digitized shorelines were acquired from the Florida Department of Environmental Protection. Some of these were sourced from T-sheet data (not available from NOAA) while other shorelines were derived from georeferenced vertical aerial photographs. The shoreline data are organized by county and provided for download as CAD files (.dwg) (ftp://ftp.dep.state.fl.us/pub/water/beaches/HSSD/drawings/draw8390/). These files could be viewed within ArcMap v9.3, but first the coordinate system for the file had to be assigned (NAD 83 State Plane Feet) in ArcCatalog. There are three State Plane FIPS zones for Florida (Florida East FIPS 0901, which covers the entire Atlantic coast along with Collier and Monroe counties on the southwestern coast of the peninsula; Florida West FIPS 0902, which covers the Gulf Coast section of the peninsula between Lee county to the south and Levy county to the north; Florida North-FIPS 0903, which covers the panhandle section of the Florida Gulf Coast from Dixie county in the east to the FL/AL border in Escambia county to the west) and the appropriate zone was assigned to the data based on location. The .dwg files consist of several layers. After the individual county .dwg files were added to the ArcMap v9.3 document, the polyline layer was selected from each county file and exported to a shapefile (right-click > export) from the ArcMap table of contents panel. The exported polyline shapefile (NAD 83 State Plane Feet) for each county was added to the ArcMap document, an edit session was started, and all non-shoreline features were deleted from the file using the “Layer” attribute field. Non-shoreline features were determined to be any entry in the “Layer” attribute field that did not begin with a date. This removed most but not all of the annotation. The “Entity” field was then used to query non-shoreline features. In all files, features that had an Entity attribute field coded as “Circle” were deleted, in some files both “Circle” and “Line” were deleted (in some files the “Line” code contained shoreline position data). In all files the “Entity” field coded as “Arc” contained shoreline position data. The Dissolve tool was used (ArcToolbox > Data Management > Generalization > Dissolve) to dissolve each shapefile based on the “Layer” field. The box next to “Unsplit lines (optional)” at the bottom was selected. Shoreline data compiled from FLDEP were projected in Esri's ArcToolbox (v10) > Data Management Tools > Projections and Transformations > Feature > Project. Parameters: input projection = NAD 1983 State Plane Florida East FIPS 0901 (Feet); output projection = NAD 1983 State Plane Florida East FIPS 0901 (Meters); transformation = none. Shoreline data were projected again in ArcToolbox (v10) > Data Management Tools > Projections and Transformations > Feature > Project. Parameters: input projection = NAD 1983 State Plane Florida East FIPS 0901 (Meters); output projection = UTM zone 17N (NAD 83); transformation = none. After all annotation had been removed from the shapefile, a check for duplicate features was run using XTools (v7.1.0). All duplicate features were deleted. A final visual check of the shorelines was performed. In many of the files it was concluded that edge matching was likely performed between adjacent T-sheets due to noticeable offsets in the shoreline. There is no way to differentiate these line segments from legitimate shoreline vectors using the attribute fields, but any that were observed during the visual inspection were deleted from the file. Close attention was paid to the overlapping areas between adjacent county shoreline files. There were several instances where inconsistent overlap of shoreline from the same date and source occurred, which required manual editing of the two county shapefiles including splitting of some shorelines at the location where the overlap began and deleting the duplicate/overlapping segments from one file. No edge matching was performed during this process. The DSAS-required attribute fields were added to the shapefiles and populated. Date or year and the source of shoreline data (T-sheet or aerial photograph) information was verified by reviewing the details summarized in the bibliography files provided by FLDEP for each county (ftp://ftp.dep.state.fl.us/pub/water/beaches/HSSD/sourcebibs/). Shoreline data compiled from FLDEP were projected in Esri's ArcToolbox (v10) > Data Management Tools > Projections and Transformations > Feature > Project. Parameters: input projection = UTM zone 17N (NAD 83); output projection = geographic (NAD 83); transformation = none. This process step started in 2012 using Arc version 9.3 and was completed in 2013 using Arc version 10.

   Date: 2013 (process 6 of 13)

   Shoreline data from NOAA were used with preference at any location where the shoreline date had previously been sourced from the Florida Department of Environmental Protection (FLDEP). Both sources extracted the shoreline from the same T-sheet, but the NOAA data have fewer process steps and therefore a reduced likelihood of additional error. If no digital shoreline vectors were available, the original T-sheet scan and world file were downloaded from the NOAA Google Earth viewer. Vector shorelines were digitized from the georeferenced T-sheets using standard editing tools in ArcMap v10. Quality assessments were performed and shorelines were edited to remove any overlap between adjacent t-sheets from the same time period. No edge-matching between neighboring shorelines was attempted. The DSAS-required attribute fields were added to the shapefiles and populated.

   Date: 2013 (process 7 of 13)

   Historical shorelines were merged in Esri's ArcToolbox (v10), Data Management Tools > General > Merge. Then the merged file was projected in Esri's ArcToolbox (v10) > Data Management Tools > Projections and Transformations > Feature > Project. Parameters: input projection = geographic (NAD 83); output projection = UTM zone 17N (WGS 84); transformation = NAD_1983_To_WGS_1984_1.

   Date: 2013 (process 8 of 13)

   Historical shorelines were appended to the lidar route data in ArcToolbox (v10) > Data Management Tools > General > Append to produce a single shoreline file for the region. The final shoreline dataset was coded with attribute fields (Date, Uncertainty (Uncy), Source, Source_b, Year_, Default_D, Location). These fields are required for the Digital Shoreline Analysis System (DSAS), which was used to calculate shoreline change rates.

   Date: 2013 (process 9 of 13)

   The appended shoreline file and the shoreline uncertainty table (.dbf) were imported into a personal geodatabase in ArcCatalog v10 by right-clicking on the geodatabase > Import (feature class for shoreline file and table for uncertainty table) for use with the Digital Shoreline Analysis System (DSAS) v4.3 software to perform rate calculations.

   Date: 2013 (process 10 of 13)

   The shoreline feature class was exported from the personal geodatabase back to a shapefile in ArcCatalog v10 by right-clicking on the shoreline file > Export > To Shapefile (single) for publication purposes.

   Date: 2015 (process 11 of 13)

   The data were projected in ArcToolbox v10.2 > Data Management Tools > Projections and Transformations > Project. Parameters: input projection = UTM zone 17N (WGS84); output projection = geographic coordinates (WGS84); transformation = none.

   Date: 25-Aug-2017 (process 12 of 13)

   Keywords section of metadata optimized for discovery in USGS Coastal and Marine Geology Data Catalog. Person who carried out this activity:
   

   U.S. Geological Survey

   Attn: Alan O. Allwardt

   Contractor -- Information Specialist

   2885 Mission Street

   Santa Cruz, CA
   

   831-460-7551 (voice)

   831-427-4748 (FAX)

   aallwardt@usgs.gov

   Date: 10-Aug-2020 (process 13 of 13)

   Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
   

   U.S. Geological Survey

   Attn: VeeAnn A. Cross

   Marine Geologist

   384 Woods Hole Road

   Woods Hole, MA
   

   508-548-8700 x2251 (voice)

   508-457-2310 (FAX)

   vatnipp@usgs.gov

3. What similar or related data should the user be aware of?
   Morton, Robert A., and Miller, Tara L., 2005, National Assessment of Shoreline Change: Part 1 Historical Shoreline Changes and Associated Coastal Land Loss along the U.S. Gulf of Mexico: Open-File Report 2004-1043, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://pubs.usgs.gov/of/2004/1043/

   Miller, Tara L., Morton, Robert A., and Sallenger, Asbury H., 2005, The National Assessment of Shoreline Change— A GIS Compilation of Vector Shorelines and Associated Shoreline Change Data for the U.S. Southeast Atlantic Coast: Open-File Report 2005-1326, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://pubs.usgs.gov/of/2005/1326/index.html

   Thieler, E.R., Himmelstoss, E.A., Zichichi, J.L., and Ergul, A., 2009, Digital Shoreline Analysis System (DSAS) version 4.0 - An ArcGIS extension for calculating shoreline change: Open-File Report 2008-1278, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://woodshole.er.usgs.gov/project-pages/DSAS/version4/
   • https://woodshole.er.usgs.gov/project-pages/DSAS/

   Other_Citation_Details: Current version of software at time of use was 4.3
   

   Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office for Coastal Management, United States Geological Survey (USGS), and National Aeronautics and Space Administration (NASA), 20140121, Fall 1999 East Coast NOAA/USGS/NASA Airborne LiDAR Assessment of Coastal Erosion (ALACE) Project for the US Coastline: NOAA's Ocean Service, Office for Coastal Management, Charleston, SC.

   Online Links:

   • https://coast.noaa.gov/digitalcoast/data/coastallidar/
   • https://www.coast.noaa.gov

   Other_Citation_Details:

   Lidar data were obtained prior to the publication date listed in this citation.

   National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Unknown, Scanned National Ocean Service (NOS) Coastal Survey Maps (also known as Topographic Survey sheets, or T-sheets): National Oceanic and Atmospheric Administration, Washington, D.C..

   Online Links:

   • https://nosimagery.noaa.gov/images/shoreline_surveys/noaa_shoreline_surveys.kmz
   • https://oceanservice.noaa.gov/news/features/feb13/historical-shoreline.html
   • https://nosimagery.noaa.gov/images/shoreline_surveys/survey_scans/NOAA_Shoreline_Survey_Scans.html

   Other_Citation_Details: NOAA shoreline manuscripts (T-sheets)
   

   Florida Department of Environmental Protection (FLDEP), Unknown, Historic Shoreline Drawings: Florida Department of Environmental Protection, Tallahassee, FL.

   Online Links:

   • https://www.dep.state.fl.us/beaches/data/his-shore.htm

   Other_Citation_Details: Historic Shoreline Database
   

   Himmelstoss, E.A., Kratzmann, M.G., and Thieler, E.R., 2017, National Assessment of Shoreline Change: Summary Statistics for Updated Vector Shorelines and Associated Shoreline Change Data for the Gulf of Mexico and Southeast Atlantic Coasts: Open-File Report 2017-1015, U.S. Geological Survey, Reston, VA.

   Online Links:

   • https://doi.org/10.3133/ofr20171015

How reliable are the data; what problems remain in the data set?

1. How well have the observations been checked?
   The data provided here are a compilation of shorelines from multiple sources, spanning 148 years. The attributes are based on the requirements of the Digital Shoreline Analysis System (DSAS) software and have gone through a series of quality assurance procedures.
2. How accurate are the geographic locations?
   Shoreline data have been acquired from 1851 to 1999, the horizontal accuracy of which varies with respect to data source from which the shorelines were digitized, the lidar data from which the shorelines were extracted, and the time period. Shorelines prior to 1960 (T-sheets) have an estimated positional uncertainty of plus or minus 10.8 meters. Shorelines from the 1960s-1980s (T-sheets) have an estimated positional uncertainty of plus or minus 5.1 meters. Shorelines from the 1960s-1970s (FLDEP, air photos) have an estimated positional uncertainty of plus or minus 3.2 meters. The lidar shoreline from 1999 has an estimated positional uncertainty of plus or minus 2.8 meters. Crowell, M., Leatherman, S.P., and Buckley, M.K., 1991. Historical Shoreline Change: Error Analysis and Mapping Accuracy. Journal of Coastal Research: v.7, n.3, pp.839-852.
3. How accurate are the heights or depths?
   The historic shorelines are proxy-based and estimate the HWL. The lidar shoreline is tidal-based and estimates MHW. While the proxy-based HWL shorelines are not shifted to the MHW datum, the distance measurements established by the transects and used by DSAS to compute rate-of-change statistics are adjusted to account for the offset between HWL and MHW. Therefore, all distance measurements along DSAS transects are referenced to the MHW datum before rates are calculated.
4. Where are the gaps in the data? What is missing?
   This shoreline file is complete and contains all shoreline segments used to calculate shoreline change rates along sections of the southeastern Florida coastal region where shoreline position data were available. These data adequately represented the shoreline position at the time of the survey. Remaining gaps in these data, if applicable, are a consequence of non-existing data or existing data that did not meet quality assurance standards. The digitized shoreline vectors downloaded from NOAA included attributes defining the shoreline type (attribute field name varies by file). For the open-ocean facing shorelines, only Mean High Water shoreline features (Natural.Mean High Water; SPOR; 20) were retained. Other shoreline features (such as seawalls, bulkheads, manmade objects) were deleted. NOAA has made non-georeferenced NOAA Shoreline Survey Scans available for download, and additional data for the region may be available (https://nosimagery.noaa.gov/images/shoreline_surveys/survey_scans/NOAA_Shoreline_Survey_Scans.html).
5. How consistent are the relationships among the observations, including topology?
   In many of the shoreline files acquired from FLDEP, it was concluded that edge matching was likely performed between adjacent T-sheets sources used to digitize the shorelines, due to noticeable offsets in the shoreline position. There is no way to differentiate these line segments from legitimate shoreline vectors using the attribute fields, but any that were observed during a visual inspection of the data were deleted from the file. By default, NOAA data were used preferentially where available. Along the open-ocean section of the coast, duplicate shoreline coverage acquired from FLDEP has been removed. Any slight offsets between adjacent segments due to georeferencing and digitizing error are taken into account in the uncertainty calculations included in the report associated with these data.

How can someone get a copy of the data set?

1. Who distributes the data set? (Distributor 1 of 1)
   
   U.S. Geological Survey

   Denver Federal Center

   Denver, CO
   

   USA

   1-888-275-8747 (voice)

   sciencebase@usgs.gov
2. What's the catalog number I need to order this data set?
3. What legal disclaimers am I supposed to read?
   Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
4. How can I download or order the data?
   • Availability in digital form:

     Data format:	These files (.cpg, .dbf, .prj, .sbn, .sbx, .shp, .shp.xml, and .shx) are a collection of files with a common filename prefix and must be downloaded and stored in the same directory. Together they are the components of the shapefile and include FGDC compliant metadata. in format Shapefile (version ArcGIS 10.2) Esri polyline shapefile Size: 1.69
     Network links:	https://www.sciencebase.gov/catalog/file/get/58b89108e4b01ccd5500c2f3 https://www.sciencebase.gov/catalog/item/58b89108e4b01ccd5500c2f3 https://www.sciencebase.gov/catalog/item/58055f50e4b0824b2d1c1ee7 https://doi.org/10.5066/F74X55X7

   • Cost to order the data: None

5. What hardware or software do I need in order to use the data set?
   These data are available in a polyline shapefile format. The user must have software to read and process the data components of a shapefile.

Who wrote the metadata?

Dates:

Last modified: 19-Mar-2024

Metadata author:

M.G. Kratzmann

U.S. Geological Survey

384 Woods Hole Road

Woods Hole, MA

USA

508-548-8700 (voice)

508-547-2310 (FAX)

whsc_data_contact@usgs.gov

Contact_Instructions:

The metadata contact email address is a generic address in the event the person is no longer with USGS. (updated on 20240319)

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)