10 ArcGIS Features Most Organizations Never Use (But Should)

The Features Hiding in Plain Sight

Most organizations use about 20% of ArcGIS. They publish web maps, run a few geoprocessing tools, maybe collect data with Field Maps. Meanwhile, entire capabilities sit dormant in the same license they are already paying for.

After years of working on the ArcGIS platform from the inside, I can tell you: the gap between what organizations pay for and what they actually use is enormous. These ten features consistently deliver outsized value when teams finally discover them.

1. Attribute Rules

Attribute rules are stored expressions that run automatically when features are edited — think database triggers, but for your geodatabase. They execute at the geodatabase level, which means they enforce data quality regardless of whether the edit comes from ArcGIS Pro, a web app, or a Python script.

Three types exist:

Calculation rules auto-populate fields (e.g., concatenate address components into a full address string)
Constraint rules reject invalid edits (e.g., prevent a pipe diameter below 2 inches)
Validation rules flag existing data that violates conditions (batch QA without blocking edits)

A water utility we advised reduced their data QA review time by 60% after implementing constraint rules on their hydrant feature class. Editors literally could not enter invalid data anymore — the geodatabase rejected it before the edit committed.

Read our deep dive on attribute rules for implementation steps.

2. Arcade Expressions Across the Platform

Most people encounter Arcade in pop-ups. They write a simple expression to format a date or concatenate two fields. Then they stop.

Arcade runs in at least 12 different contexts across ArcGIS:

Pop-ups (the obvious one)
Symbology (data-driven symbol properties)
Labels (conditional logic, multi-line formatting)
Attribute rules (geodatabase-level automation)
Field Maps (calculated fields, conditional visibility)
Dashboard indicators and gauges
FeatureForm widget in the Maps SDK
Feature reduction (clustering expressions)
Constraint expressions in Survey123
Filter expressions in web maps

The real power is using Arcade’s FeatureSetByName() function to pull data from other layers within an expression. A pop-up on a parcel can query the permits layer, count active permits, and display the result — no custom widget, no API calls, no code deployment.

3. Utility Network

If your organization manages linear infrastructure (electric, gas, water, sewer, telecom) and you are still using geometric networks or legacy schematics, you are running on architecture that Esri has stopped actively developing.

The Utility Network is the modern replacement:

Network topology with dirty area tracking — edit a pipe segment and the system knows exactly which connected features need revalidation
Subnetwork management for tracing pressure zones, electrical circuits, or fiber routes
Terminal connections model multi-port devices (transformers, switches, splitters) accurately
Named trace configurations let you save and share complex trace operations as one-click tools

Migration from geometric network to utility network is non-trivial, but the analytical capabilities justify the effort. One telecom client cut their fiber route analysis time from 4 hours to 15 minutes after migrating.

4. Versioned Editing with Branch Versioning

Traditional (now called “legacy”) versioning has served ArcGIS users for decades. Branch versioning, introduced with the utility network and now available for any feature service, modernizes multi-user editing:

Works through services (web and Pro), not just direct database connections
Named versions are lightweight — no SDE compress cycles needed
Conflict detection and resolution happen at the feature level
Version management REST API enables programmatic workflows

If your team still runs weekly SDE compress jobs and dreads state tree growth, branch versioning eliminates that entire maintenance burden.

5. ArcGIS Notebooks (Hosted Jupyter)

ArcGIS Online and Enterprise both include hosted Jupyter notebooks with the ArcGIS API for Python pre-installed. Many organizations pay for separate Jupyter infrastructure while ignoring the one built into their existing platform.

Practical applications beyond basic scripting:

Scheduled notebooks run ETL workflows on a timer — pull data from an API, clean it, publish to a feature service. No separate ETL tool needed.
Advanced analytics using scikit-learn, TensorFlow, and other libraries available in the Standard and Advanced runtimes.
Content management automation — bulk update web map pop-ups, migrate symbology across services, audit sharing permissions.
Reporting with matplotlib and pandas, exported as HTML or PDF directly from the notebook.

The Standard notebook runtime includes 16 GB RAM and access to GPU-accelerated libraries. That is a legitimate data science environment included in your Creator license.

6. ArcGIS Velocity (Real-Time and Big Data)

Velocity is an add-on, not included in base licensing — but organizations that have ArcGIS Online often qualify for it and do not realize it. Velocity handles:

Real-time analytics: Ingest streaming data from IoT sensors, GPS trackers, or message brokers (MQTT, Kafka, Azure Event Hubs). Apply geofences, detect incidents, trigger alerts.
Big data analytics: Process millions of records with distributed spatial analysis — point-in-polygon joins at scale, space-time pattern mining, hot spot analysis on massive datasets.
Feed outputs: Push processed results to feature layers, streams, or external systems in real time.

A transit agency using Velocity to track bus locations in real time can trigger geofence alerts when buses deviate from routes, calculate real-time ETAs for passenger displays, and archive historical GPS data for route optimization — all within the ArcGIS ecosystem.

7. Oriented Imagery

ArcGIS Pro 3.0+ includes oriented imagery support that most teams overlook entirely. If your organization collects street-level photos, drone imagery, or inspection photographs, this capability links those images spatially:

Photos are georeferenced with camera position and orientation
Click a feature on the map, see all photos that capture it from any angle
Navigate through a scene using photo sequences (similar to Google Street View, but with your own imagery)
Measure distances and heights directly from oblique photos

DOTs using this for bridge inspections can view inspection photos in spatial context, measure crack widths from oblique imagery, and track changes over time — without leaving ArcGIS.

8. Data Reviewer

Data Reviewer is an extension for ArcGIS Pro that automates quality assurance. It goes beyond attribute rules by checking spatial relationships, topological integrity, and cross-layer consistency:

Find features that violate domain values or contingent value rules
Detect spatial anomalies: duplicate geometry, features outside expected boundaries, invalid polygon ring orientation
Run batch validation across entire datasets and generate correction reports
Track QA status with lifecycle management (discovered, reviewed, corrected, verified)

For organizations subject to data standards (FGDC, NENA for 911, or internal SLAs), Data Reviewer turns ad-hoc QA into a systematic, auditable process.

9. Parcel Fabric

County assessors and land records offices often manage parcel data as simple polygon feature classes with no topological integrity. Parcels overlap, gaps exist between adjacent lots, and subdivisions break the geometry of parent parcels.

The ArcGIS Parcel Fabric solves this:

Topologically integrated parcels with shared boundaries — edit one boundary and both adjacent parcels update
Legal description support with COGO (coordinate geometry) tools for metes-and-bounds entry
Record-driven workflows track which survey, plat, or deed justified each parcel change
Merge, split, and remainder operations maintain full lineage

Moving from polygons-in-a-feature-class to a proper parcel fabric eliminates the chronic boundary discrepancies that plague assessor offices and reduces parcel maintenance time by 40-50%.

10. ArcGIS AllSource (Intelligence Analysis)

AllSource (formerly ArcGIS Pro Intelligence) brings intelligence analysis workflows into ArcGIS Pro. While marketed toward defense and intelligence, the capabilities apply to any organization doing investigative analysis:

Link charts visualize relationships between entities (people, places, organizations, events)
Timeline views plot events chronologically alongside spatial analysis
Entity extraction from unstructured text (reports, documents, social media)
Structured analytical techniques (SATs) built into the workflow

Law enforcement agencies, financial crime units, and corporate security teams use AllSource for investigations that require connecting spatial patterns with relationship networks.

Getting Started

You do not need to adopt all ten simultaneously. Start with the capability that addresses your biggest current pain point:

Data quality issues? Start with attribute rules and Data Reviewer.
Multi-user editing conflicts? Evaluate branch versioning.
Manual ETL processes? Set up a scheduled ArcGIS Notebook.
Underutilized field photos? Try oriented imagery.

At GeoLever, our platform optimization services start with an assessment of your current ArcGIS usage against your license entitlements. Most organizations discover they are paying for capabilities they never configured. We help close that gap.

Frequently Asked Questions

Do these features require additional licensing?

Most of them do not. Attribute rules, Arcade, branch versioning, ArcGIS Notebooks, oriented imagery, and parcel fabric are included with standard Creator licenses. Data Reviewer and AllSource are separate extensions. Velocity and Utility Network require add-on licensing. Check your Esri ELA or contact your account manager for specifics.

Can I use these features with ArcGIS Online or only Enterprise?

Attribute rules, Arcade, ArcGIS Notebooks, and Velocity work with both AGOL and Enterprise. Branch versioning, Utility Network, Data Reviewer, Parcel Fabric, and AllSource require ArcGIS Pro connected to Enterprise (or Enterprise feature services). Oriented imagery works in both environments.

How long does it take to implement attribute rules across an existing geodatabase?

For a moderately complex feature class (20-30 fields, 5-10 rules), expect 2-4 days including testing. The rules themselves are Arcade expressions — the time goes into defining the business logic, testing edge cases, and communicating changes to editors who will encounter the new constraints.

Is branch versioning compatible with existing SDE versioned workflows?

No. Branch versioning and traditional (SDE) versioning are mutually exclusive on a given feature dataset. Migration requires unregistering from traditional versioning, migrating to branch versioning, and updating all client connections. Plan this as a deliberate migration project, not a casual switch.

Want help identifying which underused capabilities would deliver the most value for your team? Book a discovery call with GeoLever and we will assess your current license utilization.