API REST - JPEG request with loss

Hello,

I’m calling the URI below to get JPEG instance:
http://localhost:8042/wado?objectUID=1.3.51.0.7.3546887940.16340.17987.48017.20243.52433.6910&requestType=WADO

I’m calling the URI below to get DICOM instance:
wadouri://localhost:8042/wado?objectUID=1.3.51.0.7.3546887940.16340.17987.48017.20243.52433.6910&requestType=WADO&contentType=application/dicom

  1. Is this the right way?
  2. Testing JPEG with CR images (X-Rays) is too large, about 8 seconds to download, is there any way for orthanc to return lighter image (even with loss)?

My sincere prestige to Orthanc!

Thank you.

I'm calling the URI below to get JPEG instance:
http://localhost:8042/wado?objectUID=1.3.51.0.7.3546887940.16340.1798
7.48017.20243.52433.6910&requestType=WADO

I'm calling the URI below to get DICOM instance:
wadouri://localhost:8042/wado?objectUID=1.3.51.0.7.3546887940.16340.1
7987.48017.20243.52433.6910&requestType=WADO&contentType=application/
dicom

1) Is this the right way?

Yes, that sounds right. Don't forget to URL-encode values in the query string as necessary[0].

2) Testing JPEG with CR images (X-Rays) is too large, about 8 seconds
to download, is there any way for orthanc to return lighter image
(even with loss)?

AFAIK there is currently no way to configure the level of compression
used to generate lossy JPEG previews. If you want to optimize that
number you might have to set up more resources for the server. Do make
sure what the bottleneck is however (it is likely network throughput
but could also be backend storage I/O or even CPU since JPEG
compression isn't free).

0: Percent-encoding - Wikipedia

Hello Thibault,

Many thanks for the reply!
It helped me a lot to get ahead in use.

Thank you!