Load ArcGIS data to DuckDB

The ArcGIS REST API provides a web service interface to interact with ArcGIS Server and ArcGIS Online resources including services, folders, and operations. Everything needed to build a working ArcGIS → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your ArcGIS to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from ArcGIS to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the ArcGIS API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

ArcGIS API at a glance

These values come from the ArcGIS API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the ArcGIS API?

ArcGIS REST APIs support token-based authentication. Tokens can be provided as a query parameter named 'token' or via HTTP headers: 'Authorization: Bearer ' or 'X-Esri-Authorization: Bearer '.

1. Get your credentials

1. Sign in to your portal dashboard (e.g., ArcGIS Location Platform at https://location.arcgis.com or ArcGIS Online at https://arcgis.com). 2. Navigate to Content > My content. 3. Click New item. 4. Select Developer credentials > API key credentials and click Next. 5. Configure the privileges, expiration date, and referrer restrictions as required. 6. Follow the prompts to generate the key. 7. Once created, click Generate the API key and copy the generated token to use in your application.

2. Add them to .dlt/secrets.toml

Copy
[sources.arcgis_source]
arcgis_api_key = "AAPK..."

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What ArcGIS data can I load into DuckDB?

These are the ArcGIS endpoints dlt can load into DuckDB:

---

How do I load only new ArcGIS records?

ArcGIS exposes start on search, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "search", "endpoint": {
    "path": "search",
    "data_selector": "results",
    "incremental": {"cursor_path": "start", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated ArcGIS pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading services and query from the ArcGIS API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def arcgis_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<host>/<context>/rest/services",
            "auth": {"type": "bearer", "token": token},
        },
        "resources": [
            {"name": "search", "endpoint": {"path": "search", "data_selector": "results"}},
            {"name": "features", "endpoint": {"path": "query", "data_selector": "features"}}
        ],
    }
    yield from rest_api_resources(config)


def load_arcgis_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="arcgis_pipeline",
        destination="duckdb",
        dataset_name="arcgis_data",
    )
    load_info = pipeline.run(arcgis_source())
    print(load_info)


if __name__ == "__main__":
    load_arcgis_to_duckdb()

Run it with python arcgis_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query ArcGIS data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("arcgis_pipeline").dataset()
df = data.query.df()
print(df.head())

SQL:

Copy
SELECT * FROM arcgis_data.query LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the ArcGIS to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw ArcGIS loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load ArcGIS data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack