Day 22: GNSS & Tide Integration – Masterpiece Edition | River Warrior

🛰️ DAY 22: GNSS & TIDE INTEGRATION

Masterpiece Edition – Combining Satellite Positioning with Water Level Corrections

Instructor: Engr. Rokib Hossain | River Warrior Academy

🏠 Course Homepage

📖 Table of Contents (Serialised)

Why Integrate GNSS and Tide?
Vertical Datums – Ellipsoid, Geoid, Chart Datum
Local Geoid Undulation Range (Bangladesh Delta)
From Instantaneous Water Level to Chart Datum
Real‑Time Integration in Acquisition Software
Practical Field Workflow Diagram
Field Checklist for GNSS‑Tide Integration
🔗 Essential External Resources (Authority Domains)
Frequently Asked Questions (with internal links)
Action Items & Next Steps
Post‑Verification Checklist (SEO & Engineering)

1. Why Integrate GNSS and Tide?

Hydrographic surveys measure depth from the vessel's transducer to the seabed. To produce a chart, depths must be referenced to a stable vertical datum (Chart Datum, usually Lowest Astronomical Tide). The GNSS gives ellipsoidal heights (H_ell). The tide gauge gives water level relative to Chart Datum. The integration is:

Depth(CD) = (Draft corrected depth) – Tide_gauge(relative to CD)

🧠 Expert Note – Transducer Draft & Index Error: The “draft corrected depth” means raw transducer depth minus the vertical offset from the water surface to the transducer face (draft). Additionally, any constant offset in the echo sounder measurement is called index error. Always calibrate index error using a bar check or known depth.

Figure: Integration of GNSS ellipsoidal height, tide gauge, and transducer draft/index error to produce charted depth.

2. Vertical Datums – Ellipsoid, Geoid, Chart Datum

Three main vertical references:

Ellipsoid (WGS84): Mathematical surface. GNSS gives height above ellipsoid (h).
Geoid (EGM2008): Mean sea level surface. Orthometric height (H) = h - N, where N = geoid undulation.
Chart Datum (CD): Usually Lowest Astronomical Tide (LAT). All depths on nautical charts are referenced to CD.

📌 Key point: GNSS gives ellipsoidal height. To get depth relative to Chart Datum, apply: geoid correction + tide reduction.

3. Local Geoid Undulation Range (Bangladesh Delta)

In the Ganges-Brahmaputra delta (Bangladesh), the EGM2008 geoid undulation N varies between –0.5 m and +1.2 m depending on location. For precise work, download the local geoid model from the EGM2008 official page or use national grid data. Always apply the correct N value before tide reduction.

🧪 Field tip: If you have a known benchmark (BM) with orthometric height, compute N = h(GNSS) – H(BM). This gives you a real‑world check.

4. From Instantaneous Water Level to Chart Datum

Depth_CD = (Draft corrected depth) – Tide_gauge(relative to CD)

5. Real‑Time Integration in Acquisition Software

1️⃣ Configure GNSS input (NMEA GGA). Set antenna offset and geoid model.

2️⃣ Connect tide gauge (serial/Ethernet). Define vertical datum.

3️⃣ Enter offset between gauge zero and Chart Datum.

4️⃣ Apply real‑time tide reduction – software subtracts tide from raw depth.

💡 Pro tip: If using predicted tides, verify with a tide staff at beginning and end of day. Difference >0.1 m means you need a gauge.

6. Practical Field Workflow Diagram

7. Field Checklist for GNSS‑Tide Integration

✅ Before leaving office: Obtain predicted tides, verify Chart Datum offset (MSL‑CD). Download EGM2008 geoid model for your area.
✅ On site (setup): Set up GNSS base station, measure antenna height. Perform bar check to determine index error.
✅ Tide gauge deployment: Mount at known reference, record initial reading. Verify draught of transducer.
✅ Software configuration: Enter antenna offset, geoid model, tide gauge datum, CD offset, and draft.
✅ Test line: Run over known depth, verify reduced depth matches.
✅ During survey: Log tide readings every 10 minutes, watch for sudden changes.
✅ End of day: Download tide gauge data, compare with predictions, note anomalies.

8. 🔗 Essential External Resources (Authority Domains)

To master GNSS integration and IHO S-44 standards, follow these official global authorities:

Organization	Resource Category	Actionable Link
NOAA	Nautical Charts & Vertical Datums	Explore NOAA Resources
IHO	S-44 Standards for Hydrographic Surveys	View IHO Standards
Hydro International	Technical GNSS & Tide Articles	Read Tech Articles
Esri Ocean	GIS for Hydrographic Data Management	Visit Esri Ocean
Kongsberg Maritime	High-End GNSS & MBES Integration	Kongsberg Maritime
NGA EGM2008	Global Geoid Model (download)	EGM2008 Download

9. Frequently Asked Questions (with internal links)

🔹 Can I use RTK height directly as depth reference without a tide gauge?

Yes, “RTK tide” method uses ellipsoidal height of water surface, but still needs geoid model. Less accurate than traditional gauge. Review Day 5: Tides for more.

🔹 Difference between tide reduction and vertical datum transformation?

Tide reduction → instantaneous water level to Chart Datum. Vertical datum transformation → ellipsoidal height to orthometric height (geoid). Both needed. See Day 20 for data logging context.

🔹 How often to check tide gauge against a staff?

Start, middle, end of each day, and after storms. Line planning (Day 21) also affects tide correction timing.

🔹 Software shows tide correction applied but depths wrong?

Check tide gauge datum, time synchronisation (NTP), and latency. Also verify transducer draft and index error.

🔹 Need geoid model for RTK tide?

Yes, to convert ellipsoidal height to orthometric (MSL) or chart datum. Download EGM2008 from the link above.

10. Action Items & Next Steps

📌 Download local tide table, identify Chart Datum offset from MSL for your nearest port.
📌 Download EGM2008 model and compute N for a known benchmark near your area.
📌 Practice entering tide parameters and draft in Hypack or QINSy demo.
📌 Write a one‑page SOP for “Daily tide gauge checks and GNSS integration”.
📌 Proceed to Day 23: Side Scan Sonar Integration.

11. Post‑Verification Checklist (For Each Post)

✅ SEO & Rich Results Verification

□ Canonical URL is correct and matches the post URL.
□ datePublished and dateModified are current (2026-05-15).
□ Schema markup passes Google Rich Results Test.
□ Open Graph and Twitter Card are present.

✅ Content & Internal Linking Verification

□ Table of Contents uses numbered list with working anchors.
□ All internal links (Day 5, Day 20, Day 21, Day 23) work.
□ External links open in new tab.
□ Print button and black box function correctly.

✅ Technical & Mobile Verification

□ Tables have `overflow-x: auto` wrapper – no horizontal break on 375px.
□ SVG diagrams scale without overflow.
□ No JavaScript errors in console.

🔗 Internal linking complete: Day 21 and Day 23 are correctly linked. FAQ contains links to Day 5, Day 20, Day 21 for better dwell time.

🌊 Day 22: GNSS-Tide & Heave Compensation