Common problems and solutions
1)Daily push Newly acquired data including ZY-3, GF-1, and GF-2 image that within users authorities.
2)Default metadata push time: 11.30PM every day. Users can check metadata information in the database.
3)Default image data push time: after finishing the metadata push. Basically before 12.00pm.
To change the storage places is not recommended. It can cause data export problem that in the data query system. Under the conditions of hard disks insufficient space or any other factors that stop the normal data push, users can modify the storage path by following the steps:
1)Use the text edit tool to open the data push system configuration file,(The path is: the system repository path/ClientPush/bin/config /config.properities.) modify the paths of diskImage(quick view repository location) and diskTar(image repository location ). P.S. please be sure the folders are existed before modifying and the folders’ name should not include Chinese characters.
2)Use the text edit tool to open the data query system configuration file, (The path is: the system repository path/ImageServer/bin/config.json.) modify the paths of imagedir(quick view repository location) and tardir(image repository location ). P.S. please be sure the folders are existed before modifying and the folders’ name should not include Chinese characters.
3)After finishing the above steps, please be remember to restart the services of clientApp and ImageServer.
It is not recommended to move the downloaded data. It can cause local download problem .
Usually the data push time is fixed, this assure data are pushed in time and accurate. In case of special circumstances, the data push time can be changed following the steps of: Type in “localhost:3000” in a browser window, find the metadata push page, click start, then metadata will be pushed right away and image data follow up.
It won’t. The server's abnormal shut down can cause the interruption of data downloading, but the downloading would be connected again when the server restart. The breakpoint resume function in the push system ensures data integrity.
1)The problem could be caused by services unexpected stop. Try to restart ImageServer service or MongoDB service.
2)If the problem can't be solved using the above methods, contact us.
1)For the quick view imagery interruption, try to restart clientserver to solve.
2)For the image interruption, try to restart clientserver to solve.
3)For the batch download interruption, i.e. The corresponding batch data in database is not the same as the downloaded data, contact us to solve.