GIS type and function execution boundaries

Baseline: v4.2.5. GIS types/functions already have reference pages; introduction and tutorials also deserve independent entry points.

Representation and constraints

Geometry payloads use WKB; subtype/SRID travel in type metadata rather than necessarily in ordinary WKB bytes. GEOMETRY and GEOMETRY32 differ in coordinate precision. Binding, casting, ingestion and client output participate in conversion.

DDL/expression binding → subtype/SRID → WKT/WKB input → geometry payload
    → ST function type/coordinate path → scalar/geometry result → protocol representation

Coordinate systems

SRID 0 uses Cartesian coordinates with input-defined units. SRID 4326 uses longitude/latitude paths; consult individual functions for distance/area units. The GEOGRAPHY alias default does not establish full PostGIS Geography semantics. Distance support does not establish geodetic predicate support.

Invariant: geometry, type metadata and function coordinate paths must agree. Relabeling SRID is not coordinate transformation. Float32 precision affects boundary/distance checks.

Execution and performance

MBR filtering differs from exact predicates; ST function usage does not prove a spatial index. Inspect scans and function calls within filters/JOINs. Test invalid geometry, NULL, subtype/SRID mismatch and boundary points separately.

Use fixed geometries, expected Contains/Covers boundary behavior and units. SQL type support does not certify every driver’s binary I/O; validate WKT/WKB/GeoJSON representations separately.

See GIS capabilities, types and functions.

Source and regression entry points