Using the REST service URL to build maps and apps is no longer a best practice. Here’s what you’re missing out on if you’re not using the ArcGIS Online Item…
How many of us have done this?
It’s the typical pattern we were taught to use with web GIS: find the REST endpoint; copy and paste it into your project. But when you do that, you’re just making life more difficult on yourself. What most people don’t realize is that the Item in an ArcGIS Online Portal is very different from the Service (or REST endpoint).
You can think of the Item as being a specific configuration of a Service. There can be many of these different configurations, and each has a unique ID that can be used to easily access the item anywhere in ArcGIS.
These unique configurations can add a ton of other additional valuable information on top of the baseline service, such as
- Custom cartography
- Configured pop-ups
- Improved metadata and provenance
- Raster functions
- Views (subsets of feature layers)
A Tale of Two Layers
Here’s a great example: WorldClim Global Mean Precipitation layer in Living Atlas.
From the linked item page above, we can see a detailed description of everything you’d need to know to use the layer effectively.
Open the layer in Map Viewer or ArcGIS Pro and you’ll see custom cartography that clearly defines gradients of precipitation.
The pop-up is customized to query the multidimensional information and provide a month by month graph of precipitation totals.
And when this item is added to a map and saved, you can easily get back to that detailed Item Description.
There’s not much useful human readable metadata in the Service URL. Sure, that can be added while publishing, but it’s not a user-friendly display. Not to mention, it’s much easier to edit the Item Description over time.
Open the Service in Map Viewer and we see it gets the default rainbow color ramp, which we all know is the worst! But the range of data and its distribution means the map comes out as a blue blob.
Click the map and the pop-up displays the default raster value – not nearly as informative as the Item version.
Lastly, you can’t see the connection between this layer and the detailed Item Description – you’re sent back to the REST endpoint rather than the Item Description. While you may have understood the details of the layer, someone who uses your map may not, so you’re putting them at a disadvantage, as well.
A Better Way
“So how should I be adding the layers?”, you might ask. Instead of the REST URL, look to the Item ID. Every Item has an alpha-numeric string in its URL. For the Sentinel-2 10m Land Use/Land Cover Time Series layer in Living Atlas, we see the URL is https://www.arcgis.com/home/item.html?id=cfcb7609de5f478eb7666240902d4d3d.
Copy the “cfcb7609de5f478eb7666240902d4d3d” and add it to any project.
In some cases, there isn’t an Item for a service, and that’s a whole other pattern that we need people to embrace! Luckily, creating one is pretty simple.
Configuring an Item
If you published from ArcGIS Pro into an ArcGIS Organization Portal, or if you uploaded a file directly to ArcGIS Online, good luck…you have an Item. It just needs to be configured. Once you adjust the cartography, pop-up, and aliases in ArcGIS Online Map Viewer, you can select Save in the layer options. Any customization is saved to the Item (but not the Service). We’ll follow-up with a blog and video on some of the most useful enhancements for Items that benefit users, along with making them candidates for Living Atlas.
Another important reason for using Items as a publisher is that it can help support alerting users to changes or potentially planned retirements. Read more about some of those best practices.