Will Conley provided a GCD project where the original data are all in imperial units but the DoD stats written to the GCD project file uses inconsistent units.
Here's the top of the GCD project file:
<Project>
<Name>HaulRd_2009_1pt5ft_CrossCompare</Name>
<DateTimeCreated>2019-05-18T19:10:01.6619615+12:00</DateTimeCreated>
<GCDVersion>7.4.1.0</GCDVersion>
<Description>Comparison of 1.5 ft DEMs derived from same LAS points using different DEM construction methods</Description>
<Units>
<Horizontal>UsSurveyFoot</Horizontal>
<Vertical>Foot</Vertical>
<Area>SquareFoot</Area>
<Volume>CubicYard</Volume>
</Units>
...
And then lower down here is part of just one of several DoD records. The area values are written using square feet but the volumes are written in metres cubed.
Will Conley provided a GCD project where the original data are all in imperial units but the DoD stats written to the GCD project file uses inconsistent units.
Here's the top of the GCD project file:
And then lower down here is part of just one of several DoD records. The area values are written using square feet but the volumes are written in metres cubed.
Solution
All values written to the GCD project file should be consistent, and probably using the project linear units.
Be careful fixing this issue and consider the impact to folks with legacy GCD projects.