Hi Mike, OK, sorry, I didn't know. Email sent. I just did a few searches on C:\FVS\Training Guides\PacificNorthwestRegionFVSTrainingGuide.pdf and it doesn't document internal details of file handling that I can see. While not deleting "foo RunGUID baz.notAnFvsExtension" or just "RunGUID.notAnFvsExtension" is certainly basic behavior it doesn't seem to have been implemented. I would certainly hope a user who modified the .key or roundtripped on the .Rdata wouldn't be surprised if those files got ...
FVS 20200713 silently deletes user data
Looks good so far as data flow (I'll take a close look at the predicted growth rates tomorrow), thanks Mike.
Hi Mike, thanks. I was able to install my uploaded xlsx after deleting the FVS_GroupAddFilesAndKeywords sheet from the workbook. However, a trivial no action run comes back with all zeros because FVS doesn't see any of the trees on the plot (it's a trivial setup: 1 stand, 1 plot, <200 trees) even though a look in FVS_Data.db shows they all got copied into the FVS_TreeInit table as expected, the STAND_ID column matches with the FVS_StandInit table, and the stand expansion factor matches the plot size...
xlsx import hangs in Checking FVS_GroupAddFilesAndKeywords
Panasonic G7 is missing from data/db/mil-panasonic.xml