Bug
The Storage Capacity tool returns different volume results based on how the input polygons are segmented.
| Bug ID Number | BUG-000157112 |
|---|---|
| Submitted | March 30, 2023 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS Pro |
| Version found | N/A |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | As Designed |
Additional Information
Thank you for reporting this issue. The problem described with a polygon being segmented differently, resulting in a different output volume, is actually the expected behavior of the Storage Capacity tool. The Storage Capacity tool documentation is to be enhanced in a future release for a clearer outline of how the tool works. In the situation described, there are two important points to consider. (1) Each volume increment is calculated between the minimum elevation of the zone and the elevation value listed on each entry of the Elevation column of the Storage Capacity output table. Note that the corresponding Volume value is not the volume for the section between each elevation increment but the accumulated volume. This means that the total volume of a zone is the last entry in the Storage Capacity output table for that zone (for example, the entry with the highest elevation value for that zone). Add these last entries for each zone to get the total volume for all zones. (2) It is not expected to get the same volume for an area when it is one zone vs. many zones. This is because the minimum and maximum elevation values change based on how the overall area is segmented. The volume of each zone is calculated based on the individual zone's minimum and maximum elevation; think of the difference between the minimum and maximum as the height of the total volume. This is an important point because the Storage Capacity tool assumes that the edge of each zone has a value equal to the zone’s maximum elevation. For example, there is a polygon with a maximum elevation of 4m and a minimum elevation of 0m. Split this polygon into two zones: the first zone has a maximum elevation of 4m and a minimum elevation of 0m, while the second zone has a maximum elevation of 2m and a minimum elevation of 0m. That second zone only calculates volume between 0m and 2 m, while the original polygon essentially includes that volume 'above' the second zone's maximum, the volume between 2m and 4m of elevation.Steps to Reproduce
Bug ID: BUG-000157112
Software:
- ArcGIS Pro
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App