I would like ArcGIS Online users to have the ability to create a hosted feature layer view from publicly shared hosted feature layers that they do not own.
In my workflow, I often use public authoritative data that is maintained and updated by another organization. The data itself is useful and current, but because it is updated in the background, the layer’s visualization, pop-ups, labels, filters, and other presentation settings may change or reset after updates. This creates extra work for users who rely on that public data in their own maps, apps, dashboards, and workflows.
A common example would be public shared data that is updated on a regular schedule. I may want to use that same data source, but configure it for my specific audience by changing the symbology, setting up pop-ups, applying filters, adjusting labels, or simplifying the visible fields. However, when the source layer is updated, those settings can be affected, requiring me to reconfigure the layer again.
If ArcGIS Online allowed users to create a view of a public hosted feature layer, the original data owner could continue maintaining and updating the source data, while the consuming user could maintain their own view-specific configuration. This would allow the data to stay current without disrupting the maps and applications that depend on customized presentation settings.
This capability would be especially helpful for workflows involving authoritative public datasets, such as government boundary layers, election data, emergency management data, infrastructure data, environmental data, and other frequently updated public information.
The benefit would be that users could:
- Preserve their own symbology, pop-ups, labels, filters, and field visibility settings.
- Continue using authoritative public data without copying or duplicating the dataset.
- Reduce rework after source layer updates.
- Build more stable maps, dashboards, and applications using public data.
- Keep the source data maintained by the authoritative owner while allowing consumers to configure it for their own needs.
This would improve the usability of public shared hosted feature layers and make them more dependable for downstream applications and organizational workflows.
