ArcGIS Online content: hosted feature layers, web maps and how they connect

The map that went blank. Picture a Monday morning at a city water utility. Overnight, three water mains broke, and the operations supervisor opens the dashboard to plan crews. The map panel is empty, and the break counter says zero. Nothing is wrong with the pipes' data. On Friday, an analyst deleted what looked like an old duplicate layer, and it turned out to be the one the whole dashboard depended on. This happens more often than you'd think, because in ArcGIS Online a dashboard doesn't hold data itself. It sits on top of a chain of connected items. In this lesson you'll learn what those items are, how they link together, and how to change things without breaking the screen your team relies on.

What you will learn. Here's the plan for this lesson. First, you'll learn the three kinds of content that matter most for dashboards: items in general, hosted feature layers that hold your data, and web maps that decide how that data looks. Second, you'll trace the full chain, from a spreadsheet of water main breaks all the way to the map panel on an operations dashboard, so you can see what each link does. Third, you'll learn how sharing and item references travel along that chain, and why one careless delete or one wrong sharing setting can blank out a screen. By the end, you should be able to look at any dashboard and name what it depends on.

Everything is an item. In ArcGIS Online, everything you save becomes an item. A spreadsheet you upload is an item, a layer is an item, a web map is an item, and the dashboard is an item too. You'll find them all under My Content. Every item has three things worth knowing. It has an owner, the account that created it. It has an item ID, a long unique code, a bit like a serial number stamped on a fire hydrant. And it has sharing, which decides who can see it. Items connect to each other by that item ID, not by name. So renaming a layer is harmless, but deleting it removes the serial number other items were pointing to.

Hosted feature layers hold the data. The hosted feature layer is where your data actually lives. Hosted means Esri stores it in its cloud for you, so you don't run a server. Inside, the data is made of features. A feature is simply one row in a table plus a shape on the map, which can be a point, a line or an area. Think of a spreadsheet where every row also knows where it sits on Earth. For our utility, each water main break is one point feature, with fields like date reported, street, pipe size and status. Because it's hosted, the layer can answer questions such as "give me only the open breaks from today", and field crews can edit it from a phone app.

Web maps hold the look, not the data. The web map is the next link. Here's the key idea, so let's slow down. A web map doesn't copy your data. It stores a list of layers it points to, plus instructions for showing them: colours and symbols, what the pop-up says when you click a break, which layers are switched on, and where the map starts zoomed in. It also adds a basemap, the background map of streets or imagery that sits underneath your layers. A good analogy is a music playlist. The playlist doesn't contain the songs, it references them and sets the order. That's why one hosted layer of water main breaks can appear in a supervisor's web map, a public map and a crew map, each styled differently, while the data stays in one place.

How the chain connects. Let's put the pieces together. The supervisor opens the operations dashboard. The dashboard's map panel doesn't draw anything on its own. It reads a web map, and now the whole chain appears: the web map points to the hosted layer of break records and to a basemap from Living Atlas, Esri's library of ready-made maps and data. Now follow one refresh. The dashboard reads the web map, the web map fetches the basemap, then it asks the hosted layer for the open breaks. The layer returns the matching rows, and the points land on the dashboard. Every panel, from the map to the counter showing today's total, queries that same hosted layer, so all of them agree.

Worked example: water main breaks. Here's the same chain built from scratch. The water team exports a CSV, a plain spreadsheet file, of breaks with latitude and longitude columns. You upload it to ArcGIS Online, and it becomes a CSV item. When you publish it, ArcGIS creates a second item, the hosted feature layer, linked back to the CSV. Next, you create a web map, add that layer, colour the points by status, say red for open and grey for repaired, and set a pop-up showing street and pipe size. Finally, you create a dashboard and choose that web map for its map panel. Count them: how many items now exist? Four. The CSV, the layer, the web map and the dashboard, each with its own item ID.

Sharing travels down the chain. Sharing works along the same chain, and it's another common reason a dashboard looks broken. When someone opens your dashboard, ArcGIS checks their access to every item underneath it: the web map, and every layer in that web map. If you share the dashboard with the Operations group but leave the hosted layer private, the supervisor sees the frame of the dashboard with an empty map and a sign-in prompt. The fix is simple: share the dashboard, its web map and its layers with the same group. While you're in each item's Settings page, also turn on delete protection for the hosted layer. It's one checkbox, and it would have saved our Monday morning.

Living Atlas as ready-made layers. You don't have to build every layer yourself. Living Atlas gives you thousands of ready-made layers that plug into the same chain with no uploading at all. For storm response, you might add live weather warnings next to your utility outages. For traffic incidents, you could add a live traffic layer beneath your crash reports. They join your web map the same way your own hosted layers do, by item ID. One habit to build: open the item page and check who owns it and how often it updates. A layer refreshed every five minutes suits an operations dashboard, while one updated yearly belongs on a strategic one.

Common mistake: copies and deletes. Now the mistake behind our opening story. People often assume that saving a web map under a new name makes a safe backup copy of the data. It doesn't. The new web map still points to the same hosted layer, so deleting that layer breaks both maps and every dashboard built on them. The opposite trap is republishing the same CSV several times, so crews edit one layer while the dashboard reads another, and the numbers quietly drift apart. Before deleting anything, open the item page and look for where it's used, or search your content for its item ID. Keep one authoritative hosted layer, and give each audience its own view, which is a later lesson.

Exercise: map one dependency chain. Here's your task before the next lesson. Open a dashboard you use at work, or any public dashboard in ArcGIS Online, such as a service request or storm response example. Open the dashboard's item page with View item details to find the web map behind the map panel, or, if you own the dashboard, edit its map element to see which web map it uses. Open that web map's item page and list every layer in it, writing down each layer's item ID, owner and sharing level. Then compare those sharing levels with the dashboard's own. Flag any layer that's shared more narrowly than the dashboard, because that's a blank map waiting to happen. Keep your notes handy, since next lesson we'll prepare the fields inside these layers.

Recap. Let's recap. First, hosted feature layers are where your data lives, with one feature per record, like one point per water main break, and they answer live queries. Second, web maps don't copy data. Like a playlist, they reference layers rather than copying them, and add symbols, pop-ups, visibility and a basemap, often from Living Atlas. Third, a dashboard reads a web map, which reads its layers, so viewers need access to every item in that chain, and deleting one link blanks everything above it. If you can sketch that chain for any dashboard you use, you already understand ArcGIS Online content better than many people who build with it daily.