crs-and-datumslisted
Install: claude install-skill wiatrek-kevin-s/columbus
# CRS and datums
Most wrong GIS answers that still look plausible come from the coordinate reference system:
measuring in degrees, measuring in Web Mercator, mixing feet, or giving a layer the wrong
label. This skill is about picking the right CRS for the job and noticing when the one you
have is wrong.
## General practice (with or without Columbus)
### 1. Geographic vs projected
- A **geographic** CRS (EPSG:4326 WGS 84, EPSG:4269 NAD83, EPSG:6318 NAD83(2011)) stores
angles in degrees. A degree is not a fixed length. At Austin (30.27° N), one degree of
latitude is about 110.9 km and one degree of longitude about 96.2 km. A "100 unit" buffer
in degrees is meaningless.
- A **projected** CRS stores metres or feet on a flat grid. Measure, buffer and simplify
only in a projected CRS chosen for the area.
### 2. Never measure in EPSG:4326 or EPSG:3857
- **EPSG:4326**: units are degrees (see above). Distances and areas are wrong, and the
error changes with latitude and direction.
- **EPSG:3857 (Web Mercator)**: units look like metres, but its scale grows as
1/cos(latitude). At Austin every length is about 16% too long and every area about 34%
too large. In the Panhandle (35° N) it is about 22% on length. Use 3857 for web map tiles
only.
### 3. Choose a projected CRS by task and area
| Task | Use | Texas examples |
| --- | --- | --- |
| Distance, buffer, length, local work (a city or county) | State plane zone for the area (conformal, very low distortion) | EPS