Thank you. Thank you. Really happy to be here. This is my first time in these Kugisk user conferences, and I've already met such a nice people and this is a real pleasure for me. So

I'm a partner at this Finnish consultancy company called Gizpo. And we are usually training people how to use open source GIS software, and we're the only real open source

software firm company in Finland doing GIS work. So most of the others have hybrid solutions, but we are only open source. I'm talking about configuring in-spice gamers, which is not very probably very sexy topic, but anyhow, this has been

providing us some bread to the table for the last year, and so I would like to tell you a little bit about this use case on digital land use planning. So if somebody doesn't know where Finland is, it's on there on the top.

A little bit distorted in this projection, but there's our home country, and I'm talking about Tampere city, which is the maybe third or fourth biggest city in Finland at the moment, and how they are

using open source in their land use planning. So a little bit about the background, land use planning in Finland. We have a national spatial data infrastructure, which is now moving towards more schema-based thinking, so

INSPIRE has made us to start thinking databases and harmonization of different data. So INSPIRE requires data to be provided in INSPIRE compatible schemas.

So data models and the National Land Survey of Finland is now trying to gather information about those data sets in Finland, and also the Environmental Ministry is doing huge projects on land use planning and database modeling.

So those projects belong to this national GI platform project, where there are different themes that we have to take into consideration in Finland. One is addresses, one is the land use planning, one is topographic basic maps, or basic databases from Finland, and then there are other issues also.

So in INSPIRE directory, there are huge amount of different data schemas, but I'm talking about the plant land use schema in my presentation here.

This project actually started one and a half years ago in 2017, when the Environmental Ministry asked our company to just figure out what would be the minimum national database or database model for land use.

And we figured out after two months of work that it's the INSPIRE directory of plant land use schema. So not very big brainer, but we had also other national options and we had to go through them and check if they are doing what INSPIRE asks and so forth. But there are some national

land use issues also that we want to take into account in the land use planning database model. And the work is going on. Regarding land use planning, we have

three levels in Finland. The regional plan, which is a huge regional land use plan, and there has been done already a model how to harmonize all the regional land use plans in Finland. And the work is led by the regional authorities in Finland and the Environmental Centre of Finland. And the detailed plan,

which is the most detailed land use plan available, that is a project of the Environmental Ministry and they are looking into that. But the general plan, which is in the middle of these two levels,

nobody is like doing anything for it because for some reason. But we had a client who wanted to dig into it, Tampere city, and I'm talking about it soon. But here's just a figure. It doesn't show very well in this

hole, but you can go to inspire.europe.eu and check the data models. And this is the land use planning models. It looks quite simple, but it's not.

So, strategy general land use plan schema was our objective with the city of Tampere. They had these needs. They needed to do something for the INSPIRE schema, so we have to take the INSPIRE land use planning schema into account.

So, what to do with it? They had data, but it wasn't in INSPIRE compatible format. They wanted to combine also different kind of information to the land use parcel. So, if there's an area object, maybe like a residential area, they wanted to have all the information that you can get

or have on that land use parcel in that polygon or feature. So, for example, documents, how did they come up with that kind of a border? What kind of decisions and public participation things evolved in the process?

So, they wanted all the information to be added to that feature and all the features should have also a unique ID. So,

in the end, it would mean that the spatial feature and its information could you could get access to the past decisions. If you have a map service, you have the land use plan, you click on that on the object and you receive all the information that is added or related to that.

So, in the end also to see how the land use planning is operated or is the future goals that the land use plan has, are they reached and how they have been reached. And it would be also

created so that it would not be static and could live in digital format along the planning process. So, it will not be a paper map, so to say. It will be a digital land use plan evolving and not being static. Yeah, if somebody doesn't know what the land use plan is, here's

the Tampere City land use plan a few years ago and this was created with Gorgis and Giuseve at the time and I have to say also that Tampere City is very very active in open source field. It's a

city policy to use open source GIS software and they are open in lots of data and they have open source solutions and so this is a land use plan, but it was a few years ago it looked like this, but now we have gone a bit further

in the database model side. So, this was the beginning, highly generalized view. We have a spatial plan. It has a border. Inside there are different land use objects, zoning elements or supplementary regulation features. Then you have land use indication. What means is

what the object actually is. So, for example residential area, core agricultural area or tourism site or whatever. Then you have a document. You need a document. What is this data set? Who has produced it? Why?

Where to find it? So forth. And then you have a huge list of different codes, code lists from the INSPIRE and also the Environmental Ministry has code lists and maybe the Tampere Cities have some code lists that they want to use them on. So, this is the core of the database, the spatial plan.

But then if you want it to be strategic and looked into the future, you have to have different other issues taking into account. Tampere didn't want to store the data that is already being done or created in somewhere else. For example,

groundwater is provided by the Environmental Center. Background maps are provided maybe by the National Land Survey. Geological Survey is doing something National Museum of Antiquities is doing something. They weren't interested in those data sets because they are already there.

We don't need them in the land use plan as such, but you need them to bring some new information. So, we went through all the data sets that they need and took them into account.

Then you have background documents, processes, reports, plans, whatever, and also planning parameters, ground level. Maybe there's a tie between two parcels. If you build a supermarket, you need highways to then, if you remove the supermarket, what happens to the highways? So, these kind of ties between the land use objects.

Visualization metadata and also the follow-up. What happens in ten years? Have we reached the goals and so forth? So, this is what we came up with.

It's a PhD modeler. Model created with PhD modeler and post is now there. But after this was done in a year project and we ended up like this. We had all the elements that they needed, but of course how to use it, how to add data, because the

users of land use planners are quite regular GIS users, so they didn't know how to use this database as such. So, the database model was looking good and you can go to our GitHub and see it if you want to.

We need some GOOGIS magic. Ta-da! Of course. And we need a system. So, we have a post GIS, GOOGIS, GeoSaver providing the interfaces and then this is a national thing, Oskari map platform, which is coming in handy in the

publishing side. Yeah, without any coding, maybe. Can we do it? We used GOOGIS model breaker, which we heard a workshop, was it yesterday or one day? I don't remember anyway.

By Andreas and Matthias. It was used to call the GOOGIS project generator and I had to change my slides because now it's model baker plugin that solves everything. So, it brings the schemas to the GOOGIS project and it worked very fine for us.

And it saved my ass a couple of times. Then we tweak the necessary relations between the tables. You don't necessarily have to do this, but I wanted to check what the relations, how they acted and also

change some names and so forth. And there were quite many of those relations, so I went through them all all by myself. I'm not a coder, I'm not a developer, I'm not a database person, but I managed to do this. So, back then we configured the attribute forms to combine the necessary tables and

tabs and pull-downs menus. As you have seen in the workshop, there are cute neat tools to do this kind of forms in QGIS. Attribute forms from the layer properties, very handy.

And in the end, the users were trained to start creating your land-use planner with all the relations and all the lists and code lists and what you need to create. So everybody's happy. I have to say that the training session wasn't very successful because the first time we tried it, we didn't have an internet connection, so the database connection failed quite badly.

Less and less, always check the environment before you go training and check the internet connection, but after that everybody was happy.

So we were, like, smiling. QGIS could do this without any coding because we wanted that project to be that the users in the company could also a little bit do some work themselves or the main users there.

So we didn't want to build a plug-in for this separate use case. And usually when you build a plug-in, you have to update it and so forth. But just with a QGIS project, we could do this. But then there are some issues

we're not very happy about still, but mainly we are. So some observations to the end. QGIS Model Baker is so nice. If you have a database, just try it. It brings all the relations. But there was a small thing. It does not yet support schemas that have relations between schemas.

So we had multiple schemas in that database model, and this still didn't understand the relations between those schemas. But inside the schemas, it brought all the relations, all the lists of whatever we had. It was very good.

So the attribute form tool saved our ass. We didn't have to code that at all, and it was really, really, really good. I did all the things I wanted. But for me, for example, it took a little while to understand what it can do.

So there was a bit of a training period before everything went all right. We're virtual layers, and SQL is great, but the syntax is a bit different in QGIS. So using alias names for dataset layers, it's not always a good idea.

I've had some trouble with this. So that one of the beautiful things was that QGIS understands relations, but many-to-many relations became a bit of an issue in this case, and we had to make some loops. And I don't know if we managed to get the perfect solution. Maybe I can discuss them

here with the developers and get some ideas. Value maps and code lists are very helpful. In some cases, they didn't have all the code lists available yet, so we have to come back later with the list and contribute to the project later.

Yes, and this is the last slide. We have the Tambara general alias plan. All the layers we need, there is dot points, lines, different kind of areas.

Then there are the tables that are related to the zoning elements and all this stuff. And you can just add the information there and everything is fine. Yeah, and we are happy.

So thank you very much. Thank you for the plug-in. Are there any questions? You can come and check the workspace later if you want to.

I can show what it can do. But on my behalf, thank you. And Slavkin says thank you also.