xyver/daedal-map

**Bring your data. Connect its geography.**
DaedalMap is geographic interoperability infrastructure: a loc_id identity
model, versioned boundary geometry, published crosswalks between geography
systems, and maintained data packs. Resolve coordinates and reference codes to
administrative matches, pull compatible shapes and data, and follow crosswalks
into other systems such as census tracts, postal areas, watersheds, and
electoral districts.
Use it through a remote MCP server, an HTTP API, a map app, downloadable files,
or this repository, which is the open runtime behind all of them.
Website |
App |
Agent docs |
Geometry |
Data packs |
Downloads |
Convert a file |
llms.txt
Connect an agent
The hosted MCP server needs no install or account for discovery:
Claude Code:
Codex:
Any client that supports streamable HTTP MCP can use the same URL. Start with
get_tool_help with topic='geometry' for geography jobs, or get_catalog, then get_pack,
then get_data for data. Setup for other clients is in the
agent docs.
Discovery and small geography lookups are free. Larger point/reference batches
and some data packs are metered: a paid call returns its exact price before any
charge and is paid from account credit with an API key. get_catalog reports
the access lane for each pack.
Tools
| Job | Tools |
|---|---|
| Learn the model | get_tool_help with a topic or exact tool name |
| Find what exists | get_catalog, then get_pack for one selected data pack or geometry family |
| Query maintained data | get_data with a pack_id, exact metrics, and structured filters |
| Inspect one disaster event | get_event with an exact event_id returned by get_data |
| Coordinates to places | resolve_point, then resolve_deep_point when Admin 4-6 or one deeper family is needed |
| Identify a column of codes | identify_dataset_geography, identify_reference_system |
| Translate codes between systems | convert_reference |
| Inspect and relate places | get_loc_id_info, compare_geographies |
| Retrieve shapes | get_geometry |
Each tool takes strict JSON arguments. The calling model turns a user's
question into those arguments, and the server returns typed errors with
recovery guidance when a call is malformed.
This table is the complete public roster, not a roadmap. Bulk export/job
builders and direct upstream live-feed wrappers remain internal or paused and
are intentionally absent from tools/list.
The loc_id model
loc_id is DaedalMap's geographic identity model. The administrative spine is
the main hierarchy and default join path:
Other geography families, such as postal areas, watersheds, tribal areas, and
marine regions, keep their own loc_id identities. Published crosswalks connect
them to the spine and to each other, and each crosswalk row carries its
relationship type, overlap weight, source, and vintage. A direct join works when
both datasets declare the same identity; otherwise the connection runs through a
crosswalk.
Schema details are in docs/DATA_SCHEMAS.md.
Coverage
**Geometry: global baseline plus 8+ deeper countries.** The same geography
tools work worldwide down to Admin 2. Country releases add deeper
administrative tiers and reference families for Australia, Brazil, Canada,
France, Germany, Mexico, the United Kingdom, the United States, and more as