Description
After using some data in an hofx test for MTG-IRS I noticed a few changed and missing variables. One where I'm not sure what the correct answer would be is sensoScanPosition. Right now, I just filled that in with dwell number.
@hongli-wang filled this with a truncated integer value of sensorZenithAngle as this roughly matched up with similar metadata associated with the GOES ABI implementation.
Requirements
Can run an hofx test using CRTM.
End users are happy with available metadata
Acceptance Criteria (Definition of Done)
Can run an hofx test using CRTM
End users are happy with available metadata
Dependencies
None
Description
After using some data in an hofx test for MTG-IRS I noticed a few changed and missing variables. One where I'm not sure what the correct answer would be is sensoScanPosition. Right now, I just filled that in with dwell number.
@hongli-wang filled this with a truncated integer value of sensorZenithAngle as this roughly matched up with similar metadata associated with the GOES ABI implementation.
Requirements
Can run an hofx test using CRTM.
End users are happy with available metadata
Acceptance Criteria (Definition of Done)
Can run an hofx test using CRTM
End users are happy with available metadata
Dependencies
None