Data

Tools

Indexes

Applications

Experiments

Open Source Science

digital-twins

https://github.com/geospatialresearch/digital-twins

Science Score: 36.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ○
    CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ○
    DOI references
  • ○
    Academic publication links
  • ✓
    Committers with academic emails
    1 of 17 committers (5.9%) from academic institutions
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (15.5%) to scientific vocabulary
Last synced: 6 months ago · JSON representation

Repository

Basic Info
Statistics
  • Stars: 19
  • Watchers: 4
  • Forks: 13
  • Open Issues: 29
  • Releases: 4
Created over 4 years ago · Last pushed 6 months ago
Metadata Files
Readme Contributing License

README.md

Copyright © 2021-2025 Geospatial Research Institute Toi Hangarau

Flood Resilience Digital Twin (FReDT)

image

Introduction

According to the National Emergency Management Agency, flooding is the greatest hazard in New Zealand, in terms of frequency, losses and civil defence emergencies. With major flood events occurring on average every 8 months (New Zealand – FloodList), it is necessary to produce high precision flood models and in order to do better planning, risk assessment and response to flood events.

The Flood Resilience Digital Twin can provide a better understanding of the degree of impact flood events can have on physical assets like buildings, roads, railways, transmission lines, etc. The digital twin not only represents the current status of the visualised assets but also how they will perform/react to future situations. The digital twin, when used to run flood models combined with other sources of information can allow us to make predictions.

Data for analysis and modelling are collected from open data portals provided by multiple organisations or data providers such as LINZ, StatsNZ, opentopography, NIWA, MFE, and more.

See our draft paper for Journal of Open Source Software for more details.

Basic running instructions

The following list defines the basic steps required to set up and run the digital twin.

Requirements

Officially Supported Operating Systems

  • Windows 10/11
  • Ubuntu 22.04

Note: Other Linux-based operating systems are likely to work but have not been as thoroughly tested.

Unsupported Operating Systems

We unfortunately do not support MacOS. Please see #358 for updates or to contribute.

Required Credentials:

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

Starting the Digital Twin application (localhost)

  1. Clone this repository to your local machine.

  2. Create a file called api_keys.env, copy the contents of api_keys.env.template and fill in the blank values with API credentials from the above links.

  3. Create a file called .env in the project root, copy the contents of .env.template and fill in all blank fields unless a comment says you can leave it blank. Blank fields to fill in include fields such as CESIUM_ACCESS_TOKEN and POSTGRES_PASSWORD. POSTGRES_PASSWORD can be a password of your choosing. You may modify other configuration variables if needed to suit particular deployment environemnts.

  4. From project root, run the command docker compose up -d to run the database, backend web servers, and helper services.

  5. You may inspect the logs of the backend using docker compose logs -f backend celery_worker

Using the Digital Twin application

  1. 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.
  2. The API is available by default on http://localhost:5000. Visit https://geospatialresearch.github.io/Digital-Twins/swagger for API documentation.

Contributing

If you are interested in contributing to this project, please see our contributing page here.

Support

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.

Setup for FReDT project software developers

Visit our wiki for some instructions on how to set up your development machine to work with on the FReDT project.

Owner

  • Name: Geospatial Research Institute | Toi Hangarau
  • Login: GeospatialResearch
  • Kind: organization
  • Email: gri-enquiries@canterbury.ac.nz
  • Location: New Zealand

GitHub Events

Total
  • Fork event: 5
  • Create event: 47
  • Release event: 2
  • Issues event: 97
  • Watch event: 4
  • Delete event: 55
  • Member event: 3
  • Issue comment event: 94
  • Push event: 241
  • Gollum event: 3
  • Pull request review event: 73
  • Pull request review comment event: 63
  • Pull request event: 81
Last Year
  • Fork event: 5
  • Create event: 47
  • Release event: 2
  • Issues event: 97
  • Watch event: 4
  • Delete event: 55
  • Member event: 3
  • Issue comment event: 94
  • Push event: 241
  • Gollum event: 3
  • Pull request review event: 73
  • Pull request review comment event: 63
  • Pull request event: 81

Committers

Last synced: 7 months ago

All Time
  • Total Commits: 2,293
  • Total Committers: 17
  • Avg Commits per committer: 134.882
  • Development Distribution Score (DDS): 0.42
Past Year
  • Commits: 236
  • Committers: 8
  • Avg Commits per committer: 29.5
  • Development Distribution Score (DDS): 0.369
Top Committers
Name Email Commits
Casey Li c****i@c****z 1,331
Luke Parkinson l****n@c****z 564
Pooja3894 8****4 139
Pooja Khosla p****a@c****z 123
Rose Pearson R****n@n****z 37
Flame1190 s****0@g****m 21
Xander Cai x****i@g****m 20
Martin Nguyen t****2@u****z 14
Martin Nguyen m****4@g****m 13
GRI Admin 1****n 13
Luke Parkinson l****n 8
Angus L a****8@u****z 3
Alistair McIntyre g****t@a****z 2
anirudh1117 a****7@g****m 2
anirudh a****h@U****g 1
Alistair McIntyre a****r@o****z 1
Pooja3894 8****4 1
Committer Domains (Top 20 + Academic)
canterbury.ac.nz: 3 uclive.ac.nz: 2 openplan.co.nz: 1 ultra-ubuntu-vm.myguest.virtualbox.org: 1 alistair.nz: 1 niwa.co.nz: 1

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 181
  • Total pull requests: 151
  • Average time to close issues: 5 months
  • Average time to close pull requests: 28 days
  • Total issue authors: 11
  • Total pull request authors: 12
  • Average comments per issue: 0.91
  • Average comments per pull request: 0.87
  • Merged pull requests: 117
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 66
  • Pull requests: 68
  • Average time to close issues: 29 days
  • Average time to close pull requests: 3 days
  • Issue authors: 5
  • Pull request authors: 5
  • Average comments per issue: 0.62
  • Average comments per pull request: 0.26
  • Merged pull requests: 54
  • Bot issues: 0
  • Bot pull requests: 0
View more stats
Top Authors
Issue Authors
  • LukeParky (133)
  • caseyli92 (30)
  • rosepearson (8)
  • changliao1025 (4)
  • Flame1190 (2)
  • MatthewDWilson (2)
  • Pooja3894 (2)
  • Martin20494 (2)
  • pritamd47 (1)
  • GRI-Admin (1)
  • xandercai (1)
Pull Request Authors
  • LukeParky (130)
  • caseyli92 (43)
  • Martin20494 (28)
  • Pooja3894 (11)
  • GRI-Admin (10)
  • Flame1190 (6)
  • alistairjmcintyre (5)
  • xandercai (3)
  • rosepearson (2)
  • 0xkon1 (2)
  • anirudh1117 (2)
  • prasannav98 (1)
  • jjm148 (1)
  • A-Load-Of-c0de (1)
Top Labels
Issue Labels
back-end (29) bug (27) front-end (23) devops/ci/cd (13) A0 - Not Associated (12) enhancement (11) A2 - Pollutant Modelling (11) documentation (10) good first issue (10) check with project manager (9) A6 - Usability (8) AA - Non Functional (8) wontfix (8) security (7) question (6) testing (5) help wanted (4) visualisation (4) blocked (4) EPIC (4) A3 - Toggling Layers (3) A4 - Exporting (3) duplicate (1) A7 - Upload Layers (1) A5 - User Auth (1)
Pull Request Labels
check with project manager (2) documentation (2) front-end (2) back-end (2) blocked (1)

Packages

  • Total packages: 2
  • Total downloads: unknown
  • Total dependent packages: 0
    (may contain duplicates)
  • Total dependent repositories: 0
    (may contain duplicates)
  • Total versions: 8
proxy.golang.org: github.com/GeospatialResearch/Digital-Twins
  • Versions: 4
  • Dependent Packages: 0
  • Dependent Repositories: 0
Rankings
Dependent packages count: 5.4%
Average: 5.6%
Dependent repos count: 5.8%
Last synced: 6 months ago
proxy.golang.org: github.com/geospatialresearch/digital-twins
  • Versions: 4
  • Dependent Packages: 0
  • Dependent Repositories: 0
Rankings
Dependent packages count: 5.4%
Average: 5.6%
Dependent repos count: 5.8%
Last synced: 6 months ago

Dependencies

.github/workflows/add-issue-to-project.yml actions
  • actions/add-to-project v0.4.0 composite
.github/workflows/blocking-issues.yml actions
  • Levi-Lesches/blocking-issues v2 composite
.github/workflows/run-tests.yml actions
  • SonarSource/sonarcloud-github-action master composite
  • actions/cache v2 composite
  • actions/checkout v2 composite
  • conda-incubator/setup-miniconda v2 composite
Dockerfile docker
  • continuumio/miniconda3 latest build
docker-compose.yml docker
  • postgis/postgis latest
.github/workflows/build-documentation.yml actions
  • actions/checkout v2 composite
visualisation/Dockerfile docker
  • nginx stable build
  • node lts-slim build
visualisation/package-lock.json npm
  • 1635 dependencies
visualisation/package.json npm
  • @typescript-eslint/eslint-plugin ^4.18.0 development
  • @typescript-eslint/parser ^4.18.0 development
  • @vue/cli-plugin-babel ~4.5.0 development
  • @vue/cli-plugin-eslint ~4.5.0 development
  • @vue/cli-plugin-typescript ~4.5.0 development
  • @vue/cli-service ~4.5.0 development
  • @vue/eslint-config-standard ^5.1.2 development
  • @vue/eslint-config-typescript ^7.0.0 development
  • eslint ^6.7.2 development
  • eslint-plugin-import ^2.20.2 development
  • eslint-plugin-node ^11.1.0 development
  • eslint-plugin-promise ^4.2.1 development
  • eslint-plugin-standard ^4.0.0 development
  • eslint-plugin-vue ^6.2.2 development
  • raw-loader ^4.0.2 development
  • typescript ~4.1.5 development
  • vue-template-compiler ^2.6.11 development
  • axios ^0.21.4
  • bootstrap-vue ^2.22.0
  • core-js ^3.6.5
  • geo-visualisation-components 0.0.5-alpha
  • vue ^2.6.11
  • vue-router ^3.6.0
environment.yml pypi
  • celery ==5.2.7
  • geovoronoi ==0.4.0
  • gunicorn ==20.1.0
sphinx/requirements.txt pypi
  • sphinx-autoapi *
  • sphinx_rtd_theme *