Merken

Interoperability with OpenLayers 3

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
OK always these Apple guys but but but but but may introduce you partition to the and also to develop personal players and they will talk about interoperability the falcon leaves you feel bad so we are going to focus on the interoperability
aspects of overlay strain and interoperability in 3 ways basically we have a lot of built-in formats saying openly history so you get a lot of support coming out of the box without using any external libraries and another thing we will do in this presentation is to look for extending the support of all latest to to an external library which we named only short for opening as as we so this will integrate would argue against the rest services an additive thing body yeah basically should he has also gonna talk about the Google Maps integration library and we can at more than OTC formats in Open history by using a great external library which is called you select from Alexi was at the Dutch of understand so
to focus a little bit on the built-in formats we have formats which unknown future formats so things like a service metadata and we have a feature believes 3 in open still we had a huge list of novel feature formats but an history we decided we want to focus on the future formats because those tight closely to the future the feature structures which we use in history and we decided not to put in many the new feature former so 1 of the few ones we have in there w must get capabilities we only support 1 . 3 and we have support for WM MDS capabilities and support for transactions in work features services so if we look at it at a built-in feature format which actually have geographic data
and we have the full support G Jason I'm sure everybody knows you Jason using
them this is you Jason an example of an overlay 3 we have support for
total adjacent which is an the topological extension of Judaization and this is
still open is the example where we
have support for entry Jason has too many flavors of this stuff unfortunately this is sum an
object the rest Feature Service which is 2nd June by opening that somebody
has already mentioned we have support for the Mac Mabel vector tell specification but also to an external libraries that
this is a matter of fact tertiles example which we have seen too
many times we also support for GPS extinct exchange format GPX
so you can show you points in Europe we have support
for Gmail which is not to be missed unfortunately also we have support for came out and
KML is 1 of the few feature formats that them have embedded styling so you get the styles from that came out of and automatically another thing we
can interoperability interoperates with them different systems is we have a we have download functions which determine how the tiles unloaded and we have to get all URL functions which determines how to retrieve the actual tile so that by using these functions you can openly published 3 towns to your own in-service if it's different so now let's talk a
little bit about only this is not to decode the logo of the project to make sure it's in the Spanish army but in only when
we have something called a linear generator and basically this is something that can generate a layer and the source configuration of opening a straight from the capabilities of dark GIS REST service so this will be done automatically we look at things like resolutions the projection the attribution and the full extent of the service and then we create dog rest source analyst 3 and that is small example if will place yeah so basically we look at the capabilities and use formats on the fly we take the information and we need and then we create GIS resources this is at the same service in the last 3 years and years API and this is still same service and 3 truly
so when did RGS REST Service has a as actual dollar information we create an xyz source in place to with a custom tolerance and this is a quick example of that so again as service in in SGRQ rest we look at the end of the information which is the level of details and then you will see it in the jest PIN again over the streets the so
this is said Grayson xyz short and
to show that it also supports custom projections and made a quick video of the Dutch service which is in the Dutch national grids and again we can consume this this information from large is ready the so another thing we
have in only libraries style generated so we can consume RTA has rest style and translate them on the fly to openly styles so
endogenous rest specification there are simple objects multiple similar time and we translate them
so we have support for simple models symbols we have support for similar symbols similar filled
simple filled symbols the
picture symbol from jazz resp and the text
symbol so it's not fully
complete but it's it's a good deal of the styling information and another thing that is not yet has resistive renderer objects those
basically you determine how you classify your data and they have something called a simple renderer which just has a single symbol and we supported almost fully except for rotation expression there is a unique value and around and we support at party so this
is an example of such a renderer we where you take an attribute from the dataset and for every value in the dataset you will have a different colors and there's also something
called a class breaks renderer it said mostly supported again not
a rotation expressions so this is an example of the glass breaks said expression other classmates and renderer where you just give like an upper and lower boundaries and
here we will see an RTS rest Feature Service which has started
studying information and we also translate is 1 of
the so you will get the same styling in 3 and OK
just something so the problem of weights and which we had an overly 3 is and
this is still a huge list of formats we manually wrote in openness to so this was a lot of effort and it was like really not possible to translate all of these formats to the new version of the the library so this this is a big list
so what he's selling Cecil makes it provides adjusted from time so it's a library script that and and it also can generate mapping files from the dead XML Schema so it takes the XML Schema so it generates a mapping files and all the classes are ready to go this to repositories associated with J something which is still schemas repository and the w 3 schemas and repository and those have bindings for almost all of the OGC standards the this
did the website from the sum of and so the list
from Jason links is even bigger than this we have now is still so things I've used it for myself and in applications is for instance WFS capabilities because we don't have the noblest 3 uh WCS get capabilities I've used it in an application where I did a lot of but processing services and also for and w 1st described feature types which gives you back an XML schema of fury and feature model and this can only it can also be ratified the stomach so what you normally do in a in an application has to import all the mapping files which is something you can see in this world and then when you create the GA some context he will pass at the list of all the mapping files you need to wash your XML data so this is also means GML depends on a lot of dependencies like filter which you need to include as well and this is dead
WPS application which I which uses just something so on the list on the left you see a list of all the processes that there were processing services supports which is then that part and also all XML which is sent to the WBS service for processing is set generated by and you you can see the XML OK I'm going to pass it on to share if you block
so it and it like Bart described with them as EI services uh we had the same kind of problem with another appropriate theory vendor so in OpenLayers to 1 of the great was the support for the the Nets support for we're maps in open so we could switch between uh several map by services like mad books the year but also a good and it was not supported by 2 OpenLayers 3 because of several reasons the 1st 1 was but ago results we had to use open data is and the domestic I was really uh part was at random support to support them to always needed the combine and work with open there's so the support was dropped and because of that that for example there was foreign several years that have been synchronization issue where open isn't good and that did not use the same genetic when bending them out so the future would like to not be that at the same time and that look at it at the or not production-ready or whatever you want to call it no and 1 of the big issue is the license so and the our law lot so I can add to the DG delight at the standard procedure that I'm correctly in that the good require you to use that the Google API to access the bias and the using the party judgments of the pie is not really parameters so what we did to of it simply well do the work and build Google Maps uh netted giant station but that would be used by over the years to bad news that's on the the so with Mary that most of the over the years functions to to have a mapping and the limits I and the we plan to goods to support that uh so that we we can you know use Google Maps inside of annotators and the way we did it is that we simply created and Google Maps petition with that when of CGI but open layers on top of it but it's invisible and when you switch between each other we some queries simply but by Gabon errors or by that's so when you get seamless
that from you get a seamless transition so here you see OpenStreetMap and the maps OpenStreetMap and the toggling between the 2 is it seems like the same application but in fact it's 2 addition and the future in being the future
in Google Maps are drawn with the good of the city I believe the the survey everything is wrong with that limits the job but the features in open areas are drawn with the open there's a child and now we can import all the direction and all the great tool that when there's provided by interacting with open there's at uh features and then there is the difference in meaning despite or representation in the universe again so that we we are using the limits of diet rather it but it is still random was among the 4 forward to support and always be date because it limits the guy that has changed a lot over time so we have to make sure that the the still work and fts to to make it uh make it always work with the current version of the
software of course there are still limitations we didn't support 100 per cent of the library for example the clusters uh are not supported the and the other things like despite functions that were mentioned earlier that already all summing over there's were not boarded needed because there is no such concept in Google Maps so we will have to to take it at the bottom and it's and there's a summer altered addition that are listed in the but all limitation on is that in the in the projects and so that we don't have a good amount uh net Anakin between the quotes would demand integration with over the years as the 2 libraries with you will only cold over there is a petition of the 2 libraries with get things so
a year in the slide the on links to the all the library that we just talk about so there's all ages design makes a big you read that barred showed in the the UPS and the limits OpenLayers 3 and that's the applied you are
on the production and use them for question few thank you thank you both good in time so we have some more time for more questions note OK and I have a question to both In my very very early times we tried something to cope with it maps of the files of art yes or even you and it was always struggling behind necessary 3 because everything changed with every wishing so how stable are your API I think for days and what I've seen with the 3 API
it's pretty stable but of course we wouldn't have like a major version change as yet so I've mostly looked at a 10 10 not axes specifications but I I think it's pretty stable they do add features which shouldn't to of course translate as well but
I would say fairly stable In our case the the the the message i times quite a lot of time there's a she released bravura the and it's not always work were compensable go goes advertised the newer giant events so you can test it and use that and then you see the old version of the Guide for all at once a year I think or something like that so we do have to to be really attractive and there's the new version before it gets out and uh and uh make sure that the old version or by forest of supportive for a few a few months at least uh and so there's some in this library but this then of the made this thing should like so most of the issues for us as the it will we get from and the station for everything's great and but that's that's a really good question because it's also the reason why the open read maps applied in is not inside the core library is because it it always has the potential to break so I remember in the opening to days everyone every time the the limits its I broke the right profitability we would get an e-mail on the open there's mainly and in about an hour or 2 it would be fixed at the point where the with the switch to the version 3 of the directly I and then evidence just fell apart uh and that's 1 of the main reason the developer of the opening the robbery didn't want to discontinue support the library the 1 because it was really too much it and it was best invest the time called like Russell reprojection and good things like that so sigh project because it down yes it does I have chances to to break um but we usually Notre mountain evidence but still dream of is a short time in the development cycle OK so
hopefully you have a good customers pay for that more there's a question the question
regarding the Google Maps API implementation used to open this tool version there was always a problem for concurrency so it from 1 control the of of this kind of we to writing behind which didn't look very appealing is that fixed now that's the whole point of the library at the it has the the the whole point of the initial if for the and this was 1st and
migrate and noble nearest to a petition with more than 2 thousand deployment and 2 on the year 2000 the blood deployment to to open their 3 and we add to form better all the features like the limo support but the main goal of the the library was to fix this the synchronization issue and it it would not be possible to fix them directly in the core library of open there's because it was too would API call a that were not done at the same time so that's why now we so when we show a map all the pieces up and layers are rendered with the Google Maps idiotic instead of with open ears and that makes the the lag between the during the
1 more question is hi OK and Google Maps style so can be contributed projects that we open Lotus Open Street
Map now what do we have to use the Web as a couple of good enough that the eye and needs to be accessed by
the the new guy doesn't support for prediction you with this that
not yet but I'm not sure what with the other things it would be interesting to test with the openers reprojection to see if we can get something out of it but I I don't think it is it would work right now all kinds of things OK thank you both
Offene Menge
Datentyp
COM
Mapping <Computergraphik>
IRIS-T
Extrempunkt
Computeranimation
Addition
Bit
Quader
REST <Informatik>
Merkmalstruktur
Mailing-Liste
Zeiger <Informatik>
Kombinatorische Gruppentheorie
Dateiformat
Overlay-Netz
Computeranimation
Eins
Integral
Metadaten
Transaktionsverwaltung
Dienst <Informatik>
Offene Menge
Programmbibliothek
Dateiformat
Transaktionsverwaltung
Netzwerktopologie
Räumliche Anordnung
Maßerweiterung
Overlay-Netz
Computeranimation
Objekt <Kategorie>
Gewichtete Summe
REST <Informatik>
Räumliche Anordnung
Graphiktablett
Dateiformat
Computeranimation
Umwandlungsenthalpie
Quader
Decodierung
Elektronischer Programmführer
Mapping <Computergraphik>
Programmbibliothek
Weitverkehrsnetz
Vektorraum
Dateiformat
Vektorraum
Dateiformat
Computeranimation
Punkt
Beschreibungssprache
Gewichtete Summe
Dateiformat
Computeranimation
Lineares Funktional
Bit
Funktion <Mathematik>
Last
Projektive Ebene
URL
Physikalisches System
Computeranimation
Sichtbarkeitsverfahren
REST <Informatik>
Quellcode
Computeranimation
Persönliche Identifikationsnummer
Übergang
Open Source
Dienst <Informatik>
Dateiformat
Projektive Ebene
Information
Maßerweiterung
Konfigurationsraum
Attributierte Grammatik
Bildauflösung
Dienst <Informatik>
Projektive Ebene
Videokonferenz
Objekt <Kategorie>
Objekt <Kategorie>
Umwandlungsenthalpie
Multiplikation
REST <Informatik>
Programmbibliothek
Ähnlichkeitsgeometrie
Symboltabelle
Computeranimation
Objekt <Kategorie>
Objekt <Kategorie>
Informationsmodellierung
Stichprobe
Gewichtete Summe
Volumenvisualisierung
Symboltabelle
Ähnlichkeitsgeometrie
Information
Computeranimation
Kreisbewegung
Subtraktion
Varianz
Regulärer Ausdruck
Symboltabelle
Drehung
Zwölf
Computeranimation
Arithmetischer Ausdruck
Volumenvisualisierung
Kantenfärbung
Eindeutigkeit
Simulation
Attributierte Grammatik
Arithmetischer Ausdruck
Klasse <Mathematik>
Volumenvisualisierung
Kontrollstruktur
Drehung
Computeranimation
REST <Informatik>
Information
Computeranimation
Metropolitan area network
Dedekind-Schnitt
Gewicht <Mathematik>
Emulation
Offene Menge
Programmbibliothek
Versionsverwaltung
Weitverkehrsnetz
Dateiformat
Mailing-Liste
Computeranimation
Schnelltaste
Web Site
Elektronische Publikation
Dokumentenserver
Rechenzeit
Klasse <Mathematik>
Applet
Mailing-Liste
Nummerung
Elektronische Publikation
Computeranimation
Mapping <Computergraphik>
Generator <Informatik>
Nichtlineares Zuordnungsproblem
Programmbibliothek
Skript <Programm>
Skript <Programm>
Standardabweichung
Prozess <Physik>
Gewichtete Summe
Kartesische Koordinaten
Mailing-Liste
Gleitendes Mittel
Kontextbezogenes System
Binder <Informatik>
Elektronische Publikation
Mapping <Computergraphik>
Dienst <Informatik>
Informationsmodellierung
Datentyp
Mereologie
Programmbibliothek
Instantiierung
Resultante
Addition
Lineares Funktional
Parametersystem
Gewicht <Mathematik>
Gruppenoperation
Güte der Anpassung
Gebäude <Mathematik>
Abfrage
Kartesische Koordinaten
Gesetz <Physik>
Algorithmische Programmiersprache
Physikalische Theorie
Computeranimation
Mapping <Computergraphik>
Dienst <Informatik>
Spezialrechner
Offene Menge
Mereologie
Arbeitsplatzcomputer
Ablöseblase
Pi <Zahl>
Inverser Limes
Fehlermeldung
Lineares Funktional
Addition
Subtraktion
Selbstrepräsentation
Versionsverwaltung
Sondierung
Computeranimation
Richtung
Array <Informatik>
Funktion <Mathematik>
Flächeninhalt
Software
Prozess <Informatik>
Offene Menge
Minimum
Programmbibliothek
Inverser Limes
Projektive Ebene
Cluster <Rechnernetz>
Klumpenstichprobe
Grundraum
Mapping <Computergraphik>
Rechenschieber
Programmbibliothek
Inverser Limes
Elektronische Publikation
Binder <Informatik>
Umwandlungsenthalpie
Punkt
Wald <Graphentheorie>
Mathematisierung
Güte der Anpassung
Besprechung/Interview
Versionsverwaltung
Elektronischer Datenaustausch
Oval
Iteriertes Funktionensystem
Ereignishorizont
Mapping <Computergraphik>
Offene Menge
Dreiecksfreier Graph
Arbeitsplatzcomputer
Programmbibliothek
Inverser Limes
Projektive Ebene
Speicherabzug
Elektronischer Programmführer
Softwareentwickler
E-Mail
Message-Passing
Lesen <Datenverarbeitung>
Punkt
Datenparallelität
Besprechung/Interview
Versionsverwaltung
Programmbibliothek
Gamecontroller
Implementierung
Vorlesung/Konferenz
Mapping <Computergraphik>
Offene Menge
Besprechung/Interview
Programmbibliothek
Projektive Ebene
Speicherabzug
Synchronisierung
Softwaretest
Mapping <Computergraphik>
Benutzerbeteiligung
Prognoseverfahren
Virtual Home Environment
Offene Menge
Güte der Anpassung
Besprechung/Interview
ICC-Gruppe
Innerer Punkt
Computeranimation

Metadaten

Formale Metadaten

Titel Interoperability with OpenLayers 3
Serientitel FOSS4G Bonn 2016
Teil 143
Anzahl der Teile 193
Autor Eijnden, Bart van den (Boundless)
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/20327
Herausgeber FOSS4G
OSGeo
Erscheinungsjahr 2016
Sprache Englisch
Produktionsort Bonn

Technische Metadaten

Dauer 22:45

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract This talk will focus on the many ways that OpenLayers 3 can integrate with different systems out there. Some of the abilities are integrated into the library itself, think of open standards such as WMS, WMTS, KML, GeoJSON. Other ways to provide integration is through external libraries such as ole, which integrates with Esri ArcGIS REST services (Map Services and Feature Services), or JSONIX to provide parsing (and serialisation) of a huge amount of OGC standards.
Schlagwörter Boundless

Zugehöriges Material

Ähnliche Filme

Loading...