Hoppa till huvudinnehållet

Serving Imagery

Permanently deleted user
I would love to hear from anyone who has a site serving both cached and dynamic imagery. Possible? My hope is that I can cache imagery to a certain scale level (e.g. 1:2000?, 1:5000?) and then serve it dynamically at any scales larger than that. Our users really want to be able to zoom in close in some cases and caching imagery at those scales requires a ton of storage space, as you all know :) Any thoughts?
0

Kommentarer

3 kommentarer

Datum Röster
  • Mike Ketler

    Hi,

     

    The problem with this setup is likely going to be how Essentials handles the "Site" spatial reference and viewing scales. When you configure a site, the first or bottom map service in Manager is used as the Primary Map Service. The site will take this service, set the overall site to match the spatial reference, and if it's cached then the tile levels become the scale levels the viewer can zoom to and from. In this example, you won't be able to zoom to scales between the scales that don't exist in the cached service.

     

    Our demo viewer rest endpoint shows how this works:

     

    Viewer:

     

    http://gedemo.geocortex.com/Html5Viewer/index.html?viewer=LA_County_.LA_HTML

     

    Rest Endpoint:

     

    http://gedemo.geocortex.com/Geocortex/Essentials/Prod/REST/sites/LA_County_/map

     

    1. The primary map service is the cached LA County street map

     

    2. The other cached services all match the spatial reference of the LA County street map

     

    3. The scales that can be viewed in the viewer always match the tile scales from LA County street map even when some of the Aerial cached services have more detail (1128.497176 vs 564.248588)

     

    4. The rest of the services are all reprojected or are the same spatial reference as the LA County street map

    You could try setting a dynamic service as the primary map service but the spatial reference must then match any cached services added after as those services can't be reprojected. This isn't usually a site configuration we test with so there may be other unforseen issues.

     

    Thanks,

     

    Mike Ketler
    0
  • Permanently deleted user
    What we did was we created our cache tile at a reasonable amount of scales and published the map. Then, we went into the tile service's conf.xml file and added more scales zoomed in closer (Pretty sure you have to stop your service during this) and then republished it with the option to create tiles on demand. So we had the tiles previously created at the larger scales, and if someone zoomed into an area really close, then new tiles would be created on demand at the closer scales (rather than having a massive cache of tiles). Of course, after a certain amount of time, we'll probably have to delete those tiles to free up space, but we'll probably have new imagery by then anyway and will get rid of the "on demand" scales for that year's imagery.

     

    Now I'm not too sure of the specifics because it was a while ago, but I'm pretty sure that was all I had to do. I remember there was a tool that was supposed to be able to update your scales in your service, but that it didn't work for me so I had to manually update the conf.xml.

     

     
    0
  • Dan Giersz
    Our Esri rep actually recommended the hybrid cache/dynamic service approach you are asking about.  We also had users wanting to zoom in, but were weary of the additional storage required to cache those extra couple levels.  We ended up just getting more storage, since it's cheap.

     

    You certainly could do this in a viewer, but you'd really have to test this in your environment to get a good look at any performance issues.

     

    As Mike mentioned, you will want a cached service as the base in your viewer with those extra zoom levels whether you actually create the tiles for them or not.
    0

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

Hittade du inte vad du sökte?

Nytt inlägg