philipbaileynar
commented
5 years ago @fluviotect thanks again for documenting this in detail.
We have found and fixed the issue. There is a new release (7.4.3) that includes the fix.
The problem was related to projects with mixed units. So in your case, feet for linear units and yards for areas and volumes. The problem would have also manifested itself for any mix of units such as metres for linear units and square kilometres for areas.
Please test 7.4.3 when you get a chance and report back your findings.
fluviotect
I tested 7.4.2 today by re-running change detection and segregation on data I've been running in 7.4.1.0 (related to issues #352 and #355).
volume values are very low (by 3 orders of magnitude)
Reproduction steps
chart is plausible:
tabular values are not:
I ran a segregation for a unit where I know rough construction quantities (should be a minimum of 85,000 cu-yds +/-):
I checked some of the xml files:
parent gcd presents same value as table in Arc Add-in viewer
child xml (project_name\Analyses\CD\DoD0001\BS\BS0003\c003_summary.xml) presents different values (of similar magnitude though)
Considering the child xml thinks it's reporting cu-ft and given recent issues with unit conversions, I checked tabular value by 27, 27^2, 35.3, and 35.3^2. All are too low.
If we assume 85,000 as the right number and divide by the reported value for thresholded volume lowering (52.72) = 1612
Which has no implicit meaning, but if we divide 1612 into 43,560 (= ft^2 per acre) we get 27. Which is the number of cu-ft in a cu-yd. Could be coincidence, but could be a good place to see if there's an issue with how unit conversions are cascading (or not).
Cheers, Will
(I suspect this is related to issue #352, but I started a new issue because now running in a different version)