A. elevationResolution is the resolution of the tileset mesh.
There is also elevationDataWidth and elevationDataHeight - this is the size of the array of the elevation data.
These parameters are determined automatically by the size of the array that you send to SetElevationData.

B. http://infinity-code.com/atlas/online-m … ample.html

C. Unfortunately, Bing Maps almost does not have good alternatives.
Actually currently only ESRI is a good alternative.
Google Maps can theoretically be used, but here need to specify the coordinates of all the points for which need to get elevation data. This is very inconvenient.
Mapbox has too much resolution (256x256 per tile) to use it runtime.

As far as I understand the script "OnlineMapsTileSetControls.cs", only 32 x 32 height data can be used for the mesh. Mapbox and others offer in the meantime far more precise elevation data.

Question:
A) Can I increase this accuracy myself and how? There is probably "public int elevationResolution = 32" In the code. But later, the elevation array is fixed to 32 x 32 ...
B) Do you have an example?
C) Are you coming with an extension for more flexibility (data provider, resolution) in the elevation data (also for offline use)?

Thanks for your feedback.