IoT Sensor Readings (JSON, 1440 records)
The IoT sensor readings as a JSON array: the format twin of the CSV, for time-series testing.
[
{
"timestamp": "2025-06-01T00:00:00Z",
"sensor_id": "sensor-01",
"temperature_c": 20.01,
"humidity_pct": 61.4,
"pressure_hpa": 1014.8
},
{
"timestamp": "2025-06-01T00:01:00Z",
"sensor_id": "sensor-02",
"temperature_c": 19.82,
"humidity_pct": 59.7,
"pressure_hpa": 1012.2
},
{
"timestamp": "2025-06-01T00:02:00Z",
"sensor_id": "sensor-03",
"temperature_c": 20.27,
"humidity_pct": 59.9,
"pressure_hpa": 1014.1
},
{
"timestamp": "2025-06-01T00:03:00Z",
"sensor_id": "sensor-01",
"temperature_c": 19.33,
"humidity_pct": 61.6,
"pressure_hpa": 1012.9
},
{
"timestamp": "2025-06-01T00:04:00Z",
"sensor_id": "sensor-02",
"temperature_c": 20.36,
"humidity_pct": 59.9,
"pressure_hpa": 1012.4
},
{
"timestamp": "2025-06-01T00:05:00Z",
"sensor_id": "sensor-03",
"temperature_c": 20.29,
"humidity_pct": 60.8,
"pressure_hpa": 1012.7
},
{
"timestamp": "2025-06-01T00:06:00Z",
"sensor_id": "sensor-01",
"temperature_c": 20.07,
"humidity_pct": 60.7,
"pressure_hpa": 1011.7
},Specifications
- Records
- 1440
- Schema
- timestamp, sensor_id, temperature_c, humidity_pct, pressure_hpa
- Domain
- IoT
Testing contract
Expected to pass- Scenario
- Exercise IoT Sensor Readings (JSON, 1440 records) in its iot workflow. The IoT sensor readings as a JSON array: the format twin of the CSV, for time-series testing.
- Expected result
- array length is 1440; first-record keys are timestamp, sensor_id, temperature_c, humidity_pct, pressure_hpa. Declared feature checks: domain=IoT.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“IoT Sensor Readings (JSON, 1440 records)” is a deterministic Testaroo fixture for Data import, Time-series data. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: 1,440 records · schema: timestamp, sensor_id, temperature_c, humidity_pct, pressure_hpa. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import json
with open("sensor-readings.json") as f:
data = json.load(f)
print(type(data), len(data))Generated by generation/data_realworld.py. Free for any use, no attribution required, license.
Related files
- csvAlder Table Bistro: HACCP temperature logHACCP temperature log for Alder Table Bistro. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.
- csvCedar Street Tacos: HACCP temperature logHACCP temperature log for Cedar Street Tacos. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.
- csvCopper Oven Bakery: HACCP temperature logHACCP temperature log for Copper Oven Bakery. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.
- csvEmber Lane Pizza: HACCP temperature logHACCP temperature log for Ember Lane Pizza. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.
- csvHarbour Kitchen Group: HACCP temperature logHACCP temperature log for Harbour Kitchen Group. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.
- csvJuniper Corner Cafe: HACCP temperature logHACCP temperature log for Juniper Corner Cafe. 84 readings across 13 columns: 3 units checked twice a day for fourteen days. Each row carries its own lower and upper limit, so the within_limit column can be recomputed from the row beside it. 2 readings fall outside their limit (TEMP-038, TEMP-071) and only those rows carry a corrective action.
