You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/filespec.rst
+120Lines changed: 120 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -276,3 +276,123 @@ The other columns in the overflow coverage pixel are filled with the default sen
276
276
277
277
If the sparse map is a bit-packed mask, the schema is the same as for a regular sparse map image.
278
278
In this case, as with the FITS serialization, the sparse map is stored as an array of unsigned 8-bit integers which is the in-memory backing of the bit-packed array.
279
+
280
+
.. _hdf5_format:
281
+
282
+
HealSparseMap HDF5 Serialization
283
+
================================
284
+
285
+
A :code:`HealSparseMap` may also be serialized to an HDF5 file.
286
+
Multiple :code:`HealSparseMap` objects can be stored in the same HDF5 file.
287
+
Each :code:`HealSparseMap` is stored in a different HDF5 group.
288
+
They are not required to have the same mask, :code:`nside_coverage`, or :code:`nside_sparse`.
289
+
290
+
All datasets are written with gzip compression and chunked such that each chunk corresponds to a single coverage pixel.
291
+
292
+
HDF5 Group Layout
293
+
-----------------
294
+
295
+
A serialized :code:`HealSparseMap` is stored within a single HDF5 group (default name :code:`"map"`), which contains:
296
+
297
+
* A dataset encoding the coverage map
298
+
* One or more datasets encoding the sparse map
299
+
* Attributes storing map metadata
300
+
301
+
Coverage Map
302
+
------------
303
+
304
+
The coverage map is stored as a one-dimensional dataset:
0 commit comments