 Right, so now we are going to discuss about maps application. So maps application, the special thing about this maps application is we just have one maps application to do all types of analysis and we'll be looking at today how to use the event and the track-tentative layers of the maps application. So the objective is to describe the maps app as it relates to the tracker data and to describe the limitations of maps when working with tracker data and to create maps using tracker data within the event layer and the tracked entity layer. So in the maps app, I mean we all must have used if we have used DHS to at some point of time for analysis maps application is a very common application that most of us use. So when we interact with the tracker data in the maps application, we are actually dealing with three different layers. The first one is a thematic then events and the track-tentative layer. Unlike the event reports and event visualized applications, the maps app allows for visualization of both aggregate and tracker data. So both these components can be visualized within the single maps application. So let us now briefly look at each of the events, each of the layers that are available for us to analyze tracker data in the maps application. So the first one is the event layer. The event layer of course allows us to map the locations of an actual event as long as the coordinates is collected during the data entry. And working with tracker and event data in this layer is exactly the same. So when we are working with the event layer, both the tracker and event data works in the same way. And when it comes to the tracked entity layer, this is a separate layer, which is different to the event layer, this allows us to map the locations of tracked entity as long as it is collected during the registration. Here this layer also allows you to show relationships. So remember, tracked entity layer is the one that we are currently using to show relationship type of visualization. But again, this layer has some limitations that we will be discussing while we are doing the demonstration. And finally, we have the thematic layer. And this thematic layer allows us to map aggregate data in two forms. The first one is the program indicator. And the second is to aggregate, is the aggregate data elements within a tracker or event program. So both this will be able to visualize using the thematic layer. But we are not going to do this layer during the demonstration today. So let us now do the demo. So let me share my screen again. All right, so what I will do is I just open the tracker capture application. You click on apps and then go to the tracker capture. Not the maps. Don't ask me why I will show you why I want to show tracker capture first. Because I want to show you where we are capturing this coordinates because it is quite important to notice where we are capturing the coordinates for us to really understand what will be displayed when. So I click on tracker capture application. And this is where I land in the tracker capture. So I will just select refresh. Right, OK, so now I'm in the tracker capture application and I can select any of the programs. So for now I will select this case based surveillance program. And in that one, I'm going to click on the register button. So when I do that, you will see under this profile title here, you see point of map. So this is where we are capturing the coordinates of a tracked entity instant. So whenever we are using the track entity layer, the coordinates are coming from what we are capturing here. So in the web, we can actually enter directly or we can capture from the map itself. Or else in the Android, we have a separate way of capturing. So for the track entity layer, the locations are coming from what we capture here. Let me go back to the list wave again so that I can open up the code. And when I do that here, you will see inside the data into tab for each of the program stages, we have an option to capture coordinates here. So this is called event point. So whatever the coordinates captured here are the ones that will be analyzed when we are doing any visualizations using the event layer in the maps application. So this event point, it's very important to identify where the coordinates are coming from. So it is coming from the event point. And the next thing I want to show is that the relationships. So this relationship is an area again which is kind of under development. A lot of enhancements will be done in the DHS2 data model and the analysis component to do the relationship analytics. So here we have this tab here to add a relationship. So basically what we do is when we click on add, we will be able to select a type of relationship. So what we mean by a type of relationship is like we configure it separately. We are not going to cover configuration of relationships in this course, but when we have already configured a relationship, for example, right now we have two different relationships we have configured. First one is has been in contact with. Second one is person to person. So if we have defined a relationship like has been in contact with, right? It will let us select different persons from the program, right? We can search them, right? Who will be related to this particular patient that we have opened in this tracker dashboard? So for example, now this patient is a name test, right? With the same name case, it's just a test record. So we are defining here who are the persons this patient name test case has been in contact with, right? So here we have identified two people. The first one is the person test and the second one is Harry, right? So that ways we can define in the track entity dashboard the people who this index case has been in contact with, right? So these three concepts I wanted to show you before moving into the maps application. So let's now move to the maps. I click on the apps button here and select the maps, right? So in the maps, we'll be discussing again two different layers, mostly in this demonstration. So the first one is the event layer. The second one is the track entity layer. So I will be covering the track entity layer first, right? Which of course will be listed under exercise two in the learner's guide, right? So I'm changing the order slightly to start with the track entity and then we will move to the events. So let us now create a new map. So what I will do is now in this maps application let us see the interface first. So onto our left, we have a component where we can keep on adding layers. So these layers will be added on top of each, I mean existing layer. So right now the lowest layer will be automatically added which is the base map. So we can select whatever the different base map. So the standard is the OSM light, but we can select something else. For example, I can even select OSM detail, right? So based on that, this base map will be changing, right? And then we have the button to add layer and then onto our right side, we have two other tabs. The first one is the file which has few options like new, open, save, save as which is kind of similar to the standard options we had in the other analytics application. And then we also have the option to download. So let me add some layers. First I will add a layer. I will add a layer which is the organic layer as a boundary layer. So I'm going to select the organic layer here, right? And I will select the first one, right? The capital. And once I have done that, I click on add layer and what it will simply do is to add a boundary, right? Organization unit, right? You don't see anything here other than defining the boundary. Okay, right? So this is not really a tracker event analytics yet, but next I'm actually going to add a tractant layer to demonstrate this first concept. So what I'm going to do is to click on add layer and here I will select tract entities, right? This one. And then it'll ask me to select the tract entity type. So in the system, we currently have only one tract entity type defined, which is the person. I select that and it is asking select the program. So I'm going to select the program. We have three programs out of them. I'm going to select the case-based surveillance program, right? And then now see the interesting thing here, right? So it is not asking us to select the program stages, right? So remember in the tract entity layer in current, I mean as of what it is now in the maps application, we can't really analyze data that we are capturing in the program stages, right? That we will show you next in the event layer. So right now we are only considering about the individual tract entity instances or else the persons in this context, right? So here it is giving us options to select like persons who are in all persons or who are having active or completed or canceled enrollment. So right now I will just keep it as it is and select all, right? Who are enrolled to that? Dr. Paramot, can we select the two options within that I mean active and completed? It doesn't really make sense, Dr. Deepal because right now for a given enrollment in a program, you can, I mean, it can be either active or completed per person, for per program, right? So the person or a tract entity instance can have enrollment in a program which could be either active, completed or canceled. You can't have multiple statuses for a given enrollment. Having said that, if you have multiple enrollments, meaning like you may have had past enrollments, then that is different. But here for a given enrollment, you can only have one state. So that's why you are only having like that. So that's why, so but, so in your instance example, like I get what you are trying to say, but here the context is you are actually looking at a single enrollment which is having one possible state. But to incorporate all the tract entity instances because we are actually analyzing tract entity instances here and not really the enrollments, that's why we have the all options, right? But if you ideally want to look at enrollments, then we may have a requirement to have, you know, like to select more than one of them, but here the use case is slightly different. But probably this can be requested as a feature. The only use case I can think of is if you want to do an enrollment analytics of people who are having a completed or active and not a canceled, something like that, which is not so common. So that's why it is not there at the moment. But yeah, of course, we can request and see whether the core team will be able to incorporate something like that. Okay, so that's all what we can define in the data parameter. And then the next thing is relationships. So again, the big box warning, this is currently an experimental feature because I mean, a lot of improvements to the relationship analytics has been discussed right now, which is not really there. So here it is giving us the option to display the track-tended relationships, right? So it'll list out all the possible track-tended relationships that which are there. So right now what we have here are two, like has been in contact with and person to person. So I will select the first one has been in contact with, right? And then the period. So the period, of course, we can select like we can of course, select a period when track-tended is the last updated or the program enrollment date. So I will, what I will actually do is I will change the start date probably to 2022 January 1st. Yeah, and in date I will keep it as it is. And for the org units, we can select where we are displaying. So for this example, I will take this particular unit here, right? And then of course, we have another parameter called style. I'm not going to touch that, but just we can look at what is here. So it'll be showing track entities in the color with the color red, right? And when it comes to the relationships, the related entities will be shown with black color and the line connecting the index or the track entity that we are discussing now to the related entity will be highlighted in blue color, right? Okay, so let us click on add layer and see what we get, right? We do that and this is what we see. So we have our first layer. Now, can you see it is like we are adding on to existing layers. I'm focusing on the left side. So we have the base map here and then we have the org unit, the boundary layer, what we are seeing here. And then on top of that, we have the track entity layer. In the track entity layer, what we are seeing is these red ones. So I can just click here, see? Like this is one case that we have here, right? And these track entity instances are connected in this blue lines to the related track entity instances, right? So for example, all these highlighted in black are the related ones. So here we are only showing track entity instances. We haven't really discussed about the data. So now there are few drawbacks as of the current status of the app. For example, we can only create relationships and visualize entities within a single program. So supposedly, like if we have two programs, one tracking, one registering all the COVID patients and then we have a separate program for contact mapping and visualization, the mapping process and the contact tracing, then we can't kind of create this link between these two track entities, right? So that's one limitation, major limitation, which is currently there in this app, right? And also, we are not able to visualize any data, right? So this is only within the scope of track entities that we can do this visualization, right? So these are some limitations of this current application. And so as I mentioned before, relationship analytics is a major thing that is currently being discussed. So probably we can expect more and more features being added to the relationship application and to the relationships concept as well as the maps application in time to come, right? All right, so this is about the tracked entity layer. So please go to the maps section in Moodle and download the learner's guide and please do the exercise two, not one. The one is the event layer, which will be covering next, but you can do the exercise in the exercise two in the learner's guide. So probably we will give you around 10 minutes and then we will be coming back to start the events layer.