5.2 Scale Ranges & Performance
Key Takeaways
- Visible scale ranges control at what zoom levels a layer is drawn.
- Reference scales lock symbology sizes to a specific map scale.
- Generalization and scale dependencies significantly improve drawing performance.
- Display caching is critical for fast navigation in complex maps.
Visible Scale Ranges
Visible scale ranges define the scales at which a layer is turned on and drawn in the map. Setting appropriate In Beyond (maximum scale) and Out Beyond (minimum scale) values is one of the most effective ways to manage map performance and cartographic clarity. If a user zooms out beyond the specified minimum scale, the layer is not drawn, saving the application from attempting to render potentially millions of overlapping features.
Setting Scale Ranges
To set a scale range, you can:
- Right-click the layer and go to Properties > General to set the In Beyond and Out Beyond scales.
- Use the Visibility Range group on the layer's Appearance tab on the ribbon.
- Right-click the layer and choose Set Minimum Scale or Set Maximum Scale based on the current map scale.
Reference Scale
By default, symbols in ArcGIS Pro draw at a constant screen size (e.g., a 10-point point symbol remains 10 points on the monitor regardless of how far you zoom in or out). However, setting a Reference Scale locks the size of symbols and text to a specific map scale. As you zoom in, symbols get larger; as you zoom out, they get smaller, behaving as if they were printed on a physical map.
To set a reference scale, right-click the map name in the Contents pane and choose Set Reference Scale. Individual layers can opt-out of the reference scale via their layer properties.
Generalization and Map Performance
When visualizing data at small scales (zoomed out), drawing highly detailed geometry (like a coastline with thousands of vertices) is inefficient and visually indistinguishable from a simplified line. Generalization involves simplifying geometry for display at smaller scales.
Techniques for Performance
- Generalize tools: Run geoprocessing tools to create simplified versions of complex layers for use at small scales.
- Scale-dependent rendering: Combine generalized layers with scale ranges so the simplified layer draws when zoomed out, and the detailed layer draws when zoomed in.
- Display Caching: ArcGIS Pro uses display caching by default. It keeps drawn areas in memory so that panning and zooming within the same extent is instantaneous. You can clear the cache in the Map Properties or application options if data changes are not reflecting.
- Hardware Acceleration: ArcGIS Pro is a true 64-bit, multithreaded application that relies heavily on the GPU (Graphics Processing Unit). Ensure DirectX or OpenGL settings are optimized in the application options.
Advanced Performance Considerations
Let us expand on performance tuning in ArcGIS Pro 3.x to meet our deep-dive requirements. Beyond simple scale ranges, one must consider spatial indexing and attribute indexing. While scale ranges prevent drawing, if the map is within the visible scale, the database must rapidly find the features in the current viewing extent. This is handled by the spatial index. If a layer is drawing slowly, rebuilding the spatial index (using the Recalculate Spatial Index tool) is a primary troubleshooting step. This is especially true for file geodatabases that have undergone extensive editing.
Another critical factor is cartographic complexity. Multi-layered symbols, markers with halos, and complex dashed line patterns require significantly more processing power to render than simple solid strokes or fills. When authoring maps for web sharing or for use on lower-end hardware, simplifying symbology is just as important as setting scale ranges. For instance, a dashed line requires the rendering engine to calculate the dash intervals along the geometry continuously. At small scales, these dashes blur together anyway. Using a scale-based display filter or scale-dependent layer to swap the dashed line for a solid line at small scales improves both aesthetics and performance.
Labeling also heavily impacts performance. The Maplex Label Engine is incredibly powerful but computationally intensive. To optimize labeling:
- Set scale ranges on label classes. Never attempt to label all streets in a county when zoomed out to the county level.
- Use fast label placement options where possible.
- Use SQL queries in label classes to label only the most important features (e.g., label only interstates at small scales, then local roads at large scales).
- Consider converting labels to Annotation if the map scale is fixed or if label placement requires manual, non-dynamic adjustments.
Feature transparency and blending modes (a modern feature in ArcGIS Pro) are processed by the GPU. While generally fast, excessive use of blending modes across many layers can cause a bottleneck on systems with weaker GPUs. If users experience 'lag' while panning a map with many blended layers, disabling blending or reducing transparency temporarily can isolate the issue.
When dealing with very large enterprise datasets, consider utilizing Map Services instead of direct database connections. A Map Service offloads the rendering workload to the ArcGIS Server, sending only the finished image tile back to ArcGIS Pro. This is highly efficient for complex reference layers (like parcel fabrics or utility networks) where the user needs to see the context but does not need to edit the geometry directly in that specific map view.
For the exam, be prepared to diagnose performance issues. If a question asks how to improve the drawing speed of a highly detailed county boundary layer when viewing the entire state, the correct answer will likely involve setting a minimum scale (Out Beyond) or using a generalized version of the layer. If the question involves symbols getting too large and cluttering the map when zooming out, the answer is to set a Reference Scale.
Furthermore, understand the concept of 'Scale Ranges' within symbology itself. In ArcGIS Pro 3.x, you can enable scale-based sizing within the Symbology pane. This allows a single symbol class to have different sizes at different scales without creating separate label classes or layers. For example, a point could be 12pt at 1:1,000, 8pt at 1:10,000, and 4pt at 1:50,000. This provides smooth transitions and reduces clutter, leveraging the same underlying principles of scale management but applied directly to symbol properties. This is a very common topic on modern ArcGIS Pro exams as it highlights a workflow improvement over ArcMap.
A user notices that their point symbols representing fire hydrants overlap and obscure the map when zooming out to view the entire city. They want the symbols to automatically shrink in size as they zoom out. What should they configure?