St. Petersburg Coastal and Marine Science Center Geoscience Data Viewer Metadata

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

Frequently anticipated questions:

What does this data set describe?

Title:
St. Petersburg Coastal and Marine Science Center Geoscience Data Viewer Metadata
Abstract:
This web mapping application is a compilation of geoscientific data collected and published by the U.S. Geological Survey St. Petersburg Coastal and Marine Science Center (USGS SPCMSC). This application does not serve as a complete archive of all the geoscientific data collected by the center, but highlights frequently published data types. Data within this web application include: seismic data extents, seismic survey tracklines (boomer, chirp, and minisparker), bathymetric footprints (singlebeam, multibeam and/or interferometric swath), light detection and ranging (lidar) footprints, sidescan sonar mosaics, and geologic cores and samples (coral, coral reef, limestone, and sediment). The web application is currently published using Esri's (Environmental Systems Research Institute) ArcGIS Instant Apps.
Supplemental_Information:
Bathymetric Digital Elevation Models (DEMs) are no longer included in the web map and application as of August 2025. Users are advised to refer to the primary publications (via the bathymetry footprint pop-ups) for these data. Aside from the geological core and sample database feature layer, data included in this web mapping application are organized by year collected from newest (top) to oldest (bottom) or data type (seismic tracklines). The year collected is either represented by the year (YYYY format) or by USGS Field Activity Number or 'FAN'. Each FAN is a unique number given to data collected during a field activity. There are two common formats used for a FAN. The first is: ##XXX##. The first two digits represent the year the data were collected. The third through fifth digits represent the project identification information, coded by the USGS to be unique to each project. The last two digits represent the number of field activities in that year under that project code. The second format for a FAN is: ####-###-FA. The first four digits represent the year the data were collected and the second, 3-digit set represents numbers assigned to a specific USGS center (for example, USGS SPCMSC numbers begin at 301). FANs are publicly accessible via the USGS Coastal and Marine Geoscience Data System (CMGDS). To view field activity details for any of the samples included in this database, CMGDS can be used to look up the FANs, by replacing the FAN (2020-301-FA) in the following URL: https://cmgds.marine.usgs.gov/fan_info.php?fan=2020-301-FA. The geologic core and sample data is also available in its own web mapping application that contains additional functionalities and is available here, https://doi.org/10.5066/F7319TR3.
  1. How might this data set be cited?
    Williams, Breanna N., Schreppel, Heather A., and Douglas, Steven H., 20171105, St. Petersburg Coastal and Marine Science Center Geoscience Data Viewer Metadata:.

    This is part of the following larger work.

    Williams, Breanna N., Schreppel, Heather A., and Douglas, Steven H., 20171105, St. Petersburg Coastal and Marine Science Center Geoscience Data Viewer: U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center, St. Petersburg, Florida.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -124.046882
    East_Bounding_Coordinate: 162.250000
    North_Bounding_Coordinate: 46.740893
    South_Bounding_Coordinate: -3.272100
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 27-May-1974
    Ending_Date: present
    Currentness_Reference:
    publication date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: application/service
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
    2. What coordinate system is used to represent geographic features?
      The map projection used is WGS 1984 Web Mercator (Auxiliary Sphere).
      Projection parameters:
      Standard_Parallel: 0.0
      Longitude_of_Central_Meridian: 0.0
      False_Easting: 0.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 meter
      The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_84.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257223563.
  7. How does the data set describe geographic features?
    Seismic Data Extents
    Attribute table for the hosted feature layer of the data extents (study areas) of all published seismic data from the USGS SPCMSC since 1975. Seismic geophysical surveys are conducted to investigate the geologic controls on barrier islands and other coastal zone features. In the web mapping application, data is grouped into a single layer and symbolized by unique values (year) in a dark orange (newest) to a light yellow (oldest) color ramp. The names/alias for these fields may differ between the attribute table and pop-up. Additional details can be found by following the publication links in the pop-up for each data extent, or in the layer's service description (https://services.arcgis.com/v01gqwM5QqNysAAi/arcgis/rest/services/Seismic_Data_Extents/FeatureServer). (Source: USGS SPCMSC)
    startdate
    Calendar date of the start of the seismic data collection. (Source: USGS SPCMSC) Date in year, month, day (YYYYMMDD) format. If the exact date is unknown, only the year (YYYY) was used.
    enddate
    Calendar date of the end of the seismic data collection. (Source: USGS SPCMSC) Date in year, month, day (YYYYMMDD) format. If the exact date is unknown, only the year (YYYY) was used.
    type
    Type (method) of seismic data collected. (Source: USGS SPCMSC)
    ValueDefinition
    Analog BoomerBoomer is a type of seismic reflection profiling equipment that operate in the ~0.7 to 2 kilohertz (kHz) region, depending on the nature of the study. These reflections were recorded on analog paper records in the field and were later converted to digital format using a large-format continuous scanner.
    BoomerBoomer is a type of seismic reflection profiling equipment that operate in the ~0.7 to 2 kilohertz (kHz) region, depending on the nature of the study.
    ChirpChirp is a type of seismic reflection profiling equipment that operate in the ~2-50 kilohertz (kHz) region, depending on the nature of the study.
    MinisparkerMinisparker is seismic reflection profiling equipment that operate in the ~400-1200 hertz (Hz) region, depending on the nature of the study.
    fan
    Acronym for 'Field Activity Number', which is a unique identifier given to data collected during USGS SPCMSC field activities. (Source: USGS SPCMSC) Each FAN is a unique number given to data collected during a field activity. There are two common formats used for a FAN. The first is: ##XXX##. The first two digits represent the year the data were collected. The third through fifth digits represent the project identification information, coded by the USGS to be unique to each project. The last two digits represent the number of field activities in that year under that project code. The second format for a FAN is: ####_###_FA. The first four digits represent the year the data were collected and the second, 3-digit set represents numbers assigned to a specific USGS center (for example, USGS SPCMSC numbers begin at 301).
    region
    State(s) involved in the seismic data collection. (Source: USGS SPCMSC) Abbreviated state name in which the seismic data collection involved. If the data were collected across multiple states, they are listed in alphabetical order and separated by a hyphen (example: AL-MS).
    data_url
    Link to a download file for the seismic data. (Source: USGS SPCMSC) Link to the download file for the seismic profiles in Society of Exploration Geophysicists (SEG-Y) format (.seg). Left blank if no data of this type was included within the primary publication.
    gis_url
    Link to a download file for the seismic data. (Source: USGS SPCMSC) Link to the download file for the GIS seismic trackline data (typically in .shp or .kmz format). Left blank if no data of this type was included within the primary publication.
    prof_url
    Link to a download file for the seismic data. (Source: USGS SPCMSC) Link to the download file for the seismic profile images (typically in .tif format). Left blank if no data of this type was included within the primary publication.
    pub_url
    Link to the source publication webpage. (Source: USGS SPCMSC) Digital Object Identifier (DOI) link to the publication webpage of the seismic dataset.
    other_pub
    Link to an additional publication in which the dataset is published. (Source: USGS SPCMSC) Link to the additional publication webpage of the seismic dataset. Left blank if not applicable.
    Seismic Survey Tracklines pop-ups
    Pop-ups for the hosted feature layer of the seismic tracklines (the vessel position during the survey) for all the published seismic data from the USGS SPCMSC since 1975. Data within this dataset are grouped under three collection methods: boomer (also includes analog), chirp, and minisparker. Each grouped data type is order by year, newest to oldest. Individual layers are labeled using their USGS Field Activity Number (FAN) and associated publication. The attributes described below are present in the pop-ups of the hosted feature layer. Additional fields may be present in the attribute table of an individual trackline layer. The names/alias for these fields may also differ between the attribute table and pop-up. Users should refer the source publication information for more details by following the publication links in the pop-up for each data extent, or in the layer's service description (https://services.arcgis.com/v01gqwM5QqNysAAi/arcgis/rest/services/Seismic_Tracklines/FeatureServer). (Source: USGS SPCMSC)
    Line
    The trackline number, or unique identifier used during data collection. (Source: USGS SPCMSC) The trackline number, or unique identifier used during data collection. Users should refer to the source publication for more information about the naming convention of the line numbers.
    Field Activity Number
    A unique identifier given to data collected during field activities at USGS SPCMSC. (Source: USGS SPCMSC) Each FAN is a unique number given to data collected during a field activity. There are two common formats used for a FAN. The first is: ##XXX##. The first two digits represent the year the data were collected. The third through fifth digits represent the project identification information, coded by the USGS to be unique to each project. The last two digits represent the number of field activities in that year under that project code. The second format for a FAN is: ####_###_FA. The first four digits represent the year the data were collected and the second, 3-digit set represents numbers assigned to a specific USGS center (for example, USGS SPCMSC numbers begin at 301).
    Method
    Type (method) of seismic data collected. (Source: USGS SPCMSC)
    ValueDefinition
    Analog BoomerBoomer is seismic reflection profiling equipment that operate in the ~0.7 to 2 kilohertz (kHz) region, depending on the nature of the study. These reflections were recorded on analog paper records in the field and were later converted to digital format using a large-format continuous scanner.
    BoomerBoomer is seismic reflection profiling equipment that operate in the ~0.7 to 2 kilohertz (kHz) region, depending on the nature of the study.
    ChirpChirp is seismic reflection profiling equipment that operate in the ~2-50 kilohertz (kHz) region, depending on the nature of the study.
    MinisparkerMinisparker is seismic reflection profiling equipment that operate in the ~400-1200 hertz (Hz) region, depending on the nature of the study.
    Profile
    Link to a download file for the seismic data. (Source: USGS SPCMSC) Link to the download file for the seismic profile images (typically in .tif format). Left blank if no data of this type was included within the primary publication.
    Publication
    Link to the source publication webpage. (Source: USGS SPCMSC) DOI link to the publication webpage of the seismic dataset.
    Bathymetry Footprints, All Bathymetry Footprints
    Attribute table for the hosted feature layer of the footprints (study area) of all bathymetric datasets from the USGS SPCMSC since 1995. In the web mapping application, the layer displays footprints by year as individual layers (Bathymetry Footprints) and all footprints merged into one layer (All Bathymetry Footprints). Data is symbolized in a neon green (newest) to a light cyan (oldest) color ramp. Individual layers are labeled using their USGS Field Activity Number (FAN) and associated publication. The presence of and names/alias for these fields may also differ between the attribute table and pop-ups. Additional details can be found by following the publication links in the pop-up for each footprint, or in the layer's service description (https://services.arcgis.com/v01gqwM5QqNysAAi/arcgis/rest/services/Bathymetry_Footprints/FeatureServer). (Source: USGS SPCMSC)
    fan
    Acronym for 'Field Activity Number', which is a unique identifier given to data collected during USGS SPCMSC field activities. (Source: USGS SPCMSC) Each FAN is a unique number given to data collected during a field activity. There are two common formats used for a FAN. The first is: ##XXX##. The first two digits represent the year the data were collected. The third through fifth digits represent the project identification information, coded by the USGS to be unique to each project. The last two digits represent the number of field activities in that year under that project code. The second format for a FAN is: ####_###_FA. The first four digits represent the year the data were collected and the second, 3-digit set represents numbers assigned to a specific USGS center (for example, USGS SPCMSC numbers begin at 301). This field is not present within the pop-up.
    fan_url
    Link to the FAN webpage on the USGS Coastal and Marine Geoscience Data System (CMGDS). (Source: USGS SPCMSC) The CMGDS FAN page associated with the dataset (https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-333-FA). If multiple FANs are present, the general CMGDS search URL is used (https://cmgds.marine.usgs.gov/data_search.php). Users are advised to use the search using each FAN listed to view its associated page.
    pub
    Represents the source publication that the dataset is derived from. (Source: USGS SPCMSC) Data were published in USGS Data Series (DS), data releases (DR), or Open-File Reports (OFR), and serve as unique identifiers to find and access the data. This field is not present within the pop-up.
    pub_url
    Online linkage to the USGS publication used for the source datasets. (Source: USGS SPCMSC) All links navigate to a publication (DS, DR, or OFR) in the USGS Publications Warehouse or USGS Trusted Digital Repository.
    geotiff
    The name of the associated bathymetric DEM in the center's internal file geodatabase. (Source: USGS SPCMSC) The name of the associated bathymetric DEM in the center's internal file geodatabase. This field is not present within the pop-up.
    type
    Type of bathymetric data collected. If multiple types were used during surveying, they are separated by comma (example: Singlebeam, Swath). (Source: USGS SPCMSC)
    ValueDefinition
    SinglebeamSinglebeam is a type of sonar system used to map the seafloor. Singlebeam uses one transducer/sonar beam to map the seafloor.
    MultibeamMultibeam is a type of sonar system used to map the seafloor. The sonar sends out multiple, simultaneous sonar beams at once in a fan-shaped pattern.
    SwathSwath is a type of sonar system used to map slope, hillshaded relief, and rugosity (the roughness and smoothness) of the sea floor.
    resolution
    The resolution of the collected bathymetric data. (Source: USGS SPCMSC) The resolution, in meters (example: 10 meters). Left blank if unknown.
    yr_collect
    The year the bathymetric survey was conducted. (Source: USGS SPCMSC) The year (in YYYY format) the bathymetric survey was conducted. If the survey spanned multiple years, the year is separated by a hyphen (example: 1995-1999).
    All Lidar Footprints
    Attribute table for the hosted feature layer of the footprints (study area) of all lidar datasets from the USGS SPCMSC since 2001. In the web mapping application, the layer displays all footprints merged into one layer (All Lidar Footprints). Individual footprints are available in Williams and others (2019). Data is symbolized in a dark purple (newest) to a lighter purple (oldest) color ramp. The presence of and names/alias for these fields may also differ between the attribute table and pop-ups. Additional details can be found by following the publication links in the pop-up for each footprint, or in the layer's service description (https://services.arcgis.com/v01gqwM5QqNysAAi/ArcGIS/rest/services/Lidar_Footprints/FeatureServer). (Source: USGS SPCMSC)
    fan
    Acronym for 'Field Activity Number', which is a unique identifier given to data collected during field activities. (Source: USGS SPCMSC) Each FAN is a unique number given to data collected during a field activity. There are two common formats used for a FAN. The first is: ##XXX##. The first two digits represent the year the data were collected. The third through fifth digits represent the project identification information, coded by the USGS to be unique to each project. The last two digits represent the number of field activities in that year under that project code. The second format for a FAN is: ####_###_FA. The first four digits represent the year the data were collected and the second, 3-digit set represents numbers assigned to a specific USGS center (for example, USGS SPCMSC numbers begin at 301). This field is not present within the pop-up.
    fan_url
    Link to the FAN webpage on the USGS Coastal and Marine Geoscience Data System (CMGDS). (Source: USGS SPCMSC) The CMGDS FAN page associated with the dataset (https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-333-FA). If multiple FANs are present, the general CMGDS search URL is used (https://cmgds.marine.usgs.gov/data_search.php). Users are advised to use the search using each FAN listed to view its associated page.
    pub
    Represents the source publication that the dataset is derived from. (Source: USGS SPCMSC) Data were published in USGS Data Series (DS), data releases (DR), or Open-File Reports (OFR), and serve as unique identifiers to find and access the data. This field is not present within the pop-up.
    pub_url
    Online linkage to the USGS publication used for the source datasets. (Source: USGS SPCMSC) All links navigate to a publication (DS, DR, or OFR) in the USGS Publications Warehouse or a USGS Trusted Digital Repository.
    returntype
    Describes the type of lidar represented in the footprint. (Source: USGS SPCMSC) There are four lidar types used to generate the DEMs covered by the footprints: bare-earth, first-surface, ground-based, and submerged. Some datasets contain one or multiple types, which are sequentially listed in the attribute table, separated by commas. Bare earth is digital elevation data of the terrain; free from vegetation, buildings, and other man-made structures. First surface is the first significant measurable portion of a return lidar pulse, includes vegetation, buildings, and other manmade structures. Ground-based lidar refers to terrestrial lidar data acquisition. Submerged refers to lidar-derived topography for submerged environments.
    yr_collect
    Calendar year of the lidar data collection. (Source: USGS SPCMSC) This field indicates the year the lidar data were collected for each footprint.
    Entity_and_Attribute_Overview:
    Sidescan Sonar - The U.S. Geological Survey, with collaboration from other agencies and partners, have conducted geophysical surveys to investigate the geologic controls on barrier islands and other coastal zone features. These tile layers are published sidescan sonar data from the USGS SPCMSC. The sidescan sonar data was processed to create Georeferenced Backscatter Rasters (GeoBars). The mosaic images represent 1-meter pixel composites of these GeoBars, with each individual image shown at a single-scaled intensity. Mosaics are labeled using their USGS Field Activity Number (FAN) and associated publication.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information were generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.
    Entity_and_Attribute_Overview:
    SPCMSC Geologic Core and Sample Database (Coral Samples, Coral Cores, Coral Reef Cores, Limestone Cores, Sediment Samples, Sediment Cores) - information on geologic cores and samples collected, analyzed, published, and/or archived by, or in collaboration with, the USGS SPCMSC. This database captures metadata about samples throughout the USGS Science Data Lifecycle: including field collection, laboratory analysis, publication of research, and archival or deaccession. The SPCMSC Geologic Core and Sample Database also includes storage locations for physical samples and cores archived in a repository (USGS SPCMSC or elsewhere, if known). The majority of the samples and cores in this database come from field activities associated with the SPCMSC and have been assigned a field activity number (FAN) in the field activity management and data inventory tool for USGS Coastal and Marine Hazards and Resources Program (CMHRP) Coastal and Marine Geoscience Data System (CMGDS), https://cmgds.marine.usgs.gov/.Additional details can be found by following the publication links in the pop-up for each sample, or by selecting the layer's item details in the legend of the web mapping application. The SPCMSC geologic core and sample database is available in its own standalone web application, https://doi.org/10.5066/F7319TR3. To view the complete list of entity and attribute definitions for this feature layer, please refer to its associated metadata https://data.usgs.gov/datacatalog/metadata/USGS.e51b16f7-3c8c-48e0-8f95-8533934535b8.xml.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information were generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Breanna N. Williams
    • Heather A. Schreppel
    • Steven H. Douglas
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Attn: USGS SPCMSC Data Management Group
    Data Management
    600 4th Street South
    St. Petersburg, Florida
    USA

    727-502-8000 (voice)

Why was the data set created?

To provide an inventory of frequently collected and updated geoscientific data published by USGS SPCMSC.

How was the data set created?

  1. From what previous works were the data drawn?
    Lidar footprints (source 1 of 2)
    Williams, Breanna N., Schreppel, Heather A., and Stalk, Chelsea A., 20191220, Footprints of Lidar Datasets Published at the U.S. Geological Survey St. Petersburg Coastal and Marine Science Center Since 2001: U.S. Geological Survey data release doi:10.5066/P9B616C5.

    Online Links:

    Type_of_Source_Media: vector digital data
    Source_Contribution:
    Data coverage footprints that show the extent of lidar data collected and published by the USGS SPCMSC, since 2001.
    SPCMSC Geologic Core and Sample Database (source 2 of 2)
    Williams, Breanna N., Schreppel, Heather A., Reich, Christopher D., Smith, Kathryn E.L., Tiling-Range, Ginger, Stalk, Chelsea A., Douglas, Steven H., Dadisman, Shawn V., Flocks, James G., Toth, Lauren T., and Stathakopoulos, Anastasios, 20130725, St. Petersburg Coastal and Marine Science Center's Geologic Core and Sample Database.

    Online Links:

    Type_of_Source_Media: application/service, tabular digital data
    Source_Contribution:
    Database containing a comprehensive inventory of geologic (coral, coral reef, limestone, and sediment) cores and samples collected, analyzed, published, and/or archived by, or in collaboration with, the USGS SPCMSC.
  2. How were the data generated, processed, and modified?
    Date: 2022 (process 1 of 6)
    Archiving published data in an enterprise geodatabase (original methodology): The SPCMSC Geoscience Data Viewer web mapping application contains geoscientific data including raster layers (bathymetry DEMs [no longer available in the web application as of August 2025] and sidescan sonar), and vector layers (bathymetry footprints, lidar footprints, seismic data extents, seismic survey tracklines, and geologic cores and samples). Bathymetric DEMs are archived internally but are no longer shared as tile layers in ArcGIS Online due to storage and credit limitations at the Bureau. All layers in the application are first published through USGS approved publication methods for data (i.e., USGS Series or USGS data release) by, or in collaboration with, the USGS SPCMSC. The bathymetry (footprints and DEM [internal access only]), lidar footprints, seismic (data extents and tracklines), and sidescan sonar raster mosaics were originally published as an ArcGIS representational state transfer (REST) map service using an ArcGIS server as part of an installation of ArcGIS Enterprise 10.6. For the previous publishing methodology of the SPCMSC Geologic Core and Samples Database, refer to its associated metadata, https://data.usgs.gov/datacatalog/metadata/USGS.e51b16f7-3c8c-48e0-8f95-8533934535b8.xml. The remaining recently published data types (mentioned above) were added to the web mapping application via a REST map service on a frequent, as-needed basis. Aside from the geologic cores and samples, the geoscientific dataset was first imported into the enterprise geodatabase shortly after publication using ArcCatalog (10.5 through 10.8, depending on the date of publication). The raster data (bathymetry DEMs [internal] and sidescan sonar) were imported as mosaic raster datasets into the geodatabase. To import the raster data, the datum was defined or reprojected (if not in WGS84) to ensure it is in WGS84 (Universal Transverse Mercator [UTM] Zone X; bathymetry DEMs only), and the statistics were calculated for each dataset within the geodatabase. The vector data (footprints and data extent) were imported into the geodatabase as a feature class. If the native coordinate system was not WGS84, the datasets were reprojected to WGS84, using the Reproject (Data Management) tool. The footprints (bathymetry and lidar) were generated from the source publication's raster dataset (DEM, LAS or XYZ file) within Global Mapper (versions 18.2 to 22.1) by generating a geographic tagged image file format (GeoTIFF) (see Williams and others, 2019). Once generated, the following steps were performed: Layer > "BBOX/Coverages" > "NO - Create Polygonal Coverage Areas" (for footprints), or "YES – Create Rectangular Areas" (for bounding boxes) to generate a footprint or bounding box shapefile. These shapefiles were imported into the geodatabase as a vector feature class. Within ArcMap (10.5 through 10.8, depending on the date of processing), the attribute tables were populated and modified using various models and tools (i.e., Add/Delete Field, Field Calculator). Please see the Entity and Attribute section of this metadata record for the fields that were created and populated. This process was repeated as more geoscientific datasets were published and imported into the center's enterprise geodatabase. The methods described in this process step were changed in 2023. Please refer to subsequent process steps below for more information. Data sources produced in this process:
    • enterprise geodatabase
    Date: 2022 (process 2 of 6)
    Creating the map document and (re)publishing a map service (original methodology): In ArcMap (10.5 through 10.8, depending on the date of the creation), an individual map document (.mxd) was created for each data type (bathymetry footprints, lidar footprints, bathymetry DEMs [now internal only], seismic tracklines, seismic data extents, and sidescan sonar). The feature class or raster layers were manually added to the associated map document, using the center's enterprise geodatabase as the data source. The feature class data were grouped and symbolized – please see the Entity and Attribute section of this metadata record for more information. Then, each map document was published as a REST map service and Open Geospatial Consortium (OGC) web mapping service (WMS), using ArcGIS server as part of an installation of ArcGIS Enterprise 10.6 on an on-premises server at the USGS SPCMSC. This process was repeated as more geoscientific datasets were published and archived onto the center's enterprise geodatabase. Once republished, the web map and associated web mapping application automatically updated. See the next Process Step for more information. The methods described in this process were changed to ArcGIS Pro and hosted feature layers in 2023. Please refer to subsequent process steps below for more information. Data sources used in this process:
    • enterprise geodatabase
    Data sources produced in this process:
    • ArcMap document (.mxd)
    • Bathymetry_DEMs
    • Bathymetry_Footprints
    • Seismic_Data_Extents
    • Seismic_Survey_Tracklines
    • Sidescan_Sonar
    • lidar_footprints
    • SPCMSC Geologic Core and Sample Database
    Date: 2022 (process 3 of 6)
    Creating a web map and web mapping application (original methodology): After each map service was published (or re-published, as new datasets were published and archived), the map services were added and saved to a blank web map in ArcGIS Online via the REST service URL. The SPCMSC Geologic Core and Sample Database was also added to the web map (classic). Basemaps (World Imagery and Hybrid Reference Layer) were added to the web map to enhance data visualization. Pop-ups were configured for each feature layer, that presented the most pertinent information from the attribute table when the layer was selected in the map. Certain pop-ups were manually edited again once the service was republished. Next, the SPCMSC Geoscience Data Viewer web mapping application was developed using Esri's ArcGIS Online Web AppBuilder. The web map was added to the application and various widgets were added to the application for enhanced functionality. The web map and associated web mapping application automatically updated when the REST map services were republished. The methods described in this process were changed to hosted feature layers and an ArcGIS Online Instant App in 2023. Please refer to subsequent process steps below for more information. Data sources used in this process:
    • Bathymetry_DEMs
    • Bathymetry_Footprints
    • Seismic_Data_Extents
    • Seismic_Survey_Tracklines
    • Sidescan_Sonar
    • lidar_footprints
    Data sources produced in this process:
    • Geoscience Data Viewer Web Map (classic)
    • SPCMSC Geoscience Data Viewer Web Mapping Application (Web AppBuilder)
    Date: 2025 (process 4 of 6)
    Archiving published data in file geodatabases (current methodology): Due the retirement of ArcMap and Catalog in 2023, all of SPCMSC's published geoscience datasets were migrated from the enterprise geodatabase to file geodatabases accessible through the center's on-premise server. The bathymetry (footprints and DEMs [internal]), lidar footprints, seismic (data extents and tracklines), and sidescan sonar raster mosaics are regularly imported to the center’s file geodatabases to serve as an archive. The methods for transforming and adding vector and raster data to file geodatabases does not significantly differ from the original methodology used for the enterprise geodatabases. The raster data (bathymetry DEMs [internal only] and sidescan sonar) are imported as mosaic raster datasets into a file geodatabase. To import the raster data, the datum is defined or reprojected (if not in WGS84) to ensure it is in WGS84 (UTM Zone X; bathymetry DEMs only), and the statistics are calculated for each dataset within the geodatabase. The vector data (footprints and data extent) are imported into another file geodatabase as feature classes. If the native coordinate system is not WGS84, the datasets are reprojected to WGS84, using the Reproject (Data Management) tool. The footprints (bathymetry and lidar) are generated from the source publication's dataset (DEM, LAS or XYZ file) within Global Mapper (version 22.1 or newer) by generating a GeoTIFF (see Williams and others, 2019). Once generated, the following steps are performed: Layer > "BBOX/Coverages" > "NO - Create Polygonal Coverage Areas" (for footprints), or "YES – Create Rectangular Areas" (for bounding boxes) to generate a footprint or bounding box shapefile. These shapefiles are then imported into the file geodatabase as a vector feature class. Within ArcGIS Pro (2.8 or newer, depending on the date of import), the attribute tables are populated and modified using models and geoprocessing tools (i.e., Add/Delete Field, Field Calculator). Please see the Entity and Attribute section of this metadata record for details about the fields that are created and populated. This process is repeated as more geoscientific datasets are published and imported into the center's file geodatabases. Data sources used in this process:
    • enterprise geodatabases
    Data sources produced in this process:
    • SPCMSCVector.gdb
    • SPCMSCRaster.gdb
    Date: 2025 (process 5 of 6)
    Creating the ArcGIS project files, configuring pop-ups, and (re)publishing the hosted feature and tile layers (current methodology): In ArcGIS Pro (2.8 or newer, depending on the date of the creation), individual ArcGIS project files (.aprx) have been created for each data type (bathymetry footprints, lidar footprints, seismic tracklines, seismic data extents, and sidescan sonar). The feature class or raster layers are manually added to the associated project file, using the center's file geodatabase as the data source. The feature class data are grouped and symbolized within the ArcGIS Pro project files – please see the Entity and Attribute section of this metadata record for more information. In each ArcGIS project file, the pop-ups (vector data only) are configured. A pop-up configuration file for each data type was created (via 'Configure pop-ups' in ArcGIS Pro) by setting the desired pop-up information (previously determined within the original publication methodology for pop-ups). Once a pop-up was generated for a given data type, the configuration was saved: Configure pop-ups > Save pop-up configuration. The pop-up configuration file (.pop) for each vector dataset (bathymetry footprints, lidar footprints, seismic tracklines, and seismic data extents) was saved to the center server for later use. Now, any new data in future updates has the pop-up added via: Configure pop-ups > Load pop-up configuration. The pop-up configuration file (.pop) is selected for the data type and is imported to each feature class within the project file. After pop-ups are configured, and the data grouped and symbolized accordingly (based on the original methodology), they are published to ArcGIS Online within ArcGIS Pro using the ArcGIS project file. For the first-time publication of these data, they were published via: Sharing > Share As Web Layer. This created a new hosted feature layer (or tile layer for raster data) for each of these geoscientific datasets. Note: the hosted feature and tile layers are shared with additional parameters for visibility range (states—town for tile layers; world—city for feature layers) to minimize credit usage and optimize data rendering in the web map and application. Therefore, these layers are not visible across all scales (zoom levels) in a map. Users will need to zoom in/out within the given scale to view these data. The re-publication process is regularly repeated as more geoscientific datasets are published and archived into the center's file geodatabases. Re-publishing data from ArcGIS Pro to ArcGIS Online involves updating the project files within ArcGIS Pro by: Sharing > Overwrite Web Layer. This will overwrite the existing hosted feature layer within ArcGIS Online. The sidescan tile layers are not typically overwritten as they are published as separate, new tile layers for each dataset. Re-publishing results in brief downtime of the public access for these data, as the center must request the item is reshared with the public by the USGS geographic information system (GIS) administrators. Data sources used in this process:
    • SPCMSCVector.gdb
    • SPCMSCRaster.gdb
    Data sources produced in this process:
    • ArcGIS project files (.aprx)
    • Pop-up configuration files (.pop)
    • Bathymetry Footprints hosted feature layer
    • Lidar Footprints hosted feature layer
    • Seismic Data Extents hosted feature layer
    • Seismic Tracklines hosted feature layer
    • Sidescan hosted tile layers
    Date: 2022 (process 6 of 6)
    Web map and web mapping application creation and configuration (current methodology): After the hosted feature layers (including the SPCMSC Geologic Core and Sample Database) and sidescan tile layers were initially published via the current methodology, the layers were added and saved to a new blank web map in ArcGIS Online. The previously used web map was in the 'Map Viewer Classic' format, which is now deprecated and should not be used for newer ArcGIS Online web applications. The primary basemap (World Imagery) was also added to the web map to enhance data visualization. Some additional re-grouping of the data within ArcGIS online is required to organize the hosted feature layer data (bathymetry footprints, lidar footprints, and seismic tracklines) by year and/or type within the web map. This is completed each time the feature layers are republished. Next, a new SPCMSC Geoscience Data Viewer web mapping application was developed using Esri's ArcGIS Instant Apps (Sidebar template) due to the deprecation of the Web AppBuilder. The web map was added to the application. Users should be aware the application may take additional time to load the data layers. Person who carried out this activity:
    Breanna N. Williams
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Geographer
    600 4th Street South
    St. Petersburg, FL
    United States

    727-502-8027 (voice)
    bnwilliams@usgs.gov
    Data sources used in this process:
    • Bathymetry Footprints hosted feature layer
    • Lidar Footprints hosted feature layer
    • Seismic Data Extents hosted feature layer
    • Seismic Tracklines hosted feature layer
    • Sidescan hosted tile layers
    • SPCMSC Geologic Core and Sample Database
    Data sources produced in this process:
    • Geoscience Data Viewer Web Map (new)
    • SPCMSC Geoscience Data Viewer Web Application (Instant App)
  3. What similar or related data should the user be aware of?
    Williams, Breanna N., and Schreppel, Heather A., 20220916, The USGS SPCMSC Geologic Core and Sample Database: Esri, ArcGIS Online.

    Online Links:

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 information is dependent on individual surveys and availability of information on historic data collection procedures. The error for location coordinates may range considerably, dependent on the date of collection, data collection methods, and available metadata. Users are advised to refer to the source publication and metadata for more information.
  2. How accurate are the geographic locations?
    The validity or accuracy of information on the horizontal positions are dependent on individual surveys and the availability of information regarding historic data collection procedures. Users are advised to refer to the source publication and metadata for more information.
  3. How accurate are the heights or depths?
    The validity or accuracy of information on the vertical positions are dependent on individual surveys and the availability of information regarding historic data collection procedures. Users are advised to refer to the source publication and metadata for more information.
  4. Where are the gaps in the data? What is missing?
    The datasets included in this web mapping application are considered complete for the information presented, as described in the abstract. New datasets are added to the application as they become published. Users are advised to refer to the source publication metadata for more information.
  5. How consistent are the relationships among the observations, including topology?
    These datasets are from multiple field sampling activities and multiple publications. Therefore, no fidelity checks were conducted. Users are advised to refer to the source publication metadata for more information.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints. Please see 'Distribution Information' for details.
Use_Constraints These data are marked with a Creative Commons CC0 1.0 Universal License, unless otherwise stated in their source publication. These data are in the public domain and do not have any use constraints. Users are advised to read the dataset's source metadata thoroughly to understand appropriate use and data limitations.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    Attn: USGS SPCMSC Data Management
    600 4th Street South
    Saint Petersburg, FL
    United States

    727-502-8000 (voice)
    gs-g-spcmsc_data_inquiries@usgs.gov
  2. What's the catalog number I need to order this data set? SPCMSC Geologic Core and Sample Database feature layer (hosted), Seismic Data Extents feature layer (hosted), Seismic Survey Tracklines feature layer (hosted), Bathymetry Footprints feature layer (hosted), Lidar Footprints feature layer (hosted), and Sidescan Sonar tile layers (06FSH01_DS291, 2010_012_FA_OFR2010_1178, 10CCT03_DS671, 10CCT02_OFR2010_1178, 10CCT02_DS577, 10CCT01_DS563, 10BIM04_DS739, 13CCT04_DS917, 14BIM05_DS1005, 2015_315_FA_DRP9374DKQ, 2016_342_FA_DRF7833Q8J_Coastal_Explorer)
  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 for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 05-Sep-2025
Metadata author:
U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
Attn: USGS SPCMSC Data Management
600 4th Street South
Saint Petersburg, FL
United States

727-502-8000 (voice)
gs-g-spcmsc_data_inquiries@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/SPCMSC_geoscience_data_viewer_metadata.faq.html>
Generated by mp version 2.9.51 on Fri Sep 5 10:11:24 2025