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

Favoring Opensource Technologies for French Fire Brigades

00:00

Formal Metadata

Title
Favoring Opensource Technologies for French Fire Brigades
Title of Series
Number of Parts
351
Author
License
CC Attribution 3.0 Unported:
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
Production Year2022

Content Metadata

Subject Area
Genre
Abstract
The NexSIS project aims to create a digital rescue platform providing all civil protection actors in France with a complete set of cloud operational services. Open Source GIS solutions were chosen for this national project with strong technical requirements. This has a direct impact on the way data will be exploited. Each Fire Department will have to adapt and create data that will be directly used by the NexSIS software (areas that require special equipment or specialized teams for example). Currently in France each fire department has a budget depending on the size / number of people in the department. This budget is used to buy new fire extinguishers, computers, but also to hire new people, etc... Most departments currently use many different proprietary softwares for all GIS aspects. Historically, each department has made their own choices on what software they use. This talk will show how we are helping fire brigades to make the switch to Open Source without losing any functionalities and without any extra work load. Using the power of both QGIS and PostgreSQL, we will show how these tools can be used to share and publish common workflows (qgis expressions, model builders) that are often used in fire emergencies, build a common atlas (report module), edit spatial data (forms, and constraints) and so forth.
Keywords
202
Thumbnail
1:16:05
226
242
Open sourceInformation securitySoftwareCalculationCore dumpData structureTime zoneRoutingVector spaceAddress spaceSearch engine (computing)Query languageSubject indexingElectronic visual displayWebsiteOpen setServer (computing)Point cloudUniform resource locatorSoftwareDifferent (Kate Ryan album)Operator (mathematics)DatabaseAddress spaceRoutingBuildingOrder (biology)AreaDenial-of-service attackCalculationScalabilityShared memoryOpen sourceFlow separationMilitary baseFeedbackMappingData structureLattice (order)Sign (mathematics)Projective planeQuery languageEndliche ModelltheorieMoment (mathematics)CASE <Informatik>Multiplication signCartesian coordinate systemTesselationData storage deviceBridging (networking)Compilation albumOpen setWeb 2.0Point cloudFormal languageGeometryServer (computing)System callElectronic visual displayLie groupForm (programming)DialectComputer animation
Transcript: English(auto-generated)
Hello, so I'm going to talk about working, the work that has been done with open source technologies for French fire brigades. So the way emergencies work in France, this is the following, there are around 100 different departments which are called French regions, and each region will decide on what kind
of software they're going to use, they're going to have different workflows, many different lingos, that means they haven't got the same names for the same trucks. And of course, each department is different, you're not going to have the same missions in Paris than you have in the Alps or in the centre of France.
Some department will have GIS teams and GIS data, some of those won't have anything. Also one of the most important things is nothing is centralised, that means when you're going to have an operation which is on several departments, it's complicated to coordinate
and to share information in between these entities, like it was the case earlier in the summer, we had big fires. And also at the moment there's no data sharing and very little feedback. So what is Nexus? It's an ambitious web-oriented software that is being built for the past three years.
And what it does, it uses GIS data at its core, so from the person calling it will be located using the GPS and advanced mobile location. It will use spatial data to determine in what area the caller is, does it need special
lorries if it's in a flooding area, if it's next to big buildings and so on. And it uses routing in order to calculate the fastest route depending on the size of the fire engine, so you can't have a two-tonne lorry on a one-tonne bridge, so that
takes that into account. And more importantly, it makes all departments have the same application, the same lingo and the same database structure, and also like it's going to save lives, it needs to be optimized and have fast calculation time.
And all this is done using open source technology. So the main application uses open layers to display and create the data on the website. It will use PostGIS to store data and query data. And it uses PG routing for fast calculations.
There's a special talk from one of my colleagues on PG routing later during the week. GeoServer and bare maps are also used to render this data, so we've developed a special cloud-optimized GeoServer that also is a talk on this later on, and the
same for bare maps, which renders vector tiles. Also, we use our doc, which is an open source technology as well, for full text address search. Locally, then there's lots of work to be done, because like I said, all departments
aren't the same, so we've done many workshops and we have regular meetings to build the structure of the GIS data and have the same model based. What that does is enables us to use the same software locally for each department, so we use QGIS and PostGIS to edit the data, and of course, as everybody's using the same
software and the same data structure, you can share forms, QGIS projects and models. In conclusion, a very interesting project. It will reduce the complexity, because it will be one single application.
In some departments, they have five different software, and with Nexus, it will be one single one. As I said before, we're going to have a sign language, so each five departments will use the same name for this library, the same name for this mission. Data will be shared, and there will be lots of feedback that is not used at the moment,
and what's quite interesting is that it proves that you can use open source technologies in a scalable way in order to try and save lives. Thank you very much.