Export Jobs: Pulse Meter Measurements Interface
A scheduled export of utility meter readings - power, energy, flow, and volume - from third-party meters connected to your sites via loggers or bridges.
Written by Shir Goldstein
Updated at May 26th, 2026
Table of Contents
A scheduled export of pulse meter readings - electricity, water, gas, heat, and air - connected to your sites via loggers or bridges, for use in downstream analytics, BI, or integration systems.
What Is a Meters Measurements Export?
A Meters Measurements export job pulls readings from the pulse meters connected to 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 meter, at one point in time, with the readings that meter produced for that interval.
Pulse meters are third-party meters - for electricity, water, gas, heat, or air - that are connected to PowerRadar through a logger or bridge device. Unlike Panoramic Power sensors, each meter type reports a different set of measurement fields: electricity, heat, and gas meters report power and energy; gas, water, and air meters report flow and volume; gas meters report all four. See Fields by Meter Type below.
Why use it?
- Feed multi-utility readings (electricity, water, gas, heat, air) into a BI tool, data warehouse, or analytics platform.
- Drive sub-metering, sustainability reporting, or utility billing workflows that need raw meter data alongside energy sensor readings.
- Keep a long-term archive of meter readings outside PowerRadar.
A Meters Measurements export is usually paired with a Catalog export. Catalog supplies the asset metadata - the sites and meters your readings reference - while Meters Measurements supplies the actual readings. Most partners run both: Catalog daily, Meters Measurements at the chosen frequency. See Export Jobs: Catalog Interface.
For Panoramic Power sensor readings, use the Measurements export type instead. For PAN-42 power meter readings, use the Pan-42 Measurements export type. Each is documented in its own article: Export Jobs: Measurements Interface and Export Jobs: Pan-42 Measurements Interface. This article covers pulse meter exports 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 Meters Measurements Export Job
The New export job page has the configuration form on the left and a Data sample preview on the right. The preview shows a fixed example of the export file format - it isn't pulled from your account - and it's there to help you see the shape of the file 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 meters - all sites".
2. Data to Export
Open the Data to export dropdown and select Meters Measurements - Meters readings measured through loggers or bridges.
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.
Sites that don't have any pulse meters connected can still be included - they contribute no rows to the export.
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. The available options are filtered by the frequency you select.
| Export Frequency | Available Data Resolutions |
|---|---|
| Every day | 15 min, 1 hour |
| Every hour | 5 min, 15 min, 1 hour |
| Every 15 minutes | 1 min, 5 min, 15 min |
| Every 5 minutes | 1 min, 5 min |
If you change Export frequency after setting Data resolution, the resolution options refresh - re-confirm your resolution choice before saving.
5. 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.
6. Apply
Click Apply at the bottom right to save the job. Use the same button when editing an existing Meters Measurements job.
Once saved, the job is active and runs automatically on the schedule you defined. To pause, re-enable, or delete a Meters 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, meters, 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).
Settings such as Sites, Export frequency, and Data resolution do not change the preview. To see how your real meter data will look at the chosen frequency and resolution, wait for the first scheduled run.
Field Reference
Every Meters Measurements record contains the following fields.
Note — not all fields are populated for every meter type. The power, energy, flow, and volume fields are conditionally included based on the type of meter. See Fields by Meter Type below. When a field is not applicable to a meter's type, its value is N/A in both JSON and CSV - not zero, and not an empty cell.
| Field - CSV header | Field - JSON key | Type | Description |
|---|---|---|---|
| meter_id | METER_ID | integer | Unique identifier of the pulse meter, matching the ID in the Catalog export. |
| meter_type | METER_TYPE | string | The utility type of the meter. Common values: Electricity, Water, Gas, Heat, Air. Older installations may show legacy values such as Electric Pulse Meter - these behave identically to Electricity for export purposes. |
| meter_name | METER_NAME | string | Display name of the meter, as assigned at installation. |
| meter_unit | METER_UNIT | string | The unit the meter measures in. For electricity and heat meters: kWh. For flow/volume meters: m3, Nm3, Sm3, ft3, SCF, or Gallon. |
| measurement_time(UTC) | MEASUREMENT_TIME(UTC) | timestamp | Start of the measurement interval, in UTC. Always UTC - regardless of the account's display timezone. |
| resolution(minutes) | RESOLUTION(min) | integer | Length of the measurement interval, in minutes. Matches the Data resolution chosen for the job. |
| site_id | SITE_ID | integer | Unique identifier of the site the meter belongs to. |
| site_name | SITE_NAME | string | Display name of the site. |
| power(W) | POWER(W) | decimal | Average electrical power over the interval, in watts. Populated for Electricity and Heat meters - N/A for all others. |
| energy(Wh) | ENERGY(Wh) | decimal | Electrical energy over the interval, in watt-hours. Populated for Electricity and Heat meters - N/A for all others. |
| flow | FLOW | decimal | Average flow rate over the interval. The unit is given by meter_unit. Populated for Gas, Water, and Air meters - N/A for all others. |
| volume | VOLUME | decimal | Total volume accumulated over the interval. The unit is given by meter_unit. Populated for Gas, Water, and Air meters - N/A for all others. |
Fields by Meter Type
The table below shows which measurement fields are populated for each meter type. Fields marked N/A carry the literal string "N/A" in the export - they are not zero and not an empty cell.
| Meter Type | power(W) | energy(Wh) | flow | volume |
|---|---|---|---|---|
| Electricity | ✓ | ✓ | N/A | N/A |
| Heat | ✓ | ✓ | N/A | N/A |
| Gas | ✓ | ✓ | ✓ | ✓ |
| Water | N/A | N/A | ✓ | ✓ |
| Air | N/A | N/A | ✓ | ✓ |
When a single export job covers sites with mixed meter types, each row includes only the fields relevant to that row's meter_type. The other fields are N/A. Your downstream store should handle a mix of populated and N/A values in the same file.
Note: Older installations may have meters with legacy type values (such as Electric Pulse Meter). These follow the same field pattern as Electricity - power and energy populated, flow and volume N/A.
Late Data and One Row Per Meter
PowerRadar guarantees one row per meter, per measurement time, per export run. The exporter looks up the most recent version of each (meter_id, measurement_time) pair at query time and emits only that - you will never receive two records for the same meter 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
(meter_id, measurement_time). - No "updated record" follow-ups. 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.
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.
| Transport | Maximum rows per file / transaction |
|---|---|
| CSV over SFTP | 10,000 rows |
| CSV over FTPS | 10,000 rows |
| JSON over HTTPS | 2,000 measurements |
A few practical notes:
- One row per meter per interval. Unlike PAN-42 meters, pulse meters are single-channel - one meter produces one row per measurement time. Row count scales with the number of meters and the resolution interval.
- Zero Pad is not available for Meters Measurements. The zero-padding option that fills missing intervals with zeros applies only to Measurements and Pan-42 Measurements jobs. Missing intervals in a Meters Measurements export are simply absent - no row is generated for them.
- Configure your endpoint for at least 1 MB payload size if you receive Meters Measurements over HTTPS.