Hi Jonathan, Thank you for the reply.
If extracROI is the right way to crop the image, then why my entire image can be successfully matched, whereas the subset image extracted by " extractROI" cannot match? If the entire image and its subset share a same RPC file, but with different origins, then how OTB can recognize that the image has been changed? At least the *column/row OFFSET* need to be reset in the RPC? Can I alternative modify the RPC file and let OTB read the user-defined RPC file? I fail to do this, when I modify the "*RPC_###.xml*" comes with the entire image, and use it for the subset image, by: *otbcli_command "Subset_Image.tif?&RPC_user_defined.XML"* Thank you, Chris, On Tuesday, August 12, 2014 5:38:20 AM UTC-4, Jonathan Guinet wrote: > > Hi Chris, > > using extractROI on your sensor image affects the origin of the image, > thus the RPC model remains valid, (it can be easilly checkerd unsing > gdalinfo) > > Cheers, > > Jonathan > > > > > 2014-08-11 20:02 GMT+02:00 Chris <[email protected] <javascript:>>: > >> Hi, >> >> I have been attempted to use OTB stereo image matching since 2012, not >> got a chance to really let it work. And this time I involved in much more >> time and it seems on the right track now. >> >> I have previously post about OTB installation >> <https://groups.google.com/forum/#!searchin/otb-users/stereo$20framework/otb-users/wANoQ9oHhss/e-ZIQwpfnd0J> >> and stereo matching >> <https://groups.google.com/forum/#!profile/otb-users/APn2wQcDet7yykx6xh3fe498XOY19WsE1RahsL9BXiAXF1uKl8kubFdNmTygPJ0uJ1yemTMFJvwn/otb-users/kocntH7LjO8/lQfHi2maLQMJ> >> problems >> I have encountered. and I have checked some related post to my work, >> such as here >> <https://groups.google.com/forum/#!searchin/otb-users/stereo$20framework/otb-users/xEoAwafKjCQ/MYq0XcAtyRMJ> >> : >> >> I have a few issues: >> 1. >> I *can now successfully *match an entire tile of triple-view Pleiades >> image in about 2*10e4 seconds. Please see attached Overview for this DSM. >> Due to such a long computation time, I attempt to crop the image first >> then match a subset image. >> The entire Pleiades tile and subset image information, according to >> otbcli_ReadImageInfo, is given in the attached >> "Image_information_list.md". >> #image subsetting >> >> ./otbcli_ExtractROI -in /path/to/my/Pleiades/Pan/image/759.TIF -startx >> 1000 -starty 1000 -sizex 2000 -sizey 2000 -out >> ../../SubsetPleaides/Test_pan_759.tif >> ./otbcli_ExtractROI -in /path/to/my/Pleiades/Pan/image/771.TIF -startx >> 1000 -starty 1333 -sizex 2000 -sizey 2000 -out >> ../../SubsetPleaides/Test_pan_771.tif >> >> >> #stereo matching framework >> >> ./otbcli_StereoFramework -input.il "Test_pan_759.tif" >> "Test_pan_771.tif" -output.res 2 -output.out Test_Pan_759_771_DSM.tif >> -elev.default 272 -bm.maxhoffset 120 -bm.minhoffset -120 -bm.radius 3 -ram >> 6000 >> >> >> # report error: >> >> 2014 Aug 11 13:03:30 : Application.logger (INFO) Minimum disparity : >> *-1.36259e+07* >> 2014 Aug 11 13:03:30 : Application.logger (INFO) Maximum disparity : >> *1.36259e+07* >> ...... >> Writing Test_Pan_759_771_DSM.tif...: 0% [ >> ]otbApplicationLauncherCommandLine: >> /usr/include/ITK-4.5/itkImageConstIterator.h:208: void >> ...... >> Dimension: 2 >> Index: [-13625856, 1321] >> Size: [2123, 660] >> is *outside of buffered region *ImageRegion (0xd6dd20) >> >> >> Considering the entire tile can match successfully, there should be >> something wrong happens during the image crop using "otbcli_ExtractROI" >> I have included the "*.geom" files (for both original large tile, and the >> subset image) generated by OTB attached to this post. >> # the ".geom" of the entire tile is export through ReadImageInfo >> >> ./otbcli_ReadImageInfo -in /path/to/my/Pleiades/Pan/image/759.TIF >> -outkwl Entier_Pleiades_Tile_759.geom >> >> # the ".geom" of the subset image is generated automatically by >> >> ./otbcli_ExtractROI -in /path/to/my/Pleiades/Pan/image/759.TIF -startx >> 1000 -starty 1000 -sizex 2000 -sizey 2000 -out >> ../../SubsetPleaides/Subset_Pleiades_759.tif >> >> >> I already compared these two *.geom files, and I notice there are no >> significant changes. >> What is the correct method to subset an large satellite image for >> matching, preserving its RPC file? >> >> >> 2. What is the* supported RPC formats *for OTB in order load geometry >> information correctly? >> From a previous post it said RPC modules are inherited from OSSIM, and >> all popular satellite formats are supported, such as Worldview, GeoEye, etc. >> The XML file comes with Pleiades image works well, but user-defined XML >> after subsetting the Pleiades does not work any more, even if in the same >> file name and location. >> What happened underneath? >> >> -- >> -- >> Check the OTB FAQ at >> http://www.orfeo-toolbox.org/FAQ.html >> >> You received this message because you are subscribed to the Google >> Groups "otb-users" group. >> To post to this group, send email to [email protected] >> <javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/otb-users?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "otb-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- -- Check the OTB FAQ at http://www.orfeo-toolbox.org/FAQ.html You received this message because you are subscribed to the Google Groups "otb-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/otb-users?hl=en --- You received this message because you are subscribed to the Google Groups "otb-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
