Hubverse Data Prep

What each field means

target_end_date

The date attached to the observed target. Hubs may use another configured name, such as target_date. Dates are exported in ISO YYYY-MM-DD format.

location

The hub's identifier for the geographic unit, such as a FIPS code or a custom location ID. Values are kept as text so leading zeros are preserved.

observation

The value that was observed for the specified date and location. It can be prepared as a number, integer, text category, or logical value.

target

A hub task ID identifying the outcome. Assign one target to all rows, map target values from a source column, or assign targets to inclusive row ranges.

How preparation works

Add dataUpload Excel, CSV, TSV, JSON, text, paste, or manually enter rows.
Choose a hubApply a preset or load the hub's current configuration, then match fields.
Assign rowsSet targets and crosswalk source locations to hub IDs.
Review checksResolve invalid dates, missing values, and duplicates.
DownloadSave time-series.csv and optional Python or R code.

Use the hub's exact setup

The selector includes the 30 public hubs in the Hubverse directory, grouped as active, training, model development, and archival entries (directory updated 31 August 2026). Private directory entries are deliberately omitted.

If a hub provides hub-config/tasks.json and hub-config/target-data.json, load one or both during mapping. The tool reads target IDs, locations, the configured date column, and observable-unit fields, then adjusts the form and checks.

Only fields required for the selected hub are exported. Unmapped source columns are removed automatically, and all recognized dates are written as ISO YYYY-MM-DD.

A hub can still define additional rules that only its official validation workflow knows. Treat this browser check as preparation—not a replacement for final hub validation.

Private by design

All parsing, cleaning, checking, and file creation happen inside this browser tab. The HTML has no analytics, server calls, or external code dependencies.

Read Hubverse target-data guidance

Turn ordinary files into hub-ready data.

Add your source data

Choose the hub and match your columns

Choose the destination hub

Match the three source columns

Reusable pipeline

Confirm the cleaning defaults

Assign targets and hub locations

Assign one target to every row

Match source locations to hub IDs

Review the checks

Check details

Output preview

Your Hubverse file is ready

A focused bridge from source data to Hubverse.

What each field means

How preparation works

Use the hub's exact setup

Private by design

Bring in almost any table