Datasets:

NewSpaceMarket
/

mrd

license: cc-by-4.0
language:
  - en
tags:
  - spacecraft
  - satellite
  - cubesat
  - smallsat
  - engineering
  - components
  - datasheets
  - aerospace
pretty_name: NewSpace Market MRD — machine-readable spacecraft component specifications
size_categories:
  - 10K<n<100K
task_categories:
  - table-question-answering
  - feature-extraction
configs:
  - config_name: values
    data_files: mrd-values.csv
  - config_name: products
    data_files: mrd-products.csv
  - config_name: properties
    data_files: mrd-properties.csv

NewSpace Market MRD

Typed, datasheet-sourced specifications for 2,486 spacecraft flight hardware products across 24 categories — reaction wheels, star trackers, propulsion, radios, antennas, structures, ground stations and more — with 19,011 values, each citing the vendor datasheet page it came from.

The dataset exists because component selection is a task where a language model must not improvise: a wheel that cannot take a 12 V bus is not a "close enough" answer. Three rules make the data safe to compute on.

Nothing is guessed. A missing property means the vendor does not publish it. The record is absent rather than filled with a typical value.
Conditions are kept apart. Idle, steady-state and peak power are separate rows, each with its measurement condition. They are never averaged into one number.
Every value is traceable. Source file and page, plus a confidence level: L0 machine-extracted, L1 verified by a human against the vendor datasheet.

Files

File	One row is	Rows
`mrd-values.csv`	one measured value	19,011
`mrd-products.csv`	one product	2,486
`mrd-properties.csv`	one property in the dictionary	111
`mrd-full.json`	everything, nested by product	—

Columns of `mrd-values.csv`

Column	Meaning
`product_id`, `product_name`, `category`	which item the value belongs to
`prop`	property key; see `mrd-properties.csv` for its label and canonical unit
`num`, `num_max`	the figure; both are filled when the vendor published a range
`text`	for non-numeric properties: interface, band, material, heritage
`unit`	canonical unit, converted by code (kg→g, dBm→W, psi→bar, tf→mN)
`bound`	`min`, `typical`, `max`, `range`, `nominal` — which end of the spec this is
`condition`	measurement condition as printed, e.g. "at 4200 rpm", "Ka-band"
`source`	`datasheet <file> p.N`, `vendor product page`, or `product description`
`confidence`	`L0` machine-extracted · `L1` human-verified

Live data and tools

The snapshot here is dated; the layer grows weekly. For current data:

Reverse search — pass requirements, get candidates grouped A (meets all) / B (fails a named requirement, both figures quoted) / C (data missing, fields named): https://newspacemarket.com/mrd-connect/match?category=reaction-wheels&momentum_min=0.2&bus_v=12
Full category dump — https://newspacemarket.com/mrd-connect/specs?category=star-trackers
MCP server for AI assistants — https://newspacemarket.com/mrd-connect/mcp (also in the official MCP registry as io.github.newspacemarket-com/mrd)
OpenAPI 3.1 — https://newspacemarket.com/mrd-connect/openapi.json
Code, schema and examples — https://github.com/newspacemarket-com/mrd

How it was built

Values are extracted from vendor datasheets (text, and page images for scanned documents), from vendor product pages and from product descriptions — the source column says which. Unit conversion is done in code, not by a model. A validation pass rejects any figure whose unit does not match the property, and an outlier scan flags values far from the category median for human review.

Limitations

Coverage is not exhaustive: where a vendor publishes nothing machine-readable, the product is not here. Most rows are L0 — machine-extracted and not yet checked by a person. Values are provided as-is; verify against the vendor datasheet before committing to a design.

Licence and attribution

CC BY 4.0. Attribution: NewSpace Market — https://newspacemarket.com