(RSLC) Inconsistent Metadata values

Overview

RSLC is inconsistent with GSLC, GCOV, and all five InSAR about how to populate the values for processingType and processingCenter metadata.

RSLC should be updated to match the XML specs and the other L1/L2 products.

RSLC Product checked: NISAR_L1_PR_RSLC_001_149_D_080_2005_QPDH_A_20251003T130952_20251003T131016_X05016_N_P_J_001

Dataset: /science/LSAR/identification/processingType

• Current value in RSLC: 'PR'
• Values: must be one of ('Nominal', 'Urgent', 'Custom')

Dataset: /science/LSAR/identification/processingCenter

• Current value in RSLC: 'J'
• must be one of ('JPL', 'ISRO')

Details

Dataset: /science/LSAR/identification/processingType

• Description from XML:
  • Processing pipeline used to generate this granule. "Nominal": standard production system; "Urgent": time-sensitive processing in response to urgent response events; "Custom": user-initiated processing outside the nominal production system
• GSLC/GCOV implementation: https://github.com/isce-framework/isce3/blob/3f7027debde70708716b1058fb630e7abe904105/python/packages/nisar/products/writers/BaseWriterSingleInput.py#L663-L675

Dataset: /science/LSAR/identification/processingCenter

• GSLC/GCOV implementation:
  https://github.com/isce-framework/isce3/blob/3f7027debde70708716b1058fb630e7abe904105/python/packages/nisar/products/writers/BaseWriterSingleInput.py#L598-L605

cc: @hfattahi @bhawkins

Start with the referenced sections of python/packages/nisar/products/writers/BaseWriterSingleInput.py, then trace the RSLC writer's population of /science/LSAR/identification/processingType and processingCenter. Compare its metadata with the XML-required values and the GSLC/GCOV implementation, and verify the checked RSLC product uses the allowed values.