An Azure service that provides geospatial APIs to add maps, spatial analytics, and mobility solutions to apps.
Is short-term server-side caching of Azure Maps Weather radar tiles, and display over a third-party basemap, permitted?
I'm building a paid consumer weather app that uses Azure Maps Weather radar tiles (tilesetId microsoft.weather.radar.main, Render API version 2024-04-01) on a Gen2 pricing tier.
Architecture: my server fetches radar tiles and caches each frame for about 2 hours (frames are superseded every 5 minutes, so nothing stale is shown). Tiles are decoded to reflectivity values and blended with public government radar sources (NOAA, ECCC, JMA, etc.) into one composited radar layer. That composited layer is displayed over a basemap from a different (non-Azure) map provider.
Two questions about the Azure Maps terms in the Microsoft Product Terms:
Q1. The terms prohibit caching Results "for the purpose of scaling such Results to serve multiple users," while permitting caching to reduce latency within the response-header validity period or 6 months. Does a short-lived server-side cache of weather radar tiles (shared across users, ~2 hour retention) qualify as permitted latency caching?
Q2. The terms prohibit displaying Results on a third-party geographical map database. Does this apply to Weather radar tile overlays shown over a non-Azure basemap?
If this isn't permitted under the standard terms, what license level or agreement would cover this use case?
Azure Maps
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more