WMTS Layer does not display in Geocortex Viewer

Permanently deleted user

10 Maj 2018 22:59

Hello Geocortex community!

 

I'd like some input on why a certain WMTS layer, (http://gistiles3.oregonmetro.gov/services/wmts/WMTSGetCapabilities.xml) while can be added successfully to my site, is not showing up in the viewer..

 

Initially I thought it's due to a conflict in tiling scheme between my basemap and other layers in the site but the same behavior is reproducible even after adding this layer to a brand new site (created from scratch, no importing of any kind). Plese note that the layer draws fine in other clients (ArcGIS Online, Arcmap).

 

I came across a similar question posted back in 2015 and didn't see any answers, only 1 like...

 

Could someone shed some light on why this is happening and what I can do? I promise I did my due diligence by checking the documentation prior to posting this question!

 

Thanks very much!

0

• 

  Tom Neer

  11 Maj 2018 17:12

  Anna,

   

  We tripped over this bug a couple months back. When the Essentials.bundle.js (located in the HTML5Viewer/Resources/Compiled) is creating the tile info, it gets the spatial reference from the tile matrix set in the WMTS service (e.g. EPSG:900913). ESPG:900913 (OSGEO Web Mercator) and EPSG:102100 (Esri's Web Mercator) are both "unofficial" web mercator projections and it is causing issues.

   

  The reason that it works on ArcGIS Online is that they shimmed ArcGIS Online to reinterpret EPSG:900913 or EPSG:3857 to be EPSG:102100. So we did the same to the Essentials.bundle.js. It is too big to post here but we put our shimmed version on our Github (https://raw.githubusercontent.com/DigitalDataServices/samples/master/Essentials.bundle.js) . 

   

  Now the warnings: 

  • We have only tested this in the HTML5Viewer v2.9.2 and Geocortex 4.9.1 REST Manager. When we tested in the Geocortex 4.9.2 REST Manager the same bug seems to be present in the REST Manager. We did not test in the v2.10.x versions of the viewer.
  • If you install this shim, it will be overwritten on any subsequent viewer update.
  • If you have many WMTS services, each service will independently call the GetCapabilities.xml. This is not a problem if the XML is small but our issue was that our XML was over 2MBs. With 80 WMTS services, the viewer was downloading 160MBs of data before loading.
  • Esri.js does not handle WMTS workspaces correctly. This is a bug throughout the entire Esri software ecosystem (ArcGIS Online, ArcGIS Enterprise, ArcGIS Javascript API, and ArcGIS Desktop). 

  Hope this helps.

   

   

  0
• 

  Permanently deleted user

  14 Maj 2018 22:27

  Hey Tom,

   

  Yes, that was definitely helpful. I'm just glad to know it isn't an user error...Thank you so much for sharing!

  0

Du måste logga in om du vill lämna en kommentar.