BAGIS AOI Repository on PSU network

[jdduh]

The AOIs of all 580 NWCC active forecast stations are now available at: \data.geog.pdx.edu\data under the ActiveForecast_AOIs folder on PSU campus network. Users need to connect through VPN to access the data off-campus.

The AOIs are organized based on the 2-digit HUC watershed they are in. The AOIs are named with their stationTriplet number and the name of the forecast station (e.g., 05016000_MT_USGS_Lake_Sherburne_Inflow). Space and special characters (e.g., apostrophe) were substituted with characters that are recognizable in ArcGIS.

To find an AOIs, please use its stationTriplet value as the key to search for the file path value in the forecast_station_log.xlsx spreadsheet that can be found in the maps_publish folder.

As of May 25, 2023, these AOIs were used to generate the Basin Analysis Report (Version 1) pdf files. Check the time stamp of the basinanalyst.def file in the AOI folder to see when the AOI was generated.

Known issues (to be addressed in the future)

1. AOIs created before 2021 contain old Weasel-compatible legacy GIS files.
2. Most AOIs' stationTriplet, stationName, and HUC2 attributes in the pourpoint and aoi_v featureclasses were updated. However, some AOIs might not have valid values for these attributes. These attributes are required for BAGIS Pro to generate basin analysis reports.

[lbross]

It seems that the path provided is a Windows UNC path: \data.geog.pdx.edu\data. I couldn't find a way to access the data via FTP. I'm not sure if this is the intent. Note: the UNC path should start with a double-slash \\. GitHub changes this to a single slash in the comments.

What action items are associated with this issue? I remember discussing enhancements to the batch tool. Do you want new functions to:

1. Delete the old Weasel folder/files from these AOIs?
2. Update the stationTriplet, stationName, and HUC2 attributes from the forecast point feature service for forecast points?

[jdduh]

You can map \data.geog.pdx.edu\data to a logical drive to access the data. Please copy the AOIs to the local drive before using them. A new tool is needed to extract AOI/report data (#45). That has become a priority moving forward. I suggest that we implement the functions that you mentioned above now, instead of coming back to them a few months/years later.

[jdduh]

I probably can write a shell script to clean up the Weasel files in the AOIs. Please retool the update forecast station data tool to allow using stationTriplet value to update the stationName and Huc attributes in the AOIs. Maybe other checkbox to "update AOI station data based on stationTriplet value"

[lbross]

Will do. What do you want to do if the stationTriplet value is not found in the forecast point webservice? Leave the values as-is before trying to update? Or do you want to run the near tool to find a station triplet. The downside of running the near tool is that it will overwrite any manual updates.

[jdduh]

Please don't use the NEAR option. We have quite a few AOIs whose pourpoints are away from the forecast stations. Just ignore the ones that don't have a matched stationTriplet. We can keep a separate logfile (i.e., don't overwrite the one generated by the current tool) to capture the ones that get ignored and updated. Leave the others (i.e., matched and no update) out of the log file. Alternatively, we can write every AOI processed to the log file, but indicate a status at the end with some thing like: "not an active forecast", "no change", "stationName updated", "huc2 updated", or "stationName and huc2 updated".

[lbross]

I think most of this is done with the latest version of the batch tools except for deleting the Weasel files. Please let me know if you need any help with this.