GPT not setting longitude as CYCLIC from ENVISAT files

Optical Toolbox
1

Hi

I have recently finished updating inherited legacy java code to use snap (11.0.0) rather than BEAM libraries. I have a remaining problem with data not wrapping correctly when the swath tracks across the dateline. I have traced this ultimately to the part of the chain where we use gpt to read ENVISAT style files (.E1 or .N1) and write them out in dimap format. Unlike beam, the snap library does not recognise that longitude is a cyclic variable so that the new dim file has an entry.

<Tie_Point_Grid_Info>

        <TIE_POINT_GRID_INDEX>1</TIE_POINT_GRID_INDEX>
        <TIE_POINT_DESCRIPTION>Longitudes</TIE_POINT_DESCRIPTION>
        <PHYSICAL_UNIT>deg</PHYSICAL_UNIT>
        <TIE_POINT_GRID_NAME>longitude</TIE_POINT_GRID_NAME>
        <DATA_TYPE>float32</DATA_TYPE>
        <NCOLS>23</NCOLS>
        <NROWS>558</NROWS>
        <OFFSET_X>-19.0</OFFSET_X>
        <OFFSET_Y>-0.0</OFFSET_Y>
        <STEP_X>25.0</STEP_X>
        <STEP_Y>32.0</STEP_Y>
        <CYCLIC discontinuity="0">false</CYCLIC>
</Tie_Point_Grid_Info>

I have manually edited this to test a fix for the problem and confirm that locations are now properly interpolated from the tie-point grid to the raster image if I set.

CYCLIC discontinuity=“180”>true

but it would be better for this to be set by the snap library function itself rather than have me adjust each output file to correct it. Thanks.