IDEA-001 — bounded comparison evidence

Documented data and access differences for DroneSight, Dronetag and BlueMark, with explicit schema and rights gaps.

Research FindingsDraft record

Basis and interpretation

Research date: 2026-10-09 America/Los_Angeles. This bounded follow-up reuses RES-001 captures from the same day, with four new public URLs. It covers official documentation for three comparisons; every product/interface/terms statement below is a vendor statement. No independent performance, uptime, data-quality, or rights verification was obtained. Unknown means unresolved in the inspected evidence, not a claim that a feature or permission does not exist. Capture manifest records exact files and the reported global URL-limit deviation.

Evidence for the consolidated matrix

Dimension	DroneSight	Dronetag	BlueMark / DroneScout
Observations	Standard broadcast Remote ID; host page expressly limits tracking to ASTM F3411 broadcasters.¹²	Scout receives broadcast/direct Remote ID; no detection without those transmissions. Optional cooperative aircraft protocols are distinct.⁵	Fixed receiver receives Bluetooth/Wi-Fi Remote ID; optional ADS-B/UAT aircraft inputs are distinct.⁸
Documented data content	Map labels aircraft/operator locations, UAS ID, receiver and signal gaps. These controls are interface evidence, not an export schema or observed live dataset.⁴	Product describes location, altitude, identification and pilot location; if unavailable, takeoff location is substituted. No evidence that that substitute is separately flagged in export.⁵	Packet metadata and encoded payload are detailed below; do not treat receiver position as drone position.¹³
Timestamps and uncertainty	Timestamp field, clock basis, units, accuracy and positional uncertainty unresolved; map offers time filters.⁴	Exact exported timestamp semantics, units and positional error/validity fields unresolved; REST requires query time bounds. GNSS is listed for Scout location.⁷⁵	See manual detail below. Encoded drone-position uncertainty fields were not inspected.¹³
Interfaces	Wi-Fi upload and host map described; captured pages do not establish public API, bulk export or local raw feed.²¹	Sensor raw feed, licensed Cloud/On-Premise interfaces; subscription table lists MQTT/webhook JSON. Authenticated REST, Socket.io recommendation and server push are documented.⁵⁶⁷¹⁰	Fixed receiver MQTT JSON, optional SQLite Dashboard/Excel history; Bridge Bluetooth relay and UART MAVLink are separate products.⁸⁹
Samples/schema	None in inspected pages; standard RID reference does not establish server output fields.¹	REST guide links API structures and DUMP; push docs name DUMP JSON/typed JSON. Full schema and sample payload not gathered within URL budget.⁷¹¹	Manual message-field descriptions and linked reference subscriber exist; figure samples and underlying binary-member layouts are incomplete in capture.¹³¹²
Retention	Map offers 12h, 24h, 3d, 7d and custom controls. These do not prove server retention, completeness or export availability.⁴	12-month retention is listed for NRID Basic/Pro; applicability to receiver observation history is unestablished. Scout Cloud/On-Premise history exists, duration unresolved.⁶⁵	Optional local Dashboard stores history, but retention duration/deletion policy unresolved. MQTT retain configuration is not a historical database retention policy.⁸¹³
Quality/duplication/uptime	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.¹³	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.⁵¹¹	Aggregation, batching and status messages documented below; cross-sensor deduplication and uptime SLA unresolved.¹³
API/output limits	Request limits and download quotas unresolved. Host map access alone does not establish API entitlement.¹	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.⁷¹⁰	MQTT configuration governs publication; no hosted-network API quota evidenced.¹³
Contributor visibility vs rights	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.¹²³	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.⁷¹⁰	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.⁸¹²

Dronetag push detail

Push supports HTTP webhook, MQTT, TCP and UDP; DUMP typed JSON adds $type. MQTT topics may route UA/operator/system telemetry and operation updates by message type. Optional payload wrapping uses data and metadata; HTTP metadata can include message type, integration client ID and public-data visibility. The selected data source governs eligible messages before conversion. Throttling trades delivery rate for latency; reliability controls govern undelivered messages, and empty payloads can provide periodic activity without new telemetry. These controls do not prove field completeness, exact delivery guarantees, deduplication, or a redistribution grant.¹¹

BlueMark manual detail

The July 2026 v2.7 manual describes MQTT packet fields: sensor ID, RSSI, channel, epoch-millisecond timestamp, MAC address, transport type, optional base64 raw air payload, and base64 Open Drone ID UASdata with validity flags. Optional LTE/GNSS location messages identify the sensor using latitude/longitude in decimal degrees and MSL altitude. Drone-position member layouts and numeric uncertainty remain uninspected. Status includes firmware/model and license state; invalid license suppresses data. No onboard RTC is provided: NTP or optional GNSS must set time; incorrect system time makes local timestamps wrong. Aggregation retains the latest information elements, while mode 2 batches received messages. Neither documents cross-receiver deduplication. QoS and MQTT retain are configurable; historical retention is unspecified. The configuration allows 50–60000 ms batching, while prose says 250–60000 ms. Mode-1 cadence wording also varies. Confirm firmware behavior before relying on a rate. Sample figures are absent from the text captures.¹³

Contradictions, limitations and next evidence

DroneSight terms use broader RF-telemetry language than the host page's ASTM restriction; a public map shell also coexists with host-exclusive beta access wording. Neither establishes broader detection or public database access.³²¹⁴

Dronetag lists Sensor+ as an operating plan while Scout FAQ calls it future firmware. Its general NRID retention promise must not be transferred to receiver data. Confirm mode/version availability and receiver-specific retention.⁶⁵

Analysis: prioritize a versioned, annotated sample and field dictionary; distinguish reception time, drone-reported time and ingestion time, receiver/drone/operator/takeoff positions, null/invalid/stale flags and uncertainty. Then request cross-node duplicate handling, loss/replay behavior, retention/deletion rules, visibility and explicit API/bulk/redistribution entitlements. These are requirements for clarifying the proposed contribution model, not established capabilities of the co-founder detector. No permission or legal conclusion is inferred from a documentation gap.

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. ↩↩↩↩↩↩↩

Sources, provenance and record details

Record type: Research Findings
Status: draft
Generated: by: codex/researcher at: '2026-10-10T05:33:40.993067+00:00'
Recorded checks: No verification metadata recorded.

Sources

All record metadata

type: Research Findings
title: IDEA-001 — bounded comparison evidence
description: Documented data and access differences for DroneSight, Dronetag and BlueMark,
  with explicit schema and rights gaps.
status: draft
generated:
  by: codex/researcher
  at: '2026-10-10T05:33:40.993067+00:00'
sources:
- id: ds-home
  resource: /references/SRC-81dda2b1dc72/source.md
  title: DroneSight home
- id: ds-host
  resource: /references/SRC-87920e76e95d/source.md
  title: DroneSight host a receiver
- id: ds-terms
  resource: /references/SRC-726546dae9a6/source.md
  title: DroneSight receiver host terms August 2026
- id: ds-map
  resource: /references/SRC-680827a4e27f/source.md
  title: DroneSight map
- id: dt-scout
  resource: /references/SRC-148960c5f336/source.md
  title: Dronetag Scout
- id: dt-sub
  resource: /references/SRC-0a9c88d8051c/source.md
  title: Dronetag subscriptions
- id: dt-api
  resource: /references/SRC-6a2cbcb96b02/source.md
  title: Dronetag REST API getting started
- id: bm-fixed
  resource: /references/SRC-52f606be7f06/source.md
  title: DroneScout fixed Remote ID receivers
- id: bm-bridge
  resource: /references/SRC-4be3f6ae6cac/source.md
  title: DroneScout Bridge
- id: dt-push
  resource: /references/SRC-235e7bcca8a0/source.md
  title: Dronetag data push getting started
- id: dt-formats
  resource: /references/SRC-fc68e3dfd51f/source.md
  title: Dronetag data push protocols and formats
- id: bm-repo
  resource: /references/SRC-a618bd384de5/source.md
  title: BlueMark RemoteID MQTT subscriber repository
- id: bm-manual
  resource: /references/SRC-89399f9304c8/source.md
  title: DroneScout receiver manual 230 240 series