Look up the correct EPSG code for a project's State Plane Coordinate System zone and reproject GNSS-collected geographic coordinates into it programmatically.
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Look up the authoritative EPSG code for the target State Plane zone (NAD83, specific zone and units) using the official EPSG Geodetic Parameter Dataset registry at epsg.org, or the community mirror at spatialreference.org.
Do not rely on epsg.io's REST API for new integrations — its /search and /transform endpoints were migrated to the MapTiler Coordinates API, and unmigrated calls to the old epsg.io API endpoints are no longer reliable as of the 2025 cutover; the human-facing epsg.io lookup site itself still works for casual browsing.
In Python, install pyproj and build a CRS/Transformer pair with `Transformer.from_crs(source_epsg, target_epsg, always_xy=True)`.
Use the modern `pyproj.crs.CRS` and `pyproj.transformer.Transformer` classes, not the deprecated `pyproj.Proj`/`transform()` functions flagged in pyproj's own gotchas/FAQ page.
Spot-check a known monument's published NGS datasheet coordinate against your transformed output before trusting the pipeline on production data.
Known gotchas
epsg.io's programmatic API (not the web page) migrated to MapTiler's Coordinates API — code written against the old epsg.io /search or /transform REST endpoints may silently break or require an API key now.
US survey feet vs. international feet vs. meters is a common silent error source in State Plane EPSG selection — many states have separate EPSG codes for survey-foot and meter realizations of the same zone.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?