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
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 Novus Examples 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))Related files
- csvStock OHLCV — Daily Candles (CSV, 252 rows)A year of daily OHLCV stock candles (open/high/low/close/volume) as a seeded random walk — a realistic finance time-series for testing charting, indicators, and importers. JSON twin included.
- jsonStock OHLCV — Daily Candles (JSON, 252 records)The daily OHLCV candles as a JSON array — the format twin of the CSV, for charting and time-series testing.
- csvWeather Forecast — 30 days (CSV, 30 rows)A 30-day daily weather forecast for one city — high/low temperature, condition, precipitation, wind, and humidity. Synthetic (seeded) data for testing weather widgets, chart tools, and time-series import.
- jsonWeather Forecast — 30 days (JSON, 30 records)The daily forecast as a JSON array — the format twin of the CSV, for import and charting tests.
- nmeaNMEA 0183 — GGA Sentences OnlyThe same twelve fixes reduced to GGA alone. GGA carries time-of-day but no date and no speed, so a parser that only reads GGA cannot place the track on a calendar — a real limitation that this file makes obvious rather than leaving to be discovered later.
- nmeaNMEA 0183 — Mixed GGA/RMC/GSA/GSV/VTG LogA twelve-fix receiver log with the five sentence types a GPS unit normally interleaves, including three-part GSV satellite-in-view sets. Every checksum is correct, so a parser that verifies them should accept the whole file.
Generated by generation/data_realworld.py. Free for any use, no attribution required — license.