Flexidao

Meter Data Validation

Meter Data for Bridge T-EACs — v1.2

Your files are not stored.

Uploaded files are processed in memory only and are never saved.

Validate your meter data files

Upload up to 20 XLSX or CSV files following the Meter Data for Bridge T-EACs standard template. We'll check each one against all format and data quality requirements.

Drag & drop your XLSX or CSV files here

or click to browse

Choose files

or

Standard Template

Download the Meter Data for Bridge T-EACs file template or examples with sample data.

Template (.xlsx) Template (.csv) Example (.xlsx) Example (.csv)

Required columns:

datetime_start_local, local_timezone, datetime_start_utc, value, unit_of_measurement, meter_id, eac_facility_id, eac_registry_id

Validation Requirements

File-Level

  • File must be .xlsx or .csv format
  • File must contain exactly one worksheet
  • File must contain exactly one eac_facility_id value across all rows

Required Headers

All 8 headers must be present in the first row:

datetime_start_local local_timezone datetime_start_utc value unit_of_measurement meter_id eac_facility_id eac_registry_id

Column Format Requirements

Column Format Example
datetime_start_local RFC 3339 with timezone offset 2025-01-01T00:00:00-06:00
local_timezone IANA Area/Location format America/Chicago
datetime_start_utc RFC 3339, must end with Z or +00:00 2025-01-01T06:00:00Z
value Numeric, . for decimals, no other characters 10321.887321
unit_of_measurement One of: GWh, MWh, kWh, Wh MWh
meter_id Meter identifier for the datapoint. If the meter_id is not known and there is only one dataset per eac_facility_id, the eac_facility_id can be used as the meter_id. 19883332
eac_facility_id Production device ID as used in EAC Registry GEN2804
eac_registry_id Valid registry ID from the m-rets
metering_type Optional One of gross or net. Defaults to gross when the column is omitted. For gross the value must be non-negative; net allows negative values. gross
metering_share Optional One of contracted or total generation. Defaults to contracted when the column is omitted. contracted

Timestamps must be plain text. Enter datetime_start_local and datetime_start_utc as RFC 3339 strings — do not use Excel's native date/time cell type. Excel dates are timezone-naive and drop the offset, so they are rejected. In Excel, format the column as Text before entering the values.

Time-Series Requirements

  • No blank cells: All required columns must be populated in every data row — no empty cells allowed.
  • Time continuity: A value and timestamp must be provided for every interval, even if null, empty, or zero. No gaps are allowed.
  • Interval readings: Values must represent generation within the time interval, not accumulated meter totals.
  • Consistent intervals: All time intervals must be the same duration (hourly or sub-hourly).
  • UTC/local consistency: datetime_start_utc must match datetime_start_local adjusted by the timezone offset.
  • DST handling: If readings are in UTC, no gaps or duplicates during DST transitions. If in local time, DST changes must be correctly reflected (missing hour in spring, duplicate in fall, both with correct offset adjustments).

API Integration

Validate files programmatically by sending a POST request with one XLSX or CSV file under file, or up to 20 files under files. See the full API reference for endpoints, request and response schemas, and status codes.

API Reference OpenAPI 3.2 spec (.yaml)

Limitations

Max file size

8 MB

Larger files are rejected with 413.

Max rows

50,000

Files with more rows are rejected with 400.

Max files

20

Batch uploads with more files are rejected with 400.

Rate limit

15 / min

Per IP address; exceeding returns 429.

Files are processed in memory only and are never stored.