We switched over to using AOI Envelope. We had better results with envelope, but it seemed to generate tiles for areas that were much larger than the envelope we supplied. This is problematic for national scale imagery. We kicked off a very small envelope yesterday, and it is still running.
1- no informative explanation why caching fails. reported error messages could be little bit more specific "cause-wise" then just failed to cache at extent xyz
2- cache status GUI in both ArcCatalog and Server Admin page keeps displaying tile generation is in progress even though cache have already reported itself to have failed in arcCatalog and dispite multiple attempts to cancel cach. i am yet to find a way to get arcgis server understand that the cache processes was terminated/or failed. i would love to have a tool to force kill an indefinitely running caching service. the only way i think is to manually update the status.gdb geodatabase, which is what i am thinking of trying out.
3- cache import/export operations take considerably alot of time to execute even for smal subsets and even for a whole cache which is equivalent to a copy past operation with physical files.
4- cache update status tools takes considerably alot of time to execute and update cache status gdb. also, you cannot specify which level to update and you have to update all, which is not the case most of the times.
5- still need a mechanism to double check the cache completed. as we are using control shapes to govern what is being cached at different scale levels, system generated "expected number of tiles" is bound to differ from completed tiles as later should be less. however, by how much less or what should the number be or how to check if cache was actually completed as intended is still not clear how to determin other than manually going through each inch of the map and see if we have an image displayed. this can be exhustive in caching basemaps of the whole contry.
6- even in the system generated expected number of files, at the lowest level for example at scale 1000, logically we would expect it to have the largest number of tiles as proven when caching previous levels, however, it is expected by the system to be less than the previous scale level. this adds ambiguity and some uncertainty in the results.
This is �??as Designed�?�. AOI envelope generates the cache tiles for the extents that cover the minimum bounding rectangle of the AOI instead of the supertiles that intersect the polygon.Would you be willing to share your data with us for testing?Thank you,Andrew
My experience with 10.1 caching is similar to other posts. The new tools are unstable and unreliable, with poor error reporting. Typical first release... It is frustrating that a relatively simple task in 10.0, which worked fine, has become a convoluted web of trial and error to get a basic cache built. I find I can build levels 1-5 when publishing the map service. When I try to build levels 6,7 and 8, this is where the witchcraft of figuring out what approach doesn't break it and leave me wondering what is going on. I found one dramatic approach that seems to help, and that is to stop all the other map services and only run the one you want to cache. NOT very efficient. Build the initial levels, and then add one at a time, and pray to the voodoo gods that it doesn't just mysteriously stop on its own. It shouldn't be this way! I have better use of my time than debugging pre-release state release software. Come on ESRI get this fixed with SP1!!!!
I'm also seeing incredibly inconsistent results.I'm building 2 caches at a national scale and I'm running into the following issues.1) The cache status window will tell me that tile generation is in progress, but no new tiles are being generated after a refresh. The completed tiles stay the same, the percent stays the same and the in progress column is indicating it's still building. I've waited overnight and let my site churn this out to come back in the morning and nothing is new. The job status says the job is done, with a 100% completion and no errors but those tiles still aren't completed on the cache status.2) the cache process seems to skip/give up on certain scales. I'll have scales that are partially completed and the cache process will simply move onto the next scale and never return to complete the missing tiles in previous scales. So the cache status is telling me that they're only partially complete, but again the job is saying the cache is 100% complete and with no errors. The services themselves have obvious missing tiles as you zoom/pan around with no data.Does anyone have any advice or has anyone been able to successfully build a national scale cache with significant data? The cache I'm generating is a nationwide Navteq 2011 Q3 street dataset with basemaps and I have clients waiting for this service.My site consists of 4 64 bit Windows Server 2008 Machines with 4 cores/8 CPU's @ 2.4GHz (32 total CPU's in the site) and each machine has 18GB of RAM. I don't think my hardware should be the issue.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
