Interaction between Vertigis Studio Web and ArcGIS Portal Web maps
Lets take the following scenario for administering web maps used by Vertigis Studio Web
1. Im adding a service with two map layers to a web map and configure pop-ups in the web map.
2. I then use the same web map in web viewer and the pop up shows on click.
3. I republish the map service in ArcGIS Server consisting of two map layers with two more layers, the service now has four layers, but the web map does not catch that automatically. I have to remove the existing service from the web map and add the service again to reflect / show all the four layers in the web map. And then I have to reconfigure the popup for all four layers.
This is a very time consuming endeavour for big sites, because our customers makes a lot of changes to the layers in our web maps used in Web viewer.
How are we supposed to adminster the underlying web map in an easy way to make the changes reflect in VSW?
In Geocortex Essentials sites we are using couple of hours every month during releases to add new layers to services, re-publish and easily pick up the changes in Geocortex Essentials Site.
I am currently trying to convince our customers to migrate from GVH to VSW (especially with javascript 3 moving to retirement by 2024) but the reality is that the solution is not providing parity on the one thing that is obviously the most time-saving functionality provided in Geocortex Essentials.
How is this intended to work with VSW?
-
I too find this whole webmap concept extremely inefficient when compared to the essentials-based site.xml configuration. We are testing the addition of layers via published AGS REST services, and are experiencing similar quirks with changing simple things like you've mentioned. To make things worse, we currently deploy site.xmls from dev to UAT, and PRD via jenkins jobs - so we only have to make the change once, and deploy from github. SO easy!, yet now with the webmap/portal in between, and unique Id's all over the place, it's becoming harder and harder to achieve this sort of thing in the new world.
The Item Manager application seems to have potential here, and I've only just started to look at it, but it's still a very manual approach at present.
Happy for feedback on this also - as we are still in testing phase and have not yet made any solid decisions about moving from Essentials to VSW.
1
Please sign in to leave a comment.
Comments
1 comment