Skip to content

Main content

Agricultural Map Crs Authority Pair Tool

Compare explicit CRS authority/code strings without projecting coordinates.

Loading tool…

Description

Require nonempty authority and code, compare both with expected values and encode [authority,code] as JSON text.

Farm data records connect field, event, sensor and source identifiers with observation and verification flags. Literal keys and supported-record shares help reconcile those records without authenticating a source, identifying a physical object or establishing measurement quality. Repeated IDs may need a different denominator from repeated rows.

Require nonempty authority and code, compare both with expected values and encode [authority,code] as JSON text.

When to use this tool

Use Agricultural Map Crs Authority Pair when checking the stated agricultural source, identity or record-support convention.

How to use the tool and how it works

  1. Enter authority, code, expectedAuthority, expectedCode. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read matches, key. Inspect matches before interpreting the associated values.

Require nonempty authority and code, compare both with expected values and encode [authority,code] as JSON text.1

Input fieldMeaning and unitsAccepted input
authorityAuthorityRequired. Text; maximum UTF-16 length 8192.
codeLiteral supplied code; no external registry lookup.Required. Text; maximum UTF-16 length 8192.
expectedAuthorityExpected AuthorityRequired. Text; maximum UTF-16 length 8192.
expectedCodeExpected CodeRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
matchesMatchesRequired. Boolean.
keyKeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "authority": "EPSG",
    "code": "4326",
    "expectedAuthority": "EPSG",
    "expectedCode": "4326"
  },
  "output": {
    "matches": true,
    "key": "[\"EPSG\",\"4326\"]"
  }
}

Limitations and assumptions

  • Literal CRS-label concordance does not validate the CRS or transform coordinates.
  • 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

Inspect original records, authoritative identifier schemes and calibrated measurements before merging data or drawing agricultural conclusions.

References

  1. Calculation and input contract: agroinformatics/agricultural-map-crs-authority-pair — tool.io

Similar or alternative tools