Geodesy Study Guide

📖 Core Concepts Geodesy – science of measuring Earth’s 3‑D shape, gravity field, and orientation over time. Geoid – equipotential surface of mean sea level; irregular, continues under continents. Reference Ellipsoid – smooth mathematical surface (defined by semi‑major axis a and flattening f) that approximates the geoid for calculations. Geoidal Undulation (N) – vertical separation between geoid and ellipsoid (≈ ±110 m for GRS 80). Datum – physical realization of a coordinate system (horizontal or vertical) anchored to surveyed points. Cartesian (ECEF) Coordinates – 3‑D X, Y, Z with origin at Earth’s centre of mass; Z aligns with rotation axis. Inertial vs. Earth‑Fixed (Co‑rotating) – inertial axes fixed to distant stars; Earth‑fixed axes rotate with Earth (used for everyday positioning). Map Projection – mathematical transformation from curved Earth to a flat plane; conformal projections preserve angles (e.g., UTM). Height Types – Ellipsoidal height (h) above ellipsoid, Orthometric height (H) above geoid, Dynamic height (D) from geopotential, Geopotential number (C). GNSS Positioning – satellite‑based determination of coordinates; point (absolute) vs relative (baseline) positioning; RTK provides cm‑level precision. Geodetic Problems – Direct (first): compute second point from start point, azimuth, distance. Inverse (second): compute azimuth & distance between two known points (Vincenty’s formulas on ellipsoid). 📌 Must Remember Flattening: $f = \dfrac{a-b}{a}$; GRS 80: $a = 6\,378\,137\,$m, $f = 1/298.257$. Geoidal undulation range: ±110 m (GRS 80). Nautical mile: 1 NM = 1 minute of latitude = 1 852 m exactly. UTM zones are 6° wide; each zone uses a transverse Mercator conformal projection. Vincenty’s inverse converges for points nearly antipodal; fallback to alternative algorithms needed. RTK requires a nearby base station (≤ 10–20 km) and a real‑time correction stream. Orthometric height = ellipsoidal height – geoidal undulation → $H = h - N$. Plumb line = direction of local gravity; zenith = upward extension of plumb line on celestial sphere. 🔄 Key Processes Converting Ellipsoidal to Orthometric Height Obtain ellipsoidal height h from GNSS. Retrieve geoid model value N at the location. Compute $H = h - N$. Solving the Inverse Geodetic Problem (Vincenty) Input lat/lon of points 1 & 2 and ellipsoid parameters (a, f). Iterate to solve for reduced latitude, λ, and σ until change < 1 µrad. Output forward & reverse azimuths and geodesic distance s. Transforming Between Inertial and Earth‑Fixed Frames Compute Greenwich Apparent Sidereal Time (GAST) for epoch. Apply rotation matrix about Z by GAST. Add polar‑motion corrections (if high precision). RTK Positioning Workflow Base station streams carrier‑phase corrections. Rover receiver collects raw GNSS observables. Double‑difference processing yields integer‑cycle ambiguities → resolve → compute baseline vector → obtain rover coordinates. 🔍 Key Comparisons Geoid vs. Reference Ellipsoid – Geoid: irregular, physical sea‑level surface; Ellipsoid: smooth, mathematical, used for computations. Orthometric Height vs. Ellipsoidal Height – Orthometric: measured above geoid (used for engineering, flood mapping); Ellipsoidal: measured above ellipsoid (output of GNSS). Point Positioning vs. Relative Positioning – Point: absolute coordinates in global frame; Relative: coordinates expressed as a vector from a known point (higher precision over short baselines). Inertial Frame vs. Earth‑Fixed Frame – Inertial: axes fixed to stars, no Earth rotation; Earth‑Fixed: rotates with Earth, convenient for navigation. Conformal Projection vs. Equal‑Area Projection – Conformal: preserves angles/shapes locally (e.g., UTM); Equal‑Area: preserves area, distorts shape (e.g., Lambert Azimuthal). ⚠️ Common Misunderstandings “Geoid = sea level” – The geoid is mean sea level without currents/pressure, not the actual observed sea surface at any moment. “Ellipsoidal height is the true height above ground” – It’s height above a mathematical surface; must be corrected by N to get physical height. “Vincenty always works” – It fails to converge for nearly antipodal points; use alternative (e.g., Karney’s algorithm). “UTM zones are universal” – Polar regions use UPS (Universal Polar Stereographic); UTM not defined beyond 84° N/S. “RTK works anywhere” – Requires a nearby base with reliable communication; ionospheric disturbances can degrade accuracy. 🧠 Mental Models / Intuition Geoid as “bumpy sea” – Imagine a perfectly still ocean covering the Earth; the bumps are gravity anomalies. Ellipsoid as “smooth egg” – A mathematically perfect, slightly flattened sphere used as a ruler. Geodetic inverse problem like “great‑circle navigation” – Find the shortest path (geodesic) and its heading; on an ellipsoid the path is slightly “wiggly”. RTK as “real‑time differential GPS” – Base station tells rover “the satellite signals are off by X meters”; rover corrects instantly. 🚩 Exceptions & Edge Cases Polar Regions – Use UPS projection; standard UTM zones do not apply. High‑latitude GNSS – Satellite geometry degrades; positioning errors increase. Large baseline relative positioning – Atmospheric and ionospheric errors no longer cancel; precision drops. Geoid models – Local/ regional models (e.g., EGM2008 vs. national models) may differ by up to several meters; choose appropriate model for the area. 📍 When to Use Which Height conversion – Use ellipsoidal→orthometric when you need physical elevation (e.g., flood mapping). Direct vs. Inverse problem – Use direct when you have a starting point, bearing, and distance (survey traverses). Use inverse when you have two known positions and need distance/azimuth (network adjustment). Projection choice – Use UTM for mid‑latitude, moderate‑area mapping; switch to Lambert Conformal Conic for east‑west‑oriented regions; UPS for polar work. Positioning method – Use point positioning for global scale or when no nearby base exists; use RTK/relative positioning for construction, cadastral surveys requiring cm accuracy. 👀 Patterns to Recognize Geoid‑ellipsoid separation (N) sign – Positive N → geoid above ellipsoid (common over oceans); negative N → geoid below ellipsoid (continental interiors). Azimuth change on sphere vs. ellipsoid – On a sphere, azimuths at both ends differ symmetrically; on an ellipsoid they differ asymmetrically, especially at high latitudes. GNSS residual patterns – Systematic residuals often indicate unmodeled ionospheric delays or outdated satellite ephemerides. Map‑scale distortion – In conformal projections, scale factor deviates from 1 away from the central meridian; look for “scale factor > 1” in UTM zone edges. 🗂️ Exam Traps Confusing N with height – A question may give h (ellipsoidal) and ask for H; forgetting to subtract N yields a large error. Latitude vs. longitude units – Some items state “1 NM = 1 minute of latitude”; mixing degrees with minutes leads to factor‑60 mistakes. Vincenty non‑convergence – An answer choice may present a distance from Vincenty for antipodal points; correct response is “use alternative algorithm” or “result undefined”. UTM zone identification – Traps often give a longitude just outside a zone’s 6° span; ensure correct zone number (e.g., 33 N vs. 34 N). RTK baseline length – A distractor may claim RTK works over 200 km; the correct limit is typically ≤ 10–20 km for reliable cm‑level accuracy. Geoid vs. ellipsoid curvature – Some items conflate “curvature of geoid” with “flattening of ellipsoid”; remember flattening $f$ applies only to the ellipsoid.