VHeimhuber / InletTracker

Google Earth Engine-enabled toolkit for automated monitoring of dynamic coastal inlets from public satellite data
GNU General Public License v2.0
38 stars 9 forks source link

Error during training due to problems in raster files #3

Open saedoquililongo opened 1 year ago

saedoquililongo commented 1 year ago

Hi Valentin,

Working with the InletTracker package I have had some problems related to raster files with incomplete bands, resulting in an interruption of the training process. I think that this could be handled as an exception by analyzing the georef variable. This is not a major issue, but it could avoid interruptions in the training process and having to start again.

Temporarily I solved this issue by removing the text files from the meta directory and loading the data again. But if there are lots of rasters with problem, this maual process could take a long time.

Please find attached a input_locations.shp file with sitename QUILIMARI, which raised this problem. Also, I attach here an example of a raster with no problems and raster which raised the error.

At the end of this message I pasted a screenshot of the error I got and of the rasters in the study area. Please note that the red area in the lower right is the raster with problems.

Regards,

imagen

imagen

input_locations.zip

sample_rasters.zip

VHeimhuber commented 1 year ago

Hi Sebastian,

Thanks a lot for putting this to my intention!

I think I came across this issue in the past and its great that you got to the bottom of it. At this stage, I hardly use the training option anymore as manually choosing a classification threshold works really well usually. I’ll try to have a look at this once I’m back to programming and updating the software.

Perhaps you could propose a solution?

Thanks,

Tino

From: Sebastián A. Aedo Quililongo @.> Sent: Friday, 25 November 2022 3:34 AM To: VHeimhuber/InletTracker @.> Cc: Subscribed @.***> Subject: [VHeimhuber/InletTracker] Error during training due to problems in raster files (Issue #3)

Hi Valentin,

Working with the InletTracker package I have had some problems related to raster files with incomplete bands, resulting in an interruption of the training process. I think that this could be handled as an exception by analyzing the georef variable. This is not a major issue, but it could avoid interruptions in the training process and having to start again.

Temporarily I solved this issue by removing the text files from the meta directory and loading the data again. But if there are lots of rasters with problem, this maual process could take a long time.

Please find attached a input_locations.shp file with sitename QUILIMARI, which raised this problem. Also, I attach here an example of a raster with no problems and raster which raised the error.

At the end of this message I pasted a screenshot of the error I got and of the rasters in the study area. Please note that the red area in the lower right is the raster with problems.

Regards,

[Image removed by sender. imagen]https://user-images.githubusercontent.com/44238492/203831227-af1a3f58-f93f-4ff0-96d5-6bca85db7aff.png

[Image removed by sender. imagen]https://user-images.githubusercontent.com/44238492/203831748-9664a397-a6a7-4b93-8db2-a67bf895b521.png

input_locations.ziphttps://github.com/VHeimhuber/InletTracker/files/10086199/input_locations.zip

sample_rasters.ziphttps://github.com/VHeimhuber/InletTracker/files/10086228/sample_rasters.zip

— Reply to this email directly, view it on GitHubhttps://github.com/VHeimhuber/InletTracker/issues/3, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL7FVJRBO4XK6M5WA3VZIE3WJ6KG5ANCNFSM6AAAAAASKSKIRA. You are receiving this because you are subscribed to this thread.Message ID: @.***>