Dear Community,
I am currently testing the World Imagery service to integrate the ArcGIS imagery base map through the following API URL:
https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x}
I have a few questions and concerns regarding this service:
1.Rate Limits and Restrictions:
Are there any rate limits or restrictions on this API, considering that it provides world imagery for free without requiring an API key?
2.Commercial Use:
Can this API be used in commercial applications?
3.Long-Term Availability:
Does Esri provide assurances for the long-term availability of this service, or is there a possibility of discontinuation in the future?
Additionally, we are facing a challenge with the ArcGIS imagery API:
•Whenever the imagery quality is low, the API responds with the message:
“Map Data Not Yet Available”
Example URL:
•However, when the imagery quality is high, the map loads successfully:
Example URL:
https://services.arcgisonline.com/arcgis/rest/services/World_Imagery/MapServer/tile/17/43218/67463
In both cases, the API responds with a 200 (success) status code, making it challenging to differentiate between a “successful” response with valid imagery and an “unsuccessful” response with missing or low-quality imagery.
Could you kindly advise if there is an alternative way to differentiate these responses programmatically? Additionally, we would greatly appreciate any guidance or assistance in resolving this issue to ensure the imagery is properly populated in tiles where “Map Data Not Yet Available” is currently displayed.
Looking forward to your guidance.
Hi @DineshBellamkonda , regarding your questions
1. the service is not free, it can only be used with an ArcGIS Online or ArcGIS Enterprise license. you must review the terms of use
2. as is stated in the terms of use, this service is not available for commercial use.
3. Review the item details here https://www.arcgis.com/home/item.html?id=10df2279f9684e4a9f6a7f08febac2a9 for updates and availability
The service response codes are what they are, and this is why we recommend developers use the ArcGIS APIs to access the tile services as they have the logic to deal with these issues. See https://developers.arcgis.com/documentation/#sdks-and-apis for the available SDKs.