Map Projections & Coordinate Systems: Types, Math & Applications

TAKEAWAYS:

• Map projections distort distance, area, or shape to flatten Earth’s sphere; no perfect projection exists—choose based on use case (navigation vs. area accuracy).
• Geographic Coordinate System (GCS) uses latitude/longitude (spherical), while Projected Coordinate Systems (PCS) like UTM use flat-grid metrics for measurements.
• Datum defines Earth’s shape (e.g., WGS84 vs. Nepal’s Everest 1830) and directly affects accuracy in GPS or cadastral maps.
• UTM divides Earth into 60 zones for minimal distortion; Nepal spans Zone 44–46N.
• Reprojection errors (e.g., shifting rivers in Google Maps) occur when data from different projections are overlaid without transformation.
• Real-world impact: A 1° lat/long error at the equator = 111 km—critical for disaster response or aviation.

Why Projections Matter: The Earth’s Unfolding Problem

Earth is a spheroid (oblate ellipsoid), but maps are flat. When you "unfold" a globe, distortions are inevitable. The choice of projection affects:

• Distance (e.g., great-circle routes for flights).
• Area (e.g., Greenland vs. Africa on Mercator).
• Shape (e.g., Greenland’s "spiky" appearance).
• Direction (e.g., compass bearings in navigation).

mindmap
  root((Map Projection Distortions))
    Distance["Great-circle vs. straight-line (e.g., flight paths)"]
    Area["Equal-area projections (e.g., Gall-Peters for fair representation)"]
    Shape["Conformal projections (e.g., Mercator for local angles)"]
    Direction["Azimuthal projections (e.g., polar navigation)"]

1. Types of Map Projections: A Classification

Projections are categorized by their mathematical transformation and preserved property. The three primary families:

Worked Example: Why Nepal Uses Transverse Mercator (TM)

Nepal’s Nepal National Grid (NNG) uses Transverse Mercator (TM) projection because:

1. Shape accuracy: Conformal property preserves angles for topographic maps (e.g., 1:25,000 scale for trekking routes).
2. Minimal distortion: Nepal’s narrow east-west span fits within one UTM zone (44–46N).
3. Legal use: Cadastral maps (land records) require precise boundary shapes.

Trace:

• Input: Lat/long of Kathmandu (27.7172°N, 85.3240°E).
• Projection: Convert to UTM Zone 45N, NAD27 datum.
• Output: Easting = 499,900 m, Northing = 3,077,000 m.
• Error check: If plotted on WGS84 Mercator, Kathmandu’s position shifts ~100 m—critical for land surveys or disaster response grids.

2. Coordinate Systems: From Lat/Long to Grid References

A. Geographic Coordinate System (GCS)

• Uses latitude (φ) and longitude (λ) on a sphere.
• Units: Degrees (°), minutes (′), seconds (″) or decimal degrees (DD).
• Problem: Distance between lines of longitude varies (111 km at equator vs. 0 at poles).

B. Projected Coordinate Systems (PCS)

Converts GCS to a flat grid (meters) using a projection. Key systems:

1. Universal Transverse Mercator (UTM)

   • Divides Earth into 60 zones (6° wide), each with its own central meridian.
   • Nepal: Zones 44N–46N (e.g., Kathmandu in 45N).
   • False Easting/Northing: Adds 500 km to avoid negative values.

2. State Plane Coordinate System (SPCS)

   • Used in countries like the US for legal surveys.
   • Nepal’s Nepal National Grid (NNG) is a custom SPCS.

3. Web Mercator (WGS84)

   • Used by Google Maps, OpenStreetMap.
   • Distortion: Greenland appears larger than Africa (area ratio ~14x).

Comparison Table:

3. Datum: The Reference Ellipsoid

A datum defines:

1. Shape of Earth: Ellipsoid (e.g., WGS84 vs. Everest 1830).
2. Origin point: Where the ellipsoid "touches" Earth (e.g., NAD83 uses Clarke 1866).
3. Orientation: How the ellipsoid aligns with Earth’s gravity.

Nepal’s Datums:

• Everest 1830: Used for cadastral maps (land records).
• WGS84: Used for GPS (e.g., Pathao navigation).
• Problem: A point in Kathmandu may differ by ~20 m between Everest 1830 and WGS84.

Worked Example: GPS vs. Land Survey Discrepancy

Scenario: A farmer in Chitwan uses eSewa’s land measurement tool (GPS-based, WGS84) but his land record (NNG, Everest 1830) shows a different boundary. Steps:

1. GPS records: Lat/Long = (27.456°N, 84.123°E).
2. Convert to UTM Zone 45N (WGS84): Easting = 500,000 m, Northing = 3,045,000 m.
3. Reproject to NNG (Everest 1830): Easting shifts ~15 m, Northing ~10 m.
4. Result: The land parcel appears offset by ~20 m—enough to cause a legal dispute.

Solution: Use datum transformation tools (e.g., QGIS) to convert between systems.

4. Reprojection and Data Integration

Problem: Combining data from different projections (e.g., satellite imagery in WGS84 + cadastral maps in NNG) causes misalignment. Solution: Reprojection using software like:

• QGIS (Project → Reproject).
• ArcGIS (Define Projection tool).
• GDAL (command-line tool).

Example: Overlaying NTC’s power line routes (UTM) with Daraz delivery zones (Web Mercator) requires reprojection to avoid 100 m+ errors in planning.

flowchart TD
    A["Raw Data\n(e.g., Google Earth: WGS84 Web Mercator)"] --> B["Reproject\nto Target PCS\n(e.g., UTM Zone 45N)"]
    C["Cadastral Data\n(NNG, Everest 1830)"] --> B
    B --> D["Overlay Analysis\n(e.g., flood risk zones)"] --> E["Accurate Output"]

5. Real-World Applications in Nepal

1. eSewa & Khalti: GPS for Payments

• Idea: Geofencing (latitude/longitude boundaries) to restrict transactions (e.g., Khalti limits payments within Nepal’s UTM Zone 44–46N).
• Projection: Uses WGS84 for global GPS but converts to NNG for local land-based services (e.g., property verification).

2. Pathao & Ncell: Navigation Systems

• Idea: UTM grids for precise route calculations.
• Example: A Pathao rider in Pokhara uses UTM Zone 45N to calculate the shortest path between two points, avoiding the Web Mercator distortion that would overestimate distances near the equator.

3. NEPSE & Land Records: Cadastral Mapping

• Idea: Everest 1830 datum for legal land boundaries.
• Example: When a farmer in Ilam sells land, the NNG coordinates (not WGS84 GPS) are used to register the transaction—preventing disputes from datum differences.

4. NTC & Daraz: Infrastructure Planning

• Idea: UTM overlays for power lines and delivery routes.
• Example: NTC uses UTM Zone 44N to plot power grids, while Daraz uses Web Mercator for customer-facing maps. Engineers reproject both to NNG for accurate ground-level planning.

Exam Tip: How to Score Full Marks

1. Define Clearly:

   • "A datum is a reference ellipsoid + origin point used to define coordinates on Earth’s surface."
   • "UTM divides Earth into 60 zones of 6° longitude, each with its own central meridian to minimize distortion."

2. Compare Projections:

   • Use a table (like above) to contrast Mercator vs. Albers vs. UTM for a specific use case (e.g., "Which would you use for a Nepal topographic map?" → UTM).

3. Worked Examples:

   • Always show calculations for conversions (e.g., lat/long to UTM).
   • Highlight datum differences in Nepal (WGS84 vs. Everest 1830).

4. Real-World Links:

   • Connect to eSewa (geofencing), Pathao (UTM routing), or NTC (NNG grids).
   • Example answer snippet: "Like Pathao uses UTM Zone 45N to calculate rider routes in Pokhara, Nepal’s cadastral maps rely on the Nepal National Grid (NNG) in Everest 1830 datum to avoid legal disputes over land boundaries."

5. Common Pitfalls:

   • Don’t confuse GCS (lat/long) with PCS (meters).
   • Never assume WGS84 works everywhere—Nepal’s land records use Everest 1830.
   • Reprojection is critical when combining datasets (e.g., satellite + cadastral maps).

6. Diagrams:

   • Draw a UTM zone map showing Nepal’s zones 44–46N.
   • Label a Mercator vs. Equal-Area projection to show distortion.
   • Show a datum offset between WGS84 and Everest 1830 over Nepal.

Final Visual Summary:

graph LR
    A["Earth's Spheroid"] --> B["Projection\n(Mercator/UTM/etc.)"]
    B --> C["Coordinate System\n(GCS or PCS)"]
    C --> D["Datum\n(WGS84/Everest 1830)"]
    D --> E["Real-World Use\n(eSewa, Pathao, NTC)"]
    E --> F["Accurate Mapping\nor Disaster Response"]