Bring your data.
Connect its geography.

Detect coordinates and supported reference columns, resolve them into the loc_id model, and connect compatible geometry, data packs, and published crosswalks without losing source or vintage.

No account needed. Options for larger files

Identity examples

One result column, across countries, depths, and geography families.

referencematched placecountryloc_idresultMCP Tool
-33.8688, 151.2093Sydney Inner CityAustraliaAUS-NSW-117-03Admin 3resolve_point
41.8781, -87.6298Block Group 1United StatesUSA-IL-031-839100-1Admin 4resolve_point
43.6532, -79.383235204616019CanadaCAN-ON-3520-005-4616-019Admin 5resolve_point
19.4326, -99.1332CuauhtémocMexicoMEX-09-015Admin 2resolve_point
Postal area 22030ZCTA 22030United StatesUSA-POSTAL-ZCTA-22030-071385E6Postal arearesolve_reference
Mediterranean SeaMediterranean SeaInternationalIHO1953-240001002Water bodyresolve_reference
Olympic National ForestOlympic National ForestUnited StatesUSA-LANDMGMT-OLYMPIC-NATIONAL-FOREST-C2F58153Forestloc_id_info
Annette IslandAnnette IslandUnited StatesUSA-INDIGENOUS-ANNETTE-ISLAND-02C32282Indigenous landloc_id_info
referenceloc_id
Sydney Inner CityAUS-NSW-117-03
Block Group 1USA-IL-031-839100-1
35204616019CAN-ON-3520-005-4616-019
CuauhtémocMEX-09-015
ZCTA 22030USA-POSTAL-ZCTA-22030-071385E6
Mediterranean SeaIHO1953-240001002
Olympic National ForestUSA-LANDMGMT-OLYMPIC-NATIONAL-FOREST-C2F58153
Annette IslandUSA-INDIGENOUS-ANNETTE-ISLAND-02C32282

Coordinates resolve into each country's administrative spine. Postal, water, forest, and Indigenous land keep their own family identities. Readable family IDs are MCP-returned preferred public aliases that resolve to the durable canonical identity.

The Join Problem

Location columns look simple until you need them to agree.

Geocorr already handles many U.S. Census-to-Census translations well. DaedalMap takes on the broader join: coordinates, codes, names, and overlapping geographic families across countries and vintages, while keeping each system's identity intact.

1

Paste a sample

Start with a small CSV or Excel worksheet containing coordinates or a supported geographic reference column.

2

Resolve loc_ids

DaedalMap returns matched places, parent geography, and unresolved rows that need cleanup.

3

Convert the rest

Run larger batches through the hosted MCP tools, install the local runtime, or send the file to us. Compare the three.

4

Use the connections

Download free geometry and write simple spatial joins yourself. For systems that do not nest, use crosswalks that retain source, relationship, weight, and vintage.

What that makes possible

The clearest hot zones sit in the more urbanized eastern and central portions of Fairfax County, while the western side stays cooler where vegetation cover is stronger and development density is lower. Heat patterns are shaped by several land-cover and built-environment factors, not a single driver.

Immediate shock (2004–2005): electricity access dropped 4.2 points, industrial CO2 intensity collapsed 76%, unemployment jumped 2.6 points, industrial production growth halved. National-level recovery was largely complete within two to three years.

Frequently asked questions

What is loc_id?

loc_id is DaedalMap's geographic identity model. Coordinate rows resolve to the administrative spine. Other geography families keep distinct identities and connect through published crosswalks.

What happens to rows that do not resolve?

They come back marked with the reason, and they stay in the output so you can fix the source values or drop them deliberately. A row that only matches to state level reports state level rather than being presented as a county match.

Do I have to restructure my data?

No. Coordinate resolution preserves every original column while adding a spine loc_id and administrative chain. Reference identification preserves the source values and asks you to confirm ambiguous systems before creating a processing binding.

What does it cost?

Testing a sample is free, and the engine and schemas are open source so you can run the same resolution yourself. Paid access covers maintenance, QA, packaging, freshness, hosted tools, and support around the maintained data layer.

Open-core engine. Maintained geographic reference layer.

The engine and schemas are open source. One maintained geographic reference graph connects durable loc_id identities, reusable display and full-detail geometry, published crosswalks, and versioned data packs. Maps, Research, Ops, downloads, and agent tools are ways to use that foundation. The maintained layer covers reference alignment, converters, source discovery, QA, freshness, hosted compute, and support.

Founded by .