A scheduled export of device-level energy readings - power, current, voltage, energy, and power factor - measured by Panoramic Power sensors, delivered to a destination you control.

What Is a Measurements Export?

A Measurements export job pulls device-level readings from your account on a schedule and delivers them as a file (CSV) or HTTP payload (JSON) to a destination you choose. Each record is one device, at one point in time, with the electrical readings the sensor produced for that interval.

Why use it?

• Feed time-series readings into a BI tool, data warehouse, or analytics platform.
• Drive billing, sub-metering, or energy attribution workflows that need raw device data.
• Keep a long-term archive of measurements outside PowerRadar.

A Measurements export is usually paired with a Catalog export. Catalog supplies the asset metadata - the sites and devices your readings reference - while Measurements supplies the actual readings. Most partners run both: Catalog daily, Measurements at the chosen frequency. See Export Jobs: Catalog Interface.

For PAN-42 power meters and Pulse Meter readings, use the dedicated Pan-42 Measurements and Meters Measurements export types — they ship different field sets and are documented in separate articles: Export Jobs: Pan-42 Measurements Interface and Export Jobs: Pulse Meter Measurements Interface. This article covers the standard Panoramic Power sensor export only.

Where to Find It

In the sidebar, open the Account Dashboard and click Auto-Export. The Export jobs list opens. Click Create New Export Job in the top right.

For a tour of the Export jobs list itself - the columns, the search and refresh controls, the row menu - see Export Jobs: Setup.

Configuring a Measurements Export Job

The New export job page has the configuration form on the left and a live Data sample preview on the right. As you change settings, the preview updates so you can see the file shape before saving.

1. Job Name

Enter a descriptive name in the Job name field. The name appears in the Export jobs list and in any failure notifications, so use something you'll recognize later - for example, "Hourly measurements - all sites.

2. Data to Export

Open the Data to export dropdown and select Measurements - Device level readings measured by Panoramic Power sensors.

3. Sites for Data Export

Choose which sites the job covers:

• Toggle All sites on to include every site in the account.
• Toggle it off to pick specific sites from the dropdown.

4. Export Frequency and Data Resolution

• Export frequency - how often the job runs. Options: Every day, Every hour, Every 15 minutes, Every 5 minutes.
• Data resolution - the granularity of each measurement record. Options: 1 min, 5 min, 15 min, 30 min, 1 hour.

The available resolution options are filtered by the frequency you select. For example, choosing Every day as the frequency will not let you pick 1 min as the resolution.

If you change Export frequency after setting Data resolution, the resolution options refresh - re-confirm your resolution choice before saving.

5. Zero Pad Measurement Gaps

Tick the Zero pad measurement gaps checkbox to fill missing intervals with zero values instead of leaving them as gaps. PowerRadar produces a continuous timeline at the chosen resolution - every numeric field (power(W), energy(Wh), current(A), voltage(V), power_factor) is set to 0 for any interval where the sensor didn't report. Device IDs, names, and site fields stay populated.

Use it when your downstream system expects evenly spaced records - for example, a BI tool that would otherwise misalign charts when intervals are missing. Leave it off when your downstream system handles sparse data on its own, or when you want to distinguish "sensor reported zero" from "sensor reported nothing".

Note: Padded rows count toward the batch size limit. A job with 8,000 real measurements and 3,000 padded rows totals 11,000 rows and will be split into two files - see Batch Sizes and Limits below.

This option is available for Measurements and Pan-42 Measurements jobs only. It does not apply to Catalog or Meters Measurements.

6. Data Transfer Method

Pick how the file is delivered. Three methods are available:

• JSON over HTTPS - Recommended. Sends the export as a JSON payload to a URL you control.
• CSV over SFTP - Best FTP protocol. Sends a CSV file to a secure SFTP folder hosted by Panoramic Power.
• CSV over FTPS - Older FTP protocol. Sends a CSV file over FTPS.

Each method has its own configuration fields and a How it works? panel below the cards.

For the full breakdown of each transport - including credentials, ports, firewall rules, and the SFTP vs FTPS decision - see Export Jobs: Setup and the SFTP and FTPs Server Connection Checklist.

7. Apply

Click Apply at the bottom right to save the job. Use the same button when editing an existing Measurements job.

Once saved, the job is active and runs automatically on the schedule you defined. To pause, re-enable, or delete a Measurements job later, open the three-dot menu in its row on the Export jobs list - see Export Jobs: Setup for the list controls.

Sample Outputs

The Data sample panel on the right side of the New export job page shows a fixed example file that illustrates the structure and field names of the export you're configuring. The same example is shown to every account - it does not reflect your actual sites, devices, or measurements.

The preview changes when you switch:

• Data to export - between Measurements, Catalog, Pan-42 Measurements, and Meters Measurements.
• File format - between CSV (used by CSV over SFTP and CSV over FTPS) and JSON (used by JSON over HTTPS).
• Version - for Catalog jobs only, between v1.0 and v1.1.

Settings such as Sites, Export frequency, Data resolution, and Zero pad measurement gaps do not change the preview. To see how your real data will look at the chosen frequency and resolution, wait for the first scheduled run.

Field Reference

Every Measurements record contains the following fields. In JSON over HTTPS payloads, fields that carry a unit of measurement include the unit in the key itself - partners parsing the JSON must read keys like "measurement_time(UTC)" and "power(W)" verbatim. Fields without a unit (the ID, name, and power_factor fields) use plain key names.

Note — JSON key format: Fields that carry a unit of measurement include the unit in the key - read "measurement_time(UTC)", "resolution(minutes)", "current(A)", "voltage(V)", "power(W)", and "energy(Wh)" verbatim, with the parentheses. The remaining fields ("device_id", "device_name", "site_id", "site_name", "power_factor") use plain key names. Your downstream parser must read each key exactly as shown.

Late Data and One Row Per Measurement

PowerRadar guarantees one row per device, per measurement time, per export run. The exporter looks up the most recent version of each (device_id, measurement_time) pair at query time and emits only that — you will never receive two records for the same device and timestamp in a single run.

What this means in practice:

• No deduplication needed. You can append every row to your downstream store without checking for duplicates by (device_id, measurement_time).
• No "updated record" follow-ups. Unlike some legacy exporters, PowerRadar does not re-send a previously delivered record with a corrected value.
• Late data has a 5-minute window. A reading that arrives at PowerRadar within 5 minutes after its measurement window closes is included in the next export run. Data that arrives later than that is stored in PowerRadar but is not picked up by any future export run.

If you need a measurement window that has already passed, run a Manual Export - manual exports are not bound by the 5-minute window. See Manual Export. 

Batch Sizes and Limits

Large exports are split into multiple files or transactions. The split is automatic - you don't need to configure it - but if you size downstream ingestion or storage by record count, the numbers below are the ones to plan against.

A few practical notes:

• Zero Pad Gaps rows count toward the limit. A job with 8,000 real measurements and 3,000 padded rows totals 11,000 rows, which exceeds the 10,000-row file limit and will be delivered as two files.
• JSON over HTTPS retries. Each HTTP transaction must return HTTP 200 OK on its own. Failed transactions are retried in the next scheduled run for up to one week.
• Configure your endpoint for at least 1 MB payload size if you receive Measurements over HTTPS.

Related Articles

• Export Jobs: Setup
• Export Jobs: Catalog Interface
• Export Jobs: Pan-42 Measurements Interface
• Export Jobs: Pulse Meter Measurements Interface
• SFTP and FTPs Server Connection Checklist