Hi,
Is your data really in the UTM 31 N zone ?
Do you have any log during execution ?
The rpc option should not be used for Pleiades data (which already has
RPC modelling).
Also, some things might speed up the process :
-io.out
"/export/lw01/pleiades/FCGC600116002/IMG_PHR1A_MS_002/IMG_PHR1A_MS_201312171058461_ORT10_777505101-002_R1C1c.tif?&gdal:co:TILED=YES"
uint16
TILED=YES writes tiles instead of strips, and will therefore be less
intensive for reading the JP2 file (which is tiled). uint16 will save
you half the size of the file (default is float) and therefore half the
bandwidth of the hard-drive.
If you want even smaller files, you can add &gdal:co:NBITS=12 which will
save another 25% (since pleiades images are 12 bits).
Regards,
Julien
Le 31/08/2015 14:03, Julien Radoux a écrit :
Thank you for your message. here is the last command line (version
4.3.0) I used
/usr/local/engebin/OTB/otbcli_OrthoRectification -io.in
"/export/lw01/pleiades/FCGC600116002/IMG_PHR1A_MS_002/IMG_PHR1A_MS_201312171058461_SEN_777505101-002_R1C1.JP2?&skipcarto=true"
-io.out
/export/lw01/pleiades/FCGC600116002/IMG_PHR1A_MS_002/IMG_PHR1A_MS_201312171058461_ORT10_777505101-002_R1C1c.tif
-map utm -map.utm.zone 31 -outputs.spacingx 2 -outputs.spacingy -2
-elev.dem /export/lw01/DEM/ -opt.ram 4000
I tried with and without the "skipcarto", with a constant height
instead of SRTM, with EPSG:31370 instead of UTM 31 N, but the results
are always inaccurate. I expected a shift because the SRTM resolution
is too coarse, but not as large (the processing time with a full
resolution DSM is too long to run some tests.)
the DIM file seems to be recognized, because I have an error message
when I rename it.
Here is the result of otbcli_ReadImageInfo
Image general informations:
Number of bands : 4
Start index : [0,0]
Size : [8795,16932]
Origin : [0.5,0.5]
Spacing : [1,1]
Estimated ground spacing (in meters): [2.20824,2.1049]
Image acquisition informations:
Sensor : PHR 1A
Image identification number: 777505101-002
Acquisition time : 2013-12-17T10:58:00
Country : Belgium
Town : Freylange
Image footprint coordinates:
Upper left corner (latitude, longitude) = [49.8598,5.64303]
Upper right corner (latitude, longitude) = [49.8536,5.91126]
Lower left corner (latitude, longitude) = [49.5404,5.64257]
Lower right corner (latitude, longitude) = [49.5316,5.91146]
Image default RGB composition:
[R, G, B] = [0,1,2]
Ground control points information:
Number of GCPs = 0
GCPs projection =
Output parameters value:
indexx: 0
indexy: 0
sizex: 8795
sizey: 16932
spacingx: 1
spacingy: 1
originx: 0.5
originy: 0.5
estimatedgroundspacingx: 2.20824337
estimatedgroundspacingy: 2.104904652
numberbands: 4
sensor: PHR 1A
id: 777505101-002
time: 2013-12-17T10:58:00
ullat: 49.85978317
ullon: 5.643033028
urlat: 49.85359573
urlon: 5.911261082
lrlat: 49.53157806
lrlon: 5.911462307
lllat: 49.54036331
lllon: 5.642566681
town: Freylange
country: Belgium
rgb.r: 0
rgb.g: 1
rgb.b: 2
projectionref:
keyword:
gcp.count: 0
gcp.proj:
gcp.ids:
gcp.info:
gcp.imcoord:
gcp.geocoord:
And this is for gdalinfo
Size is 8795, 16932
Coordinate System is `'
Origin = (0.500000000000000,-0.500000000000000)
Pixel Size = (1.000000000000000,-1.000000000000000)
Image Structure Metadata:
INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left ( 0.5000000, -0.5000000)
Lower Left ( 0.500, -16932.500)
Upper Right ( 8795.500, -0.500)
Lower Right ( 8795.500, -16932.500)
Center ( 4398.000, -8466.500)
Band 1 Block=2048x2048 Type=UInt16, ColorInterp=Red
Overviews: 4397x8466, 2198x4233, 1099x2116, 549x1058, 274x529
Overviews: arbitrary
Image Structure Metadata:
NBITS=12
Band 2 Block=2048x2048 Type=UInt16, ColorInterp=Green
Overviews: 4397x8466, 2198x4233, 1099x2116, 549x1058, 274x529
Overviews: arbitrary
Image Structure Metadata:
NBITS=12
Band 3 Block=2048x2048 Type=UInt16, ColorInterp=Blue
Overviews: 4397x8466, 2198x4233, 1099x2116, 549x1058, 274x529
Overviews: arbitrary
Image Structure Metadata:
NBITS=12
Band 4 Block=2048x2048 Type=UInt16, ColorInterp=Alpha
Overviews: 4397x8466, 2198x4233, 1099x2116, 549x1058, 274x529
Overviews: arbitrary
Image Structure Metadata:
NBITS=12
On Monday, August 31, 2015 at 11:37:19 AM UTC+2, Julien Radoux wrote:
I am trying to orthorectify Pleiades images with
otbcli_Orthorectification . The file is a JP2 with a DIM and a RPC
file in XML. I read from the doc that the ancillary files are
seamlessly used, but the results of the orthorectification are not
good (1 km error). Maybe do I not understand the use of the
-opt.rpc parameter ? What should I use there ?
--
--
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Julien MICHEL
CNES - DCT/SI/AP - BPI 1219
18, avenue Edouard Belin
31401 Toulouse Cedex 09 - France
Tel: +33 561 282 894 - Fax: +33 561 283 109
--
--
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.
