Marika,
Thanks for the response, perhaps Kevin from ESRI Technical Support was able to reach you. While he and I have been working on several issues related to ArcPad, we had been using the download tile applet developed from your team. I discovered that when defining the number of cache levels to download 'below' your current level, the tool would in fact try to download L20; the various cache folders were created in the appropriate location (My Documents) but no tiles were downloaded for this level (only blank HTML files). This is the exact behavior I had witnessed when trying to access cached tiles from our AGS. When I had been testing this with another analyst which concluded in the issuing of a new bug (BUG-000082371), I suddenly recalled that they had me generated only a portion of the tiles (not starting with the world extent). Presumably, they did the same thing on their end (at ESRI), because they observed the behavior. So, ArcPad was trying to access tiles which did not exist.
So, this morning is set-about creating a new cache which originated at the world extent (level 00). These tiles were all created and can be seen in the GIS cache directories. However, when accessing this service in ArcPad (after clearing the HTTP 400 error) the same behavior persists. I don't know of any other parameter that is required at this point. The service is:
- Using Web Mercator projection
- A cached service using the 'exploded' storage format option
- The appropriate Tiling Scheme which includes the level 0 tiles
The cached folder ArcPad creates a folder called L01 with blank HTML references and does not appear to be creating an L00 folder first as expected.
Furthermore, when you add any service from ArcGIS online, it initiates the tile download with Level 01; you must perform a fixed zoom out in order to acquire L00 in your local cache folder.
Even though you have level 0 tile cache present for your AGS map service, ArcPad is starting with L01 (which does exist).