...
| No. | Use Case | Option 1: Very restrictive | Option 2: Transform to product grid (B<i>.CS -> P.CS) | Option 3: Transform to product grid to raster grid (B<i>.CS -> P.CS -> Bh.CS) | ||
|---|---|---|---|---|---|---|
| 1 | Band Arithmetic: Combining two or more bands of different sizes (adding, multiplying, ...) to create a new band / Creating a RGB Image View from multi-size bands | Don’t allow it, display error message ((/) done in Maybe extend Symbol with method Problem: must provide to users an operation that does the transform from B<i>.CS -> P.CS | Auto-transform to product resolution B<i>.CS -> P.CS Problem: Might not be expected by users | Auto-transform to Bh res which has the highest res of the B<i>
Problem: we need to find and perform transform B<i>.CS -> P.CS -> Bh.CS | ||
| 2 | Correlative Plot/Profile Plot: Displaying a plot for a rdn with vector data | The position of the vector data within the raster image coordinates is considered. Parts of the geometry outside of the image will not be displayed in the plot. When the box size value is altered, it will refer to the pixel size of the raster image grid. Only compatible (equal size) ROI Masks are selectable. | The position of the vector data within the raster image coordinates is considered. Parts of the geometry outside of the image will not be displayed in the plot. When the box size value is altered, it will refer to the pixel size of the raster image grid. | The position of the vector data within the raster image coordinates is considered. Parts of the geometry outside of the image will not be displayed in the plot. When the box size value is altered, it will refer to the pixel size of the raster image grid. | ||
| 3 | Adding/Managing GCPs or Pins | GCPs and Pins will be displayed in all rdn's of a product. They will be displayed at the location which is specific to the grid. When the pin/GCP is moved, its position will change in all product scene views. Pins or GCPs are always located at the center of a pixel. | GCPs and Pins will be displayed in all rdn's of a product. They will be displayed at the location which is specific to the grid. When the pin/GCP is moved, its position will change in all product scene views. Pins or GCPs are always located at the center of a pixel. | GCPs and Pins will be displayed in all rdn's of a product. They will be displayed at the location which is specific to the grid. When the pin/GCP is moved, its position will change in all product scene views. Pins or GCPs are always located at the center of a pixel. | ||
| 4 | Placemark/GCP view | In the views, the pixel position is given in product coordinates. This is noted explicitly. | In the views, the pixel position is given in product coordinates. This is noted explicitly. | In the views, the pixel position is given in product coordinates. This is noted explicitly. | ||
| 5 | GeoCoding | The GeoCoding information will be displayed for the currently selected rdn. | The GeoCoding information will be displayed for the currently selected rdn. | The GeoCoding information will be displayed for the currently selected rdn. | ||
| 6 | Layer Manager | Only allow adding bands B<i> where B<i>.CS == Bv.CS | Auto-transform all bands to Prod res.To transform a grid onto another grid, the user can choose which type of interpolation to use. By default, NEAREST NEIGHBOR is selected. Problem: Might not be expected by users | Auto-transform all bands to Bv res. To transform a grid onto another grid, the user can choose which type of interpolation to use. By default, NEAREST NEIGHBOR is selected. Problem: we need to find and perform transform B<i>.CS -> P.CS -> Bv.CS | ||
| 7 | Mask Manager | Masks are only displayed/applicable to bands of the same size/resolution. It is not allowed to combine rasters of different sizes to create a new mask. | Both the grid and the mask are transformed to the product grid. Problem: Might not be expected by users | The grid in the currently selected productsceneview sets the reference grid: A mask will be displayed with regard to this grid. The mask is interpolated onto a grid using the NEAREST NEIGHBOUR method. Problem: we need to find and perform transform B<i>.CS -> P.CS -> Bv.CS | ||
| 8 | Navigation | When clicking 'Zoom to all', the zoom will be performed with regard to the rdn bounds. When the "Synchronizing" options are selected, the synchronistion should behave like for multiple products right now.. | ? | When clicking 'Zoom to all', the zoom will be performed with regard to the raster bounds, not the product bounds. When the "Synchronizing" options are selected, the viewports and the cursor position will be transformed, such that not the same pixel locations are used. | ||
| 9 | Pixel Info View | Only display pixel values of bands B<i> where B<i>.CS == Bv.CS If Bv.CS != P.CS don't show scan line time. If Bv.CS != P.CS don't show TPGs. If TPG shown don't show Bands != P.CS | ? | Display pixel values of all bands B<i> at corresponding pixel positions given by Question: Shall an interpolation be used? | ||
| 10 | Scatter Plot | Only show scatter plot for bands of the same size. Error is already shown but selection should be prevented. | Transform both bands to product coordinates. | Scatter plots can be shown for bands of all sizes. The number of pixels will be determined by the grid with more pixels. If for one pixel no corresponding pixel exists in the other band, it will not be considered in the plot. | ||
| 11 | Spectrum View / Magic Wand Tool | Only display pixel values of bands B<i> where B<i>.CS == Bv.CS | Transform all concerned bands to product coordinates. Display pixel values of all bands B<i> at corresponding pixel positions given by Bv.CS -> P.CS | Display pixel values of all bands B<i> at corresponding pixel positions given by Bv.CS -> P.CS -> B<i>.CS | ||
| 12 | Non-UI operations using masks | Masks will only be applicable to bands of the same size. | Masks and bands will be scaled to be on the product CS. | The mask will be transformed to be on grid of the concerned raster data node (or, in the case of multiple raster data nodes with different sizes, of the one with the finest resolution). | ||
| 13 | World Map | The World Map will display the bounds of products. | The World Map will display the bounds of products. There is an option to display bounds of raster data nodes of a different grid, too, in a way it is apparent they are part of the product. | The World Map will display the bounds of products. There is an option to display bounds of raster data nodes of a different grid, too, in a way it is apparent they are part of the product. | ||
| 14 | Create Filtered Band | Option will only be available for bands on the product CS. | Box sizes will refer to pixel sizes of the product CS. | Box sizes will refer to pixel sizes of the selected raster CS. | ||
| 15 | Create Geo-Coding Displacement Bands | These bands can be only created for the product geo-coding. | These bands can be created for geo codings of bands, too, if these might differ from the product's geocoding. | These bands can be created for geo codings of bands, too, if these might differ from the product's geocoding. | ||
| 16 | Attach Pixel Geo-Coding | Pixel Geo-Codings can only be attached to the whole product. | Pixel Geo-Codings can be attached to either the whole product or single bands. The latitude/longitude bands must be of the same grid as the product/band(s) for which they are created. | Pixel Geo-Codings can be attached to either the whole product or single bands. The latitude/longitude bands must be of the same grid as the product/band(s) for which they are created. | ||
| 17 | Compute Mask Area | The mask must have the same CS as the product or its own GeoCoding. | The mask area will be computed with regard to the product CS. | The mask area will be computed with regard to the raster in the currently selected product scene view. | ||
| 18 | Pixel Extraction | This operation will only be available for raster data nodes on the product grid. | Bands will be transformed onto the product CS. Pixel windows refer to pixel areas in the product CS.
| Pixels to be considered for extraction are determined on base of geographic coordinates, i.e., exactly one pixel can be determined. As no reference grid can be determined, for each pixel the window size is given in the pixel sizes of the grid: A 3x3 window is always a 3x3 window, regardless of the area covered by the pixels in the respective grid. | ||
| 19 | GPF: Use of PixelOperators | Only bands on the product grid can be considered. | Bands will be transformed onto the product CS, if necessary. | A PixelOperator operating on multi-sized source rasters will provide the option to either collect source samples on a pixel basis (no transformation) or on a location-aware basis (using scene raster transformations). The method computePixel will be passed sourcesamples accordingly. The option will not be public. When using computeTileStack, each pixel will be either transformed or non-transformed, depending on the option set. By default, the option will be set to "transform". The source resolution of the output bands will be determined as in use case 1. | ||
| 20 | Reprojection / Orthorectification | Don’t allow it, display error message
Problem: must provide to users an operation that does the transform from B<i>.CS -> P.CS | Auto-transform all bands to product resolution B<i>.CS -> P.CS Problem: low res bands are exploded to highest res, redundant info, more memory | n.a. | ||
| 21 | Subset / Flipping | Don’t allow it, display error message
Problem: must provide to users an operation that does the transform from B<i>.CS -> P.CS | Auto-transform all bands to product resolution B<i>.CS -> P.CS Problem: low res bands are exploded to highest res, redundant info, more memory | n.a. | ||
| 22 | Binning | Only allow binning for bands on a product CS. | Transform all bands to product CS. | When using expressions, proceed as for Band Maths. Use grids in their native sizes. | ||
| 23 | Mosaicing | Only allow for bands on product CS. | Transform all bands to product CS. | When using expressions, proceed as for Band Maths. Use grids in their native sizes. | ||
| 24 | Collocation | Don’t allow it, display error message
Problem: must provide to users an operation that does the transform from B<i>.CS -> P.CS | Auto-transform all bands to product resolution B<i>.CS -> P.CS Problem: low res bands are exploded to highest res, redundant info, more memory | This is the one tool where different CS are actually dissolved: All bands are transformed to the CS of the master product.
Comment: This tool might be enhanced, such that bands can be transformed onto a product grid for good. | ||
| 25 | Range Finder | Only allow for rasterdatenodes with product resolution | Use band CS to determine range | Use band CS to determine range | ||
| 26 | Graticule Layer | Display correct graticule for each displayed rasterdatanode. | Display correct graticule for each displayed rasterdatanode. | Display correct graticule for each displayed rasterdatanode. |
Design Approach Matrix
The purpose of this matrix is to list the various possibilities on how multi-size-bands can be supported in SNAP and what these approaches would mean for various use cases
...