Saved Project Maps Layer List breaks with map service updates / changes
Essentials v4.6.1 w/ GVH 2.7 – If a layer is removed from a map service that was “saved” as a user project deleted layers still display in the project’s layer list and turn on/off (visibility check-box) for a different/incorrect layer. I believe the project is saving a layer’s index and not associating layername as part of the property value creating a misalignment between a user’s saved map-project and an updated map service.
I suggest a dialog that will inform users supporting map service layers have changed and allow them to (re)associate / remove misaligned layers with map service modifications (much like the site manager does).
Note: If multiple layers are removed from the map service and new layers are then added user’s saved map projects fail to load completely.
0
-
I have had this a couple times, and it is very annoying! I havent had any suggestions on fixes from my local support either. I would have hoped we could modify the data store documents to fix the layer id index... 0 -
Hi Guys,
I think the layer visibility that is saved with a project is simply a snapshot of the layer list and (as observed) will make its best effort to line up with the services when the project is loaded.
There are a few Ideas posted here already requesting better control over what is within the saved project and the behavior of project load - please add your comments and votes to those Ideas, or post a new one if you can't find an Idea that suits your use case.0 -
I am running into this issue now. We implemented the layer catalog functionality on our internal company site to give users less layers they need to scroll through in the layer list. We told them to add the layers they require from the layer catalog and to save projects so they don't have to add the same layers over and over every morning when they open the application. However, we are realizing that a change to the map service causes their project to not load if their project contains any of the datasets that were removed or if data was added and it changed the layer ID of data they have in their project.
This is an incredible shortfall of the software causing our heavy users frustration, as well as the GIS team when trying to improve the data available to our users.
Has this been improved with the most recent update? We are at Essential 4.8.2.24 and Viewer 2.9.1
I cannot explain how frustrated our users are when their projects don't load because we have republished the layer catalog map service with even small data layer changes.
Any updates or idea on way around the issue?
Thanks,0 -
Hi Jennifer,
Thanks for letting us know how you are using the Layer Catalog and describing the issue with detail.
I've added your feedback to our issue tracker. I did not find any updates to the product that would change the behavior of saved projects with layer catalog layers, but I did find one Idea post (https://support.geocortex.com/essentialsGSCIdeasDetail?c=09a6000000008RsAAI&id=087600000008eU2AAI&categ=&sub-nav=ideas&main-nav=essentials) that mentions layer visibility.
If you have any additional ideas or comments on how best to handle external data changes please add them to our Ideas section!
Regards,
-Malcolm0 -
bump 0 -
Same - incredibly frustrating for users! 0 -
I have implemented a change to our map services where I manually assign the layer ID. I keep track of what the last number is that I used and any new layer gets the next sequential ID. If I remove a layer from a map service, that Layer ID is not re-used.
So far this has worked. I have made a couple changes to map services (removing and adding layers) and I haven't received any nasty phone calls from my users. Hopefully this is a work around until something better is implemented directly in the software to manage this. Either that or my users are just fed up and don't tell me any more when the application makes them angry :)0 -
When we edit an ESRI mapservice, we always add the new data layer at the end. We then adjust the drawing order in Essentials. We also never remove any services that are not used in order to preserve the sequential ID. They can be removed in Essentials.
Rick0 -
It's come up recently in discussion around this bug that there is a method of publishing your services in ArcGIS such that the Layer IDs are preserved: (http://desktop.arcgis.com/en/arcmap/10.3/map/publish-map-services/map-authoring-considerations.htm#ESRI_SECTION1_4C54586DEB0445B4B97AF15856E546AB) 0
Please sign in to leave a comment.
Comments
9 comments