DaedalMap
Docs / Bring Your Data

Prepare your data
for DaedalMap.

DaedalMap data starts as a table with places, times, and measurements. loc_id connects each row to the maintained pack layer. Clean rows work across maps, Research, Ops, and agent tools.

Place

Coordinates resolve to the administrative spine. Supported names, admin codes, postal codes, and reference-system ids resolve to their published loc_id identities or crosswalk relationships.

Time

Time-aware rows use timestamp. Yearly filters work better when the table also stores year.

Metrics

Measurements belong in numeric columns with readable names, units, source notes, and caveats.

Minimum table

Each row needs a place and one or more values. The place becomes loc_id. Static facts do not need time fields; observations, events, and time series use timestamp and usually year.

  • Required: loc_id and at least one metric column.
  • Recommended: timestamp, year, units, and source notes.
  • Best for analysis: numeric metric columns, stable row identifiers, and clear missing-value rules.

Example input

A source table often starts with ordinary coordinates and measurements. 

site_name,latitude,longitude,timestamp,temperature_c
Site A,38.8382,-77.4134,2025-07-01,31.4

Resolved table

The resolved table keeps the original coordinates and adds the shared place identifier. 

site_name,latitude,longitude,timestamp,year,loc_id,temperature_c
Site A,38.8382,-77.4134,2025-07-01,2025,USA-VA-059,31.4

loc_id resolution

Point lookup turns latitude and longitude into the deepest available loc_id plus the parent chain above it. Use the deepest match for local observations, or roll up to a parent when the question belongs at county, state, province, or country scale.

Reference lookup handles non-coordinate geography. Postal codes, admin identifiers, named places, warning zones, tribal areas, marine areas, and other catalog-backed systems resolve through DaedalMap reference bridges.

Maintained packs

A maintained DaedalMap pack adds the trust layer around a clean table: metadata, source sheets, license and citation records, runtime files, QA checks, and release status.

Pack checklist

  • Source: who made the data, where it came from, and what license applies.
  • Shape: clean files with loc_id, time fields, numeric metrics, and documented units.
  • Metadata: readable names, descriptions, categories, keywords, caveats, and default examples.
  • QA: checks for loc_id coverage, time fields, query behavior, display behavior, and export readiness.
  • Credit: contributor or maintainer information when a person, lab, or partner prepared the pack.