RadioHound

RadioHound data format for spectrum monitoring

*.rh.json

Validate

Check your file against this schema

Opens the validator with this schema already loaded. Paste your *.rh.json and it validates in your browser — nothing is uploaded.

Validate a *.rh.json → View raw schema

Reference

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field	Type	Description
`data`required	`string`	—
`gain`required	`number`	—
`latitude`required	`number`	The latitude where the data was captured, in decimal degrees
`longitude`required	`number`	The longitude where the data was captured, in decimal degrees
`mac_address`required	`string`	MAC address of the device, without separators
`metadata`required	`object`	Metadata for a RadioHound capture.
`metadata.data_type`required	`string`	Data types supported by RadioHound. one of: `"periodogram"`
`metadata.fmax`required	`integer`	The maximum frequency in the sample
`metadata.fmin`required	`integer`	The minimum frequency in the sample
`metadata.gps_lock`required	`boolean`	Whether a GPS satellite lock is obtained, otherwise the last known coordinates
`metadata.nfft`required	`integer`	Number of FFT bins, recommended to be a power of 2
`metadata.scan_time`required	`number`	The time taken to scan this sample, in seconds
`metadata.xcount`deprecated	`anyOf`	[Deprecated] The number of points in the periodogram default: `null`
`metadata.xstart`deprecated	`anyOf`	[Deprecated] The start frequency of the periodogram default: `null`
`metadata.xstop`deprecated	`anyOf`	[Deprecated] The stop frequency of the periodogram default: `null`
`metadata.archive_result`	`anyOf`	Whether the data was archived default: `null`
`sample_rate`required	`integer`	Sample rate of the capture, in Hz
`short_name`required	`string`	The short name of the device
`timestamp`required	`string`	Timestamp of the capture start, as ISO 8601 with timezone information
`type`required	`string`	Numpy-compatible dtype of `data` elements
`version`	`string`	Version of the RadioHound data format default: `"v0"`
`altitude`	`anyOf`	The altitude where the data was captured, in meters default: `null`
`center_frequency`	`anyOf`	The center frequency of the capture, calculated as the mean of the start and end frequencies default: `null`
`custom_fields`	`object`	Custom fields that are not part of the standard schema
`hardware_board_id`	`anyOf`	The hardware board ID of the device capturing the data default: `null`
`hardware_version`	`anyOf`	The hardware version of the device capturing the data default: `null`
`scan_group`	`anyOf`	The scan group, used to group RH files. UUID version 4 as a 36 char string (with dashes). default: `null`
`software_version`	`anyOf`	The software version of the device capturing the data default: `null`
`batch`deprecated	`anyOf`	[Deprecated \| Use scan_group instead] Can be used to group scans together. default: `null`
`suggested_gain`deprecated	`anyOf`	[Deprecated] Suggested gain for the device default: `null`
`uncertainty`deprecated	`anyOf`	[Deprecated] Uncertainty of the measurement default: `null`
`requested`	`anyOf`	Attributes set by requestor default: `null`

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
32 properties, 94% carrying a description, max nesting depth 7.

Standards

Specification sections for the keywords in this schema

Keyword	Document	Section
`$defs`	JSON Schema Core, draft 2020-12	§8.2.4 — Schema Re-Use With "$defs"
`$id`	JSON Schema Core, draft 2020-12	§8.2.1 — The "$id" Keyword
`$ref`	JSON Schema Core, draft 2020-12	§8.2.3.1 — Direct References with "$ref"
`$schema`	JSON Schema Core, draft 2020-12	§8.1.1 — "$schema"
`additionalProperties`	JSON Schema Core, draft 2020-12	§10.3.2.3 — "additionalProperties"
`anyOf`	JSON Schema Core, draft 2020-12	§10.2.1.2 — "anyOf"
`default`	JSON Schema Validation, draft 2020-12	§9.2 — "default"
`deprecated`	JSON Schema Validation, draft 2020-12	§9.3 — "deprecated"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`enum`	JSON Schema Validation, draft 2020-12	§6.1.2 — "enum"
`exclusiveMaximum`	JSON Schema Validation, draft 2020-12	§6.2.3 — "exclusiveMaximum"
`exclusiveMinimum`	JSON Schema Validation, draft 2020-12	§6.2.5 — "exclusiveMinimum"
`format`	JSON Schema Validation, draft 2020-12	§7 — Vocabularies for Semantic Content With "format"
`maxLength`	JSON Schema Validation, draft 2020-12	§6.3.1 — "maxLength"
`properties`	JSON Schema Core, draft 2020-12	§10.3.2.1 — "properties"
`required`	JSON Schema Validation, draft 2020-12	§6.5.3 — "required"
`type`	JSON Schema Validation, draft 2020-12	§6.1.1 — "type"
`format: "date-time"`	RFC 3339	§5.6 — Internet Date/Time Format

Documents

JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.

Source

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas