Geodatabase Regions

To understand Geodatabase Region Resources (GRRs), we need to step back to discuss how a work order is assigned to a designer in the first place.

IMPORTANT:

The topics in this help chapter apply to you if your geodatabase uses the Geometric Network (GN). If you are on the GN, create your GRRs in Solution Center > Designer > Mapping > Geodatabase Regions.
If your geodatabase uses the Utility Network (UN), do not create your GRRs here. Instead, create them in Solution Center > Feeder Services > Mapping > Geodatabase Regions. See the Feeder Services topic Configure Geodatabase Regions for more information.

When a work order is created, it includes a design address or XY coordinate. The application uses that address or location to figure out which feeder (in electric) or design region (in gas) contains the upcoming work. Then, the application packages all the existing network features in that feeder or region and includes them in the design. This is what allows the designers to snap into the existing network, but technically they are snapping into a subset of the network. Using a subset enhances performance, as most often designers do not need the entire network in the “live” map in order to do design work. But, this subset constricts designers to the feeder or region originally associated with the work order, and they are not able to design against or snap into nearby feeders or regions.

With that said, there are times when a designer needs to “bring in” an adjacent feeder (in electric) or design region (in gas) to assist in the design. They use a tool called the Add Data tool, and then they are able to import a feeder or region that was not originally included in their design. The GRRs inform the Add Data tool. In other words, when designers are bringing in additional feeders or regions, they are interacting with the GRRs you create in this subtab. The GRRs are extracted and saved in the design storage, so users do not have to wait for the extraction process.

When configuring GRRs, keep the following points in mind:

GRRs are snapshots of a Design Region/Feeder. When you create a GRR, you are essentially capturing the state of the Design Region/Feeder at a specific time.
The application knows what features and fields to include based upon the Schema.
The application uses the Structure Buffer Radius to determine which structures to include in the GRR. This radius is set on the Electric Options or Gas Options.
“Feeders” are derived from the electric network via a feeder trace. “Regions” are drawn polygons that can surround multiple feeders, gas pressure zones, geographic areas, etc. Gas exclusively uses regions. Electric can use a combination of feeders and regions.
As the user brings in additional feeders or design regions, the application does not duplicate existing components. It uses the Global ID field to ensure components are not duplicated.
If there are changes to either the features within a Design Region/Feeder or the shape of the polygon for a Design Region, those changes are not captured in the GRR until another snapshot is taken. This is why you should Schedule Updates for Geodatabase Regions.
Changes to either the Design Region/Feeder state or the GRR state have no impact on existing designs. This is because existing designs gathered their features upon their prior initialization.
- The Add Data tool is the only way GRR updates can be loaded into existing designs. An updated GRR can be selected from the Add Data tool again, but the only updates that are pulled in are new features. Any existing features (using Global ID as the key) are not updated.

In short, in this subtab you create regions that give your designers the opportunity to import more network information into their design. Further, you schedule how often the regions update from the geodatabase.