-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New data interface ingest #46
Merged
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
States, and all other region types, now come with full context from the supercomputer.
* Refactor some code structure * Ingest in to WIP directories * Put everything in 3 more intuitive top-level `${STORAGE_DIR}` subdirs: `incoming`, `ingest-wip`, `live`.
* Update schemas for colormap/variables static files * Cleanup: * "cogs", "points", "plots" dir placeholders * "shapes" dir and all shapes inside (these will be sent from supercomputer, and there will be too many regions to reasonably store in a Git repo (unless LFS) * Migrate "legends" static data files to new static dir * Add new "variables.json" and "colormaps.json" static data files, these are probably the only pieces that will be static. There may be a couple more... * Add README to static dir
…c repo files Migrated tasks into their own module
Ruff's isort ruleset doesn't want to combine "as" imports and regular imports (even with `combine-as-imports` enabled). Maybe I need to upgrade?
nsidc-service-admin
force-pushed
the
new-region-ingest
branch
from
January 3, 2024 18:13
4d9e4e1
to
65972c8
Compare
nsidc-service-admin
force-pushed
the
new-region-ingest
branch
11 times, most recently
from
January 26, 2024 03:50
d0fff1d
to
4134bae
Compare
nsidc-service-admin
force-pushed
the
new-region-ingest
branch
from
January 26, 2024 03:56
4134bae
to
fa188cd
Compare
Openlayers' colorstops for some reason displayed the old representation as pure white instead of the desired grey.
Move colormaps in to dedicated "common" category.
Terminology is messed up so the code looks backwards, but `dataValueRange` is what comes in on regional data to tell us its coverage today. `variable.valueRange` tells us the expected extents of that variable's values.
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.
No description provided.