Ardhuin, 2002: coast of Duck, North Carolina

Frequently-anticipated questions:

• What does this data set describe?
  1. How should 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?

Title: Ardhuin, 2002: coast of Duck, North Carolina

Abstract:

Sediment and bedform data obtained in the course of ONR research on the U.S. east coast continental shelf off North Carolina

1. How should this data set be cited?

   Ardhuin, F., 2002, Ardhuin, 2002: coast of Duck, North Carolina.

   Online Links:

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -75.738170

   East_Bounding_Coordinate: -74.837500

   North_Bounding_Coordinate: 36.584300

   South_Bounding_Coordinate: 36.113350

3. What does it look like?

   ardhuin.jpg (JPEG)

   Image map showing extent and distribution of data layer coverage

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

   Calendar_Date: Pre-2002

   Currentness_Reference: ground condition

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

   Geospatial_Data_Presentation_Form: document

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):

      • Entity point (234)

   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.000000. Longitudes are given to the nearest 0.000000. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.400000.
      The flattening of the ellipsoid used is 1/294.978698.
      

7. How does the data set describe geographic features?

   ardhuin

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   LATITUDE

   Latitude of coordinate description (Source: Source report)

   LONGITUDE

   Longitude of coordinate description (Source: Source report)

   SITENAME

   Survey or laboratory code for site (Source: Data compiler)

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • F. Ardhuin

2. Who also contributed to the data set?

   Please review the cross reference information for the original data set credit to Ardhuin (2002.)

3. To whom should users address questions about the data?

To create a digital version of ONR data related to bedform research for inclusion in the usSEABED data collection

1. From what previous works were the data drawn?

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

   (process 1 of 3)

   Data was digitized in MapInfo from this paper's figures for a Roughness paper with georegistration internally accurate to 1 or 2 pixels per diagram.

   Person who carried out this activity:
   

   Chris Jenkins
   Institute of Arctic & Alpine Research (INSTAAR) University of Colorado at Boulder
   1560 30th Street
   Boulder, CO 80309-0450
   USA
   

   (303) 492-6387 (voice)
   (303) 492-6388 (FAX)
   chris.jenkins@colorado.edu
   

   (process 2 of 3)

   Grainsizes estimated from colour of dots vs spectral scale (acc=0.02mm) [Sites 50 & 51 were not plotted on the GRZ map)

   Person who carried out this activity:
   

   Chris Jenkins
   Institute of Arctic & Alpine Research (INSTAAR) University of Colorado at Boulder
   1560 30th Street
   Boulder, CO 80309-0450
   USA
   

   (303) 492-6387 (voice)
   (303) 492-6388 (FAX)
   chris.jenkins@colorado.edu
   

   (process 3 of 3)

   Digital data were checked, formatted to dbSEABED input format, then processed using dbSEABED software to produce a range of output formats. The processing contained quality checking that may have declined to pass faulty or suspect data to outputs.

   Person who carried out this activity:
   

   Chris Jenkins
   Institute of Arctic & Alpine Research (INSTAAR) University of Colorado at Boulder
   1560 30th Street
   Boulder, CO 80309-0450
   USA
   

   (303) 492-6387 (voice)
   (303) 492-6388 (FAX)
   chris.jenkins@colorado.edu
   

3. What similar or related data should the user be aware of?

   Ardhuin, F., Drake, T.G., and Herbers, T.H.C., 2002, Observations of wave-generated vortex ripples on the North Carolina continental shelf: Journal of Geophysical Research VOL. 107, NO. C10, 3143.

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 observations, including topology?

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

Access_Constraints: None.

Use_Constraints: None.

1. Who distributes the data set?[Distributor contact information not provided.]

2. What's the catalog number I need to order this data set?

   Ardhuin, 2002 data

3. What legal disclaimers am I supposed to read?

   Although this data set has been used by the U.S. Geological Survey (USGS), no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and/or related materials. 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. Trade, firm, or product names and other references to non-USGS products and services are provided for information only and do not constitute endorsement or warranty, express or implied, by the USGS, USDOI, or U.S. Government, as to their suitability, content, usefulness, functioning, completeness, or accuracy.

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

     Data format:	Size: 0.040

   • Cost to order the data:

Dates:

Last modified: 25-May-2005
Last Reviewed: 03-May-2005

Metadata author:

Jamey Reid
U.S. Geological Survey
IT Specialist (Data Management)
384 Woods Hole Rd.
Woods Hole, MA 02543-1598

(508) 548-8700 x2204 (voice)
(508) 457-2310 (FAX)
jreid@usgs.gov

Metadata standard:

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

Metadata extensions used:

• <http://www.esri.com/metadata/esriprof80.html>