spacemap 0.1.15 → 0.1.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -47,7 +47,7 @@ your page:
47
47
  ```html
48
48
  <div id="map" style="height: 500px"></div>
49
49
  <script type="module">
50
- import { createMap } from 'https://cdn.jsdelivr.net/npm/spacemap@0.1.15/dist/spacemap.js';
50
+ import { createMap } from 'https://cdn.jsdelivr.net/npm/spacemap@0.1.16/dist/spacemap.js';
51
51
  const map = await createMap({ container: '#map' });
52
52
  </script>
53
53
  ```
@@ -662,6 +662,22 @@ A `system` is named by its primary and measured in the primary's radii. A body
662
662
  with no moons has no system map, and asking for one rejects, leaving the map as
663
663
  it was.
664
664
 
665
+ A ringed primary's rings are a band across every ring there is, out to the
666
+ faintest dust: Saturn's runs past Mimas, Enceladus, Tethys and Dione to the
667
+ E ring. `rings: 'visible'` spans only the rings `createMap` shows, at the cost
668
+ of the primary's bundle and its ring profiles:
669
+
670
+ ```js
671
+ createSystemMap({
672
+ container: '#picker',
673
+ view: { kind: 'system', id: 'naif-699' },
674
+ rings: 'visible'
675
+ });
676
+ ```
677
+
678
+ Jupiter's and Neptune's rings are too faint to see, so their systems then have
679
+ no band.
680
+
665
681
  **A click reports what was picked and goes nowhere.** Walking down into a
666
682
  system and back up is the page's own doing, which is what lets it keep a back
667
683
  button, a breadcrumb or a URL of its own: