What a GBIF occurrence map shows

Three counts answer different questions. The source-record count concerns the whole query. Map aggregates group records for display at the selected scale. Loaded details are the part of the result currently retrieved. A list of one hundred rows does not mean there are only one hundred observations worldwide. Read the query conditions and the counter's explanation together.

Many records in one area can reflect more collecting or reporting rather than more organisms. A blank area does not establish absence. Comparing abundance or changes over time requires information about how and where people searched, which ordinary occurrence records may not provide.

Quality flags help locate questionable coordinates, but need interpretation. GBIF distinguishes issues such as invalid coordinates, a 0/0 location and a mismatch between country and coordinates. Known uncertainty is separate information. A hidden or generalized location should not be turned into an invented precise address.

Try a fixed query

Worked example: open Picea glauca in the EcoGenesis atlas and keep the species identity fixed. Choose a country and year range; note whether records without dates are included. Compare the query total, displayed map aggregates and rows loaded for one area. Open one original record and write down its dataset, basis of record, event date, coordinate uncertainty and licence. Record the query settings before comparing another area; do not treat a denser display as a population estimate.

Add a molecular relationship

Now require a linked protein record. The map concerns organisms with a confirmed molecular relationship in EcoGenesis. A particular marker is not thereby a sequenced sample. Save the query and area, restore the research and check that the same conditions return.

Check the conclusion

Check your understanding. An empty area can mean a lack of matching published data. A denser map for a later year can reflect changes in recording. Neither alone establishes population decline or growth.

Views of one query

Different views of the same query conditions; loaded rows do not measure total coverage.

Suppose a fixed query matches 2,400 published records, the current map groups them into 12 displayed aggregates, and the detail list has loaded 100 rows. These invented numbers mean three things: 2,400 matches to this query, 12 display groups at this scale, and 100 details currently available to inspect. They describe neither 12 organisms nor 100 records worldwide. Even with equal query settings, a denser map alone does not establish greater abundance. Replace the teaching values with the live counters when you run your own query.