Skip to content

Comments

feat(bigquery): add PEERDB_BIGQUERY_GEO_MAKE_VALID#3918

Open
lukejudd-lux wants to merge 1 commit intoPeerDB-io:mainfrom
lukejudd-lux:feature/bigquery-geo-make-valid
Open

feat(bigquery): add PEERDB_BIGQUERY_GEO_MAKE_VALID#3918
lukejudd-lux wants to merge 1 commit intoPeerDB-io:mainfrom
lukejudd-lux:feature/bigquery-geo-make-valid

Conversation

@lukejudd-lux
Copy link
Contributor

@lukejudd-lux lukejudd-lux commented Feb 12, 2026

Resolves #3920

feat(bigquery): add PEERDB_BIGQUERY_GEO_MAKE_VALID dynamic setting for ST_GEOGFROMTEXT

BigQuery uses S2 geometry which has stricter validity rules than GEOS/PostGIS. Geometries that are valid in PostGIS can fail to load into BigQuery due to S2 edge intersection checks.

This adds a configurable setting that passes make_valid => TRUE to ST_GEOGFROMTEXT during CDC merge and initial load, allowing BigQuery's S2 engine to repair geometries on ingest.

Defaults to false (no behaviour change for existing mirrors).

…r ST_GEOGFROMTEXT

BigQuery uses S2 geometry which has stricter validity rules than
GEOS/PostGIS. Geometries that are valid in PostGIS can fail to load
into BigQuery due to S2 edge intersection checks.

This adds a per-mirror configurable setting that passes
make_valid => TRUE to ST_GEOGFROMTEXT during CDC merge and initial
load, allowing BigQuery's S2 engine to repair geometries on ingest.

Defaults to false (no behavior change for existing mirrors).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BigQuery: Add make_valid option for ST_GEOGFROMTEXT during geo column loading

1 participant