Example report · Public data
A reproducible first-page audit of GBIF occurrence records matched to Türkiye. This is an early demonstration of evidence checks, not a model, suitability map or conservation assessment.
Discuss a pilotFirst 300 API results out of 950 reported matches. These signals call for review; they are not automatic exclusions.
Inspect the complete example reportWhat the sample shows
300 of 300 sampled records have coordinates, but 37 lack a stated coordinate-uncertainty value. 18 report uncertainty above 10 km. 245 carry GBIF’s coordinate-rounded flag. Rounded coordinates can reflect source handling and should be interpreted with the original dataset.
262 of 300 records come from one dataset in this first-page sample. This is not evidence of ecological sampling bias by itself, but it means independence and spatial coverage should be checked before modelling.
The sampled records span 2019–2026; 0 lack an event date. 1 has a continent–coordinate mismatch flag. Each flag needs record-level review before deciding whether to retain or exclude a record.
Method & provenance
This fixed snapshot was retrieved 9 October 2026 from the GBIF Occurrence Search API using the accepted taxon key 8225376, country code TR, offset 0 and limit 300. GBIF reported 950 matches at retrieval. The API’s first page is not a random or representative sample, and counts can change as GBIF updates.
We counted coordinate and event-date completeness, reported coordinate uncertainty, selected GBIF issue flags and the largest dataset contribution. We have not checked taxonomic identifications, duplicate events, sampling effort, environmental layers or model performance. Full research use would require a defined download, citation, licences, spatial review and expert decisions.
Example records for inspection:
GBIF’s issue-flag definitions explain how to interpret these signals.