DOI: 10.5281/zenodo.15391839
title: DSWx-Width: Data products associated with computing river widths from the OPERA DSWx product

description: Corresponding peer-reviewed publication

This dataset corresponds to all input and output files that were used in the study reported in:



Wade, J., Frasson, R.P.M., David, C.H., Munasinghe, D. Collins, E. (In Prep), DSWx-Width: Computing River Widths from the OPERA DSWx Product


When making use of any of the files in this dataset, please cite both the aforementioned article and the dataset herein.

 

Summary

The DSWx-Width data product transforms observations of surface water extent provided by the OPERA Dynamic Surface Water Extent (DSWx) product into measurements of river width. River width measurements are made along nodes in the SWOT River Database (SWORD; Altenau et al., 2021), enabling comparison with SWOT observations of width. Within this dataset, we evaluate the compatibility of SWOT- and DSWx-derived widths within the Missouri River Basin from 2023-07-01 to 2024-10-19 at 75,218 unique SWORD nodes.

 

DSWx-Width:

1.     Aggregate and prepare OPERA DSWx imagery for width computation.

2.     Compute widths from the DSWx product using an automated workflow.

3.     Provide comparisons between SWOT- and DSWx-derived widths in the Missouri River Basin.

 

Software

The software that was used to produce files in this dataset are available at https://github.com/jswade/DSWx-width.

 

Primary Data Products

The following files represent the primary data products of the DSWx dataset. In general, each file class is split over 4 UTM zones and 34 date windows, resulting in 136 unique files for most file types. The data products can be broken down into files corresponding to inputs used by automated scripts and outputs produced by those scripts.

The DSWx input files available here correspond to both shapefiles used to delineate the study area and SWOT PIXCVec observations used for future visualization.





input.zip:



/area_shp/missouri_area.shp: Shapefile delineating the Missouri River Basin used to select SWORD nodes for width computation.

/utm_zones/missouri_utmXXN.shp: Shapefiles delineating the UTM zone boundaries within the Missouri River Basin used to split files into UTM zones to match SWOT observation projections.

/swot_pixcvec/SWOT_L2_HR_PIXCVec_XX.nc: Example SWOT PIXCVec observations used for visualizing SWOT’s surface water detection against OPERA DSWx.




 

The output SWORD files correspond to SWORD node shapefiles, extreme distance buffers, and Voronoi (Thiessen) polygons that form the targets for river width computation.





output_sword.zip:



/nodes/target_nodes_utmXXN.shp: Shapefiles containing the target SWORD nodes for width computation in each UTM zone.

/buffers/ext_dist_buffer_utmXXN.shp: Shapefiles containing extreme distance buffers surrounding SWORD nodes in each UTM zone. Buffers delineate maximum distance for pixel assignment to each node.

/voronoi/clipped_voronoi_utm_XXN.shp: Shapefiles containing Voronoi (Thiessen) polygons surrounding SWORD nodes in each UTM zone. Polygons delineate zone of influence for pixel assignment to each node.




 

The output OPERA files correspond to the primary outputs of our analysis, including OPERA DSWx tile reclassification, aggregation, and merging, main river identification, width computation, and comparison to width observations made by SWOT.



output_opera.zip



/conf_reclass/OPERA_L3_DSWx_HLS_XXX.tif: OPERA DSWx CONF tiles reclassified to match simpler pixel values used by the WTR layer using aggressive reclassification strategy (see ConfReclass_OPERA.py).

/temp_agg/opera_TXXX_date1_date2.tif: Reclassified OPERA DSWx tiles temporally aggregated over 2 week windows across study period.

/utm_overlap/opera_utm_overlap.csv: File listing the UTM zones of OPERA DSWx tiles for segmenting analysis by UTM zones.

/merge/opera_XXN_date1_date2.tif: Spatially merged temporally aggregated OPERA DSWx tiles corresponding to each UTM zone and date window.

/clump/reclass/ opera_XXN_date1_date2_reclassified.tif: OPERA DSWx merged tiles reclassified to simple water/no water pixel values for main river identification.

/clump/clumpedras_poly/opera_XXN_date1_date2_clumpedRas_poly.shp: Shapefiles of clumped adjacent pixels with same water/no water pixel values. Used in main river identification.

/conwater/con_ras/opera_XXN_date1_date2_connected_water_raster.tif: Raster delineating which open water pixels belong to main connected channel and which represent disconnected water.

/conwater/con_reclass/opera_XXN_date1_date2_connected_reclass.tif: Connected water rasters reclassified to include information regarding partial surface water, snow/ice, and cloud cover.

/conwater/main_river/ opera_XXN_date1_date2_main_river.tif: Raster differentiating connected/unconnected open and partial water pixels for each UTM zone and date window.

/pixel_num/opera_XXN_date1_date2_pixel_nums_thiessen.csv: Files containing the number of each pixel class from OPERA DSWx corresponding to SWORD nodes in each UTM zone and date window. Pixel counts used to compute river width.

/width_utm/opera_XXN_date1_date2_river_width.csv: Files containing computed river widths from OPERA DSWx for each UTM zone and date window.

/width/opera_date1_date2_riverwidth.csv: Files containing computed river widths from OPERA DSWx aggregated across all UTM zones for each date window.

/swot_comp/opera_swot_comp_2023-07-01to2024-10-19.csv: File containing paired SWOT and OPERA-DSWx river widths at coincident locations and times for comparison.

/node_metrics/swot_opera_metrics_2023-07-01to2024-10-19.csv: File containing the results of SWOT-OPERA DSWx width comparison aggregated to SWORD nodes.

/node_metrics/swot_opera_metrics_2023-07-01to2024-10-19.shp: Shapefile containing the results of SWOT-OPERA DSWx width comparison aggregated to SWORD nodes.

/swot_rast_diff/SWOT_L2_HR_PIXCVec_XXXX.shp: Shapefile of SWOT PIXCVec point cloud assignments to SWORD nodes.

/swot_rast_diff/SWOT_L2_HR_PIXCVec_XXXX.tif: SWOT PIXCVec point cloud observations rasterized to same spatial resolution as OPERA DSWx rasters.

/swot_rast_diff/SWOT_L2_HR_PIXCVec_diff_XXXX.tif: Raster of difference between rasterized SWOT PIXCVec point cloud and OPERA DSWx raster for temporally coincident observations. Resulting raster shows differences in water detection between SWOT and OPERA DSWx




 

The output SWOT files correspond to downloaded SWOT L2 HR River Single Pass observations of river width and their associated decoded bitwise quality flags.



output_swot.zip



swot_nodes_2023-07-01to2024-10-19.csv: SWOT L2 HR River Single Pass observations of river width and associated observation attributes for selected SWORD notes.

swot_nodes_2023-07-01to2024-10-19_bit_qual.csv: SWOT L2 HR River Single Pass decoded bitwise quality flags corresponding to observations at selected SWORD nodes.




 

The input testing files consist of a full set of inputs for a select location used for continuous integration testing of analysis scripts through GitHub. These files are not intended for use outside of CI testing.



input_testing.zip: Input files corresponding to reduced set of SWORD nodes and OPERA DSWx tiles used for GitHub Continuous Integration testing. Not used in primary analysis.


 

The output testing files consist of a full set of outputs for a select location used for continuous integration testing of analysis scripts through GitHub. These files are not intended for use outside of CI testing.



output_testing.zip: Output files corresponding to reduced set of SWORD nodes and OPERA DSWx tiles used for GitHub Continuous Integration testing. Not used in primary analysis.