Skip to content
Novus Examples
json1.3 KB

IOT — Sensor Readings Mini (JSON)

JSON twin of the iot/sensor-readings-mini mini-dataset.

Preview — first 50 linesjson
[
  {
    "device_id": "dev_1",
    "ts": "2026-01-15T00:00:00Z",
    "temp_c": 20,
    "humidity": 40
  },
  {
    "device_id": "dev_2",
    "ts": "2026-01-15T01:00:00Z",
    "temp_c": 21,
    "humidity": 41
  },
  {
    "device_id": "dev_3",
    "ts": "2026-01-15T02:00:00Z",
    "temp_c": 22,
    "humidity": 42
  },
  {
    "device_id": "dev_4",
    "ts": "2026-01-15T03:00:00Z",
    "temp_c": 23,
    "humidity": 43
  },
  {
    "device_id": "dev_1",
    "ts": "2026-01-15T04:00:00Z",
    "temp_c": 24,
    "humidity": 44
  },
  {
    "device_id": "dev_2",
    "ts": "2026-01-15T05:00:00Z",
    "temp_c": 20,
    "humidity": 45
  },
  {
    "device_id": "dev_3",
    "ts": "2026-01-15T06:00:00Z",
    "temp_c": 21,
    "humidity": 46
  },
  {
    "device_id": "dev_4",
    "ts": "2026-01-15T07:00:00Z",
    "temp_c": 22,
    "humidity": 47
  },
  {
75 lines total — download for the full file.

Specifications

Records
12
Schema
device_id, ts, temp_c, humidity

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 Mini (JSON)” is a deterministic Novus Examples fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 12 records · schema: device_id, ts, temp_c, humidity. 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-mini.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/breadth_extra_wave_c.py. Free for any use, no attribution required — license.