InSAR / Water Mask license info metadata not populated
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start with stage_watermask.py and trace how the LICENSE.txt fields are written into the water mask VRT. Then follow the STATIC and InSAR workflows that read water_mask_description and populate waterMaskSource and mask disclaimer metadata. Done means the relevant products contain the license description instead of "(NOT SPECIFIED)" and no longer omit the disclaimer or valid_min attributes.
Written by the indexing model from the issue text.
Description
Issue
Currently, the operational InSAR products are populating the Water Mask Source with "(NOT SPECIFIED)" and omitting the mask disclaimer. These should be populated with the license terms for the water mask in accordance with its input datasets' licenses.
These errors are noted in the details of Issue #219 and Issue #204 ; submitting this as a separate Issue to raise awareness. Here are the error messages, copied here for convenience (note that the path in these messages has been generalized for all relevant product types):
"Value is '(NOT SPECIFIED)', which is not valid for nominal NISAR data. Path: /science/LSAR/[RIFG|RUNW|GUNW|ROFF|GOFF]/metadata/processingInformation/inputs/waterMaskSource""Attributes found in XML but not HDF5: {'disclaimer', 'valid_min'} - Dataset /science/LSAR/[GUNW | GOFF]/grids/frequencyA/unwrappedInterferogram/mask"
Background
During the implementation of the STATIC layers workflow (which also uses the water mask), there arose several discussions by NISAR ADT regarding the correct process that the STATIC and InSAR SASs should use re: the water mask license. The full discussions and final resolution are documented in these links:
- How to get DEM description + license for Static Layers? https://github.com/isce-framework/isce3/issues/80
- Add water_mask_file_description to runconfig for InSAR, Static Layers : https://github-fn.jpl.nasa.gov/isce-3/isce/issues/2164
- Add license to staged WaterMask VRT: https://github.com/isce-framework/isce3/pull/77
- Add the water mask source and update the L2 InSAR product mask attributes : https://github.com/isce-framework/isce3/pull/96
- STATIC workflow implementation: https://github.com/isce-framework/isce3/pull/144
Resolution (copied from: https://github-fn.jpl.nasa.gov/isce-3/isce/issues/2164#issuecomment-24044 ) :
Similar to the decision for the DEM license (see https://github.com/isce-framework/isce3/issues/80#issuecomment-3166138150):
- Static Layers and InSAR products will include a waterMaskSource dataset that includes the concatenated Short Description + Notes fields from teh water mask LICENSE.txt (see here: https://github-fn.jpl.nasa.gov/isce-3/isce/issues/2164#issuecomment-23800)
- Static Layers & GUNW & GOFF product will also include an attribute called disclaimer on their mask layers that includes the same string.
- stage_watermask.py will read these two strings from the LICENSE.txt file, concatenate them into a single string, and insert this string into the water mask VRT file as a metadata item called "water_mask_description". The Static Layers and InSAR workflows will read it directly from the VRT.
cc: @xhuang-jpl @jungkyoJung @hfattahi
- Dominant language
- Python
- Stars
- 239
- Forks
- 90
- Avg merge
- 13d 1h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from isce-framework/isce3
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
isce-framework/isce3#353 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
isce-framework/isce3#341 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
isce-framework/isce3#290 · 1 comment · 3 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
isce-framework/isce3#255 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
isce-framework/isce3#380 · 1 comment ·
All issues in isce-framework/isce3
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100