You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: 'Get column names, types, sample values, and coded value lists for a dataset — formatted like SELECT * LIMIT 1 output. Also includes the read_parquet() path. **Call this before your first SQL query against a dataset.** Instant, no approval needed. For datasets outside your app, use `get_stac_details` instead.',
285
+
description: 'Get column names, types, sample values, and coded value lists for a dataset — formatted like SELECT * LIMIT 1 output. Also includes the read_parquet() path. **Call this before your first SQL query against a dataset.** For datasets outside your app, use `get_stac_details` instead.',
286
286
inputSchema: {
287
287
type: 'object',
288
288
properties: {
289
289
dataset_id: {type: 'string',description: 'Collection ID of the dataset'}
Copy file name to clipboardExpand all lines: app/system-prompt.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,8 @@ This applies equally when styling (e.g., building a `match` expression to color
50
50
51
51
The dataset catalog below lists `read_parquet()` paths for every pre-loaded dataset. **These paths are authoritative — never guess, construct, or modify S3 paths.** Use them directly in SQL.
52
52
53
+
**When a dataset has both a hex-indexed parquet path and a full GeoParquet path, prefer the hex path for SQL queries.** The hex path is partitioned by H3 cell and dramatically faster for spatial aggregations and joins. Asset titles make the distinction clear (e.g. `"SVI 2022 hex"` vs `"SVI 2022"`).
54
+
53
55
**Before your first SQL query against a dataset, call `get_schema(dataset_id)`.** It returns column names, types, representative values, and coded value lists — instant, no approval needed. You don't need to call it again for follow-up queries on the same dataset unless you're unsure about column names.
54
56
55
57
For datasets outside your app config, use `get_stac_details(collection_id)` instead.
0 commit comments