Merken

Sensor Web for Oceanology

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
he's good afternoon again this is
the trick from Sensor Web Enablement and now we have the 2nd speaker is so Simon aircraft from 50 to north and you will I'll talk about that's a more practical application of persons rep enablement of data collection and specifically about the other domain the domain of ocean ology sir a tour the of the that thank you very much for your introduction the today I'm going to presented application example of sensor technology from the ocean science domain we have applied sends a lot in the past them current topics like air quality hydrology and this time I would like to
introduce new new domain which may benefit from this technology so just as an introduction this is an image from 1 of our projects and to illustrated that the challenge so if you look at this there are lots of different types of of samples of the that our research vessels up there that deep-sea gliders which are autonomously going through the ocean collecting data we have which stations have stationary observations we are detecting for example also animals had such as Wales by having click detectors under the sea so lots of different data types that we are dealing with in emotionality and for bringing these different datasets together using standards is really of high importance and that's also some objective of the project that I'm talking about
so just to introduce again and therefore projects making this work at the moment possible bridges next also hold it and fix all 3 all for our projects funded by the European Commission on the Future of Marine Sciences was different focus points produce more on the deep-sea gliders next on the full range of communication from the sensor into the application 603 focusing on in situ observatories and hold it more on the general interoperability aspects between different types of observatories so these
projects to a certain extent also teaming up to have a common approach how to use on the web also here again an introduction different sensor types used within the next project and again to demonstrate by having all these different kinds of sensors integrating the sensors and different sensor platforms may cause quite a lot of work for people to integrate the data into their applications to work really get some results of the data so to illustrate this a bit of the
status quo we have different observation networks observatories and these observatory networks may have totally different languages they're talking so they may be different databases of fostering the observation data there may be different types of sensors providing the data so if you're looking at real time data streams and if you would like to integrate all these different data sources into applications you would have to customize each data consumer to the interface and data formats of each data provided and the more data sources you have and and watch ontology we are talking about lots of different observatories operated in the ocean and the number of operation and this increases dramatically the more data sources and data consumers do you have so the idea really of these projects is to look at the use of standards to harmonize this data transfer and I will focus a bit on SOS technology therefore technologies which I will also show the mention but here the focus will clearly be on the SOS this sense observation service and OGC standards for the interoperable sharing of observation data by a web-based interface and the sites and so as we are relying on to further standards also defined by the OGC on the 1 hand observations and measurements that's a data model and data how to transmit data so how to encode your data in an XML document and on L especially relevant for the marine sciences because you also need metadata about his hands on so it's not sufficient just to transplant the sensor data from a to B you also need the metadata especially for marine science they are really careful about when was the sender the calibrated for the last time but when was the configuration of the sense of change and that's all part of the sensor metadata important for understanding the data that has been generated so send them out as the 4th point and the idea now is to use the standard if you enable 1 observatory to support the standard then each data consumer of supporting the standard will be able to understand to every new observatory that supports the standard as well so a dramatic reduction of integration and integration efforts if you want to share observation data between different organizations so
here quick look at the big picture of Sensor Web Enablement standards what a chart now about was smart mainly this data access route so having an SOS server providing based access to observation data besides this there's other relevant functionality for example controlling sounds are in the marine science is quite important again for example transmitting a certain track that shall be followed by an undersea sounds or having for that also and the interchangeable way how to do this a mechanism and a publish-subscribe approach here and this that quite a lot of standards recently in the OGC this the you OTC pub standard is emerging which has already been voted on as far as I know and this will work but I offered them also the subscription better sensor data streams finally we will have a real nice push way to transmit data also to user so 3 functionalities covered by sends Web based data access to send a request and get the data set that you would like to have push based access to subscribe and get the new data as soon as it is available and controlling the samples by sending commands so that
looking at all these different standards we have seen in the past many many projects are already using Sweden emotionality however there were some the different approaches that were used especially in the past years where we have very early versions of the SOS standard some projects even implemented versions before 1 0 so very old versions then there's a quite Trent Lott brought range of 1 . 0 implementations and now we have 2 . 0 has the latest as as version and what we would like to do and what we are doing in fact on the project is to develop some kind of best practice guidance for or in this case for the portion of the ontology we did that in the past in similar ways also for hydrology providing users data managers and their hands on document and documentation recommendations how they can implement sounds like practice which parts of the standards are relevant for which functionality and then also facilitate the cooperation between different oscillatory but did you in the end will be to push this into the OGC process at least as a best practice paper perhaps even more as an extension of so as if necessary we will have to see what that some of the topics we will be covering by the sensor web architecture comprises on the 1 hand I mentioned that metadata including editing these metadata documents and then of course providing Wilson guidance on data models of course this will be based on OTC owned and however recommendations on specific observation type specific parts of the standard because you do not want to implement the whole standard for just 1 application domain the data access also there some operations and highly relevant for the Marine Science others perhaps less important to provide some guidance which parts of SS they do need to provide guidance how to use how to control your senses using SPSS and 1 very important topic also looking at vocabularies for example at UDC and the UK there's a very good activity regarding the definition of vocabularies and also provide guidance on how to use these vocabularies to not only increases syntactic interoperability but also at least where if wherever possible have some kind of of common vocabulary to have at least a basic site yeah foundation of semantic interoperability so now we're
looking a bit more specifically at the nexus project and this project is with mainly 2 types of sensors on the 1 hand we have these deep-sea gliders these are what enormous platforms which are traveling undersea collecting data and on the other hand such queries which are set stationary fixed to the ocean floor and then ah yes deliver data such as salinity water temperature there lots of other types of data and again we will be using all we are in fact already using these different standards so as as for getting the data SPS for providing control functionality and also some functional here we have still we are likely to switch to pops up so besides this what have
seen now is basically the path from some kind of intermediary layer to the end user so the end user application if you build a web client that will talk to as low as a tasking sensor tasking final talk to SPS and what we are also looking at and this part is going to pass also to the sense so Sensor Web can take a both parts you do not have to do both but in this case we are going to the sensor so enabling some kind of sends up backtrack complain that the sender is able to push data into SOS using the transactional operations that we can also have some kind of data loggers where you can connect and sense the sensor shall have sounds ML-based self-destruction you can extract the self-description learn about the interface of the sensor but also the data lower can generate on the fly some kind of a lover of some kind of driver for the sensor so that we have an automatic and play you put a new sensor into your observatory it takes the metadata of the sensor generates a drive and then pushes is into the Web by the standardized operations and 1 important part is when they're talking about or marine sensors the cells operate sometimes in very remote locations that means they are traveling but far out on the ocean but they do not have a mobile phone coverage or whatever so in some cases for some datasets they want to to transmit the data and then using satellite communications and for that purpose we are evaluating more complicated yet more simple more lightweight approaches to publish sensor data on the 1 hand we are investigating as a binary XML encoding which is currently being standardized at the moment and so we are looking at the results handling operations of the which you can further reduce the amount of data that you have transmitted and that really gets very efficient very low low data volume for publishing data used by a satellite communication and this has led to a certain implementation architecture which we have our realized within the nexus project and that project that we are basically looking at our centers and at least we go untold this r component meant sends approach which is implemented by another project partner which will connect to the sounds also act as intermediary box somehow to the senders and this box will on the 1 hand be able to talk the SPS protocol receiving commands from users from operators of the sensors we have the data push mechanism based on the transactional operations you see this up here we have our that enables sensor is this technology we are building the the project these transactional operations can be used for pushing data into the air so as what specific is is a result handling operations we have an observation database for storing the intermediate storage of the data from their own we can on the 1 hand to feeding over Pub-Sub mechanism as well as have a web-based visualization of data and that's also the next
thing I would like to demonstrate quickly let's try with light and inspiration so what you will see now that is the SOS data viewer which has been implemented within the next project the book you have to moment to and the so there
it is so this is a time series Europe for the data available and measured the project that is again see the different data providers already configured in this kind so we are talking to different data providers for example you see c which is not entirely new Barcelona that'll come it's on the Canary Islands we have some further services like a socially which is more technologies to enrich the data demonstration that more trios it's send you send the manufacturer in northern Germany and the other 1 is German coastal observation data and if we go for such an SOS server we can
select this and
subsequently we can also switch on a map and get for example the map view of the available sensor observation data sets we can then also quickly look at so certain station we get an overview for
example here at the German coast the ancestors connecting and the people in the front rows can see that's that's really really to data so from today at 2 o'clock and 40 minutes the 3 measures in time we can connect to the sender and get it into our
diagram on so that's really good showcase for interoperability we have different providers all these data sources that you have seen distributed all around us and this case Europe could be on that are all around the world these data and managed by the organizations which have collected them so they do not have to put it somewhere else they can manage the data they can to all the quality control of the data and the way they would like to do it and then they can push the data for published data by IDSs interface and many users can easily access these data an enhancement which is being developed in that project
concerns the access tool mobile sensor data especially in the marine domain this is quite critical so you may have research vessels being on a mission taking some data we have these undersea light is that you have seen and in this case we have been working together with a partner within the project was operating so-called ferry boxes carry boxes are devices mounted to regular tree of various traveling across the sea and these terrorists continuously collect data when they reach the next part that would transmit their data and especially here in the northern sea but there are other regions in the world but this is also being done but they transmit the data to an ancestral are presented database that we have the as a server on top of the database and then we can access also such mobile observation data so for example you can see here we can then see the different measurements that were taken along the trajectory can put this also internalized by quick visualizations and have a look at that so going back to
presentation so I
would that I would like to give a quick summary about or experiences the project also some recommendations of course uh that's easy integration for end users chose the benefits of interoperability of all state reuse but what's important is to provide guidance for users how to apply the standards because if you just say OK here's the ancestor estimates and Zermelo owned and please read that it's too complex for most users they really need some guidance to explain them what are the benefits how to use the standards and which of the parts which parts of standards are important we have a full suite of these implementations that you've seen available as open source software by a 52 not so that includes for example the SOS server by erecting REST API for developing kind so this rested his clients that have seen are based on the REST API with the rest Jason communication of course the client applications are available the Pub-Sub mechanism is at the moment being in a better stage but of course will be also available and what I did not demonstrate today and metadata editor for handler metadata where can push the data into a metadata repository discovery of sensors is currently being in development are already available and it happened but that will also follow quite soon as a real release shortly also reference to inspire because these are implementations that have seen at least the 1st ones already support the emerging recommendations on implementing the inspired on what service by an SOS interface that there are certain extensions necessary so of course you have to implement as to there but beyond that there are some further extensions regarding multilinguality sees CRS support additional metadata and what's really important we have already support for certain inspire observation types which are defined in the U. S. and emerging document but xt and result handling very efficient for publishing data were very nicely are working in the community and finally In order to make sense on it looks more easy to and so for example avoiding too large so that the capabilities document as an approach of hierarchical procedures and offerings but which is basically in line with the standard however we will also provide this as feedback to the OGC tool that provide other users more guidance on and as a last thing for those of you
who will still stay in Germany next week and I'm interested in this topic we will organize the sense conference and next week but if you still get interested in the topic the conference free so you may think about joining share the details if you would like have more information I think you yes thank
you very much so some of this is really a good overview also how to use not just as a West standard but also the additional standards from the SWE the Sensor Web Enablement and now we have 5 minutes for questions for possibly the story was very you completes the let's say the no questions you
should the just as couldn't say no this yourself there is complete there was wondering because I were with the qualities scientists collect profile data in the nose so many you know so that a few years how do you handle the user profile data analysis selling of solution so we are that's something which we are not doing in in the context of the ocean energy project but for inspiring so the inspired to do to have 9 annex or a technical guidance document that contains now what will contain book content already in the past the so called owned and profile observations so that's a specific observation time which allows you to describe measurement values along a certain profile so that's already implemented for all of for example at the energy and the French which conservative they're using this observation type um for the oceans projects it's not so right at the moment of course they also have some data that with some may need this plot for these projects is not select I have a question about you is elided this will still be xt you told that some of the objective objective will be
this sense between these
communicating directly you be their this energy single so that means that they will do reduce the sensory questions yes infected with insects sense or so we have switched as such to the there but they are doing an insult sends request with that get the metadata and then are we do it at all and 1 further step we do all that then rely on in search result and plate and then the results
for the date of publication and because that avoids the repetition of certain metadata from the date of publication process but in general it's work because of up to 9 of us so some sense of speaking to the standard of the users perceive the development of the system loses its racism brand from some so in this case and it's basically box which is of some kind contains some kind of humor there's humor in will also likely be deployed in the project into the femur of some sensor manufacturers involved in the project so this is really on the research level at the moment but on the 1 hand this will be a so called a box of say which will be basically you can focus on the and it's there and other sounds or manufacturers in the project will also are implemented in 2 different so it's work-in-progress very good any more questions just do you do any of you processing of the data so uh the combined observations that produce layer is students you like kind of thing as a just the raw data that you have to drink and in this project as many the raw data however it with another project with the community without looking at Copper coupling ancestor WPS so for example there's a project in hydrology where we are driving statistical parameters of the the time series in other cases we are also looking at generating much from that so there are other projects not in this context but we're working also on this WPS as well as integration and links and you know you the the end users of the states the speedup writing data use actually using it as so the derived data in the other project that hydrologists so we have 4 1 partner in the ontology administration they're using access with in their internal data infrastructure and they want to provide their users are within the different departments the functionality to explore the chances of that more of the time series data and metadata are derived thank you have room for 1 more final question the if not otherwise so similar thank Simon again and I will leave now
5 minutes for changing just and the next speaker will start to another 5
minutes
Open Source
Software
Domain-Name
Benutzerbeteiligung
Kartesische Koordinaten
Wiederkehrender Zustand
Strömungsrichtung
Computeranimation
Telekommunikation
Subtraktion
Momentenproblem
Kartesische Koordinaten
Bridge <Kommunikationstechnik>
Fokalpunkt
Computeranimation
Objekt <Kategorie>
Spannweite <Stochastik>
Domain-Name
Analogieschluss
Datentyp
Arbeitsplatzcomputer
Stichprobenumfang
Luenberger-Beobachter
Projektive Ebene
Bildgebendes Verfahren
Standardabweichung
Resultante
Web Site
Bit
Subtraktion
Punkt
Gemeinsamer Speicher
Selbst organisierendes System
Formale Sprache
Mathematisierung
Zahlenbereich
Kartesische Koordinaten
Dienst <Informatik>
Systemplattform
Computeranimation
Physikalisches System
Metadaten
Benutzerbeteiligung
Software
Datennetz
Datenstrom
Datentyp
Luenberger-Beobachter
Maßerweiterung
Konfigurationsraum
Einflussgröße
Schnittstelle
Beobachtungsstudie
Nichtlinearer Operator
Ontologie <Wissensverarbeitung>
Datenhaltung
Open Source
Datenmodell
Datentransfer
Dateiformat
Fokalpunkt
Ordnungsreduktion
Integral
Dienst <Informatik>
Echtzeitsystem
Tensor
Analogieschluss
Mereologie
Client
Dateiformat
Projektive Ebene
Standardabweichung
Web Site
Prozess <Physik>
Metadaten
Versionsverwaltung
Implementierung
Kartesische Koordinaten
Computeranimation
Formale Semantik
Metadaten
Spannweite <Stochastik>
Weg <Topologie>
Benutzerbeteiligung
Domain-Name
Datenmanagement
Standardabweichung
Reelle Zahl
Datenstrom
Stichprobenumfang
Datentyp
Schwingung
Luenberger-Beobachter
Maßerweiterung
Ereignishorizont
Beobachtungsstudie
Prinzip der gleichmäßigen Beschränktheit
Umwandlungsenthalpie
Nichtlinearer Operator
Kraftfahrzeugmechatroniker
Lineares Funktional
Ontologie <Wissensverarbeitung>
Pay-TV
Datenmodell
Ähnlichkeitsgeometrie
Routing
Datenstrom
Menge
Analogieschluss
Mereologie
Server
Projektive Ebene
Messprozess
Computerarchitektur
Standardabweichung
Resultante
Bit
Quader
Browser
Web-Applikation
Implementierung
Zellularer Automat
Kartesische Koordinaten
E-Mail
Systemplattform
Computeranimation
Physikalisches System
Open Source
Metadaten
Benutzerbeteiligung
Datentyp
Visualisierung
Luenberger-Beobachter
Zusammenhängender Graph
Spezifisches Volumen
Speicher <Informatik>
Schnittstelle
Umwandlungsenthalpie
Nichtlinearer Operator
Lineares Funktional
Kraftfahrzeugmechatroniker
Protokoll <Datenverarbeitungssystem>
Konvexe Hülle
Datenlogger
Datenhaltung
Abfrage
Überlagerung <Mathematik>
Backtracking
Druckertreiber
Mereologie
Gamecontroller
Projektive Ebene
Computerarchitektur
URL
Bridge <Kommunikationstechnik>
Datenübertragung
Viewer
Standardabweichung
Momentenproblem
Projektive Ebene
Viewer
Computeranimation
Viewer
Beobachtungsstudie
Dienst <Informatik>
Subtraktion
Zeitreihenanalyse
Server
Projektive Ebene
Service provider
Computeranimation
Beobachtungsstudie
Mapping <Computergraphik>
Datensatz
Sichtenkonzept
Arbeitsplatzcomputer
Extrempunkt
Einflussgröße
Computeranimation
Beobachtungsstudie
Quader
Selbst organisierendes System
Datenhaltung
Open Source
Mobiles Internet
Güte der Anpassung
Trajektorie <Mathematik>
Service provider
Dialekt
Computeranimation
Magnettrommelspeicher
Domain-Name
Diagramm
System F
Mereologie
Visualisierung
Server
Gamecontroller
Projektive Ebene
Einflussgröße
Schnittstelle
Momentenproblem
Texteditor
Service provider
Computeranimation
Eins
Metadaten
Client
Standardabweichung
Typentheorie
Gerade
Schnittstelle
Suite <Programmpaket>
Kraftfahrzeugmechatroniker
Addition
Dokumentenserver
REST <Informatik>
Algorithmische Programmiersprache
Texteditor
Dienst <Informatik>
Software
Hierarchische Struktur
Server
Client
Projektive Ebene
Ordnung <Mathematik>
Aggregatzustand
Standardabweichung
Telekommunikation
Rückkopplung
Server
Metadaten
Implementierung
Maßerweiterung
Kombinatorische Gruppentheorie
Open Source
Software
Datentyp
Luenberger-Beobachter
Maßerweiterung
Softwareentwickler
Demo <Programm>
Schätzwert
Hierarchie <Mathematik>
Open Source
Integral
Modallogik
Rückkopplung
Mereologie
Analogieschluss
Viewer
Benutzerbeteiligung
Freeware
Gemeinsamer Speicher
Information
Registrierung <Bildverarbeitung>
Computeranimation
Standardabweichung
Umwandlungsenthalpie
Momentenproblem
Datenanalyse
Besprechung/Interview
Profil <Aerodynamik>
Plot <Graphische Darstellung>
Dienst <Informatik>
Kontextbezogenes System
Computeranimation
Objekt <Kategorie>
Physikalisches System
Energiedichte
Datennetz
Datentyp
Client
Luenberger-Beobachter
Projektive Ebene
Inhalt <Mathematik>
Benutzerprofil
Einflussgröße
Resultante
Lineares Funktional
Parametersystem
Prozess <Physik>
Metadaten
Ontologie <Wissensverarbeitung>
Quader
Systemverwaltung
t-Test
Physikalisches System
Kontextbezogenes System
Binder <Informatik>
Computeranimation
Übergang
Integral
Metadaten
Zeitreihenanalyse
Standardabweichung
Luenberger-Beobachter
Projektive Ebene
Modelltheorie
Softwareentwickler
Standardabweichung
Aggregatzustand
Metadaten
Standardabweichung
Besprechung/Interview
Computeranimation

Metadaten

Formale Metadaten

Titel Sensor Web for Oceanology
Serientitel FOSS4G Bonn 2016
Teil 104
Anzahl der Teile 193
Autor Jirka, Simon
Rieke, Matthes
Mitwirkende Simon Jirka (52°North Initiative for Geospatial Open Source Software GmbH)
Matthes Rieke (52°North GmbH)
Lizenz CC-Namensnennung 3.0 Deutschland:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
DOI 10.5446/20323
Herausgeber FOSS4G
Open Source Geospatial Foundation (OSGeo)
Erscheinungsjahr 2016
Sprache Englisch
Produktionsort Bonn

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract In the marine community, observation data sets are a critical input for many scientific questions. Thus, significant investments are made in equipment and data acquisition technology. To ensure that the collected data is efficiently used by a larger number of researchers, the interoperable sharing of observation data is getting more attention in recent time. This presentation introduces open source Sensor Web components from several European projects such as NeXOS, FixO3, BRIDGES and ODIP II that cover different requirements for Sensor Web technology in marine applications. On the one hand there are server-side tools such as the 52°North Sensor Observation Service which facilitate the publication and download of marine observations. On the other hand this is complemented by tools such as the 52°North JavaScript SOS Client, which offers a lightweight approach to explore and visualise observation data sets generated by mobile (e.g. research vessels) as well as stationary sensors (e.g. buoys). In our presentation we will introduce the basic principles of an interoperable Sensor Web infrastructure for Oceanology as well as show how this infrastructure can be implemented using the open source software components of 52°North. Simon Jirka (52°North Initiative for Geospatial Open Source Software GmbH) Matthes Rieke (52°North GmbH)
Schlagwörter 52°North Initiative for Geospatial Open Source Software GmbH
52°North GmbH

Ähnliche Filme

Loading...