Binary
BSON: Binary JSON (MongoDB)
The records as BSON: the binary-JSON encoding MongoDB stores documents in. For testing BSON decoders and JSON↔BSON conversion.
- File
- BSON · Binary · 5 rows
- Use case
- Conversion testing / Serialization testing
Equivalent data across serialization formats
Known records represented as JSON, MessagePack, CBOR, BSON, Protobuf, Arrow, and related formats for testing round trips, schema handling, type preservation, and binary decoders.
Each card starts with one representative test file. Choose a use case, search, or filter to find a specific profile; a card’s variant menu contains its related samples.
More filters and sorting
Results
38 test families · 143 available files · Page 1 of 3
P8 Convert
Convert v2 ORC Employee Table Source
Binary orc source for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-source.
- File
- ORC · P8 Convert · 5 rows
- Use case
- Conversion testing / Data engineering
P8 Convert
Convert v2 Protobuf Creator Record
Valid Protobuf wire record with string, uint32, and string fields for schema-guided decoding. Stable P8 artifact p8-convert-protobuf-source.
- File
- PB · P8 Convert · 3 fields
- Use case
- Conversion testing / Serialization testing
Precision
Coordinate Precision: 1 Decimal Place
The same harbour light written to 1 decimal place, enough to identify which country you are in. The ladder exists because coordinate precision is almost always chosen by accident, and shipping six unnecessary digits mult
- File
- GEOJSON · Precision · UTF-8
- Use case
- Geospatial / JSON parsing
Precision
Coordinate Precision: Float64 Round-Trip Hazards
Five features whose coordinates are the values that break naive JSON number handling: 17-significant-digit doubles, the classic 0.1 + 0.2 artefact, the largest float64 below 180, a 1e-7 offset, and coordinates written in
- File
- GEOJSON · Precision · UTF-8
- Use case
- Geospatial / JSON parsing
Captions Timelines Projects
Creator Timeline EDL 01
Download-only EDL timeline fixture 01 carrying a deterministic two-second edit reference without embedding playable media. Stable P8 artifact p8-video-timeline-edl-01.
- File
- EDL · Captions Timelines Projects
- Use case
- Timeline testing / Video editing
Captions Timelines Projects
Creator Timeline FCPXML 01
Download-only FCPXML timeline fixture 01 carrying a deterministic two-second edit reference without embedding playable media. Stable P8 artifact p8-video-timeline-fcpxml-01.
- File
- FCPXML · Captions Timelines Projects
- Use case
- Timeline testing / Video editing
Captions Timelines Projects
Creator Timeline OTIO 01
Download-only OTIO timeline fixture 01 carrying a deterministic two-second edit reference without embedding playable media. Stable P8 artifact p8-video-timeline-otio-01.
- File
- OTIO · Captions Timelines Projects
- Use case
- Timeline testing / Video editing
Imaging
DICOM-Shaped Part 10 File: Explicit VR, Synthetic Phantom (.bin)
A DICOM Part 10 file built byte by byte: 128-byte preamble, the DICM magic, an explicit-VR file meta group and a 27-element dataset ending in 16-bit pixel data. Every identifier is invented: the patient name is SYNTHETIC
- File
- BIN · Imaging · 32 rows
- Use case
- Scientific data / Serialization testing
Wkt Wkb
EWKB: PostGIS Hex With an Embedded SRID
PostGIS EWKB, where the SRID is carried by OR-ing 0x20000000 into the geometry-type word and appending the code. A strict OGC WKB reader sees type 0x20000001 instead of 1 and either fails or, worse, reports an unknown ge
- File
- TXT · Wkt Wkb · 2 records
- Use case
- Geospatial / Serialization testing
Wkt Wkb
EWKT: PostGIS Extended WKT With an SRID Prefix
PostGIS's extended WKT, which prefixes the geometry with `SRID=4326;`. It is not part of the OGC standard, so a strict WKT parser rejects the whole string, while a PostGIS-aware one gets the coordinate system for free.
- File
- WKT · Wkt Wkb · ASCII
- Use case
- Geospatial / Serialization testing
Fits
FITS BINTABLE: Typed Columns with TUNIT (.fits)
A FITS binary table with four typed columns, big-endian numerics packed with no inter-field padding and TUNIT declaring milli-jansky on the two flux columns. It is the fixture for a table reader that has to build a row s
- File
- FITS · Fits · 12 rows
- Use case
- Scientific data / Serialization testing
Fits
FITS BLANK: Undefined Integer Pixels (.fits)
Integer FITS images mark undefined pixels with the BLANK keyword, and BLANK is compared against the stored value before BZERO and BSCALE are applied. Scale first and the four undefined pixels turn into a perfectly plausi
- File
- FITS · Fits
- Use case
- Scientific data / Serialization testing
Fits
FITS with World Coordinate System: Tangent Plane (.fits)
A 32-bit integer image carrying a complete tangent-plane WCS: 1-based CRPIX reference pixels, a deliberately negative CDELT1 so right ascension runs the other way, and an ICRS frame. It targets the two mistakes every WCS
- File
- FITS · Fits
- Use case
- Scientific data / Serialization testing
Gettext
gettext MO with Plural-Forms: Arabic (compiled)
The compiled Arabic MO twin. Plural entries are encoded the way msgfmt does it (the original is 'singular\\0plural' and the translation is the 6 forms joined by NUL), and the header entry carries the Plural-Forms express
- File
- MO · Gettext · Arabic
- Use case
- Internationalization / Serialization testing
Hdf5
HDF5 Chunked + gzip + shuffle Filters (.h5)
One array stored twice in the same file: chunked with the shuffle and gzip filters applied, and contiguous with no filters at all. Comparing the two proves a reader ran the HDF5 filter pipeline rather than reading raw ch
- File
- H5 · Hdf5
- Use case
- Scientific data / Serialization testing
Hdf5
HDF5 Compound Record dtype: Mixed Field Types (.h5)
A compound-dtype dataset mixing an integer key, two float measurements, a fixed-width byte string and a boolean flag in a single record. It is the fixture for readers that must map an HDF5 record type onto a native struc
- File
- H5 · Hdf5 · 10 records
- Use case
- Scientific data / Serialization testing
Hdf5
HDF5 Deeply Nested Group Tree: Eight Levels (.h5)
Eight levels of nested groups, each holding a dataset whose values equal its own depth. Any tree walk that caps recursion depth or flattens names silently loses the lower levels, and the depth-valued arrays make that imm
- File
- H5 · Hdf5
- Use case
- Scientific data / Serialization testing