IMServer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[category:Connectome]] | [[category:Connectome]] | ||
== Why yo store data in image server == | |||
* Format neutral representation. A Standard API to view and manipulate the data at given resolution and given | |||
* Though it is possible to access any image with multiresolution, especially the formats liKE JPEG 2000 or ndpi, the processing takes time, and not always suitable for web server | |||
== Hosting an image server == | == Hosting an image server == | ||
Revision as of 17:25, 16 February 2011
Why yo store data in image server
- Format neutral representation. A Standard API to view and manipulate the data at given resolution and given
- Though it is possible to access any image with multiresolution, especially the formats liKE JPEG 2000 or ndpi, the processing takes time, and not always suitable for web server
Hosting an image server
Current dependencies to
- A database capable of storing binary objects
- A webserver currently Apache2
- Server side code to fetch images from database on demand
Adding large image set to the server
- | VTK
- VTKMicroscopy / VTKPers, libraries extending VTK (Developed at Kiware)
- 64bit C++ driver for MongoDB database
- An uploading script Implementation for dir_uploader
Using multiresolution data
Development of a browser based client
- The implementation can be better understood with demos
- Demo from Kitware network
- Demo from outside
- Viewer for Jeff's data
- Implementation of IMServer:WebClient
