search

natcap / global-web-viewer

A web viewer prototype for visualizing and analyzing global data.
GNU General Public License v3.0
3 stars 1 forks source link

Inconsistencies with In-country regions #102

Closed newtpatrol closed 2 years ago

newtpatrol commented 2 years ago

For In-country region, I sometimes don't see the region names and outlines that correspond with what's shown in the pop-up. For example, in Slovenia, if I click on or search for Ljubljana, it zooms to the right place, but when I click on Ljubljana to get the service stats, the popup location is Osrednjeslovenska, not Ljubljana. But I don't see Osrednjeslovenska labeled on the map, nor can I search for it in the In-country Search box.

However, this works fine in the US, where states are shown, and per-state averages are shown in the service info pop-up. It also seems to work ok in Brazil. But then in Bolivia, the sub-national areas are not labeled (but they are delineated). This might be due to an inconsistency within GADM level 1? Trying in Uganda, it looks like the outlines don't correspond with the Region names (the outlines seem to be smaller/lower level). Also in Uganda, it's hard to tell the difference between towns and sub-national regions, since the font is very similar across many of their labels.

So there seems to sometimes be a mismatch between the sub-national regions that are shown, versus what we're providing stats for, and being able to search for.

dcdenu4 commented 2 years ago

This is a tough one. We are showing the Gadm1 outlines and boundaries as well as the basemap boundaries. Their overlap does make it unclear of what is "selectable" or not. I'm not sure the best way to help fix this visualization confusion. I guess we could highlight the gadm0, gadm1, hybrobasin boundaries in a pale yellow or something to differentiate them.

dcdenu4 commented 2 years ago

Admin search now only returns filtered results through what is available from GADM 1. Osrednjeslovenska is now searchable. Hopefully this helps clear up some of that confusion. There is still the confusion of showing the basemap boundary and the GADM 1 outline boundary. I think this is something that could more cleanly be addressed in the future, but it's not clear what the solution would be for this prototype. Closing this issue for now.