一键导入
carto-find-spatial-data
Discover and subscribe to external spatial datasets via CARTO Data Observatory and partner catalogs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Discover and subscribe to external spatial datasets via CARTO Data Observatory and partner catalogs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Author, edit, publish, and validate CARTO Builder maps via the `carto maps` CLI. Use when the user wants to create a map from a natural-language request, edit an existing map (datasets, layers, styling, privacy, popups, widgets, SQL parameters), duplicate one, upload custom marker icons, or wire up an AI agent on a map. Covers the full `carto maps` subcommand surface — `list`, `get`, `create`, `update`, `delete`, `publish`, `validate`, `schema`, `agents`, `markers`, `screenshot`, `datasets update`.
Start here for first-time CARTO use — install the CLI, authenticate, switch profiles, understand JSON output and async job patterns. Also orients on the two parallel access paths into the CARTO platform (CLI for authoring/scripting, MCP server for inline interactions in chat hosts) and which skills cover each.
Administer the CARTO org — users, roles, quotas, activity audit, and bulk resource operations.
Write spatial SQL against the connected warehouse — dialect-specific guidance, performance defaults, and CARTO's query/job execution model.
Generate a working geospatial app powered by CARTO and deck.gl — basemap, layers (vector / H3 / quadbin / raster), widgets, filters, legend, inputs, optional chat-with-map agent, and the right auth strategy (public token, OAuth, SSO, or M2M).
Render an ad-hoc interactive map inline in the chat from a deck.gl declarative spec via the CARTO MCP server's view_map tool. Use whenever the user asks to map, visualize, or show the geographic distribution of points, polygons, hexagons, quadbins, clusters, density (heatmaps), or raster — and the map is exploratory or throwaway, not meant to be saved as a permanent CARTO Builder map. Triggers on "show me X on a map", "visualize Y", "make a heatmap of Z", "render the points/clusters/raster of W". Distinct from carto-create-builder-maps (CLI authoring of permanent maps), carto-preview-builder-map (loading an existing saved Builder map), and carto-develop-app (writing a from-scratch deck.gl app in TypeScript / JavaScript).
| name | carto-find-spatial-data |
| description | Discover and subscribe to external spatial datasets via CARTO Data Observatory and partner catalogs. |
| license | MIT |
The CARTO Data Observatory (DO) is a catalog of curated external spatial datasets — demographics, points of interest, environmental data, mobility, financial — that you can subscribe to and have materialized into your own data warehouse. Instead of the user hunting down a US census shapefile, this skill answers: "what's already curated in the DO that would help here?"
This skill covers discovery and subscription. Once subscribed, the data lives in the user's warehouse and is queryable like any other table — see carto-query-datawarehouse.
If the user already has the dataset in their warehouse, jump to carto-explore-datawarehouse instead — DO is for sourcing new external data.
# Discover what's available — by keyword
carto do search --keyword "census" --json
carto do search --keyword "weather" --country usa --json
# Inspect a specific dataset
carto do get <dataset-id> --json
# List your active subscriptions
carto do subscriptions list --json
# Subscribe (writes to a connection in your org)
carto do subscribe <dataset-id> \
--connection carto_dw \
--destination my_project.do.census_tracts
The exact
carto dosubcommand surface is evolving —search,get,subscribe,subscriptionsare the stable verbs. Checkcarto do --helpif a flag isn't recognized.
| Topic | Reference |
|---|---|
| Discovery: searching, filtering, evaluating datasets | references/data-observatory.md |
| Subscribing: paid vs free, materialization, refresh, costs | references/subscribe.md |
carto do get shows the licensing and pricing tier.carto-manage-platform.carto do get first. The dataset's metadata reveals coverage (US-only, EU-only, global), update cadence (monthly, yearly, real-time), and licensing — all critical to whether it actually fits the user's question.carto-explore-datawarehouse/references/named-sources.md) are the user's saved queries; DO is the curated catalog of third-party data.