feat: add geometry column settings in map settings - #815

Allow WKB columns in geometry selectors

When the dataset schema is inspected from ST_AsWKB(...)/generated point transforms, the geometry output column is reported as BLOB (and ST_AsText(...) as VARCHAR), not GEOMETRY. Filtering the new Geometry selector to only isColumnGeometry therefore hides the valid geom, __sqlrooms_geom, source_geom, and target_geom columns that existing WKB map configs rely on; before this change those selectors used the unfiltered column list, so users could select or repair these bindings.

Useful? React with 👍 / 👎.

Do not reuse generated lon/lat geometry for WKB mode

For a lon/lat-generated point map, activeLayerDataset.geometryColumn is the generated __sqlrooms_geom created by the transform, but this WKB-mode branch also replaces the dataset source with a bare table source below, so that generated column no longer exists. On tables that have both lon/lat and a real WKB geometry column, toggling to “Geometry Column (WKB)” leaves the map and fit config pointing at a missing generated column instead of the native geometry column until the user manually fixes it.

Useful? React with 👍 / 👎.

Convert DuckDB GEOMETRY before marking it as WKB

When the selected column is a DuckDB GEOMETRY column (the type this new Geometry selector allows), this branch stores the raw table as the source while forcing geometryEncodingHint: 'wkb'. DuckDB spatial GEOMETRY values are not standard WKB—the existing decoder path tells callers to use ST_AsWKB/ST_AsText first—so switching to this mode for a native geometry table makes dataset preparation fail unless the source includes a conversion transform.

Useful? React with 👍 / 👎.

Preserve qualified table identity in WKB mode

In this branch sourceDataTable.tableName is always used because that deprecated field is required, so the getTableIdentity(sourceDataTable.table) fallback is effectively unreachable. For a selected table outside the default schema/catalog (or when duplicate table names exist), switching to WKB mode rewrites the dataset source to an unqualified table name and can query the wrong relation or fail, unlike the regenerate path that preserves the qualified table reference.

Useful? React with 👍 / 👎.

Avoid creating an empty dataset id without an active layer

When the settings panel is open for an empty map that still has a selected table, activeLayerDatasetId is undefined but this control is still rendered. Choosing “Geometry Column (WKB)” then writes a dataset under the empty-string key and fitToData.dataset: '' without creating any layer, leaving the map in an invalid/unrenderable state instead of seeding a normal dataset-backed layer like the lat/long regenerate path does.

Useful? React with 👍 / 👎.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Fragile 'wkb' config construction: unsafe dataset key, hardcoded fallback column, dropped transformSql.

Several issues in the hand-rolled config update when switching to WKB mode:

• Line 61/73: activeLayerDatasetId ?? '' silently writes to datasets['']/fitToData.dataset: '' when there's no active dataset (e.g., no layer yet), producing an orphaned config entry instead of failing safely.
• Line 56: falls back to the literal 'geom' column name with no check that such a column exists, unlike regenerateMapConfigForTable/createDeckMapConfigForTable, which resolve real columns from the table.
• Lines 65-69: source: {tableName: ...} replaces the whole source object, dropping any existing transformSql on activeLayerDataset.source.

       if (value === 'wkb') {
+        if (!activeLayerDatasetId) return;
         // Switch to WKB mode - regenerate config with geometry column
-        const geometryColumn = activeLayerDataset?.geometryColumn ?? 'geom';
+        const geometryColumn =
+          activeLayerDataset?.geometryColumn ??
+          sourceDataTable.columns.find((c) => isColumnGeometry(c.type))?.name ??
+          'geom';
         onConfigChange({
           ...mapConfig,
           datasets: {
             ...mapConfig.datasets,
-            [activeLayerDatasetId ?? '']: {
+            [activeLayerDatasetId]: {
               ...activeLayerDataset,
               geometryColumn,
               geometryEncodingHint: 'wkb',
               source: {
+                ...(activeLayerDataset?.source as Record<string, unknown> | undefined),
                 tableName:
                   sourceDataTable.tableName ??
                   getTableIdentity(sourceDataTable.table),
               },
             },
           },
           fitToData: {
-            dataset: activeLayerDatasetId ?? '',
+            dataset: activeLayerDatasetId,
             geometryColumn,

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/deck/src/MapGeometrySettings.tsx` around lines 52 - 82, Harden
handleGeometryModeChange when switching to WKB: return without updating config
if activeLayerDatasetId is missing, and resolve the geometry column from
sourceDataTable using isColumnGeometry instead of defaulting to “geom”. Preserve
the existing activeLayerDataset.source fields, including transformSql, while
updating only tableName and geometry-related settings; keep datasets and
fitToData keyed by the validated dataset ID.