Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    geojson geometry safety reviewer

    1

    Find GeoJSON geometry, CRS and polygon errors before they reach production.

    Free

    1 useSecurity scanned
    geojson geometry safety reviewer

    geojson geometry safety reviewer

    Example session with this skill installed

    Review this GeoJSON polygon for a web mapping API: {"type": "Polygon", "coordinates": [[[ -122.4, 37.7 ], [ -122.5, 37.7 ], [ -122.5, 37.8 ], [ -122.4, 37.7 ]]]}

    • Read your context and instructions
    • Compiled the geojson geometry safety

    The provided GeoJSON has been reviewed against RFC 7946 standards. The geometry fails basic linear ring requirements due to insufficient vertices.

    Verdict: FAIL

    Contract Detected

    • Format: GeoJSON (RFC 7946)
    • CRS: EPSG:4326 (Default)
    • Coordinate Order: [Longitude, Latitude]
    • Geometry Type: Polygon
    • Dimensions: 2D

    Findings

    • Severity: Critical
    • Location: coordinates[0]
    • Violated Rule: LinearRing must contain at least four positions.
    • Impact: Map renderers and spatial databases (PostGIS) will reject this geometry as invalid.
    • Minimal Correction: Add a fourth coordinate to close the triangle properly.

    Geometry Checklist

    CheckStatusNotes
    StructurePASSValid JSON Polygon nesting
    Coordinate OrderPASSCorrect [Lon, Lat] for San Francisco area
    Ring ClosureFAILStart and End match, but only 3 positions provided
    NestingPASSSingle exterior ring
    OrientationPASSCounter-clockwise winding
    CRSPASSNo legacy CRS member detected
    Z/MN/ANo third/fourth ordinates
    TopologyFAILTriangle requires 4 points (3 distinct + closure)

    Unproven Assumptions

    • The source data intended to represent a simple triangle.
    • The coordinate values correctly represent the intended geographic location.

    Next steps

    1. Update the coordinate array to include the missing vertex: [[-122.4, 37.7], [-122.5, 37.7], [-122.5, 37.8], [-122.4, 37.7]].
    2. Verify the geometry in a linting tool or via ST_IsValid in PostGIS.
    3. Test the API consumer's behavior when receiving a 3-point Polygon to ensure graceful failure.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Review GeoJSON with a GIS-aware agent before invalid coordinates, polygons or CRS assumptions reach your database or production API.

    This skill teaches your AI coding agent to review RFC 7946 GeoJSON as spatial data rather than ordinary JSON. It detects common but costly GIS mistakes such as reversed longitude/latitude, invalid or open polygon rings, incorrect Polygon vs MultiPolygon structures, CRS confusion, unsafe Z/M assumptions and geometries that look correct on a map but are not actually valid.

    It is useful when building or reviewing geospatial APIs, PostGIS applications, OpenLayers integrations, imports, geometry editors and spatial validation pipelines.

    What it checks

    • RFC 7946 longitude/latitude order
    • Polygon and MultiPolygon structure
    • Ring closure and minimum vertex requirements
    • Exterior rings and holes
    • CRS and projection mistakes
    • ST_SetSRID vs ST_Transform misuse
    • Z/M dimensional assumptions
    • Bounding-box semantics
    • Topology risks and invalid geometry
    • Unbounded or unsafe GeoJSON API payloads

    The skill deliberately distinguishes closed geometry from valid geometry and never recommends silently repairing production data with ST_MakeValid.

    It produces a structured PASS / PASS WITH WARNINGS / FAIL review with findings, severity, corrections, unproven assumptions and recommended test cases.

    Works as a standalone skill and does not require OpenGeoForge.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    Cannot prove full topological validity without database tooling like ST_IsValid. Does not transform coordinates between systems. Source CRS must be explicitly stated or it remains unresolved.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed26 days ago

    What's inside

    Frequently Asked Questions

    This skill enforces strict RFC 7946 standards to prevent the "reversed coordinate" bug (latitude/longitude swap) and ensures Polygons are properly closed, preventing broken map renders and failed database inserts.

    The skill is designed to integrate with any LLM-based agent or workflow that processes JSON data, making it compatible with tools used for PostGIS migrations, Leaflet development, and Mapbox integrations.

    It validates GeoJSON structure, coordinate order, ring closure, and nesting; however, it is not a replacement for server-side functions like ST_IsValid for final production-grade topology proofs.

    You receive the full skill definition, including the 13-point inspection logic and the structured output template for PASS/FAIL verdicts, ready to be deployed in your AI workflow.

    Yes, the reviewer specifically identifies legacy Coordinate Reference System (CRS) members and flags them as warnings or failures to ensure your data remains portable across modern web mapping platforms.

    New in APIs & Backend

    Free