[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASAMP2HANKZFWN74JVM5B5":3,"skill-same:01M7ASAMP2HANKZFWN74JVM5B5":106},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M7ASAMP2HANKZFWN74JVM5B5","geopandas",null,"Guidance and local audit tools for Python workflows that directly use GeoPandas GeoSeries, GeoDataFrame, spatial operations, or vector-data I\u002FO.","nikhilesh-s\u002Fclaude-toolkit","nikhilesh-s","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F123913414?v=4","01M7ARX6NXB6DFY1CCP91599KE","Nikhilesh Suravarjjala","01M7ARX6PFTQKR6ME1K2S4AZ9K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\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\ncompatibility: Requires Python 3.10+ and uv. Bundled CLIs are local-only; runtime analysis requires the pinned GeoPandas stack below.\nallowed-tools: Read Write Bash Glob Grep\nmetadata:\n  version: \"1.1\"\n  skill-author: K-Dense Inc.\n  last-reviewed: \"2026-07-23\"\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,"allowed-tools":28,"compatibility":29},{"version":25,"skill-author":26,"last-reviewed":27},"1.1","K-Dense Inc.","2026-07-23","Read Write Bash Glob Grep","Requires Python 3.10+ and uv. Bundled CLIs are local-only; runtime analysis requires the pinned GeoPandas stack below.","nik-claude-toolkit","4feaa2876384b593d9e30d9190bc56985eeeeb8e","skills\u002Fgeopandas","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s","2026-10-22 14:30:58",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add nikhilesh-s\u002Fclaude-toolkit --skill geopandas",{"tool":42,"command":43},"bunx","bunx skills add nikhilesh-s\u002Fclaude-toolkit --skill geopandas",{"tool":45,"command":46},"pnpm","pnpm dlx skills add nikhilesh-s\u002Fclaude-toolkit --skill geopandas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002FSKILL.md",true,[50,56,60,64,68,72,76,82,86,90,94,98,102],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcrs-management.md","REFERENCE","参考文档",8882,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Freferences\u002Fcrs-management.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdata-io.md",12197,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Freferences\u002Fdata-io.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdata-structures.md",7611,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Freferences\u002Fdata-structures.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fgeometric-operations.md",9739,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Freferences\u002Fgeometric-operations.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fspatial-analysis.md",9840,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Freferences\u002Fspatial-analysis.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fvisualization.md",8665,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Freferences\u002Fvisualization.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002F_common.py","SCRIPT","脚本",21323,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002F_common.py",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fcrs_reprojection_plan.py",7420,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002Fcrs_reprojection_plan.py",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fexport_plan.py",11098,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002Fexport_plan.py",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fgeometry_validity_report.py",7436,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002Fgeometry_validity_report.py",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fsensitive_coordinates_checklist.py",8980,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002Fsensitive_coordinates_checklist.py",{"path":99,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fspatial_join_audit.py",12848,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002Fspatial_join_audit.py",{"path":103,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fvector_inventory.py",4488,"https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fgeopandas\u002Fscripts\u002Fvector_inventory.py",[107,114,122,129,136,143],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7AT8339CZMCRMRZP6G1R329","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7AT77E7JPH96ETQBNDVVYDM","video-use","Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvideo-use\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7AT6YVX000D73Q40SBPZYKP","venue-templates","Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Use when selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvenue-templates\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M7AT6SGGBENKX1G6V8V9G2MJ","vaex","Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV\u002FHDF5\u002FArrow\u002FParquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that do not fit in memory.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fvaex\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M7AT6HHDJ54MR4HDPFHJYR7G","usfiscaldata","Query the U.S. Treasury Fiscal Data REST API for federal financial data. No API key required. Use for national debt (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates, foreign exchange rates, savings bonds, or U.S. government revenue and spending statistics.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Fusfiscaldata\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M7AT662JFE4THBVAZBB3ANJD","uncertainty-and-units","Track physical units and propagate measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility checks using dimensionless groups (Reynolds, Peclet, Damkohler, Knudsen, Biot, Womersley), characteristic scales such as diffusion time or Debye length, and observed magnitude ranges. Trigger on \"is this number physically reasonable\", \"sanity check these units\", \"what regime is this flow in\", or a result that looks off by orders of magnitude.","https:\u002F\u002Fgithub.com\u002Fnikhilesh-s\u002Fclaude-toolkit\u002Fblob\u002Fnik-claude-toolkit\u002Fskills\u002Funcertainty-and-units\u002FSKILL.md",[],[]]