crs-and-reprojection

Estrelas12

Forks2

Atualizado14 de março de 2026 às 22:28

Use when working with coordinate reference systems, EPSG codes, datum mismatches, reprojection choices, projected versus geographic CRS, unit confusion, or map alignment problems in geospatial data.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

phuismann

phuismann/geoskills

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	crs-and-reprojection
description	Use when working with coordinate reference systems, EPSG codes, datum mismatches, reprojection choices, projected versus geographic CRS, unit confusion, or map alignment problems in geospatial data.

CRS And Reprojection

Use this skill when the core problem is spatial reference correctness.

Goals

Determine whether the current CRS information is known, missing, or wrong.
Explain the operational impact of the CRS on measurements, overlays, and map alignment.
Recommend a safe target CRS for the task.
Distinguish assigning a CRS from reprojecting data.

Workflow

Establish the current state.
- What CRS is declared?
- Is it geographic or projected?
- What units are implied?
Check whether the CRS matches the task.
- Web mapping.
- Distance or area measurement.
- Local engineering workflow.
- Regional or global analysis.
Identify the failure mode.
- Missing CRS metadata.
- Wrong CRS assignment.
- Mixed layers in different CRS.
- Datum mismatch.
- Coordinates with suspicious magnitude or axis order.
Recommend the correction path.
- Assign the correct source CRS if metadata is missing but known.
- Reproject only after the source CRS is trustworthy.
- Choose a target CRS based on the analysis objective, not habit.
State validation checks.
- Overlay known reference layers.
- Confirm units.
- Sanity-check extent and feature alignment.

Decision Rules

Use a local or regional projected CRS for accurate distance and area work.
Use geographic CRS only when the workflow truly operates in angular coordinates.
Avoid Web Mercator for precision measurement analysis.
If the source CRS is uncertain, stop and resolve that before downstream processing.

Output Format

Observed CRS situation:
Why it is a problem or not:
Recommended source CRS action:
Recommended target CRS:
Validation checks:
Risks / assumptions:

Example Triggers

"These layers do not line up, help me diagnose the projection issue"
"Which EPSG should I use for area calculations in this region?"
"Do I assign a CRS or reproject this dataset?"
"Why are the coordinates huge and the map is offset?"

Mais deste repositório

mesmo repositório

global-crs-selection

phuismann/geoskills

Use when choosing a coordinate reference system for world-scale or near-global geospatial work, including global maps, world choropleths, antimeridian issues, polar coverage, global grids, or deciding between EPSG:4326, EPSG:3857, Equal Earth, LAEA, Robinson, or other world projections.

2026-03-1412

geospatial-ml

phuismann/geoskills

Use when applying machine learning to geospatial data, including spatial feature engineering, morphometric indicators, urban analysis, spatial cross-validation, library selection, or integrating geopandas, momepy, pysal, osmnx, torchgeo, or rasterio into an ML pipeline.

2026-03-1412

geodata-intake

phuismann/geoskills

Use when inspecting a new geospatial dataset for the first time, including GeoJSON, Shapefile, GeoPackage, raster, CSV with coordinates, or mixed geo data. Helpful for schema review, CRS detection, geometry summary, dataset extent, and first-pass analysis planning.

2026-03-1412

geodata-qaqc

phuismann/geoskills

Use when performing quality assurance or quality control on geo data before analysis, sharing, or publishing. Covers vector validity, attribute consistency, raster sanity checks, completeness, and basic geospatial data fitness review.

2026-03-1412

postgis-geospatial

phuismann/geoskills

Use when working with PostGIS in PostgreSQL for geospatial SQL, including geometry or geography design, SRID handling, spatial indexing, ST_Intersects or ST_DWithin queries, raster or vector analysis patterns, and query tuning for PostGIS workloads.

2026-03-1412

snowflake-geospatial

phuismann/geoskills

Use when working with geospatial data in Snowflake, including GEOGRAPHY columns, WKT or GeoJSON loading, spatial joins, ST_INTERSECTS or ST_DISTANCE queries, geohash workflows, and performance-aware SQL design for geo analytics in Snowflake.

2026-03-1412

name	crs-and-reprojection
description	Use when working with coordinate reference systems, EPSG codes, datum mismatches, reprojection choices, projected versus geographic CRS, unit confusion, or map alignment problems in geospatial data.

CRS And Reprojection

Use this skill when the core problem is spatial reference correctness.

Goals

Determine whether the current CRS information is known, missing, or wrong.
Explain the operational impact of the CRS on measurements, overlays, and map alignment.
Recommend a safe target CRS for the task.
Distinguish assigning a CRS from reprojecting data.

Workflow

Establish the current state.
- What CRS is declared?
- Is it geographic or projected?
- What units are implied?
Check whether the CRS matches the task.
- Web mapping.
- Distance or area measurement.
- Local engineering workflow.
- Regional or global analysis.
Identify the failure mode.
- Missing CRS metadata.
- Wrong CRS assignment.
- Mixed layers in different CRS.
- Datum mismatch.
- Coordinates with suspicious magnitude or axis order.
Recommend the correction path.
- Assign the correct source CRS if metadata is missing but known.
- Reproject only after the source CRS is trustworthy.
- Choose a target CRS based on the analysis objective, not habit.
State validation checks.
- Overlay known reference layers.
- Confirm units.
- Sanity-check extent and feature alignment.

Decision Rules

Use a local or regional projected CRS for accurate distance and area work.
Use geographic CRS only when the workflow truly operates in angular coordinates.
Avoid Web Mercator for precision measurement analysis.
If the source CRS is uncertain, stop and resolve that before downstream processing.

Output Format

Observed CRS situation:
Why it is a problem or not:
Recommended source CRS action:
Recommended target CRS:
Validation checks:
Risks / assumptions:

Example Triggers

"These layers do not line up, help me diagnose the projection issue"
"Which EPSG should I use for area calculations in this region?"
"Do I assign a CRS or reproject this dataset?"
"Why are the coordinates huge and the map is offset?"