Skip to content
Benjamin Stévens edited this page Apr 24, 2014 · 13 revisions

Welcome to the IMS wiki!

Formats supported

Format name Vendor Extension Multiple files Tool use to read Converted
JPEG N.A. jpg, jpeg NO Image Magick VIPS YES
PNG N.A. png NO Image Magick VIPS YES
TIFF N.A. tiff, tif NO Image Magick VIPS YES
BMP N.A. bmp NO Image Magick VIPS YES
PGM N.A. pgm NO Image Magick VIPS YES
VMS Hamamatsu vms YES Openslide NO
NDPI Hamamatsu ndpi NO Openslide NO
SVS Aperio svs NO Openslide NO
SVSLIDE Sakura svslide NO Openslide NO
MRXS Mirax mrxs YES Openslide NO
SCN Leica scn NO Openslide NO
Roche TIFF Roche tiff NO Image Magick VIPS YES

Formats unsupported

  • DICOM (part 145)
  • Zeiss ZVI
  • Philipps (extension ?)

Upload & deployment process

Note :

  • If a image is composed of multiple files, they must be zipped before the upload. One image per zip.
  • A zip may contains multiple image which are composed of single files

Process :

  1. File is uploaded to NGINX the passed to IMS upload service.
  2. For each image uploaded, IMS create an instance of UploadedImage which contains some informations (the path of the files, the target storages, the user, ...).
  3. A service check the format of the UploadedFile.
  • The service copy all the file into the right storage directory.
  • If this is an archive file (like ZIP), the service unzip all the files and return an array of UploadedFile.
  • If the image format require a conversion to be compatible with IIP Image Server, the service convert the file, create a new UploadedFile instance an return it.
  • Finally, the service create an AbstractImage into the Cytomine database, with the final UploadedFile instance.
Clone this wiki locally