WKT problems in subset operator

Hi all,

I was using the Graph Builder and noticed several curiosities regarding the subset operator.

  1. When drawing a bounding box within the map preview to define an area of interest for the subset, the WKT polygon inside the input field only updates if Imove one of the nodes inside the graph section.

  2. The WKT polygon contains the last lon/lat coordinate pair twice. See image below.

If I save the graph as XML, it contains the same WKT polygon with duplicated last coordinate pair:

 <node id="Subset">
    <operator>Subset</operator>
    <sources>
      <sourceProduct refid="Read"/>
    </sources>
    <parameters class="com.bc.ceres.binding.dom.XppDomElement">
      <sourceBands>B2,B3,B8</sourceBands>
      <region>0,0,0,0</region>
      <referenceBand>B2</referenceBand>
      <geoRegion>POLYGON ((6.2885541915893555 51.32944107055664, 6.6484246253967285 51.32944107055664, 6.6484246253967285 51.035003662109375, 6.2885541915893555 51.035003662109375, 6.2885541915893555 51.32944107055664, 6.2885541915893555 51.32944107055664))</geoRegion>
      <subSamplingX>1</subSamplingX>
      <subSamplingY>1</subSamplingY>
      <fullSwath>false</fullSwath>
      <tiePointGridNames/>
      <copyMetadata>true</copyMetadata>
    </parameters>
  </node>
  1. If I edit the XML file and delete one of the duplicated coordinate pairs and then load the file within the Graph Builder, the WKT polygon contains the duplicated coordinate pairs, again.

  2. The referenceBand parameter won’t be considered when loading the XML file within the Graph Builder. In the above example, I selected band “B2” but the UI lists band “B1”.

Since I didn’t find any similiar issue within this forum, I wondered, if these are known issues to you.

Thanks for the report @SebaDro.
As far as I know they are not yet known.
@lveci can you have a look?

I recommend to adjust the parameters when running the batch processing and not when preparing the graph.

As you recommended, I adjust the parameters before executing the graph. Nevertheless, the processing runs succesfully despite the duplicated coordinate pair within the WKT polygon.
However, we only use the Graph Builder for preparing a graph and exporting the XML-file in order to execute the process by using the GPT class of the Java API. And since we are using processing parameters (${name}) for some operators, it was a little bit confusing of how to specify the WKT polygon, due to the duplicated coordinate problem.