Interoperability framework for freshwater biodiversity data.
TFBIS Project 282
Primer / discussion document for comment from project team and wider community
Background
Various organisations across New Zealand hold and / or curate archives and databases of freshwater
biodiversity survey (FBIO) data. To date there is no easy and nationally agreed way to query or
transfer freshwater biodiversity survey information across organisations and systems. New Zealand
needs a biodiversity interoperability framework to achieve that. In this project we conduct a number
of workshops with a key stakeholder group of freshwater biodiversity data managers and architects
to scope key users, components, architecture, and develop a roadmap for a national freshwater
biodiversity interoperability framework. (from TFBIS proposal)
Key Stakeholder Group










Jim McLoed, WRC
Jim Fretwell, BOP
Jerry Cooper, LCR
James Lambie, Horizons
Jochen Schmidt, NIWA
Brent Wood, NIWA
Paul Barter, Cawthorn
Norm Thornley, DOC
Lucy Baker, MfE (Observer)
Potentially observer from MSI/MAF
Target audience
Our understanding is that there are different communities with regards to management of FBIO
data:
1.
2.
3.
4.
5.
6.
7.
A range of CADDIS users among regional councils and Cawthorn.
A range of EcoBase (IQUEST) users among regional councils.
Freshwater Fish community feeding data into FFDB and that into FBIS.
NIWA aquatic plants group uses AQPDB which feeds into FBIS.
NIWA freshwater invertebrate groups feed into FBIS.
NIWA freshwater algae groups plan to feed into FBIS.
A large range of NIWA and RC staff use their own excel spreadsheets etc. (= ’wild west’)
It seems to be sensible to focus for now on the question how to integrate the CADDIS/EcoBase/FBIS
communities into an interoperability framework.
What are the fundamental and common concepts of a FBIO Management system?
The key paradigm of the FBIO interoperability framework can be defined as:
Regardless how and where FBIO data is managed, we want stakeholders to be able to discover it in a
taxa, spatial, and temporal context, provide consistent metadata, and be able to access the
information in a consistent way.
To enable interoperability we need to define the same concepts which are common in the
underlying FBIO systems.
We suggest they are:



Survey (or dataset). A set of FBIO data collected for one purpose, through one continuous
survey. Typically the scope of what “survey” entails can be variable and is defined by the
curator. We suggest to use ANZLIC? / Darwin core? / GBIF? as the common data concept to
describe those.
Sampling efforts (or sampling events). A survey always consists of a number of sampling
events. A sampling event is defined by FBIO data collected in one location (coordinates), one
date/time, one method (and more?). What is the common conceptual information model for
sampling efforts?
Sampling Data. The actual data can be quite variable and multifold. Therefore currently in
FBIS we have modelled that as a set of (hierarchical) key-value pairs. What is the common
conceptual information model for sampling data?
(Note: We are just focussed on survey data for the purposes of this project, but we do recognise that
other data, e.g. community captured, & opportunistic, exists).
Key elements of a NZ FBIO interoperability framework
We suggest the following elements needs to be dealt with:
1. Interoperable taxa management. To be interoperable all taxa data need to be compatible.
This should be achieved through references to NZOR.
2. Interoperable spatial references. To be interoperable all spatial references need to be
compatible.
3. Interoperable temporal references. To be interoperable all temporal references need to be
compatible.
4. Interoperable methods references. To be interoperable all methods references need to be
compatible. Typically different systems use their own terminology. It will be very hard to
achieve consistency here. Probably best dealt with reference to a locally managed methods
register.
5. Open Standard (web service) to expose survey information. We suggest this should be done
through OGC catalogue services for the web CSW (or others?).
6. Open Standard (web service) to expose sampling effort information. We suggest this should
be done through a clearly specified OGC web feature service WFS (Or SOS? Or Others?).
7. Open Standard (web service) to expose sampling data. Need to develop a standard for that?
Is there an existing one? GBIF/SOS?
Overall architecture of a NZ FBIO framework.
We suggest that the overarching principles and architecture should be defined as follows:




Every major collector of FBIO data need to feed their data into a “managed FBIO system”.
A “managed FBIO system” is uses the fundamental concepts as defined above.
A “managed FBIO system” is consistent with (1), (2), (3), (4) above.
A “managed FBIO system” stores survey information exposes its information through (5), (6),
(7)