Apply Missing project bounds to 2024CONUS projects

[philipbaileynar]

During the 2024 CONUS run, the XML enricher broke and many projects were produced without project bounds. It affects several project types, but RME is the worst affected.

Task

Python script to:

1. Loop over projects with the tag 2024CONUS that do not have project bounds.
2. Find a project with the same HUC metadata that does have project bounds. Preferably this would be a project with the tag 2025CONUS because it ensures its the latest and greatest version.
3. Apply the bounds to the 2024CONUS project that is missing them.
4. Update the project in the Data Exchange. (Update existing... not add a new one)

---

Note: Make sure any scripts you write are tested thoroughly on staging before applying them to production

[MattReimer]

There are some weird edges here that we haven't considered. The easiest thing to do would be to reassign the boundsId in the database but that won't put the project_bounds.json file into the project and it won't update the XML with the correct bounds data.

This wouldn't be a problem until the next upload of that project but it puts a bunch of projects in a precarious position of having broken bounds on the next update so.....

Probably the best way to do this is to use the rscli to download do it this way:

1. Use the rscli to download the project.
2. add the project_bounds.json and the bounds xml node from the source project.
3. Re-upload just the delta.

---

Downloading files from the data exchange:

You can actually use the python API to download files you need (see scripts/utility/file_download.py)

download_files()

Uploading files to the data exchange

You can do this via the API but it's tedious and we don't have a method to automate this yet. Probably better to use the python to call rscli upload

⚠️ Before this task can start both these issues need to be solved:

• https://github.com/Riverscapes/rs-web-monorepo/issues/819
• https://github.com/Riverscapes/rs-web-monorepo/issues/820

[philipbaileynar]

Yes, your latter suggestion is what I was thinking. No need to get fancy or performant. This is a one time process.

[MattReimer]

Performance is a little bit of a concern since there are untold thousands of these operations to do. At the very least we should be only operating on the smallest fileset possible so we don't have to download the whole project to make this work.

[jagDhillon077]

RME project HUCs missing project.rs.xml file

• 0110000403
• 0205020504
• 0207000801
• 0208020606
• 0303000501
• 0304020801
• 0305020707
• 0306010202
• 0309010101
• 0311010204
• 0312000110
• 0401020107
• 0510010202
• 0511000109
• 0511000504
• 0512011308
• 0701020405
• 0705000507
• 0706000108
• 0707000106
• 0708020106
• 0708020404
• 0708020901
• 0711000204
• 0713000905
• 1009020603
• 1103000505
• 1109020104
• 1114020801
• 1402000606
• 1403000402
• 1407000611
• 1606000814
• 1707010510

[jagDhillon077]

Rs context HUC missing project.rs.xml

• 1708000101

[jagDhillon077]

This has some of the HUCs without an RS context, may need to look into these, re assigning to Philip for the missing HUC problem