Raw Data for All Survey:

SBES:
1. SBES (Single Beam Echo Sounder):
• Raw Data:
o Depth measurements: Single point depth readings at regular intervals
along the survey line.
o Time stamps: When each depth measurement was taken.
o Position coordinates (latitude and longitude): This would be from a
DGPS system, providing georeferenced depth data.
o Raw acoustic signals: The initial sound waves sent and received by the
device (may be processed into depth data later).
Format:
• Typically, this would be in a text file (CSV or similar) containing columns like
Timestamp, Latitude, Longitude, Depth, and Heading.

2. MBES (Multibeam Echo Sounder):

• Raw Data:
o Multibeam depth measurements: High-resolution depth data along
multiple beams (often between 30 to 256 beams).
o Backscatter intensity: A measure of the reflectivity of the seafloor at
each beam.
o Position and heading data: Coordinates, roll, pitch, and yaw of the
vessel to correct for motion and ensure accurate readings.
o Time stamps: When each set of data was collected.
o Beam angle and distance: Information on the angle and distance for
each individual beam’s measurement.
o Sound velocity profile: Temperature, salinity, and pressure data, often
used to adjust depth measurements.
Format:
 • Often stored in XYZ or CSV format with the columns containing Latitude,
Longitude, Depth (per beam), Backscatter, Heading, and Time.

3. SSS (Side Scan Sonar):

• Raw Data:
o Sonar backscatter data: Raw acoustic signals returned from the seabed,
showing intensity variations.
o Distance to the seafloor: Measured from the sonar transducer,
providing an idea of the shape and texture of the seafloor.
o Side scan imagery: Images of the seafloor showing the locations of
objects (e.g., cables, wrecks, or other features).
o Position data: From DGPS, ensuring the images are accurately
georeferenced.
o Time stamps: When each image or backscatter data point was collected.
o Slant range data: The distance between the sensor and the seafloor,
adjusted for the angle of the sonar.
Format:
• Image files (e.g., TIFF, JPEG) for the sonar imagery.
• Text files (CSV or similar) for raw sonar intensity readings, which may include
fields such as Latitude, Longitude, Intensity, and Time.

4. SBP (Sub-bottom Profiling):

• Raw Data:
o Echo sounder signals: Raw acoustic signals reflected off different layers
beneath the seafloor.
o Layer data: Information about sediment layers or horizons detected,
including their depth and acoustic impedance.
o Signal travel time: Time it takes for the acoustic signal to travel to the
seabed and back.
o Position coordinates: DGPS position of the vessel or system during
profiling.
o Time stamps: For each sub-bottom profile reading.
Format:

• Typically stored in binary or CSV formats that include data such as Depth,
Layer Number, Travel Time, Latitude, Longitude, and Time.

5. MAGGY (Magnetometer):
• Raw Data:
o Magnetic field measurements: The strength and direction of the
magnetic field at each data point, typically recorded in nanotesla (nT).
o Position coordinates: DGPS data to associate each magnetic reading
with a geographical location.
o Time stamps: When each magnetic reading was taken.
o Height above the seabed: The height at which the magnetometer was
flown or deployed (e.g., 9 meters above the seabed).
Format:

• Text files (e.g., CSV) that contain columns such as Latitude, Longitude,
Magnetic Field Strength (nT), Height Above Seabed, and Time.

6. GS (Grab Sampling):
GS stands for Grab Sampling, which refers to the collection of sediment or soil
samples from the seabed using a grab sampler. This method is used to collect physical
samples of the seafloor for further analysis, such as identifying sediment types,
contaminants, or other geological properties.
• Raw Data for GS (Grab Sampling):
o Sample location: GPS coordinates (latitude and longitude) where the
grab sample was taken.
o Sample depth: The depth at which the sample was collected.
o Sample description: A brief description of the sediment or material
collected, including its type, texture, and appearance.
o Time stamps: When each sample was collected.
o Sample ID: An identifier for each sample collected during the survey.
o
Format:
• Typically, this data would be stored in a CSV or Excel file with columns such as
Timestamp, Latitude, Longitude, Sample ID, Sample Description, Depth, and
Time.

Example of Raw Data Format for Each

Equipment:
1. SBES Example (CSV format):

Timestamp, Latitude, Longitude, Depth (m), Heading

2025-03-06T10:00:00, 26.2020, 50.5820, 5.2, 120

2025-03-06T10:00:30, 26.2025, 50.5825, 5.3, 122

2. MBES Example (CSV format):

Timestamp, Latitude, Longitude, Beam1_Depth, Beam2_Depth, ..., BeamN_Depth,

Backscatter, Heading

2025-03-06T10:00:00, 26.2020, 50.5820, 4.8, 4.9, ..., 5.0, 120

3. SSS Example (CSV format):

Timestamp, Latitude, Longitude, Intensity, Slant Range, Backscatter (Image)

2025-03-06T10:00:00, 26.2020, 50.5820, 200, 15.2, image1.tiff

4. SBP Example (CSV format):

Timestamp, Latitude, Longitude, Layer, Depth to Layer (m), Travel Time (ms)

2025-03-06T10:00:00, 26.2020, 50.5820, 1, 4.2, 20

5. MAGGY Example (CSV format):

Timestamp, Latitude, Longitude, Magnetic Field (nT), Height Above Seabed (m)
2025-03-06T10:00:00, 26.2020, 50.5820, 520, 9

6. Grab Sampling Data:

Timestamp, Latitude, Longitude, Sample ID, Sample Description, Depth (m)

2025-03-06T10:00:00, 26.2020, 50.5820, GS001, Sandy clay, 5.2

2025-03-06T10:15:00, 26.2025, 50.5825, GS002, Gravel with shells, 4.9

Example of Raw Data to GeoTIFF Conversion:

7. Side Scan Sonar to GeoTIFF:
o Raw sonar backscatter data would look like this in a CSV format:

Timestamp, Latitude, Longitude, Slant Range (m), Intensity

2025-03-06T10:00:00, 26.2020, 50.5820, 15.2, 200

2025-03-06T10:10:00, 26.2025, 50.5825, 14.8, 180

o After processing and georeferencing, this data would be used to create a

side scan sonar mosaic. The output would be a GeoTIFF that can be
viewed in a GIS system, with each pixel representing sonar backscatter
intensity at a specific geographic location.

8. Bathymetric Data (MBES) to GeoTIFF:

o Raw MBES depth data might look like this:

Timestamp, Latitude, Longitude, Depth (m)

2025-03-06T10:00:00, 26.2020, 50.5820, 5.2

2025-03-06T10:10:00, 26.2025, 50.5825, 5.1

o After processing, a bathymetric map is created, and the resulting depth

map is exported to a GeoTIFF showing the entire survey corridor with
depth information.
 9. Example of GeoTIFF Metadata:
A GeoTIFF file will include metadata such as:
• Coordinate Reference System (CRS): The coordinate system used (e.g.,
WGS84).
• Bounding Coordinates: The latitude and longitude range of the survey area.
• Pixel Resolution: The spatial resolution of the image (e.g., 1 meter per pixel).
• Depth Ranges (for bathymetric data) or Backscatter Intensity (for sonar data).
• Time Information: Time of data capture or processing.

10. Bathymetric data in XYZ format

is a commonly used format for storing depth data, where each data point consists of
three values: X (longitude), Y (latitude), and Z (depth). When you specify a 1-meter
interval, it means that the bathymetric data is being recorded at 1-meter intervals along
the survey route.
This type of data is often collected using Multibeam Echo Sounder (MBES) or Single
Beam Echo Sounder (SBES) systems, where each measurement represents the depth
of the seafloor at a given geographic point.

11. Explanation of XYZ Format:

• X (Longitude): The geographical longitude coordinate of the measurement.
• Y (Latitude): The geographical latitude coordinate of the measurement.
• Z (Depth): The depth of the seafloor at that specific latitude and longitude,
typically in meters (m).

12. Example of Bathymetric Data in XYZ Format at 1-meter Interval:

Here's an example of how bathymetric data collected at a 1-meter interval would look
in XYZ format:

Longitude, Latitude, Depth (m)

50.5820, 26.2020, 5.1

50.5821, 26.2021, 5.2

50.5822, 26.2022, 5.3

50.5823, 26.2023, 5.4

50.5824, 26.2024, 5.5

50.5825, 26.2025, 5.6

50.5826, 26.2026, 5.7

...
Key Points:
• Longitude (X): The first value (50.5820, 50.5821, etc.) represents the longitude.
• Latitude (Y): The second value (26.2020, 26.2021, etc.) represents the latitude.
• Depth (Z): The third value (5.1, 5.2, etc.) represents the depth at each
coordinate.
The 1-meter interval suggests that the data points are being recorded at every meter
along the survey path, though actual data collection intervals may vary depending on
the survey equipment used.

13. Applications of XYZ Data:

1. Bathymetric Mapping: Create contour maps, 3D surface models, and digital
elevation models (DEMs).
2. Seafloor Visualization: Used in GIS software (such as ArcGIS or QGIS) to
generate bathymetric charts.
3. Submarine Features Identification: Help in identifying underwater features
such as ridges, valleys, and structures like pipelines or cables.
 14. Data Conversion to XYZ Format:
Once the raw bathymetric data is collected, the following steps occur to convert it into
XYZ format:

1. Data Collection: The raw depth data is collected along the survey line by the
MBES or SBES equipment.

2. Data Processing: The raw data is processed to include the correct geographic
coordinates for each data point. This involves referencing the collected depth
readings to their respective longitude and latitude positions.

3. Formatting: The processed data is then formatted into XYZ format, where each
line represents a depth measurement at a specific latitude and longitude. The
data might be recorded every meter (or at other intervals based on survey
requirements).

Example Workflow:
1. Data Collection:
o The MBES records depth readings at regular intervals as the survey vessel
moves along the designated survey path.

2. Georeferencing:
o The DGPS system provides the exact longitude and latitude for each
depth measurement.

3. Data Formatting:
o The collected depth readings (Z) are combined with the longitude (X) and
latitude (Y) to form the XYZ file.

4. Output:
o The XYZ data is saved in a text-based file (CSV or TXT format) for use in
further analysis or visualization.

15. Isopach Spot Depths in XYZ Format:

Isopach refers to contours representing thickness variations of a
particular sediment or geological layer. In this case, spot depths indicate
specific points along the survey area where the thickness of the sediment
or seabed layers has been recorded.
• XYZ Format:X (Longitude)
 o Y (Latitude)
o Z (Spot Depth or Thickness)
Example:

Longitude, Latitude, Thickness (m)

50.5820, 26.2020, 1.5

50.5821, 26.2021, 2.0

50.5822, 26.2022, 1.8

16. Raw Grab Sample Images:

These are images of the samples taken from the seabed using a grab sampler. These
images are typically photos or scans of the samples collected during the survey.
• Format:
o Photos may be in JPG or PNG format.
o Each image should ideally be associated with metadata (e.g., Sample ID,
Location, Time).
o Example filenames might look like GS001_sample.jpg,
GS002_sample.png.
These images will help illustrate the physical characteristics of the collected seabed
materials.
17. Tide Table for the Entire Survey Period:
The tide table records the tidal data (high/low tides, tidal range, etc.) over the entire
survey period. It helps in understanding the sea level fluctuations during the survey,
which can affect bathymetric data accuracy.
• Format:
o Typically, the tide table is presented in a CSV or Excel format.
o Columns may include Date, Time, High Tide, Low Tide, and Tidal Range.
Example of Tide Table:

Date, Time, High Tide (m), Low Tide (m), Tidal Range (m)

2025-03-06, 12:00, 2.5, 0.8, 1.7

2025-03-06, 18:00, 2.4, 0.9, 1.5

 18. Marine Activity Record within and in the Vicinity of the Survey Area:
This record logs any marine activities (such as vessels, construction, fishing, etc.) that
occurred during the survey period or near the survey area. This information is crucial for
understanding external influences on the survey environment.
• Format: Typically, a CSV or Excel file.
• Columns include Date, Time, Activity Type, Location, and Description.
Example:

Date, Time, Activity Type, Latitude, Longitude, Description

2025-03-06, 10:30, Fishing, 26.2020, 50.5820, Fishing boats in the area

2025-03-06, 15:00, Vessel Transit, 26.2025, 50.5825, Supply ship passing by

19. MDB Bathymetry Contour File:

This file contains the bathymetric contours representing various depth levels of the
seafloor. The MDB (Multibeam Data) refers to bathymetric data collected using
multibeam echo sounders. The file will contain contour lines at specific depth
intervals.
• Format:
o This could be in ESRI shapefile (.shp) format or other GIS-compatible
formats (e.g., GeoJSON or KML).
o Contour Lines will represent specific depths at intervals (e.g., 1m, 5m,
etc.).

20. MDB Seabed Features File:

This file records the features observed on the seabed (such as wrecks, cables,
pipelines, or natural features like ridges or valleys) based on the survey data.
• Format:
o Likely stored in an MDB (or KML, GeoJSON, etc.) format.
o Each feature is typically marked with location coordinates and an
associated description (e.g., cable, rock, etc.).
 21. GeoTIFF Showing Seabed Gradients (Change of Gradient Interval Every
5°):
A GeoTIFF can be generated to show the gradients of the seabed, highlighting areas
where the seafloor changes sharply. The 5° change in gradient likely refers to
representing slope changes of the seabed at 5-degree intervals.
• Format: A GeoTIFF image with each pixel representing a specific gradient of the
seafloor.
• The gradient could represent the change in slope or bathymetric slope over a 5°
range.

22. MDB Isopach Contour File (Where Required):

Similar to the bathymetric contours, an isopach contour file shows the thickness of a
geological layer (e.g., sediment thickness) in the survey area.
• Format:
o Typically shapefile (.shp), GeoJSON, or KML.
o Contour lines will represent areas of equal thickness in the survey area

23. Between Inshore Limit to 15m/End of Inshore Survey Corridor – Images

of Bathymetric DTM (Digital Terrain Model):
A Digital Terrain Model (DTM) is a 3D representation of the seabed's surface. It helps to
visualize the terrain and depths across the survey area.
• Format:
o GeoTIFF, KML, or 3D model formats (e.g., OBJ).
o This file will likely include images or visual models of the seabed between
the inshore limit and the 15-meter depth contour.

24. Bathymetry GeoTIFFs:

These GeoTIFFs represent bathymetric data in raster form, where each pixel
corresponds to a specific depth value. This can be used for visualization of the
bathymetry across the survey corridor.
• Format: GeoTIFF (raster image format) with depth data encoded in the pixel
values.

25. Bathymetry KML – Major and Minor Contour Layers with the Depth (Z
Value) Embedded:
A KML file is used to store and share geographic data, often in the context of Google
Earth or other GIS tools.
 • Format: KML (Keyhole Markup Language).
• It will contain major and minor contours as separate layers, with depth (Z
values) embedded as part of the contour data.

26. 13. Seabed Features .KML – Contain the Same Layers from MDB File:
The Seabed Features KML file will include all the seabed features (e.g., cables,
pipelines, rocks, wrecks) recorded in the MDB Seabed Features File, but in KML
format, which is compatible with mapping tools like Google Earth.
• Format: KML.
• The layers will contain geographic coordinates for each seabed feature, with
depth and feature descriptions embedded.