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

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.

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.

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.

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.

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.

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.