UGAtlas final sign off list

[akahure]

Issues discovered from final QA from UGATlas

• Remove classification of legend and give only one symbol
  • Markets
  • Trading centers
• - Remove all poverty indicators from the fill layer
• - Change the indicator to a number in the map like the legend, currently, it appears as a percentage
• - Please add population number next to the refugee settlement name like shown in red
  
• [x ] - All Indicators in Health below TB/TSR in the drop-down have inconsistent legends in the bar chart. E.g when PCV3 is selected, the legend in the bar chart shows ANC4 impact where it should show PCV3

[Janemesi]

@akahure Kindly clarify:

1. Remove classification of legend and give only one symbol This means that we will also remove the categories from the filter section? When they zoom in, they will only see markets/trading centres for a specific district/sub region with the count of the sites as a pop up?
2. Remove all poverty indicators from the fill layer Please provide the name of the layers
3. Change the indicator to a number in the map like the legend, currently, it appears as a percentage Please share sample case scenarios
4. Point 4 and 5 are to be done by an engineer because both charts are code generated.

[kahummer]

@ukanga @akahure
Seem's the engineering task here is Adding the value to the chat. I'd give it half-day in case anything comes up from data side too

[akahure]

@Janemesi

1. Yes, this is correct. the only place they can view the different markets will be via filtering and a breakdown on the summaries per district
2. Poverty layers
   
3. Sorry forgot to include it - Fresh stillbirths in health (FSB)
   
4. @kahama94 kindly look into 4 and 5
5. @Janemesi one more thing can you look into this legend - it does not make sense to have 0-0
   

[Janemesi]

@akahure This might take 3/4 of a day @kahummer I'll need help on point 2 because I do not have access to the map explorer

[kahummer]

I've pushed changes for 2 and the map explorer change. I think the other issues can be handled from the data side
Here are the changes


@akahure Should I proceed to deploy or wait for all the changes then deploy?