Worked example

Query a WKT CSV in the Browser

The example deliberately uses a WKT column with valid point text in every row, so it passes GeoLab's content-based detector without depending on a special column name.

Rows: 3 points
Geometry field: wkt text
Expected matches: 2 points
Predicate: ST_Within

1. Save the CSV

places.csvcsv

id,name,wkt
1,North Market,"POINT (-0.100 51.520)"
2,River Quarter,"POINT (-0.060 51.520)"
3,Outside,"POINT (-0.200 51.520)"

2. Import the file

Choose places.csv in GeoLab and keep the source name places. GeoLab samples the text fields, recognizes wkt as point geometry, and creates the local relation.

3. Filter the points

Return points inside a test polygonsql

SELECT
  id,
  name,
  ST_GeomFromText(wkt) AS geometry
FROM places
WHERE ST_Within(
  ST_GeomFromText(wkt),
  ST_GeomFromText(
    'POLYGON ((-0.15 51.50, -0.04 51.50, -0.04 51.54, -0.15 51.54, -0.15 51.50))'
  )
)
ORDER BY id;

4. Verify the result

id	name
1	North Market
2	River Quarter

NoteOutside is excluded because its longitude is west of the test polygon. The geometry alias is a native DuckDB GEOMETRY column, so the two rows render as points.

Limits to keep visible

The detector expects supported WKT with coordinates; EMPTY forms are not recognized.
EWKT SRIDs are not an automatic coordinate transformation step.
The CSV and query result remain session-only and are not written back to disk.

Sources and scope

These links document the product behavior summarized above. GeoLab-specific claims are limited to the current public v0.1.0 implementation.

GeoLab WKT detectionImplemented text sampling and supported WKT families.
DuckDB Spatial functionsOfficial reference for geometry constructors, predicates, and measurements.