- Messages
- 1,606
- Country
Arno,
I have dozens of tf2 files based on hundreds of square kilometers, thousands a image samples and thousands of sample points. As a test, I would like to combine them into one large tf2 file - sort of like the large database we were talking about and see if this provides enough data to detect properly in the geographic area I am working on (currently the state of California, USA). I imagine a little app or selection in scenProc to combining tf2's into one would be the best way. And I assume creating this large of a file may take hours to process? One that would need to be ran on its own and not part of a script with lots of other steps (like combining and then immediately into detection and exports). If it shows promising results, this could be an option for the end-user to create their own data bases rather than waiting on you to collect 10's of 1,000's of samples.
Question - one observation I have noticed, when I continue adding sample images and sample points, as I click on "save" it will take a little longer each time to run the algorithm. It starts out instantly saving and then a few seconds longer as I continue to add. My typical wait time can run up to 1-2 minutes each time I save/update a file.... that's typically a few dozen images and 100's of sample points. That's fine, I am used to that and not sure if there is a way to improve the processing speed. I again suspect the process of combining dozens of files which may take several hours to process (hopefully no crashes!). My question is once combined into a single tf2, the processing of a detection script will also take hours for detection or all the hard work has been done beforehand? Or, running the tf2 detection time-wise will be somewhat "normal"? For me "normal" is running detection at about 7 minutes per a 30 square kilometer image. Which is ok but if it takes several hours per image... well this process would not be applicable. I guess the test will reveal.
This test is for vegetation detection only. If successful, then try the same for water detection.
Thoughts on this idea?
I have dozens of tf2 files based on hundreds of square kilometers, thousands a image samples and thousands of sample points. As a test, I would like to combine them into one large tf2 file - sort of like the large database we were talking about and see if this provides enough data to detect properly in the geographic area I am working on (currently the state of California, USA). I imagine a little app or selection in scenProc to combining tf2's into one would be the best way. And I assume creating this large of a file may take hours to process? One that would need to be ran on its own and not part of a script with lots of other steps (like combining and then immediately into detection and exports). If it shows promising results, this could be an option for the end-user to create their own data bases rather than waiting on you to collect 10's of 1,000's of samples.
Question - one observation I have noticed, when I continue adding sample images and sample points, as I click on "save" it will take a little longer each time to run the algorithm. It starts out instantly saving and then a few seconds longer as I continue to add. My typical wait time can run up to 1-2 minutes each time I save/update a file.... that's typically a few dozen images and 100's of sample points. That's fine, I am used to that and not sure if there is a way to improve the processing speed. I again suspect the process of combining dozens of files which may take several hours to process (hopefully no crashes!). My question is once combined into a single tf2, the processing of a detection script will also take hours for detection or all the hard work has been done beforehand? Or, running the tf2 detection time-wise will be somewhat "normal"? For me "normal" is running detection at about 7 minutes per a 30 square kilometer image. Which is ok but if it takes several hours per image... well this process would not be applicable. I guess the test will reveal.
This test is for vegetation detection only. If successful, then try the same for water detection.
Thoughts on this idea?