You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug was reported by a user who was editing the reference shoreline after loading from a session where the data had been downloaded in a previous session. When the user attempted to extract shorelines they got a no roi_settings found error despite the fact the log file for show that when the user loaded the session load_config_json shows that the roi settings were read from the config.json file.
When it downloads files it puts the session name in it and when you download any files a new session name is created using the current time you downloaded data. So all your files from the other session have the wrong name which means they all got filtered out because the session name didn't match.
This issue would need to be fixed in both coastsat_package and coastseg. Basically instead of reading the exact filename it should query the correct file based on the date and satellite. To avoid this kind of issue in the future coastsat_package should be updated to no longer save the sitename as part of the filename. This would make combining multiple download MUCH easier
2320sharon
changed the title
Roi Settings Randomly do not load
Feature Request: Update coastsat_package and coastseg to be less sensitive to tiff name changes
Dec 6, 2023
This bug was reported by a user who was editing the reference shoreline after loading from a session where the data had been downloaded in a previous session. When the user attempted to extract shorelines they got a no roi_settings found error despite the fact the log file for show that when the user loaded the session
load_config_json
shows that the roi settings were read from the config.json file.Relevant Files
roi_setting_bug.zip
The text was updated successfully, but these errors were encountered: