DaedalMapWhat is DaedalMap?
DaedalMap is geographic reference infrastructure: durable loc_id identities, reusable geometry, published crosswalks, and maintained data packs. Maps, Research, Ops, downloads, conversion, and agent tools are ways to use that foundation.
What is a loc_id?
A loc_id is DaedalMap's identifier for a place, such as USA-VA-059 for Fairfax County, Virginia. Coordinates, names, and codes that describe the same place resolve to the same loc_id. Postal areas, watersheds, and other geography families keep their own identities, and published crosswalks connect them.
Do I have to restructure my data?
No. Try Your Data keeps every original column and adds loc_id and admin_level. When a code could belong to more than one geography system, it asks you to confirm before converting.
What happens to rows that do not resolve?
They stay in the output, marked with the reason, so you can fix the source values or drop them deliberately. A row that matches only at state level is reported at state level, not presented as a county match.
What do I get without paying?
Testing a sample is free. You can also inspect the data and geometry catalogs, download eligible releases, and use the free geographic reference and geometry MCP tools.
Is DaedalMap open source?
The core 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.
How does geometry fit the product?
Geometry is a maintained product layer, not just map decoration. Country releases publish reusable representations for display and detailed analysis. loc_id identities and published crosswalks connect administrative and specialized geography families without collapsing them into one universal hierarchy.
What is a pack?
A pack is a maintained release unit for geographic evidence. It groups source data, metadata, provenance, coverage, licensing, and runtime behavior so the evidence can be explored, analyzed, monitored, or called from tools.
Can I make my own pack?
Yes. A source pack should document its source, methodology, coverage, update pattern, license, caveats, and loc_id alignment before it becomes part of the maintained layer.
Can I run DaedalMap myself?
Yes. Publicly, there are two paths: use it online or install it yourself.
If you install it yourself, you can either use the packaged local runtime or the GitHub and manual setup path.
Why does the site talk so much about sources?
Because source-backed answers need a visible trail. Users should know where the evidence came from, how current it is, what geography it covers, and where the limits are.
Should I use the hosted app or run it myself?
Use hosted if you want the fastest path in: open the app, start querying, no setup. It is the right default for demos, shared team access, and maintained convenience.
Install it yourself if you want the same engine on your own machine. The packaged local runtime is the easier install path. It works offline once packs are installed, keeps private data on your machine, and removes the hosted-query dependency.
Use the GitHub and manual path when you want deeper deployment control, private catalogs, or more technical customization.
The engine is the same either way. The difference is delivery, trust assumptions, and performance. See install it yourself to get started.
Is the hosted app the same as local use?
Same engine, different operating assumptions. Hosted mode optimizes for convenience and shared access. Installing it yourself optimizes for local control. The packaged local runtime is the easier install, while the GitHub and manual path gives deeper control.