The Zonal Adjustment Editor may be used to edit data in the Tree View or the Table View. These views have similar functionality, but with a few distinctions. The Tree View aggregates values to larger time spans for reporting and editing multiple dates, whereas the Table View just shows the actual time increments of the data. With either of these views, the user can make adjustments to the table through direct text entry, or the right-click popup menu. The right-click popup menu includes the Multiply, Linear Fill and Repeat Fill options, with the Linear Fill and Repeat Fill options only available when multiple time-steps are selected. Multiply will allow the user to directly enter a multiplication factor. Linear Fill will interpolate between the first and last selected row, and Repeat Fill will repeat the value in the first selected row for all selected cells. The right-click menu is displayed in the image below.

After a value is changed in the table, the affected cells will be bolded, and an edit is added to the stack of edits in the Map Window (see Edit Tracking Tool for details about the Edit Stack). This edit will be applied to all TIN points that are within the zone. In the case of Grids, the edit will be applied to all grid cells where the center point falls within the zone. Adding this edit to the Edit Stack will initiate a recompute of the data in the Map Window, applying all active edits in the Edit Stack. This will make the spatial display in the Map Window update in real-time based on modifications to the Zonal Adjustment Editor. Alternatively, if the data is edited through the Map Window while the Zonal Adjustment Editor is open, the Zonal Averages will be recomputed, and the table will be updated.

While the Zonal Adjustment Editor is open, it is recommended to avoid making edits via the Right Click context menu in the Map Window (Ad-Hoc Operations in the Map Window Right-Click menu). Although simultaneous Map Window and Zonal Adjustment Editor edits are supported, it will lead to two issues:

  1. All bolding of values within the table will be cleared. After the data is recomputed, the Zonal Adjustment Editor data is updated, losing the change tracking within the table.
  2. Values in the Zone Adjustment Editor table will be recalculated, causing them to change.

Tree View

Below is an image of the Tree View in the Zonal Adjustment Editor for precipitation data. In this image, the January 2nd 2024 node is expanded, showing the individual hours within that day. Note that for the Upper zone, there were 8.793 inches of precipitation in January 2024, with .457 inches falling on January 2nd 2024, with all of that precipitation falling in the last 5 hours of that day. In this scenario, values can be altered on the hourly, daily, monthly or annual rows. If edits are performed on rows with timespans longer than one hour (termed "Roll Up" rows), the edits will be disaggregated temporally based on the Edit Disaggregation Method. Illustrative examples are provided in the following subsections.

Roll Up Row Edits

Below are two examples of editing with Roll Up rows based on the example table in the previous section. Note that both edits change the value on the "02Jan2024" from .457 inches to 1 inch, but differ in the applied disaggregation method. In the first image below, the edit was applied using Normalized disaggregation. In the second image below, the edit was applied using Uniform disaggregation. In both images, the "02Jan2024" was changed to 1 inch, but note that the hourly rows are different between the two disaggregation methods. In the Normalized disaggregation, the adjustments are isolated to the hours that originally had data, and the values are increased with the same proportion. Alternatively, the Uniform disaggregation led to a constant value of .042 inches being set for each hour, leading to a total of 1 inch of precipitation for that day. 

The following figure shows changing "02Jan2024" from .457 inches to 1 inch using Normalized disaggregation.

The following figure shows changing "02Jan2024" from .457 inches to 1 inch using Uniform disaggregation:

Multiple Cell Selection

In the Zonal Adjustment Editor table, selecting multiple cells is limited to consistent intervals. For example, if the user clicks on the "02Jan2024 12:00 - 13:00 GMT", that is an hourly row, and selection will be limited to hours within that day. This selection limitation is to prevent errors when making group edits via the right-click popup menu. If the user was allowed to select the "02Jan2024" row and the hours within that day simultaneously, then clicked the multiply option, it would not be clear if the multiplication is applied to the daily or hourly rows. Since the daily and hourly rows are mathematically consistent, they must be edited independently. An example of this selection limitation is shown below, where the user clicked on the cell containing .062, then dragged the mouse down across the "03Jan2024" row, but the selection was stopped at the "02Jan2024 23:00 - 24:00 GMT" row.

Table View

In the example above of hourly data, the Table View shows all of the hours of the data without any "Roll Up" rows. The Table View has two distinct benefits in comparison to the Tree View: 1) The progression of the hourly data across multiple days is easier to view and 2) The user has no cell selection limitations, allowing for editing data across multiple days. The image below illustrates the benefit of the Table View, showing the hourly data progressing from 02Jan2024 into 03Jan2024, and allowing selection across the transition between days.

Partial Data Overlap

It is possible to load data into the Map Window that does not completely overlap the specified zones. In this case, the incompletely overlapping zone column will be highlighted in yellow, as shown below. When there is partial overlap of the data, the presented zonal averages are for the area of intersection between the zone and the data. Any edits performed on that zone will apply to the intersecting area between the zone and the data. If there is no overlap between the zone and the data, the cells in that column will be filled with NaN. In this case, the data is not editable, as the Zonal Adjustment Editor cannot change the extents of the data.