Yes, and that was the eeox, so I'm sorry for that, so you can take your time.

Which is good because I have like 60 seconds. Of course we can finish a bit earlier than that. So let's say, okay, we all know GeoSurfer of course, and it's always good to, there's new and GeoSolutions, one of the main sponsors of this program, and the floor is yours.

Okay, so good morning everyone, I am Nuno Oliveira, I work for GeoSolutions, I'm a developer of GeoSurfer, GeoTools, GeoWebCache, and I'm doing this presentation in the place of

Andrei, which is stuck in Barcelona. So, this presentation was actually made by these three persons. If you know them, you know they like GeoSurfer very much, so this is a very big presentation, so if I'm going late, please let me know. Okay, so GeoSurfer, I guess is a pretty well-known product, so GeoSurfer implements

a several set of OGC protocols, and a lot more of extension that allows you to read several data and produce data in other several formats, okay? So this presentation will start with a small summary of GeoSurfer status, and then I will

go through all the features, so hopefully it will not be too boring. So the release schedule, this is an important part of any project. If you are in a version beyond GeoSurfer 2.12, upgrade, because otherwise you'll need several important security fixes, it's not only about the new features, it's not only

about keeping the stability, it's mainly about security fixes, that's an important topic. So, this was about the upgrade, and now, this is a bit blocked, just a second, sorry. So now we'll start with the features, so vector data source, okay?

So the new thing in the last versions of GeoSurfer is that GeoPackage become a main data store, which means when you download GeoServer, you have GeoPackage available, and everyone loves GeoPackage, it's basically SQLite database, buzzed on our new GC standards,

so it's very interportable between several systems, you can use it in WMS, WFS, and WPS. Okay, so the keyboard is not working, okay? So the GeoPackage performance improvements, there was several performance improvements in the last months, basically making fast, I mean, every time we contribute a new data

store, it's not in a perfect final state, so the performance will upgrade over time, so it's not yet close to shapefile, which is a very old perform that got a lot of work on it, but I mean, it's progressing. Okay, then we have MongoDB. So MongoDB become an extension in the last two months.

One nice thing about MongoDB is that you can use it now, so we tap up a schema to serve complex features, which means that if you are working in Inspire, this may be something interesting for you, okay? Now we have the new support for some specific post-crazy scale data types, we have the

array support, which has been implemented right now, and we are also working on the support for the M-ordinates, okay? So raster data source, okay, so one of the recent improvements was the ability to use, let's say, several raster for different coordinate system and let your server handling

all the business of merging all of these together. In my opinion, this is one of the best features for raster, is the ability right now to create a view over several raster files, so pretty similar to a SQL view, so basically you can say, use the band from that raster file, use this band from this

raster file, they may be in different coordinate systems, everything will work just fine, and of course, behind the scenes, there is performance improvements, you just read the bands we need, et cetera, et cetera. There is also a new community module if you want to store your Jotif files in the Amazon S3, which may be interesting for certain use cases.

Now, getting to the web map service, so okay, this was an improvement on the time dimension, so if you have raster file, typically this is for raster files, of course, you can also use vector data. If you have a time dimension, now you can say to use as the default value, let's say

the nearest match, the real value will be returning back to the client in a specific HTTP header, so it takes advantage of the HTTP stack and so on. This is a new vendor parameter that was implemented in WMS and in WSCS2, if I'm not wrong, basically allow us to sort by a specific attribute.

If you have already used WMS from your server, you know you have another vendor parameter, which is the SQL filter parameter, which allows you to filter your data based on the OGC filters, so now you can also sort your data by a specific attribute. The typical use case, you have several raster files, you'd want the most recent one

with the less cloudy ones. Okay, this is for labels, I mean, labels is something that is always being proven. You can always do better, so there was a recent improvement to make the label position to be a better position on the map. Well, there is not much to say about it, so now you can basically say where you want

your label and your server will try to put in a nice position inside the polygon. Okay, getting to the web feature service, the source of vector data, and XML and JML issues too, sometimes, so we have been working on WFS 2.0 certified compliance with OGC.

We fixed several issues, mainly related with exception codes, with capabilities, missing elements, and so on, and we are almost there, but right now this is not the priority, okay, but we are working on it on the, let's say the community

is working on it, we have the App APS scheme improvements, probably not sure how many people know about this, App APS scheme is what allows you to build complex features in your server, so you have an output JML schema, you have all that on a database, and you want to output JML vector data that match that specific schema.

So there was several improvements, the usage of MongoDB, we are now using Pash Solar as a data store, you can use an external index, that's something that is being implemented right now, to speed up your queries, for example, if you have a text search basket query, you can say to your server, hey, if you have a filter that needs to do a full text search on this attribute,

please get the data you need from the relational database, but make sure you speed up the query by also looking at the solar index. Okay, the web coverage service, so as I say, okay, the SQL filter and sort by vendor parameters, they were ported to the WCS service,

which means that it's now fully compatible, let's say it's actually similar to WMS now, you can do the same stuff with those two parameters. There was some specific improvements on the NetCDF input-output format that you can configure through the UI to get the data in a way you need

for some specific use case, honestly, I have no idea what this is, no idea, you will have to ask Andrea tomorrow, sorry. So you have the tiles, okay, so you have the WMTS service, which is the best service, sorry, I mean, in GeoServer is the, let's say,

the best service you have right now to serve tiles, which means that now you can also do cascading, like you can do for WMS, so GeoServer will not be a simple routing system, a proxy system, you'll actually act like a client, which means that you'll be able to take advantage of GeoServer features

when querying a layer that was cascaded by GeoServer to another WMTS. The person who did this in the room is Jan, so you can ask him questions, I guess, afterwards. Another improvement that was done on JWebCache was the parameter filter, so if you have used JWebCache, I mean,

you know, when you have to store the tiles, you have to have a look at the request to infer a specific key to identify to which request corresponds each tile, there was some issues in deciding how to delete these tiles, how to carry these tiles, so there was several improvements around that. And of course, REST API of JWebCache was improvement, was also improvement,

allowing you to take advantage of some of those improvements, so. That's for JWebCache, so you have the styling now, your cartographic table, sometimes, so labeling improvements, so yeah, basically, there was some formatting options that were added to SLD,

like kerning, underline, strikethrough, you can use them and use all the usual options, like all around the text, the size of the text, the color, and so on. This is a vendor option, okay, and the SLD is not part of the SLD specification.

Another improvement was, again, regarding displacements, so now you can give an int to just server, okay, when you do your algorithm to decide where to position the labeling, you can actually, I don't know, go to the west, go to the north, something like that. SVGs, this is a nice improvement, so basically it allows you, it allow us, on the just server SLD, to decide how to,

how the SVG will be renderized, the stroke of the SVG, the feeling of the SVG, so this is a nice feature if you are using SVG, basically you don't need to have multiple SVG files anymore, for example, if you have the same symbol with different colors, you can have a single file, and then on the SLD decide which color,

the size of the stroke, and so on, that will be used to do the rendering. Okay, so this is a Mapbox style community module, so basically it allows you to use Mapbox styles. I'll be honest, I don't know much about it. CSS improvements, okay, this is something Andrea likes very much.

So it's always improving it on its part time. So basically the recent improvements was to allow us, when you have a huge unit to define instead of writing three trillions of zero, you can use unities, and there is also the usage of certain variables,

basically make the CSV file more readable. Okay, so this is another nice thing you can do with raster file, is the ability, let's say, when you use SLD in GeoServer, you can use OGC functions, okay, to make your style more dynamic. One of the things you can do is, for example, using the env variable, which is something that you can add to the request,

used to invoke, for example, GeoServer demo FS service, and then you can use those attributes to make your SLD more dynamic. Now, you can use this with the dynamic channel selection to basically select at run time which bands from your raster should be reader and use it to do the rendering.

Basically this will allow you to have like ten different styles to use different bands. You can do a single style, and then you can select the bands at run time. Okay, the web processing service. So basically what we used to do,

we used usually this service to do everything we cannot do with the other ones. So this is another nice feature, is the GFL algebra. So it basically allows you to use, in SLD, as a rendering transformation to do raster algebra with this language.

So for example, in this case, you get several raster files as input, and here you use this GFL script where basically you say, okay, I need to take the band number weight, the number number four from this raster, and I need to combine them using this formula to produce this raster file. And you can do all of this directly in the SLD.

Now, if you take into account the other improvements I've talked about, like the dynamic channel selection and so on, it means that you can really have fully dynamic styles. So behind the scenes, this is also very profound because your server will be smart enough to only read the channels you need to read and so on.

So it's quite an extensive work. WPS Donald. So WPS is something that is always also improving. So the last improvement on it was to allow us to download large raster files, large raster data in an asynchronous way and so on,

which is something you cannot do with WFS, for example. Then we have the CSV input and output for WPS, which means that right now you can share an input data stored and an output data stored that use CSV format. Okay, now moving to configuration and management.

So you have the user interface. Okay, there was several optimizations that were done in the interface to allow for auto computation. This was also done for SLD, if I'm not mistaken. So basically now when you type stuff on your server interface, it will suggest you an auto complete, which is a very nice thing.

Raster parameters, so these are basically more options for the coverage parameters. Sorry, for coverage raster files configuration for rendering. We have also the full screen style editor. If you have already edited a style on your server web UI, you know how bad it is sometimes because it was very small,

the files could be very big. So now you have an option to use all the screen and it will make your life easier. Okay, so again, improvements on SLD. To help us basically select the stuff you need, you want to see on the SLD map. This one is to pick the image when you have a mark

that you want to use on the SLD. Instead of having to copy paste the part from the file system, you can directly select it on the SLD. Okay, you have another improvement, the color picker, which is quite useful. Okay, and then I'm not very, I don't know much about this,

but we are also working on the QG Striezer style export compatibility with your server. Feel free to ask questions to Andrea tomorrow. So, isolated workspaces. Okay, so this is a very strange thing. So basically, if you are using your server, this is for App API schema for complex features.

So if you are working on Inspire, this is interesting for you. Otherwise, you will not use this. So basically, if you need to publish complex features, this will allow you to publish the same complex features multiple times. There is some new limitations, we are working on it, but that's what use it for. So if you are using complex features, working on Inspire,

you can ask me more detailed questions afterwards. G2DBC config, G2DBC store, so using the two server catalog on a database, there is some issue with this model, but we are working on it, mainly on the performance side. So we have the open search for Earth observation.

This was a community module that will basically make the life easier for those who need to search this data. There is nothing much to say about this. And that's all about the features. It was actually quicker than what I expected.

So as usual, if you have any doubt, feel free to ping the mailing list. This is another important, because we have a few of them lately. If you ever find a security issue on your server or related projects, don't public post it on the mailing list. Make sure you contact the steering committee

or a specific developer that you know is in the steering committee. The key point is don't make it public, okay? Every last Friday of the month, we have a bank stamp where you basically go through the most recent just server issues and we try to fix them.

So if you have to report the issue to just server, make sure you make a clear way to reproduce it, because basically what happens is that we'll go to the JIRA issues and the ones that look very easy to reproduce and that look very important, there is a big probability that they will be fixed during the bank stamp. And that's all I have to say.

That's all. Thank you very much. And then the last scheduled change of us. I forgot to introduce you. The speaker is Nuno Oliveira from GeoSolutions.

And he will be able to answer some questions, and also questions later on Guimaraes. Yeah. So just in your bio you studied here. So, but first, yeah. Are there any questions on GeoNetwork or what was just presented?

Okay, there is one from Jan. Mr. Turton, yes.

Yes, that was a nice comment, indeed. That's good. So if you have issues with QGs and SLD from GeoServer Export,

VH GeoServer community. I mean, everything was very clear, apparently. Everything was very clear, apparently. I don't know. So don't be shy. This is your moment to ask questions.

Yes. That was the improvement. Now you can use multiple raster.

And they can actually be in different coordinate systems. So let me try to find it. I'm sorry, I don't know this presentation very well, so I need to look for it. Okay, yeah. So basically the idea is that you can have multiple raster files, and then you can create a coverage view, like you'll do with an SQL view.

So you can have different, in SQL you'll have different tables. Here you'll have different raster files, okay? And you just basically say, I want to use this band from this raster file. I want to use this band from the other raster file. And GeoServer will take care of merging everything, reprojecting the data, and so on. Did I answer your question?

Okay, cool. We still have time for one more question.

I know they were working on it, but right now you can't. You can only use GeoTiff.

But I think they are working, actually let me check the slide. I'm pretty sure they were working on to improve me to also support Imagic, Mosaic, and so on. But it will be better if you can ask this question afterwards to Andrea. I'm not aware of that, fully aware of that, the status of that project.

Okay, so, yes, the third speaker is supposed to... So thank you again very much. Great applause. The third speaker who is supposed to be here

was Joakim Ungar, but I think like Andrea, they're both stuck in Barcelona, so I have all the time to implement new features to GeoServer and Eox, but possibly he will be showing up later and maybe possibly use a holding schedule later this week,

because I think that's a very interesting presentation as well about role raster data in the browser, GeoTiff in the browser, styling, I think. So we were, when we started, we were ten minutes behind schedule, and now we are about 13 minutes in front of the schedule.

So we'll close off this session. We'll go to lunch somewhat earlier then, and we'll see you all this afternoon at the next sessions. Thank you very much.