Issue: Sensitive ROI Directory Naming in Data Directory

[2320sharon]

Issue: Sensitive ROI Directory Naming in Data Directory

Problem:

CoastSeg expects the ROI directory to follow a specific naming convention within the data directory. Beta testing revealed issues when users attempted to extract shorelines with ROI directories that were nested within another directory of the same name, likely due to data being downloaded on a different computer. This misplacement causes the extraction process to fail due to incorrect ROI directory path.

Complications:

• Directory Nesting: Searching for nested ROI directories could be time-consuming, as it may involve traversing multiple subdirectories.
• Configuration Mismatch: Config files might not correspond correctly to the new file locations.
• Session Discrepancy: Existing sessions may not be able to locate download data if the original file locations have changed.

Current Status:

This is a complex issue with no immediate solution due to the current structure of the application. It requires further investigation and careful consideration of future application design to handle such cases effectively.

Action Required:

• Investigate potential solutions for directory structure flexibility.
• Consider implementation changes in future versions of CoastSeg to accommodate varying user data directory structures.
• Create efficient methods for iterating through downloaded data quickly

This issue serves as a reminder to address this challenge in upcoming development cycles.