WEBVTT 00:00.000 --> 00:05.000 Thank you. 00:05.000 --> 00:10.000 So good afternoon everyone. 00:10.000 --> 00:12.000 Thank you for attending. 00:12.000 --> 00:13.000 Thank you for being here. 00:13.000 --> 00:15.000 I'm very happy to be with you this afternoon. 00:15.000 --> 00:16.000 I'm from Swadakum. 00:16.000 --> 00:21.000 I've been contributing for open street maps since maybe 15 years. 00:21.000 --> 00:25.000 And I will give you some updates about put a mess of 00:25.000 --> 00:30.000 new methodology we try to install in France to monitor some 00:30.000 --> 00:35.000 topics of contribution in the project. 00:35.000 --> 00:39.000 What I propose you today is to give you the global explanation about 00:39.000 --> 00:42.000 the put a mess of 12 what it's used for for our 00:42.000 --> 00:45.000 with runs and give you demonstration live demonstration for 00:45.000 --> 00:48.000 a particular topic I chosen here in Belgium. 00:48.000 --> 00:50.000 So we will have both parts, 00:51.000 --> 00:54.000 very and practice in this presentation. 00:54.000 --> 00:59.000 And finally we will see for the development perspective we can 00:59.000 --> 01:02.000 bring it up together. 01:02.000 --> 01:06.000 A few reminder of our about open street map is working. 01:06.000 --> 01:10.000 Some of you may already know that for maybe very long time, 01:10.000 --> 01:12.000 but it's useful to understand the presentation. 01:12.000 --> 01:17.000 Open street map has a very basic data model that has been fixed 01:17.000 --> 01:19.000 for many years. 01:19.000 --> 01:22.000 And the most important part is tax. 01:22.000 --> 01:25.000 We are getting a very basic set of features points, 01:25.000 --> 01:28.000 lines, relations and we put tax on them to make a difference 01:28.000 --> 01:31.000 between a tree and a building and an highway. 01:31.000 --> 01:33.000 That's our open street map works. 01:33.000 --> 01:36.000 The tagging is evolving significantly thanks to the 01:36.000 --> 01:39.000 contribution of the community itself because it's a 01:39.000 --> 01:42.000 self-built ontology. 01:42.000 --> 01:46.000 That's all you have to know if we look at this 01:46.000 --> 01:50.000 background map you may have seen. 01:50.000 --> 01:51.000 It's very basic. 01:51.000 --> 01:55.000 It's very neat background that if we look inside, 01:55.000 --> 01:57.000 we will see many tax. 01:57.000 --> 02:01.000 Tax are everywhere on every feature that compose the database 02:01.000 --> 02:04.000 and allow to produce this kind of map. 02:04.000 --> 02:09.000 And right now since open street map is more than 20 years old, 02:09.000 --> 02:13.000 the point is not about not only about completeness. 02:13.000 --> 02:17.000 It's also about maintenance and change management. 02:17.000 --> 02:21.000 We need more and more tooling, more advanced tooling, 02:21.000 --> 02:27.000 to manage those tax to not only the spread of the project 02:27.000 --> 02:30.000 but also the change in the ontology. 02:30.000 --> 02:31.000 So we have to monitor that. 02:31.000 --> 02:35.000 We have to monitor the contribution and get a very 02:35.000 --> 02:38.000 detailed insights about this contribution. 02:38.000 --> 02:41.000 No matter how many tax you have, 02:41.000 --> 02:45.000 you need the tool to observe what contributors are doing in the database. 02:45.000 --> 02:51.000 And currently, we don't have the necessary tooling I will present you today. 02:51.000 --> 02:54.000 Let's get into this kind of chart. 02:54.000 --> 02:56.000 I illustrate this. 02:56.000 --> 03:01.000 It's the change log of the project to manage in your country, 03:01.000 --> 03:04.000 in your community, in your continent, even worldwide. 03:04.000 --> 03:08.000 You have a filter that is created in the database that appeared 03:08.000 --> 03:11.000 that disappear, you have tax, you remove them. 03:11.000 --> 03:16.000 And a long time, you will have those features appearing 03:16.000 --> 03:18.000 and disappearing from your project. 03:18.000 --> 03:21.000 You can change a tree in a building or a hydrant or whatever 03:21.000 --> 03:26.000 and you have to monitor if the objects are showing up or not. 03:26.000 --> 03:29.000 And that's what we do in Podama. 03:29.000 --> 03:31.000 We build this change log. 03:31.000 --> 03:37.000 We build in two dates, and we count at fixed dates. 03:37.000 --> 03:41.000 To get the exact amount of features corresponding to given 03:41.000 --> 03:45.000 filter in a global perimeter. 03:45.000 --> 03:49.000 So we are mostly interested in green features, 03:49.000 --> 03:51.000 because grey don't attach. 03:51.000 --> 03:54.000 Yellow have any tax you want and the green have the 03:54.000 --> 03:56.000 tax corresponding to the filtering may set. 03:56.000 --> 04:00.000 So the main goal of Podama is to maintain this change log 04:00.000 --> 04:02.000 and build KPI. 04:02.000 --> 04:05.000 And provide many more functionalities as well. 04:05.000 --> 04:09.000 In OpenStreet map, we have ways to get statistics. 04:09.000 --> 04:12.000 It's not a very recent topic. 04:12.000 --> 04:15.000 We have many tools to get statistics out of the project. 04:15.000 --> 04:18.000 I and I, three of them that you have many more. 04:18.000 --> 04:21.000 The OSM start by Pascal Nisto instance. 04:21.000 --> 04:26.000 Awesome dashboard and tag info, which has three very popular tool 04:26.000 --> 04:30.000 to get statistics about how the features are set and 04:30.000 --> 04:31.000 remove from the database. 04:31.000 --> 04:35.000 But we miss a topic for QS platform that is able to 04:35.000 --> 04:39.000 undo the contribution both worldwide and locally on a 04:39.000 --> 04:40.000 given filter. 04:40.000 --> 04:44.000 Without maintaining the wall database on your own server. 04:44.000 --> 04:46.000 And that's a big point. 04:46.000 --> 04:49.000 I was working on a project last year that improved a lot 04:49.000 --> 04:50.000 Podama. 04:50.000 --> 04:54.000 And we add to monitor the poor grid mapping worldwide. 04:54.000 --> 04:57.000 And that's a very big topic. 04:57.000 --> 05:00.000 But it's not so big regarding the global amount of data. 05:00.000 --> 05:04.000 So we don't want to maintain the global database in the 05:04.000 --> 05:05.000 server. 05:05.000 --> 05:07.000 We only want to focus on the feature. 05:07.000 --> 05:08.000 And here it was the poor feature. 05:08.000 --> 05:10.000 But it can be any feature you want. 05:10.000 --> 05:13.000 And we miss that tool. 05:13.000 --> 05:16.000 So the timeline of Podama first of all. 05:16.000 --> 05:20.000 It was created in 2020 in France when a few of my 05:20.000 --> 05:24.000 fellow contributors in France were struggling at 05:24.000 --> 05:26.000 organizing project of the month. 05:26.000 --> 05:31.000 And project of the month is held as I said in one 05:31.000 --> 05:34.000 month on a given topic. 05:34.000 --> 05:37.000 And we were computing statistics by hand. 05:37.000 --> 05:39.000 Every day we are counting features that 05:39.000 --> 05:42.000 contributor may have set on the selected topic. 05:42.000 --> 05:44.000 And it was a hassle. 05:44.000 --> 05:48.000 So we build a tool called project more in France. 05:48.000 --> 05:50.000 And it started like that. 05:50.000 --> 05:52.000 We extended it with the N.A.D. 05:52.000 --> 05:56.000 Collaboration which is a very big company in France that is 05:56.000 --> 05:58.000 interested to get a few features from open 05:58.000 --> 05:59.000 straight map. 05:59.000 --> 06:01.000 So it slowly improved. 06:01.000 --> 06:03.000 And last year with the map you're 06:03.000 --> 06:07.000 really initiative that allow to build things and 06:07.000 --> 06:10.000 make them a very helpful worldwide scale. 06:10.000 --> 06:14.000 So it's still to be continued because the 06:14.000 --> 06:17.000 functionalities are not over with that story. 06:17.000 --> 06:20.000 And we still seek for support and 06:20.000 --> 06:23.000 contribution that project will prove the functionality. 06:23.000 --> 06:25.000 First of all, Podama is maintaining the 06:25.000 --> 06:27.000 change log of the features corresponding to the 06:27.000 --> 06:28.000 filter. 06:28.000 --> 06:31.000 After that, because of the existing 06:31.000 --> 06:34.000 tool I mentioned as meon because it's the underlying 06:34.000 --> 06:37.000 software that allow to filter the data out of 06:37.000 --> 06:40.000 the open straight map archives. 06:40.000 --> 06:42.000 And the filtering functionality of a 06:42.000 --> 06:46.000 small is very simple for good reasons. 06:46.000 --> 06:49.000 And we extend those functionality with 06:49.000 --> 06:53.000 labelling features inside Podama to get a few 06:53.000 --> 06:58.000 groups of objects out of a more broad filter. 06:58.000 --> 07:01.000 After that, we come them and we assign the 07:01.000 --> 07:04.000 features to some graphic boundaries and 07:04.000 --> 07:05.000 teams. 07:05.000 --> 07:08.000 We can build teams out of using names. 07:08.000 --> 07:10.000 So you can in your project define a few 07:10.000 --> 07:13.000 teams to observe how they are contributing and 07:13.000 --> 07:14.000 how they are doing. 07:14.000 --> 07:17.000 And we can see that we are going to see 07:17.000 --> 07:20.000 the results in the same 07:20.000 --> 07:23.000 time competing as well on the top picture selected. 07:23.000 --> 07:26.000 That's the basic feature. 07:26.000 --> 07:29.000 That's how things work. 07:29.000 --> 07:31.000 We process and you will see an action. 07:31.000 --> 07:34.000 Right after we process all those step and get the 07:34.000 --> 07:36.000 map you see on the right. 07:36.000 --> 07:39.000 And that's exactly what we need. 07:39.000 --> 07:42.000 Thanks to map your grid, we can observe several 07:42.000 --> 07:43.000 of the map. 07:43.000 --> 07:46.000 The main functionality of the web interface is 07:46.000 --> 07:47.000 dashboarding. 07:47.000 --> 07:51.000 You get all necessary insights from the project in 07:51.000 --> 07:53.000 different views like the Podium. 07:53.000 --> 07:56.000 Regarding the users, you are observing the map. 07:56.000 --> 07:59.000 Regarding the different boundary you are considering 07:59.000 --> 08:01.000 and the evolution of the features. 08:01.000 --> 08:05.000 Not only the existing features in green, but also 08:05.000 --> 08:08.000 the two integrated features got from or 08:08.000 --> 08:09.000 smalls for instance. 08:09.000 --> 08:12.000 Because Podium is not doing quality insurance. 08:12.000 --> 08:15.000 It's not comparing with open data, external data 08:15.000 --> 08:16.000 source. 08:16.000 --> 08:19.000 It's only observed what's happening in open 08:19.000 --> 08:22.000 street map and can take real value from 08:22.000 --> 08:26.000 smalls and gathering corresponding issues you can 08:26.000 --> 08:29.000 address on existing object as well. 08:29.000 --> 08:33.000 You also got an API that they were some basic 08:33.000 --> 08:36.000 information about the process KPI on every date 08:36.000 --> 08:39.000 process, the amount, the length on 08:39.000 --> 08:42.000 ways as well, the area. 08:42.000 --> 08:45.000 Also, you get very basic information about what's 08:45.000 --> 08:47.000 going on in open street map and you can observe the 08:47.000 --> 08:49.000 evolution of those KPI. 08:49.000 --> 08:53.000 We also got a web editor because back in days 08:53.000 --> 08:55.000 during the project of the maps in France, 08:55.000 --> 08:58.000 we are also interested to enable users to 08:58.000 --> 09:01.000 contribute, then to provide them a view of what 09:01.000 --> 09:02.000 exists. 09:02.000 --> 09:04.000 So where they are not forced to contribute and what 09:04.000 --> 09:06.000 should be integrated is the difference between 09:06.000 --> 09:08.000 the green and the red dots. 09:08.000 --> 09:12.000 But also you can see on the left, we have a 09:12.000 --> 09:16.000 very contextualized editor with precise set of 09:16.000 --> 09:18.000 fields you can contribute. 09:18.000 --> 09:20.000 It's a very pretty customized and it 09:20.000 --> 09:23.000 adapts to the project you are managing. 09:23.000 --> 09:26.000 Finally, the gamification as well, we provide 09:26.000 --> 09:30.000 the Podium of the users, we give points, 09:30.000 --> 09:32.000 depending on the action done on the database. 09:32.000 --> 09:34.000 So if you add an object, you get some points, 09:34.000 --> 09:36.000 if you add it one, depending on the field you 09:36.000 --> 09:39.000 add it, you can get another point and so on. 09:39.000 --> 09:43.000 And finally, you get this kind of thing. 09:43.000 --> 09:45.000 It's the very beginning of gamification, 09:45.000 --> 09:48.000 Podium, I didn't pretend to have a very 09:48.000 --> 09:51.000 broad set of functionalities, but it's a platform 09:51.000 --> 09:54.000 that allows to deploy it more deeply if you 09:54.000 --> 09:57.000 want in your community. 09:57.000 --> 10:01.000 If the web interface doesn't satisfy your need, 10:02.000 --> 10:05.000 it's completely possible because it's a generic web interface. 10:05.000 --> 10:08.000 The API allows to deploy such kind of dashboard 10:08.000 --> 10:10.000 you can build on your own, 10:10.000 --> 10:12.000 regarding the project you are managing. 10:12.000 --> 10:15.000 So thanks to the API of the dashboard we deploy 10:15.000 --> 10:17.000 in the map you're reading initiative. 10:17.000 --> 10:19.000 So full customized dashboard, 10:19.000 --> 10:21.000 consuming API, getting insights, 10:21.000 --> 10:23.000 the point is not to understand what's displayed, 10:23.000 --> 10:26.000 but it's only intended to show that there's 10:26.000 --> 10:29.000 difference between this and this. 10:29.000 --> 10:32.000 And that's why it's important to not only have the web 10:32.000 --> 10:36.000 interface, but also the API to deploy such 10:36.000 --> 10:42.000 very customized dashboards. 10:42.000 --> 10:47.000 I propose we try this in Belgium this afternoon. 10:47.000 --> 10:50.000 I selected a few atopic. 10:50.000 --> 10:53.000 I was interested in, but you may have a hint 10:53.000 --> 10:54.000 under the right of the screen, 10:54.000 --> 10:57.000 make some of you guess what we are going to count, 10:57.000 --> 10:59.000 maybe if you know this example, 10:59.000 --> 11:02.000 do we have any ID? 11:02.000 --> 11:05.000 No, it's not pencils. 11:05.000 --> 11:08.000 Firstly, now it's benches. 11:08.000 --> 11:12.000 Let's give you the try on public benches in Belgium. 11:12.000 --> 11:17.000 That's a broad enough feature to get the real perspective 11:17.000 --> 11:20.000 of our customized working, but also a limited enough 11:20.000 --> 11:24.000 to not take any time and a long time to wait for results. 11:24.000 --> 11:27.000 So I have recorded the process. 11:27.000 --> 11:30.000 It lasts approximately 11 minutes. 11:30.000 --> 11:35.000 I shot it the most long faces to not let you wait so much. 11:35.000 --> 11:38.000 The video will last for four minutes to give you the 11:38.000 --> 11:42.000 world process and show how it achieve the processing. 11:42.000 --> 11:44.000 But first of all, let's have a look to the very 11:44.000 --> 11:46.000 basic set of configuration. 11:46.000 --> 11:47.000 It may look complicated. 11:47.000 --> 11:49.000 I wanted to detail all parameters, 11:49.000 --> 11:52.000 but understand it well. 11:52.000 --> 11:56.000 But it's a very neat configuration 11:56.000 --> 11:59.000 regarding the functionality and the advantage for the 11:59.000 --> 12:00.000 my brains. 12:00.000 --> 12:04.000 It takes me approximately one hour to get it worked 12:04.000 --> 12:08.000 from the Git clone to the results I got from the process 12:08.000 --> 12:10.000 for this topic. 12:10.000 --> 12:11.000 So it's very simple. 12:11.000 --> 12:14.000 It's intended to be very simple and let you deploy it on your 12:14.000 --> 12:18.000 own and not bother you with so much parameters. 12:18.000 --> 12:20.000 The most important are the red ones. 12:20.000 --> 12:22.000 The most of all you should type all of your platform. 12:22.000 --> 12:24.000 You just call it very basically put them at first 12:24.000 --> 12:26.000 them, very original. 12:26.000 --> 12:30.000 But you also set secrets for open street map users 12:30.000 --> 12:32.000 because the web editor will push data to open street map and 12:32.000 --> 12:34.000 we'll need an account. 12:34.000 --> 12:37.000 And also you have to indicate the URL to 12:37.000 --> 12:39.000 what the open street map archive files. 12:39.000 --> 12:43.000 The big files where all the open street map data is provided. 12:43.000 --> 12:47.000 I selected a file for custom Belgium. 12:47.000 --> 12:50.000 Obviously I didn't download the worldwide file. 12:50.000 --> 12:55.000 I got it from Geofabric servers and I focused on Belgium. 12:55.000 --> 12:59.000 I also set the polygon URL for Belgium. 12:59.000 --> 13:02.000 The extend and the B-box. 13:02.000 --> 13:07.000 And also a title for the URL for titles for the web editor. 13:07.000 --> 13:09.000 But these are very basic set of feature actually. 13:09.000 --> 13:13.000 If you have the docs, you are perfectly able to set it on your 13:13.000 --> 13:14.000 own. 13:14.000 --> 13:20.000 Once we set up the instance, we will define the project. 13:20.000 --> 13:23.000 Obviously it's still configuration files. 13:23.000 --> 13:25.000 Tomorrow it can be done in the interface directly. 13:25.000 --> 13:30.000 If we spend the right time on improving the interface to 13:30.000 --> 13:33.000 let users define all those parameters on that one. 13:33.000 --> 13:35.000 It will be even easier. 13:35.000 --> 13:38.000 So for this project I give you a name. 13:38.000 --> 13:39.000 It's benches. 13:39.000 --> 13:47.000 I added the first of January in 2020 and it ends in 2025. 13:47.000 --> 13:50.000 It's a soft, soft end. 13:50.000 --> 13:54.000 So it will continue to count endlessly until now. 13:54.000 --> 13:56.000 I give it a filter. 13:56.000 --> 13:57.000 So the filter is here. 13:57.000 --> 14:00.000 It's the most important part of the configuration. 14:00.000 --> 14:04.000 I will select the nodes but also the ways that correspond to the bench. 14:04.000 --> 14:08.000 So in a pencil it's a mini-t equals bench that corresponds to those 14:08.000 --> 14:09.000 benchings. 14:09.000 --> 14:12.000 We have many more attributes that we will be catching up with those 14:12.000 --> 14:17.000 features, the seeds, the anything, the color, the material, whatever 14:17.000 --> 14:19.000 it we came with with this. 14:19.000 --> 14:23.000 And I also provide higher views with that. 14:23.000 --> 14:29.000 Here for funders, higher views that will help people to map 14:29.000 --> 14:32.000 the missing bench they may find. 14:32.000 --> 14:33.000 And that's all. 14:33.000 --> 14:35.000 The last parameter I enable the counts. 14:35.000 --> 14:38.000 What I want is it select the benches and come them 14:38.000 --> 14:42.000 a long time and give us the insights about our contribution 14:42.000 --> 14:47.000 going in a global way and we'll contribute it to. 14:47.000 --> 14:48.000 Let's put it all in Docker. 14:48.000 --> 14:50.000 It's not mandatory but we provide as well 14:50.000 --> 14:52.000 Docker functionality. 14:52.000 --> 14:55.000 We process them and I will launch the video to show you how it's going 14:55.000 --> 14:57.000 and explain all the steps. 15:03.000 --> 15:06.000 I hope it's okay. 15:06.000 --> 15:09.000 So it runs in several steps. 15:09.000 --> 15:11.000 So the first step is downloading the data. 15:11.000 --> 15:12.000 The project is installing. 15:12.000 --> 15:14.000 So it takes the JSON file. 15:14.000 --> 15:15.000 Putting the database. 15:15.000 --> 15:17.000 We'll recall the database to stay okay. 15:17.000 --> 15:18.000 I have a project. 15:18.000 --> 15:22.000 And then we check if it knows locally the archive file. 15:22.000 --> 15:23.000 It doesn't know it. 15:23.000 --> 15:26.000 So it will download directly from geofabric. 15:26.000 --> 15:28.000 The number is going. 15:28.000 --> 15:31.000 Belgium is only 1.3 gigs. 15:31.000 --> 15:34.000 And you get the wall is three of a panstreet mapping. 15:34.000 --> 15:35.000 1.3 gigs. 15:35.000 --> 15:38.000 Worldwide is 350 gigs maybe. 15:38.000 --> 15:42.000 So the Belgium was appropriate for this demonstration. 15:42.000 --> 15:45.000 Once downloaded, it just checked the dates 15:45.000 --> 15:48.000 because those files are generated a few times a month. 15:48.000 --> 15:49.000 So we will get a date. 15:49.000 --> 15:50.000 It's not today. 15:50.000 --> 15:52.000 It's a few years ago. 15:52.000 --> 15:53.000 A few days ago. 15:53.000 --> 15:56.000 And it will pay the way for the next step. 15:56.000 --> 15:59.000 So it's 12th of January. 15:59.000 --> 16:01.000 Once we got the file and it's date, 16:01.000 --> 16:04.000 we will extract the history in the time frame selected. 16:04.000 --> 16:07.000 You remember we start from 1st of January, 16:07.000 --> 16:09.000 20 to 24 to now. 16:09.000 --> 16:12.000 So we will just extract the wall is three of a panstreet mapping. 16:12.000 --> 16:16.000 This time frame to reduce the amount of process to be done. 16:16.000 --> 16:21.000 And once it's done, it takes, let's say, 50 seconds. 16:21.000 --> 16:24.000 Once it's done, it will get into details regarding the filter. 16:25.000 --> 16:28.000 We selected so benches. 16:28.000 --> 16:31.000 Just afterwards a few seconds. 16:31.000 --> 16:33.000 Yeah. 16:33.000 --> 16:37.000 And the most important part is we reduce slowly the perimeter 16:37.000 --> 16:40.000 to get the most efficient process as possible. 16:40.000 --> 16:42.000 Because worldwide, it's a lot of data. 16:42.000 --> 16:46.000 And you want to save some hours of processing by doing so. 16:46.000 --> 16:47.000 And that's why. 16:47.000 --> 16:50.000 So over, it extract features regarding the filter 16:50.000 --> 16:51.000 we selected. 16:51.000 --> 16:55.000 So right now it's selecting benches in the time frame we selected. 16:55.000 --> 16:59.000 And it also select all the related features for instance 16:59.000 --> 17:01.000 when you have benches defined as ways. 17:01.000 --> 17:05.000 It will also select the nodes as to rebuild the geometry. 17:05.000 --> 17:06.000 It's very important. 17:06.000 --> 17:07.000 It's a detail. 17:07.000 --> 17:10.000 But it's very important if you want to get the length of benches. 17:10.000 --> 17:12.000 We have to get the related feature as well. 17:12.000 --> 17:13.000 And put them. 17:13.000 --> 17:15.000 I will do it for you. 17:15.000 --> 17:17.000 Then it reports in the database. 17:17.000 --> 17:18.000 It's a detail. 17:18.000 --> 17:19.000 All the steps. 17:19.000 --> 17:21.000 But it's important that I basically rebuild the geometry. 17:21.000 --> 17:23.000 It assigns on boundaries. 17:23.000 --> 17:25.000 I preloaded the boundary. 17:25.000 --> 17:27.000 I made administrative boundaries of Belgium. 17:27.000 --> 17:28.000 The country. 17:28.000 --> 17:29.000 But also the region. 17:29.000 --> 17:30.000 And so on. 17:30.000 --> 17:31.000 Once done. 17:31.000 --> 17:35.000 You know, it does until the 12th of January. 17:35.000 --> 17:38.000 We have to catch up with the present time. 17:38.000 --> 17:40.000 Because the file stops at the date in the past. 17:40.000 --> 17:42.000 We're so together. 17:42.000 --> 17:43.000 Under this. 17:43.000 --> 17:46.000 The daily diff of our open street map. 17:46.000 --> 17:47.000 Every day. 17:47.000 --> 17:48.000 Worldwide. 17:48.000 --> 17:52.000 And we have to combine them. 17:52.000 --> 17:53.000 Filter again. 17:53.000 --> 17:54.000 The diff. 17:54.000 --> 17:55.000 Regarding. 17:55.000 --> 17:56.000 Not only the Belgium. 17:56.000 --> 17:57.000 But also the benches. 17:57.000 --> 17:59.000 We only want to get the diff. 17:59.000 --> 18:01.000 For the Belgian benches. 18:01.000 --> 18:04.000 And we don't update the open street map archive. 18:04.000 --> 18:07.000 The usual practices to update the open street map archive. 18:07.000 --> 18:08.000 We don't update it. 18:08.000 --> 18:10.000 We filter the diff directly. 18:10.000 --> 18:11.000 And we apply under the database. 18:12.000 --> 18:15.000 So that's why it's called catch up. 18:15.000 --> 18:19.000 We already had important the benches until the 12th of January. 18:19.000 --> 18:24.000 We are now importing the diffs between the 12th of January and now. 18:24.000 --> 18:26.000 So we currently extract in the polygon. 18:26.000 --> 18:27.000 This type is pretty long. 18:27.000 --> 18:28.000 That's why I shouldn't it. 18:28.000 --> 18:31.000 A bit for sake of the presentation. 18:31.000 --> 18:35.000 But it lasts two or three minutes. 18:35.000 --> 18:37.000 We are doing the same way. 18:37.000 --> 18:38.000 Like before. 18:38.000 --> 18:39.000 We are filtering the diff. 18:39.000 --> 18:41.000 We are importing the database. 18:41.000 --> 18:43.000 And at the end of this step we will have that database. 18:43.000 --> 18:46.000 We will all the changes regarding the benches. 18:46.000 --> 18:47.000 Two years ago. 18:47.000 --> 18:49.000 And we are about to count them. 18:49.000 --> 18:51.000 That's the second step. 18:51.000 --> 18:53.000 For no it didn't count anything. 18:53.000 --> 18:55.000 Right now we are going to count. 18:55.000 --> 18:57.000 And we will see how fast it goes. 18:57.000 --> 19:00.000 And why we are doing so much thing. 19:00.000 --> 19:02.000 And process before that. 19:02.000 --> 19:05.000 Because the counting is pretty immediate. 19:06.000 --> 19:10.000 And I don't remember exactly how much we have benches in Belgium. 19:10.000 --> 19:12.000 But it's several thousand. 19:12.000 --> 19:13.000 Doesn't have thousand. 19:13.000 --> 19:18.000 And it's really useful to get so fast at counting. 19:18.000 --> 19:19.000 So it's done. 19:19.000 --> 19:21.000 We done the war process. 19:21.000 --> 19:23.000 The features are imported. 19:23.000 --> 19:24.000 Count it. 19:24.000 --> 19:27.000 And right now we are just rebooting the web docker. 19:27.000 --> 19:30.000 And we will get some results. 19:30.000 --> 19:32.000 Let's see those results. 19:35.000 --> 19:45.000 Get back and the presentation. 19:45.000 --> 19:46.000 Okay. 19:46.000 --> 19:47.000 So at the results. 19:47.000 --> 19:48.000 Here are the results. 19:48.000 --> 19:50.000 Yeah, the dashboard you get. 19:50.000 --> 19:51.000 You can access it. 19:51.000 --> 19:52.000 We have an address. 19:52.000 --> 19:55.000 And I will maintain it online few days after the first them. 19:55.000 --> 19:57.000 You can browse the results. 19:57.000 --> 19:58.000 We got from this process. 19:58.000 --> 20:00.000 And we see some interesting insights. 20:00.000 --> 20:01.000 So first of all. 20:01.000 --> 20:03.000 I don't want to see it. 20:03.000 --> 20:06.000 Because contributors are adding benches and nothing. 20:06.000 --> 20:07.000 Belgium and nothing. 20:07.000 --> 20:17.000 And so we also see that there's a regular progress on mapping benches in Belgium. 20:17.000 --> 20:20.000 This is the basic features of the web interface. 20:20.000 --> 20:26.000 You can obviously extend that depending on the theme you selected for your project. 20:26.000 --> 20:29.000 What you got from this dashboard. 20:29.000 --> 20:32.000 We also have the most frequent keys that has been used on benches. 20:32.000 --> 20:35.000 And as I said, we don't only get the main tag. 20:35.000 --> 20:36.000 I mean, it's a bench. 20:36.000 --> 20:38.000 But also the secondary attributes. 20:38.000 --> 20:40.000 And put on my steering wheel. 20:40.000 --> 20:43.000 What's the key that are most used on features as well. 20:43.000 --> 20:47.000 But that's a very generic set of features. 20:47.000 --> 20:50.000 We also got some podium. 20:50.000 --> 20:53.000 And we see that. 20:54.000 --> 20:57.000 You know, remember, but it's written. 20:57.000 --> 21:03.000 We have almost a thousand contributors that has been contributed on benches in Belgium. 21:03.000 --> 21:05.000 That's a figure we don't. 21:05.000 --> 21:10.000 We are not used to that figure because without predominates, we are to get this number. 21:10.000 --> 21:15.000 We can get the number of people that has been the last editor of many benches. 21:15.000 --> 21:17.000 Partically on tag info. 21:17.000 --> 21:19.000 But we don't get this number. 21:19.000 --> 21:28.000 Because this is the compilation of all mappers involved both adding and adding on those features. 21:28.000 --> 21:30.000 But we have a winner area. 21:30.000 --> 21:38.000 The podium tells that's the EB user got 7,000 points by mapping benches in Belgium. 21:38.000 --> 21:39.000 So congratulations. 21:39.000 --> 21:41.000 If you know him, Tanym. 21:42.000 --> 21:46.000 Obviously this podium updates a long day. 21:46.000 --> 21:52.000 Because I processed only one time from this presentation that you kind of dates daily. 21:52.000 --> 21:55.000 Or even only on a holiday basis, you can re-burn the process. 21:55.000 --> 21:58.000 It will only get the diffs. 21:58.000 --> 22:00.000 It won't process the world at a base. 22:00.000 --> 22:02.000 So here it was the initialization. 22:02.000 --> 22:05.000 You don't get this hassle every day. 22:05.000 --> 22:08.000 Every day it just updates the last 24 hours. 22:08.000 --> 22:10.000 So this podium of dates. 22:10.000 --> 22:17.000 And here is how we manage efficiently some contribution progress in a pencilic map. 22:17.000 --> 22:20.000 But when you help. 22:20.000 --> 22:27.000 It's not over that venture only starts here actually because we provide the most valuable product. 22:27.000 --> 22:31.000 There's technical depth as many projects. 22:31.000 --> 22:35.000 So you may help in those values fields. 22:35.000 --> 22:37.000 If you want to. 22:37.000 --> 22:40.000 Not only the technical depth, but also to a test. 22:40.000 --> 22:44.000 Because we are pretty good at runs the. 22:44.000 --> 22:47.000 I'm most 20 projects on four instances. 22:47.000 --> 22:49.000 Yet on on Podomar different instances. 22:49.000 --> 22:53.000 But it may deserve some well designed test. 22:53.000 --> 22:55.000 You need test and integration test. 22:55.000 --> 22:57.000 So if you want to help feel free. 22:57.000 --> 22:59.000 We also want to develop some new features. 22:59.000 --> 23:00.000 Custom counts. 23:00.000 --> 23:02.000 We didn't do custom counts. 23:02.000 --> 23:03.000 It's only counts. 23:03.000 --> 23:04.000 It's not a rare for now. 23:04.000 --> 23:05.000 It's not custom. 23:05.000 --> 23:06.000 We don't. 23:06.000 --> 23:09.000 We can get the amount of benches that are at least two seats. 23:09.000 --> 23:11.000 For instance. 23:11.000 --> 23:14.000 It may be interesting to have those those features. 23:14.000 --> 23:15.000 But also. 23:15.000 --> 23:18.000 You can use the change log if you want. 23:18.000 --> 23:22.000 You can use the existing Podomar instance and get used to that. 23:22.000 --> 23:24.000 Just get on the a pencilic map week. 23:24.000 --> 23:27.000 You will get a list of the four instance existing. 23:27.000 --> 23:31.000 And you will be able to connect and get the change log on the existing project if you want to. 23:31.000 --> 23:40.000 That may be also help to give feedback about that and ask for a particular information that may be missing in this change log. 23:40.000 --> 23:42.000 And also creating your home project. 23:42.000 --> 23:46.000 You will be able to use Podomar on your own server. 23:46.000 --> 23:50.000 Use it on the topic you want to select. 23:50.000 --> 23:57.000 And that's also really nice to provide to extend amounts of instance existing. 23:57.000 --> 24:02.000 You can get the source on GitHub on the Append Street map front. 24:02.000 --> 24:08.000 And I'm sure you will have some very useful comments. 24:08.000 --> 24:11.000 But there's one more thing. 24:11.000 --> 24:14.000 The most complicated one I think actually. 24:14.000 --> 24:20.000 As I mentioned, Podomar is able to gather the related feature as I explain. 24:20.000 --> 24:23.000 Because then she's our mostly mapped as nodes. 24:23.000 --> 24:26.000 It's fine when it's doing so because it's a very simple feature. 24:26.000 --> 24:28.000 You have this location in the problem. 24:28.000 --> 24:30.000 But sometimes you have ways. 24:30.000 --> 24:31.000 Like this one. 24:31.000 --> 24:34.000 An inappropriate map only nodes all coordinate. 24:34.000 --> 24:36.000 So ways are composed of nodes. 24:36.000 --> 24:39.000 And if you don't have nodes, you don't know where the way is here. 24:39.000 --> 24:41.000 That's a problem. 24:41.000 --> 24:43.000 So let's consider this situation. 24:43.000 --> 24:45.000 You have three nodes mapped as nodes. 24:45.000 --> 24:51.000 And you have many other features in a pen street map like this tree rule mapped as a way. 24:51.000 --> 24:55.000 But what happens when a user show up and say, 24:55.000 --> 24:58.000 this tree rule is not free or it's actually a bench. 24:58.000 --> 24:59.000 And it changed the tags. 24:59.000 --> 25:03.000 It changed the natural tree rule tag into a many bench. 25:03.000 --> 25:05.000 So Podomar will sit in this. 25:05.000 --> 25:06.000 It will appear in this. 25:06.000 --> 25:13.000 Okay, you have an existing way that became in the last 24 hours a bench. 25:13.000 --> 25:19.000 And now as Podomar is not maintaining in this is to to get the wall. 25:19.000 --> 25:20.000 Pen street map database. 25:20.000 --> 25:22.000 It won't know the nodes. 25:23.000 --> 25:26.000 So we don't know that the way has become a bench. 25:26.000 --> 25:29.000 But it won't know where. 25:29.000 --> 25:35.000 So you have to get the nodes with another pass query to catch up the catch up. 25:35.000 --> 25:36.000 Let's say. 25:36.000 --> 25:39.000 So it will intensify the missing nodes and ask of a pass. 25:39.000 --> 25:41.000 But that's not an efficient way to do so. 25:41.000 --> 25:43.000 Because sometimes of a pass may be overloaded. 25:43.000 --> 25:49.000 Because you may have issues of any kind of by depending on third parties of two. 25:49.000 --> 25:54.000 So I think what I call an unreached diff may be useful to stay in the diff. 25:54.000 --> 25:56.000 We have the related feature as well. 25:56.000 --> 26:00.000 Currently in a bench street map, you will only see the way. 26:00.000 --> 26:02.000 You won't see the nodes in the diff. 26:02.000 --> 26:04.000 That's why Podomar can't know them. 26:04.000 --> 26:07.000 And what if we have those unregative on a bench street map? 26:07.000 --> 26:13.000 Podomar could know the nodes and don't have to rely on a bench street map to get those geometry. 26:13.000 --> 26:16.000 Without maintaining the wall database. 26:16.000 --> 26:19.000 When you maintain a render, you maintain the wall database. 26:19.000 --> 26:24.000 So you don't have issues when some features show up with existing tags and so on. 26:24.000 --> 26:26.000 You already have it in database. 26:26.000 --> 26:31.000 It's not the case for Podomar and similar software running the same method. 26:31.000 --> 26:33.000 Thank you for your attention. 26:33.000 --> 26:36.000 You may have questions. 26:36.000 --> 26:37.000 Thank you. 26:37.000 --> 26:55.000 I hope it was clear. 26:55.000 --> 27:00.000 You mentioned that community was a big drive in this project. 27:00.000 --> 27:03.000 Have you personally made any use of it? 27:03.000 --> 27:06.000 What have you done with it? 27:06.000 --> 27:13.000 I said there are currently four Podomar instances running. 27:13.000 --> 27:15.000 I run three of them. 27:15.000 --> 27:17.000 Mainly in France. 27:17.000 --> 27:20.000 We are using one for map your grid worldwide. 27:20.000 --> 27:23.000 So it's a demonstration for worldwide extent. 27:23.000 --> 27:27.000 But also two others in France, focused in France. 27:27.000 --> 27:31.000 So we have the different configuration. 27:31.000 --> 27:33.000 And yes, I'm making a great use of that. 27:33.000 --> 27:36.000 And it saves so much of my time. 27:36.000 --> 27:43.000 I don't worry anymore about getting difficult KPIs to process on my own projects. 27:43.000 --> 27:46.000 Thank you. 27:46.000 --> 27:51.000 Another question? 27:51.000 --> 27:56.000 You will sleep really, really well with Podomar than without. 27:56.000 --> 27:58.000 Believe me. 27:58.000 --> 28:08.000 Thank you for the presentation. 28:08.000 --> 28:14.000 I'm still a bit confused about the use of it. 28:14.000 --> 28:19.000 I can understand it for monitoring to manage. 28:19.000 --> 28:20.000 How is it going? 28:20.000 --> 28:25.000 Who used this? 28:25.000 --> 28:26.000 That's a good question. 28:26.000 --> 28:29.000 I identify at least two different profiles of users. 28:29.000 --> 28:33.000 Indeed, project managers have a project. 28:33.000 --> 28:37.000 In the community and project of the month of the association, 28:37.000 --> 28:42.000 the fourth instance is the project of the month of the French community. 28:42.000 --> 28:45.000 So project managers are using that. 28:45.000 --> 28:47.000 But also third parties. 28:47.000 --> 28:51.000 In open street map ecosystem, we have many different actors and some 28:52.000 --> 28:56.000 companies that are interested on given topic. 28:56.000 --> 29:02.000 And without such tools, they are completely lost to understand what is 29:02.000 --> 29:06.000 actually the contribution on this topic in open street map. 29:06.000 --> 29:10.000 They may look at the tools I mentioned, 29:10.000 --> 29:13.000 a handful, a tagging history, whatever. 29:13.000 --> 29:18.000 But it only gives a very broad insight of what's going on. 29:18.000 --> 29:23.000 We have to get into details because people are not only adding 29:23.000 --> 29:25.000 features, they are also adding them. 29:25.000 --> 29:30.000 And changing tags is as valuable as adding features right now. 29:30.000 --> 29:32.000 We have to add features. 29:32.000 --> 29:36.000 We have some movements inside the existing set of features. 29:36.000 --> 29:41.000 So that's why even companies or third parties teams can be interested 29:41.000 --> 29:47.000 to run their own instance of products just to observe what's happening. 29:47.000 --> 29:54.000 Thank you. 29:54.000 --> 29:58.000 I think we've got time for one more question. 29:58.000 --> 29:59.000 Hello. 29:59.000 --> 30:04.000 I just curious, did you say that it needs to write to open street map 30:04.000 --> 30:05.000 by the API as well? 30:05.000 --> 30:08.000 I was wondering what is it writing? 30:08.000 --> 30:09.000 Exactly. 30:09.000 --> 30:12.000 We just take back the interface. 30:12.000 --> 30:14.000 The writing is not required. 30:14.000 --> 30:17.000 It's an additional feature we provide to put on my users 30:17.000 --> 30:19.000 because we have the web editor. 30:19.000 --> 30:23.000 And the only situation in which it writes on open street map is 30:23.000 --> 30:26.000 because people are contributing to open street map directly 30:26.000 --> 30:28.000 in put on my interface. 30:28.000 --> 30:30.000 But let's say it's not mandatory. 30:30.000 --> 30:35.000 You can perfectly run a project only with observation feature. 30:35.000 --> 30:37.000 Like this one. 30:37.000 --> 30:39.000 No editing in this dashboard. 30:39.000 --> 30:41.000 Only observation. 30:41.000 --> 30:44.000 So it's only for punctual contributor. 30:44.000 --> 30:47.000 Right now, the web editor needs to post note by the way. 30:47.000 --> 30:49.000 You are not able to draw ways. 30:49.000 --> 30:52.000 Users that want to draw ways mapping benches as ways, 30:52.000 --> 30:57.000 for instance, are invited to use more elaborated digital. 30:57.000 --> 31:00.000 I think we've got five minutes. 31:00.000 --> 31:03.000 Thanks a lot for presentation. 31:03.000 --> 31:07.000 Could you explain in video, I've seen that you initially 31:07.000 --> 31:10.000 don't load whole world map. 31:10.000 --> 31:15.000 And after that, filtering out data for Belgium. 31:15.000 --> 31:17.000 Is it a correct way? 31:17.000 --> 31:23.000 Because you can download only files for example for Belgium. 31:23.000 --> 31:26.000 And don't process whole world. 31:26.000 --> 31:33.000 Is it not included the contribution metadata or what's the reason for this one? 31:33.000 --> 31:37.000 You mean what's it actually in the files? 31:37.000 --> 31:38.000 Yeah, yeah. 31:38.000 --> 31:44.000 I've seen in the videos that first step was downloading data from OpenStipMap. 31:44.000 --> 31:45.000 Yeah, whole world. 31:45.000 --> 31:46.000 Yeah. 31:46.000 --> 31:47.000 Not seen it. 31:47.000 --> 31:51.000 And the next one step filtering out data. 31:51.000 --> 31:55.000 Everything instead of Belgium. 31:55.000 --> 31:57.000 Just keep only Belgium. 31:57.000 --> 32:00.000 But OpenStipMap, 32:00.000 --> 32:04.000 allow you just download data for Belgium. 32:04.000 --> 32:05.000 Yeah. 32:05.000 --> 32:07.000 The detail. 32:07.000 --> 32:09.000 And that's a good question. 32:09.000 --> 32:15.000 Because the focus of the platform, I chosen Belgium this afternoon. 32:15.000 --> 32:19.000 And there's several inputs to provide as to focus it on Belgium. 32:19.000 --> 32:21.000 It's not only the data file you provide. 32:21.000 --> 32:23.000 I could import the worldwide file. 32:23.000 --> 32:26.000 And instead of Belgium, I could get the world. 32:26.000 --> 32:28.000 But it's way more data to process. 32:28.000 --> 32:29.000 And we have those polygon. 32:29.000 --> 32:32.000 And the polygon is useful to process the divs. 32:32.000 --> 32:34.000 We have the data file with the history. 32:34.000 --> 32:35.000 And we have the divs. 32:35.000 --> 32:38.000 And the divs are only available worldwide. 32:38.000 --> 32:43.000 The effect rig, which is a company, is preparing for free for us. 32:43.000 --> 32:46.000 The localized data files for history. 32:46.000 --> 32:49.000 But we don't have the localized divs every time. 32:49.000 --> 32:53.000 Belgium community can provide the localized divs if they want. 32:53.000 --> 32:57.000 It will be good to use them without filtering with the polygon. 32:57.000 --> 33:00.000 But we have to have the polygon for the divs. 33:00.000 --> 33:05.000 Worldwide div instead of the data file. 33:05.000 --> 33:06.000 I think that's it. 33:06.000 --> 33:07.000 Time. 33:07.000 --> 33:09.000 Thank you for your talk. 33:09.000 --> 33:10.000 Thank you.