Investigating the site index population for 4FRI I disovered that the current project version (built or upgraded to 5.10.1, not sure which) has no cases of site index populated in the BioSum generated FVSIn.DB. Could this be due to BioSum trying to override the FIADB.FVS_STANDINIT_COND value with a BioSum generated one (which could not be generated because we have never had site index roll-our-own capability for AZ)? IN projects generated in 5.10.0, I am seeing FVSIn.DB.SITE INDEX populated but not in more recent versions. What would be helpful to provide or further test to get into this? We may need to go back to the very beginning of the 4FRI project to rerun FVS if there as not a site index populated for those runs that were written up in the Billion Ton report and reported at the SAF Convention.
Investigating the site index population for 4FRI I disovered that the current project version (built or upgraded to 5.10.1, not sure which) has no cases of site index populated in the BioSum generated FVSIn.DB. Could this be due to BioSum trying to override the FIADB.FVS_STANDINIT_COND value with a BioSum generated one (which could not be generated because we have never had site index roll-our-own capability for AZ)? IN projects generated in 5.10.0, I am seeing FVSIn.DB.SITE INDEX populated but not in more recent versions. What would be helpful to provide or further test to get into this? We may need to go back to the very beginning of the 4FRI project to rerun FVS if there as not a site index populated for those runs that were written up in the Billion Ton report and reported at the SAF Convention.