Repository navigation
feat(neptune): add a Voyager 2 map assembled from the 1989 approach frames - #1354
Merged
Merged
Conversation
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.
Neptune's Hubble map is soft because Hubble sees the planet only about 58 pixels wide. Neptune now has a Voyager 2 dataset: one color map assembled here from 89 NASA frames of August 1989, about three times finer on screen. Hubble 2025 stays the default. Uranus is unchanged; its ledger records why no sharper map exists. Bodies: Neptune, Uranus (ledger only). Details: Neptune README.
Limits: Chrome only. North of 34.8° N is gray grid. Clouds in unmatched bands take their band's mean color. 51 frames borrow the twist of the nearest recorded attitude.
neptuneonce, published to R2, inventory committed.Clean: map tests 12 of 12; observed-surfaces, runtime-contract, scene-contract and source-record tests; authoring typecheck; ESLint; hash, ledger, body-reference and ownership checks;
check-assets-published.PR rules: titles, PDS4 provenance and ISO plain language.