Hi all,
Hopefully someone can help with what seems to be a very simple issue I'm struggling with. I have the Terra cache directory insalled to an SSD hard drive for outputting very large datasets. I opened Terra without the hard drive attached so Terra automatically reverted to the C drive. Now when I try to direct Terra to the old cache directory it creates a new folder rather than 'reading' the missions I had already processed. What I want to do is either get Terra to read the old directory or load my missions into the new one. If someone could provide guidance on either of these two options I'd greatly appreciate it!

Thanks,

SOLVED I just allowed Terra to create the new file directory in the same folder as the old one and then swapped the file names. Now Terra is reading the old one.

Can you elaborate on this a little more?  I am confused by "allow Terra to create a new file directory." Every time you change the cache directory, it transfers all of the jobs in the current directory to the new place. I do not want to do this. I don't want to move all of the files, I just want Terra to read to another directory or an entirely new one like you stated.

muckag7 Posted at 2022-7-31 13:24
SOLVED I just allowed Terra to create the new file directory in the same folder as the old one and then swapped the file names. Now Terra is reading the old one.

I have the same Problem.
The Data-directory including mission.db is existing at a different file location (external).

We tried everything... copying, renaming of directory etc. - but in no case the missions will be shown within Terra.

This is extremly confusing. How many GigaByte or TerraByte should our computer have to store all data on a local harddisc for ever to reuse it???

I think I found a workaround... at least for re-importing mission folders that weren't exported via Terra, but also is a way to rebuild the mission.db

1. Import a proper old one, gut a current one, or just create a new mission container that has been fully processed. One will do.


2. Copy or just move the real/target mission contents into said mission container folder.


3. Delete or rename the original real/target mission folder... (or just rename it to avoid a name conflict).


4. Rename the container mission in Terra back to your target/real mission name. (the open folders in windows will update upon refresh)


5. Properly export the real mission via Terra. Import via Terra, when ready to fully rebuild mission.db, or simply go back to step 1 and make a new container mission.


mission.db seems to only look at the WFS folder name, and then only examines the contents of said folder when you click the mountains to actually open that data in Terra.
I have a screen recording... but can't seem to upload it here... may create a share link to it later.

PS Shame on you DJI... for making mission.db so useless and risky to your designed workflow. ;)
Your current form of file/folder/mission management is barely tolerable for freeware... let alone paid enterprise software. If you must use mission.db... fine, but WHY IS IT NOT READABLE or EDITABLE with normal software?