Coordinate Format Auto-Detector
The "Magic Box" Geodetic Engine: Paste any coordinate string to identify its format instantly.
Quick Reference: Format Detection
Why this matters: Detecting the right coordinate format first eliminates the most common source of conversion error. This is especially important before you convert for professional or legal workflows.
Pro Tip: If the detector identifies UTM or MGRS, use the linked coordinate tools immediately to avoid manual transcription mistakes.
Liability Note: Format Misidentification
Misidentifying a coordinate format (e.g. confusing Decimal Degrees with local Grid Eastings) is a leading cause of 1:1 project alignment failure. Professional geodetic workflows require format verification against project specifications to avoid systematic errors. This tool is a reference engine only and should be verified against official datum documentation.
How the Engine Identifies Formats
Our pattern-matching engine uses geodetic regex benchmarks to parse strings for localized markers:
- MGRS: Looks for the 100km square identification letters (e.g.
SUJ) and grid zone designators. - UTM: Identifies Easting (6 digits) and Northing (7 digits) separated by zone designators (e.g.
33T). - DMS: Parses symbols like , ′, ″ and hemisphere suffixes (N, S, E, W).
- Decimal: Validates numeric ranges within latitudinal (±90) and longitudinal (±180) boundaries.
The Cumulative Boundary & Engineering Rework Exposure: NAD83 vs WGS84
Because the North American Plate moves ~2cm/year, NAD83(2011) and WGS84(G1762) currently diverge by over 2.2 meters. Using a "standard" GPS WGS84 coordinate for a high-precision NAD83 cadastral staking has triggered Boundary Dispute Geodetic Offset claims for foundational rework and utility misplacement.