Open lbross opened 5 months ago
See issue #305. Note that if the analysis uses the option to update plot.gis_yard_dist_ft when loading the gis data, it will overwrite the value that was originally loaded from PLOT.RDDISTCD.
We are leaning towards populating plot.gis_yard_dist_ft from PLOT.RDDISTCD. @jsfried is working from a lookup table that he created from the FIADB definitions for PLOT.RDDISTCDs. @jsfried, can you provide this table when finalized so that we can append it to this issue and have it on hand when we're ready to implement this?
RD_DIST.csv Here is the table. The codes are decoded to the upper limit, in feet, of the road distance class except for class 8 which is farther than 5 miles, which we code as -1. Users will need to be sure to set limits on the farthest distance to be considered in Optimizer for steep and not steep plots. 2640 or 5280 are recommended as maximum dist ance for ground based systems; probably 2640 for steep sloped systems. OpCost may behave badly with very large yarding distances.
From @jsfried: Not sure how often PLOTGEOM is updated but out BioSum internal fiadb_fvs_variant table hasn’t been updated in probably 5-6 years (I never though to). I now see that it does need updating because FVS tweaks its maps a bit over time, apparently, and because new plots get added when spatial intensifications are undertaken (as they were in Oregon over the last few years). Relying on a corporate source for such changes (like PLOT GEOM) would leave fewer plots unaccounted for. Going forward, I think we should source variant from the FIADB table PLOTGEOM—one more table to pull into BioSum when adding plots, I guess. This is important now that BioSum is national. We will tackle this when/after we convert the plot table to sqlite
Optional: Get the default move distance (fiadb_fvs_variant.MoveDistance_ft) as the midpoint of the road distance class in PLOT.RDDISTCD given that this distance is populated from the actual plot location, not from a point that can be up to .71 miles away.