How to setup 3D terrains(elevation) with Mapproxy for Bing maps?

[VrushalNCT]

I followed the tutorial to setup Bing maps https://vts-geospatial.org/tutorials/bing-maps.html
However, it's just rendering the flat surface with textures and labels.
How to setup bing maps to load the 3D terrains? Can mapproxy process height information on the fly to be able to load 3d terrains?

[ladislavhorky]

Please see first part of my answer to your other issue melowntech/vts-backend#17 .

I you want to serve your own terrain, please refer to tutorials like https://vts-geospatial.org/tutorials/mars-peaks-and-valleys.html , most tedious work is now solved by mapproxy-setup-resource tool that gets you from raster DEM to working resource in mapproxy but it is good to know what happens under the hood.

[VrushalNCT]

Hello @ladislavhorky

I went through all the tutorials and concepts, and I'm able to set up a DEM surface for a small region for now along with bing maps as a bound layer.
However, I'm facing one issue regarding the resolution quality of the map.
When I'm loading the bing maps with only a spheroid surface, I'm getting a very good resolution of the details when I zoom till almost the roads.

But, when I used the bing maps as a bound layer with the custom DEM surface after a certain zoom level, it's not loading further details. and it is a very poor quality blur surface as compared to the above scenario.

Following are the lod and tile range details. (referenceFrame "melown2015")

1. For tms bing-maps :
   "lodRange": [2, 21],
   "tileRange": [[0, 0], [1, 1]]

2. Custom DEM surface:
   "lodRange": [ 9, 15 ],
   "tileRange": [[ 56, 110 ],[ 57, 111 ]]

Could you please suggest how can we fix this issue?

[vaclavblazek]

"lodRange": [2, 21],
"lodRange": [ 9, 15 ],

You need to have the same bottom of both datasets (i.e. 21 in this case). VTS does not support more external textures placed on one tile (so far).

[ladislavhorky]

Hello @VrushalNCT

more specifically, --bottomLod option in mapproxy-setup-resource if you are using it. It will take more time to set up DEM up to this LOD - this is expected.

[VrushalNCT]

Thank you very much. It worked with the --bottomLod option.

I was not using mapproxy-setup-resource but, I think it has made things easy.
However, now the maps are taking more time to load in the vts-browser even if we zoom in at a certain location, it takes more than 5 minutes to load the details, is this an expected behavior? (I have good internet bandwidth)

[ladislavhorky]

Hi, 5 mins is quite too much... I'd have a look on how vts-mapproxy is doing during that period:

• run htop on the server where mapproxy runs, when you load the map look at used RAM - should not be full, no swapping. If it is, you'll need to change rssLimit in conf as by Is VTS Mapproxy optimized for Bing maps transactions? vts-backend#17 or pick HW with more RAM.
• if the server has less than (say) 4 cores, it may be just too little, mapproxy needs some burst power when generating tiles on the fly
• if mem an load is OK, look into /var/log/vts/mapproxy.log If there are from time to time lines like "kill leviathan", you'll need to raise rssLimit