Term |
Description |
|---|---|
Asset |
Resources/Operating facilities in a Utility Network |
Attribute data, or Properties of objects represented in a geographical information system (GIS). Attribute data are data without a specific spatial reference such as, for example, in the case of land owned by the owners or, in the case of woodland, the tree species. |
|
Chart |
A graphical representation of data, facts or information. |
When using this mode, only the feature templates that can be associated with the desired object from the network topological point of view are offered when creating new features. |
|
Coded Value Domain |
A type of attribute constraint that restricts values to a predefined list of options, where each option has a code and description. Functions like a drop-down menu with specific choices. •Code 1 = "Steel" •Code 2 = "Plastic" •Code 3 = "Concrete" Users can only select from these predefined options, ensuring data consistency and preventing invalid entries.
|
Dirty Areas |
Areas with untested geometry of network features and attributes or areas where errors are displayed. See Validate topology |
Feature Layer |
A feature layer is a grouping of similar geographic features, for example, buildings, parcels, cities, roads, and earthquake epicenters. Features can be points, lines, or polygons (areas). Feature layers are most appropriate for visualizing data on top of basemaps. |
A long transaction refers to an extended editing session, often spanning days or weeks, managed through versioning to avoid locking the main database. Changes are isolated until they are merged back as a single unit of work. |
|
Network Diagram |
A schematic representation of objects (e.g. pipelines of gas, water, electricity) derived from a georeferenced map. |
An OEM license is a software license that is bundled with, and tied to the specific hardware it was first installed on, such as a pre-built computer. |
|
Pane |
A pane is a dockable window in which the contents of a view (Contents pane), the content of a project or portal (Catalog pane) or commands and settings related to a functionality area (for example, the panes Symbology and Geoprocessing) are displayed. |
Portal for ArcGIS |
Portal for ArcGIS is a component of ArcGIS Enterprise that allows you to share maps, scenes, apps, and other geographic information with other people in your organization. The content that you share is delivered through a website. |
Portal item |
A portal item is an item that can be accessed through the active portal and is available in the Catalog or in the catalog pane. |
Posting writes all edits from the editing version back to the default version. Before posting, the system automatically performs a reconciliation and transfers any default version changes to the editing version. If no conflicts are found, the edits are posted. In the event of a conflict, a warning appears. You can either: •Resolve conflicts in favor of the editing version and proceed. •Cancel and resolve the conflicts manually in ArcGIS Pro before posting. |
|
Properties |
See Attribute data |
Range Value Domain |
A type of attribute constraint that restricts values to numbers within a specified minimum and maximum range. Functions like a number slider with defined boundaries. Example: Pipe Diameter attribute •Minimum value: 6 inches •Maximum value: 48 inches •Valid entries: Any number between 6 and 48 (such as 6, 12.5, 24, 36.75, etc.) Users can enter any numeric value within the specified range, allowing for precise measurements while maintaining data validation. |
Reconciliation aligns your editing version with the current state of the default version. Any changes made to the default version since your edits began are brought into the editing version. If both versions modified the same features, conflicts are detected, and a warning prompts you to either: •Resolve conflicts in favor of the editing version. •Abort the process to prevent overwriting changes from the default version. |
|
Solution |
Tailored GIS solution based on customer needs |
Styles are collections of reusable elements such as symbols and other objects that appear on maps, scenes, and layouts. |
|
Symbols |
Symbols are used to graphically describe, categorize, or evaluate geographic features and labels to search for them and display qualitative and quantitative relationships. They represent graphic elements in a layout. You can create symbols in collections that are known as Styles are designated, stored, managed and shared. |
Technical data |
See Attribute data |
Template |
Template, e.g. for capturing objects or for printing |
View |
Views are windows for working with Maps, Scenes, Tables, Layouts, Diagrams, Reports and other representations of data. A project can have many views that can be opened and closed as needed. Several views can be opened at the same time, but only one of them is active. The active view affects which tabs are displayed on the ribbon and which items are displayed in panes, e.g. in the Contents pane. |
Web map (ArcGIS) |
A web map is a 2D map that can be created, edited and used in various applications. |
Esri-specific terminology and definitions can be obtained directly from Esri .
Term |
Definition |
|---|---|
Job Management (JM) |
A VertiGIS Networks Editor feature that enables users to create, assign, track, and close jobs related to utility network data. |
JM-Group |
A group created within Job Management to represent departments or contractors. These are distinct from ArcGIS Portal groups. |
Hierarchy 1 (Single-Level) |
A group structure where workers act as both workers and supervisors, managing the full job lifecycle. |
Hierarchy 2 (Two-Level) |
A group structure with separate roles for supervisors and workers. Supervisors manage and assign jobs; workers execute them. |
Job Admin |
A user role with full privileges including creating jobs, managing users and groups. |
Supervisor |
A user role responsible for assigning jobs, managing job status, and resolving conflicts. Limited in publishing and user management rights. |
Worker |
A user role focused on executing assigned jobs. May have limited assignment rights in Hierarchy 1 but cannot publish or manage users. |
Conflict Resolution |
The process of resolving data discrepancies between job and default versions. Can be automatic or manual. |
Automatic Resolution |
System resolves conflicts based on predefined rules without user input. |
Manual Resolution |
Supervisors manually choose which version of conflicting data to retain. |
Reconcile |
The process of merging changes from a job version into the default version, resolving any conflicts. |
Post |
Final step in job closure where validated edits are committed to the default version and the job version is deleted. |
Job Board |
The interface where users view, filter, and manage jobs based on assignment and status. |
Assign to Me |
A feature allowing users (typically in Hierarchy 1) to self-assign jobs. |
Batch Reassignment |
A feature allowing supervisors to reassign multiple jobs at once to different users. |
Validation |
A quality control step to ensure edits meet topological and organizational standards before posting. |
Job Status |
Indicates the current state of a job: Active, On-Hold, Completed, or Closed. |
Overdue Job |
A job that has passed its due date without being marked as completed. |
Create Job |
The process of initiating a new job by defining its name, description, assigned users, and geographic area. |
Close Job |
The final step in the job lifecycle where the job version is reconciled, posted, and deleted. |
Validate Network |
A tool used to verify the integrity of edits before completing or posting a job. |