Hi everyone,
We're currently experiencing an issue when creating offline areas in ArcGIS Enterprise 11.1, specifically related to the "World Imagery for Export" basemap. Here's a breakdown of the situation:
Details:
ArcGIS Enterprise 11.1
Web map includes referenced layers and the "World Imagery for Export" basemap
Problem:
When attempting to create offline areas, the packaging process successfully includes the referenced layers but fails to package the "World Imagery for Export" basemap.
Other exportable basemaps (e.g., Topographic, Streets) work without any issues.
No error messages are displayed—just a silent failure to include the basemap.
Troubleshooting Steps Taken:
Reviewed the ArcGIS Server's Offline Packaging geoprocessing service—no errors or logs indicating a problem.
Checked the browser's developer console—only a status 304 is returned, with no additional details.
Recreated the web map item in Portal for ArcGIS, ensuring credentials are stored correctly—still no success.
Has anyone encountered a similar issue with "World Imagery for Export"? Any insights or suggestions would be greatly appreciated!
Thanks in advance!
Hi @nicomg
Have you seen the following documentation
Problem: Unable to Export a Tile Package from the World Imagery Services
It states
“Basemap services are configured by default to prevent the export of more than 100,000 tiles. The World Imagery (for Export) map service is designed to support exporting small volumes of basemap tiles for offline use, according to the access and use constraints.”
It seems as though this is the reason why it is failing
Additionally, the World Imagery (for Export) item page confirms that the service is intended for limited offline use and provides examples of exportable areas:
• A large city (e.g., San Francisco) at full detail
• A medium-sized state (e.g., Colorado) at ~1:36,000 scale
• A large country (e.g., continental U.S.) at ~1:288,000 scale
If your offline area exceeds this tile count, the packaging process may silently fail—just as you're experiencing.
Might also be worth checking you have added the referrer URLs in the limit usage
It should look something like this