IMPORTANT INFORMATION — NBN Atlas

Release of a new tool - the Temporal map tool

null@example.com (r.stock) — Wed, 11 Feb 2026 11:16:52 +0000

Dear NBN Forum users,

We would like to inform you of the release a of new feature to the NBN Atlas, the Temporal map tool. This new tool allows users to explore records across years and the meteorological seasons. This will be useful for visualising how records change over time. The tool is integrated into the Interactive map (https://docs.nbnatlas.org/viewing-speci … -on-a-map/).

If you're able to, it would be helpful if you can have a go at using the tool and provide any feedback you have, both positive and negative. This can help us with further developing the tool or similar tools in the future.

Here is the guidance for using the new tool - https://docs.nbnatlas.org/temporal-map-tool/

If you have any questions, please do not hesitate to ask.

Thank you.

Kind regards,
Rhiann

UKSI updated February 2026

null@example.com (r.stock) — Wed, 11 Feb 2026 10:55:08 +0000

Dear NBN Atlas users,

We would like to inform you that the UKSI has been updated on the NBN Atlas as of February 2026. We apologise for the long delay in updating the UKSI, this was caused by having to prioritise the switch over to the NBN Atlas' new data infrastructure.

Now that this major infrastructure work has been completed we expect UKSI updates to been completed quarterly.

We have checked for any issues, but if you notice anything that doesn't look correct please let us know.

Kind regards,
Rhiann

Most values for individualCount are not being exported

null@example.com (David Hepper) — Mon, 12 Jan 2026 16:35:30 +0000

Exports in Full DwC (and probably Simple) format from dr731 are not exporting any values other than "1" in the individualCount column of the output CSV. All other values export as Null. This seriously compromises the usefulness of our data resource.

We use values "Present", 1 and abundance ranges 2-5 etc. but with a special character instead of a minus sign, in an attempt to avoid confusing Excel: The char is '–' which is En Dash (U+2013 = Alt+0150).

Surely the NBN Atlas download feature should export whatever values are in the fields, not police them itself.

I don't think this is likely to be a new problem caused by the new Pipelining code.

The problem is likely to affect anyone else using slightly non-standard abundance values.

[Also sent to Will by email.]

NBN Atlas downtime (7:30-9:00 GMT on Tuesday 9 December)

null@example.com (r.stock) — Tue, 02 Dec 2025 15:55:20 +0000

Dear NBN Atlas users,

We will be carrying out some essential maintenance on the NBN Atlas between 7:30-9:00 GMT on Tuesday 9th December. During this period, the NBN Atlas will be unavailable. Apologies for any inconvenience caused.

Kind regards,
Rhiann

Search by Taxon Name fails if Genus is not unique

null@example.com (David Hepper) — Tue, 21 Oct 2025 15:03:12 +0000

A genus Gomphus exists independently in both fungi (BMSSYS0000045863) and dragonflies (NHMSYS0000079883). In Advanced Search, if you search by Taxon Name for 'Gomphus' it finds only the fungus records whereas if you search for 'Gomphus vulgatissimus' it finds the dragonfly records.
Searching for the genus name should find all records from both groups. Currently it seems impossible to find genus-level records of Gomphus dragonflies.

Sorting by Date doesn't work for records with date ranges

null@example.com (David Hepper) — Fri, 02 May 2025 15:38:45 +0000

The Atlas allows records with date ranges rather than a single day/month/year observation date. The sorting of records by date does not work for records with a month range or only a year specified. It should at least sort these by year.

See attached example screenshot of the Occurrences view.

NBN Atlas Maps -survey now closed

null@example.com (melhardie) — Mon, 07 Apr 2025 10:49:15 +0000

Thank you to everyone who contributed to the survey to help us understand what you want from the NBN Atlas maps.
The survey is now closed and we will work with Futures Wild to compile the results and review how we can start implementing some of your suggestions.

Advanced search truncates (badly) Grid Refs finer than 100 m = hectare

null@example.com (David Hepper) — Tue, 25 Mar 2025 16:45:03 +0000

The placeholder Help for the Grid Reference filter in Advanced search says 'Enter any grid reference e.g.SK5740' but it does not qualify this.
If a 10 m (8-figure) grid reference is entered it is truncated to 6-figure by removing the last two digits, without warning.
e.g. SZ18229383 becomes SZ182293 and then treated as a 100 m (6-figure) grid reference which does not even contain SZ18229383. If truncation is necessary because a 'grid_ref_10' index is unavailable then the Easting and Northing should be truncated separately to produce SZ182938.

Pipistrellus pipistrellus ss on the NBN Atlas issues

null@example.com (melhardie) — Fri, 14 Feb 2025 12:12:55 +0000

There has been an issue with the NBN Atlas processing of Pipistrellus pipistrellus (Schreber, 1774) sensu stricto (TVK: NHMSYS0020001355) - they are not being picked up as sensitive in those countries that list them.

In order to ensure any sensitive data is not accidentally being shared at full resolution in the NBN Atlas, a temporary fix is in place to automatically remove occurrence records for this taxon from all datasets provided to us for data processing whilst we work to resolve the issue.

Further detail:
The sensitive data service, embedded in the data processing, is not using the ID but the name and the lookup for Pipistrellus pipistrellus (Schreber, 1774) sensu stricto returns the results for Pipistrellus pipistrellus (Schreber, 1774) sensu lato. We are updating the data processor which will enable us to fix this, but the fix will require occurrence records to be supplied with both the scientificName and taxonId.
This does not appear to be an issue for any other listed sensitive species.

Apologies for any data partners that this impacts. Please get in touch if you need further information.

Please release the 2025 Data Processing Schedule

null@example.com (David Hepper) — Wed, 13 Nov 2024 16:55:09 +0000

https://nbnatlas.org/nbn-atlas-data-pro … -schedule/

Advanced Search behaves weirdly when searching on Recorder Name

null@example.com (David Hepper) — Tue, 12 Nov 2024 09:33:26 +0000

The field help for the 'Recorded by' field of Advanced Search (to match the field elsewhere known as 'Collector'!) says "Enter all or part of the name". This should correspond to a double-wildcard match e.g. '*Broomfield*' (or in SQL: '%Broomfield%') but it doesn't:

- If a single name is entered it finds only exact matches of the whole name. e.g. 'Broomfield'.

- If 'Mary Broomfield' is entered it unexpectedly finds all 'Broomfield' but not all 'Mary'! i.e. it finds all of "Mary Broomfield", "J. Birchall;Mary Bloomfield", "Broomfield, Mary", "M. Broomfield", "Rachel Bloomfield" and more. I would logically expect it to find only the first and second of these.

- If 'Broomfield, Mary' is entered it unexpectedly finds all names containing soundex-style variants of 'Mary' such as "Marie", "Anne-Marie". This is really unhelpful!

- If wildcard '%' characters are explicitly added to the search string it fails to find anything.

I think this field is being over-processed to try matching both name orders and causing serious confusion.

Is the 'Feature Requests' forum still monitored?

null@example.com (David Hepper) — Mon, 21 Oct 2024 16:20:30 +0000

I've submitted a couple of feature requests here > https://forums.nbn.org.uk/viewforum.php?id=51 but it's all a bit quiet...

Advanced Search cannot find records within a 100 km (Myriad) square

null@example.com (David Hepper) — Fri, 18 Oct 2024 17:31:33 +0000

Advanced Search with a filter on 'Grid Reference' correctly finds all records of any precision within a 10 km square, e.g.
TL04 finds records with OSGB specified as any of:
> TL04
> TL04Y
> TL0741
> TL078412
> etc.
This uses computed record attribute 'grid_ref10000'.

However, Advanced Search finds nothing when only the 100 km square is specified, e.g.
TL reports "No records found for grid_ref:TL ..."
This is because the attribute 'grid_ref100000' either does not exist or is not used by Advanced Search.

If this is by design it should be noted on the search form, please!

Advanced Search cannot find 'Records of absence'

null@example.com (David Hepper) — Fri, 12 Apr 2024 19:11:44 +0000

Issue

Advanced Search allows search by Occurrence ID but cannot find records such as iBRC7129589.NR because an additional filter element (exclude) occurrence_status:"absent" is automatically added to the search.

Workaround

Allow the search to fail and then edit the URL to change '-' to '+' in the last filter element:

 ... &fq=+occurrence_status%3A"absent"

Suggested Enhancement

Add a field to Advanced Search to control this parameter, defaulting to Exclude.

Unexpected handling of records where grid ref straddles VCs

null@example.com (David Hepper) — Sat, 06 Apr 2024 18:21:25 +0000

Records where the grid ref straddles one or more VC boundaries seem to be assigned only to the VC having the larger area. (Please confirm) and other fields within the section 'Additional political boundaries information' may be being computed inconsistently.

Although the field title 'Watsonian Vice Counties (GB)' implies that all VCs are shown, in practice I only ever find one. Would it be possible to assign boundary-straddlers to all VCs so that they are included when searching by any such VC?

Example: record https://records.nbnatlas.org/occurrence … 4280737dd3 has Occurrence ID iBRC17560955.Ad and of a dragonfly recorded in grid square SO2111 which is mostly in Breconshire but straddles the VC boundary into Monmouthshire.
I do not have a side-by-side comparison between Preserved (modern) and Historic (VC) Counties of Wales but the assignments to this record may not be consistent:

- Districts, Boroughs and Unitary Authorities (Great Britain): Sir Fynwy - Monmouthshire
- Watsonian Vice Counties (GB): Breconshire