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
Currently OpenJPH supports full image frame decoding. This works great for standard image sizes but does not work for very large size images (e.g. > 10,000 width x 10,000 height) as is found in Digital Pathology and satellite imaging. For these large images, the ability to extract a region of interest (ROI) is required to access the full resolution data without exhausting memory (and using unnecessary compute). This functionality is also a requirement to support JPIP. JPIP window rendering functionality would be a good source of requirements for the ROI rendering API (e.g. how to specify the ROI, resolution, quality)
Note this functionality would also require being able to support sparse cacheing/reading of HTJ2K bitstreams to minimize memory use. This could be done by reading from the file itself directly or over the network via JPIP or HTTP Byte streams
The text was updated successfully, but these errors were encountered:
Currently OpenJPH supports full image frame decoding. This works great for standard image sizes but does not work for very large size images (e.g. > 10,000 width x 10,000 height) as is found in Digital Pathology and satellite imaging. For these large images, the ability to extract a region of interest (ROI) is required to access the full resolution data without exhausting memory (and using unnecessary compute). This functionality is also a requirement to support JPIP. JPIP window rendering functionality would be a good source of requirements for the ROI rendering API (e.g. how to specify the ROI, resolution, quality)
Note this functionality would also require being able to support sparse cacheing/reading of HTJ2K bitstreams to minimize memory use. This could be done by reading from the file itself directly or over the network via JPIP or HTTP Byte streams
The text was updated successfully, but these errors were encountered: