Open data

The requirements database and the roaming ranges, as files you can download and build on. Free to reuse under CC BY 4.0.

Version: 2026-10-05
Entries: 13
Sourced values: 199
Roaming ranges: 7

Downloads

Every value carries its source address and the date it was read. The files hold published entries only, the same ones the requirements database shows. The version is the latest date anywhere in the data, so the same data always has the same version.

File	Rows	Size	SHA-256
requirements.jsonRequirements database (JSON)	13	138.0 KB	8ef97d0d23b2baf7cbb25c7f68d5a0fa1b5bd86258ee4943bd0d411883fe7683
requirements-parameters.csvRequirements: one row per value (CSV)	199	118.2 KB	76e880f2a9051343b30940e16439a8089a12a287e6e866ddc114a51bab89a70d
requirements-entries.csvRequirements: one row per entry (CSV)	13	7.5 KB	93e4df389893bcf6bc6f6c2fdf4ee7af760f19bb4b5484e9f0d26f356ea5fc57
roam-methods.jsonRoaming interruption ranges (JSON)	7	10.1 KB	5f0243a74569926d26d23523a4b464fc5c19f0362d908b8e39b2f7cde8073247
roam-methods.csvRoaming interruption ranges (CSV)	7	7.3 KB	937b0edc45d5cf49e86fad3ff6ce44e71b182748dbfe9385ec0bb63af704d318
datapackage.jsonData package descriptor (Frictionless)	5	8.5 KB	96fbab257330b6af779c548ce44b440de6f207f59180903464b40fc367952357

What is not included

The files hold the values and their sources. They leave out the review notes behind each page, drafts that have not been approved, and the field guide's prose.

Using the files

The JSON files wrap the records with the license, the version, a count, and a SHA-256 hash of the records, so you can tell when the data changed. The data package descriptor lists every file with its size, hash, and fields, in the Frictionless Data format.

The CSV files are UTF-8 with a byte order mark, so a spreadsheet reads accented characters correctly. Every field is quoted. A text cell that starts with =, +, - or @ and is not a number begins with an apostrophe, so a spreadsheet cannot run it as a formula. Numbers such as -70 stay numbers.

Any site may fetch the files from a browser: the server allows cross-origin requests to /data/v1/. Field names are stable within a version of the schema. A change to them is listed below and raises theschema_version in the JSON.

Fields

Values (one row per value)

requirements-parameters.csv; in requirements.json, each record’s parameters

Field	Type	Meaning
entry_id	string	The entry this value belongs to; its page is /requirements/<entry_id>/.
entry_kind	string	protocol or device.
vendor	string	The maker or standards body.
model_or_version	string	The model, series, or specification version the value applies to.
parameter	string	What the value is, in plain words.
value	string	The value as the source states it. "Not published by the vendor" means the sources were checked and give none.
unit	string	The unit, where the value is a number.
condition	string	When the value applies, or what qualifies it.
category	string	For device values: bands-channels, min-signal, roam-time, fast-roaming, latency-loss, throughput, security, ports, loc-behavior, loc-timeout, or other.
source_url	string	The public document the value comes from.
source_title	string	The document's title.
source_date	string	The document's own date or revision, where it states one.
locator	string	Where in the document: section, table, or page.
accessed	date	The date the document was read.
entry_url	string	The entry's page on otwireless.com.

Entries (one row per protocol or device)

requirements-entries.csv; in requirements.json, the record fields

Field	Type	Meaning
id	string	Stable identifier; the page is /requirements/<id>/.
kind	string	protocol or device.
title	string	The entry's title.
vendor	string	The maker or standards body.
model_or_version	string	The model, series, or specification version.
last_verified	date	The date the entry's sources were last checked.
parameter_count	integer	How many sourced values the entry has.
loss_of_comms_behavior	string	What the vehicle does when it loses the network, as its maker states it.
loss_of_comms_timeout	string	How long before it acts.
loss_of_comms_recovery	string	How it recovers.
loss_of_comms_source_url	string	The source for the three loss-of-comms fields.
top_speed	string	The vehicle's top speed as its maker states it.
top_speed_source_url	string	The source for the top speed.
url	string	The entry's page on otwireless.com.

Roaming ranges

roam-methods.csv and roam-methods.json

Field	Type	Meaning
id	string	Stable identifier for the roaming method.
label	string	The roaming method.
min_ms	number	Low end of the typical interruption, in milliseconds. Empty where no source supports a range.
max_ms	number	High end of the typical interruption, in milliseconds. Empty where no source supports a range.
kind	string	standard, vendor-claim, or draft.
note	string	What the range rests on, and its limits.
source_urls	string	The sources, separated by " \| ".
source_publishers	string	Their publishers, in the same order, separated by " \| ".

License and attribution

The data is licensed under Creative Commons Attribution 4.0 International. You may copy, change, and build on it, including commercially, if you credit it. Credit it as: OT Wireless (otwireless.com), Ben Rutter, CC BY 4.0, with a link to this page.

The values come from makers' and standards bodies' public documents, linked on every row. The license covers this compilation. The source documents keep their own terms.

How to cite

Rutter, B. (2026). OT Wireless open data (version 2026-10-05) [Data set]. OT Wireless. https://otwireless.com/data/

@misc{rutter20261005otwdata,
  author = {Rutter, Ben},
  title = {{OT Wireless open data}},
  year = {2026},
  version = {2026-10-05},
  howpublished = {\url{https://otwireless.com/data/}},
  note = {Data set, CC BY 4.0},
}

Changes

Oct 5, 2026: First release. The requirements database (entries and values) and the typical roaming interruption ranges, as JSON and CSV, with a data package descriptor.

Report an error

If a value is wrong or out of date, send Ben the entry and the document that shows it on LinkedIn. Corrections are made in the database, and the next build updates the files and the version. The transparency index shows which values each robot maker publishes.