Projects where the area and volume units are not direct equivalents of the linear units (i.e. square and cubic yards used with rasters in feet) were causing problems. This code fix ensures that areas and volumes are handled consistently in these cases.
Again, projects consistently using metres (i.e. with metres squared and metres cubed) were not affected.
Note that this change also involved disabling the ability to change the project area and volume units after the project is created. (So as not to cause a problem when writing values in one set of units and reading them in another.)
Related to #358
Projects where the area and volume units are not direct equivalents of the linear units (i.e. square and cubic yards used with rasters in feet) were causing problems. This code fix ensures that areas and volumes are handled consistently in these cases.
Again, projects consistently using metres (i.e. with metres squared and metres cubed) were not affected.
Note that this change also involved disabling the ability to change the project area and volume units after the project is created. (So as not to cause a problem when writing values in one set of units and reading them in another.)