Skip to content

Main content

Conservation Record Precision Redaction

Truncate explicit public-record coordinates toward zero to a supplied decimal precision; this reduces precision but does not guarantee location confidentiality.

Loading tool…

Description

Truncate supplied latitude and longitude for public display.

Conservation observations depend on sampling effort, specimen provenance, spatial precision and the population being assessed. Survivors among assessed plants differ from survivors among all planted plants. Coordinate rounding or cell assignment changes a display location without guaranteeing protection, and a time-gap threshold does not establish independent observations.

Truncate supplied latitude and longitude for public display.

When to use this tool

Use Conservation Record Precision Redaction when you already have latitude, longitude, publicDecimalPlaces and need to truncate supplied latitude and longitude for public display.

How to use the tool and how it works

  1. Enter latitude, longitude, 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 publicLatitude, publicLongitude. Use the output convention below.

Require latitude in [-90,90], longitude in [-180,180] and whole decimal places 0..6; apply Math.trunc(value*10^places)/10^places to each.1

Input fieldMeaning and unitsAccepted input
latitudeLatitudeRequired. Finite number; minimum -90; maximum 90.
longitudeLongitudeRequired. Finite number; minimum -180; maximum 180.
publicDecimalPlacesWhole count 0..6; coordinates are truncated toward zero rather than rounded.Required. Safe integer; minimum 0; maximum 6.
Output fieldInterpretationReturned shape
publicLatitudePublic LatitudeRequired. Finite number.
publicLongitudePublic LongitudeRequired. Finite number.
json
{
  "input": {
    "latitude": 12.34567,
    "longitude": -45.67891,
    "publicDecimalPlaces": 2
  },
  "output": {
    "publicLatitude": 12.34,
    "publicLongitude": -45.67
  }
}

Limitations and assumptions

  • Truncation is toward zero, not nearest rounding. It does not secure underlying coordinates, guarantee sufficient obscurity, transform a datum or establish publication permission.
  • 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 original field records, specimens, survey design and location-access requirements. Use the complete ecological and spatial method for population or protection decisions; local rates, interval flags and source-qualified labels do not supply it.

References

  1. Calculation and input contract: conservation-biology/conservation-record-precision-redaction — tool.io

Similar or alternative tools