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 -
I remember how the transition from Silverlight to HTML5 forced me to break up my sites into smaller ones with fewer layers… How is speed on these new sites? I just took a class, but their web maps only had a few layers…
Are folks using the Newer Map Viewer or the “Classic” to configure the Web Maps?
0 -
I think all the demos I ever see on VSW seem to have very minimal layers. I've so far testing with an VSW app with 250 layers in it, and yeah, it seems to work ok. I don't think it's as quick as essentials, and the html viewer if the truth be told - I just find the UI experience just that little bit slower in general, and clunky almost (map tip responses etc) but it's very early days at our end in moving to the new world.
I think we're both in the same boat with trying to understand the best way to do this, with a lot of moving parts now in the Enterprise/Portal space. What was so easy and configurable in XML/json based Essentials and REST Services is not so easy now, although I'm slowly warming to the new way. It's been a curve for sure, and still learning new things every day.
Just on my journey - I used the classic map viewer to compose the webmaps - I basically built it from large chunks of our current Essentials AGS REST services. I've since moved ourt testing to the new map viewer, as I think as soon as you save a webmap in this version, it aint backwards compatible (happy to stand corrected on that one).
I still haven't federated our Essentials AGS nodes with the portal, and I'm wrestling with adding secured services to the webmap that's used in the VSW App. It keeps prompting the user for a login, so therein lies the next challenge. I'm trying to keep our AGS nodes out of the whole portal federation thing for now, so I can try to run services for the two parallel applications. Time will tell on this though.
0 -
I still haven't federated our Essentials AGS nodes with the portal, and I'm wrestling with adding secured services to the webmap that's used in the VSW App. It keeps prompting the user for a login, so therein lies the next challenge. I'm trying to keep our AGS nodes out of the whole portal federation thing for now, so I can try to run services for the two parallel applications. Time will tell on this though.
Try to add them first as items to the portal and add these to the webmap.
0 -
We have been using on premise services with layers mostly coming from SDE for Geocortex. We do not have an Enterprise Portal. I'm hoping to continue using our services along with AGOL. Anybody else with that setup? I would use ESRI's basemaps (they have our current aerial), so would need far fewer layers. Are folks converting to AGOL's projection? I would like to not have to replicate our data into another projection, but what are people seeing regarding re-projecting on the fly? Is it slowing things down? I'm curious what folks' expected timeline to be completely converted are? I have so many sites with so many layers… I had not thought I would have to do another migration before I retired.
0 -
Try to add them first as items to the portal and add these to the webmap.
Thanks Nico for that tip, will give it a go today.
Mike Hargreaves - Can't really comment on the AGOL approach as we don't actively use it, and only now starting the Enterprise ‘journey’. Our plan is to migrate slowly and have at least a couple of our major sites running in parallel for this fire season, just in case anything goes awry with the GVH. They won't be fully featured but will contain the essentials (pardon the pun). We have 10+ years of development (complex workflows, and custom modules) to transfer to the new world, so there's a bunch of stuff to do!
1 -
Mats Hallén - I was thinking about this some more, as I'm wrestling with this also. Would creating a webmap from scratch and importing every single layer once - from underlying AGS REST services - help?
I too have imported the layers in bulk from a bunch of underlying AGS services, and this I'd assume makes things harder to keep in sync between AGS changes, and webmaps. There also is the problem of keeping layer ids the same as you add more layers (or re-order), but I think publishing from ArcPro does this now?
it's a minefield for sure, and I'll be playing around with this also.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare