GeoSolutions presenting GeoServer for serving Meteorological Data at ECMWF

Dear All,a couple of weeks ago we have been invited to ECMFW for the MOS14 Workshop to give a presentation on the current and future capabilities of GeoServer for serving Metereological and Oceanographic data.Here below you can find the presentation that was given by Simone Giannecchini. In addition to an in-depth discussion about GeoServer capabilities a few real-world use cases area also presented. Using GeoServer for spatio-temporal data management with examples for MetOc and remote sensing from GeoSolutions If you'd like to know more about what you could achieve with GeoServer, do not hesitate and get in touch with us. If you need professional services to get...


Oceanographic Database, managing oceanographic data with GeoServer and GeoBatch

Dear All,in this post we'd like to introduce some work we have done recently at GeoSolutions towards an applications that is able to ingest in real-time, manage, visualize, retrieve and chart data acquired by oceanographic and meteorological sensors (like sensors mounted onboard underwater gliders as an instance) over time. We called this application, Oceanographic Database.The infrastructure we have put together is shown in the picture below.Summarising, we can identify the various components and their roles as follows:Data is ingested via GeoBatch in near real-time with proper prepocessingGeoServer is used in conjunction with some custom REST extensions for performinng visualization, dissemination and export to Google...


Adding TIME and ELEVATION support to GeoServer and Mosaic plugin

Ciao a tutti,in my previous post I showed a preview of the work we are doing to be able to serve raster datasets with support with TIME and ELEVATION in both WMS and WCS. We have been doing some more progresses with this work and now we can support the ELEVATION keyword as well in WMS queries, therefore I wanted to show some screenshots.Here below you see some screenshots of of the water temperature over the Ligurian see with the respective requests, first at the same timestamp at increasing depths, then at a certain depth with increasing timestamps. Notice that...