...
| # | Title | User Story | Importance | Status | Notes |
|---|---|---|---|---|---|
| 1 | Assessment using reference points | The user opens an OLCI L1B and a SLSTR L1B product. He/she continues to load in a list of reference points with well-known geolocations. These points are placed on the image grids. The user can then assess how well the points were placed. The primary format for the geolocations are plain text, CSV files: <lat>, <lon>, <label>. Useful are also Google Earth KMZ and ESRI Shapefiles. | MUST | Implemented. This is basically the import of placemarks. |
|
| 2 | Assessment by comparing geolocations | The user places a pin in an OLCI L1B product at some distinct feature (e.g., the tip of an island). The user places another pin at the same feature in a SLSTR L1B product. Both pins will have geolocations assigned to them. These geolocations can be compared. | COULD | Not implemented. We are unsure about how and whether to integrate the uncertainty. The plan is for someone to look at the displacement bands created from olci and slstr pixelgeocodings and to determine whether the displacement is so large it should be considered. | This would also require form of uncertainty information: What is the error which is introduced by the application of the inverse geocoding? |
| 3 | Assessment by transferring pins | The user places a pin in an OLCI L1B product. A pin is automatically set in a SLSTR product on base of the pin's geolocation. The displacement of the pin and its expected position can be assessed visually. In addition, the geocoding from the expected position in the SLSTR product can be derived and compared to the pin's geoposition. | MUST | Not implemented, but there is a new feature: When pins are transferred from Product A to Product B a second time (or multiple times), the user is asked whether to update the pins. If the answer is yes, the corresponding pins from an earlier transfer are removed and replaced by new pins. This didn't work once without me being able to find out why. | This would make use of a global or synchronized pin.Short Term solution: Enable" Move pins to other product" action to also update pins |
| 4 | Assessment in a SYN L1C product | First, the L1Cany "OLC_RADIANCE _O17" band (which is located at 865 nm, the reference wavelength) is opened. The user places pins in one of the camera images or imports pins from an external file. The "OLCI pins" are automatically transferred to anyFrom a "MISREGIST " files. These are nc-files which contain two variables: "row_corresp" and "col_corresp" for each camera image. From these variables, the pixel position in the respective radiance bands can be retrieved_OLC" file, the SceneRasterTransform (forward and inverse) is created. "OLC_RADIANCE_O17" is the reference band and has the SceneRasterTransform.IDENTITY. Using "MISREGIST_SLSTR", SceneRasterTransforms (only inverse!) are created and set to SLSTR bands. A pin set in an OLCI image can thereby be placed at the corresponding position in a SLSTR image.The position of the pixels can be compared visually or by comparing the geo-locations. | MUST | Implemented. Users can set pins or draw shapes in any OLCI band. These figures are depicted on all OLCI or SLSTR bands. It is not possible to draw on SLSTR bands, as there is no forward transform. When a figure is set outside of the area where the misregistration has valid values, the figure is distorted. |
User interaction and design
...