BL for new sediment fingerprinting project #721
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
MattReimer
approved these changes
Jul 9, 2024
MattReimer
force-pushed
the
sediment-fingerprinting
branch
from
5124f0a to
c1120af
Compare
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.
Business logic for new sediment fingerprinting database.
Just one layer in the project.
I do reference a symbology file, but I have intentionally not created it yet. Patrick's web site shows a logical categorical symbology based on a small number of coarse categories. I cannot find the corresponding categories in the data and suspect that the map on this web site is manually curated.
I can't find any other convenient field with which to symbolize the data. Most fields in the database have dozens of distinct values that would be meaningless in the map.