 Note that this is the next version of 235 that will be released and it does have the bug that was introduced in 235.3, I believe, fixed there. If you're using 234 or below, this should work as well. But the demo instance, which does have this bug that causes an issue where the tracked entity layer appears to load for a very long time. Like this you can see here. So, let's go ahead and create this tracked entity layer. I'm going to remove this layer. I'm going to go ahead and click add layer, go to tracked entities, select a tracked entity type. In the demo instance we have malaria entity and the program malaria case diagnosis treatment and investigation. I am going to then also select display relationships so we can display tracked entity relationships from index case to cases. I'm going to go ahead and do that you see that there's also a case to focus relationship type, which would be between this program and another program which is malaria focus areas. But I'm going to use the index case to cases relationship type here. The index case doesn't really make a ton of sense necessarily in a malaria context but that this does show that you do have the ability to have relationships between different cases for epidemiology epidemiology investigation. I'm going to leave most of the rest of this the same except that I know that in this, this instance particularly there's no data in the last year. There's no data from 2019. So I will go ahead and move this back to other way. Move this back to April 2019. April 28, 2019. And this may be something that causes some issues for your, your, your own instance, but tracked entity data is at the lowest level so usually it's collected by the facility. And so it's only available at that facility. It's not available in an aggregate setting where you're at the visualizing Sierra Leone because no, there are no tracked entities in this data and at least that are collected with Sierra Leone as their org unit. In order to visualize all of the facilities and all of the data in all of Sierra Leone, I need to select the selected and all below option for arguments, which shows tracked entities in and all below Sierra Leone. So that means that all of the facilities in all of the Sierra Leone will be shown in this output. So I've selected 2019 to 2021 I've selected Sierra Leone and all its children or all the other org units in underneath it. I've selected the relationship type index case to cases, and I've selected malaria entity with the program malaria case diagnosis here. And I'm going to go ahead and add that layer. You can see that there, there is a little bit of data here there's not a lot, but you can see that you have a index case which is has a relationship with several subsequent cases. And you can see in the legend here that our index case is indicated with a red circle. So I'm going to go ahead again to indicate the relationship between that red circle and related cases, which are indicated as a small black dot. And the style tab for this layer you can also update the, the style of those points. So we can make the index case bigger. And I'm going to change the related entity style so right now it's black but I'm going to make that blue. And I'm going to change the point size to be the same so I'm going to make it 12 as well. And I'm going to change the line color to be red. So it's going to be a very colorful map that we're making here. So our index cases in green are related cases in blue or purple, and the line of the relationship between them in red. And you can take a picture of that if you wanted to. So this is just demonstration of the tracked entity layer. There is a bug in 235 latest patch, but the next patch that will be released in a few weeks I believe will be will have a fix for that bug. So it's just worth noting that this is a experimental feature for relationships, and you may not have the data available for it in your instances, but you can do that with the demo data on on plays on play when the this next patch comes up. Okay, I saw that there was a race and a couple questions I think it's time for a Q&A, and Bjorn did you want us to take over and start with the Q&A or did you did someone have a question that they wanted to raise down. I will just briefly before starting Q&A also mentioned a little bit about the earth engine layers. Take over. I see Tuzo has his hand raised. Tuzo if you can ask your question on the on the questions channel and slack. That would be good otherwise we'll we'll probably open it up for anyone to ask questions after Bjorn talks about the Google Earth engine layer in maybe 10 minutes or so. Okay. So Google Earth engine, which has not yet been covered. It has been around for a few releases so probably you also have access to these layers on your instance. I'll go back to 235 on the testing instance, workshop instance, and these layers are shown on this road. So they are not named Google Earth engine. They are just named by the topic it's more user friendly, but this layer are hosted by Google but provided by different organizations for free. It's greatly improved in 236, but you can still use them in earlier versions. So I've added some exercises that you can do on yourself, but I will just show you how you can do it. So one test is to see if Google Earth engine is enabled on the instance. And then I recommended you to try to add the elevation layer and just click add layer. If the layer loads, so you actually see some some elevation data coming here. It is enabled for instance, if not, you should talk to your system administrator. And ask them to the only thing is the set of process is to get some access permission from Google that you need to add to your instance. And this will be much, much more useful for when you upgrade to 236 when there are the capabilities are greatly improved. But what you can already do here and also part of the exercise is to check where you live. So to sort of zoom in, you can change to positive to this layer so you can also see the map below. And you can right click anywhere on this map and click elevation. And then you will see the elevation at that particular location. So here in Burundi, the place where I click is 16,000 1,600 meters above sea level. So you can try this yourself. Now I will move to the 236 that was released just two days ago. So it's available on our demo instance for 236. And what you can do here is that you can aggregate the data provided by Google Earth Engine to your own organization units and this is something we will look into in detail tomorrow. And then we will do it with a desktop program called QGIS. And the good thing we will do it there is that you don't need to upgrade to be able to do this exercise or to be able to use this data. So because I guess quite a few of you, you need to wait until you can upgrade instance 236. But then tomorrow we will show you another way to do the same. So for population, if you need to know the population within your org units, you could just add a population layer. You can select here how you want to aggregate it. Now I'm interested in the sum and then add layer. This will take a little bit more time to load because we now need to do this computation on the Google Earth Engine service and they can be quite intensive. But it will load. And then when you now click on one of your org units, you will see the estimated population within that org unit. And this is great if you have limited census data for your country. And of course, this data might not be is an estimate not not be correct, but tomorrow we will have this data set presented and and we will tell you the benefits and the shortcomings of these data sets here as well. You can drill down. And then we will load the next level the chief terms with the population inside. We can also open this data table here and see we can, for example, sort by population, we see that this district here has the highest population. And another improvement you can see here in this last latest release is that if you hover the table, we will highlight the org unit in the map so it's easy to see where it belongs. So we also got a special request for vaccination, COVID vaccination planning, and that is that often you would also like to know the age groups to within the different districts. So we also added a new layer with population age groups. You can select the age groups you would like to to use. So for example, if you would like to see the population about 80 years, you can select women about 80 and we could also select men. And then we use the same levels and add layer. So then this will only show the population about 80 years in each district. So we can see here that it's an estimated in the Mojamba district 680 to two people, about 80 years. And this can also be done for health facilities. So if I go back here, select organization unit, and instead of this street I select facilities and then in one, I will select Dharma in one of the chieftains. And then I can set a buffer. So I will still use this five kilometers buffer. What then will happen is that they will make these buffers and if you click them, you will see that in this hospital, there will be an estimated only 13 in this age group. Of course, these are estimates again, but we will look more into this tomorrow and you can see and check for your own country how accurate you think these numbers are. So we have an exercise for this. So the first one was the one I just mentioned with the elevation. So you can try yourself because also with it on the 236 you can check the highest elevation within your arguments. The last one I can show you which is a little bit different. That is the land cover data sets. So the question is what is the dominant land cover land use in one district. So if I go back to the maps app and I go new map, I will use this land cover. And then I will select an organization unit and select Western area and add layer. So this will also aggregate the data shown here. This is showing different land use so urban is red. So this is urban areas. So if I click on this, I will see that the most dominant land use or land cover in Western area is Savannah by almost 40%. So this is also now something you can do from 236 with your own country and organization units as these data sets are global. So that was a short demo. You can try this on your own afterwards. We will now look briefly at the questions. So I think I'll take this one over here. I saw that it was with some questions about the legends from Leslie. I had one question if you could create manual class divisions in thematic layers. So because we had have these automatic ones that are equal counts or equal intervals, and there are also other possibilities. There's something called natural breaks, for example, which sort of tries to read your data and, and make a best guess of, of how you should divide the classes. We also need some feedback for you if you would like to have more options than we have. If you want to set manual class divisions, you can't do that in the Maps app, but you can do it by creating a predefined legend. So I can just briefly show you where that is done. So if I go to the maintenance app, and then I can search for a legend. So here you have under other you have a legend entry where you can modify and create new legends. So I will just go and have a list view of these are all the legends on the demo instance that we have. And then so we, for example, see the weight in kilo, we can edit it. And here you can see that you can type in the start and end values as you like and basically create your own classes and you can also click on this and pick your own color. So here you have all flexibility of creating custom legends. And then if you are editing, and if I go back or editing an indicator. So I go back here. And if I'm editing an indicator, you will see that there is also a legend here so you can associate the legends that you would like to associate with with this indicator. I recommend only selecting one. And then this one will be selected by default in the map set to make it easier for your users. You see, so there was also a question if what happens if you drill down. Will the classes be the same. And I can show you that if I go back to the maps up. And then I'm adding a new layer. I use automatic color legend equal intervals for classes. Sorry, I went a little bit faster. And then if I then drill down you can see the classes here 53 starting from 53.9 146. And then if I drill down. It will be different. So I do see the need of the possibility of this legend to be the same. And you can achieve this by creating a predefined legends. The reason why we don't do this for automatic legends is that we don't know what the user will do. So, and we don't have all the data available when we create the legends. So that's why we need to adapt this when the user is is drilling up and down. So the way to fix this or find a way around it is to use a predefined legend. If you want them to stay the same. And then if you could change the colors and transparency of the buffers. I don't think you can. Our buffers support for different layers. But if we we use this for the facilities layer. So select facility type. Facility. And then turn on the buffer. So this will always have these blueish color. You can change the opacity by doing this, it will also change the opacity of the icon. If you would like to be able to change the color and maybe the opacity of only the buffer, please send us a feature request. And that is something we can can look into. If you have buffers for events. The event buffer will have the same color just brighter. With the same color as the event itself. Can you take over a bit Austin. Sure, I don't think there were a ton more questions but I saw two that came in that we could look at here. One is the most recent one what's the difference between the two options for period and tracked entity layer. And so beyond if I'm going to take over your screen. And I have this here. The question is about these two options in the period dialogue. When you're creating a tracked entity layer. So there are a number of different dates that we could be talking about when we're talking about events, particularly tracked entity events. So attract entity has an enrollment in a particular program. For instance, you might enroll a mother in the anti natal care program. You might enroll a person with a particular disease in the program for that disease. And the date when that person is added to that program or when they first visit a health facility in most cases is when they are enrolled in that program, which is this second option here. So we want to show, and all people that were enrolled in this in this case we're looking at malaria case diagnosis. So malaria entity, if we're showing the moment that that person was added to the malaria program, then we show the select the second option, and we can choose the dates that we care about. If we want to instead see the time the when that person or the tracked entity was last updated within this program, we can select this first option. And in that case, if someone is enrolled, for instance, in a malaria program, and then they are given anti malarial drugs at a later date, they might be enrolled on April the first. And then they're given a follow up visit on April the 15th, maybe the last updated to be the last time data was entered for that tracked entity or that person in that program, and that's when you would select this first option. So hopefully that makes that a little bit more clear. Any other questions here. There was another question which was quite good about using locations in data sets. Which is aggregate data that I believe is not currently supported in the maps application to visualize the data element from an aggregate program on the map. Bjorn, correct me if I'm wrong on that. I think that's correct. I think that's correct too. But if that is something that is useful and would be another good feature request that sounds like an interesting use case. You can of course collect that information in a tracker program, and then visualize it in that way, or or as anonymous events as well. So if you're collecting those in a data set in the data entry application, I believe there is not currently a way to visualize that on the map. There are some technical challenges in terms of how you determine what the geography associated with different values in that data element are. And that's not currently supported in DHS to I see there is one question about printing out a map. I'm not sure if I'm answering correctly, but I've not been covering that so I'll show you that in the maps up you can download we don't have a print option. But you can download the map. And then you have a few options here you can decide. It will be depending on the shape of your country where the which corner the legends should be. The name will only be shown if you have saved the map because then you actually add a name to it as well. And then you can click the download button. And if you click on this that will be just an image that you can print or use in your presentations or or whatever. This works so basically what you see on the screen is what you get in the print. So if you want a different ratio or a different view, you can just adapt what you see here. And whenever what you see when you click download is what you get downloaded. There was another question here in was asked in exercise for but it relates to something that was asked earlier as well. And that's about creating the the org unit geometries, which we did not cover today and maybe a little bit much to cover here in terms of what how you create that information. So that is something that would you would use the import export application to import a shape file or a geo JSON file for your boundaries of different levels different organization unit levels for your country so you might have boundaries for the operational level for the district level for the maybe the county level, and then also the points for individual facilities in your country, and you can import those into the DHS to system, not through the maps application that might be a little bit outside of scope for that today. So yeah, I agree and this is also so important that you have this in your on your instance because you can't use the maps without it or just very little of it. So I think what I would suggest here is you can contact us directly, we might also send out an email to this list and ask who are struggling with this part. And then I think we could have a separate workshop just for this group. Because it's not useful to have these all together because this is a one time task is only the system administrators who do it. But please give us some feedback if you would like us to have a separate workshop just on on adding coordinates to your audience. And we will help out. There was also a good response to that question so OSM which is the data source for the base maps is called it's an acronym for open street map. And you can anyone can suggest edits to that open street map data. It's not part of DHS to at all but you can contribute to open street map, I believe it's open street map dot org, that you can add or edit data if it is incorrect in that base map, and eventually it will show up also in the data that's coming into DHS2 system. But I would recommend if you're looking at targeting interventions or using things like county boundaries or facility locations in your DHS to in DHS to to target your health innovations or health interventions. And that you import that data directly to DHS to instead so that you can use it directly because otherwise it will just be kind of an image in the background of your system. I see that we get the suggestion to be able to support manual legends in the maps up and it's a good idea. So I will create a feature request for that and then we'll see you can you can load it up if it should be prioritized but it's something we can definitely add. I think it's also useful often in other GIS application you can see histogram which means you can see like a chart of of your distribution of your values and then how the classes will will affect that and I think that would also be a nice feature to have. And then we yes there has been quite a lot of things happening under the hood. In the database so there is a question now that the formats has changed. So the big change is that we have introduced something called post GIS, which is quite a long time ago. And then we have also switched so we are no longer storing coordinates in text fields that we did before, but in in the proper geometry fields, which have better control that they are correct that the latitude longitude is not out of about 180 and so on. So, and I think from the database directly you can export GML and CSV file but then you need database access, but you can download all your org units in do Jason format which is more used in GML, and that we will do tomorrow. That will be a big part of the of the program tomorrow. So, the presentation is shared in PDF. Is that okay. If not, I can also share it as a PowerPoint. I will do it here directly in the channel. Also, remember that we have a Q&A tomorrow at the same time so if you have more questions we can we also do tomorrow I know. And I'm sorry for that, but a few of you are hungry I saw there was a demand for for a lunch break. So we have this, they like this the three hours that this compulsory and then this part is is optional tomorrow we will do the same so please make sure you have a little bit food. Before we start tomorrow because we will run through the same program tomorrow. So lunch needs to be after we are done. So please keep some snack or something to keep you keep you going. I have a question about having to show data labels in the maps up so so far. We only show the names, and then you need to hover it to see the show the value so I think we could. We should improve that so you can also in, you can display the value directly on the map so it's not yet possible but it's I will I'm wondering if we should stop now and then if you have more questions please keep them for for tomorrow. Or do you have anything to add Austin. No, I haven't seen any major questions come up. I'm just want one thing to say about. I mentioned a couple times that people can create feature requests, they want to add something to do that you go to the DHS to Jira instance. So in order to do that you can go to DHS to dot org. There should be a link there to Jira, but you can also go directly to Jira jir a dot DHS to dot org maybe be on this if you have the shared map maybe you can share that. I can also share my screen. I'll stop sharing. So, as you can see here there is Jira dot DHS to dot org, you can then create an account or log in if you already have one. And you can create a new issue that you can bring up to us so if you create a new issue, you can select the, sorry, this will be the DHS to project is the one that is always here. Most people will only see this one I think you will then see the feature. You can have a description. The feature, you can select the maps application here, and then describe exactly in detail what what you want it and why. And also, if, once you've created this issue. You can also go to this the issue that is created here. And then you can also vote. So if you there is an issue that someone else has created you can search for it in using the search field. If there's an issue that someone else has created, or you know that other people would like the issue that you have created or the feature, you can vote for this as well. If you have created this this issue, I can't vote for it. But if more people vote, then we see it, and we know that it is something that a lot of people want. So that's something else that you can do. When you have created an issue or someone else has created an issue with a feature in Jira. Just wanted to point that out. I've shared now the presentation also in the questions thread. It is shared other places as well. And also remember that this is recorded and will be available on the YouTube channel. So if you missed some parts of the workshop today, you should be able to watch it later. So I don't suggest that we end here and meet again tomorrow. It's 10 o'clock our time so so thanks a lot for joining. You might still ask questions the slack slack will be open. So you can still ask questions here and we will try to reply or do it tomorrow. So, so I hope it was useful today and thank you for joining and then see you again. See you again tomorrow. Yep. Thank you all very much.