WMTS In Studio Go
I noticed a few releases ago there was a note that WMS and WMTS sublayers were now supported. We are able to add WMS layers as a custom basemap baselayer, but when we try to add the same service as WMTS it fails to load. Are they not supported here? The extra speed would be a great improvement over WMS.
-
Hi Max,
Thank you for your question. When we implemented support for WMS & WMTS sublayers, we tested a variety of services that we, and our European colleagues, had available and they all worked, with one exception. A Swiss service that required some additional, external token authentication that we were unable to get to load. Does the service you're working with make use of any additional authentication? Does this same service load in your Portal's map viewer?
Have a nice weekend,
Phil
0 -
Hi Phil,
The URL has a token in it but that is the only auth, same as the WMS url/service. The WMTS does work as expected and the same way as WMS in portal maps and Esri desktop software.
0 -
Hi Max,
Thanks for clarifying. Would you be willing to share the service with us so I can have someone on our team take a look? You can reach me at phil.macintyre@vertigis.com rather than sharing it here.
Phil
0 -
Hi Max,
Apologies for the confusion, I didn't realize you were referencing an error in Mobile App Designer rather than in Go itself. We've reproduced the issue locally and I've logged a bug into the App Designer team's backlog for assessment and prioritization. They're going to look at it shortly. I tried to find a hand-coding way to get the service to work in Go, skipping Designer, but wasn't able to get anything stable unfortunately. I also tried reversing the order of some of the URL parameters, which worked in AGOL/Portal, but alas not Designer.
I'll let you know as soon as I hear anything from them, and/or if we can find a stable workaround to get you unstuck.
Thank you for your patience,
Phil
0 -
Hi Max,
One of the Designer devs is digging in to this. He did find, however, that if you provide the authKey as a custom parameter when you add the service to your Portal that Designer then respects it. Like so:
We'll see if we can work on adding support without needing that extra step, but in the meantime, hopefully this will help unblock you for now and let you make use of the service.
Please let me know if you have any problems with that,
Phil
0 -
Hi Phil,
Thanks for the possible work around. I gave it a shot and was able to add the URL as a portal item using the custom parameter and it works in portal maps and I am able to add it to the mobile designer. However, when I open studio go it prompts for a login to that service and seems to ignore the authkey.
We can continue to use it as WMS for now so we arn't super stuck, WMTS is mostly for hopeful performance gains.
0 -
Hi Max,
Thank you for clarifying. I've reproduced the issue on our side as you've described. I'll file a ticket into our backlog to investigate, but it's good to hear you're not fully stuck from this.
Have a great weekend!
Phil
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
7 kommentarer