Conversation
m-mohr
force-pushed
the
dggs
branch
3 times, most recently
from
a607206 to
6f086a0
Compare
m-mohr
changed the title
m-mohr
force-pushed
the
dggs
branch
3 times, most recently
from
0381f81 to
0445607
Compare
This file contains hidden or 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
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.
I'm unsure whether we should merge mask and mask_dggs...
Revert the package.json change once the package has a new release that supports the new dimension type.
Disclaimer: I have no major experience with DGGS, this may not make sense. The processes were written based on what AI explained me about DGGS vs raster data cubes. :-)