Map Fields, Units, and Timestamps

Meteobreeze stores weather values in canonical units, so it needs to know what each source column means before it can import the file correctly.

Use this guide when you are mapping CSV columns during a historical import.

Recommended: connect your live source first, then map and import the historical file. That keeps your station current while you finish backfilling old records.

When to use it

• Your CSV has columns that do not match Meteobreeze names exactly
• Your source uses Fahrenheit, miles per hour, inches, or another non-canonical unit
• Your timestamps are in local time and need a timezone

Before you start

• Know which column is the timestamp
• Know the source unit for each mapped measurement
• Know which timezone the source timestamps use

Step-by-step

1. Map the timestamp column to observedAt.
2. Map each weather column to the correct Meteobreeze field.
3. Set the source unit for each mapped column.
4. Set the timestamp timezone if the file uses local time.
5. Review the preview before starting the import.

Common issues

• If Meteobreeze says the timestamp is required, the observedAt column has not been mapped yet.
• If values look too high or too low, the source unit is probably wrong.
• If the times are shifted, the timestamp timezone is probably incorrect.
• If a column is not recognized, map it manually instead of relying on auto-detection.

FAQ

• Do I need to map every column? No. Only the columns you want to import.
• What happens to unmapped columns? They are ignored.

Related pages

• Units
• Import a CSV file

Image needed: a screenshot of the column-mapping screen showing a timestamp column, a measurement column, and the unit selector for that measurement.