Skip to content

Main content

Occurrence Coordinate Precision Label

Label explicitly supplied occurrence uncertainty and public coordinate precision without treating decimal places as measured accuracy.

Loading tool…

Description

Label supplied occurrence uncertainty and a proposed public precision.

Biodiversity records distinguish surveyed sites, nondetection, counts, sampling units, voucher references and source-qualified taxonomic states. A coordinate-precision label changes metadata rather than protecting a location. Relative abundance and mean count per represented unit depend on their supplied denominators and survey scope.

Label supplied occurrence uncertainty and a proposed public precision.

When to use this tool

Use Occurrence Coordinate Precision Label when you already have occurrenceId, uncertaintyMeters, publicDecimalPlaces and need to label supplied occurrence uncertainty and a proposed public precision.

How to use the tool and how it works

  1. Enter occurrenceId, uncertaintyMeters, publicDecimalPlaces. 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 label. Use the output convention below.

Require nonempty occurrenceId, uncertaintyMeters>=0 and publicDecimalPlaces a whole 0..15; append both values in a label.1

Input fieldMeaning and unitsAccepted input
occurrenceIdOccurrence IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
uncertaintyMetersUncertainty MetersRequired. Finite number; minimum 0.
publicDecimalPlacesWhole label annotation 0..15; no coordinate is rounded or redacted.Required. Safe integer; minimum 0; maximum 15.
Output fieldInterpretationReturned shape
labelLabelRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "occurrenceId": "O17",
    "uncertaintyMeters": 100,
    "publicDecimalPlaces": 3
  },
  "output": {
    "label": "O17; uncertainty=100 m; public decimal places=3"
  }
}

Limitations and assumptions

  • The tool does not round or remove coordinates, estimate uncertainty, enforce disclosure policy or guarantee location privacy.
  • 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review specimens, original observations, sampling design and controlled taxonomic sources. Use complete detection, population and spatial methods when a local count fraction, source label or precision bin cannot answer the ecological or disclosure question.

References

  1. Calculation and input contract: biodiversity/occurrence-coordinate-precision-label — tool.io

Similar or alternative tools