[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTJF2ANTE6E97PA92VWD95":3,"skill-same:01M7CTJF2ANTE6E97PA92VWD95":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7CTJF2ANTE6E97PA92VWD95","geopandas",null,"Guidance and local audit tools for Python workflows that directly use GeoPandas GeoSeries, GeoDataFrame, spatial operations, or vector-data I\u002FO.","mrsonord2240\u002Fopenscience-specialists","mrsonord2240","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76487430?v=4","01M7CTEM40S43GSJZ9A3YCCXZK","Samuel Nord","01M7CTEM4K69JD1GBYNHVJ9ZP4",2,"MIT","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: geopandas\ndescription: Guidance and local audit tools for Python workflows that directly use GeoPandas GeoSeries, GeoDataFrame, spatial operations, or vector-data I\u002FO.\nlicense: MIT\nmetadata:\n  version: \"1.0.0\"\n  last-reviewed: \"2026-07-23\"\n---\n\n\n\n# GeoPandas\n\nUse GeoPandas for planar vector data represented as pandas-like `GeoSeries` and\n`GeoDataFrame` objects. This skill targets stable **GeoPandas 1.1.4** (released\n2026-06-26), not the unreleased 1.2 documentation.\n\n## Reproducible environment\n\nGeoPandas 1.1.4 requires Python 3.10+; its tagged source requires NumPy >=1.24,\npandas >=2.0, Shapely >=2.0, pyproj >=3.5, pyogrio >=0.7.2, and `packaging`.\nThis exact Python 3.12 snapshot was smoke-tested on 2026-07-23:\n\n```bash\nuv venv --python 3.12\nuv pip install \\\n  \"geopandas==1.1.4\" \\\n  \"numpy==2.5.1\" \\\n  \"pandas==3.0.5\" \\\n  \"shapely==2.1.2\" \\\n  \"pyproj==3.7.2\" \\\n  \"pyogrio==0.13.0\" \\\n  \"pyarrow==25.0.0\" \\\n  \"packaging==26.2\"\n```\n\nKeep optional plotting and PostGIS packages pinned in the project lock as well.\nDo not mix binary geospatial packages from incompatible package channels.\n\n## Safety and privacy contract\n\n- Treat exact coordinates, addresses, parcel boundaries, trajectories, and\n  small-area joins as sensitive. Default reports to counts, categories, coarse\n  extents, and redacted identifiers. Generalize before publication.\n- Never automatically load a URL, cloud URI, GDAL `\u002Fvsi*` path, archive, or\n  geocode an address. Obtain explicit approval, validate provenance and hashes,\n  then stage an unpacked local file in an isolated workspace.\n- GDAL\u002FOGR drivers, GEOS, PROJ, pyogrio, Shapely, pyproj, and their wheels are a\n  native-code trust boundary. Prefer official wheels\u002Fconda-forge, record native\n  versions, restrict drivers, and process untrusted data in a sandbox.\n- Do not open macro-enabled office files or nested archives through permissive\n  GDAL drivers. The bundled CLIs use an extension allowlist and reject archives.\n- Read only named database secrets such as `GEOPANDAS_POSTGIS_PASSWORD`; use a\n  secret manager or scoped environment variable. Never embed a password in a\n  URL or source, print an engine\u002FURL, or dump the environment.\n- Every derived artifact needs source hashes\u002Fversions, CRS, operation parameters,\n  predicate, join cardinality, precision\u002Frepair choices, and row-count checks.\n\n## Correctness gates\n\nApply these gates before trusting a result:\n\n1. **Identity and provenance** — identify the source layer, stable feature key,\n   duplicate IDs, row count, geometry column, parser\u002Fdriver, and content hash.\n2. **Geometry state** — count null, empty, invalid, mixed, Z\u002FM, and collapsed\n   geometries separately. `None` is missing; an empty Shapely geometry is real.\n3. **CRS semantics** — require CRS metadata. `set_crs()` assigns metadata;\n   `to_crs()` transforms coordinates. Never guess a CRS from coordinate ranges.\n4. **Units and operation** — GeoPandas is planar. Geographic coordinates are\n   angular; do not use them directly for buffer, distance, area, nearest joins,\n   precision grids, or tolerances. Choose a fit-for-purpose local\u002Fequal-area CRS\n   or a geodesic method.\n5. **Transform quality** — inspect axis order, area of use, datum pipeline,\n   expected accuracy, ballpark status, and missing grids. Keep PROJ network\n   disabled unless the user explicitly approves grid retrieval.\n6. **Topology and precision** — validate before and after repair\u002Foverlay. Pick a\n   precision grid from source accuracy and CRS units; arbitrary snapping can\n   collapse features or create bias.\n7. **Cardinality** — state expected one-to-one, one-to-many, or many-to-many\n   behavior before `merge`, `sjoin`, or `sjoin_nearest`; audit unmatched and\n   multiplied rows afterward.\n8. **Output contract** — use a new output path, preserve a stable feature ID,\n   document schema\u002FCRS\u002Fencoding, reopen the artifact, and compare counts\u002Ftypes.\n\n## CRS and antimeridian rules\n\nGeoPandas stores CRS as `pyproj.CRS`. Coordinate arrays use traditional GIS\n`(x, y)` order, while authority definitions can advertise latitude-first axes.\nUse `Transformer(..., always_xy=True)` for explicit coordinate-array pipelines,\nand record that choice.\n\n`to_crs()` transforms vertices and assumes each segment is straight in the\nsource CRS; it does not transform geodesic arcs. Geometries crossing ±180° or a\nprojection boundary can be badly wrapped. Detect crossings, split\u002Funwrap and\ndensify in a documented geographic representation, transform parts, then\nvalidate. Do not use Web Mercator as a general measurement CRS.\n\n```python\ncrs = gdf.crs  # a pyproj.CRS when present\nif crs is None or crs.is_geographic:\n    raise ValueError(\"Choose a justified projected CRS before planar measurement\")\n\nunit_names = [axis.unit_name for axis in crs.axis_info]\nareas = gdf.geometry.area  # square CRS units, not automatically square metres\n```\n\nSee [CRS management](references\u002Fcrs-management.md).\n\n## Core API decisions\n\n### Data structures\n\n- A `GeoDataFrame` can hold multiple geometry columns, each with CRS metadata,\n  but only `active_geometry_name` drives frame-level spatial operations.\n- Binary `GeoSeries` methods are row-wise and align by index by default. Use\n  `align=False` only when positional pairing is explicitly intended and lengths\n  and order were verified.\n- Duplicate column names and duplicate feature IDs are ambiguous; reject or\n  resolve them before joins and exports.\n\nSee [data structures](references\u002Fdata-structures.md).\n\n### Geometry validity, precision, and union\n\nUse `is_valid` and redacted `is_valid_reason()` categories before\n`make_valid(method=\"linework\"|\"structure\", keep_collapsed=...)`. Repair can\nchange geometry type or dimension; retain the original and compare counts,\narea, types, empties, and collapsed parts.\n\n`set_precision(grid_size, mode=...)` uses **CRS units** and may remove duplicate\nvertices or collapse features. `union_all(method=\"unary\", grid_size=...)` is the\nrobust default. Use `coverage` only after `is_valid_coverage()` proves\nnon-overlap and edge matching; use `disjoint_subset` with Shapely >=2.1 when its\npartitioning assumption is useful.\n\nSee [geometric operations](references\u002Fgeometric-operations.md).\n\n### Joins, overlay, clip, and dissolve\n\n- `sjoin` predicates are directional: `left.within(right)` is not\n  `left.contains(right)`. `intersects` includes boundary contact; `contains`\n  excludes boundary-only points, while `covers` includes boundary points.\n- `predicate=\"dwithin\"` requires `distance`; scalar or per-left-row distances\n  are in CRS units. `sjoin_nearest` returns all equidistant nearest matches and\n  does **not** implement a `k=` parameter.\n- `overlay(..., make_valid=True)` repairs invalid input but can change types;\n  `keep_geom_type=None` drops other types with a warning. Precision mismatch can\n  create slivers; quantify them rather than silently deleting them.\n- `clip` dissolves the mask. Rectangle clipping is fast but possibly dirty and\n  may omit a line collapsed to a point; validate its output.\n- `dissolve` combines `groupby.agg` with `union_all`; choose explicit attribute\n  aggregations and audit null group keys.\n\nSee [spatial analysis](references\u002Fspatial-analysis.md).\n\n### I\u002FO, Arrow, and PostGIS\n\nGeoPandas 1.x defaults to pyogrio. Driver availability and semantics come from\nthe installed GDAL, not GeoPandas alone. Prefer local GeoPackage for general\ninterchange and WKB GeoParquet for columnar interoperability.\n\nGeoParquet defaults to stable schema 1.0.0. Native GeoArrow encodings and bbox\ncovering require schema 1.1.0 and remain less interoperable. A missing GeoParquet\n`crs` key means `OGC:CRS84`; explicit `crs: null` means unknown—do not conflate\nthem. Reopen and validate every export.\n\nUse parameterized SQL and a SQLAlchemy `Engine`\u002F`Connection` for PostGIS.\n`if_exists=\"replace\"` is destructive; default to `\"fail\"` and use a transaction.\n\nSee [data I\u002FO](references\u002Fdata-io.md).\n\n## Migration checklist\n\nFor code moving from GeoPandas 0.14 or earlier:\n\n- GeoPandas 1.0 supports Shapely >=2 only; PyGEOS, Shapely \u003C2, and the rtree\n  spatial-index backend were removed.\n- pyogrio replaced Fiona as the installed\u002Fdefault I\u002FO engine. Set `engine=`\n  explicitly and test schema, empty, datetime, encoding, and append behavior.\n- Replace `sjoin(op=...)` with `predicate=`, `sindex.query_bulk()` with\n  `sindex.query()`, `unary_union` with `union_all()`, and\n  `GeometryArray.data` with `to_numpy()`\u002F`np.asarray`.\n- Replace `read_file(include_fields=...|ignore_fields=...)` with `columns=`.\n  Use `schema_version=`, not the removed GeoParquet `version=` compatibility.\n- Do not use removed `geopandas.datasets`, internal `geopandas.io.*` entry\n  points, plot `axes`\u002F`colormap`, or set-operation operators.\n- `explode()` now defaults `index_parts=False`; a named Series passed to\n  `set_geometry()` supplies the new active-column name; a named right index can\n  replace `index_right` in `sjoin` output.\n- Do not assign `.crs` to override metadata or rely on deprecated\n  `set_geometry(drop=...)`; use explicit `set_crs()` and rename\u002Fdrop steps.\n- GeoPandas 1.1 requires Python >=3.10, pandas >=2.0, NumPy >=1.24, and pyproj\n  >=3.5. Version 1.1.2 fixed SQL injection through a PostGIS geometry-column\n  name; the pinned 1.1.4 includes that fix.\n\n### Plotting and exploration\n\nMaps are analytical outputs: label units, classification method, missing data,\nnormalization denominator, and date. `explore()` can expose every attribute in\ntooltips\u002Fpopups and contact tile\u002FCDN servers; generalize first and use\n`tiles=None`, `tooltip=False`, and `popup=False` for a local draft.\n\nSee [visualization](references\u002Fvisualization.md).\n\n## Bundled local CLIs\n\nAll helpers are deterministic, reject network\u002Farchive paths, bound input bytes\nand feature counts, keep imports lazy so `--help` is dependency-free, and emit\nJSON without coordinates or record identifiers.\n\n| CLI | Purpose |\n|---|---|\n| `scripts\u002Fvector_inventory.py` | Redacted local vector\u002FGeoParquet technical inventory |\n| `scripts\u002Fcrs_reprojection_plan.py` | CRS units, axes, candidate transform and antimeridian plan |\n| `scripts\u002Fgeometry_validity_report.py` | Dry-run validity audit; optional repair to a new GeoPackage |\n| `scripts\u002Fspatial_join_audit.py` | Predicate semantics, duplicate IDs and join cardinality |\n| `scripts\u002Fexport_plan.py` | Non-executing vector\u002FGeoParquet export contract |\n| `scripts\u002Fsensitive_coordinates_checklist.py` | Privacy\u002Fgeneralization release gate |\n\n```bash\npython skills\u002Fgeopandas\u002Fscripts\u002Fvector_inventory.py --help\npython skills\u002Fgeopandas\u002Fscripts\u002Fcrs_reprojection_plan.py \\\n  --source-crs EPSG:4326 --target-crs EPSG:32631\npython skills\u002Fgeopandas\u002Fscripts\u002Fgeometry_validity_report.py data.gpkg\npython skills\u002Fgeopandas\u002Fscripts\u002Fspatial_join_audit.py points.gpkg zones.gpkg \\\n  --predicate within --left-id point_id --right-id zone_id\npython skills\u002Fgeopandas\u002Fscripts\u002Fexport_plan.py data.gpkg result.parquet \\\n  --format geoparquet --schema-version 1.0.0 \\\n  --stable-id-column feature_id --id-unique-verified\npython skills\u002Fgeopandas\u002Fscripts\u002Fsensitive_coordinates_checklist.py \\\n  --public-output --precise-points --contains-addresses\n```\n\n## Reference index\n\n- [Data structures](references\u002Fdata-structures.md)\n- [CRS management](references\u002Fcrs-management.md)\n- [Geometric operations](references\u002Fgeometric-operations.md)\n- [Spatial analysis](references\u002Fspatial-analysis.md)\n- [Data I\u002FO](references\u002Fdata-io.md)\n- [Visualization](references\u002Fvisualization.md)\n\n## Sources (verified 2026-07-23)\n\n- [GeoPandas 1.1.4 on PyPI](https:\u002F\u002Fpypi.org\u002Fproject\u002Fgeopandas\u002F1.1.4\u002F) — released 2026-06-26.\n- [GeoPandas 1.1.4 release](https:\u002F\u002Fgithub.com\u002Fgeopandas\u002Fgeopandas\u002Freleases\u002Ftag\u002Fv1.1.4) — bug-fix release.\n- [GeoPandas 1.1.4 tagged dependencies](https:\u002F\u002Fgithub.com\u002Fgeopandas\u002Fgeopandas\u002Fblob\u002Fv1.1.4\u002Fpyproject.toml).\n- [Stable GeoPandas documentation](https:\u002F\u002Fgeopandas.org\u002Fen\u002Fstable\u002F).\n- [GeoPandas 1.0 migration release](https:\u002F\u002Fgithub.com\u002Fgeopandas\u002Fgeopandas\u002Freleases\u002Ftag\u002Fv1.0.0).\n","# GeoPandas\n\nUse GeoPandas for planar vector data represented as pandas-like `GeoSeries` and\n`GeoDataFrame` objects. This skill targets stable **GeoPandas 1.1.4** (released\n2026-06-26), not the unreleased 1.2 documentation.\n\n## Reproducible environment\n\nGeoPandas 1.1.4 requires Python 3.10+; its tagged source requires NumPy >=1.24,\npandas >=2.0, Shapely >=2.0, pyproj >=3.5, pyogrio >=0.7.2, and `packaging`.\nThis exact Python 3.12 snapshot was smoke-tested on 2026-07-23:\n\n```bash\nuv venv --python 3.12\nuv pip install \\\n  \"geopandas==1.1.4\" \\\n  \"numpy==2.5.1\" \\\n  \"pandas==3.0.5\" \\\n  \"shapely==2.1.2\" \\\n  \"pyproj==3.7.2\" \\\n  \"pyogrio==0.13.0\" \\\n  \"pyarrow==25.0.0\" \\\n  \"packaging==26.2\"\n```\n\nKeep optional plotting and PostGIS packages pinned in the project lock as well.\nDo not mix binary geospatial packages from incompatible package channels.\n\n## Safety and privacy contract\n\n- Treat exact coordinates, addresses, parcel boundaries, trajectories, and\n  small-area joins as sensitive. Default reports to counts, categories, coarse\n  extents, and redacted identifiers. Generalize before publication.\n- Never automatically load a URL, cloud URI, GDAL `\u002Fvsi*` path, archive, or\n  geocode an address. Obtain explicit approval, validate provenance and hashes,\n  then stage an unpacked local file in an isolated workspace.\n- GDAL\u002FOGR drivers, GEOS, PROJ, pyogrio, Shapely, pyproj, and their wheels are a\n  native-code trust boundary. Prefer official wheels\u002Fconda-forge, record native\n  versions, restrict drivers, and process untrusted data in a sandbox.\n- Do not open macro-enabled office files or nested archives through permissive\n  GDAL drivers. The bundled CLIs use an extension allowlist and reject archives.\n- Read only named database secrets such as `GEOPANDAS_POSTGIS_PASSWORD`; use a\n  secret manager or scoped environment variable. Never embed a password in a\n  URL or source, print an engine\u002FURL, or dump the environment.\n- Every derived artifact needs source hashes\u002Fversions, CRS, operation parameters,\n  predicate, join cardinality, precision\u002Frepair choices, and row-count checks.\n\n## Correctness gates\n\nApply these gates before trusting a result:\n\n1. **Identity and provenance** — identify the source layer, stable feature key,\n   duplicate IDs, row count, geometry column, parser\u002Fdriver, and content hash.\n2. **Geometry state** — count null, empty, invalid, mixed, Z\u002FM, and collapsed\n   geometries separately. `None` is missing; an empty Shapely geometry is real.\n3. **CRS semantics** — require CRS metadata. `set_crs()` assigns metadata;\n   `to_crs()` transforms coordinates. Never guess a CRS from coordinate ranges.\n4. **Units and operation** — GeoPandas is planar. Geographic coordinates are\n   angular; do not use them directly for buffer, distance, area, nearest joins,\n   precision grids, or tolerances. Choose a fit-for-purpose local\u002Fequal-area CRS\n   or a geodesic method.\n5. **Transform quality** — inspect axis order, area of use, datum pipeline,\n   expected accuracy, ballpark status, and missing grids. Keep PROJ network\n   disabled unless the user explicitly approves grid retrieval.\n6. **Topology and precision** — validate before and after repair\u002Foverlay. Pick a\n   precision grid from source accuracy and CRS units; arbitrary snapping can\n   collapse features or create bias.\n7. **Cardinality** — state expected one-to-one, one-to-many, or many-to-many\n   behavior before `merge`, `sjoin`, or `sjoin_nearest`; audit unmatched and\n   multiplied rows afterward.\n8. **Output contract** — use a new output path, preserve a stable feature ID,\n   document schema\u002FCRS\u002Fencoding, reopen the artifact, and compare counts\u002Ftypes.\n\n## CRS and antimeridian rules\n\nGeoPandas stores CRS as `pyproj.CRS`. Coordinate arrays use traditional GIS\n`(x, y)` order, while authority definitions can advertise latitude-first axes.\nUse `Transformer(..., always_xy=True)` for explicit coordinate-array pipelines,\nand record that choice.\n\n`to_crs()` transforms vertices and assumes each segment is straight in the\nsource CRS; it does not transform geodesic arcs. Geometries crossing ±180° or a\nprojection boundary can be badly wrapped. Detect crossings, split\u002Funwrap and\ndensify in a documented geographic representation, transform parts, then\nvalidate. Do not use Web Mercator as a general measurement CRS.\n\n```python\ncrs = gdf.crs  # a pyproj.CRS when present\nif crs is None or crs.is_geographic:\n    raise ValueError(\"Choose a justified projected CRS before planar measurement\")\n\nunit_names = [axis.unit_name for axis in crs.axis_info]\nareas = gdf.geometry.area  # square CRS units, not automatically square metres\n```\n\nSee [CRS management](references\u002Fcrs-management.md).\n\n## Core API decisions\n\n### Data structures\n\n- A `GeoDataFrame` can hold multiple geometry columns, each with CRS metadata,\n  but only `active_geometry_name` drives frame-level spatial operations.\n- Binary `GeoSeries` methods are row-wise and align by index by default. Use\n  `align=False` only when positional pairing is explicitly intended and lengths\n  and order were verified.\n- Duplicate column names and duplicate feature IDs are ambiguous; reject or\n  resolve them before joins and exports.\n\nSee [data structures](references\u002Fdata-structures.md).\n\n### Geometry validity, precision, and union\n\nUse `is_valid` and redacted `is_valid_reason()` categories before\n`make_valid(method=\"linework\"|\"structure\", keep_collapsed=...)`. Repair can\nchange geometry type or dimension; retain the original and compare counts,\narea, types, empties, and collapsed parts.\n\n`set_precision(grid_size, mode=...)` uses **CRS units** and may remove duplicate\nvertices or collapse features. `union_all(method=\"unary\", grid_size=...)` is the\nrobust default. Use `coverage` only after `is_valid_coverage()` proves\nnon-overlap and edge matching; use `disjoint_subset` with Shapely >=2.1 when its\npartitioning assumption is useful.\n\nSee [geometric operations](references\u002Fgeometric-operations.md).\n\n### Joins, overlay, clip, and dissolve\n\n- `sjoin` predicates are directional: `left.within(right)` is not\n  `left.contains(right)`. `intersects` includes boundary contact; `contains`\n  excludes boundary-only points, while `covers` includes boundary points.\n- `predicate=\"dwithin\"` requires `distance`; scalar or per-left-row distances\n  are in CRS units. `sjoin_nearest` returns all equidistant nearest matches and\n  does **not** implement a `k=` parameter.\n- `overlay(..., make_valid=True)` repairs invalid input but can change types;\n  `keep_geom_type=None` drops other types with a warning. Precision mismatch can\n  create slivers; quantify them rather than silently deleting them.\n- `clip` dissolves the mask. Rectangle clipping is fast but possibly dirty and\n  may omit a line collapsed to a point; validate its output.\n- `dissolve` combines `groupby.agg` with `union_all`; choose explicit attribute\n  aggregations and audit null group keys.\n\nSee [spatial analysis](references\u002Fspatial-analysis.md).\n\n### I\u002FO, Arrow, and PostGIS\n\nGeoPandas 1.x defaults to pyogrio. Driver availability and semantics come from\nthe installed GDAL, not GeoPandas alone. Prefer local GeoPackage for general\ninterchange and WKB GeoParquet for columnar interoperability.\n\nGeoParquet defaults to stable schema 1.0.0. Native GeoArrow encodings and bbox\ncovering require schema 1.1.0 and remain less interoperable. A missing GeoParquet\n`crs` key means `OGC:CRS84`; explicit `crs: null` means unknown—do not conflate\nthem. Reopen and validate every export.\n\nUse parameterized SQL and a SQLAlchemy `Engine`\u002F`Connection` for PostGIS.\n`if_exists=\"replace\"` is destructive; default to `\"fail\"` and use a transaction.\n\nSee [data I\u002FO](references\u002Fdata-io.md).\n\n## Migration checklist\n\nFor code moving from GeoPandas 0.14 or earlier:\n\n- GeoPandas 1.0 supports Shapely >=2 only; PyGEOS, Shapely \u003C2, and the rtree\n  spatial-index backend were removed.\n- pyogrio replaced Fiona as the installed\u002Fdefault I\u002FO engine. Set `engine=`\n  explicitly and test schema, empty, datetime, encoding, and append behavior.\n- Replace `sjoin(op=...)` with `predicate=`, `sindex.query_bulk()` with\n  `sindex.query()`, `unary_union` with `union_all()`, and\n  `GeometryArray.data` with `to_numpy()`\u002F`np.asarray`.\n- Replace `read_file(include_fields=...|ignore_fields=...)` with `columns=`.\n  Use `schema_version=`, not the removed GeoParquet `version=` compatibility.\n- Do not use removed `geopandas.datasets`, internal `geopandas.io.*` entry\n  points, plot `axes`\u002F`colormap`, or set-operation operators.\n- `explode()` now defaults `index_parts=False`; a named Series passed to\n  `set_geometry()` supplies the new active-column name; a named right index can\n  replace `index_right` in `sjoin` output.\n- Do not assign `.crs` to override metadata or rely on deprecated\n  `set_geometry(drop=...)`; use explicit `set_crs()` and rename\u002Fdrop steps.\n- GeoPandas 1.1 requires Python >=3.10, pandas >=2.0, NumPy >=1.24, and pyproj\n  >=3.5. Version 1.1.2 fixed SQL injection through a PostGIS geometry-column\n  name; the pinned 1.1.4 includes that fix.\n\n### Plotting and exploration\n\nMaps are analytical outputs: label units, classification method, missing data,\nnormalization denominator, and date. `explore()` can expose every attribute in\ntooltips\u002Fpopups and contact tile\u002FCDN servers; generalize first and use\n`tiles=None`, `tooltip=False`, and `popup=False` for a local draft.\n\nSee [visualization](references\u002Fvisualization.md).\n\n## Bundled local CLIs\n\nAll helpers are deterministic, reject network\u002Farchive paths, bound input bytes\nand feature counts, keep imports lazy so `--help` is dependency-free, and emit\nJSON without coordinates or record identifiers.\n\n| CLI | Purpose |\n|---|---|\n| `scripts\u002Fvector_inventory.py` | Redacted local vector\u002FGeoParquet technical inventory |\n| `scripts\u002Fcrs_reprojection_plan.py` | CRS units, axes, candidate transform and antimeridian plan |\n| `scripts\u002Fgeometry_validity_report.py` | Dry-run validity audit; optional repair to a new GeoPackage |\n| `scripts\u002Fspatial_join_audit.py` | Predicate semantics, duplicate IDs and join cardinality |\n| `scripts\u002Fexport_plan.py` | Non-executing vector\u002FGeoParquet export contract |\n| `scripts\u002Fsensitive_coordinates_checklist.py` | Privacy\u002Fgeneralization release gate |\n\n```bash\npython skills\u002Fgeopandas\u002Fscripts\u002Fvector_inventory.py --help\npython skills\u002Fgeopandas\u002Fscripts\u002Fcrs_reprojection_plan.py \\\n  --source-crs EPSG:4326 --target-crs EPSG:32631\npython skills\u002Fgeopandas\u002Fscripts\u002Fgeometry_validity_report.py data.gpkg\npython skills\u002Fgeopandas\u002Fscripts\u002Fspatial_join_audit.py points.gpkg zones.gpkg \\\n  --predicate within --left-id point_id --right-id zone_id\npython skills\u002Fgeopandas\u002Fscripts\u002Fexport_plan.py data.gpkg result.parquet \\\n  --format geoparquet --schema-version 1.0.0 \\\n  --stable-id-column feature_id --id-unique-verified\npython skills\u002Fgeopandas\u002Fscripts\u002Fsensitive_coordinates_checklist.py \\\n  --public-output --precise-points --contains-addresses\n```\n\n## Reference index\n\n- [Data structures](references\u002Fdata-structures.md)\n- [CRS management](references\u002Fcrs-management.md)\n- [Geometric operations](references\u002Fgeometric-operations.md)\n- [Spatial analysis](references\u002Fspatial-analysis.md)\n- [Data I\u002FO](references\u002Fdata-io.md)\n- [Visualization](references\u002Fvisualization.md)\n\n## Sources (verified 2026-07-23)\n\n- [GeoPandas 1.1.4 on PyPI](https:\u002F\u002Fpypi.org\u002Fproject\u002Fgeopandas\u002F1.1.4\u002F) — released 2026-06-26.\n- [GeoPandas 1.1.4 release](https:\u002F\u002Fgithub.com\u002Fgeopandas\u002Fgeopandas\u002Freleases\u002Ftag\u002Fv1.1.4) — bug-fix release.\n- [GeoPandas 1.1.4 tagged dependencies](https:\u002F\u002Fgithub.com\u002Fgeopandas\u002Fgeopandas\u002Fblob\u002Fv1.1.4\u002Fpyproject.toml).\n- [Stable GeoPandas documentation](https:\u002F\u002Fgeopandas.org\u002Fen\u002Fstable\u002F).\n- [GeoPandas 1.0 migration release](https:\u002F\u002Fgithub.com\u002Fgeopandas\u002Fgeopandas\u002Freleases\u002Ftag\u002Fv1.0.0).\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25,"last-reviewed":26},"1.0.0","2026-07-23","main","e0956dc9606356ab78468936b502e55a365282e2","specialist-src\u002Fpublished-skills\u002Fgeopandas",0,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists","https:\u002F\u002Fgithub.com\u002Fmrsonord2240","2026-10-12 03:19:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add mrsonord2240\u002Fopenscience-specialists --skill geopandas",{"tool":40,"command":41},"bunx","bunx skills add mrsonord2240\u002Fopenscience-specialists --skill geopandas",{"tool":43,"command":44},"pnpm","pnpm dlx skills add mrsonord2240\u002Fopenscience-specialists --skill geopandas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002FSKILL.md",true,[48,54,58,62,66,70,74,80,84,88,92,96,100],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcrs-management.md","REFERENCE","参考文档",8882,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Freferences\u002Fcrs-management.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdata-io.md",12197,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Freferences\u002Fdata-io.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdata-structures.md",7611,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Freferences\u002Fdata-structures.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fgeometric-operations.md",9739,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Freferences\u002Fgeometric-operations.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fspatial-analysis.md",9840,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Freferences\u002Fspatial-analysis.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fvisualization.md",8665,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Freferences\u002Fvisualization.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002F_common.py","SCRIPT","脚本",21323,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002F_common.py",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fcrs_reprojection_plan.py",7420,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002Fcrs_reprojection_plan.py",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fexport_plan.py",11098,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002Fexport_plan.py",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fgeometry_validity_report.py",7436,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002Fgeometry_validity_report.py",{"path":93,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fsensitive_coordinates_checklist.py",8980,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002Fsensitive_coordinates_checklist.py",{"path":97,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fspatial_join_audit.py",12848,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002Fspatial_join_audit.py",{"path":101,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fvector_inventory.py",4488,"https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialist-src\u002Fpublished-skills\u002Fgeopandas\u002Fscripts\u002Fvector_inventory.py",[105,113,120,127,134,141],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7CW36A6QAGWFE2C008M1XPG","bio-workflows-metabolomics-pipeline","Orchestrates the untargeted LC-MS metabolomics pipeline end-to-end (xcms 4.x feature extraction, QC\u002Fdrift\u002Fnormalization, confidence-stratified annotation, permutation-validated statistics, background-aware pathway mapping), naming what each stage decides and where it silently fails. Use when running a full LC-MS metabolomics study from raw mzML to enriched pathways and needing the honest handoffs between stages. Each stage defers to its component skill for parameters and traps; for stable-isotope flux (a separate branch, not this untargeted flow) see metabolomics\u002Fisotope-tracing.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-workflows-metabolomics-pipeline\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7CW2Y18623NA2S1Y30FRQW1","bio-metabolomics-xcms-preprocessing","Programmatic untargeted LC-MS feature extraction in R with the modern xcms 4.x MsExperiment\u002FXcmsExperiment API, taking raw mzML to a feature table via CentWave peak detection, retention-time alignment, peak-density correspondence, gap-filling, CAMERA redundancy collapse, and built-in QC feature filtering. Use when converting centroided LC-MS runs into a features-by-samples matrix and deciding centWave\u002Fgrouping\u002Falignment parameters. For drift correction and QC\u002FCV filtering execution see metabolomics\u002Fnormalization-qc; for metabolite identification see metabolomics\u002Fmetabolite-annotation; for the MS-DIAL GUI alternative with MS2Dec deconvolution see metabolomics\u002Fmsdial-preprocessing; for downstream statistics see metabolomics\u002Fstatistical-analysis.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-xcms-preprocessing\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7CW2M364HVWPNQEKE2WP4PP","bio-metabolomics-statistical-analysis","Decision-grade statistical analysis for metabolomics intensity tables. Covers transformation and scaling (Pareto vs unit-variance as a hidden hypothesis), unsupervised structure (PCA\u002FHCA for QC), permutation-validated PLS-DA\u002FOPLS-DA (R2 vs Q2, double CV, VIP as heuristic), univariate testing (Welch\u002FMann-Whitney\u002FANOVA\u002FLMM with covariate adjustment), and dependence-aware multiple testing. Use when testing which metabolites differ, building or validating a discriminant model, choosing a scaling, or correcting many correlated tests. For sample-wise normalization\u002Fdrift correction see metabolomics\u002Fnormalization-qc; for ML classifiers and selection-inside-CV leakage see machine-learning\u002Fbiomarker-discovery and machine-learning\u002Fmodel-validation; for pathway interpretation see metabolomics\u002Fpathway-mapping; for design\u002Fpower\u002Fmultiplicity regime see experimental-design\u002Fmultiple-testing.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-statistical-analysis\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7CW2BCBF851WYE03Z8XPEDQ","bio-metabolomics-pathway-mapping","Maps metabolomics results to biological pathways via over-representation (ORA), metabolite-set enrichment (MSEA\u002FQEA), mummichog\u002FPSEA on raw m\u002Fz peaks, and network-diffusion enrichment (FELLA), with correct background-set construction and honest interpretive ceilings. Use when interpreting differential metabolites or an untargeted LC-MS feature table in pathway context, choosing ORA vs MSEA vs mummichog vs topology, or setting the reference\u002Fbackground set. For annotation confidence levels feeding ORA see metabolomics\u002Fmetabolite-annotation; for gene-set concepts see pathway-analysis\u002Fgo-enrichment and pathway-analysis\u002Fgsea; for joint gene+metabolite pathways see multi-omics-integration\u002Fmofa-integration.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-pathway-mapping\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7CW21NSZMCPMF7D9CHJM718","bio-metabolomics-normalization-qc","Designs QC, corrects signal drift, removes batch effects, filters features, normalizes samples, and imputes missing values for untargeted LC-MS\u002FGC-MS metabolomics, framing each step as a measurement model that can create or erase biological signal. Use when processing a peak\u002Ffeature table before statistical analysis, choosing a drift-correction or sample-normalization method, deciding QC RSD vs D-ratio filtering, or handling left-censored missing values. The feature table is produced by metabolomics\u002Fxcms-preprocessing or metabolomics\u002Fmsdial-preprocessing; transformation\u002Fscaling for modeling defers to metabolomics\u002Fstatistical-analysis; cross-study design issues link to experimental-design\u002Fbatch-design.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-normalization-qc\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7CW1SWVM0NYHVE6Q7MA3G7R","bio-metabolomics-msdial-preprocessing","Runs the MS-DIAL preprocessing workflow (peak picking, MS2Dec spectral deconvolution, alignment, gap-filling) and imports the alignment-result table into R or Python with honest filtering. Use when preprocessing LC-MS DDA\u002FDIA (SWATH) or GC-MS raw data with MS-DIAL, deciding MS-DIAL vs XCMS, configuring the MSDIALCUI console run, or parsing an MS-DIAL export into a clean feature matrix. For programmatic R peak detection and the feature-table-as-artifact framing see metabolomics\u002Fxcms-preprocessing; for lipid annotation mode see metabolomics\u002Flipidomics; for MSI-level confidence honesty see metabolomics\u002Fmetabolite-annotation; for drift correction and QC see metabolomics\u002Fnormalization-qc.","https:\u002F\u002Fgithub.com\u002Fmrsonord2240\u002Fopenscience-specialists\u002Fblob\u002Fmain\u002Fspecialists\u002Funtargeted-metabolomics-analyst\u002Fversions\u002F1.0.0\u002Fpackage\u002Fskills\u002Fbio-metabolomics-msdial-preprocessing\u002FSKILL.md",[],[]]