DHIS2 GEE App and GEE Data Importer App are 2 web apps that enable end-users and administrator to easily inject Google Earth Engine data in their DHIS2 instances. Both apps share the same backend but have different front-end.
DHIS2 GEE App is the one prepared for administrators. They will be able to configure the GEE Dataset to extract the data from, to map it with any dataset in DHIS2, transform the extracted data on-the-fly and to download as a json the desired data.
DHIS2 GEE Data Importer App is a the end-user interface for a clean and extremely easy import process. This secondary app aims to ease the process of importing data from GEE without caring about mapping and variables, which will have been configured by the administrators using the DHIS2 GEE App.
These apps require the installation of a Google key in DHIS2, in order to connect to Google Earth Engine service.
DHIS2 GEE App and Data Importer App can:
Create mappings between Google Earth Engine datasets and DHIS2 datasets
Import GEE data into DHIS2
Configure GEE datasets to be used per Organisation Unit for end-users to easily import data from them without the need of mapping variables
We are announcing the new release version 1.0.1 of DHIS2 Google Earth Engine app.
Hi @Scott. I can prepare you a quick demo docker to run it locally in your machine if you install the d2-docker utility that we announced here.
Otherwise, it could be installed very quickly in play.dhis2.org, as I see you already have the google key in that instance (https://play.dhis2.org/2.34.1/api/tokens/google) and the app is using the token that DHIS2 exposes via the API. You only need a very simple dataset with a dataElement to test it, let’s say, to import rainfall data from ERA5 daily dataset in Google Earth.
However, let me know if you prefer me to do the demo in a quick videocall. Maybe that’s even simpler.
Can you confirm the functionality of the GEE App on currently (2.37+) versions of DHIS2? I’m running into an inability to pull information, but not sure if its a backend or a version issue that is causing it. Thanks!
Just to keep track of it so the community is also aware. The GEE app is at this moment having its mapping functionality broken due to a radical change in the GEE API. We don’t have at this moment the use-case in any of our direct clients to fix it, so unless somebody backs the development of that fix or we find some spare time in the team, at this moment the app is not fully working (the user would have to map it directly through the datastore which is not very intuitive or functional).
In the event that somebody reading this wants to use the app to map any data in GEE with agg data elements in DHIS2, and has financial resources to back it, please don’t hesitate in contacting us by DM. Likewise, this is an opensource project and can be contributed so if someone is happy to take the relay and develop the fix, we will be very happy to accept contributions in the code.