20240408 14392800 1.0 FGDC CSDGM Metadata FALSE MeanHighWaterLines_Historical 002 0.000 599491.521821 750918.651381 1599069.892121 1868841.426396 1 Projected GCS_North_American_1983_HARN Linear Unit: Foot_US (0.304801) NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",656166.6666666665],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-81.0],PARAMETER["Scale_Factor",0.9999411764705882],PARAMETER["Latitude_Of_Origin",24.33333333333333],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2881]]</WKT><XOrigin>-17791300</XOrigin><YOrigin>-41645400</YOrigin><XYScale>3048.0060960121918</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2881</WKID><LatestWKID>2881</LatestWKID></ProjectedCoordinateSystem> 20240408 14395500 20240408 14395500 150000000 5000 FGDC Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 Historical Mean High Water Lines 1 -81.178116 -80.702218 29.474533 28.732300 Historical Mean High Water Lines from the State of Florida DEP https://publicfiles.dep.state.fl.us/DWRM/Beaches/HSSD/readme/readmeb.pdf <DIV STYLE="text-align:Left;"><DIV>Last Rev. 01/24/08 - E.Foster, P.E. - FSU/BSRCThe Historic Shoreline Database on the Web contains many directories of related types of information about beach changes in Florida over the past 150 or so years. The historic shoreline map images (see the Drawings directory) show precision-digitized approximate mean high water (mhw) shorelines, from the US government coastal topographic maps listed in the associated map bibliography files (see the Sourcebibs directory). These generally show data extending from the mid to late 1800’s to the mid to late 1970’s. The mhw positions have been extracted and tabulated (see the MWHfiles directory) relative to fixed reference “R” points along the beach, spaced approximately 1000 feet (300 meters) apart. Reference points not actually corresponding to actual “in the ground” survey markers are virtual “V” points. Mean high water positions have been and continue to be extracted from FDEP beach profile surveys from the 1970’s through the present and added to the tables. The beach profile data files from which mhw data have been extracted and added into the mhw tables can be found in the ProfileData directory and visually (for many areas) in the ClickOnProfiles directory. The beach profile files include elevation information along the entire length of the profiles. This profile data set has undergone up to fifteen additional quality control checks to ensure accuracy, reliability, and consistency with the historic database coordinate and bearing set. Note that any data deeper than wading depth have not yet undergone any extra quality control checks. Note also that there are *.cod text files of notes associated with the review of the profile data files.The digital historic shoreline map image files are given in a DWG autocad-based format, which should be usable on most versions, as well as many GIS systems. The Florida State Plane 1927/79-adjusted and 1983/90 horizontal coordinate systems are used. These are not metric systems, but with the proper software can be converted to whatever systems you may need. Each map image DWG file contains many layers, documented in an ASCII layer list archived with the DWG file.The database has been maintained and greatly expanded by E. Foster since approximately 1987 and by N. Nguyen since 1995. The initial map digitizing effort was done for FDEP at Florida State University, primarily by S. Demirpolat. Final processing and editing of the original map files to make them user-friendly was performed by N. Nguyen and E. Foster in 1995-7. Extensive quality control and update work has been performed by E. Foster since 1987, and by N. Nguyen since 1995. Field profile surveys have been performed by the FDEP Coastal Data Acquisition section since the early 1970’s, and by a number of commercial surveyors in recent years.The formats of the mhw tables and profile files are explained in text files included in the respective directories.Note that the digitized map image files were originally created in the UTM coordinate system on Intergraph equipment. The translation from UTM to the State Plane coordinate systems has resulted in some minor textual and other visual shifts in the northwest Florida area map image files.The dates in the map legends in the map images are generally composite dates. It is necessary to use the mhw data tables and map bibliographies for accurate dates for any specific location. The date ranges in the data tables relate to specific information given in the map bibliography files.2Generally it may be assumed that the historic shorelines have been digitized as carefully as possible from the source maps. If a historic shoreline does not contain a systematic position error and is feasible in a physical sense, the accuracy of the mhw position is estimated at plus or minus 15 to 50 feet (5 to 15 m), depending on the source and scale. This is as a position in time, NOT as an average mhw position. Data added from field surveys are estimated at plus or minus 10 feet (3 m) or better.It is to be noted that from the 1920’s onward, aerial photographs have usually been the basis of the US government’s coastal topographic maps. Prior to that, the method was plane table surveying. Along higher wave energy coasts, especially the Florida east coast, if there was significant wave activity in the source photography, it is very possible that the mhw was mapped in a more landward location than was probably correct. Alternatively, the use of photography sets with excessive sun glare may have caused the mhw to be mapped in a more seaward location than was probably correct. These effects have been frequently observed in comparisons of close-in-time FDEP controlled aerial photography with FDEP profile surveys. The use of some photography sets containing high wave uprush or sun glare is probable within the historic data. For example, on the east coast the 1940’s series maps tend to show the mhw more seaward than expected, possibly due to sun glare, and the 1960’s series tend to show the mhw more landward than expected. In the latter case, the effect may be due to the 1960’s being a decade of frequent storms. It is recommended that the analyst be aware that some of these effects may exist in the historic data. A questionable historic shoreline is NOT necessarily one to be discarded, just considered with allowance for its’ potential limitations.Using this database, it can readily be observed that the historic trends in shoreline evolution are very consistent with behavior expected from the longshore transport equation, well known to coastal engineers. This is a non-linear equation. Shoreline change can be expected to be linear or constant only in certain situations. It is NOT recommended that any analyst arbitrarily assume constant or linear shoreline change rates over long periods of time, which is often done but not supported by the evidence. The three primary factors controlling shoreline change are sand supply, wave climate, and local geographic features. In some parts of Florida, major storms since 1995 have also become important factors.</DIV></DIV> Florida Department of Environmental Protection Water Feature Class 0.000 dataset 21 Simple FALSE 21 TRUE FALSE MeanHighWaterLines_Historical Feature Class 21 OBJECTID FID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 4 0 0 Feature geometry. Esri Coordinates defining the features. Layer Layer String 254 0 0 Shape.STLength() Shape.STLength() Double 0 0 0 20240408 EPSG 8.9.3(9.0.0)