Shoreline Change Rates for Barnegat and Great Bay, NJ: 1839 to 2012 (ver 1.1, December 2017)

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?
   Smith, Kathryn E.L., and Terrano, Joseph F., 20170809, Shoreline Change Rates for Barnegat and Great Bay, NJ: 1839 to 2012 (ver 1.1, December 2017): U.S. Geological Survey Data Release doi:10.5066/F75X275C, U.S. Geological Survey, St. Petersburg, FL.

   Online Links:

   • https://doi.org/10.5066/F75X275C

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -74.577325105
   East_Bounding_Coordinate: -74.041075153
   North_Bounding_Coordinate: 40.081196268
   South_Bounding_Coordinate: 39.299815615
   

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

   Beginning_Date:

   Ending_Date: 01-Jan-2012

   Currentness_Reference:

   ground condition

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

   Geospatial_Data_Presentation_Form: Vector Digital Dataset (Polyline)
   

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.
   2. What coordinate system is used to represent geographic features?
      

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:

      UTM_Zone_Number: 18
      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -75.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.6096
      Ordinates (y-coordinates) are specified to the nearest 0.6096
      Planar coordinates are specified in Meter
      The horizontal datum used is D_North_American_1983.
      The ellipsoid used is GRS_1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      
7. How does the data set describe geographic features?

   Entity_and_Attribute_Overview:

   The entity and attributes in these datasets are compiled and generated by the AMBUR program given the input shoreline dataset and transects. No data values are left blank. Field descriptions with "NA" are used for AMBUR processing only and do not provide information that is useful for analysis. All distance units are in meters and time unites are in years. Therefore, rates of change would be in meters per year. For attribute definitions, see p. 37 of: Jackson, C.W., Jr., 2010. Basic User Guide for the AMBUR package for R, version 1.0a. http://ambur.r-forge.r-project.org/user/ambur%20basic%20user%20guide%201_0a.pdf (also included in data zip files).

   Entity_and_Attribute_Detail_Citation:

   Please review the rest of the metadata record for additional details and information. For details on AMBUR programming code, statistical analyses, and attributes, see the AMBUR project on the R-Forge web site (http://ambur.r-forge.r-project.org/) and the documentation: Jackson, C.W., Jr., 2010. Basic User Guide for the AMBUR package for R, version 1.0a. http://ambur.r-forge.r-project.org/user/ambur%20basic%20user%20guide%201_0a.pdf

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • Kathryn E.L. Smith
   • Joseph F. Terrano
2. Who also contributed to the data set?

   Acknowledgment of the U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center, as a data source would be appreciated in products developed from these data, and such acknowledgment as is standard for citation and legal practices. Sharing of new data layers developed directly from these data would also be appreciated by the U.S. Geological Survey staff. Users should be aware that comparisons with other datasets for the same area from other time periods may be inaccurate due to inconsistencies resulting from changes in photointerpretation, mapping conventions, and digital processes over time. These data are not legal documents and are not to be used as such.

3. To whom should users address questions about the data?
   U.S. Geological Survey St Petersburg Coastal and Marine Science Center

   Attn: Kathryn E.L. Smith

   Ecologist

   600 4th Street South

   St. Petersburg, FL
   

   727-502-8073 (voice)

   727-502-8182 (FAX)

   kelsmith@usgs.gov

Why was the data set created?

The purpose of these data is to examine the shoreline change rates for Barnegat and Great Bay, New Jersey.

How was the data set created?

1. From what previous works were the data drawn?

   Shorelines (source 1 of 1)

   Smith, K.E.L. and Terrano, J.F., 20170810, Shorelines for Barnegat and Great Bay, NJ: 1839 to 2012: U.S. Geological Survey, St Petersburg, FL.

   Online Links:

   • https://doi.org/10.5066/F75X275C

   Type_of_Source_Media: digital data
   Source_Contribution: Dataset containing compiled vector digital shorelines
   

2. How were the data generated, processed, and modified?

   Date: 2017 (process 1 of 2)

   Transects were generated by buffering the available shoreline datasets to create inner (land based) and outer (water based) baselines. The baselines form the start and end point for shoreline-perpendicular transects. Baselines were input into the AMBUR statistical package for R (version 3.3.2). AMBUR has several tools, which utilize shoreline parallel baselines to generate transects that are generally perpendicular to the shoreline. Transects were constructed at a sampling distance of 50 meters. Length varied from 1000 to 3000 meters, depending on location, and was selected to cover all dated shorelines. Once transects were created, the Filter Transects tool was used to adjust and even out the spread of transects. Where shorelines experience sharp bends, such as in small bays and narrow spits, transects may fall at a non-perpendicular angle. Final transects were checked and edited in ArcGIS (Version 10.3), if necessary, in order to improve analysis results and improve shoreline coverage. Transects were manually edited to reduce errors in the analyses. Shoreline points and final statistical analyses were completed in AMBUR to generate the shoreline change rates. The following analysis parameters were used: fist intersection (if transect intersects the same shoreline more than once, then by dfault it selected the first intersection), confidence level 95 (confidence level for the linear regression statisics), unit label m (the units of measure for the map is for UTM and in meters), analysis type is advanced (advanced includes additional statistics for a robust linear regression), and time unit for rates is yr (utilizes years for calculating rates of shoreline change). More information on the AMBUR program can be obtained from Jackson, C.W., Jr., 2010. Basic User Guide for the AMBUR package for R, version 1.0a. http://ambur.r-forge.r-project.org/user/ambur%20basic%20user%20guide%201_0a.pdf Person who carried out this activity:
   

   Kathryn Smith

   U.S. Geological Survey

   Ecologist

   600 4th St S

   St Petersburg, FL
   

   727-502-8073 (voice)

   727-502-8182 (FAX)

   kelsmith@usgs.gov

   Date: 13-Oct-2020 (process 2 of 2)

   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?
   Jackson, C.W., Jr., 2010, Basic User Guide for the AMBUR package for R, version 1.0a.

   Online Links:

   • http://ambur.r-forge.r-project.org/user/ambur%20basic%20user%20guide%201_0a.pdf

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

1. How well have the observations been checked?
   Shoreline change rates are influenced by availability and accuracy of shoreline data. Analyses of highly dynamic areas are particularly challenging, including 1) areas near inlets, where there is excessively dynamic depositional/erosional sand bars that may appear/disappear rapidly, and 2) stretches of backshore where overwash fans can form islands that are difficult to resolve and distinguish from barrier islands themselves. The End Point Rate (EPR) and Linear Regression Rate (LRR) were compared to identify and correct significant errors in the shoreline change rate.
2. How accurate are the geographic locations?
   A formal accuracy assessment of the horizontal positional information in the dataset has not been conducted.
3. How accurate are the heights or depths?
   A formal accuracy assessment of the vertical positional information in the dataset has either not been conducted, or is not applicable.
4. Where are the gaps in the data? What is missing?
   Dataset is considered complete for the information presented. Some dated shorelines do not have complete coverage over the entire study area (for example, 1839 shorelines were available for the estuarine shorelines of Long Beach Island, but not for the Barnegat Bay mainland region); however, this was acceptable as the analysis method accounts for the available dates only. Users are advised to read the rest of the metadata record carefully for additional details.
5. How consistent are the relationships among the observations, including topology?
   Vector features and attributes were checked for completeness and accuracy. Linework is generated by the "Construct transects" and "Filter transects" algorithm in the AMBUR program and are generally perpendicular to the shorelines. However, where shorelines experience sharp bends, such as in small bays and narrow spits, the filter algorithym can create transects that are not perpedicular to the shoreline.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:

The U.S. Geological Survey requests to be acknowledged as originator of the data in future products or derivative research.

1. Who distributes the data set? (Distributor 1 of 1)
   
   U.S. Geological Survey St Petersburg Coastal and Marine Science Center

   Attn: Kathryn E.L. Smith

   Ecologist

   600 4th Street South

   St. Petersburg, FL
   

   727-502-8073 (voice)

   727-502-8182 (FAX)

   kelsmith@usgs.gov
2. What's the catalog number I need to order this data set? NJ_SLC_foreshore_v1.1.zip, NJ_SLC_backshore_v1.1.zip, NJ_SLC_mainland_v1.1.zip, NJ_SLC_islands_and_tribs_v1.1.zip
3. What legal disclaimers am I supposed to read?

   This digital publication was prepared by an agency of the United States Government. Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the display or utility of the data on any other system, nor shall the act of distribution imply any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and (or) contained herein. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof.

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	ArcGIS Shapefile
     Network links:	https://coastal.er.usgs.gov/data-release/doi-F75X275C/data/NJ_SLC_mainland_v1.1.zip https://coastal.er.usgs.gov/data-release/doi-F75X275C/data/NJ_SLC_backshore_v1.1.zip https://coastal.er.usgs.gov/data-release/doi-F75X275C/data/NJ_SLC_foreshore_v1.1.zip https://coastal.er.usgs.gov/data-release/doi-F75X275C/data/NJ_SLC_islands_and_tribs_v1.1.zip

   • Cost to order the data: None. No fees are applicable for obtaining the dataset.

Who wrote the metadata?

Dates:

Last modified: 13-Oct-2020

Metadata author:

U.S. Geological Survey St Petersburg Coastal and Marine Science Center

Attn: Kathryn E.L. Smith

Ecologist

600 4th Street South

St. Petersburg, FL

727-502-8073 (voice)

727-502-8182 (FAX)

kelsmith@usgs.gov

Metadata standard:

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