IMServer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
|||
| Line 26: | Line 26: | ||
* The implementation can be better understood with [[IMServer:Demos demos]] | * The implementation can be better understood with [[IMServer:Demos | demos]] | ||
** Demo [http://dash1old/connectome/index2.php?image=z3459 from Kitware network] | ** Demo [http://dash1old/connectome/index2.php?image=z3459 from Kitware network] | ||
** Demo [http://tripoint.kitware.com/connectome/index2.php?image=z3459 from outside] | ** Demo [http://tripoint.kitware.com/connectome/index2.php?image=z3459 from outside] | ||
Revision as of 17:37, 5 April 2011
Why Image Server
- Format neutral representation. A Standard API to view and manipulate the data at desired extent and resolution
- 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 sevice
Hosting an image server
Current dependencies to
- A database capable of storing binary objects
- A webserver currently Apache2, if the data needs to be accessed remotely (note it is also possible to directly connect to a database remotely.
- 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
- The implementation can be better understood with demos
- Demo from Kitware network
- Demo from outside
- Viewer for Jeff's data
- Implementation of IMServer:WebClient
