ArcGIS Enterprise

Scale dependent multiple datasources for a single feature layer

There are sometimes when you want to have a multi-level-geography map, as seen above, where you want to visualize an attribute at national level as well as at regional or even at neighborhood level as you zoom to larger scales in order to reveal the same information in finer details. For example, the map above shows ‘vacant housing unit rate comparing to national average’ at state level and then as you zoom in you can see the same information at county level followed by at census tracts and all the way to block-group level.

Traditional solution:

This might be something you have done many times before – the traditional approach to solve this problem is to use multiple layers, with mutually exclusive scale visibility range, where each layer represents one geographic/political unit such as states, provinces, divisions, counties, districts, tracts, blocks etc. And symbolize all layers using the same symbology. If you want, you can give it a try with this webmap – when you open it, it shows 2010 population density at US state level, as you zoom in, you will see that it shows the same information at greater details – from states to counties to census tracts to block groups. Now, if you want to change symbology e.g. to symbolize them with a different color scheme, you will run into the problem that is described below.

Problem:

The issue that we often run into with this approach is that it requires symbology set separately for each layer to begin with. And if you need to make any change to a symbol or change break values for a class breaks symbology, you need to keep repeating the same thing for all layers. It gets even harder when you want to share as a web layer and you want your end users to modify its symbology based on their needs.

Solution:

ArcGIS Pro 2.2 introduces view_scale parameter in a query layer that allows you to vary where clause or selected fields or even table name in a SQL statement based on the current map scale. We will use that to read features from different tables based on map scale. Please note, in this case schemes for all these tables must be identical as it is the case in the webmap specified earlier.

Steps:

Notes:

About

Tanu is a product engineer on Esri Mapping Team

Next Article

What’s New in ArcGIS Solutions (September, 2018)

Read this article