Hi Jonathan,
Even if I remove the -elve.default parameter, still reports the same error.
And it takes me many hours..
Is it possibly you could help to take a look at my dataset in this Drobpox
<https://www.dropbox.com/sh/jhfk64oh14ae8eh/AAB_iXLNxRtZXWoRRR--V94oa> (
https://www.dropbox.com/sh/jhfk64oh14ae8eh/AAB_iXLNxRtZXWoRRR--V94oa)?
./otbcli_StereoFramework -input.il /..../Pleiades_Subset_759.tif
/.../Pleiades_Subset_771.tif -output.out ../../Test_Pan_759_771_DSM.tif
-elev.dem /.../DEM_london -elev.geoid /.../egm96.grd
or
./otbcli_StereoFramework -input.il /..../Pleiades_Subset_759.tif
/.../Pleiades_Subset_771.tif -output.out ../../Test_Pan_759_771_DSM.tif
-elev.dem /.../DEM_london -elev.geoid /.../egm96.grd *-bm.minhoffset 20
-bm.maxhoffset 20 *
2014 Aug 13 10:13:12 : Application.logger (INFO) Elevation management:
setting default height above ellipsoid to 0 meters
2014 Aug 13 10:13:12 : Application.logger (INFO) Elevation management:
using geoid file (/home/qczeng/StereoMatching/SubsetPleaides/egm96.grd)
2014 Aug 13 10:13:12 : Application.logger (INFO) Elevation management:
using DEM directory (/home/qczeng/StereoMatching/SubsetPleaides/DEM_london)
2014 Aug 13 10:13:12 : Application.logger (INFO) 1 Stereo couples will
be processed
2014 Aug 13 10:13:12 : Application.logger (INFO) Processing stereo
couple 0 (images index 0 and 1)
Computing epipolar grids...: 0% [
Computing epipolar grids...: 2% [*
Computing epipolar grids...: 4% [**
Computing epipolar grids...: 6% [***
....
Computing epipolar grids...: 100%
[**************************************************] (2e+02 seconds)
2014 Aug 13 10:15:45 : Application.logger (INFO) Minimum disparity :
*-2.27105e+06*
2014 Aug 13 10:15:45 : Application.logger (INFO) Maximum disparity :
*2.27105e+06*
Inverting left displacement field ...: 0% [
Inverting left displacement field ...: 9% [****
Inverting left displacement field ...: 19% [*********
...
Inverting left displacement field ...: 100%
[**************************************************] (0.7 seconds)
2014 Aug 13 10:15:45 : Application.logger (INFO) Using robust SSD Metric
for BlockMatching.
2014 Aug 13 10:15:45 : Application.logger (INFO) Using reverse
block-matching to filter incoherent disparity values.
Estimating min/max elevation...: 0% [
Estimating min/max elevation...: 2% [*
Estimating min/max elevation...: 4% [**
...
Estimating min/max elevation...: 100%
[**************************************************] (1e+04 seconds)
2014 Aug 13 14:12:16 : Application.logger (INFO) Minimum elevation found
: 0
2014 Aug 13 14:12:16 : Application.logger (INFO) Maximum elevation found
: 0
2014 Aug 13 14:12:16 : Application.logger (INFO) Disparity mask formula
: if((hdisp > -2.27105e+06) and (hdisp < 2.27105e+06) and (mask>0),255,0)
2014 Aug 13 14:12:16 : Application.logger (INFO) Output DSM parameters
are estimated from sensor input data.
2014 Aug 13 14:12:16 : Application.logger (INFO) Output DSM projection
reference:
GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS
84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]]
Writing ../../Test_Pan_759_771_DSM.tif...: 0% [
]2014 Aug 13 14:12:17 : Application.logger (FATAL)
The following error occurred during application execution :
/home/qczeng/StereoMatching/OTB/Code/IO/otbGDALImageIO.cxx:1416:
itk::ERROR: GDALImageIO(0x7d67d0): Dimensions are not defined.
Inconsistency detected by ld.so: dl-close.c: 762: _dl_close: Assertion
`map->l_init_called' failed!
On Wednesday, August 13, 2014 3:43:40 AM UTC-4, Jonathan Guinet wrote:
>
> Hi Chris,
>
> there is something wrong witj your input elevetation parameters :
> -elev.default
> 272 -elev.dem /.../DEM_Directory -elev.geoid /.../egm96.grd
>
> you should use either elev.default to set elevation to default value , or
> eleve.dem and elev.geoid to handle DEM,
>
> Jonathan
>
>
>
> 2014-08-13 5:29 GMT+02:00 Chris <[email protected] <javascript:>>:
>
>> 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]>:
>>>
>>>> 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]
>>>>
>>>> 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.
>>>>
>>>
>>> --
>> --
>> 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.
