We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Offline viewing and editing Geographic Information for Forest Fire Defense

00:00

Formal Metadata

Title
Offline viewing and editing Geographic Information for Forest Fire Defense
Title of Series
Number of Parts
295
Author
Contributors
License
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
As part of the Open DFCI project: Geographic Information Portal for the Defense of Forests Against Fires, the Entente Valabre for the Mediterranean forest wished to put in place a solution of offline viewing and editing geographic information. We will presents the context: OpenDFCI web portal based on Lizmap, the firemen needs, the Geoppopy choice: Raspberry Pi Standalone WebGIS Server, and the realisation.
Keywords
Multiplication signPresentation of a groupForestSoftwareWeb 2.0Context awarenessLevel (video gaming)Special unitary groupSoftware testingFluidShared memoryWave packetRule of inferenceGame controllerLecture/Conference
Web serviceComputer hardwareAreaWeb serviceDenial-of-service attackNatural numberTime zone
Natural numberContinuous trackOntologyConstraint (mathematics)Field (computer science)Data structureData typeDigitale VideotechnikTrailBitWater vaporProjective planeGroup actionForestAttribute grammarAreaField (computer science)Data storage deviceLevel (video gaming)Digital photographyEndliche ModelltheorieExtension (kinesiology)Graph coloringVector spaceTable (information)Electronic mailing listLetterpress printingObject (grammar)TouchscreenGeometryHydraulic motorDivision (mathematics)Type theoryDigital libraryConstraint (mathematics)Symbol tableData structureGenetic programmingShared memoryMetadataDifferent (Kate Ryan album)VolumenvisualisierungComputer animationSource code
Ordinary differential equationCategory of beingProcess (computing)Server (computing)Client (computing)InformationSoftwareLocal GroupAuthenticationConfiguration spaceNetwork topologyAttribute grammarFinitary relationWorld Wide Web ConsortiumTrailField (computer science)Data structureCodeProjective planeMappingLevel (video gaming)Focus (optics)Digital rights managementAuthenticationPresentation of a groupGroup actionCategory of beingDifferent (Kate Ryan album)AreaCybersexAdditionExtension (kinesiology)Connected spaceProcess (computing)Cartesian coordinate systemSpacetimeData storage deviceWeb 2.0Server (computing)World Wide Web ConsortiumSelf-organizationSoftwareTable (information)Web applicationAttribute grammarDiagramComputer animation
SurfaceExtension (kinesiology)WebsiteCodeCharacteristic polynomialPrincipal idealMenu (computing)AreaTable (information)Numbering schemeWeb serviceDefault (computer science)EmailLocal ringDatabaseCuboidLevel (video gaming)Vector spaceForm (programming)Web 2.0TouchscreenLetterpress printingDatabaseWeb pageMappingProcess (computing)Forcing (mathematics)
Numbering schemeLocal ringAreaTable (information)Web serviceEmailDatabaseDefault (computer science)System administratorEmailProcess (computing)Server (computing)DatabaseWeb serviceData storage deviceArithmetic meanSource codeComputer animation
Field (computer science)Constraint (mathematics)View (database)InternetworkingDemo (music)Attribute grammarBuffer solutionForm (programming)Computer-generated imageryElectronic mailing listAuthenticationLoginData managementTable (information)Digital filterSynchronizationFinitary relationDatabaseServer (computing)Conflict (process)Tablet computerAndroid (robot)Projektiver ModulConnected spaceInternetworkingWeb 2.0Projective planeLevel (video gaming)Form (programming)Expected valueWindowView (database)Android (robot)Buffer solutionTablet computerOpen setSoftware development kitField (computer science)Power (physics)Visualization (computer graphics)Attribute grammarMobile WebSoftware testingSound effectDeclarative programmingHTTP cookieComputer animation
GeometrySoftwareClient (computing)File Transfer ProtocolServer (computing)PlastikkarteComputer hardwareFrame problemLaptopWeb browserGraphics tabletWeb 2.0Flow separationServer (computing)CuboidSoftwareProjective planeComputer animationJSON
Server (computing)Web browserInterface (computing)Computer fileGeometryOpen sourceComputer hardwareSoftwareConstraint (mathematics)View (database)Vector spaceFile formatRaster graphicsAuthenticationData conversionForm (programming)Line (geometry)Web browserAndroid (robot)MappingField (computer science)Interface (computing)Computer fileGoodness of fitSoftwareObject (grammar)BitMultiplication signCartesian coordinate systemWeb 2.0Open sourceAuthenticationServer (computing)Level (video gaming)Table (information)Tablet computerConnected spaceGeometryPower (physics)Boss CorporationArithmetic progressionNeuroinformatikLine (geometry)SmartphoneComputer animation
SynchronizationField (computer science)SynchronizationTable (information)Computer animation
Phase transitionGroup actionData managementField (computer science)DatabaseHypermediaSynchronizationServer (computing)Key (cryptography)Hill differential equationRevision controlInformationSource codeMetreMultiplication signGroup actionTable (information)Intrusion detection systemQuery languageProcess (computing)Prisoner's dilemmaComputer animationSource code
LogarithmSynchronizationField (computer science)ImplementationServer (computing)Process (computing)Menu (computing)Hausdorff spaceDirectory serviceGroup actionTable (information)SmartphoneModule (mathematics)AlgorithmFeedbackMetadataTablet computerServer (computing)SynchronizationField (computer science)Process (computing)Asynchronous Transfer Mode
Level (video gaming)FeedbackServer (computing)Complex (psychology)Interface (computing)Portable communications deviceSoftware testingClient (computing)Computer hardwareSynchronizationElectronic visual displayAndroid (robot)GeometryFeedbackWeb servicePower (physics)SoftwareOpen sourceTablet computerLink (knot theory)Server (computing)Chemical equationBitoutputKolmogorov complexityData storage deviceAndroid (robot)AreaLetterpress printingExecution unitSmartphoneGradientComputer animation
Client (computing)VideoconferencingAndroid (robot)Server (computing)Link (knot theory)Level (video gaming)Web browserProcess (computing)Server (computing)Multiplication signJSONComputer animation
Field (computer science)Water vaporArithmetic progressionFeedbackForm (programming)Projective planeProof theoryOpen sourceDatabaseAreaProbability density functionScripting languageSoftware maintenanceLevel (video gaming)Link (knot theory)Client (computing)Software testingTablet computerAttribute grammarMathematicsServer (computing)Multiplication signSocial classForcing (mathematics)Right angleScaling (geometry)State observerSoftwareGroup actionCondition numberPresentation of a groupLecture/Conference
VideoconferencingAndroid (robot)Server (computing)Client (computing)Link (knot theory)SummierbarkeitKey (cryptography)Android (robot)WebsiteField (computer science)Computer animationSource code
Software testingOpen sourceClosed setComputer animationLecture/Conference
Transcript: English(auto-generated)
OK, so I think I will start. It's the right time. Welcome to this presentation. My name is Michel Duchamp. I work for the Threeliz company in France.
And basically, we had people to use QGIS, PostgreSQL. And we have a web map publication app, which is called LizMap. And today, I will show you feedback on a solution based on the offline special server, which
is called Geopoppy, in the context of the forest fire defense. So let's talk about the stakeholders, data, and software used today. Vallabra is a French public institution. Their main mission is to help actors
to prevent and fight natural risks, like fires, floods. And so they test new technologies. They do some trainings, research. They share services and hardwares. And they work with partners in the French Mediterranean areas.
So that's some pictures. You can see firefighters and so on. A bit of history of the project. We will speak about a small topic in their missions.
But it's about the firefighting infrastructures, like water tankers, tracks, road tracks or forest tracks, watchtowers, and so on. And they have also standardized grids to be able to know where some actions must be taken.
So they share standardized grids. And they have, obviously, base layers, like photographic IL photos and digital television models and so on. They have done a lot of work to harmonize and centralize
the data between all the stakeholders, which means they have set up a list of layers to share. What are the names, the metadata, the ontology? What is it about? They agree on the data structure, like the fields, constraints, the types, everything.
You need to agree on your attribute tables and the geometry type. They have created common glossaries. They share the same way to describe the data. And they agreed also on the data styling, which
means symbology, the colors used. Because when you're in the field against the fire, you really need, if you work on an area in the frontier between two different administrative areas,
you really need to be quick to see in the map what is this object, this object. So you need to share how you will render the data in a map. The extent is the French Mediterranean areas. It's about around 100,000 square kilometers.
And it represents 200, but it depends on the data. Four vectors and 30 gigabytes for our stores. That's a print screen of the data.
So you can see some water tanks. You can see the tracks here. And the weird grid they use in the field to locate the different structures and to see where they have some codes with that.
Sorry. This is the main area, so the special extent of the project. They already use some software since some times. QGIS is the main GIS used in Vallabh, which is the organization I talked about.
But some actors also use different GIS solutions, like MapInfo, S3, or GeoConcept, which is a French GIS, very old one. And they use PostgreSQL to store and process data. They have an hosted server.
And they also use the application LizMap Web Client, which is made to publish web maps from QGIS. So I will really focus this presentation on this triptych. It's QGIS, PostgreSQL, and web publication with LizMap.
What is LizMap? Basically, you take your QGIS project. You send that to the server. And you have a web application which render a map based on the project properties and layers.
And it respects a lot of QGIS features, like attribute tables and so on. One of the key features for the Vallabh is the authentication and group rights management. So you can tell this map can be seen by these groups of users or not. These kind of users can edit the data or not and so on.
Some print screen about the solution. So that's the main page. You have a map in QGIS. You get it in LizMap. You can have more complex data.
This is one of the key features. You can edit data with forms based on QGIS forms. So you don't have to code your form. You just describe it in QGIS in the vector dialogue with combo boxes, check boxes. And you get that back inside LizMap.
So they use this kind of maps since three years. So they are very used to this web map solution. And they also have organized a PostgreSQL database to be able to share data and to do
some processing in the server. For example, they use Triggers Python services to send emails when somebody has modified data to the admin. And then when the data is validated,
you get an email back to tell you, OK, your data has been validated by the admin user. So they have a complete, it's not just a storage PostgreSQL. They use it with all the features you can expect from this kind of database.
The project objectives, they wanted to use this web map solutions, but offline. Because sometimes you have no internet connections when you go to the field, for example. And they ask us to help us to test
this solution in the field. So they needed GIS features like the same we talked about, like data editing, base layers, attributable visualizations. And they needed the tool to be based on QGIS projects
to simplify the workflow. They didn't want to do some more styling for another tool. They did not want to recreate web forms from XML. I don't know what. And they also needed to have some PostgreSQL views offline
to be able to see some buffers or some data special analyses that you can do with SQL views or triggers and things like that. They have no internet connections in the field. In France, you can have internet connection.
But when you're a firefighter, you really need to have a tool which can work without internet. So one of the other expectations was
they needed to be able to synchronize the data when they get back from the field. So they didn't want to use the copy-paste and manual checking of the data afterwards.
They asked us to try to help them to synchronize it easily. So they have studied some solutions, like Windows tablets or Android tablets. Can they use a simple but powerful data collection tool,
like Open Data Kit or QGIS-based mobile solutions? They preferred the latter. And then they tried Qfield, but did not like it for some reason. And I haven't spoken enough with them for that. But they told me, we want to try Geopoppy.
So what is Geopoppy? Geopoppy has been around since, I think, three years. Basically, it's a special server in the box. Like you take a Raspberry Pi with battery,
and you put a LISMAP web client, QGIS server, PostgreSQL, and an FTP server inside a Raspberry Pi. Then you can have an offline web server solution. The main concept of that is Julien Anselin from a research center in France.
And he based the work on Docker, how do you update the softwares, and how do you package all the different softwares inside this box. It is already used by researchers,
like in France, and also for some projects in Africa, in Africa, to collect rain deforestation data, and in Madagascar, too, for another project.
So this is a Raspberry Pi, very naked one. And when you use it, so you put QGIS server, you put PostgreSQL and LISMAP, and then you connect with Wi-Fi, with your smartphone, tablet, or computer, you connect to it.
So that's a bit of another picture, which shows it's not very packaged. So you need a bag to put that. I think it's a little bit like do it yourself, look and feel. So that's some disadvantages of this tool.
It's tied to web browser capabilities, because you use a web browser like Firefox or another one to see the map. So you need to use the geolocation API. You cannot really save files locally, et cetera.
And the LISMAP web client application is responsive, but it's not dedicated to field data collection. So you have some improvements that can be made. And one of the problems in Android OS is you cannot connect to 3G, 4G, or 5G, and to the Wi-Fi
at the same time. So it's offline with the geolocation, and you will use the LISMAP and the PostgreSQL. And you cannot do that and be connected to another network to gather some external data.
But you have some advantages for them. It's open source. It's affordable, because the Raspberry Pi is not very expensive. You work offline, and you have no new software. So you use QGIS, QGIS server, LISMAP, and PostgreSQL.
For them, it's a known workflow, because they used that before to publish the web maps and data to the central server. It's PostgreSQL powered, so you can use all the good stuff in PostgreSQL. You can use all the features of QGIS to style your layers
and to show some data. And you can also use the authentication and other LISMAP features. Some pictures of the LISMAP interface.
So you can see data on objects. You can start editing data in the field. And so for them, it was OK, because they use LISMAP in the desktop when they're working, and they can use the same tool in the field.
They needed, when you work in the field offline, you need to package the data to be able to go to the field. And then you need to go back and synchronize the data. So for that, they asked us to develop some synchronization
meter. So we wanted a very, very small PostgreSQL-based solution. So we just used unique IDs in every table. And we developed some tools based on QGIS processing
to run the queries to be able to synchronize the data. I won't spend time to present this, because it will be a bit long. But the main goal is to have a log with audit of every actions made in the PostgreSQL
server for every tables. And then you can replay this log, because you know which device has created or updated the data. And you have all the synchronization data,
metadata in the central server. So basically, in QGIS desktop, you have a processing algorithm. And you can find the same algorithm in the LISMAP WPS module. So you can use it in QGIS and in LISMAP
with your smartphone or a tablet in the field. It's the same algorithm which does the job. And as a conclusion, I will give some feedback. It works. So some people are very excited about this solution,
because it's low cost. It's a full powered special server based on open source software, QGIS, PostgreSQL, LISMAP. But I think it's also a bit complicated for users, compared to some other solution based on QGIS, like Qfield.
Or the last one is input, which is a great tool, too. But I think the main problem here is the fact that you have others to carry, like the Raspberry Pi and the battery. And if we want to make it more user friendly,
there is a solution ongoing, developed by Julien Anselin. You just take all the features. You put that on your Android, which means you don't need your Raspberry Pi. All the servers are packaged to run on your phone,
on your tablet. So you just need your smartphone, your tablet, and you will be able to have the same thing, PostgreSQL, which is running on Android now. And so I think that can be a great solution. But you really need to evaluate
the balance to balance between the complexity of your needs. Do you need complex PostgreSQL, QGIS features, or not to choose to use that solution? But with PostgreSQL running on Android, you can also use Qfield or input
to speak with this data storage. Some links on Geopopy and PostgreSQL audit tool, PQGIS server based on QGIS processing algorithm, and how do you on LISMAP web client.
I will thank you for your attention. I think he is right on time. If you have some questions.
Only one. Does it work? Only one question, actually. Basically, as I understand, the first thing you had to do in this project was to make some kind of atlas of fire equipment
in the field. Then you can, and you could, your first step was probably to get the, so all the shareholders agreed on this at some level about the science and everything. And I'm asking, is this atlas also possible
to get in some kind of paper form or PDF or something like that? Sure. I talked about it in the history. They have already make all this stuff. They have paper atlases. They don't rely on Geopopy for emergency situations.
It's only to go to the field, see if the water tanks is OK or not, change some attributes. So it's not the only solution they use. They really reuse QGIs in desktop and PostgreSQL
to centralize and share all the data. But they have paper. They have other tools, like proprietary tools also to deal with the data. Geopopy is like a proof of concept. They really want to know if they can use it in the field or not. And they were able to use it, but we
have some progress to make. Did you test how many clients can hang off the Raspberry Pi and maintain performance? I have some feedback by Julien Slant.
He told me like five people can use the Raspberry Pi. So that's OK because you have the Raspberry Pi in the backpack and you have different people in the same area that can gather some data. So for deforestation data, for biology observation,
like if you see a bird or you see something, you can work together with the same database. But really, it won't scale.
If you're 10 or 20 people in the same Raspberry Pi, it won't. But if you have an Android solution, you can have as many server as you have devices. That will be the solution.
Hi. Sorry. Just one question. I didn't get it. Did you sell that? Or is it open source? And how do you sell it like with the Raspberry Pi and the software? And what is the education of that users? How do you educate the users for that?
OK, so we do open source. So everything is open source. The synchronization, PostgreSQL scripts is not yet published, but there will be. What we did for this project is just
buy the job, the Raspberry Pi, and all the tablets for Valab, because it was easier for them. But we just sell them the same price. So we don't earn money with this project. It's a side project of Thrillies. But it's mainly used by researchers and by NGO,
because you can just grab all the sources, the documentation. You have the link at the end of the presentation. And you have a good documentation
of how to get the image, put that on your Raspberry Pi, and then use it. So you can test it with no problem. You can already test it on Android. There is a GitHub describing how to do that. So I will just try to.
So that's data of flower, like poppy sites in the field. So it's open source. Of course, it's open source. There is nothing closed.
No more questions? OK, so thank you very much. Thank you very much.