Report on the Developed and Validated Atmospheric Thematic Services (Release #1)

This document reports on the 1st release of the Atmospheric Thematic services and the software underlying each service. This report, NEANIAS deliverable 3.4, comes out right after the first thematic atmospheric services release, deliverable D3.3. The A1 Service, named “ATMO-FLUD”, (for flux densities) provides a set of algorithms for the calculation of flux densities of Sensible Heat, Latent Heat, Turbulent Kinetic Energy and other scalars like GHGs. The input data to the service is user provided although test data are available for trial runs. Real data should be experimentally obtained by the user bearing in mind that the fundamental method employed in this service is the “Eddy Covariance”. The A2 Service comprises two services: one named “ATMO-STRESS” calculates the trajectories of tectonic stress based on a series of local data of stress and presents them as a map (stress field). The second service, named “ATMO-SEISM”, compares a series of parameters regarding the seismicity of a region and the variation of gas emission in the atmosphere, in order to find possible correlations. The A3 Service, named “ATMO-4CAST”, is responsible for Air quality estimation, monitoring and forecasting, providing users with the ability to obtain and visualise meteorological and air quality forecasts based on their own datasets through a central server. This is done by processing the incoming data, passing it through popular models such as WRF-ARW and CMAQ, and processing and creating visualisations based on their outputs. For each released service a point-of-access is provided, as well as interface through which it may interact with other services and documentation explaining how to use it. Documentation of all NEANIAS atmospheric services is organized under NEANIAS docs service. Services reported here have gone through the first release round, most services have been integrated to NEANIAS authentication system service, the documentation workflow, and integrated with GARR infrastructure services. As expected, this first milestone of services, uncovered some gaps in their deployment stack. Integration with other core and delivery services will be addressed for the next milestone and releases