Map Image Layer or Layers

[LanceCole]

We are getting ready to publish a new set of web maps and apps.  For testing and development, we published to AGOL our different layers or layer groups in a single Map Image Layer.  We then only include needed layers or layer groups in the maps to be published.  There are about 120 layers in 10 groups.  Some groups are broken down into subgroups so there are about a total of 15-18 groups of data in total.  Below is a screenshot small part of the layers in the single Map Image Layer.

Some maps published for FieldMaps may only have a single layer being used; whereas, our default public web app includes almost everything we want to publicly expose.  We are utilizing a hybrid approach with our data being hosted on an enterprise deployment and exposed to AGOL to be consumed by published maps and apps on AGOL.

Would it be better to publish multiple Map Image Layers by a group rather than a single one with everything included? 

[RussRoberts · Accepted solution]

I would definitely recommend breaking it up.

Is it really usable to the user to try and find a layer inside 120 inside a map/app? Are these layers you would provide on an open data sight or more focused web maps/apps?

Also when you have to add/update one layer you are touching the entire service which adds some level of risk to maintain this large service. 

[LanceCole]

Thanks Russell.

We will break it down into the 15 to 18 groups of data and host those as individual Map Image Services.  The majority of the data will be consumed by focused web maps/apps that only utilize a small number of layers.  There is one large “default” map that has about 80% of the layers available but only 10-15% turned on by default.

I agree maintenance would be easier and safer.  

[RussRoberts]

Also if you move to more online - Map Viewer (not Classic) supports authoring sub group layers too so if you are using more feature layers than map image layers you can create a nested group structure within the web map.