Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / geospatialresearch/digital-twins issues and pull requests
#169 - Linux PDAL warning
Issue -
State: open - Opened by LukeParky 7 months ago
Labels: back-end, A0 - Not Associated
#168 - Empty env variables with defaults do not use default
Issue -
State: closed - Opened by LukeParky 7 months ago
- 9 comments
Labels: bug, good first issue, back-end, AA - Non Functional
#167 - Selenium can't find element
Issue -
State: closed - Opened by LukeParky 7 months ago
- 2 comments
Labels: bug, back-end, AA - Non Functional
#166 - Switch to a newzealidar version that works on both Windows and Linux
Pull Request -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
#165 - Heartbeat logs are getting through to docker services
Issue -
State: open - Opened by LukeParky 8 months ago
Labels: bug, devops/ci/cd, back-end, A0 - Not Associated
#164 - Demo reality mesh capture in Cesium to investigate uses within DT
Issue -
State: closed - Opened by LukeParky 8 months ago
- 2 comments
Labels: front-end, check with project manager
#163 - Create backend API controls for MEDUSA
Issue -
State: closed - Opened by LukeParky 8 months ago
- 2 comments
Labels: enhancement, good first issue, blocked, back-end, A2 - Pollutant Modelling
#162 - Create front-end visualisation and controls for MEDUSA model
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
Labels: blocked, front-end, A2 - Pollutant Modelling
#161 - Write API spec for MEDUSA
Issue -
State: open - Opened by LukeParky 8 months ago
- 1 comment
Labels: documentation, A2 - Pollutant Modelling
#160 - Add medusa database outputs to geoserver
Issue -
State: closed - Opened by LukeParky 8 months ago
- 2 comments
Labels: enhancement, back-end, A2 - Pollutant Modelling
#159 - Add additional more strict python linting rules for documentation
Issue -
State: closed - Opened by LukeParky 8 months ago
- 3 comments
Labels: documentation, good first issue, devops/ci/cd, back-end, AA - Non Functional
#158 - Add MEDUSA 2.0 modelling core
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: enhancement, back-end, A2 - Pollutant Modelling
#157 - Update Scrapy to fix datasets issue
Pull Request -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
#156 - Learning task: Find which bridges cross which rivers
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
#155 - Front-end ability to toggle layers
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: question, front-end, A3 - Toggling Layers
#154 - Add a system to programatically retrieve all input names, and their valid values from the backend rest api
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
Labels: question, back-end, A2 - Pollutant Modelling
#153 - Epic: Upload layers to compare analyses
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: enhancement, front-end, check with project manager, security, EPIC, back-end, A7 - Upload Layers
#152 - Model pollutant contribution loads based on historical weather station data
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
Labels: wontfix, A0 - Not Associated
#151 - Epic: library of previously run scenarios
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
Labels: enhancement, wontfix, front-end, EPIC, back-end, A0 - Not Associated
#150 - Investigate pre-implemented MEDUSA model, and find out if it can be integrated into the DT
Issue -
State: closed - Opened by LukeParky 8 months ago
- 2 comments
Labels: question, check with project manager, A2 - Pollutant Modelling
#148 - View the input parameters used for a scenario run from the frontend
Issue -
State: closed - Opened by LukeParky 8 months ago
- 5 comments
Labels: front-end, A4 - Exporting
#147 - Export the input parameters used for a scenario run from the rest api
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: enhancement, back-end, A4 - Exporting
#146 - Epic: Add MEDUSA 2.0 pollutant model
Issue -
State: closed - Opened by LukeParky 8 months ago
- 2 comments
Labels: enhancement, front-end, EPIC, back-end, A2 - Pollutant Modelling
#145 - Add option to utilise S3 buckets as persistant storage as an alternative to the file-system
Issue -
State: open - Opened by LukeParky 8 months ago
Labels: enhancement, back-end, AA - Non Functional
#144 - Update Vue2 to Vue3 in visualisation website
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: front-end, AA - Non Functional
#143 - Rec data download
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
Labels: bug, documentation, AA - Non Functional
#142 - Automate deployment to RCC testing server
Issue -
State: closed - Opened by LukeParky 8 months ago
- 1 comment
Labels: devops/ci/cd, AA - Non Functional
#141 - Bug relating to instruction file mapping not working.
Issue -
State: closed - Opened by LukeParky 8 months ago
- 2 comments
Labels: bug
#140 - Ensure deployment documentation is 100% correct for all deployment strategies
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: documentation, devops/ci/cd, AA - Non Functional
#139 - Change NZLidar Dependency to a single branch approach, managed by GRI
Issue -
State: closed - Opened by LukeParky 8 months ago
Labels: back-end, AA - Non Functional
#138 - Pull Request for pollution model.
Pull Request -
State: closed - Opened by Flame1190 8 months ago
- 3 comments
#137 - Scrapy version specification
Pull Request -
State: closed - Opened by Flame1190 9 months ago
#136 - Add JOSS paper. Changes for 1.0 release
Pull Request -
State: closed - Opened by LukeParky 11 months ago
#135 - AWS S3 Bucket for FReDT
Pull Request -
State: closed - Opened by caseyli92 11 months ago
- 4 comments
#113 - Database for Network
Issue -
State: closed - Opened by caseyli92 over 1 year ago
- 3 comments
#110 - Add tests for `tide_slr` and `river` modules
Issue -
State: closed - Opened by caseyli92 over 1 year ago
- 2 comments
Labels: good first issue, testing, back-end
#103 - Add river module - REC1 and OSM data etc
Pull Request -
State: closed - Opened by caseyli92 over 1 year ago
#103 - Add river module - REC1 and OSM data etc
Pull Request -
State: closed - Opened by caseyli92 over 1 year ago
#102 - Add web servers to digital twin
Pull Request -
State: closed - Opened by LukeParky almost 2 years ago
#102 - Add web servers to digital twin
Pull Request -
State: closed - Opened by LukeParky almost 2 years ago
#101 - NETCDF->gtiff georeferencing issue, they do not get added to geoserver
Issue -
State: closed - Opened by LukeParky almost 2 years ago
- 3 comments
#101 - NETCDF->gtiff georeferencing issue, they do not get added to geoserver
Issue -
State: closed - Opened by LukeParky almost 2 years ago
- 3 comments
#100 - Add river module
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#100 - Add river module
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#99 - Complete and modify current tide and sea level rise codes
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#99 - Complete and modify current tide and sea level rise codes
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#98 - The `src/digitaltwin` module needs updating for fetching multiple datasets and improved functionality
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#98 - The `src/digitaltwin` module needs updating for fetching multiple datasets and improved functionality
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#97 - Complete and modify current tide and sea level rise codes
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#97 - Complete and modify current tide and sea level rise codes
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#96 - Review, restructure and refactor Tide and Sea Level Rise codes
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#96 - Review, restructure and refactor Tide and Sea Level Rise codes
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#95 - Review, restructure and refactor current Tide and Sea Level Rise codes
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#95 - Review, restructure and refactor current Tide and Sea Level Rise codes
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#94 - Add CRS to BG-Flood Model output
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#94 - Add CRS to BG-Flood Model output
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#93 - Add CRS to BG-Flood Model Output
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#93 - Add CRS to BG-Flood Model Output
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#92 - Use latest release of BG-Flood Model
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
- 1 comment
#92 - Use latest release of BG-Flood Model
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
- 1 comment
#91 - Rainfall Module Suggestions and Fixes
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#91 - Rainfall Module Suggestions and Fixes
Pull Request -
State: closed - Opened by caseyli92 almost 2 years ago
#90 - Consolidate all the Enum used in the rainfall module into a single script
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#90 - Consolidate all the Enum used in the rainfall module into a single script
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#89 - Modify the existing procedure for storing rainfall depth data in the database
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
- 1 comment
#89 - Modify the existing procedure for storing rainfall depth data in the database
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
- 1 comment
#88 - Avoid storing rainfall intensity data in the database
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#88 - Avoid storing rainfall intensity data in the database
Issue -
State: closed - Opened by caseyli92 almost 2 years ago
#87 - Update ReadMe for the 'dynamic_boundary_conditions' module
Issue -
State: closed - Opened by caseyli92 about 2 years ago
- 1 comment
#87 - Update ReadMe for the 'dynamic_boundary_conditions' module
Issue -
State: closed - Opened by caseyli92 about 2 years ago
- 1 comment
#86 - Update test_setup_environment.py to pass on local machines and not run in GitHub Actions
Pull Request -
State: closed - Opened by LukeParky about 2 years ago
- 1 comment
#85 - Spatially varying rainfall model input, Tests, etc
Pull Request -
State: closed - Opened by caseyli92 about 2 years ago
- 1 comment
#85 - Spatially varying rainfall model input, Tests, etc
Pull Request -
State: closed - Opened by caseyli92 about 2 years ago
- 1 comment
#84 - Spatially varying rain input for BG-Flood
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#84 - Spatially varying rain input for BG-Flood
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#83 - Further parametise inputs to BG_FLOOD/geofabrics, and version control input files for it.
Issue -
State: closed - Opened by LukeParky about 2 years ago
Labels: help wanted
#83 - Further parametise inputs to BG_FLOOD/geofabrics, and version control input files for it.
Issue -
State: closed - Opened by LukeParky about 2 years ago
Labels: help wanted
#82 - Add tests for the 'dynamic_boundary_conditions' module
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#82 - Add tests for the 'dynamic_boundary_conditions' module
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#81 - 79 paramatise inputs to the digital twin application wide
Pull Request -
State: closed - Opened by LukeParky about 2 years ago
#81 - 79 paramatise inputs to the digital twin application wide
Pull Request -
State: closed - Opened by LukeParky about 2 years ago
#80 - Spatially uniform rain input for BG-Flood
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#80 - Spatially uniform rain input for BG-Flood
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#79 - Paramatise inputs to the digital twin application-wide
Issue -
State: closed - Opened by LukeParky about 2 years ago
#79 - Paramatise inputs to the digital twin application-wide
Issue -
State: closed - Opened by LukeParky about 2 years ago
#78 - Add Thiessen Polygons
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#78 - Add Thiessen Polygons
Issue -
State: closed - Opened by caseyli92 about 2 years ago
#77 - Separate geometry from api links, to enhance security of API keys with GeoServer
Issue -
State: closed - Opened by LukeParky about 2 years ago
- 1 comment
Labels: security
#77 - Separate geometry from api links, to enhance security of API keys with GeoServer
Issue -
State: closed - Opened by LukeParky about 2 years ago
- 1 comment
Labels: security
#76 - Remove LiDAR and Tile Index tables
Issue -
State: closed - Opened by LukeParky about 2 years ago
- 4 comments
#76 - Remove LiDAR and Tile Index tables
Issue -
State: closed - Opened by LukeParky about 2 years ago
- 4 comments
#75 - fix Autodetect column names for LiDAR files #33
Pull Request -
State: closed - Opened by xandercai about 2 years ago
- 3 comments
#75 - fix Autodetect column names for LiDAR files #33
Pull Request -
State: closed - Opened by xandercai about 2 years ago
- 3 comments
#74 - #73 add lxml to fix compile error
Pull Request -
State: closed - Opened by xandercai about 2 years ago
#74 - #73 add lxml to fix compile error
Pull Request -
State: closed - Opened by xandercai about 2 years ago
#73 - Compile error when set up the Python environment using environment.yml
Issue -
State: closed - Opened by xandercai about 2 years ago
#73 - Compile error when set up the Python environment using environment.yml
Issue -
State: closed - Opened by xandercai about 2 years ago
#71 - #43 actions for add issue and pr to project.
Pull Request -
State: closed - Opened by xandercai about 2 years ago
- 2 comments
#71 - #43 actions for add issue and pr to project.
Pull Request -
State: closed - Opened by xandercai about 2 years ago
- 2 comments
#70 - 65 add geoserver to serve map data
Pull Request -
State: closed - Opened by LukeParky over 2 years ago