X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 26 Apr 2018 02:14 PM by  Grant Pearse
Sentinel-2 XML Error
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

Grant Pearse



New Member


Posts:1
New Member


--
25 Apr 2018 04:48 PM
    Hi,

    I am aware of the previous issues opening long filenames or opening Sentinel-2 L1/L2 images in older versions of ENVI but the issue seems to have cropped up again with the latest version of ENVI in combination with the latest outputs from Sen2Cor.

    I processed some L1C images to L2A using Sen2Cor 2.5 and attempted to open them using ENVI 5.5 from the XML file. Immediately after the first 'Reading Sentinel 2' dialog box I get a second dialog box saying 'ENVI Error: IMAGEINFO.'
    The files are in the latest PSD format direct from SciHub and opening the L1C products (same root folder) from the XML file works fine so probably not a path length or PSD version issue.
    This is unexpected as ENVI should be able to open L1 and L2 from the documentation - can you investigate this behavior? Hopefully there is a workaround by manipulating the XML data.

    Many thanks,
    Grant

    MariM



    Veteran Member


    Posts:2396
    Veteran Member


    --
    26 Apr 2018 10:58 AM
    XML files are parsed in ENVI based on the tags in them and when tags change, it breaks the reader. We have recently received reports on this behavior and have opened a bug report on this issue with Sentinel L2 data products. We do not have a work around at this moment but the jp2k files can be opened individually.

    Grant Pearse



    New Member


    Posts:1
    New Member


    --
    26 Apr 2018 02:14 PM
    Thanks for opening the issue. Here are some more details to help make it reproducable:
    Sen2Cor - Standalone Windows x64: Version: 2.5.5
    Input Sentinel-2 product: Type L1C; Product version: 14.5; Processing baseline 02.06
    ENVI 5.5 Rev. 347767 Build 1/22/2018 - Windows x64

    Thanks.
    Grant
    You are not authorized to post a reply.