Search

Cloud-based big earth data workflow architectures for operational decision making across communities need to follow FAIR (Findable, Accessible, Interoperable, Reusable) principles in order to be effective. This presentation highlights mature implementations of OGC standards-based building blocks for climate data processing and service provision that are deployed in leading climate services information server systems such as the COPERNICUS Climate Change Service C3S. OGC Web Processing Services (WPS) form the bases of component operations in these implementations, from simple polygon subsetting to climate indices calculation and complex hydrological modelling. Interoperable building blocks also handle security functions such as user registration, client-site utilities, and data quality compliance. A particular focus will be the ROOCS (Remote Operations on Climate Simulations) project, a set of tools and services to provide "data-aware" processing of ESGF (Earth System Grid Federation) and other standards-compliant climate datasets from modelling initiatives such as CMIP6 and CORDEX. One example is the WPS service ‘Rook’, that enables remote operations, such as spatio-temporal subsetting, on climate model data. It exposes all the operations available in the ‘daops’ library based on Xarray. Finch is a WPS-based service for remote climate index calculations, also used for the analytics of ClimateData.ca, that dynamically wraps Xclim, a Python-based high-performance distributed climate index library. Finch automatically builds catalogues of available climate indicators, fetches data using “lazy”-loading, and manages asynchronous requests with Gunicorn and Dask. Raven-WPS provides parallel web access to a dynamically-configurable ‘RAVEN’ hydrological modelling framework with numerous pre-configured hydrological models (GR4J-CN, HBV-EC, HMETS, MOHYSE) and terrain-based analyses. Coupling GeoServer-housed terrain datasets with climate datasets, RAVEN can perform analyses such as hydrological forecasting without requirements of local access to data, installation of binaries, or local computation.The EO Exploitation Platform Common Architecture (EOEPCA) describes an app-to-the-data paradigm where users select, deploy and run application workflows on remote platforms where the data resides. Following OGC Best Practices for EO Application Packages, Weaver executes workflows that chain together various applications and WPS inputs/outputs. It can also deploy near-to-data applications using Common Workflow Language (CWL) application definitions. Weaver was developed especially with climate services use cases in mind.The architectural patterns illustrated by these examples will be exercised and tested in the upcoming OGC Climate Services Pilot initiative, whose outputs will be also incorporated into disaster risk indicators developed in the upcoming OGC Disaster Pilot 2022.Further reading:https://docs.google.com/document/d/1IrwlEiR-yRLcoI9fGh2B1leH4KU0v0SUMWQqiaxc1BM/edit

International audience; Data owners are creating an ever richer set of information resources online, and these are being used for more and more applications. Spatial data on the Web is becoming ubiquitous and voluminous with the rapid growth of location-based services, spatial technologies, dynamic location-based data and services published by different organizations. However, the heterogeneity and the peculiarities of spatial data, such as the use of different coordinate reference systems, make it difficult for data users, Web applications, and services to discover, interpret and use the information in the large and distributed system that is the Web. To make spatial data more effectively available, this paper summarizes the work of the joint W3C/OGC Working Group on Spatial Data on the Web that identifies 14 best practices for publishing spatial data on the Web. The paper extends that work by presenting the identified challenges and rationale for selection of the recommended best practices, framed by the set of principles that guided the selection. It describes best practices that are employed to enable publishing, discovery and retrieving (querying) spatial data on the Web, and identifies some areas where a best practice has not yet emerged.

Two new methods for deprotection of diphenylmethylsilyl (DPMS) ethers are described. Selective unmasking can be achieved with either catalytic amounts of perfluoro‐1‐butanesulfonyl fluoride (a SuFEx reagent) under mild, aqueous micellar conditions, or using stoichiometric amounts of 18‐crown‐6 ether in aqueous ethanol.

Introduction. The enterocyte-specific protein, intestinal fatty acid binding protein (I-FABP), is detectable in serum only after intestinal injury. Previous studies in animals suggest that I-FABP might be a useful marker of intestinal allograft rejection. Materials and Methods. I-FABP was repetitively measured in nine intestinal transplant recipients and correlated with findings of surveillance endoscopy. Results. Average interval between I-FABP determination and biopsy was 3.4 days (SD=4.2 days). Average number of rejection episodes per patient totalled 1.6±1.2. General linear modeling demonstrated no tendency for increases in serum FABP to precede histologic graft rejection (P=0.263). Restriction of the analysis to I-FABP determinations 1 day before or on the day of biopsy failed to affect these results. Minor increases in I-FABP were often associated with histologically normal grafts, whereas rejection often occurred when I-FABP was not detectable. Discussion. Serum I-FABP levels do not predict clinical intestinal allograft rejection.