Topographic survey transect data along the Carmel River, central California, 2013 to 2021 (ver. 2.0, March 2022)

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?
   East, Amy, Harrison, Lee R., Smith, Douglas P., Bond, Rosealea, Logan, Joshua, Nicol, Colin, and Chow, Kaitlyn, 20220331, Topographic survey transect data along the Carmel River, central California, 2013 to 2021 (ver. 2.0, March 2022): data release doi:10.5066/P9HG8UDS, U.S. Geological Survey, Pacific Coastal and Marine Science Center Santa Cruz, California.

   Online Links:

   • https://doi.org/10.5066/P9HG8UDS
   • https://www.sciencebase.gov/catalog/item/61ef2f19d34e8b818adb7ba7

   This is part of the following larger work.
   East, Amy, Harrison, Lee R., Smith, Douglas P., Bond, Rosealea, Logan, Joshua, Nicol, Colin, and Chow, Kaitlyn, 2017, River-channel topography, grain size, and turbidity records from the Carmel River, California, before, during, and after removal of San Clemente Dam (ver. 2.0, March 2022): data release doi:10.5066/P9HG8UDS, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

   Online Links:

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

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -121.93733
   East_Bounding_Coordinate: -121.70072
   North_Bounding_Coordinate: 36.54163
   South_Bounding_Coordinate: 36.42018
   

3. What does it look like?

   https://www.sciencebase.gov/catalog/file/get/5a2ed8c2e4b08e6a89d3fc22?name=Carmel_2013to2021_TransectEndpointsMap.png&allowOpen=true (png)

   Transect endpoint locations of topographic surveys (BW=Berwick, CR=Control Reach, CRO=Crossroads, DDL=DeDampierre Lower, DDU=DeDampierre Upper, DM=Dam Reach, RS=Reservoir Reach, SC=San Carlos, SH=Sleepy Hollow, SR=Schulte Road)

4. Does the data set describe conditions during a particular time period?

   Beginning_Date: 2013

   Ending_Date: 2021

   Currentness_Reference:

   ground condition

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

   Geospatial_Data_Presentation_Form: Comma-separated values
   

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?
      This is a Point data set. It contains the following vector data types (SDTS terminology):
      • Point (10452)
   2. What coordinate system is used to represent geographic features?
      

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:

      UTM_Zone_Number: 10
      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -123.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.001
      Ordinates (y-coordinates) are specified to the nearest 0.001
      Planar coordinates are specified in meters
      The horizontal datum used is NAD83 (National Spatial Reference System 2011) (EPSG:1116).
      The ellipsoid used is GRS 1980 (EPSG:7019).
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      

      Vertical_Coordinate_System_Definition:

      Altitude_System_Definition:

      Altitude_Datum_Name: North American Vertical Datum of 1988 (EPSG:5703)
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:

      Explicit elevation coordinate included with horizontal coordinates

7. How does the data set describe geographic features?

   Carmel_2013to2021_TransectData.csv

   Topographic measurements taken at 10 sites along 6 transects at each site on the Carmel River, from 2013 to 2021. (Source: Producer defined)

   PID

   Point ID. Not unique. For reaches CR, RS, DM and SH, the PID values are the values assigned during the survey and are only unique for each reach and year. For reaches DDU, DDL, BW, SR, SC and CRO, the PID values were assigned sequentially. (Source: Producer defined) A non-unique identification code for the point.

   SITE

   Site and transect number (Source: Producer defined.) A unique location identifier presented as an alpha-numeric code indicating the name of the survey site (BW=Berwick, CR=Control Reach, CRO=Crossroads, DDL=DeDampierre Lower, DDU=DeDampierre Upper, DM=Dam, RS=Reservoir, SC=San Carlos, SH=Sleepy Hollow, SR=Schulte Road) followed by a number indicating the survey transect.

   RIVERKM

   The distance in kilometers along the river to the measurement site from the river's mouth. (Source: Producer defined)

   Range of values
   Minimum:	2.08
   Maximum:	32.69
   Units:	kilometers

   YEAR

   The water year (October 1 to September 30) in which the measurement was made. (Source: Producer defined.)

   Range of values
   Minimum:	2013
   Maximum:	2021
   Units:	years

   DATE

   The date on which the measurement was made, in ISO 8601 date format (YYYY-MM-DD). Note that San Carlos (SC), 2013 measurements were made on calendar day 2014-03-07. Due to low river flows during the preceding months, the measurements made during this survey were determined to be representative of water year 2013. (Source: Producer defined.)

   Range of values
   Minimum:	2013-06-18
   Maximum:	2021-06-16
   Units:	YYYY-MM-DD

   NORTHING

   Northing coordinate of data point relative to the NAD83(2011) (North American Datum of 1983, National Spatial Reference System 2011) datum, projected in the Universal Transverse Mercator (UTM) Zone 10 North coordinate system, meters (EPSG:6339). For measurements made using an auto level, the northing coordinate is set to "NULL" to denote that the horizontal UTM coordinates were not measured for this data point. (Source: Producer defined)

   Range of values
   Minimum:	4031573.861
   Maximum:	4034148.471
   Units:	meters

   EASTING

   Easting coordinate of data point relative to the NAD83(2011) (North American Datum of 1983, National Spatial Reference System 2011) datum, projected in the Universal Transverse Mercator (UTM) Zone 10 North coordinate system, meters (EPSG:6339). For measurements made using an auto level, the easting coordinate is set to "NULL" to denote that the horizontal UTM coordinates were not measured for this data point. (Source: Producer defined)

   Range of values
   Minimum:	615053.606
   Maximum:	615896.390
   Units:	meters

   ELEVATION

   The elevation in meters at the point of measurement, relative to the NAVD88 (North American Vertical Datum of 1988) vertical datum. (Source: Producer defined)

   Range of values
   Minimum:	2.907
   Maximum:	169.475
   Units:	meters

   DISTANCE

   Distance in meters from the left benchmark across the river. (Source: Producer defined)

   Range of values
   Minimum:	0
   Maximum:	102.001
   Units:	meters

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • Amy East
   • Lee R. Harrison
   • Douglas P. Smith
   • Rosealea Bond
   • Joshua Logan
   • Colin Nicol
   • Kaitlyn Chow
2. Who also contributed to the data set?
   Data collection was funded by U.S. Geological Survey, California State University Monterey Bay, and National Oceanic and Atmospheric Administration
3. To whom should users address questions about the data?
   U.S. Geological Survey, Pacific Coastal and Marine Science Center

   Attn: PCMSC Science Data Coordinator

   2885 Mission Street

   Santa Cruz, CA
   

   831-427-4747 (voice)

   pcmsc_data@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: 2021 (process 1 of 2)

   Topographic measurements were made at four to six transects per site along the Carmel River between water years 2013 and 2021 using a total station at sites CR, RS, DM, and SH, and with an auto level and survey rod at sites DDU, DDL, BW, SR, SC, and CRO. This dataset contains the cross-sectional survey data for each site and year as distance from left end point vs elevation. All data were collected in NAD83 UTM10N horizontal coordinates and NAVD88 Geoid 12B vertical coordinates, in units of meters. Person who carried out this activity:
   

   Joshua Logan

   U.S. Geological Survey, Pacific Coastal and Marine Science Center

   Physical Scientist

   2885 Mission Street

   Santa Cruz, CA
   

   US

   831-460-7519 (voice)

   831-427-4748 (FAX)

   jlogan@usgs.gov

   Date: 2022 (process 2 of 2)

   Changes to version 2.0 of data release: -Added the following transect data: - RS transects surveyed in 2014 - Additional transects in RS (RS3B and RS5B) added in 2017 and 2019 after re-orientation of river channel. - DDU, DDL, BW, SR, SC, and CRO transects surveyed in 2018 - CR, RS, DM, SH, DDU, DDL, BW, SR, SC, and CRO transects surveyed in 2019 - DDU, DDL, BW, SR, and CRO transects surveyed in 2020 - DDU, DDL, transects surveyed in 2021 - Added horizontal UTM coordinates to all data points measured with a total station (reaches CR, RS, DM and SH). - Added a non-unique point ID field (PID). For reaches CR, RS, DM and SH, the PID values are the values assigned during the survey. For reaches DDU, DDL, BW, SR, SC and CRO, the PID values were assigned sequentially. - Recalculated distance from left bank for some transects to account for movement of reference point in response to channel widening and reorientation. - Changed method of calculating distance measurement for reaches CR, RS, DM and SH to account for measurements taken slightly off the line. The revised method projects each point to its closest position along the transect before calculating the Euclidean distance along the transect to the left-bank mark. - Corrected survey-rod height error for 8 measurements on river-right side (SE side, DISTANCE > 16.5) of transect DM6 surveyed in 2017. The incorrect rod height used was 2.568 meters; the correct rod height was 1.519 meters. Elevations for these points were increased by 1.049 meters accordingly. - Corrected errors in measurements from transect SC1, measured in 2015. Person who carried out this activity:
   

   Joshua Logan

   U.S. Geological Survey, Pacific Coastal and Marine Science Center

   Physical Scientist

   2885 Mission Street

   Santa Cruz, CA
   

   US

   831-460-7519 (voice)

   831-427-4748 (FAX)

   jlogan@usgs.gov

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?
   No formal attribute accuracy tests were conducted
2. How accurate are the geographic locations?
   Initial survey control for all topographic transects was established using static GPS occupations, which have an estimated horizontal accuracy of around 1.5 cm. For sites CR, RS, DM and SH control densification and transect horizontal measurements were conducted using a total station. Repeat check measurements conducted during the surveys on points with established coordinates suggest a horizontal precision of around 2 cm for measurements at these sites. For sites DDU, DDL, BW, SR, SC and CRO control densification was completed using a total station and transect horizontal measurements were conducted using a fiberglass tape stretched along the transect and recorded to the nearest centimeter. The horizontal precision of these measurements is estimated to be around 3 cm.
3. How accurate are the heights or depths?
   Initial survey control for all topographic transects was established using static GPS occupations, which have an estimated vertical accuracy of less than 3 cm. For sites CR, RS, DM and SH control densification and transect measurements were conducted using a total station. Repeat check measurements conducted during the surveys on points with established coordinates suggest a vertical precision of less than 2 cm for measurements at these sites. For sites DDU, DDL, BW, SR, SC and CRO control densification was completed using a total station. Transect elevation measurements for these sites were conducted using an auto level. The vertical precision of these measurements is estimated to be around 1 cm.
4. Where are the gaps in the data? What is missing?
   Data set is considered complete for the information presented, as described in the abstract. At most survey sites, there are six transects. However, there are only four transect at DeDampierre Lower (DDL) and Schulte Road (SR). 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?
   No formal logical accuracy tests were conducted

How can someone get a copy of the data set?

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

   U.S. Geological Survey - ScienceBase

   Denver Federal Center, Building 810, Mail Stop 302

   Denver, CO
   

   United States

   1-888-275-8747 (voice)

   sciencebase@usgs.gov
2. What's the catalog number I need to order this data set? data are downloadable in .csv format (Carmel_2013to2019_TransectData.csv) along with CMGDS FGDC-compliant metadata.
3. What legal disclaimers am I supposed to read?
   Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
4. How can I download or order the data?
   • Availability in digital form:

     Data format:	CSV file contains the transect data in format comma-delimited text Size: 0.7
     Network links:	https://www.sciencebase.gov/catalog/file/get/61ef2f19d34e8b818adb7ba7f https://www.sciencebase.gov/catalog/item/61ef2f19d34e8b818adb7ba7f https://doi.org/10.5066/P9HG8UDS

   • Cost to order the data: None.

5. What hardware or software do I need in order to use the data set?
   The downloadable data file is available in comma-separated values (CSV) spreadsheet format. Text editing software can be used to open the file, as well as spreadsheet programs, such as Microsoft Excel.

Who wrote the metadata?

Dates:

Last modified: 01-Apr-2022

Metadata author:

U.S. Geological Survey, Pacific Coastal and Marine Science Center

Attn: PCMSC Science Data Coordinator

2885 Mission Street

Santa Cruz, CA

831-427-4747 (voice)

pcmsc_data@usgs.gov

Metadata standard:

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