isce-framework / isce-framework/isce3

(Spec non-compliance) dtype Mismatch: `diagnosticModeFlag` (XML uint8 vs HDF5 uint32)

Open
#313 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
239
Forks
90
Avg merge
13d 1h
Merged PRs (30d)
5

Description

Data type mismatch between XML specification and HDF5 implementation for dataset /science/LSAR/identification/diagnosticModeFlag:

  • XML spec: uint8
  • HDF5 file: uint32

Impact: Affects all 8 NISAR L1/L2 product types

Products Checked

  • NISAR_L1_PR_RSLC_001_149_D_080_2005_QPDH_A_20251003T130952_20251003T131016_X05016_N_P_J_001
  • NISAR_L1_PR_RIFG_013_118_A_171_014_2000_SH_20260222T102514_20260222T102520_20260306T102515_20260306T102521_X05016_P_P_J_001
  • NISAR_L2_PR_GUNW_001_062_A_019_006_2000_SH_20250927T114508_20250927T114542_20251126T114516_20251126T114545_X05016_P_F_J_001
    • NISAR_L2_PR_GCOV_001_149_D_080_2005_QPDH_A_20251003T130952_20251003T131016_X05016_N_P_J_001
    • NISAR_L2_PR_GOFF_005_106_A_140_006_7700_SH_20251117T140848_20251117T140925_20251129T140849_20251129T140925_X05016_P_P_J_001
    • NISAR_L1_PR_ROFF_007_106_A_140_008_7700_SH_20251211T140849_20251211T140926_20251223T140850_20251223T140926_X05016_N_P_J_001
    • NISAR_L1_PR_RUNW_007_106_A_140_008_7700_SH_20251211T140849_20251211T140926_20251223T140850_20251223T140926_X05016_N_P_J_001
    • NISAR_L2_PR_GSLC_001_149_D_080_2005_QPDH_A_20251003T130952_20251003T131016_X05016_N_P_J_001

cc: @hfattahi @bhawkins @gshiroma @xhuang-jpl @seongsujeong

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the XML definition and HDF5 writer or validator for /science/LSAR/identification/diagnosticModeFlag, then compare how its dtype is selected. Check the behavior against the eight listed NISAR L1/L2 product types; done means the implementation complies with the XML uint8 specification across all products.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, xml
Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.