Archive of Digital Chirp Sub-bottom Profile Data Collected During USGS Cruise 07SCC01 Offshore of the Chandeleur Islands, Louisiana, June 2007

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Archive of Digital Chirp Sub-bottom Profile Data Collected During USGS Cruise 07SCC01 Offshore of the Chandeleur Islands, Louisiana, June 2007
Abstract:
In June of 2007, the U.S. Geological Survey (USGS), in cooperation with the Louisiana Department of Natural Resources (LDNR), conducted a geophysical survey offshore of the Chandeleur Islands, Louisiana. This report serves as an archive of unprocessed digital Chirp sub-bottom profile data, trackline maps, navigation files, GIS information, FACS logs, observer's logbook, and formal FGDC metadata. Gained digital images of the sub-bottom profiles are also provided.
For more information on the seismic surveys see http://walrus.wr.usgs.gov/infobank/g/g107la/html/g-1-07-la.meta.html
These data are also available via GeoMapApp (http://www.geomapapp.org/) and Virtual Ocean ( http://www.virtualocean.org/) earth science exploration and visualization applications.
Supplemental_Information:
The USGS St. Petersburg Coastal and Marine Science Center (SPCMSC) assigns a unique identifier to each cruise or field activity. For example, 07SCC01 tells us the data were collected in 2007 for the Subsidence and Coastal Change (SCC) study and the data were collected during the first field activity for that study in that calendar year. Refer to <http://walrus.wr.usgs.gov/infobank/programs/html/definition/activity.html> for a detailed description of the method used to assign the cruise or field activity ID. The naming convention used for each trackline is as follows: yye##a, where 'yy' are the last two digits of the year in which the data were collected, 'e' is a 1-letter abbreviation for the equipment type (for example, c for SB-424 and i for SB-512i Chirp), '##' is a 2-digit number representing a specific track, and 'a' is a letter representing the section of a line if recording was prematurely terminated or rerun for quality or acquisition problems. The Chirp systems used a signal of continuously varying frequency. The towfish is the sound source and receiver, which is typically towed 1 - 2 m below the sea surface. The acoustic energy is reflected at density boundaries (such as the seafloor or sediment layers beneath the seafloor), detected by a receiver, and recorded by a PC-based sub-bottom acquisition system. This process is repeated at timed intervals (for example, 0.125 s) and recorded for specific intervals of time (for example, 50 ms). In this way, a two-dimensional vertical image of the shallow geologic structure beneath the ship track is produced. The sub-bottom source employed for Chirp data collection, during this cruise, consisted of an EdgeTech (FSSB) XStar SB-424 and SB-512i towfish running Triton Imaging SB Logger V. 1.6.4.37.73 acquisition software that was towed about 5.83 m behind the GPS antenna. The frequency range was 4 - 16 kHz (SB-424) and from 0.5 - 8 kHz to 0.5 - 6 kHz (SB-512i). Sample frequencies of the data for the 512i and 424 were 21 and 25 kHz, respectively, and record length was approximately 50 ms. A total of 2 lines were collected using the 424 system and 47 were collected with the 512i. For each recorded shot of the Chirp data, 3 channels of trace data are collected. Channel 2 is the "real," or in-phase component of the signal, channel 1 is the "imaginary," or quadrature component of the signal, and channel 0 is the "envelope," or product of channels 1 and 2. Only channel 0 was used to produce the profiles presented here. However, all channels are included in the SEG-Y data files. The archived trace data are in standard SEG-Y rev 1, 4-byte integer, IBM float format (Norris and Faichney, 2002); an ASCII format is used for the first 3,200 bytes of the card image header instead of the SEG-Y rev 0 (Barry and others, 1975) EBCDIC format. The SEG-Y files may be downloaded and processed with commercial or public domain software such as Seismic Unix (SU) Release 41 (Cohen and Stockwell, 2005). See the How To Download SEG-Y Data page for download instructions. The SEG-Y formatted trace files have a .sgy extension. Also provided are example SU scripts that allow the user to strip off navigation fixes from the SEG-Y headers, along with a fix for every 1,000 shots, and produce a printable, gained GIF image of each profile. The processed SEG-Y data were exported to Chesapeake Technology, Inc. (CTI) SonarWeb version 3.16.0096 PRO software to produce an interactive version of the profile that allows the user to obtain a geographic location and depth from the profile for a cursor position. This information is displayed in the status bar of the browser. NOTE: The only supported Web browsers that properly display all features of the interactive profiles are Internet Explorer 8 or greater for Windows and Firefox 3.6 or greater for all platforms. For all browsers, the status bar and JavaScript must be enabled. Firefox also requires "Change status bar text" to be checked under Advanced JavaScript Options. If using Internet Explorer 8, you must disable scripts/Active X controls. To do this, right click the information bar (found at the top of the page), left click "Allow Blocked Content...", and then select "Yes". Use of other browsers may result in spurious or no information given in the status window. Firefox may be downloaded at <http://www.mozilla.org/products/firefox>. Post-processing of the data also revealed the first shot value recorded to the SEG-Y headers of lines 07i1, 07i4, 07i5, 07i7, 07i9, 07c14, 07c15, 07i16, 07i17, 07i18, 07i21, 07i22, 07i24, 07i27, 07i31, 07i32, 07i35, 07i36, 07i37, 07i40, 07i42, 07i45, 07i47 to be something other than one. A conversion program called Fixping V. 1.0.0 was used to correct this issue; these corrected SEG-Y files are provided in this archive.
  1. How might this data set be cited?
    Forde, Arnell S., Dadisman, Shawn V., Flocks, James G., and Wiese, Dana S., 2010, Archive of Digital Chirp Sub-bottom Profile Data Collected During USGS Cruise 07SCC01 Offshore of the Chandeleur Islands, Louisiana, June 2007: U.S. Geological Survey Data Series 553, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -89.300898
    East_Bounding_Coordinate: -88.855756
    North_Bounding_Coordinate: 30.148091
    South_Bounding_Coordinate: 29.417192
  3. What does it look like?
    http://pubs.usgs.gov/ds/553/maps/cruisenav/07scc01_location_map.jpg (JPEG)
    Location map of all digital sub-bottom profile data collected during USGS field activity 07SCC01. This map was created at a scale of 1:1,000,000. Refer to the Lineage section below for the trackline map creation process and other details.
    http://pubs.usgs.gov/ds/553/maps/cruisenav/07scc01_north.jpg (JPEG)
    Trackline map of digital sub-bottom profile data collected around the northern Chandeleur Islands (refer to Northern Islands area on the location map) during USGS field activity 07SCC01. This map was created at a scale of 1:250,000.
    <http://pubs.usgs.gov/ds/553/maps/cruisenav/07scc01_south.jpg> (JPEG)
    Trackline map of digital sub-bottom profile data collected around the southern Chandeleur Islands (refer to Southern Islands area on the location map) during USGS field activity 07SCC01. This map was created at a scale of 1:215,000.
    http://pubs.usgs.gov/ds/553/profiles/printable/ (GIF)
    Directory containing printable images of all sub-bottom profiles.
    http://pubs.usgs.gov/ds/553/nav/procnav/07scc01.txt (ASCII Text File)
    Processed shotpoint navigation file for all tracklines collected during field activity 07SCC01.
    http://pubs.usgs.gov/ds/553/nav/shotnav/s07scc01.txt (ASCII Text File)
    Processed 1,000 shotpoint navigation file for all tracklines collected during field activity 07SCC01.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 02-Jun-2007
    Ending_Date: 13-Jun-2007
    Currentness_Reference:
    Data collection interval
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Sub-bottom Profile Section
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference:
      Horizontal X and Y locations (latitude and longitude coordinates) for each shot are provided as ASCII text files, along with the day of year and time (UTC) the shot was recorded.
      This is a Point data set.
    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 North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.25722210100002.
  7. How does the data set describe geographic features?
    07scc01.txt, s07scc01.txt, and 07scc01_s.txt
    Shotpoint navigation files (Source: Society of Exploration Geophysicists (SEG)-Y headers (<http://www.seg.org/publications/tech-stand>).)
    FID*
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    Shape*
    Feature geometry. (Source: ESRI) Coordinates defining the features.
    UTMX
    UTM-X coordinate (Zone 16) (Source: Universal Transverse Mercator Geographic Coordinate System)
    Range of values
    Minimum:276868
    Maximum:3320625
    UTMY
    UTM-Y coordinate (Zone 16) (Source: Universal Transverse Mercator Geographic Coordinate System)
    Range of values
    Minimum:3256523
    Maximum:3336173
    Line
    Trackline number (Source: U.S. Geological Survey)
    Range of values
    Minimum:07i01
    Maximum:07i49
    Shot
    Shotpoint number (Source: U.S. Geological Survey)
    Range of values
    Minimum:1
    Maximum:20000
    Lon
    Longitude (decimal degrees) (Source: Geographic Coordinate System North American Datum of 1983)
    Range of values
    Minimum:-89.274896
    Maximum:-88.856922
    Lat
    Latitude (decimal degrees) (Source: Geographic Coordinate System North American Datum of 1983)
    Range of values
    Minimum:29.419127
    Maximum:30.143049
    YEAR
    Year (Source: U.S. Geological Survey)
    Range of values
    Minimum:2007
    Maximum:2007
    DOY:HR:MIN:SEC
    Day of year:hour:minute:second (Source: Coordinated Universal Time) Day of year, hour, minute and second of data acquisition
    Entity_and_Attribute_Overview:
    Binary data file: Trace data are available as binary files in SEG-Y format. These files have a .sgy extension and range in size from 9 to 262 MB.
    Entity_and_Attribute_Overview:
    Graphic image file: Printable versions of the sub-bottom profiles are available as GIF images. Interactive profiles are available as HTML pages with accompanying JPEG images. The line navigation maps and trackline maps are JPEG images. The trackline maps contain links to the sub-bottom profiles and line navigation maps.
    Entity_and_Attribute_Overview:
    Navigation file: Navigation files are available as ASCII text files. Provided are raw (unprocessed) shotpoint navigation files, processed shotpoint navigation files, and processed 1,000-shot-interval location files. Fields/Attributes [FID, Shape] marked above with an asterick (*) were created by ESRI ArcGIS and are used exclusively by the shapefiles created from the aforementioned .txt files; these fields are not included in the original navigation files. All remaing attributes listed in the above section that do not have an accompanying asterick are found in 07scc01.txt, s07scc01.txt, and 07scc01_s.txt.
    Entity_and_Attribute_Overview:
    GIS file: The GIS project used to create the trackline maps is provided as a .zip file composed of ESRI map documents, shapefiles, and metadata.
    Entity_and_Attribute_Detail_Citation:
    Barry, K.M., Cavers, D.A., and Kneale, C.W., 1975, Recommended standards for digital tape formats: Geophysics, v. 40, no. 2, p. 344-352. Also available on-line at http://www.seg.org/SEGportalWEBproject/prod/SEG-Publications/Pub-Technical-Standards/Documents/seg_y_rev0.pdf.
    Entity_and_Attribute_Detail_Citation:
    Cohen, J.K., and Stockwell, J.W., Jr., 2010, CWP/SU: Seismic Unix Release 41: A free package for sub-bottom research and processing, Center for Wave Phenomena, Colorado School of Mines. Available on-line at <http://www.cwp.mines.edu/cwpcodes/index.html>.
    Entity_and_Attribute_Detail_Citation:
    Disc Image Credit: Descloitres, J., MODIS Land Rapid Response Team at the NASA Goddard Space Flight Center, 2001, Mississippi.A2001361.1640.250m.jpg. Available on-line at <http://visibleearth.nasa.gov/view_rec.php?id=2364>
    Entity_and_Attribute_Detail_Citation:
    Norris, M.W., and Faichney, A.K., eds., 2002, SEG Y rev 1 Data Exchange format: Society of Exploration Geophysicists. Also available on-line at <http://www.seg.org/SEGportalWEBproject/prod/SEG-Publications/Pub-Technical-Standards/Documents/seg_y_rev1.pdf>.
    Entity_and_Attribute_Detail_Citation:
    Zihlman, F.N., 1992, DUMPSEGY V1.0: A program to examine the contents of SEG-Y disk-image sub-bottom data: U.S. Geological Survey Open-File Report 92-590, 28 p. Also available on-line at <http://pubs.er.usgs.gov/usgspubs/ofr/ofr92590>.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Arnell S. Forde
    • Shawn V. Dadisman
    • James G. Flocks
    • Dana S. Wiese
  2. Who also contributed to the data set?
    Funding for this study was provided by the LDNR and USGS CMGP. We thank R/V G.K. Gilbert captain Richard Young of the USGS in St. Petersburg, FL, for his assistance in data collection. This document was improved by the reviews of Jordan Sanford (USGS) and Jamie Bonisteel-Cormier (Jacobs Technology Inc.) of the USGS St. Petersburg Coastal and Marine Science Center.
  3. To whom should users address questions about the data?
    James Flocks
    USGS
    Geologist
    600 4th Street South
    Saint Petersburg, FL
    USA

    (727) 803-8747 extension 3012 (voice)
    jflocks@usgs.gov

Why was the data set created?

The data archived here were collected as part of the USGS Barrier Island Comprehensive Monitoring (BICM) project, which is part of a broader study focused on Subsidence and Coastal Change. The purpose of the study was to investigate the shallow geologic framework and monitor the enviromental impacts of Hurricane Katrina (Louisiana landfall was on August 29, 2005) on the Gulf Coast's barrier island chains.

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: 2010 (process 1 of 8)
    SEG-Y header processing: All erroneous lines were first processed with FixPing V.1.0.0 software to correct first shot values that were other than 1 within the trace headers. These corrected SEG-Y files are included in this archive.
    Date: 2010 (process 2 of 8)
    Chirp processing: The SEG-Y data were processed with Seismic Unix software to produce gained GIF images of the sub-bottom profiles included in this report. A representative Chirp data processing sequence consisted of (1) stripping off channel 0 for each shot and converting to SU format, (2) applying automatic gain control, (3) displaying PostScript, and (4) converting of PostScript image to a GIF image. For additional SU processing and script details, please refer to <http://pubs.usgs.gov/ds/553/software/su/readme.txt> All the processed SEG-Y data were later exported to CTI SonarWeb V.3.16.0096 PRO software to produce an interactive, geospatial version of each profile that allows the user to obtain a geographic location and depth for a given cursor position on the profile. Refer to the Supplemental Information section above for details on how to use the interactive profiles. Person who carried out this activity:
    Arnell S. Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL

    (727) 803-8747, ext. 3111 (voice)
    aharrison@usgs.gov
    Date: 2010 (process 3 of 8)
    Navigation processing: Shotpoint navigation, start of line, and 1,000-shot-interval location files were extracted using Seismic Unix software and output as ASCII text files; they were then processed with PROJ.4.7.0 (<http://trac.osgeo.org/proj/>) to generate UTM coordinates from latitude and longitude coordinates. Text files for each seismic line were concatenated into two comma-delimited text files (for use with ESRI software), one containing unique shotpoint positions (07scc01.txt) and another containing the 1,000 shot interval locations (s07scc01.txt); both can be viewed within the nav folder, refer to the Browse_Graphic section above for details. NOTE: During data collection of line 07i47, the navigation system cable became disconnected from the acquisition system; consequently, no navigation data were collected between shot 584 and 9484 (an interval of approximately 30 minutes). [This line is displayed on the Northern Islands map as as dashed yellow line.] Due to the aforementioned error and the lack of other concurrently running acquisition systems, additional/replacement navigation could not be used and the shotpoint navigation processing script was unable to interpolate between points. Since discrete navigation fixes were not recorded for shots 1000 through 9000, only one latitude and longitude fix (from shotpoint 584), -88.952519, 30.140927, was associated with line 07i47 of the processed shotpoint navigation file.
    Date: 2010 (process 4 of 8)
    Both concatenated, comma-delimited text files were imported into ESRI ArcGIS 9.3 and saved as either a point (07scc01_shots.shp) or polyline (07scc01_tracklines.shp) file in the ESRI shapefile format.
    Date: 2010 (process 5 of 8)
    Trackline map creation: The trackline maps provided in this archive were created using the Points to Lines ArcScript (D. Rathert, <http://arcscripts.esri.com/details.asp?dbid=12702>) along with ESRI ArcGIS 9.3 software and then exported to Adobe Illustrator V. 12.0.1 for further editing. The maps were later converted into JPEG format by Adobe GoLive 8.0.1. The maps are unprojected (geographic coordinates, NAD83). The coastline layer is a Louisiana Oil Spill Coordinator's Office (LOSCO) dataset. The USGS is the originator of all other layers used. A map of trackline navigation for each sub-bottom profile was also produced with CTI SonarWeb V.3.16.0096 PRO software.
    Date: 2010 (process 6 of 8)
    Data Series preparation: In addition to the process steps described above, the following steps were taken to produce this Data Series: the handwritten logs were scanned and saved as PDF files, digital FACS logs were created using the handwritten logs and personal accounts of the crew members and saved as PDF files, and an HTML-based format was used to present the various parts of this archive.
    Date: 24-Jan-2017 (process 7 of 8)
    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: 13-Oct-2020 (process 8 of 8)
    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?

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

  1. How well have the observations been checked?
    The validity or accuracy of marine sub-bottom profiles is highly qualitative and depends on equipment and operating condition variables. Visual inspection of the images rendered from the data did not show any major anomalies. Minor anomalies include a distortion in the profile image after shot 1500 of line 07i20 (this was due to interference in the acquisition system introduced by a nearby thunderstorm) and lines 07c14, 07c15, and 07i40 (the interference was of unknown origin). During data collection, the frequency range for lines 07i46 - 07i48 was changed from 0.5 - 8 kHz to 0.5 - 6 kHz; the effects of this change can be observed in both the water column and the subsurface of the profile.
  2. How accurate are the geographic locations?
    As the sub-bottom profiles were acquired, the position of the vessel was continuously determined by a Coda Octopus F190 DGPS receiver, which is accurate to within 20 cm. Positions were recorded and written to the trace headers in latitude and longitude coordinates about every 1 s. The ASCII navigation files and trackline maps have not been corrected to reflect the approximately 5.83-m offset between the Chirp and GPS antenna. Refer to figure 1 included with this archive (Data Series 553) for a diagram of the acquisition geometry, including the GPS offset measurements. Line navigation maps and interactive profiles generated with CTI SonarWeb software have been corrected for the GPS offset.
  3. How accurate are the heights or depths?
    These data are not to be used for bathymetry. Depths shown on the Chirp profiles are relative to the depth of the towfish, not to sea level. Furthermore, the raising or lowering of the towfish during a survey (to avoid obstacles or follow relief) produces a relative shift in the multiple reflections seen in the profile, which may be confused as a geologic feature. Any elevation change of the towfish should be recorded in the logbooks and is evident on the sub-bottom profiles by steep, abrupt shifts in the seafloor return.
  4. Where are the gaps in the data? What is missing?
    These data are collected along tracklines (2-D) and are therefore inherently incomplete. Geologic details between lines must be inferred.
  5. How consistent are the relationships among the observations, including topology?
    This dataset is from one field activity with consistent instrument calibrations. Tracklines 07i1 - 07i13 and 07i16 - 07i49 were collected using the EdgeTech SB-512i system. Tracklines 07c14 and 07c15 were collected using the EdgeTech SB-424 system.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None. These data are held in the public domain.
Use_Constraints:
The USGS requests that it be acknowledged as originator of the data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    Arnell Forde
    U.S. Geological Survey
    Geologist
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 803-8747, ext. 3111 (voice)
    aharrison@usgs.gov
    Contact_Instructions: All of this report except the SEG-Y files is available on-line.
  2. What's the catalog number I need to order this data set? U.S. Geological Survey Data Series 553
  3. What legal disclaimers am I supposed to read?
    This DVD 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: The SEG-Y standard format (Barry and others, 1975) consists of the following: a 3,600-byte reel identification header, with the first 3,200 bytes consisting of an EBCDIC header block followed by a 400-byte binary header block, both of which include information specific to line and reel number; a trace data block that follows the reel identification header, with the first 240 bytes of each trace block consisting of the binary trace identification header; and sub-bottom data samples that follow the trace identification header. in format SEG-Y Size: 9590
      Media you can order: DVD (format ISO 9660)
      Note: Unix, Linux, DOS, Macintosh
      Data format: The GIS project used to create the trackline maps is composed of map documents, shapefiles, and metadata. Map documents were created with ESRI ArcGIS 9.3 software. The shapefiles provided may also be viewed using other versions of of ESRI desktop software including their free software, ArcGIS Explorer (http://www.esri.com/software/arcgis/explorer/index.html), or GeoMapApp (<http://www.geomapapp.org/>). in format map document, shapefile, metadata Size: 41.7
      Network links: http://pubs.usgs.gov/ds/553/software/arc/arc.zip
      Data format: The SEG-Y standard format (Barry and others, 1975) consists of the following: a 3,600-byte reel identification header, with the first 3,200 bytes consisting of an EBCDIC header block followed by a 400-byte binary header block, both of which include information specific to line and reel number; a trace data block that follows the reel identification header, with the first 240 bytes of each trace block consisting of the binary trace identification header; and sub-bottom data samples that follow the trace identification header. in format Download SEGY data Size: 9590
      Network links: http://cmgds.marine.usgs.gov/data/07scc01/chirp/
    • Cost to order the data: Prices vary.

    • Special instructions:
      Publications are available from USGS Information Services, Box 25286, Federal Center, Denver, CO 80225-0046 (telephone: 1-888-ASK-USGS, e-mail: infoservices@usgs.gov).
  5. What hardware or software do I need in order to use the data set?
    Use of SEG-Y data requires specialized sub-bottom processing software, such as public domain software Seismic Unix (<http://www.cwp.mines.edu/cwpcodes/index.html>).

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2020
Metadata author:
Arnell Forde
U.S. Geological Survey
Geologist
600 4th Street South
St. Petersburg, FL
USA

(727) 803-8747, ext. 3111 (voice)
aharrison@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/ds-553metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:54 2021