//! Shared DataFusion `SessionContext` factory for pipeline SQL execution.
//!
//! The transform (reshape) context is pre-registered with geodatafusion's spatial functions so
//! pipeline SQL steps run native PostGIS-style `ST_*` — `ST_Contains` / `ST_Distance` / `ST_Area` /
//! `ST_GeomFromText` / `ST_Point` / … — over real geometry (geoarrow), instead of string/GeoJSON
//! juggling. The same registration is reused by the datafusion-postgres serving surface
//! so a PG-wire client sees the identical function catalogue.
use SessionContext;
/// A fresh `SessionContext` with geodatafusion's `ST_*` UDFs registered (measurement, relationships,
/// processing, constructors, WKT/WKB I/O, geohash). Use this anywhere pipeline SQL executes.