Eswatini Droughtmap Hub
-
Clone and Install GeoNode You can either clone this default repository or use the GeoNode Project repository to generate a customized GeoNode.
git clone https://github.com/akvo/geonode-project.git cd geonode
-
Set Up Local Environment Install the necessary dependencies (Docker is the recommended approach for ease of setup):
docker-compose up -d
-
Set Environment Variables Update your
.env
file or export the following environment variables:export GEONODE_BASE_URL="http://<your_ip_address>" export GEONODE_ADMIN_USERNAME="<your_admin_username_or_email>" export GEONODE_ADMIN_PASSWORD="<your_admin_password>"
Replace
<your_ip_address>
,<your_admin_username_or_email>
, and<your_admin_password>
with your desired values. -
Access GeoNode Open GeoNode in your browser at
http://<your_ip_address>
and log in using the admin credentials. -
Add a New Dataset Category
- Navigate to Admin Panel → Base → Metadata Topic Categories → Add topic category.
PATH URL: /[locale]/admin/base/topiccategory/add/
- Fill in the details as follows:
- Identifier:
cdi-raster-map
- Description [en]:
CDI Raster Map
- Identifier:
- Save the category.
-
Set Environment Variables In the Eswatini Droughtmap Hub project, update your environment variables file to include:
GEONODE_BASE_URL="http://<your_ip_address>" GEONODE_ADMIN_USERNAME="<your_admin_username_or_email>" GEONODE_ADMIN_PASSWORD="<your_admin_password>"
-
Restart the Droughtmap Hub Restart the application to apply the updated environment variables.
-
Upload a Dataset to GeoNode
- Log in to GeoNode as an admin.
- Upload a TIFF or GeoJSON dataset.
- Set its category to
cdi-raster-map
.
-
Verify in Eswatini Droughtmap Hub
- Log in to the Droughtmap Hub as an admin.
- Navigate to
/publications
. - If configured correctly, the list of datasets from GeoNode should appear, allowing you to start a new publication.
-
Troubleshooting
- If no datasets are visible:
- Double-check the environment variable values in the Droughtmap Hub.
- Verify that GeoNode is accessible and the dataset category is correctly assigned.
- Open a new issue in the relevant repository if the problem persists.
- If no datasets are visible: