Screen occurrence records for exposed listed species
screen_exposureDo these occurrence records publish where a listed species lives too precisely? Occurrence records in one call, up to 5000: each record's species name and coordinates as published, optionally coordinateUncertaintyInMeters, a place, and what the file declares about the point (dataGeneralizations, informationWithheld, the eventID, locationID or locality it shares with other records, an iNaturalist export's coordinates_obscured, geoprivacy, public_positional_accuracy). Our engine's names screen answers as it answers a file dropped on passage-data.com: for each species a register lists, listed_by gives which register lists it (its status, whether it applies where the records are, the line the register prints) and exposure how many of its records sit at a coordinate finer than a 0.01 degree grid (about 1.1 km, precise enough to walk to), and how many of those a rounding would not protect because another record states the same position (withhold those). treatment is Chapman 2020's, GBIF's best practice for sensitive species: the category the data holder's documented answers to its questions reach (send them as determinations) with its grid, the Darwin Core terms to fill and how many records it would round and withhold; without answers, a coded refusal (sensitivity.criteria_unevaluated) naming the next question, beside what each category would do. A listing is not that determination. Every register screened is named with its edition: a species no register lists is a statement about those registers, never that it is unprotected. Nothing sent is kept.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"records": "<records>"
},
"name": "screen_exposure"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| place | No | ISO 3166 code of where the records are: a country (CA, US, FR, GB) or a subdivision (CA-QC, US-CA, GB-SCT). Omit it and the screen places them by their own points against public boundaries, and says so. | |
| records | Yes | The occurrence records, in order. Fields other than these are not read (their names are listed back in `query.fields_ignored`). | |
| determinations | No | The data holder's documented answers to Chapman 2020's questions, by number: {"1.1": true, "1.2": false, ...}. An answer without them lists every question in `treatment.questions`. |