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
I've been exploring the capabilities of fo-dicom for medical imaging applications and have found it to be a robust tool.
However, I noticed that it currently lacks support for HTJPEG2000 compression. Given the growing adoption of HTJPEG2000 in medical imaging due to its superior compression efficiency and image quality, I believe adding support for this format would greatly enhance the versatility and usability of fo-dicom.
Could you please consider adding support for HTJPEG2000 compression in future releases of fo-dicom? This would enable us to efficiently store and transmit medical images while maintaining high fidelity and reducing storage requirements. I'm eager to hear your thoughts on this feature request and would appreciate any updates on its potential implementation.
The text was updated successfully, but these errors were encountered:
This is a duplicate of #1687. Note that while fo-dicom now supports this in principle (at least in the development branch), it relies on the codecs from Efferent Health (fo-dicom.Codecs), which does not support it yet.
I've been exploring the capabilities of fo-dicom for medical imaging applications and have found it to be a robust tool.
However, I noticed that it currently lacks support for HTJPEG2000 compression. Given the growing adoption of HTJPEG2000 in medical imaging due to its superior compression efficiency and image quality, I believe adding support for this format would greatly enhance the versatility and usability of fo-dicom.
Could you please consider adding support for HTJPEG2000 compression in future releases of fo-dicom? This would enable us to efficiently store and transmit medical images while maintaining high fidelity and reducing storage requirements. I'm eager to hear your thoughts on this feature request and would appreciate any updates on its potential implementation.
The text was updated successfully, but these errors were encountered: