Credential Fixture Review
python scripts/_secrets_inline.py is review material for the GeoJSON skill. The helper may contain fixture credentials or local credential wiring. Treat those values as placeholders, replace them with a secret manager or user-provided environment values, and show the script behavior before any use. Do not contact external services with embedded sample credentials.
GeoJSON
Use this skill for practical GeoJSON inspection and validation.
This skill focuses on safe read-only analysis of GeoJSON structure and coordinates. For deterministic GIS conversion, reprojection, clipping, or raster/vector processing on files, hand off to qgis.
What This Skill Does
- Validate whether a JSON file or payload is plausible GeoJSON.
- Summarize top-level type, feature count, geometry types, and bbox.
- Flag obvious coordinate-range issues for longitude/latitude style data.
- Explain common GeoJSON mistakes such as malformed
FeatureCollection, missing geometry, or wrong coordinate nesting.
- Recommend when
EPSG:4326 assumptions are safe and when CRS clarification is required.
Standard Workflow
- Confirm whether the input is a file path or inline JSON.
- Parse the JSON and identify the top-level GeoJSON type.
- Count features and geometry types.
- Compute bbox from coordinates when possible.
- Flag likely coordinate problems:
- out-of-range longitude/latitude
- swapped
lat,lon vs lon,lat
- mixed geometry structures
- If the user needs file transformation, reprojection, or editing, switch to
qgis.
Practical Commands
Summarize a GeoJSON file
python3 {baseDir}/scripts/geojson_tool.py summary --file ./data/sample.geojson
Validate a GeoJSON file
python3 {baseDir}/scripts/geojson_tool.py validate --file ./data/sample.geojson
Summarize inline GeoJSON
python3 {baseDir}/scripts/geojson_tool.py summary --json '{"type":"Point","coordinates":[116.4074,39.9042]}'
Decision Rules
- Assume GeoJSON coordinates are
lon,lat when they represent geographic positions unless the source clearly says otherwise.
- Do not assume every GeoJSON file is WGS84 just because it is GeoJSON; verify source context if precision matters.
- GeoJSON CRS metadata is effectively absent in modern practice; prefer explicit prose in the answer when CRS is uncertain.
- If distance or area analysis is needed, recommend reprojection to a projected CRS before measurement.
- Treat malformed but parseable data as suspect; report the issue instead of silently guessing.
What To Return
- Top-level GeoJSON type.
- Feature count when applicable.
- Geometry type counts.
- Bounding box when coordinates are present.
- A short note about likely CRS/coordinate-order assumptions.
- Specific validation errors or suspicious patterns when found.
When Not To Use
- Reverse geocoding or coordinates-to-address lookup: use
geocode.
- WGS84-specific CRS reasoning: use
wgs84.
- Deterministic GIS processing, conversion, reprojection, or clipping: use
qgis.
- CesiumJS rendering logic: use
cesium.
OpenClaw + ClawHub Notes
- Keep examples generic and portable.
- Do not hardcode private datasets, machine paths, or secrets.
- For clawhub.ai publication, keep examples standards-based and version/changelog updates semver-driven.
Reference Docs In This Skill
- Read
{baseDir}/references/geojson-notes.md for common structures, nesting rules, and failure cases.
1---2name: geojson-63description: Inspect, validate, summarize, and troubleshoot GeoJSON files and payloads, including FeatureCollection checks, geometry counting, bbox generation, coordinate range review, and CRS-related safety guidance. Use when the user asks about GeoJSON, FeatureCollection, geometry validity, 坐标范围检查, bbox, GeoJSON summary, or GeoJSON debugging.4---56789### Credential Fixture Review1011`python scripts/_secrets_inline.py` is review material for the `GeoJSON` skill. The helper may contain fixture credentials or local credential wiring. Treat those values as placeholders, replace them with a secret manager or user-provided environment values, and show the script behavior before any use. Do not contact external services with embedded sample credentials.1213# GeoJSON1415Use this skill for practical GeoJSON inspection and validation.1617This skill focuses on safe read-only analysis of GeoJSON structure and coordinates. For deterministic GIS conversion, reprojection, clipping, or raster/vector processing on files, hand off to `qgis`.1819## What This Skill Does2021- Validate whether a JSON file or payload is plausible GeoJSON.22- Summarize top-level type, feature count, geometry types, and bbox.23- Flag obvious coordinate-range issues for longitude/latitude style data.24- Explain common GeoJSON mistakes such as malformed `FeatureCollection`, missing `geometry`, or wrong coordinate nesting.25- Recommend when `EPSG:4326` assumptions are safe and when CRS clarification is required.2627## Standard Workflow28291. Confirm whether the input is a file path or inline JSON.302. Parse the JSON and identify the top-level GeoJSON type.313. Count features and geometry types.324. Compute bbox from coordinates when possible.335. Flag likely coordinate problems:34 - out-of-range longitude/latitude35 - swapped `lat,lon` vs `lon,lat`36 - mixed geometry structures376. If the user needs file transformation, reprojection, or editing, switch to `qgis`.3839## Practical Commands4041### Summarize a GeoJSON file4243```bash44python3 {baseDir}/scripts/geojson_tool.py summary --file ./data/sample.geojson45```4647### Validate a GeoJSON file4849```bash50python3 {baseDir}/scripts/geojson_tool.py validate --file ./data/sample.geojson51```5253### Summarize inline GeoJSON5455```bash56python3 {baseDir}/scripts/geojson_tool.py summary --json '{"type":"Point","coordinates":[116.4074,39.9042]}'57```5859## Decision Rules6061- Assume GeoJSON coordinates are `lon,lat` when they represent geographic positions unless the source clearly says otherwise.62- Do not assume every GeoJSON file is WGS84 just because it is GeoJSON; verify source context if precision matters.63- GeoJSON CRS metadata is effectively absent in modern practice; prefer explicit prose in the answer when CRS is uncertain.64- If distance or area analysis is needed, recommend reprojection to a projected CRS before measurement.65- Treat malformed but parseable data as suspect; report the issue instead of silently guessing.6667## What To Return6869- Top-level GeoJSON type.70- Feature count when applicable.71- Geometry type counts.72- Bounding box when coordinates are present.73- A short note about likely CRS/coordinate-order assumptions.74- Specific validation errors or suspicious patterns when found.7576## When Not To Use7778- Reverse geocoding or coordinates-to-address lookup: use `geocode`.79- WGS84-specific CRS reasoning: use `wgs84`.80- Deterministic GIS processing, conversion, reprojection, or clipping: use `qgis`.81- CesiumJS rendering logic: use `cesium`.8283## OpenClaw + ClawHub Notes8485- Keep examples generic and portable.86- Do not hardcode private datasets, machine paths, or secrets.87- For clawhub.ai publication, keep examples standards-based and version/changelog updates semver-driven.8889## Reference Docs In This Skill9091- Read `{baseDir}/references/geojson-notes.md` for common structures, nesting rules, and failure cases.
knownasnaffy