Output setting of batch processing changes

[oaeen]

I have already created my own graph, which has modify the output parameters of reprojection.

<resampling>Nearest</resampling>
<referencePixelX>1685.5</referencePixelX>
<referencePixelY>1076.0</referencePixelY>
<easting>-74.25</easting>
<northing>40.5</northing>
<orientation>0.0</orientation>
<pixelSizeX>0.01</pixelSizeX>
<pixelSizeY>0.01</pixelSizeY>
<width>3371</width>
<height>2152</height>

However, the output parameters changed when I loaded my graph in Graph Batch Processing. It automatically selected the 'Preserve Resolution' in the node of reprojection but that's not I want. I just want my personally modified output parameters but not the automatically selected one.


Is there any method that I can cope with this question? Thank you for your help!

[ASDC - ingridgs]

Dear user,

Thank you for reaching out to the Earthdata Forum.

To better re-direct your question to the correct department, can you please let us know what product you are using and what tool are you using?

Thank you,

[oaeen]

Thank you for your reply!

I am using L2-Level data of MODIS and the product is 'SeaDAS'.

I have already set the output parameters of reprojection in the graph.xml (e.g. Reference Pixel, Easting, Northing). However, when I loaded the graph, the output parameters all disappeared and I have no choice but to set the parameters again.

What should I do to avoid this situation?

[OB SeaDAS - knowles]

In order for us to replicate what you are seeing, can you provide the file myGraph3.xml which you are loading into the Batch Processing tool (or can you upload the file's full contents)?

[oaeen]

Sure！

myGraph.xml:

<graph id="Graph">
<version>1.0</version>
<node id="Read">
<operator>Read</operator>
<sources/>
<parameters class="com.bc.ceres.binding.dom.XppDomElement">
<file>${ifile}</file>
<formatName>SeaDAS-L2</formatName>
</parameters>
</node>
<node id="Reproject">
<operator>Reproject</operator>
<sources>
<sourceProduct refid="Read"/>
</sources>
<parameters class="com.bc.ceres.binding.dom.XppDomElement">
<wktFile/>
<crs>GEOGCS[&quot;WGS84(DD)&quot;, &#xd;
DATUM[&quot;WGS84&quot;, &#xd;
SPHEROID[&quot;WGS84&quot;, 6378137.0, 298.257223563]], &#xd;
PRIMEM[&quot;Greenwich&quot;, 0.0], &#xd;
UNIT[&quot;degree&quot;, 0.017453292519943295], &#xd;
AXIS[&quot;Geodetic longitude&quot;, EAST], &#xd;
AXIS[&quot;Geodetic latitude&quot;, NORTH]]</crs>
<resampling>Nearest</resampling>
<referencePixelX>1509.0</referencePixelX>
<referencePixelY>1064.5</referencePixelY>
<easting>-72.25</easting>
<northing>40.5</northing>
<orientation>0.0</orientation>
<pixelSizeX>0.01</pixelSizeX>
<pixelSizeY>0.01</pixelSizeY>
<width>3371</width>
<height>2152</height>
<tileSizeX/>
<tileSizeY/>
<orthorectify>false</orthorectify>
<elevationModelName/>
<noDataValue>NaN</noDataValue>
<includeTiePointGrids>true</includeTiePointGrids>
<addDeltaBands>false</addDeltaBands>
</parameters>
</node>
<node id="Subset">
<operator>Subset</operator>
<sources>
<sourceProduct refid="Reproject"/>
</sources>
<parameters class="com.bc.ceres.binding.dom.XppDomElement">
<sourceBands>chlor_a</sourceBands>
<region>0,0,0,0</region>
<referenceBand/>
<geoRegion>POLYGON ((-75 42, -69.5 42, -69.5 39, -75 39, -75 42, -75 42))</geoRegion>
<subSamplingX>1</subSamplingX>
<subSamplingY>1</subSamplingY>
<fullSwath>false</fullSwath>
<tiePointGrids/>
<copyMetadata>true</copyMetadata>
</parameters>
</node>
<node id="Write">
<operator>Write</operator>
<sources>
<sourceProduct refid="Subset"/>
</sources>
<parameters class="com.bc.ceres.binding.dom.XppDomElement">
<file>${ofile}</file>
<formatName>NetCDF4-CF</formatName>
</parameters>
</node>
<applicationData id="Presentation">
<Description/>
<node id="Read">
<displayPosition x="37.0" y="134.0"/>
</node>
<node id="Reproject">
<displayPosition x="155.0" y="224.0"/>
</node>
<node id="Subset">
<displayPosition x="359.0" y="225.0"/>
</node>
<node id="Write">
<displayPosition x="455.0" y="135.0"/>
</node>
</applicationData>
</graph>

[OB SeaDAS - knowles]

The bad news here is that I can confirm when I load into either the GUI Graph Builder or the GUI Batch Processing an xml file for the Reproject operator containing the fields of the Reproject "Output Parameters", these particular parameters are NOT loaded in, and the defaults are used.

We will look into fixing this in a future SeaDAS release (current release as of this post is SeaDAS 8.2.0)

This is a GUI bug, so running gpt from the command line with your xml file should work fine.

To run from the GUI, right now you will need to manually set these Reproject parameters within the GUI.