DaedalMap
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.

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.

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.

Open the live pack library

Download glossary

Download tiers describe the geometry representation included with a package. They do not remove records from the underlying data release.

  • Lite: complete data tables, or geometry identities and crosswalks, without an attached reusable polygon bank.
  • Display: the Lite contents plus simplified geometry for maps, previews, and ordinary local display.
  • Detail: the Geometry Display contents plus the highest-resolution maintained shapes and spatial indexes for precise local work.

Data packs are available as Lite and Display. Geometry packages are available as Lite, Display, and Detail. Data-native coordinates, tracks, footprints, and event perimeters remain part of the data itself in both data editions.

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.

Sources and coverage

A source data sheet is the public record behind a pack. It names the original publisher, pack maintainer, and method used to clean, merge, or model the data. Check its update date, time range, main fields, license, citations, and caveats before relying on a result.

  • Pack name and short summary
  • Original publisher, source links, maintainer, and contributor credit
  • Methodology, update cadence, and last update
  • Time range, geographic coverage, and main metrics or fields
  • License, citations, caveats, and release history

How country coverage is declared

Global sources declare coverage against a shared list of 200 sovereign states instead of repeating every country code. A companion list holds 52 territories and special regions that upstream datasets often omit. Each source records its geographic_coverage type (global, country, or regional), common_count, common_missing, and uncommonly_included. Actual coverage is the common-country list minus missing countries plus any listed additional territories or regions. For example, all 200 common countries plus 17 additional territories means 217 country-level regions covered.

A country pack names its ISO3 code and the administrative levels carrying data. A regional pack names the country and the region inside it. These declarations keep a regional source from being described as global. Check the live pack catalog for each published release's actual coverage and source record. The open engine keeps its country reference lists and aliases under mapmover/reference/.

Prepare a pack-ready table

Start with a place and one or more values in each row. The location can begin as coordinates or a supported reference code; use the geometry tools to resolve it to a suitable loc_id. Preserve the source fields. Static facts need no time field; observations, events, and time series use timestamp, usually with a separate year for annual filtering. Measurements work best as numeric columns with readable names, units, stable row identifiers, and missing-value rules.

  • Table: loc_id and at least one metric; add time fields where the data changes over time.
  • Source: publisher, source link, methodology, coverage, license, and caveats.
  • Metadata: names, descriptions, categories, keywords, units, and useful examples.
  • QA: check loc_id coverage, time fields, queries, display, and export readiness.
  • Credit: identify contributors or maintainers who prepared the pack.

The engine and schema model are open. A maintained release adds the source sheet, citation and license records, runtime files, QA, and release status around a clean table. A source's stated gaps and modeled values stay visible rather than being inferred from a map.