Closed gubuntu closed 5 years ago
@NyakudyaA if you can't get it to work with modified regions then revert it to a working condition and put your suggestions in upstream tickets.
e.g. I searched for 'manica' under regions and got 0 results yet there are several layers that are in or intersect with manica
I did not assign the metadata keywords to the districts and sub-districts because it would have taken me a long time to do that and look at which layer intersects which. In fact, the majority of the layers are of national coverage. If a user smaller datasets then they can allocate the regions to the smallest unit
OK...but the metadata wizard is still not loading as per OP - can you fix that?
I have fixed this for now. I have opened a ticket upstream. This issue turns out was caused by the characters used in the Portuguese language. I had to change the encoding to PGCLIENTENCODING=UTF8
I have created an issue upstream with how metadata regions should be handled
@gubuntu cc @boney-bun I think this is caused by the metadata regions which I deleted. Geonode does not handle metadata regions properly and this causes it to not load everything.
Here is a sample layer that I have loaded for Mozambique in testing. If you look at the default metadata regions assigned to it.![metadata-regions](https://user-images.githubusercontent.com/2510900/47990839-3ffbb200-e0f1-11e8-8028-37f1eccbc147.png)
Just because I deleted some of the regions now Geonode still looks for them and fails to find them and this affects the metadata region.
I suggest the following.
Fix the way metadata regions are allocated to layers in Geonode.
Global
-Continent
-Region
-Country
-Provinces
(If a user has added them) -District
until we get the smallest unit defined by a user.Global
-Continent
-Region
-Country
and a user can add other smaller units if he has defined them