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

GeoMapFish status: vector tiles!

00:00

Formal Metadata

Title
GeoMapFish status: vector tiles!
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
GeoMapFish is an open source WebGIS platform developed in close collaboration with a large user group. It targets a variety of uses in public administrations and private groups, including data publication, geomarketing and facility management. OpenLayers and an OGC architecture allow to use different cartographic engines (MapServer, QGIS Server). Recently new features have been added such as vector tiles integration, from raw data to visualization. In order to get rid of AngularJS dependency, a roadmap has been established for a migration to a web components architecture. Everything has been planned so that our users can continue to develop their projects during this process. K8S support is evolving with the implementation of the necessary tools for Azure environments. Highly integrated platform, large features scope, fine grained security, reporting engine, top performances and excellent quality of service are characteristics of the GeoMapFish solution. In this talk we ll present the key usages, web components migration process and latest developments, including vector tiles support.
Keywords
202
Thumbnail
1:16:05
226
242
Euclidean vectorOpen sourceDemo (music)Interface (computing)User interfaceMobile WebData modelSoftware maintenanceText editorDecision theoryOvalOpen setVolumenvisualisierungTable (information)Raster graphicsUniform resource locatorQuery languageOpen sourceBitLevel (video gaming)Server (computing)Vector spaceImplementationInterface (computing)Client (computing)System administratorProjective planeComputer architectureQuery languageMobile WebTessellationStandard deviationDatabaseLink (knot theory)Internet service providerWeb 2.0Demo (music)MappingSoftwareExpert systemSoftware frameworkEndliche ModelltheorieVisualization (computer graphics)TouchscreenText editorDebuggerComputer fontEuclidean vectorComputer fileTesselationSet (mathematics)Image resolutionSoftware developerDecision theoryMultiplication signProduct (business)GeometryType theoryConfiguration spaceComputer animation
Euclidean vectorStandard deviationQuery languageVector spaceData managementClient (computing)Server (computing)Probability density functionWeightSoftware frameworkAnalytic continuationCloud computingRevision controlProof theorySoftware developerClient (computing)TesselationHuman migrationGoogle Street ViewProjective planeProcess (computing)Letterpress printingWebsiteVector space2 (number)Element (mathematics)Library (computing)SmoothingIntegrated development environmentData managementServer (computing)ImplementationEvoluteProduct (business)Shift operatorRange (statistics)Internet service providerQuery languageTessellationWeb 2.0Euclidean vectorInformationMusical ensembleLevel (video gaming)Control flowArtistic renderingModule (mathematics)Probability density functionPower (physics)Computer animation
Point (geometry)PixelLarge eddy simulationBit rateLine (geometry)Standard deviationGraph coloringRoutingWeb pageLevel (video gaming)Student's t-testInterface (computing)Module (mathematics)Projective planeOffice suiteSlide ruleCartesian coordinate systemGraph (mathematics)2 (number)Physical systemWebsiteInstance (computer science)Computer animation
User profileDemo (music)Cartesian coordinate systemWeb 2.0Revision controlEuclidean vectorDemo (music)Profil (magazine)Content (media)Computer animation
Demo (music)Demo (music)Link (knot theory)WebsiteMusical ensembleComputer animation
Transcript: English(auto-generated)
Okay, so yes, we are going to talk about geomafish, the status of the project, and also about vector ties, but much less technical stuff. Okay, I will quickly talk about the company and what we do, and a lot about geomafish
vector ties. It's a first implementation vector ties in geomafish, the big step of migrating geomafish to web components, and about Kubernetes support, and so project examples.
So welcome to camp. So we are open source service provider since 2001. We are bigger and bigger, more than 150 employees now. I was the sixth employee in 2006 when I joined the company.
So yeah, we are also contributors, not only service provider. We use a lot of agile software development, and we have experts in DevOps, et cetera. And yes, we are the largest European service provider for a geospatial open source.
Geomafish is a flexible web GIS. You can see here screenshots of the demo project. It's highly customizable. It's more like a framework than a product.
It's highly interoperable with all the standards using QGIS server or map server or the map provider. We have a desktop interface with a lot of features, a bit too many features for the
mobile. That's why you have a mobile interface too, and a very rich administration interface to be able to add layers, add themes, also manage all the holes in users, et cetera.
So Geomafish is a community-driven project. We have quite a large community of more than 20 members and a project steering committee. So I didn't tell that before, but you saw the map. We are in Switzerland, but also in France and in Germany.
Originally, Geomafish was more a Swiss project, but now we have also customers in France and in Austria, and maybe soon in Germany. I'm not sure. So community members are Swiss cantons, cities, but also in private sector.
And we are a member of this community as the editor of the solution. So the goals of the community is sustainable development, so promote dialogue between the members, decision-making, fair funding, and also the fact that we have
several members, so the contribution level can be lower. And this model works since 2011. So this is about Geomafish, what it is, and now let's see the new features of Geomafish.
We just released 2.7 release. So you know what is vector ties, of course, but for our customers, it was important to
have this support added to Geomafish because we have more and more services offering vector ties. The advantages, you know them, adapt to screen resolution, the custom size on the client side, light files, and also much faster to generate new set of data.
So the first implementation Geomafish, it was quite a small project, actually. The budget was not very big, so we had to choose and not do full support of vector
ties in the solution. But that was important for us to have this implementation, this first implementation at all levels. So from the data in the database to the visualization on the front end.
So screenshots, yes. We have here a map with vector ties. Actually, it is a partial implementation, so only base maps can be vector ties right now. We had to change the administration interface to be able to add this new type of layer.
So this is what you see here, a screenshot of the administration interface. Maybe a bit more technical is the architecture of how we did that.
So as I said, we changed the administration interface to be able to configure the SQL query that will be the way to extract data from the PostGIS database.
And also, we have a link to the style. The vector ties service in the middle here, for each request from the client, it will get the SQL query, add what it needs to be added to be able to get just one tile
in the database, and also get the style, of course. And this will give the vector tie that will be sent to the client.
And all this, of course, is done n-types when you have to display n vector ties. Okay, as I said, it was in partial implementation, and so what we did not do and that we would
like to do if we have the funding for that. And adding, of course, the standard layers, not only the background layers, adding the possibility to have the query on vector tile. It can be either from the vector ties itself, when you click on it, you have the information
that is into the vector tile, or using WFS as a fallback. We are also thinking about PDF print, because we have a quite powerful print module in geomapfish,
so it would be interesting to have the print also for vector ties. It can be on the server side, as it is now with mapfish print, what we use for non-vector ties, but it could be also done on the client, it's not fixed now.
We have some improvement to do with the style management, and on the client side rendering, right now we use open layers, but we could use something else, maybe to be able to have
maybe more powerful rendering on the client side. Okay, so the second big news about geomapfish is the fact that we are migrating to web components.
That was quite a challenge actually, because we are using right now AngularJS, and AngularJS is at the end of its life, and so we had to change it. So last year we had a big thinking with the whole community of geomapfish, how to get
rid of AngularJS, and so we had a big analysis, and we decided to go to web components using elite elements, so it's quite a light library, and one important goal was to have a smooth
migration, because for customers it's very important to be able to continue to use, to update, and to improve the framework, and to of course continue to update and improve their projects using the framework.
It was totally impossible to stop and to do the migration and then continue with the new version. So, we did some proof of concept that will be now followed by an iterative process to have at the end a non-AngularJS client, and also one important aspect also is that
all developments, including the proof of concept, are reusable. It was important from the beginning of the proof of concept that all developments were
reusable. It's not a proof of concept and then to the trash. So this is our roadmap for migrating geomapfish. So, the 2.7 is out, it was out like a couple of weeks ago, or maybe one month, and it's
stable, it's a long-term support version. It proved the concept, and also it includes all the breaks that are needed for continuing
this process of migration. Also, on our project aspect, it is important also to have better estimates, and so we did some migration of some components, and now we know more how long it takes to do every
component of the solution. Next year, we will have the 2.8 with more web components migrated, and the goal is to have in 2024 the version 3 of geomapfish without AngularJS.
Another evolution of the product is the fact that we are supporting more Kubernetes
environments. So, with the 2.6, it was possible to use OpenShift. The goal was to have a Swiss cloud provider because many of our customers want to be hosted in Switzerland, but we needed to have a wider range of providers, and so with the
2.7, we did what was needed to have the support of Microsoft Azure. Why Microsoft Azure? It's also because it is hosted in Switzerland, and AWS, it's not guaranteed.
Okay, a couple of examples of geomapfish implementations. Here we have the Carto-Lacote project.
It's a project of the municipality of Nyon next to the Lemon Lake, Lake of Geneva, and also other municipalities around. What is interesting here is that they have a lot of themes with a lot of layers inside
each of them, and so, yeah, they did a very good job also with the monetization. It looks good, and for the screenshot, I open also the fact that we have Street View module
in the geomapish. That is not new, but that was nice to have the castle of Nyon. Another project is a project at EPFL. It's the polytechnical school in Lausanne.
Until very recently, we had our office next to this school, so it's a historical customer. Now we are moving. This project is interesting on different aspects.
First, it's one of our projects that has the most customized interface. What you see on the left here is the interface of the public application for visitors, for students of the school, and this is highly customized.
This is not at all what looks the standard geomapish. And so, yeah, this is very interesting. They have also a routing module. Here we can see the line of the routing.
I don't have a screenshot here, but they have a second application for professionals, so it's not only, oh, yes, it's the next slide. Okay, I will tell you about that next slide. Here, below, it's possible to include a map in their website.
It was important for the school to have, for instance, here it's a restaurant, and this restaurant is located on this place, and so they have on the web page of the restaurant also an interactive map coming directly from geomapish.
And yes, the professional portal is here. So this is much more standard. This is the geomapish standard. They changed only some colors to be more EPFL-like colors. And I told you about the routing.
So they have a very powerful routing system, so they can say, okay, I want to go from my office to this restaurant, and there will be routing for pedestrians. And the editing of the graph is directly done in geomapish.
So this is a specific module that we developed for them. And what you can see here is the graph, and it's quite complex, but it works well. And finally, here's a screenshot of the demo application of geomapish.
What you can see here is the LIDAR profile. It was implemented first for the content of Neuchâtel, and now it is from the 2.7
version, it is in the heart of geomapish, and also it is one of the first components that we moved to web component technology. And I thank you for your attention.
And you have all the links here to the demo, and the second link is the website of the community, and then documentation, et cetera. Yeah, thank you.