discussion / AI for Conservation  / 20 November 2024

Conservation Data Strategist?

Hello everyone – long time lurker, first time poster...

I’m the founder of a recently funded tech startup working on an exciting venture that bridges consumer technology and wildlife conservation. We’re developing user-friendly devices that collect wildlife data. While our main goal is to create an engaging experience for users, we genuinely believe the data we gather could make a meaningful contribution to conservation efforts and research.

We’re currently in the early stages of developing our data strategy and are keen to ensure that we get it right from the beginning. We want to make sure our data is valuable, ethically managed, and effectively utilised by the conservation community.

I'm looking to find experts or advisors who specialise in conservation data strategy, who can help advise, shape, and guide us to build the most useful thing for nature.

Some of the topics we're looking for guidance on:

Valuable Data Types and Metadata

  • What types of data and metadata are most beneficial for conservation purposes?
  • Are there specific data standards or protocols we should adhere to?

Data Standardization and Integration

  • How can we best align our data formats with existing conservation databases?
  • What best practices exist for facilitating data integration and interoperability?

Ethical Guidelines

  • What ethical considerations should we be mindful of when collecting and sharing wildlife data?
  • How can we protect sensitive species and habitats from potential risks associated with data sharing?

Data Validation

  • What processes are effective in ensuring accurate species identification?
  • Have community verification or expert reviews been beneficial in your projects?

If you know of individuals or organizations that might be interested, or if you have suggestions on where else we should look, we’d greatly appreciate your guidance. This space is new to me, and so I'm not even sure if what I'm asking for is a thing!

Thanks,

Pete.
 




I recently started looking at data standards - initially for camera trap related data - and found that this is a fairly uncoordinated area open for standardization and simplification to make it more usable and understandable for citizen scientists (since "formal" scientists mostly have their own organizational/institutional standards to comply with).

You might be aware of all or most of these and it might not be what you're looking for, but I found the following online sources useful:

 

And there's probably a million other useful pieces of info out there that I haven't found yet...

 

Hey Pete!

Fellow founder here. Up until Summer, we were creating our own wildlife camera (called it Animal Detect as well). Some of the considerations you've listed resonate with our experience.

@HeinrichS already dropped some really good suggestions. 

From what is not mentioned I can add that if one plans to operate within Europe, then one must take care of GDPR regulations. It is mostly a gray-zone definitions, but generally: don't detect/record humans on public territories, do not reveal locations of cameras or detected animals (to avoid poachers tracking rare species).

You haven't mentioned in the post what exactly are you building. Is it a trail camera collecting images/videos or something else? :)

Lastly, we've spent a fair share of time tinkering with our own electronics, before realising that outsourcing the design+production of components is way faster/cheaper.

If you want to chat or generally stay in touch, add me on any socials, same name as here.

Great resources being shared! Darwin Core is a commonly used bio-data standard as well.  

For bioacoustic data, there are some metadata standards (GUANO is used by pretty much all the terrestrial ARU manufacturers). Some use Tethys as well.

Recordings are typically recorded as .WAV files but many store them as .flac (a type of lossless compression) to save on space. 

For ethics, usually acoustic data platforms with a public-facing component (e.g., Arbimon, WildTrax, etc.) will mask presence/absence geographical data for species listed on the IUCN RedList, CITES, etc. so that you're not giving away geographical information on where a species is to someone who would use it to go hunt them for example.