Tima version:
LHS version:DeltaTima version:GeometryServer version:FMS type:
Client:
Diagnosis and Solution: This problem can occur for two reasons:
1- If it is a new orthophoto, it is very likely that something in the new file is not right, so if we go to the log of the scheduled task we can see the path where the photo is being searched for in the next most recent log (C:\Users\userexample(change it to the server username)\AppData\Local\TiMiNiNG\GeoServerLogs)
After making sure that the photo is new, we would have to validate with the geometry team that the orthophoto as such is fine in all aspects (bits, channels and others)
2 - If it is an orthophoto already used before, it is very rare that the scheduled task fails, so as in point 1, the task log must be reviewed to see what happens
Other reasons may be:
-MinIO space full (https://timsoporte.freshdesk.com/a/solutions/articles/44002345621)
Note: To confirm that the orthophoto was well processed when opening the log of the scheduled task we will see <Response [200]>
