postgis-knowledge-patch

Document PostGIS 3.5 to 3.6 API changes and SFCGAL function renames.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill postgis-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postgis-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/postgis-knowledge-patch/skills/postgis-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill postgis-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude and other models are often trained on older PostGIS knowledge and can emit deprecated function names, incorrect raster behavior, and outdated topology assumptions; this Skill supplies concise changelog-driven guidance so generated SQL and migration steps match PostGIS 3.5–3.6 behavior and requirements.

Core Features & Use Cases

  • SFCGAL rename guidance: explains the ST_ to CG_ migration and lists new CG_ 3D and partitioning functions so AI-generated queries use correct names.
  • Breaking-change summaries: highlights behavior changes (ST_DFullyWithin, ST_GeneratePoints seeding, ST_Clip touched parameter, ST_TileEnvelope clipping, TIN/PolyhedralSurface accessors).
  • Raster & topology updates: documents ST_AsRasterAgg, ST_ReclassExact, ST_IntersectionFractions, topology bigint migration, and required version constraints for PostgreSQL, GEOS, Proj, and SFCGAL.
  • Practical use: load before authoring PostGIS SQL, upgrading databases, rebuilding materialized views, or generating migration scripts.

Quick Start

Load the postgis-knowledge-patch and ask for a summary of breaking changes, new functions, and migration steps relevant to my PostGIS SQL and upgrade path.

Frequently Asked Questions about postgis-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate SFCGAL ST_ functions to CG_ in PostGIS 3.6?

To migrate SFCGAL functions in PostGIS 3.6, replace deprecated ST_ prefixes with CG_ for 3D and partitioning operations. This ensures generated SQL matches current API behavior and avoids deprecated function errors during database upgrades.

What are the breaking changes in PostGIS 3.6?

Breaking changes in PostGIS 3.6 include behavior updates for ST_DFullyWithin, ST_GeneratePoints seeding, ST_Clip touched parameter, ST_TileEnvelope clipping, and TIN/PolyhedralSurface accessors. Reviewing these changes prevents unexpected query results and migration failures.

How do I perform a topology bigint migration in PostGIS?

Topology bigint migration in PostGIS requires updating topology schemas to support bigint data types. Following the PostGIS 3.6 changelog guidance ensures topology utilities function correctly and maintains data integrity during the migration process.

Why does my AI-generated PostGIS SQL use deprecated raster functions?

AI-generated PostGIS SQL uses deprecated raster functions because models are trained on older PostGIS knowledge. Applying updated API guidance ensures generated queries use current raster functions like ST_AsRasterAgg and ST_ReclassExact correctly.

When do I need to update PostGIS SQL for version 3.6 compatibility?

Update PostGIS SQL for version 3.6 compatibility when upgrading databases, rebuilding materialized views, or generating migration scripts. This ensures SQL aligns with new raster utilities, topology bigint migration, and SFCGAL CG_ function names.