AWS 2-8: Global Watershed Delineation Back-end #3662
+117
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The full dataset is too big for local development. This subset is of a 200 mile radius circle centered on Philadelphia.
The actual SQL query is very fast, but we still wrap it in a Celery job so that it is logged and recorded, and is consistent with the other APIs. In case no matching basins are found, the returning feature would have a None geometry. For details on this algorithm, please see: https://github.com/WikiWatershed/global-hydrography/?tab=readme-ov-file#modified-nested-set-index
An error occurred while trying to automatically change base from
tt/3660/fix-rwd-in-conus
to
develop
November 22, 2024 15:44
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Adds development data for TDX Basins, used for global watershed delineation. This subset is 200 miles around Philadelphia.
This also adds URLs, Views, Tasks, and Calcs to allow for delineation. The actual algorithm uses the nested set index developed in https://github.com/WikiWatershed/global-hydrography/?tab=readme-ov-file#modified-nested-set-index.
Even though this is highly performant, enough to be a synchronous response, we still use the async job workflow for two reasons:
Closes #3658
Demo
When the watershed resulting from the default point is loaded in QGIS, it looks like this:
Testing Instructions
vagrant upvagrant ssh app -c 'cd /vagrant && ./scripts/aws/setupdb.sh -B'global-watershedsAPI endpoint, using the default values