Biodiversity Significance Layer 3.0 #3374
Merged
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
edbrett
approved these changes
Apr 23, 2018
01painadam
added
_DEPLOY
and removed
WIP
|
Now ready for PROD! |
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
Oh boy, here I go updating Biodiversity layers again!
The new layer is possibly the greatest achievement in biodiversity layer visualisation. It's got new technology, implementing the RW-API layer hosting.
It's already being described as on, for production.
It also updates the layer to paint pixels only where forest data exists, deciding the significance of biodiversity in a region in a way that can satisfy any data scientist or researcher, at least. And indeed, at most.
Looking ahead to May, we can hope not to see any more updates to biodiversity metrics several times, and in various combinations.
Note
Please leave open and merge with staging. I will need to update the LayersNav if everyone is happy with this layer to go to prod.