Virtual Meeting 02. CoP Plenary workshop Forum 6

When:

Description

• Parallel session in the CoP Plenary workshop Forum 6

Links of interest for the event.

• Agenda for the two days and some minutes (Google docs)
• New channel on Gitter:
• Not use the usual channel in GoToMeeting number but a zoom room: https://zoom.us/j/91624461741?pwd=dHA3R3p6WVdLVjgxc2VXcUpBaVYzZz09
• Or use our email interop-cop3@listsNOspamPlease.weobserve.eu

Attendants

• Attendants: Joan Masó, Andy Cobley, Lukas Mocek, Lucy Bastin, Andreas Matheus, Anne Bowser, Landon van Dyke, Bente Lilja Bye, Larisa Schelkin, Ester Prat

Agenda

• Analize the GBIF API (13:00 to 14:00)
• Anne will report on their progress
• Engeniering Report writing (14:00 to 16:00)
  • https://github.com/opengeospatial/CitSciIE/tree/master/SecondPhase

Meeting minutes

• Sensor Community: no support and no funding. For https://maps.sensor.community/#2/0.0/0.0 the tool used is https://www.windy.com/?51.727,8.771,5. In http://pjgueno.epizy.com/SCStations/: red points are sensor community measurements. JRC is taking them in https://fairmode.jrc.ec.europa.eu/. 250m and 1000m circles are indicating citizens where sensor community sensors can be established to get measurements close to the official ones.
• How to build your own sensor is described in detail in https://sensor.community/en/. More than 40.000 sensors in more than 70 countries. Similar to CanAirIO but this one takes average measures and not instant measurements like Sensor Community. Not secure if they are allowed to participate in EC calls for proposals (no answer from the Commission). Also no feedback from the participation in https://unhabitat.org/un-habitat-convenes-virtual-workshop-on-improving-air-quality-and-public-space-monitoring-in. Maybe it’s about fear of losing control about data.
• Links with the CAMS dataset? Would be good, but in WO we actually have tried to link CS data with the in-situ component in the Copernicus Land Service, but they are having tenders with companies to provide those data and they have their own business model. Write to Lukas for more info: Lukas@Sensor.Community.
• They are going to do soil moisture now. Any possible links with GROW? Should check how sensors perform in several contexts.
• JM: We have been working on the 2nd round of the CS Engineering Report, mainly in the API proliferation part. We should collect our attempts to use SensorThingsAPI. The iNaturalist API is extensively described and also the Sensor Community API. In this case values are retrieved but info on units or parameters is missing. Lukas says there are dozens of sensors, but nevertheless info on values can be provided. Andreas asks which is the license, if you get the file, are you able to share it or not? Where are the credits or the contact info? https://github.com/opengeospatial/CitSciIE/tree/master/SecondPhase. It should be stated in some place. AM: Who owns the individual contributions? Users contribute data, the license states mentioning origin, and this is the community. No personal data is provided. USA Citizen Science Cloud Data Portal is also described. Every field in the dataset can be used as a filter and data model is retrieved. It contains the attribution fields at the observation level.
• GBIF API is used in the Citizen Science Cloud Data Portal to retrieve observations. It would be good to have a dynamic transformation from GBIF API to STA.Landon: It’s possible. JM: would be good to have an STA endpoint to allow for huge queries, we are close to that. If we provide the type of queries to Landon he can try to build it.
• AM: Tracking users' ID is useful for building profiles and providing quality enrichment. LM: must be made clear which are the benefits of adopting such a big model for a modest CS project. BLB: can be a requirement for sharing data in GEO, for example. AC: it also allows to show only observations from one contributor. AM: identifiers can be exposed but not resolved.
• JM: not sure if we will succeed in proposing a common API for CS because everybody is running away when trying to implement it. AM suggests to write a proposal to get funding to investigate just this.

Next Action points

• CS session in the next OGC Meeting is still empty.
• Please provide contributions to the Engineering Report: https://github.com/opengeospatial/CitSciIE/tree/master/SecondPhase.