Skip to content
Novus Examples
jsonl14.5 KB

Pine Assembly Workshop: Shipment tracking events as newline-delimited JSON

Shipment tracking events as newline-delimited JSON for Pine Assembly Workshop. The same 74 scan events as tracking-events.csv, one JSON object per line with no enclosing array and no trailing comma. The file is not valid JSON as a whole and is not meant to be: each line is a complete document, which is what lets a consumer stream it without buffering the whole file.

jsonl

application/x-ndjson

14.5 KB
Document Set
logistics
Industry
logistics
Source Kit
inventory-manufacturing
Synthetic
true
As Of
2026-09-08
Rows
74

Binary jsonl: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
logistics
Industry
logistics
Source Kit
inventory-manufacturing
Synthetic
true
As Of
2026-09-08
Rows
74
Top Level
one object per line
Encoding
UTF-8
Line Endings
LF

Testing contract

Expected to pass
Scenario
Parse the file line by line as JSON and then try to parse the whole file as one document.
Expected result
Line-by-line parsing yields 74 objects, each with 8 keys, identical to the CSV rows. Parsing the whole file as a single JSON document fails at the start of line 2, which is the correct behaviour for newline-delimited JSON and the distinction this fixture exists to test.

What is a .jsonl file?

JSONL (JSON Lines) is a text format where each line is a complete, independent JSON value, allowing records to be streamed and appended without parsing the whole file. It is not itself a JSON array and each line must stand alone. It is common in logging, machine learning datasets, and data pipelines.

How to use this file

Use an example JSONL to test line-by-line streaming parsers, append-and-resume ingestion, and batch pipelines that process one record per line.

How to use this file for testing

“Pine Assembly Workshop: Shipment tracking events as newline-delimited JSON” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 74 rows · UTF-8 · LF. 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("tracking-events.jsonl") as f:
    rows = [json.loads(line) for line in f]
print(len(rows), rows[0])

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