MapServer Python API Docs | dltHub
Build a MapServer-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The MapScript API documentation for MapServer is available at https://mapserver.org/mapscript/mapscript-api/index.html. It details the MapScript interface generated by SWIG. The latest updates and proposals for the API can be found in the RFC documents. The REST API base URL is http://<host>/cgi-bin/mapserv/<map_alias>/ogcapi and MapServer OGC API has no built‑in authentication; optional token can be passed via query parameters or protected by web server/proxy..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading MapServer data in under 10 minutes.
What data can I load from MapServer?
Here are some of the endpoints you can load from MapServer:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| landing | ogcapi/ | GET | links | OGC API landing page (JSON or HTML) with links to capabilities |
| api | ogcapi/api?f=json | GET | (document) | API document / OpenAPI / conformance metadata |
| collections | ogcapi/collections?f=json | GET | collections | List of collections (layers) served by this mapfile |
| collection_items | ogcapi/collections/{collectionId}/items?f=json | GET | features | GeoJSON FeatureCollection for a collection (features array contains records) |
| collection_item | ogcapi/collections/{collectionId}/items/{featureId}?f=json | GET | (GeoJSON Feature) | Single feature (GeoJSON object) |
| conformance | ogcapi/conformance?f=json | GET | conformsTo | Conformance classes supported |
| collections_queryables | ogcapi/collections/{collectionId}/queryables?f=json | GET | properties | Queryable properties/fields for a collection |
How do I authenticate with the MapServer API?
MapServer OGC API normally requires no auth. You can add a query‑string token via ows_extra_params/oga_extra_params or enforce authentication at the web server or proxy level.
1. Get your credentials
- Determine the authentication method you will use (e.g., query‑string token or web‑server basic auth).
- If using a token, edit the mapfile or mapserver.conf and add an ows_extra_params entry, e.g., ows_extra_params "token=YOUR_TOKEN".
- Save the configuration and restart MapServer.
- If using web‑server authentication, configure the web server (Apache, Nginx, etc.) with the desired auth scheme and protect the /cgi-bin/mapserv/.../ogcapi path.
- Verify that requests include the token or that the server prompts for credentials.
2. Add them to .dlt/secrets.toml
[sources.mapserver_source] token = "your_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the MapServer API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python mapserver_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mapserver_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mapserver_data The duckdb destination used duckdb:/mapserver.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline mapserver_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads collections and collection_items from the MapServer API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def mapserver_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://<host>/cgi-bin/mapserv/<map_alias>/ogcapi", "auth": { "type": "none", "token": token, }, }, "resources": [ {"name": "collections", "endpoint": {"path": "ogcapi/collections?f=json", "data_selector": "collections"}}, {"name": "collection_items", "endpoint": {"path": "ogcapi/collections/{collectionId}/items?f=json", "data_selector": "features"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mapserver_pipeline", destination="duckdb", dataset_name="mapserver_data", ) load_info = pipeline.run(mapserver_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("mapserver_pipeline").dataset() sessions_df = data.collection_items.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mapserver_data.collection_items LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mapserver_pipeline").dataset() data.collection_items.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load MapServer data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for MapServer?
Request dlt skills, commands, AGENT.md files, and AI-native context.