addition - One can merge the split images into one image using for example otbcli_TileFusion. However, this function does not take care for creating a unified geom file - if so, how you maintain the sensor information which is located in the XML?
On Wednesday, June 28, 2017 at 11:33:31 AM UTC+3, Ofer Zilberstein wrote: > > > I saw some discussion and workaround about this back is 2014, and I bring > it back ... > > large Pleiades image is supplied as a multi-image (large image broken into > non-overlapping tiles). > > For example - the XML file > *RPC_PHR1A_PMS_201609270827376_SEN_2033167101-001.XML* describe image > that is devided into 2 tiles: > *IMG_PHR1A_PMS_201609270827376_SEN_2033167101-001_R1C1.JP2* > *IMG_PHR1A_PMS_201609270827376_SEN_2033167101-001_R2C1.JP2* > > It is expected that application that supports Pleiades format will read > the image using the above XML and not the separated images... > > Unfortunately, it is not the case with OTB command file. I just tried > *otbcli_ReadImageInfo, *but I understand that it is the same with other > commands as well. > > Note - Erdas-Imagine-Photogrammetry read the image parts using the > above XML. > > Is there a way to overcome this issue? Or I do something wrong ... > > Best regards... > > Ofer > > -- -- 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.
