postgis-skill

Optimize slow PostGIS SQL queries by applying indexing hints on geometry columns and refactoring spatial joins. Adding indexes to geometry columns speeds up functions like ST_Intersects, significantly improving query performance on large geospatial datasets.

Best practices for readable PostGIS SQL include following consistent naming conventions, adding clear comments to complex spatial logic, and structuring queries cleanly. These conventions reduce errors and make geospatial data workflows easier to maintain.

Debug complex spatial queries in PostGIS by applying targeted debugging techniques to isolate faulty geometry operations. Auditing spatial tables for missing indexes or malformed geometries helps identify and resolve performance bottlenecks effectively.

You need a spatial index for ST_Intersects in PostGIS when querying large geospatial datasets to prevent full table scans. Creating an index on the geometry column allows the database to quickly filter intersecting bounding boxes before executing exact geometry checks.

Yes, you can use this skill to audit existing spatial tables for missing comments on create statements and identify geometry columns lacking indexes. It provides actionable instructions to apply recommended changes for improved query clarity and performance.

A PostGIS query might ignore a geometry index due to malformed query syntax or missing spatial constraints. Reviewing query refactor strategies and applying proper indexing hints ensures the query planner utilizes the index for geospatial data retrieval.