Live catalog first
Use the pack library for the live published list. It is generated from the active pack catalog and links to per-pack pages with coverage, licensing, provenance, and field detail.
Docs / Packs
Packs are the maintained data units behind every DaedalMap surface.
Each pack carries source data, metadata, coverage, provenance, and query behavior as one versioned unit. The live library holds the pack count, release status, access details, and per-pack evidence.
One release unit
A pack bundles source data, metadata, coverage notes, license details, and query behavior into a versioned unit that can be shown on the site, opened on the map, queried by Research, or exposed to agents.
Shared runtime
Explore, Research, Ops, local installs, and agent/API surfaces resolve pack identity through the same maintained catalog.
What a pack is
A pack is DaedalMap's durable packaging layer for maintained datasets. It can contain one source or a source family, but it presents one public identity for browsing, documentation, release status, and query routing.
Pack pages answer the practical questions before someone runs a query: what the pack covers, where the data came from, which fields and metrics are available, what geography keys it supports, how it is licensed, and what caveats apply.
Live inventory
The public pack library is the human-facing catalog and the source of truth for the live published list.
Pack detail is the authority
Each pack detail page is the right place to inspect release status, source agencies, data coverage, licensing, and field-level notes. For programmatic discovery, use the catalog endpoints before writing a query.
GET /api/v1/catalog- live agent/API pack index.GET /api/v1/packs/{pack_id}- full detail for one pack./packs- public human-facing pack library./packs/{pack_id}- public human-facing pack detail.
Release maturity
Packs can move through different release states as coverage, QA, and surface support mature. Live status belongs on the pack page and catalog payload because it changes as data is promoted.
- Core - stable, broadly ready, and suitable for default surfaces.
- Standard - maintained and public, with scope or freshness still evolving.
- Experimental - useful but still maturing, narrow, or region-specific.
- Private - partner-restricted or not yet published.
Access and pricing
Free, hosted, paid, downloadable, and agent/API availability are pack attributes. Check the pack library or API catalog for the live access tier before assuming a pack can be queried from a particular surface.
Coverage inventory
For a broader view of source families, geography coverage, and planned data directions, use the source map alongside the pack library.
Contributing a pack
The pack model is also the path for packaging your own data into the same runtime. The engine and schema model are open, while the maintained layer keeps published packs documented and queryable.