POM feedback: node_order availability + SWOT NC suggestions

[jameshgrn]

POM Feedback (2026-03-18)

1. nodes/node_order reported missing in some regions

POM reports node_order not found in pfafstetter codes 1 (AF), 2 (EU), 3 (AS), 4 (AS), 6 (SA).
Present in 5 (OC), 7 (NA), 8 (NA), 9 (NA).

Investigation: All 6 current v17c exports (data/exports/v17c_beta/*.nc) have node_order in every region. v17b has it in zero regions. POM likely has stale files from an earlier export batch. Need to confirm which files POM is testing (filenames, checksums) and re-share current exports.

2. Suggestion: add node_order to SWOT NC files (Confluence Input module)

POM suggests SWOT NC files should include nodes/node_order so downstream consumers don't need to recompute it. This is a CNES/JPL Confluence request — outside our direct scope but worth passing along.

3. Suggestion: add SWORD version metadata to SWOT NC files

POM suggests SWOT NC files should include which SWORD version (17b, 17c, etc.) was used, to help consumers understand expected treatments. Also a Confluence-side request.

Action items

• Verify our exports have node_order in all regions
• Confirm which files POM is testing
• Re-share current v17c exports if needed
• Forward suggestions 2 and 3 to CNES/JPL Confluence team

[jameshgrn]

Resolved in 0.0.3:

• node_order present in all 6 exported regions (verified)
• Fresh exports re-shared to Google Drive (Mar 26)
• POM's stale file issue resolved by new versioned filenames (_0.0.3)
• CNES/JPL suggestions (node_order in SWOT NC, version metadata) are out of scope — forwarding to Tamlin separately