Coordinate Reference Systems (CRS)

When working with geospatial data, you need a way to describe where things are on the earth. This is where Coordinate Reference Systems (CRS) come in. A CRS defines how the two-dimensional, projected map in your analysis relates to real places on the globe. Without a CRS, your spatial data would have no contex — coordinates would be just numbers, not actual locations.

There are two main categories of CRS: geographic coordinate systems and projected coordinate systems. A geographic coordinate system uses latitude and longitude, representing locations on a spherical surface. In contrast, a projected coordinate system transforms these locations onto a flat surface, using units like meters or feet. This transformation is called a map projection. Each projection distorts the earth's surface in some way, which can affect area, shape, distance, or direction. Choosing the right CRS and projection is crucial, because the wrong choice can lead to inaccurate measurements or misleading maps.

Whenever you analyze, visualize, or combine geospatial datasets, you must ensure that all layers use compatible CRS. If layers use different CRS, their features might not align, and spatial calculations—like measuring distances or finding intersections—will be incorrect. Understanding CRS is therefore fundamental for reliable geospatial analysis.

The code example demonstrates how to work with Coordinate Reference Systems (CRS) using geopandas. First, it loads a GeoDataFrame from a remote GeoJSON file containing populated places. The code then prints the original CRS, which is typically EPSG:4326 (WGS84 latitude and longitude). Next, it reprojects the GeoDataFrame to a different CRS—EPSG:3857 (Web Mercator) — using the to_crs method. Printing the new CRS confirms the transformation. This workflow shows how to inspect and change the CRS of your data, which is essential for ensuring that spatial layers align correctly and measurements are accurate in geospatial analysis.