There’s some great content available about the Sharpham Estate, created/curated by our partners at Ambios. One of their guys has a Google Earth file that collates a huge wealth of geotagged nature information in a structured way: there’s information about the habitats, from broad-brush classification (e.g. woodland), down to finer-grained (e.g. semi-natural woodland); there’s information about the wildlife, from surveys to individual observations and videos from camera traps. As well as the nature data, there’s old maps (Ordnance Survey) and old photos from a local library.
There’s all the usual issues you’d expect about making content available freely: curating and organising (metadata!), checking the rights situation with the original creators and any assignees, perfectionism (don’t want to share until it’s all perfectly right), formats, and so on. We’re working away on those.
But there’s one issue I hadn’t expected.
One data set we have is the locations of all the badger setts on the estate. Usually, badgers like to make their setts in the middle of woodland. But when you view the badger sett data on top of a Google Map, you can quickly see that one of the setts is slap in the middle of a field, which is unusual. However, when you overlay the 1891 Ordnance Survey map, all is revealed: back then, the sett would’ve been in the middle of woodland, which has since been cleared. Badgers are known to maintain setts for hundreds of years once started, so it seems that this sett was created in woodland, and has been used since then despite the clearance.
This is a fantastic story, illustrating the power of combining data sets, and is likely to be really interesting to people who come to the Sharpham bioblitz. Connecting people up to this sort of great content is exactly the sort of thing we want to do with iSpot Local.
Alas, we can’t make the badger sett data set available!
Badgers are protected by law: it’s illegal to harm them or their setts without a licence. But there are people who want to harm badgers – e.g. farmers worried about bovine tuberculosis and badger baiters – who aren’t deterred by the law. So overwhelmingly the advice we’ve had is that it’s a very, very bad idea to publish the location of badger setts.
On iSpot, we have a ‘hide precise location’ option on observations to deal with this sort of issue, where there are species at risk of persecution. This ‘snaps’ the location to the 1km grid square that includes the original location, so you can see the area the observation was made in, but not the precise location. This also helps when it’s humans who need a bit of privacy – e.g. if you’re making observations in your own garden but don’t want to tell the world your precise address.
But even if we could implement that for iSpot Local (there are technical issues), it would blur the data to be uninteresting – the sett-in-the-field-that-was-once-woods story wouldn’t emerge, since the field in question is less than 1km wide. And some badger experts would still be unhappy at sharing such comprehensive data even at that resolution.
So a new (to me, at least) barrier to sharing content: protection of badgers from interference.



