IDEA-001 — detector data and access matrix
Four-subject comparison separates displayed/decoded data, export interfaces and access rights; unknowns and partial captures retained.
Interpretation and date
Snapshot: 2026-10-09 America/Los_Angeles. All capability/interface/terms statements are vendor documentation unless labelled user context or analysis. Unknown means not established by this bounded, partly incomplete evidence set. No performance, access entitlement or field uptime was independently demonstrated. The user's co-founder relationship is accepted as context, not evidence of detector capabilities.14
The rows compare different observations: analog-video signal alerts and cooperative Remote ID records must not be treated as interchangeable drone tracks. Receipt of a signal, a coordinate in a broadcast and a surveyed receiver position have different meanings. Analysis: require a versioned field dictionary and sample before defining any common data contribution record.
Comparison
| Dimension | BlueBird / Chuyka | DroneSight | Dronetag | BlueMark / DroneScout |
|---|---|---|---|---|
| Observations | Analog-video RF detection and intercepted video viewing; signal presence does not establish a uniquely identified or geolocated aircraft.1718 | Standard broadcast Remote ID; host page expressly limits tracking to ASTM F3411 broadcasters.12 | Scout receives broadcast/direct Remote ID; no detection without those transmissions. Optional cooperative aircraft protocols are distinct.5 | Fixed receiver receives Bluetooth/Wi-Fi Remote ID; optional ADS-B/UAT aircraft inputs are distinct.8 |
| Documented data content | Displayed count/histogram, frequency/channel, signal level/RSSI, battery/mode; video output. Machine-readable observation fields not established.201718 | Map labels aircraft/operator locations, UAS ID, receiver and signal gaps. These controls are interface evidence, not an export schema or observed live dataset.4 | Product describes location, altitude, identification and pilot location; if unavailable, takeoff location is substituted. No evidence that that substitute is separately flagged in export.5 | Packet metadata and encoded payload are detailed below; do not treat receiver position as drone position.13 |
| Timestamps and uncertainty | No event time/clock or target positioning/uncertainty schema established. App approximate location policy is not a detector location field.23 | Timestamp field, clock basis, units, accuracy and positional uncertainty unresolved; map offers time filters.4 | Exact exported timestamp semantics, units and positional error/validity fields unresolved; REST requires query time bounds. GNSS is listed for Scout location.75 | See manual detail below. Encoded drone-position uncertainty fields were not inspected.13 |
| Interfaces | Video output, charging/power and Wi-Fi OTA documented; telemetry API/SDK/structured export unestablished.182022 | Wi-Fi upload and host map described; captured pages do not establish public API, bulk export or local raw feed.21 | Sensor raw feed, licensed Cloud/On-Premise interfaces; subscription table lists MQTT/webhook JSON. Authenticated REST, Socket.io recommendation and server push are documented.56710 | Fixed receiver MQTT JSON, optional SQLite Dashboard/Excel history; Bridge Bluetooth relay and UART MAVLink are separate products.89 |
| Samples/schema | No structured sample/schema established in inspected material. Both linked PDF manuals inaccessible.2425 | None in inspected pages; standard RID reference does not establish server output fields.1 | REST guide links API structures and DUMP; push docs name DUMP JSON/typed JSON. Full schema and sample payload not gathered within URL budget.711 | Manual message-field descriptions and linked reference subscriber exist; figure samples and underlying binary-member layouts are incomplete in capture.1312 |
| Retention | App policy gives necessity-based retention; detector observation/video history duration/export unknown.23 | Map offers 12h, 24h, 3d, 7d and custom controls. These do not prove server retention, completeness or export availability.4 | 12-month retention is listed for NRID Basic/Pro; applicability to receiver observation history is unestablished. Scout Cloud/On-Premise history exists, duration unresolved.65 | Optional local Dashboard stores history, but retention duration/deletion policy unresolved. MQTT retain configuration is not a historical database retention policy.813 |
| Quality/duplication/uptime | Monitor mode pauses scanning of the viewed band; threshold/filter/band settings change observations. False alarms acknowledged. No tested uptime/deduplication evidence.2120 | Homepage says observations are merged; no dedup algorithm or accuracy measure. Terms describe temperature, upload-error and Wi-Fi-RSSI diagnostics; hosts must maintain power/Wi-Fi. No SLA demonstrated.13 | 24/7 and latency claims are marketing specifications, not measured uptime. Push delivery controls exist; cross-sensor deduplication, false positives, clock quality and SLA unresolved.511 | Aggregation, batching and status messages documented below; cross-sensor deduplication and uptime SLA unresolved.13 |
| API/output limits | No telemetry API rate limits, buffering, loss/replay or access scope established in inspected documents.2022 | Request limits and download quotas unresolved. Host map access alone does not establish API entitlement.1 | REST airspace endpoints require time+bbox except operation-ID or UAS-ID exceptions; country/continent/world bbox prohibited. Numeric bbox/request quotas unresolved. Push target count is limited but number unspecified.710 | MQTT configuration governs publication; no hosted-network API quota evidenced.13 |
| Contributor visibility vs rights | Personal-use app license and own-data privacy rights do not establish pooling, redistribution or whole-network access.2223 | Active hosts get beta platform/premium visibility. Host terms assert DroneSight exclusive ownership of uploaded airspace data and its aggregation/display/publication rights. Host bulk/API/redistribution entitlement not established.123 | Personal tokens access account data; portal access requires Pro or cooperative business partner status. These are not evidence of unrestricted network access or resale/redistribution permission. Data-license terms not captured.710 | Local integration/reference code is evidenced; repository labels MIT code license. A code license does not establish rights to third-party observations; network-data entitlement and redistribution terms unresolved.812 |
Technical caveats that affect interpretation
- BlueBird 4.0 FAQ describes Monitor mode pausing its selected band; the example's band list does not fully match the four-band product specification. Confirm model/firmware behavior. App Wi-Fi connectivity or an OTA download is not evidence of observation upload.201822
- Dronetag's pilot-position description allows takeoff location as a substitute; export flags for that distinction were not established. Sensor+ is marketed as a plan but described elsewhere as future firmware. Receiver-history retention cannot inherit the NRID transmit-service retention statement.56
- BlueMark manual describes epoch-millisecond packet timestamps, but no onboard RTC: correct NTP or optional GNSS time is required. Sensor latitude/longitude is not drone latitude/longitude. Encoded drone-position members and positional uncertainty were not fully inspected. Latest-information aggregation/batching does not establish cross-sensor deduplication.13
- DroneSight map controls are interface evidence; dynamic observations, retention and bulk-access entitlements were not captured. Host terms' broad RF language does not establish detection beyond the host page's Remote ID restriction.423
See co-founder evidence, comparison detail and prioritized gaps. No numeric comparative range, economics or network coverage conclusion is drawn.
-
https://www.getdronesight.com/; 2026-10-10T04:54:52Z capture. How it works and FAQ. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩↩↩
-
https://www.getdronesight.com/host-a-receiver; 2026-10-10T04:55:00Z capture. The Receiver and How it works. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩
-
https://www.getdronesight.com/terms-of-service; 2026-10-10T04:55:00Z capture. August 2026 sections 2–4. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩
-
https://map.getdronesight.com/; 2026-10-10T04:55:01Z capture. Time/receiver filters, Flights counters and Signal gap legend. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩
-
https://www.dronetag.com/products/scout; 2026-10-10T04:55:28Z capture. Specifications and FAQs on licenses, modes, pilot position and compatibility. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩↩↩↩
-
https://www.dronetag.com/subscription; 2026-10-10T04:55:25Z capture. NRID Subscription and Scout Operating Modes. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩
-
https://help.dronetag.com/developers/data-pull/getting-started-rest/; 2026-10-10T04:55:26Z capture. Obtaining API Credentials, DUMP format and Conditions for Telemetry Request Parameters. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩↩
-
https://dronescout.co/dronescout-remote-id-receiver/; 2026-10-10T04:55:45Z capture. Introduction, Dashboard and Specifications. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩
-
https://dronescout.co/bridge/; 2026-10-10T04:55:46Z capture. Modes and FAQ. Vendor-authored evidence; capture limitations in source metadata. ↩
-
https://help.dronetag.com/developers/data-push/getting-started; 2026-10-10T05:31:20Z capture. How to Access the Integration Portal; What Can You Configure; Setting Up Your First Distribution Target. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩
-
https://help.dronetag.com/developers/data-push/protocols-and-formats; 2026-10-10T05:31:21Z capture. Compatibility Matrix, Portal Names, delivery controls, Metadata and Protocol Notes. Vendor-authored evidence; capture limitations in source metadata. ↩↩
-
https://github.com/BluemarkInnovations/RemoteID-MQTT-subscriber; 2026-10-10T05:31:22Z capture. README What is it, Configuration, Add-ons; file listing. Vendor-authored evidence; capture limitations in source metadata. ↩↩
-
https://download.bluemark.io/dronescout_sensor_manual_230.pdf; 2026-10-10T05:31:24Z capture; 2026-10-10T05:31:52Z capture; 2026-10-10T05:31:52Z capture. July 2026 v2.7; printed pp.29–35 and 43–50; PDF text page markers are zero-based, printed pages are one-based. Vendor-authored evidence; capture limitations in source metadata. ↩↩↩↩↩↩↩
-
Preserved user clarification; technical capabilities are not inferred from co-founder status. ↩
-
Immutable approved scope; execution gates recorded separately.
-
L109–141, L348–367, L567–569; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded.
-
Technical characteristics / Functions / Operating principle, L168–255; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩
-
Technical characteristics / Functions / package / FAQ, L187–247, L296–307, L331–334, L528–536; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩↩
-
Chuyka manual links, L121–171; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded.
-
FAQ displayed fields, modes and firmware, L190–258; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩↩↩
-
FAQ operation, charging and interference, L138–218; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩
-
Sections 1, 4–6; L95–163; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩↩
-
Sections 1.3, 5–6; L131–149, L188–204; capture 2026-10-10T05:31:45Z. Partial web text; HTML/assets excluded. ↩↩↩
-
Failed PDF download; capture 2026-10-10T05:31:46Z. Failed capture; no PDF contents inspected. ↩
-
Failed PDF download; capture 2026-10-10T05:31:46Z. Failed capture; no PDF contents inspected. ↩