You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bing maps for enterprise has been deprecated and the service will be discontinued in June 30, 2025 (free/basic) or June 30, 2028 (enterprise). It would therefore be advantageous if the class is already marked as deprecated so that developers are made aware of this.
There is already an implementation for Azure Maps - but I don't know if new imagery layers will be added to Cesium or if existing ones are only available for legacy reasons and everyone should switch to Cesium ion or their own imagery layer. Therefore, it would be good if either an AzureMapsImageryProvider is already included when deprecating, or a reference to the external project is given.
The text was updated successfully, but these errors were encountered:
@SunBlack Thanks for reaching out and sharing your input. We're tacking this on our side and with our counterparts at Microsoft, especially as Bing Maps is the default imagery from Cesium ion. As we have more concrete plans for the transition, we'll be sure to communicate those. Our intention is to provide a long enough runway for developers to transition without any issues.
Feature
Bing maps for enterprise has been deprecated and the service will be discontinued in June 30, 2025 (free/basic) or June 30, 2028 (enterprise). It would therefore be advantageous if the class is already marked as deprecated so that developers are made aware of this.
There is already an implementation for Azure Maps - but I don't know if new imagery layers will be added to Cesium or if existing ones are only available for legacy reasons and everyone should switch to Cesium ion or their own imagery layer. Therefore, it would be good if either an
AzureMapsImageryProvider
is already included when deprecating, or a reference to the external project is given.The text was updated successfully, but these errors were encountered: