COBWEB: Brief Introduction, GBIF Secretariat
Download as PPTX, PDF0 likes547 views
The document introduces COBWEB, a research project that develops a crowdsourcing infrastructure for collecting and analyzing environmental data provided by citizens. The project aims to address data quality issues and support policy decisions. It has several pilot sites and partners, including UNESCO biosphere reserves. The framework includes mobile apps, QA processes, and a portal to view and analyze citizen-submitted data. It uses open standards and aims to be customizable for different use cases involving topics like biological monitoring and flooding.
COBWEB: Brief Introduction, GBIF Secretariat
- 1. COBWEB Brief Introduction, GBIF Secretariat Copenhagen, 15th Jan, 2016 Chris Higgins chris.higgins@ed.ac.uk Sta
- 2. Introduction to COBWEB • Research Project: Funded under the European Commission’s Framework Programme 7 • Started Nov 2012 for 4 years (Month 39 of 48) • First demonstrator completed and tested during the 2015 field season • Why? – GPS enabled, internet connected mobile devices now ubiquitous – Lots of potential, eg, can citizen sourced environmental data be useful for decision making?
- 3. Citizen Observatory Web • Generic crowdsourcing infrastructure – A toolkit which can be downloaded and used in multiple scenarios • Data which supports policy • Address data quality issues • Open standards
- 5. UNESCO World Network of Biosphere Reserves Sites of excellence to foster harmonious integration of people and nature for sustainable development through participation, knowledge sharing, poverty reduction and human well-being improvements, cultural values and society's ability to cope with change, thus contributing to the Millennium Development Goals
- 6. COBWEB Biosphere Reserves Biosffer Dyfi Biosphere Mount Olympus Gorge of Samaria Wadden See & Hallig islands
- 7. Co-design
- 8. Co-Design - Penparcau Community Forum • Temperature • Humidity • Wind speed • Wind direction • Pressure • Precipitation In situ sensors
- 9. Not just apps… A number of demonstrator mobile phone applications – Exactly what, deliberately left open and subject to discussion with community 3 pilot case study areas: 1. Validating earth observation products 2. Biological monitoring 3. Flooding
- 10. COBWEB Framework
- 11. Key components at different TRL’s • Conflation • QA workflow editor • QA WPS/services • Sensor networks • GeoNetwork/Portal • Middleware • Authoring tool/Survey designer • Apps • User management and privacy • Access control • Authentication
- 12. The app itself Key features • Capture information – Images – Audio – Text – Location • High quality background maps • Saved maps for use “offline” • Custom data collection forms • Manual location correction
- 14. Customise your own app for your survey
- 15. Customise your own app for your survey
- 16. Customise your own app for your survey
- 17. Citizen captures data on their phone
- 18. Approach to QA • Quality Assurance: complex problem and often use case specific: – Internal quality (metrics) – External quality (fit for purpose) • A generic system that can be easily customised to fit new use cases, based on standards • Understanding data quality is likely to require a combination of approaches and tests, the system is designed to enable this • As quality requirements are use case specific, the quality control tests are configurable to utilise a wide variety of datasets and parameters
- 19. Classifying quality: Seven pillars Pillar Example Test Notes Pillar 1 – Location Based services Assessment of spatial accuracy – estimate from a mobile device and number of satellites Tests often carried out on the mobile device Pillar 2 – Cleaning Removal of junk data via an attribute text check Very lightweight, can flag or remove malicious entries Pillar 3 – Automatic validation Analysis whether an image is blurry Higher level testing, often used to assess ranges Pillar 4 – Comparison with authoritative data Use of a set of boundary polygons to check whether an observation is in or out Wide variety of tests that involve comparison with what it known Pillar 5 – Model based validation Running a flood model Can be complex, and may also include question based modeling Pillar 6 – Big/Linked data Querying Twitter via a hashtag for similar phenomena Tapping into large databases such as sensor records and social media Pillar 7 – Semantic harmonisation Rationalisation of entries via an ontology Attempts to recognise multiple entries of the same observation
- 20. Web Processing Service • OGC Standard • Web facing • Public • Holds spatial and non-spatial processes • Processes are suited to chaining • BPEL is the traditional method of chaining – However, removed from WPS 2.0
- 21. BPMN Workflow Engine • JBOSS JBPM – A Java based BPM workflow engine • Orchestrates processes in a given order with defined inputs • Chains results from one process to the next • Can be executed remotely via REST • Graphical interface utilises BPMN2.0 – a recently ratified OMG standard • Unlike BPEL this interface is standardised
- 22. Service Provider (SP) Identity Provider (IdP)Discovery Service (DS) “GEOSS user” Single- Sign-On Trust Gateway (TG) to OpenID Google OpenId COBWEB/GEOSS AIP-6 Federation NASA Ames Secure Dimensions CUAHSI* Catapult University of Edinburgh Kst. GDI.DE *: Consortium of Universities for the Advancement of Hydrologic Science EarthServer (FP7) project MEEO
- 23. Remainder of project…emphasis shifting • Rolling out software • Getting greater buy-in • Sustainability • More focus on research agenda • Greater focus on Greece, Germany • Additional Biosphere Reserves
- 25. Injecting semantics into the COBWEB workflow