GNSS and RTK receiver hardware
Positioning hardware should be specified around the required output and correction workflow. An RTK label alone does not describe the complete positioning system.
What to specify
Use these fields to describe your requirement. Values are supplied by the buyer or the responsible integrator; this reference does not list an in-stock SKU or a universally compatible replacement.
| Requirement | Information to include |
|---|---|
| Task | Mapping, navigation or time reference |
| Signals | Constellations/bands required |
| Corrections | Source and supported format |
| Output | Protocol, rate and interface |
| Antenna | Connector and matching requirements |
| Evidence | Accuracy test conditions and installation |
Sample and acceptance review
Request the receiver documentation and a full interface list. Evaluate the intended correction source and antenna as part of sample qualification.
A common purchasing mistake
A receiver specification is not the same as achieved survey accuracy for a finished aircraft.
Related purchasing decisions
RTK and PPK procurement questions
Positioning workflows differ in how correction data is delivered and used. A buyer should map the intended receiver, correction source and processing process before ordering.
Component sourcing for survey and mapping firms
Survey firms buy a reliable deliverable rather than a pile of sensors. Component procurement should preserve the relationship between camera, position, timing and processing.
Technical reading
The following independent resource provides technical context. The request fields and review notes on this page are AVDORS editorial procurement guidance, not a quotation of product specifications or a claim of manufacturer authorization.
Holybro hardware documentation