features: use the GeoPackage spatial index for spatial predicates by cportele · Pull Request #618 · ldproxy/xtraplatform-spatial

cportele · 2026-08-24T17:01:24Z

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele · 2026-08-24T17:01:24Z

Closesldproxy/ldproxy#1758.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row.

The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation:

only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT
only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery
only for a column that an R-Tree is known for, determined once per provider on startup
never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same

The changes also include a fix for another bug:

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

MinMaxDeriver seeded the maxima with Double.MIN_VALUE, which is the smallest positive value rather than the most negative one, so every Math.max against it won on an axis whose coordinates are all negative and the maximum stayed at 4.9E-324. Spatial extents are derived from this, so the extent of data west of Greenwich or south of the equator came out wrong.

A spatial predicate on a GPKG provider was encoded as a bare ST_Intersects(geom, ...). Unlike PostGIS, where ST_Intersects embeds the && bounding box operator and GiST applies by itself, SQLite cannot infer from a spatial operator that the R-Tree of the geometry column is relevant: unless the query names the rtree_<table>_<column> virtual table, the operator is evaluated for every row. The dialect now contributes a bounding box predicate over that table, added as a conjunct to the exact predicate. On a 41.6 GB GeoPackage with 24.6 million rows, a bbox request for ten features goes from 149 s to 0.3 s while returning the same features. The conjunct is only added where it is implied by the exact predicate, so that it can change neither the result nor the meaning of the predicate under negation: - only for operators whose match implies that the bounding boxes intersect, which excludes S_DISJOINT - only for a geometry column of the main table, since the semi-join form of a joined property would need the predicate inside its subquery - only for a column that an R-Tree is known for, determined once per provider on startup - never below a negation, because a NULL geometry has no entry in the R-Tree while the exact predicate is NULL for it, and negating those two is not the same The index is joined on the primary key of the feature table rather than on rowid. A GeoPackage feature table is required to have an INTEGER PRIMARY KEY, which SQLite makes an alias of rowid, but a file that does not follow that requirement would otherwise match the wrong rows.

…latform-spatial into gpkg-spatial-index

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

cportele added 4 commits August 24, 2026 12:25

Merge branch 'gpkg-spatial-index' ofhttps://github.com/ldproxy/xtrap…
05850ac
…latform-spatial into gpkg-spatial-index

cportele requested a review from azahnen as a code owner August 24, 2026 17:01

cportele mentioned this pull request Aug 25, 2026
fix the geometry of a column a sub-decoder derives from an expression #619
Merged

azahnen approved these changes Aug 25, 2026
View reviewed changes

azahnen merged commit be66382 into masterAug 25, 2026
3 checks passed

azahnen deleted the gpkg-spatial-index branch August 25, 2026 13:01

azahnen added a commit that referenced this pull request Sep 1, 2026
features: use the GeoPackage spatial index for spatial predicates (#618)
abeb0b4

Uh oh!

Conversation

cportele commented Aug 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cportele commented Aug 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cportele commented Aug 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cportele commented Aug 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cportele commented Aug 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cportele commented Aug 24, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation