... We note that many of our tools could be repurposed as back ends for web applications
and APIs. This would enable our users to interact directly with our archived data products
before deciding which ones to download.
[G.4.1] Images are most amenable to this approach. Our own “picmaker” script reads PDS-labeled
data files and converts them to standard display formats such as JPEG or TIFF. It also provides
an enormous range of processing options, including zooming, grayscale-stretching, color
enhancement, and even filtering. It can operate on a single image or a long list. It is quite fast, so
it should provide a responsive user experience. We propose to build a web front end and an API
for picmaker. We will integrate it into our OPUS gallery view and also into our volume browser
interface. With a published API for such a tool, a user would also be able to bulk-process large
numbers of images and download the results.
The 2016 RMS PDS Proposal [G.4.1] states:
... We note that many of our tools could be repurposed as back ends for web applications and APIs. This would enable our users to interact directly with our archived data products before deciding which ones to download.
[G.4.1] Images are most amenable to this approach. Our own “picmaker” script reads PDS-labeled data files and converts them to standard display formats such as JPEG or TIFF. It also provides an enormous range of processing options, including zooming, grayscale-stretching, color enhancement, and even filtering. It can operate on a single image or a long list. It is quite fast, so it should provide a responsive user experience. We propose to build a web front end and an API for picmaker. We will integrate it into our OPUS gallery view and also into our volume browser interface. With a published API for such a tool, a user would also be able to bulk-process large numbers of images and download the results.