Description
Qualify an explicit GNSS quality code by source.
Precision-agriculture records separate spatial reference versions, quality-code sources, calibration factors and target prescriptions. A cross-track error needs a directed planar line, while pulse counts require a compatible volume-per-pulse factor. Local map differences and overlap widths do not select a treatment, control machinery or establish positioning accuracy.
Qualify an explicit GNSS quality code by source.
When to use this tool
Use Gnss Fix Quality Source Code when you already have fixRecordId, qualityCode, codeSource and need to qualify an explicit GNSS quality code by source.
How to use the tool and how it works
- Enter fixRecordId, qualityCode, codeSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter fixRecordId, qualityCode, codeSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| fixRecordId | Fix Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| qualityCode | Quality Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| codeSource | Code Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"fixRecordId": "FIX17",
"qualityCode": "Q2",
"codeSource": "Receiver key A"
},
"output": {
"token": "[\"FIX17\",\"Q2\",\"Receiver key A\"]"
}
}Limitations and assumptions
- The result records supplied values without estimating positioning accuracy. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the original georeferenced map, calibrated meter and verified machine geometry for field decisions. A full guidance or application analysis must include coordinate system, path extent and equipment constraints beyond one signed offset or overlap width.
References
Similar or alternative tools
- Drone Ground Sample Unit
Preserve explicit image ground-sample distance text and unit.
- Soil Grid Sample Cell ID
Qualify an explicit soil-grid sample cell code by field and grid version.