Modifying the Set Visibility Range

Question

I have a service created in Enterprise 10.8.1 and Pro 2.6 where I have a maximum. visibility range set and no minimum range set.  I have loaded this into a Web Map in Portal 10.8.1.  For this ONE map I want to remove the maximum visibility range.  I have gone into the Change Style Options and slide the slider all the way to the left to show at all scales.  However, it still doesn't not display the data at a higher level than what I set in the published service.  If I change the minimum with the Change Style Options is reflects that change.  Is there a way to override this visibility setting in a web map or what you publish in the service is your only option.

I have SEVERAL other maps set up pointing to this service where I want that maximum range set and I only want to change it for just this one map.  My other only solution I have come up with is publishing an entire new service with the visibility range not set, but that seems a little much as they will just eat of more resources on the server for just one map.

DavidPike · Answer

You've not got a range on the group layer overriding a sublayer have you?

jcarlson · Answer

So, try adding the layer to a web map using its URL, and instead of the regular service URL, use the URL for the individual layer, "/MapServer/0" or whatever the layer index happens to be.

When you do that, it treats the added layer like a Feature Service, and may give you different capabilities. However, you'll lose any "fancy" symbology or labeling that the Map Image happened to use. But maybe that's more tolerable than publishing a new service for one map.

LindseyStone · Answer

This service is a published map image.  No editing capabilities.  I tried it in a brand new web map but still the same thing that it would go out further than what I defined in map prior to publishing it.

I defined the max. scale because 99% of the maps that I will use for this service will need that scale set, so I didn't want to have to set in every web map I add it too.  This is a one off case where I don't want it and I was trying avoid the need to publish ANOTHER service just for this one special map.