القائمة
Import geospatial files into the data warehouse via CARTO, export results back out, and prepare tilesets for fast map rendering.
التثبيت باستخدام 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-import-export-data |
| description | Import geospatial files into the data warehouse via CARTO, export results back out, and prepare tilesets for fast map rendering. |
| license | MIT |
Move data into the warehouse from local files / URLs (carto import), pull data out (carto activity export for usage data; warehouse-native unloads for everything else), and prepare tilesets for performant map rendering of large geospatial datasets.
If the user just wants to query a file already in the warehouse, jump to carto-query-datawarehouse. If they want to discover what's already there, carto-explore-datawarehouse.
# Import a local file
carto import --file ./data.csv \
--connection carto_dw \
--destination project.dataset.table
# Import from a URL
carto import --url https://example.com/data.geojson \
--connection carto_dw \
--destination my_project.demo.regions
# Async (return immediately, poll separately)
carto import --file ./big.parquet \
--connection carto_dw \
--destination my_project.demo.huge \
--async
# Overwrite existing table
carto import --file ./data.csv \
--connection carto_dw \
--destination my_project.demo.t \
--overwrite
| Topic | Reference |
|---|---|
carto import — flags, formats, size limits, async | references/imports.md |
| Tileset preparation for large maps | references/tilesets.md |
Exporting data: warehouse-native unloads vs activity export | references/exports.md |
--connection is the connection name (from connections list), not the warehouse project ID. If you only know the project, run carto connections list --json first to find the matching connection.--destination is the fully-qualified target name in the warehouse's syntax: project.dataset.table (BigQuery), DATABASE.SCHEMA.TABLE (Snowflake), schema.table (Postgres/Redshift), catalog.schema.table (Databricks), SCHEMA.TABLE (Oracle).--url to a presigned URL.--no-autoguessing skips column type detection — use it when you've prepared a precise schema and don't want CARTO to second-guess types (especially for columns that look numeric but should stay string, like ZIP codes).--async to return immediately. The CLI prints a job ID in async mode that you can use to check progress.