Geologic Sea-Floor Mapping: Marine Data Model Case Study

1. Geologic Sea-Floor Mapping: Marine Data Model Case Study Brian Andrews-USGS, Woods Hole, MA Seth Ackerman-CZM, Woods Hole, MA

2. Presentation Overview • Project Overview & Goals • Data Types • Data Model Methods • Current Status • Future Research

3. Project Overview • USGS/CZM Cooperative • 1 of 3 areas (Boston, South Essex, & Cape Ann) • Regional geologic sea-floor mapping • Characterize the surface and subsurface sea floor

5. South Essex Survey Area • Survey area = 123 km2 • Survey lines = 970 km • Lane spacing = 100m • Depth range = 0-55m

6. Data Types • Geophysical Data • Interferometric-sonar bathymetry (swath) • Interferometric-sonar backscatter (swath) • Sidescan-sonar backscatter • Seismic-reflection profile • RTK/DGPS Navigation (x,y,z) • Ground Validation • Bottom photography (still & video) • Sediment samples (grain size)

7. Process Phase Swath Bathymetry Raster Depth Backscatter Sidescan-Sonar Raster Backscatter Mosaic Seismic Profile Vector Depth to reflector (x,y,z1,z2,z3..) Sediment Samples Vector (x,y,z-grainsize) Bottom Video/Stills Vector (x,y) Preliminary Analysis Phase Raster (2,5,10m) Hillshade Slope Roughness Backscatter Vector Contours Raster (< 1m) Reclassified image Raster (25+m) Interpolated Surface Profiles (jpgs) Raster (25+m) Interpolated Surface (Grain Size) Ground Validation Mpeg /station Bottom stills Modeling Phase Reclassified Raster Based on Slope Roughness Backscatter How is subsurface stratigraphy related to seafloor morphology? ? ? ? ArcGIS 9.0 Data Flow B.D. Andrews, USGS,28 June 04

8. Existing MDM

9. ESRI Classes:: Feature +Shape : esriFieldTypeGeometry MarineFeature -MarineID : DomainIDField -MarineCode : esriFieldTypeString -CruiseID : esriFieldTypeInteger MarinePoint MarineLine MarineArea Points Lines Areas SurveyLine {GeometryType = esriGeometryPolyline, TimeDurationLine FeatureLine FeaturePoint HasM = True, {GeometryType = esriGeometryPolyline, {GeometryType = esriGeometryPolyline, HasZ = True} HasM = True, HasM = True} HasZ = True} -SurveyID : esriFieldTypeInteger -DataLineType : esriFieldTypeString -StartDate : esriFieldTypeDate FeatureArea -LineID : esriFieldTypeString -EndDate : esriFieldTypeDate -Survey : esriFieldTypeString -VehicleID : esriFieldTypeInteger {GeometryType = esriGeometryPolygon} MeasurementPoint -LineJDay : esriFieldTypeInteger -BoundaryType : esriFieldTypeString LocationSeriesPoint -LineStart : esriFieldTypeString Shoreline {GeometryType = esriGeometryPoint} -LineEnd : esriFieldTypeString -Area : esriFieldTypeSingle {GeometryType = esriGeometryPolyline, -LineLength : esriFieldTypeSingle HasM = True} -RecordedTime : esriFieldTypeDate -BoundaryDesc : esriFieldTypeString -MDeviceID : esriFieldTypeInteger -SeriesID : esriFieldTypeInteger -VDatum : esriFieldTypeDouble -BoundaryName : esriFieldTypeString -mpgLink : string -ShorelineType : esriFieldTypeString SurveyPoint {GeometryType = esriGeometryPoint, Run InstantaneousPoint HasZ = True} {GeometryType = esriGeometryPolyline, TimeSeriesPoint {GeometyType = esriGeometryPoint} -ZValue : esriFieldTypeDouble {GeometryType = esriGeometryPoint} -PointTime : esriFieldTypeString -RecordedTime : esriFieldTypeDate -MarineID : esriFieldTypeInteger -SurveyID : esriFieldTypeInteger -RunID : DomainIDField -RunName : esriFieldTypeString -RunMethod : esriFieldTypeString -Description : esriFieldTypeString -LocationDescription : esriFieldTypeString 1 1 1 HasM = True, HasZ = True} * Marine Objects:: Cruise -CruiseID : esriFieldTypeInteger -CruiseName : esriFieldTypeString 1 -CruiseType : esriFieldTypeString InstantPointHasMeasurements -ShipName : esriFieldTypeString -Description : esriFieldTypeString -CruiseStatus : esriFieldTypeString * * * * LineHasSurveys VesselHasMeasureDevice Measurements:: Measurement * 1 1 SVInfoHasMDevice 1 * -FeatureID : esriFieldTypeInteger -PointTime : esriFieldTypeDate * Tables Marine Objects:: VesselInfo -PointX : esriFieldTypeDouble 1 * Marine Objects:: SurveyInfo -PointY : esriFieldTypeDouble -VesselID : esriFieldTypeInteger -SurveyID : esriFieldTypeInteger -PointZ : esriFieldTypeDouble -VesselName : esriFieldTypeString Measurements:: MeasuringDevice -StartDate : esriFieldTypeDate -JDay : esriFieldTypeInteger -VesselDesc : esriFieldTypeString -EndDate : esriFieldTypeDate -date : esriFieldTypeDate -MDeviceID : esriFieldTypeInteger -SurveyDesc : esriFieldTypeString -Station : esriFieldTypeInteger -MDeviceName : esriFieldTypeString -MDeviceID : esriFieldTypeInteger -MeasureID : esriFieldTypeInteger -MDeviceDesc : esriFieldTypeString -SurveyCode : esriFieldTypeString -MDeviceID : esriFieldTypeInteger -VesselID : esriFieldTypeInteger -ImageLink : esriFieldTypeString -MDeviceLabel : esriFieldTypeString -date_time : esriFieldTypeDate ESRI Classes:: Object 1 +OBJECTID : esriFieldTypeOID USGS MDM

10. USGSMarine Data Model

11. Marine Data Model

12. Geodatabase Raster Catalog Measurement Table Survey Tracklines (4 data types) Relationship Class Marine Data Model

15. USGS MDM Status/Lessons Learned • Just do it • Data management of ground validation points • Useful for topological update (feature class) • Annotation classes • Simplify USGS Open File Report process.

16. Future Research • How can the relationship class help us with spatial relationships? • How do we extract the high-res data from rasters? • Interpolation of seismic profile data in Geostatistical Analyst • How do we manage geologic interpretations in MDM? • Talk to the Geology Data Model Crew • Publish USGS Open File Report Spring 2005

17. A B D C

18. Brian Andrews bandrews@usgs.gov • Seth Ackerman seth.ackerman@state.ma.us