 Good morning, everyone, and welcome to this online version of Open Belgium. I want to quickly thank our three main sponsors, Mono Design, Microsoft and Agentschappen, Binalands, Pesture, but without further ado, I want to give the floor to Steven. One moment, please. Getting started. Does that work for you? Yes. Okay. So good morning, everyone. My name is Stefan Tjobel. I'm representing Antico. I'm the workgroup leader, the technical specifications of the TNITS platform and TNITS stands for Transport Network Intelligent Transportation Systems. So today I will be talking about sharing open road data in Flanders and Europe, the TNITS way. I will give an introduction first and then Lien and here it will continue focusing on the Flemish context and giving you examples of what TNITS is about and what it means. So without further ado, here's the overview of my 10 minutes introduction. So context, introduction to TNITS. Quick word on the TNITS Go project and I will also show you an overview of the European open road data exchange services and stop with an outlook. So first of all on the context, so of course everyone is concerned about road safety and vehicle manufacturers over the last year have developed a number of technologies to support drivers keeping lane, keeping safe speed, you know, even making sure that the car drives correctly and shifts gear, things like that. So these are called ADOS, advanced driver assistance systems and they typically work with a map on board of the vehicle that can, that map can actually be for the driver for a visualization aid, but it could also be for the car just to, as I mentioned before, you know, pick the right gear in an automatic gearbox. So that map is quite important. If it's on board, then of course it needs to be maintained because as it is the representation of the environment, it needs to be correct and that's a crucial thing, the maintenance of the digital map. So the leading map makers have invested in a number of technologies to collect information on the road environment and bring that to their maps to update their maps. Think about this type of street fuel vehicles, think about floating car data, so monitoring either your mobile phone or your navigation device in your car and use these anonymous traces to update their maps. But one important aspect of sources for changes for maps comes from government sources. That's authoritative data. A lot of that data already in Europe is being published or made available as open data. What is important is because the leading map makers, they have high quality map databases already. The focus is on the changes of the road data. So not necessarily the bulk, as is data, but the changes of the road data. And there's also a common data model and interface required to do that. Because if you imagine like a leading map maker, if they get access to authoritative data in one country, they would prefer that the same access would apply for authorities in different countries. So common data model and interface. And that's exactly where TNITS jumps in. So TNITS is on one side, it's an association. It's a platform under the Ertico umbrella. But it's also a technical specification. So it's under the same technical specification, technical committee. What is it? 278 Working Group 7. That's the ITS group. And it's also a building block for today's and future mobility data space. So on the right hand side of the slide, you see a number of building blocks. And each represents a domain where standardization of interfaces of data models has happened in the past or in the recent past. So on the bottom, you see vehicle sensor data. There is a standardization activity ongoing called sensoris to deal with that. For traffic information, you might have heard of DATEX. For multi-modal, there's also a group that's working on technical specifications. So there's, I would say, complementarity in the technical specification for the exchange of mobility data. And on the top right, you see TNITS as one of the building blocks for base layer data or base map data. So TNITS is a trusted and market-driven mobility data exchange service. Trusted because authorities provide the data and market-driven is because leading map makers are actually, you know, heavily involved in both the association and the technical discussions and also the strategy of the platform. So it's once the, I would say, rogue authorities adopt the or implement such a service, then they will be sure that at the end, the map makers will consume the data and update their maps accordingly. So what's in focus? As I mentioned before, TNITS represents the data model, the format, the infrastructure to exchange primarily changes of road attributes for the maintenance of digital maps for different ITS services. So we're talking about typically static road attributes, attribute just speed limits, traffic restrictions, warning information, EV, alternative fuel charging points, lane information, and so on. So when we look at a typical TNITS infrastructure in place, it's at the side of the rogue authorities. When they publish changes of rogue data, they do it in a TNITS compliant way, and that's the bridge, so to speak, to the map makers. TNITS does not address how the map makers provide fresh maps to the users, be it the car, a roadside unit, a traffic center, a portable navigation device, or an in-vehicle system, that's outside the scope of TNITS. What is also interesting is in the red circle, you see that the arrow goes both ways, and that's the so-called, so you see the changes streaming from left to right, so towards the road, towards the map makers, but there's also a feedback link that's specified, and that actually reflects information that is provided by the map makers back to the rogue authorities, which describes how the map makers actually decoded and integrated that data. So let me go to the next slide. So a word on the TNITS association, so I mentioned it's coordinated by ETICO. Currently, the members are either rogue authorities, mob and service providers, ITS, and transport organization, and you see some names, so we have a lot or a strong mordic presence in the rogue administrations. We have the main map makers in Europe on board, Tom Tom here, and Geo Junction. So the association is supporting the European policy on RTTI and ITS. It supports the standardization, so there's technical specification is available. It offers implementation support, so if a rogue authority wants to implement such a TNITS service, it can get support from the association, and that support might be the access to the reference model, so the UML that describes the data content and the exchange infrastructure. Then it's also about building the brand and the trust. So at the end, at the driver's side, at the end of the data users, it needs to be known that the data, the maps are maintained via a TNITS process, as that increases the reliability of that information, and therefore also the service. We have worked for over seven years in strong cooperation with the European Commission, with SEN, with the Joint Research Center, and also with ITS associations. We are not doing that alone. We are doing that together with a number of partner standardization groups. I will not go in detail about them, but just understand that there is a strong link, of course, with dynamic information, whereas we focus on static road data. There's also the community that's working on traffic. There is a dynamic information traffic data, that's the DataX2, and the Traffic Management 2.0 platform that work on that. There's the link to automated driving via CCAM and via the auto drive forum. There's the link with the National Access Point Program, and then there's of course the link to SEN as a standardization body in Europe. One word or few words on the TNITS Go project, so it's a SEV project. It will actually end this year. There are 20 partners in Europe, and the aim is to build at least 15 TNITS services across Europe, which publish changes of road attributes, typically minimum on the TNT network. There are a number of partners there that provide also updates for lower road classes. I will do that immediately. That project is also supporting all standardization and implementation initiatives. I mentioned the feedback loop. Here is where it's being prototyped, and also new features for new attributes, for new cases that are being explored in this project. I will not go into great detail on this slide, however I would like to emphasize. This is the overview of the TNITS services today in Europe. On the top row you have the country for which the service or who has implemented the service. You say who is the data provider. You see the status. There is the coverage of the updates, whether it's like for a full country and applicable for the TNT or all roads, whatever. Somewhere in the middle you see the map attributes, which attributes and features are supported. Typically, as you can see, speed limits are of top priority. Over road information like street names, route numbers, that type of information, road classes, lane information is also made available by a number of road authorities. It indicates the location referencing method, either OpenLR or GML coordinate string. It indicates the updates, so the frequency of the updates. You see that some countries are providing daily uploads or daily changes of road attributes on their network. There's the link to the service. There is a mention if the service is also available via the national access point program, and on the right-hand side a little bit bigger is the data license under which the data is provided. So the second row, you see Flanders. That's the one you will be hearing more about on the next presentation. So what's the link with open data? First of all, because of the origin of TNITS and the fact that that is what's supported by the European Commission by a number of research projects, the results of funded projects are typically open as much as possible. So that's one thing. On the other hand, from the overview we've seen before, that you can see that many or almost all of the data providers offer data under open data license. A creative common forest mention the most. Attribution is probably around 50%. That means that you have to declare that you are using or you have to indicate the source of the information. I've seen no share of light conditions, which is very important to maximize the reuse of that information. There is the technical specification with SEM, which is available for marginal costs. And of course, you are free to use the specification to implement. So on the implementation itself, the web service to expose the data, there are no costs involved. And there are some authorities who do not use an open data license yet, but use the TNITS specification and the interface for their pilot service, EGN in France. So the National Geographic Institute in France is an example of that, of such an authority. Now that brings me to almost my last slide. So I'm not going to go too much in detail, but this is the roadmap for TNITS. So we're now in 2021. We will finalize the TNITS Go project and implement the feedback loop. We will have activities to include TNITS work under the new National Access Point Program. In 2020, TNITS will of course support the Intelligent Speed Assistance, which is mandated by the European Commission in the General Safety, what is it, GSR program for new cars. So by 2020, all new cars on the European market will need to have a speed assistance technology. So TNITS is going to support with fresh speed limit information. So 2023, we will also see the involvement of cities and commercial road operators. So currently, the focus is on national road authorities, but that will shift in the future because there might be important bigger cities, metropolitan cities that have important data to share in the TNITS way without going through a national body. So 2025, extended road attributes and also work on automated licensing. In 2017, we support for the higher level of SAE automations for self-driving cars. And on the further horizon, we expect that there will be some harmonized worldwide system in place where there's a single process for sharing and reusing road data. One has to keep in mind that the map makers who consume the TNITS data, they are typically global players like Tom Tomman here. And that's in fact the best way how they can consume the data, the best way how they can forward the data to the end users. So the end user is typically the citizen. And if you benefit the citizen, that's of course in the interest of the authorities. So along the path, you will see the maintenance of the technical specification and of course the growth of the community. So if you just tune in and do not really understand what I was talking about. So here it is in a nutshell. So TNITS is a platform technical specification to exchange changes of road data in Europe. The focus is on static road data and it's a key component in a mobility data space in Europe and outside Europe. The road authorities provide trusted data to modern service providers and help us to improve road safety and ensure efficient road use. And currently there are a number of operational services in Europe and most of them share their data under open data license. More information you can find on the links. You can have a look at them after the call or later on watching the movie. Latest news, we recently had a webinar on TNITS success stories which you might want to have a look at. So that's it from my side. I conclude my presentation and I give over the floor to Lin and hear it. Thank you Stefan for this interesting presentation. So in this second part we are going to focus more on the case of Flanders. So we want to make it a bit more concrete and at the end of the session you can ask questions if there are questions and we will answer them one by one. You can also write them in the chat so you don't forget them. Before I start my presentation I want to do a small poll to see whether there are already some people in the audience who know about our project. So you can answer just yes or no so we can have an overview of that. Okay so I see that the most people answered it. I will publish the results in just a second. So I see that about a third of the people already know about the project. So I'm going to give these people a quick recap in the beginning of our presentation. Then I'm going to focus more on the TNITS service itself. Then further on we are going to talk about the challenges we tackled in the project. Talk about one proposed solution, our mobile app moving and then in the end we are going to address our future plans both in the short term and in the longer term. Then at the end also my colleague here, Twain Haver, will give a presentation, a demonstration of the two applications. So the project Snell at Vlaanderen is actually a cooperation between the Department of Mobility and Public Works and the Agency of Roads and Traffic. So here you can see an overview of the project team. You can see the name of here, Twain Haver, he's the application owner but so you hear more about him at the end. My name is Liem Waiklands, I am the business analyst and also the person behind the help desk. So the project has actually three goals. The first one is to create one unique authentic data source for all the traffic signs in Vlaanders. So to accomplish this we first had to merge two existing databases. The first one the traffic sign database of MOA was developed for the cities and municipalities and then you also had the road asset database of RIV for the major roads. So it was chosen to develop the road asset database of RIV further and therefore we did a gap analysis to know more about the needs of the cities and the municipalities. This was done in 2017 and in 2018 the new Verkirch-Bordewandre application was launched. Secondly we want to derive a speed map for Vlaanders and then thirdly we want to publish this as open data. So on the one hand for the TNITS service for the map makers and on the other hand also for just for the general public as GIS services on the Hayopunt website of Vlaanders. So firstly how did we derive these speed limits? So the traffic signs or point locations and then the road network are lines. So we project actually these traffic sign locations onto the streets, the lines, with an algorithm that actually drives as a car through the whole Flemish road network. When it passes a traffic sign the attributed speed is also gets will be on the line and from then on this speed will be the case for that line and further on as you can see in the example. The result is an automatically generated speed map which takes into account the updates that were done during the day and then process them each night and then the next day you can see the results as a new speed map. The algorithm uses a number of things. So first the traffic signs for example a build-up area sign that says that the speed has to be 50 kilometers an hour, then the road morphology of the road network and also the implicit speed limits that you can find in the legislation. For instance when there is no traffic sign present the speed is 70 kilometers an hour. The result is for such as this but then for whole Flanders. So here you can see the example of the city of Thurnout and then on the right for Leopoldspurg. So for example if you come from the west in here on the right you can see the orange color that says the speed is 70 kilometers an hour, then you pass the build-up area sign of Leopoldspurg and from then on the speed is 50 kilometers an hour. So all this data is shared within the TNITS project. Here on the slide you can find the link to the service itself which was developed as a pilot project in the Common Exchange format Rosatte. So we took all the traffic signs in the database and tried to map them on this format. We started with only the speed limits and the traffic signs with a speed limit and then we also took into account more traffic signs as you can see here on the slide. This is only a selection you can find the whole list on our website. So all this information is shared with the map makers TomTom and here as Stefan already discussed. So there only the updates are shared. So you have the updates performed by road authorities. They appear in the TNITS service so they can be used by TomTom and here to process these updates and this will be available in the products. So GPS devices and other devices and they will take this into account when they calculate your route from A to B and as such this has a positive impact on the traffic safety and livability. Then we also offer other publicly available data on web map services and web feature services. So firstly the graphical representation of traffic signs. So really that you can see how the traffic sign looks like like it is visualized in the application itself. Then you have also point locations that you can use to do queries for instance and also all the derived data sets. So firstly the speed limits but also other speed zones like build-up areas, highway zones and residential areas for example. For people who don't have access to GIS software they can also go to the geopunt home page on the map. You can also visualize the speed limits and the traffic signs. Then what were the challenges in the project. So data quality was a big challenge. We used two data sources. So firstly the official Flemish road network Wegergister where we use the morphology and the driving directions. So we don't take into account unpaved roads or private roads but if this data is not accurately available in the road network then this will cause errors. Also the driving directions were only available on the major roads and not for the smaller ones and this is also a bit problematic at some locations. Then we use of course also the traffic sign database where we had the challenge of getting all the municipalities and cities to update their database. So for a number of municipalities their traffic sign database is quite outdated and they find it difficult to start updating them. So we try to encourage them to do this through giving workshops and also we try to make on-site data collection more efficiently. I will talk a bit more about that in the further presentation. There are also some cities that use external software so they don't work in our application but they use other software providers and there we are talking to them to synchronize their data so we can also use it to derive our speed limit map. So to get the users on board with the workshops in each Flemish province we talked about tips and tricks and gave some training. We also have a website Verkeersbordepen-Vlaner where you can find manuals for the applications, more information about our open data and also frequently asked questions and also our help desk is always available so you can send a mail with a question to Verkeersbordepen-Vlaner.ba. Then I want to talk a bit more about our mobile app moving so we understood from our users that they had problems to do on-site inspections. They went on to on-site with a paper map and started writing on that map which traffic signs were outdated in the database and which were okay and so on but this takes a lot of time so therefore we developed our mobile app moving very quickly actually in a few months so we focused on the minimal usable product. We asked our users what is really the most essential what do you need to do these inspections and we launched a beta version so a number of users could already test the application very quickly and the results were quite positive so we also focused on user friendliness on a mobile device because when you go on terrain you of course want to use a tablet or even a smart smartphone so it had to be easy to use on a small screen. The big advantage of using move-in is that when you do an inspection you have this date of on-site inspection which is an important measure of data quality because of course our users of our open data they don't know which of these cities and municipalities is really updating their database or which ones are outdated and with this date of on-site inspection you get an important measure of data quality. So what were the results of our efforts so in 2018 the Vergeer-Bordefraander application was launched and you can see that a number of municipalities got on board quite quickly you also see the the hatched municipalities that they use external software and then it's now quite recently in 2021 you see that the map is turning blue and that more and more municipalities are starting to use our applications. We also track our user amount of users with Google Analytics from 2019 on and you can see the rising trend in user accounts to 2020 and also for a move-in that we launched at the end of 2019 you can see that it was really popular in the spring of 2020 and we believe that it has it's also the consequence of the COVID-19 measures when a number of employees of local authorities had to do different jobs because they couldn't do their regular tasks. So actually for COVID-19 our so it was actually a good thing for our traffic sign database. Then what are our future plans so we want to bridge the digital gap between on-site inspection and database input further so actually our vision there is that you take a picture of a traffic sign and it is automatically updated in our database. Of course this is something for the long term and we are not there yet but this is what we want to accomplish in the future. Other plans are deriving weight restrictions because we now focus on speed zones and we also want to derive other interesting data sets from traffic signs. We are also integrating with other applications so as Stefan told you the focus is on static data sets but we are also looking into how we can incorporate dynamic road signs within the mobility data project. Then we also have a new application ERG in Flanders for making the local decision mobility decisions publicly available within the LB LOD project. So we want to make a link between a mobility decision by a local authority and the traffic signs that are linked to that decision. Then we have also a new version of HEPOT and we also want to see what we can do with temporary traffic signs but that is only just starting. Then we also want to do a redesign of the existing application. It was launched in 2018 as a new version of an old application so it is already quite old and we want to tackle technical depth and improve our data model and of course keep all the users on board. And then also in the TNITS project we want to look into the feedback loop, what we can do with this in our application and also the new code to the new standard. So this was everything for me and I want to give the floor to Geert van Gijver who will give you an overview of how our applications work. Okay, hello everyone I'm Geert van Gijver, I'm the application owner of Moving and the traffic sign database. I work for the agency for roads and traffic and in the next 15 minutes I give you a short demo of the Moving app and the traffic sign database. First I want to start with moving because that's the most important thing to give some inspections of the existing traffic signs but also you can add new ones for instance. It's in fact a web app so I can use it on my browser but when you have Chrome installed on your iOS or under your Android device you can use it mobile. So I go, I zoom in, I can choose here my background cards, auto photos of GRB or our regular background cards. When I zoom in they will appear you see the black dots and the purple ones that's where I have permission to so the purple ones I can manage. The black ones are in fact the traffic signs that are that are from the local authorities so I work for agency of roads and highways so here this road is one of ours so I can manage the traffic signs there. I can also click on one and then you see which traffic sign there is located on that place so you can see here we have a bunch of directing traffic signs. I can also click on one that's not in my permission so I can see what's behind or in the side streets of our main road. There's also a legend so I can see what just happened to our traffic signs. Right now I have done none of the control tools so there are no recent controls here. I can also put out the signs that are not in my supervision or not in my authority and then I can start a control. First of all I can check one, start control and then I can choose between remove it, change it or there is no action necessary. When I put no action necessary I can still take a new photograph of the sign in fact so I can take one here. I can take this photograph, I open it and I can even remove this. It's on the test and integration side so there is some problems with the photo so I can remove this photograph and add this new one. I click on send and you can see there is control right now that needs to process in the traffic sign database. Also I can remove some, for instance I can click on remove. I can even choose which one of the traffic signs will I remove. I think for instance only the under traffic sign here I will remove and the three others will remain so I can also add a new photo. I'm not going to do it right now and I send it. I can remove a whole of everything and I check all the things here, click to remove and send it or I can change one. I can start control, I can say change it and I say add see 43, 90, 43 here, 90 and I can take a new picture for instance. I just select one, it's not the right one but just on the demo so it doesn't matter. I can remove this picture because it's not the good one and I send it and then the last one so I can add a new one. So when I click in the card for instance I can take my auto photos because it's it's better to look where did you pick the new traffic sign. For instance I want to set here a new traffic sign. I just click in the card I set start new traffic sign and I give you my state of the direction which it seems when the cars are driving so in this thing it's that direction that I should set my new traffic sign. I choose the side of the road in this fact right I go to control. I set in my ads for instance also a see 43 with 90 and B9 400 and 90 will be 900 millimeters tall. Also I can add a photo and I can send it and you can see when I go back to the regular site you can see here with the cross unit it's a new traffic sign that I put into the database. So now I've done my work and moving so you can go along on the streets check every sign that you pass and then you go for the other work you open the Verkeers-Borden-Flanders application. So here I'm still on test and here I hope you see it otherwise I have to you see here the controls on terrain and I have for instance I have five so here you see the user which the text which I added I added the date it's a new one to change to remove it you can see here the status the owner of the traffic sign so this is district Pürs I see the traffic signs and where the traffic sign is located so this is the N16 in Borne and I can see here the pictures I added to the so I can go when I use the spy glass I can go to the traffic sign is that and you can see here now it's selected and I can then do the action in fact and the action is in fact the green logos or that you see here so when I click on the green logo my action is done so when I select another one and resect we reselect the traffic and you see the photo is added then I choose the next one was remove one traffic sign over the bench I go are you sure you want us to remove the plate and you see it's directly removed the others because there were three F33 ace so I removed one I can check it also and I click on okay and it's done then here I want to remove the total traffic sign are you sure to remove totally I say yes oh and here it says it is a temporary sign of it so I can remove it so it's normal so I can I first have to set the the temporary order plans traffic sign on the right spot and then I can remove it when I want to here I want to change one so here I set in my seat right not right now but I can I set to add a C4 390 so I go here to the C section and C4 3 I choose 900 no kilometers added and the speeds regime is 90 so I click on okay and it will be added on the D7 it's okay I click on okay the photo is renewed and it's out of my list and then the last one is a new one that I will add so I click on the logo I just need to link it to the Flanders road database or we can register so it's linked on this segment of the vehicle register then the application knows it's n16 it's on the right side I pick the date of placement so I for the first of March for instance the authority spurs I go to my I set also it's a C4 3 also a 900 with 90 on it and I'm my second also automatically there's a support added to the bunch of traffic signs my second plate is a B9 that's a 400 so it also then my traffic sign is completed I can check everything I can change my diameter of the support when it's on concrete or just on soil I can choose here every everything I can manage I mean it's okay I just click on okay and you see when I choose close this one I added this extra there are a whole bunch of seat 43s for the here but this is the new one I added I can also see on my dates check control and that's very important for the TNATS for the for here and Tom Tom to know this date or last change 15 3 15 3 the 15th of March is today so they can when they get the TNATS service they can filter on that and then took the change is as real so that's very important so when I go back to moving it takes a while but I when I refresh and I go back to the place where I did some it's about here I think normally I can find a little more no normally they but it takes a while but normally all the the recently changed traffic size will be with a full circle around it so you know you have recently checked these ones and you have to check all along the where there are no recent controls or checks on it that's in brief what you can you are here in the GUI you have you can do the same direct somebody muted me I think so you have here in the GUI you can do the same things directly on the database so you don't have to use moving but it's a very simple thing to maintain or to update your traffic sign database a quick review to the TNATS rest data sets so you see the links will be provided on links so you here see the that's are already a lot of Rosetta data sets I mean I click one you can see here how it's give to the Tom Tom and here's so they can read it out you see here for instance a an added traffic sign on the 14th of March it was inspected the second of March and then they after in the traffic sign database it's added on the 14th of March and you see it's fixed traffic sign start of motorway and the maximum speed limit is 120 kilometers an hour so the TNATS service translates the data to the Rosetta specs and you can see it right here we also have data x2 data x2 via the verkeersentrum.be we have some data x2 data and lean totes all everything is put on reopened so okay you can find it mobility transport of lands the verkeers bottom flanders so you can see the locations of the traffic signs or the derived speed limits when you use our open data link or VMS you can also check out the derived speedway zones or the other zone 30 or zone 50 and all the other ones so that's my demo about 50 minutes 20 minutes perhaps so over to the questions the first question is will other makers also be involved for instance google maps ways open street map we already talked to ways and yeah their view point was that they find their input from the community very important so they they know that our data exists but they as far as we know we they are not really using it because they think their own information is from the best quality how they deal with varying data quality yeah that that is an important point and we try to deal with it to by giving them access to the dates so the date of last of the inspection on terrain and also the date of the last edit and also they only get the updates that are done so they don't really need to take into account all the the old data so they only get the changes the updates and we we think that these updates are are always yeah better than the old data yes even it's in fact yeah it's a tndt service but it was before effectively the rosette specs yeah the crowdsource data that is something we we want to look into but for our process with our applications that the bottleneck is the the vehicle for the flaner application because in moving you can do these inspections you can say what is wrong on terrain but someone has to go over all these inspections to really make the changes in the database so if we would make moving publicly available the the people at the local authorities would have a very large list of inspections to cover but we we want yeah to take this into account and try to to look at how we we can solve that but it's a very interesting thing to look at yeah of course i'm seeing the last question properly steven yeah so currently we have no contacts with the brussels or waloon um authorities uh we have tried a number of times reaching out to them and so well the bottom line is that there is not always the possibility to um work on setting up tndt service for many different reasons it could be that the priority is on dynamic data it could often there is an issue on resources often there is an issue on source data and tools bottom line is we yeah it's it has not realized or materialized and we're of course very welcome um to explain tn it as to them to brussels and and waloon authorities to educate them to convince them of the of the benefits that setting of these services has for the authorities themselves that's important and of course the benefits for for their citizens um it's it's a pity but i would also say it's not um unique to the belgium situation we have in europe other regions where the responsibilities uh and the i should say commitments are are diverse only in a few countries especially in the nordics you have like these kind of unique federal road administrations and that's a one-stop shop and that's of course the ideal situation is if you think about germany the responsibility is distributed over um provinces or bundeslander as they're called and there it's very difficult to um introduce tn it is on that level um there is now i understand in germany a federal organization that's been put into place for the highest road classes motorways and we hope that we will cooperate with them in the future to set up this type of data exchange um also the situation is problematic in in france and in italy for the rest i mean typically the smaller the country is the easier it is to um to to get things moving okay are there any questions left i i think we covered them all and maybe i can come back on tim's question on how to how do map makers deal with varying data quality um i've worked for one of the leading map makers for almost 20 years so i'm well positioned to um to give an answer on that so typically there is like a um a system in place that um evaluates different sources of changes either from floating car data from authoritative data such as tn ites from other type of gis data from active user input people complaining like okay the speed limit for my road is completely wrong uh let's put it on 50 so that happens so there is a system in place which um assigns values to different input streams and as it is now authoritative data such as tn ites can trump other types of data so just kind of a trumping mechanism in place and finally um depending on certain thresholds or whether certain thresholds are met or not met an automatic update is generated and the map is updated if a certain threshold of confidence is not met then it goes to a manual review stream and then operators evaluate what is the best source to rely on to um to make an update if there is a decision that i mean the input information is not of sufficient quality then that can be um um fed back to the the provider either a person actively submitting a change request or the authorities as i've mentioned before for floating car data of course that that doesn't work and you cannot send back an observation from a car that that's that chain is not is not implemented and that's also the interesting thing about the feedback loop i think that we can give feedback from the map makers to the the authorities for example so that is something we really want to look into so currently um in pilot phase we have provided so we the map makers have provided feedback related to successful matches of location references or unsuccessful matches that's that's probably the most important feedback information on mid and longer term this feedback can also act as a way to inform authorities of changes on on the network that is observed from an other source than what is you know what they mentioned as a potential change but that's part of the um you know ongoing discussion with the mapping industry and authorities in europe okay okay are there more questions or maybe we can conclude this session i don't see any questions coming in so i suggest that we conclude the session as lean said i want to thank you lean and stefan for this session um and i will end the recording now but i will keep the room open for two more minutes if there are maybe um any questions coming up in the chat good morning everyone and