CSV Format

orig_lat,orig_lon,trans_lat,trans_lon,source_datum,target_datum
51.5074,-0.1278,51.5063,-0.1265,WGS84,OSGB36
35.6762,139.6503,35.6758,139.6499,Tokyo,JGD2011
-33.8688,151.2093,-33.8674,151.2079,GDA94,GDA2020
Supported source datums: WGS84, OSGB36, Tokyo, JGD2000, GDA94, NAD27, NAD83
Supported target datums: WGS84, OSGB36, JGD2011, GDA2020, NAD83, ETRS89
Maximum 500 rows. Headers optional (auto-detected).

Use Cases for Batch Validation

  • Survey QA: Validate a transformed dataset before submission to a client or regulatory body
  • GIS data migration: Flag coordinate rows that look suspicious after a datum conversion pipeline
  • Contractor audit: Cross-check transformed coordinates supplied by a third party
  • Legacy data review: Detect NAD27/NAD83 confusion in historical survey data

Related Tools & Resources

Explore our full suite of coordinate transformation and compliance tools:

GIS Tools Hub Universal Sandbox (EPSG Explorer) LatLong —UTM Datum Compliance Engine
Certified Geodetic Insight
Verified against professional geodetic standards

The $50,000 Geodetic Drift Liability: 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 $50,000 Professional Liability claims for foundational rework and utility misplacement.

Risk Exposure Metric: 2.2-Meter Tectonic Drift & Epoch Accumulation

What's Your Next Step?

Explore more coordinate tools. Continue your journey with our precision tools and guides.

Warning: Verify Your Calculation

Coordinate accuracy varies by device and datum. Do not use these results for legal or construction purposes without checking:

GPS Accuracy Alert

Your phone's GPS can be off by 30 meters. This can cause critical errors in your data.

Check My Accuracy

Datum Shift Risk

Using the wrong coordinate system (e.g. WGS84 vs NAD83) creates a permanent 1-meter offset.

Verify My Datum