ILWIS, the next generation tool framework for GIS and remote sensing
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 188 | |
| Autor | ||
| 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. | |
| Identifikatoren | 10.5446/31690 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache | ||
| Produzent | ||
| Produktionsjahr | 2014 | |
| Produktionsort | Portland, Oregon, United States of America |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
| |
| Schlagwörter |
FOSS4G 2014 Portland79 / 188
7
10
14
15
16
23
24
25
28
29
33
37
39
40
43
45
46
48
50
56
64
65
69
72
74
82
89
91
98
102
107
111
114
118
128
131
132
135
138
141
143
147
149
150
157
158
161
164
165
166
173
174
175
179
185
00:00
Funktionale ProgrammierspracheSoftwareSoftwareentwicklerInformationssystemWürfelStandardabweichungDifferenteMinimalgradMinimumCodeTotal <Mathematik>TermParametersystemKreisbewegungÄhnlichkeitsgeometrieMapping <Computergraphik>GRASS <Programm>Modul <Software>MAPOpen SourceIntegralDatenstromCASE <Informatik>Minkowski-MetrikPhysikalisches SystemFunktionale ProgrammierungZahlenbereichSatellitensystemBenutzerfreundlichkeitKartesische KoordinatenRichtungBildverarbeitungBitStatistikInformationSharewareVisualisierungFakultät <Mathematik>EntscheidungsunterstützungssystemMereologieEinsDigital Rights ManagementSchlüsselverwaltungOrtsoperatorZeitzoneWasserdampftafelMultiplikationsoperatorFlächeninhaltGeradeProzessfähigkeit <Qualitätsmanagement>Bitmap-GraphikTypentheorieOffice-PaketTaskSystemplattformTeilbarkeitGewicht <Ausgleichsrechnung>Objekt <Kategorie>Streaming <Kommunikationstechnik>Nichtlinearer OperatorFrequenzArithmetisches MittelCoxeter-GruppeDienst <Informatik>Selbst organisierendes SystemWeg <Topologie>Kollaboration <Informatik>RechenwerkSchnittmengeKrümmungsmaßDichte <Physik>Hill-DifferentialgleichungReibungswärmeHistogrammEinflussgrößeSummierbarkeitForcingVorhersagbarkeitRechenschieberVerschlingungComputeranimation
07:31
DifferenteThermodynamischer ProzessProzess <Physik>Funktionale ProgrammierspracheSoftwareDatenstromQuaderService providerOpen SourceAuswahlverfahrenZahlenbereichWellenpaketSatellitensystemKartesische KoordinatenFramework <Informatik>BenutzerbeteiligungImplementierungFigurierte ZahlArithmetisches MittelMomentenproblemGebäude <Mathematik>MereologieAnalytische FortsetzungDiagrammObjekt <Kategorie>MultiplikationsoperatorInterface <Schaltung>Kernel <Informatik>MAPBitBasisvektorSoftwareentwicklerResultanteTopologische AlgebraForcingSchlüsselverwaltungDatenverarbeitungssystemBenutzerfreundlichkeitTermInverser LimesFront-End <Software>VersionsverwaltungModul <Software>MaßerweiterungBitmap-GraphikUnternehmensmodellHyperbelverfahren
15:01
BasisvektorOntologie <Wissensverarbeitung>TermProgrammierumgebungSoftwareentwicklerGrundraumInterface <Schaltung>MomentenproblemProzess <Physik>Topologische AlgebraThermodynamischer ProzessFunktionale ProgrammierspracheKartesische KoordinatenKonstruktor <Informatik>TypentheorieEndliche ModelltheorieMapping <Computergraphik>DifferenteBitmap-GraphikVektorraumWasserdampftafelTemplatePunktVersionsverwaltungDateiformatSystemplattformApp <Programm>BenutzeroberflächeFréchet-AlgebraEchtzeitsystemSoftwareModul <Software>BenutzerfreundlichkeitNotepad-Computert-TestObjekt <Kategorie>Physikalisches SystemWeb SiteDiagrammDatenbankGarbentheorieRegistrierung <Bildverarbeitung>GruppenoperationKlasse <Mathematik>SharewareDatenstrukturVarietät <Mathematik>Open SourceOnline-KatalogGRASS <Programm>SchaltnetzAnalysisZahlenbereichInstantiierungNichtlinearer OperatorEin-AusgabeGrenzschichtablösungBitrateSpeicherabzugCodeVariableDatenmodellCoxeter-GruppeMAPSchnittmengeMultiplikationsoperatorComputeranimation
Transkript: Englisch(automatisch erzeugt)
00:00
Possibly somewhat smaller than GRASS GIS and somewhat more unknown here at FOS4G community. And that's why I'm here to present it to you, to get a bit more visibility on our project. Okay, so I'm going to talk about ILWIS, Integrated Land and Water Information System.
00:24
It's something that we develop at our institute. We are the ITC. Formerly, we were an independent institute, now we are part of the faculty of the University of Twente in the Netherlands, pretty relatively small organization and, well, we're doing
00:45
a lot of things in developing countries like research, teaching and projects. And as part of this, we are also developing our own software. And we do that as part of the 52 North initiative.
01:02
So 52 North is a collaborative platform where research and innovation is combined with software development and the objective is then to advance this development and to get working software. 52 North has this name because we as ITC and also University of Munster and 52 North
01:24
office is at approximately 52 North degrees latitude. So 52 North has different communities, ILWIS is one of them. So there are nine communities in total and this is a very good way to have these
01:45
communities together so that we also have cross development as we do in our software development. ILWIS is a relatively small community but it depends a bit how you look at it. If you count the number of code lines, then we are far more the biggest one of these
02:07
other communities. So as I said, the name stands for the integrated land and water information system. We also have quite a rich history. So we started already in 85 with a small project in Indonesia for doing land use zoning
02:26
and watershed management. Over the years we have been gradually extending the software and I will tell you a bit of history throughout the presentation as well.
02:41
So the key features are in fact raster operations and image processing but we also can handle factor operations quite well. In that sense, I think there is quite some similarity with GRASS GIS also. We concentrate also on map statistics and the projection issues, coordinate systems
03:03
are very well developed within ILWIS. So visualization is also a strength here and the ease of use and that is why the software has been used a lot in countries where we are active, typically in Africa,
03:20
Asia, South America and there we have a pretty large user base. So a bit of history. So we had quite some time of development as a proprietary software. We also had a short marriage with PCI Canada but soon after that we went into shareware
03:46
and finally in 2007 we went open source on a GPL. And in that period we also realized that we had to link with other softwares and
04:00
that is when we started to also incorporate RGC standards. Now here is some functionality pretty much similar I would say again to GRASS. Here you see an example of where we have different layers, the bottom layer is the OSM and on top we have temperature in this case and what we can do is also here do
04:24
a path measurement, that is the line there on the left and then you can do all kinds of histograms, graphics and whatever you like to do there. We have several modules also incorporated, ones on disaster management and this is one
04:45
on spatial decision support system where you can weight different scenarios also by means of a slider as you see at the top left there and then you can apply different weights to different types of tasks and then you can see different scenarios in terms
05:05
of maps here at the bottom. So just one of the functionalities that have been added some time ago. We do also have space time cube functionality. So here you see an example of a black death happening in the last century.
05:27
So don't have the demo here but if you would like I can show it to you. So you can rotate the cube in any direction and then also the bottom layer,
05:40
the reference layer you can move up so with time, so time is on the vertical axis. Here you see another example of a pedestrian research project where you see also again on the z axis the vertical one pedestrians walking in a particular area
06:02
and then you can move these layers like the topographic layer and there's also a thematic layer which could be land use also and then you can exactly see at which positions in time that particular stream of pedestrians were. So there are many applications in fact.
06:23
We also now are applying that to a project called Envirocar which is a crowd sourcing project where people have a small OBD device in their car and then also track their path of driving and at the same time this connector is then storing engine parameters
06:44
like rotation and exhaust. So this is for environmental research. Another module that we have developed is Geonetcast.
07:00
So this is a module which is able to manage information coming from different satellite imagery channels. So you see here an overview of the different satellite coverages so it's pretty much world coverage of different satellite data streams that we can get
07:24
into devices such as these ones. It's actually again a quite low cost solution and not surprisingly because we are again implementing this technology in developing countries.
07:42
So in fact for a few thousand US dollars you are up and running with a cheap satellite dish, a computer and an interface box. So you see here some pictures of training and this is actually what we call our control room at ITC
08:02
where we can receive also all the satellite imagery and do basic processing. So this is what we call the Geonetcast toolbox that has been implemented inside the ILWIS software with which you can manage the different satellite data streams.
08:26
You can select to pre-process and so forth and then you can use ILWIS as the base software then to display the different layers and then do further processing. Also here you see again that it's also combined with a WMS layer.
08:47
So this has been quite a success for us. There have been many projects that have been implementing Geonetcast and that's also the way that our business model that we try to get this funding
09:04
from the different projects also to develop the toolbox further and also to implement that in several countries. So of course we are trying to do this ourselves but by means of the training
09:20
and training the trainers, people in Africa can do that on the long term themselves. So next step, after some time we also again realize that yeah, making your software open is not the only way to get more functionality in it
09:41
and as we also have quite a limited developer base, we realize that we had to make the software also more modular and to invite more people to develop. We thought yeah, C++ and so that's the basis for the software.
10:00
People are not so skilled and there are not so many people who are able to actually help us with this development. So we decided to open it up in a way of modularizing it, refactoring it and also develop yes, also a Python API.
10:21
So we are now in the process and that was just a recent start of getting the software more fit for the future. It's a bit of a hard thing though because we can't find easily the funding because if you go to a project and say okay yes, we have this nice software
10:42
and this is how it works and now we are going to overhaul it completely and we need your money to do that and then the project says okay, but we are only interested in that particular part and we don't pay for that basis. So we are trying now, we are getting some funding from our own institute and we are gradually coming there to build this new basis
11:05
with the small developer base that we have and with internships and so forth. So this is the architecture we are looking at at the moment. So we have in the central part of this figure, this diagram, a kernel.
11:22
We call that the ILWIS objects engine and in fact the whole process that we are trying now to refactor the software we call ILWIS next generation, ILWIS NG. But the final project will be called ILWIS objects. So at the bottom part you see we are now going to provide different data connectors
11:45
so we are able to get different data sources and they will be then transparently built and are going to be used by anyone who is using a particular data source and is not actually even aware of that.
12:02
It is either PostGIS or WFS or any other source. So we are also building these process connectors for different processing parts like WPS and so forth and then on the top end you will find the different user interfaces
12:22
so via Python API people will be able to access ILWIS functionality. And then the desktop is also important because of course people also want to see the results of these processing, this functionality and see a map.
12:42
So that is something that we are now kind of ready to start also to get the functionality of what I would call the current ILWIS into the new setup. So modularity and extensibility is important, interoperability of course,
13:02
but we also think that we are providing high performance processing for satellite imagery because the back end of the ILWIS engine is really constructed in such a way that it can handle large satellite imagery and raster data.
13:27
The ease of development is of course also an important issue because we would like to extend the software not only with our own developer base but also outside. And then also support web and mobile users. I will come back to that a bit later.
13:43
So this is currently the developments, the things that we have done already. So we have interface of course with GDAL and WFS and then we have now almost this Python API ready.
14:03
Short-term things that we are working on now is PostGIS and also on the ILWIS applications as I said that we had already in the current ILWIS. And then so the current ILWIS actually called ILWIS 3.x, so 3.8 is the latest version
14:23
and the new framework-based ILWIS is going to be called ILWIS 4. And our implementation is in QT. So here an example of the Python API.
14:41
So the good thing is that we have our functionality as we already have it as I said. So this is just an example of calculating NDVI. And what we are doing here is also using, reusing NumPy library. And that's the big win I think here that people can not only use our functionality
15:03
but combine it in a fairly easy developing environment with other types of functionality. So our ILWIS Next Generation can be found here on GitHub. You will find some of the documentation here.
15:22
And if you want to get to start with it, just go to this website. And then there are several tutorials already available. So this is the new, the next generation. If you want to learn about the current ILWIS 3 desktop applications,
15:42
you have to go to the 52 North side and then go to the ILWIS section. Okay, object diagram. I'm not going to zoom in here, but it's available also on the same website if you want to know the actual details behind it.
16:01
So as I said, we are involving internships, people like student assistants and also to help us with the development. And recently we also had a Google Summer of Code candidate and he did quite a nice job developing a mobile application based on ILWIS.
16:25
I have it here if you want to see it working, then I can give you a short demo. Actually, what is it? It is a universal data collection application with which we can do collection in terms of, for instance, water point mapping, land use mapping,
16:44
disease mapping, registration of cholera patients, registration of malaria patients and so forth, all in one app and then with a flexible template structure. So if you need it for one application today and then the next application tomorrow,
17:01
you can change the template and these templates will be, so currently it's under construction of course, but they will be shareable also between different platforms and different applications. How do we do this? These templates will be based on ontologies.
17:23
So what we are currently implementing in a project which is on water mapping is the relationships between the different relevant classes. Maybe we can zoom in a little bit here. So you see the different actors here, different devices
17:42
and also the different classes for mapping functionality of water tap. So these are all defined in this ontology here and we are now in the process of using this ontology as a basis for creating the templates in this particular application.
18:05
So the actual future for ILWIS and then version 4 is to actually go on with these use of, ease of use
18:27
and then make it also possible for people to do the processing and the mapping in one interface. And we are planning to implement a kind of model builder type workflow system here
18:44
where you will be able to choose your data layers from a catalog on the left hand side and then create workflow in a diagram as you see. This is a mockup so it doesn't exist yet.
19:00
And then you will be able to drag and drop and then to change and to move these things around and then in real time we need to have the map available and you see this works like a slider kind of interface. So that's the near future. And then we have some things that we need to do.
19:23
Some headache things maybe. We are going to create a web interface also that we are not stuck to the desktop as we are at the moment. And then we are planning to also make use of QGIS in a sense that we are going to develop just similar to what Gras has done already and Sextant
19:45
to make our toolbox available within the QGIS interface. We are not there yet. We actually think that we might lose some performance there doing this. So we will have ILWIS also as a separate software there.
20:03
But this would be good also to increase let's say the user base somewhat more. So improving developer community, that's why I'm here also to talk with other people to see how we can actually do this and then, yeah, documentation.
20:23
Okay, thank you. Yes?
20:42
Thank you for your presentation. Does your application have any ability to deal with LIDAR data? Do you process that at all? Or do you have any modules that are specific to that data type? I think currently not. No.
21:00
Short answer. Would you be interested? Yes. Okay. We can try to maybe talk afterwards. No questions? Yeah, another one? What does it use as the underlying, so you talked about vector and raster formats
21:23
and the number, what types of data modules does it port to? For instance, does it read from Postgres? What types of databases and file formats are you able to incorporate? Yeah, Postgres, of course. As I said, well, we are currently having a kind of transition
21:45
from the LWIS 3 to the LWIS 4 version. So we're using GDAL as a library so we can actually enter all the things that are supported by GDAL.
22:00
And then, yeah, WFS. So, yeah, that's quite a variety of all these sources that we can handle. And, yeah, naturally they will also become available in the next version as well.
22:27
Yeah? Okay. Thank you.