# Add a parallel compression method to NRRD and/or MetaImage?

**URL:** https://discourse.itk.org/t/add-a-parallel-compression-method-to-nrrd-and-or-metaimage/696
**Category:** Engineering
**Created:** [February 21, 2018, 4:33pm UTC](https://discourse.itk.org/t/add-a-parallel-compression-method-to-nrrd-and-or-metaimage/696 "2018-02-21T16:33:03Z")
**Posts on this page:** 1
**Showing post:** 28

<div class="post-metadata">

### Author: ![neurolabusc](https://discourse.itk.org/user_avatar/discourse.itk.org/neurolabusc/32/735_2.png) [@neurolabusc](https://discourse.itk.org/u/neurolabusc)
#### Post date: [January 15, 2019, 4:11pm UTC](https://discourse.itk.org/t/add-a-parallel-compression-method-to-nrrd-and-or-metaimage/696/28 "2019-01-15T16:11:10Z")

</div>

I think this thread is related to this other [issue](https://github.com/InsightSoftwareConsortium/ITK/issues/348). Since I support NRRD without using your code, I would ask that these changes become part of the formal NRRD specification and are done with full awareness that they will break compatibility with older tools. This may well be worth it - zstd is very fast and is gaining widespread traction. However, using pigz would provide faster compression without breaking compatibility and pre-filtered zstd (e.g. blosc) might be much better suited for the nature of NRRD data than pure zstd.

---

_[View the full topic](https://discourse.itk.org/t/add-a-parallel-compression-method-to-nrrd-and-or-metaimage/696)._
