Thank you for the support
I made a report on the issues list.

Cyril Bernard

Le vendredi 5 mai 2017 11:48:45 UTC+2, Julien Michel a écrit :
>
> Thanks for sharing, I could indeed reproduce the problem. For some 
> reason OSSIM does parse the DIMAP XML file correctly. Can you file a bug 
> report at bugs.orfeo-toolbox.org ? In the mean time we will investigate 
> the issue, and hopefully get a fix for 6.0. 
>
> Regards, 
>
> Julien 
>
> Le 04/05/2017 à 16:23, Julien Michel a écrit : 
> > Hi, 
> > 
> > Any way you could share your data with us so that we can investigate 
> > this ? We are in the midle of producing OTB 6.0 so it is time for 
> > bugfixes. 
> > 
> > Regards, 
> > 
> > Julien 
> > 
> > Le 04/05/2017 à 16:09, 'CBernard' via otb-users a écrit : 
> >> Hello, 
> >> 
> >> I have a similar problem with recent (2017) Pleiades data but it is 
> >> not a software version problem for me. 
> >> 
> >> Several months ago, I applied the workflow (optical calibration, 
> >> orthorectification) on Pleiades 2016 scenes around Montpellier, and 
> >> it worked. 
> >> 
> >> My laboratory bought Pleiades 2017 scenes for the same place, and it 
> >> does not work anymore - with 5.8.0 version and 5.10.1 version as well. 
> >> 
> >> 
> >> I checked the metadata with ReadImageInfo : 
> >> 
> >> otbcli_ReadImageInfo -in 
> >> "Input\IMG_PHR1B_MS_201703141059586_SEN_2270315101-002_R1C1.TIF" 
> >> -keywordlist 1 
> >> 
> >> OTB does not find "sensor :" information in metadata in my newest 
> >> data; all the information about "support_data.*" keywords have 
> >> dissappeared too. 
> >> 
> >> 
> >> And yet, there is a 
> >> DIM_PHR1B_MS_201703141059586_SEN_2270315101-002.xml and a 
> >> RPC_PHR1B_MS_201703141059586_SEN_2270315101-002.xml files with the TIF. 
> >> And everything seem normal in it ! 
> >> 
> >> Any ideas ? 
> >> 
> >> 
> >> Cyril BERNARD 
> >> CEFE-CNRS 
> >> 
> >> 
> >> 
> >> 
> >> Le vendredi 21 avril 2017 09:00:25 UTC+2, Julien Michel a écrit : 
> >> 
> >>     Hi, 
> >> 
> >>     Can you file a bugreport on bugs.orfeo-toolbox.org 
> >>     <http://bugs.orfeo-toolbox.org> ? It needs to be 
> >>     investigated before the 6.0 release. 
> >> 
> >>     Thanks, 
> >> 
> >>     Julien 
> >> 
> >>     Le 20/04/2017 à 17:32, William Ouellette a écrit : 
> >>     > 
> >>     > Hi, 
> >>     > 
> >>     > I am trying to run a typical otbcli_OpticalCalibration, 
> >>     > otbcli_BundleToPerfectSensor, otbcli_Orthorectification on level 
> 1 
> >>     > pléiades data (non-georeferenced). 
> >>     > Since 5.10, I get a sensor unknown, which did not happen with 5.8 
> >>     > which I had used in the past to perform those operations without 
> >>     issues. 
> >>     > It seems that the metadata file (DIM xml) is being bypassed. 
> >>     > 
> >>     > This is the message I get from all of the above utilities when 
> >>     trying 
> >>     > to perform them on my pleiades geotiff data: 
> >>     > 
> >>     > 2017 Apr 20 15:26:13  :  Application.logger  (INFO) 
> >>     > File: 
> >>     > 
> >> 
> /home/s_admin/TPP1600600643/IMG_PHR1B_P_001/IMG_PHR1B_P_201609271052073_SEN_2254102101-001_R1C1.TIF
>  
>
> >> 
> >>     > Sensor unknown! 
> >>     > Additional parameters are necessary, please provide them (cf. 
> >>     > documentation)! 
> >>     > 
> >>     > There seems to be nothing wrong with the metadata file which is 
> >>     > located in the same folder. 
> >>     > 
> >>     > Thanks for your help. 
> >>     > 
> >>     > Cheers, 
> >>     > 
> >>     > William 
> >>     > -- 
> >>     > -- 
> >>     > Check the OTB FAQ at 
> >>     > http://www.orfeo-toolbox.org/FAQ.html 
> >>     <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 
> >>     <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:> 
> >>     > <mailto:[email protected] <javascript:>>. 
> >>     > For more options, visit https://groups.google.com/d/optout 
> >>     <https://groups.google.com/d/optout>. 
> >> 
> >> 
> >>     --     Julien MICHEL 
> >>     CNES - DSO/SI/2A 
> >> 
> >> -- 
> >> -- 
> >> 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:> 
> >> <mailto:[email protected] <javascript:>>. 
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
>
>
> -- 
> Julien MICHEL 
> CNES - DSO/SI/2A 
>
>

-- 
-- 
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.

Reply via email to