Calculated field
SHAPETYPE(MAKEPOINT([lat],[lon]))
Sample data
| shipment | shipped | received | text | year | month | day | hour | minute | second | lat | lon | wkt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 2024-12-29 | 2024-12-29T16:25:40 | 2024-12-29 | 2025 | 2 | 25 | 9 | 25 | 40 | 10 | 106 | POINT (106 10) |
| 2 | 2024-12-30 | 2024-12-30T16:25:40 | 2024-12-30 | 2025 | 2 | 26 | 10 | 25 | 40 | 10.1 | 106.1 | POINT (106.1 10.1) |
| 3 | 2025-01-01 | 2025-01-01T16:25:40 | 2025-01-01 | 2025 | 2 | 27 | 11 | 25 | 40 | 10.2 | 106.2 | POINT (106.2 10.2) |
| 4 | 2025-01-31 | 2025-01-31T16:25:40 | 2025-01-31 | 2025 | 2 | 28 | 12 | 25 | 40 | 10.3 | 106.3 | POINT (106.3 10.3) |
| 5 | 2025-02-28 | 2025-02-28T16:25:40 | 2025-02-28 | 2025 | 2 | 29 | 13 | 25 | 40 | 10.4 | 106.4 | POINT (106.4 10.4) |
| 6 | 2025-03-15 | 2025-03-15T16:25:40 | 2025-03-15 | 2025 | 2 | 30 | 14 | 25 | 40 | 10.5 | 106.5 | POINT (106.5 10.5) |
| 7 | null | null | null | 2025 | 2 | 31 | 15 | 25 | 40 | 10.6 | 106.6 | POINT (106.6 10.6) |
| 8 | 2024-02-29 | 2024-02-29T16:25:40 | 2024-02-29 | 2025 | 2 | 32 | 16 | 25 | 40 | 10.7 | 106.7 | POINT (106.7 10.7) |
The same calculation as SQL
SELECT 'Point' AS result FROM input ORDER BY shipment
Runs the example above.
SELECT CASE WHEN ST_GEOMETRYTYPE(ST_MAKEPOINT(lon,lat))='ST_Point' THEN 'Point' ELSE ST_GEOMETRYTYPE(ST_MAKEPOINT(lon,lat)) END AS result FROM input ORDER BY shipment
Written for this dialect; not run here.
SELECT CASE WHEN ST_GEOMETRYTYPE(ST_GEOGPOINT(lon,lat))='ST_Point' THEN 'Point' ELSE ST_GEOMETRYTYPE(ST_GEOGPOINT(lon,lat)) END AS result FROM input ORDER BY shipment
Written for this dialect; not run here.
Result
| shipment | shipped | received | text | result |
|---|---|---|---|---|
| 1 | 2024-12-29 | 2024-12-29T16:25:40 | 2024-12-29 | Point |
| 2 | 2024-12-30 | 2024-12-30T16:25:40 | 2024-12-30 | Point |
| 3 | 2025-01-01 | 2025-01-01T16:25:40 | 2025-01-01 | Point |
| 4 | 2025-01-31 | 2025-01-31T16:25:40 | 2025-01-31 | Point |
| 5 | 2025-02-28 | 2025-02-28T16:25:40 | 2025-02-28 | Point |
| 6 | 2025-03-15 | 2025-03-15T16:25:40 | 2025-03-15 | Point |
| 7 | null | null | null | Point |
| 8 | 2024-02-29 | 2024-02-29T16:25:40 | 2024-02-29 | Point |
Same rows from the calculation and from the SQL in DuckDB.
Where a naive translation goes wrong
- The line shape label differs from the GeoJSON geometry type.
Naive SQL
SELECT 'LineString' AS result FROM input ORDER BY shipment
shipment shipped received text result 1 2024-12-29 2024-12-29T16:25:40 2024-12-29 LineString 2 2024-12-30 2024-12-30T16:25:40 2024-12-30 LineString 3 2025-01-01 2025-01-01T16:25:40 2025-01-01 LineString 4 2025-01-31 2025-01-31T16:25:40 2025-01-31 LineString 5 2025-02-28 2025-02-28T16:25:40 2025-02-28 LineString 6 2025-03-15 2025-03-15T16:25:40 2025-03-15 LineString 7 null null null LineString 8 2024-02-29 2024-02-29T16:25:40 2024-02-29 LineString Matches the calculation
SELECT 'Line' AS result FROM input ORDER BY shipment
shipment shipped received text result 1 2024-12-29 2024-12-29T16:25:40 2024-12-29 Line 2 2024-12-30 2024-12-30T16:25:40 2024-12-30 Line 3 2025-01-01 2025-01-01T16:25:40 2025-01-01 Line 4 2025-01-31 2025-01-31T16:25:40 2025-01-31 Line 5 2025-02-28 2025-02-28T16:25:40 2025-02-28 Line 6 2025-03-15 2025-03-15T16:25:40 2025-03-15 Line 7 null null null Line 8 2024-02-29 2024-02-29T16:25:40 2024-02-29 Line
Signature
SHAPETYPE(geometry)