Copyright © 2021-2026 Geospatial Research Institute Toi Hangarau
A template repository to be used to quickly start new EDDIE Digital Twin applications.
The following list defines the basic steps required to set up and run the digital twin.
We recommend basing your application on this template and modifying it to suit your needs. You can find a working example of an EDDIE application based on this template at our Flood Resilience Digital Twin repository.
- Windows 10/11
- Ubuntu 22.04
Note: Other Linux-based operating systems are likely to work but have not been as thoroughly tested.
We unfortunately do not support MacOS. Please see Digital-Twins#358 for updates or to contribute.
Create API keys for each of these services. You may need to create an account and log in
- Stats NZ API Key
- LINZ API Key
- MFE API Key
- NIWA Application API Key - Create an app that has the Tide API enabled.
- Cesium Ion Access Token
-
Clone this repository to your local machine.
-
Create a file called
api_keys.env, copy the contents ofapi_keys.env.templateand fill in the blank values with API credentials from the above links. -
Create a file called
.envin the project root, copy the contents of.env.templateand fill in all blank fields unless a comment says you can leave it blank. Blank fields to fill in include fields such asCESIUM_ACCESS_TOKENandPOSTGRES_PASSWORD.POSTGRES_PASSWORDcan be a password of your choosing. You may modify other configuration variables if needed to suit particular deployment environemnts. -
From project root, run the command
docker compose up -dto run the database, backend web servers, and helper services. -
You may inspect the logs of the backend using
docker compose logs -f backend celery_worker
- With the docker compose application running, the default web address is http://localhost:3001 to view the web
application.
- To perform custom modelling, "Explore map data" has configurable models.
- The API is available by default on http://localhost:5000. Visit https://geospatialresearch.github.io/Digital-Twins/swagger for API documentation.
If you are interested in contributing to this project, please see our contributing page here.
If you run into an issue, bug, or need help with the software, please consider opening an issue or discussion, this will be the best way to reach us.
Visit our wiki for some instructions on how to set up your development machine to work with on the FReDT project.