Skip to main content

GE 4.2.0: error when adding “cached service” to the Geocortex,

Comments

5 comments

  • Permanently deleted user

    I just had the same issue all of a sudden. It seems to be site specific. I can add and view the tiled map service in all other sites and viewers with no problems except one and I am getting that same error message. Has anyone else had this problem and found a solution?

    0
  • Permanently deleted user

    All of my tiled map services stopped appearing in one of my sites and the reason was because the service which displays the 'background' of the map, or geographical context is often a tiled service which displays over multiple scale ranges. I had recently added a scratch feature class to my site that is only used to dynamically display data populated into that feature from a workflow. When I added this layer, I put it at the bottom of the Map Services list so the site was actually using that service as the default basemap to display all map services on. I moved that scratch feature class up the top of the list and my tiled services appeared once again. 

    0
  • Permanently deleted user

    What is meant by basemap? Is it the service at is set to be “base” in the Geocortex?

     

    What is meant by tiled map? Is it the cached service at a number of scales when published in the ArcGIS Server?

     

    /customer/servlet/servlet.FileDownload?file=00P6000000em1aEEAQ

    /customer/servlet/servlet.FileDownload?file=00P6000000elzfoEAA

     

    0
  • Dan Giersz

    GE will use the bottom service from the list of services on the "Map Services" tab as the base map of the viewer.  This is independent of setting the 'Function' to mark a servce as a Base Map. Setting the 'Function' to Base seems to only put that service in the Base Map folder in the Layer List and add it to the BaseMapWidget. (Yes, 'tiled service' means you set it to cache when you published it.  The tiles are what is being cached.)

    GE uses this bottom service base map for the base projection, zoom levels of the map, etc.

    Any time you add a service that does not match the base service, you get this warning.

    You can still add services that don't match the base map, but they won't always work as expected and you may have to change their settings.

    Your bottom service is probably dynamic and throwing this warning.

    Just move the tiled services to the bottom of the list after you add them (or move the dynamic services up the list, like Robert did).

    0
  • Permanently deleted user

    Thank you Dan for help. This is very useful.

    By testing multiple cases, I concluded the following

    -Dynamic services of different coordinate systems can live in one site with no errors

     

    -Cached services with different schema (caching scales) can be accommodated in one site without producing an error

     

    -Cached services of different coordinate systems will produce an error if added to the same site

    Am I correct?

    0

Please sign in to leave a comment.