From: Laymon, Marc A (Research) <laymon@cr...> - 2003-11-26 20:02:27
I am porting code from TargetJr for reading NITF images. Since the imaging
is somewhat different between TargetJr and VXL, I wanted to check and see if
had suggestions for dealing with large images like are encountered with NITF
(300-600MB) before I just ported the TargetJr code over verbatim.
One approach that was used by TargetJr. was to use pyramid image files,
where some kind of hierarchy of images with decreasing resolution is
Any other suggestions ?
Secondly, I am the point where I can read the NITF image file headers,
create a vil_image_resource
(using an NITF specific sub-class I wrote) and get a vil_image_view from
reading the pixel bytes.
Any image under 100MB displays fine. (I just modified the example in the
on how to display images using vgui_image_tableau, vgui_viewer2D_tableau,
and vgui::run to use my own vil_image_view.) However, for any image where
the actual number of bytes
in the displayed image is over 100MB, vgui:run generates a segmentation
I have traced this down to the call to glutMainLoop inside static function
vgui_glut_impl.cxx. Before I try to look into the GLUT code, has anyone
else run into this limitation ?
GE Global Research
Get latest updates about Open Source Projects, Conferences and News.