3D terrain in map.geo.admin.ch

[Varun Sharma]

Hello, 

I am trying to learn from map.geo.admin.ch on how I could use CesiumJS for my applications. I understand that there a new version in the works at test.map.geo.admin.ch. 

In the current app, the 3D terrain works very well. It is quite rapid. It is much slower in the new app. Ofcourse, there could be many reasons for this as the new app is in development. 

But looking at the terrain sources, I see that the current app directly fetches from terrain*.geo.admin.ch for example : 

https://terrain104.geo.admin.ch/1.0.0/ch.swisstopo.terrain.3d/default/20200520/4326/18/274005/198811.terrain?v=1.0.0

The test version of the new app seems to fetch from 3d.geo.admin.ch. For example: 

https://3d.geo.admin.ch/ch.swisstopo.terrain.3d/v1/20201203/16/69060/49774.terrain?v=3924.0.0

Is there a reason for this switch that someone like me developing cesium apps and dependent on swisstopo's datasets should know about ? The 3d.geo.admin.ch service adds a layer of in-direction isnt it ? is that why the test.map's terrain fetching 'seems' to be slower ? 

Best, 

Varun

[Pascal Barth]

Hello Varun,

The new URL scheme is there because we took the opportunity of our latest data update to rework a bit our infrastructure holding these data.

This data update is only available through our currently in-developpement web-mapviewer, that is bound to replace map.geo.admin.ch very soon. But that meant that we had to keep the "old" data available while publishing the new (transition period). The data from the first URL you gave is meant to be used with a (now pretty) old version of Cesium, and isn't 100% compatible with the latest version (that's one of the main reason we are updating our data, we want to use the latest version of Cesium on our ongoing development)

So the caveat is that the first terrain URL scheme you mentioned might be decommissioned in the future. As soon as we have finalized our move to the new codebase we might start removing the specific stuff that was there for the mf-geoadmin3 viewer.

Regarding speed of loading/performance, we haven't done too much performance refinement yet, so there might be some leeway to improve load/performance in this regard.

Hope this answers most of your questions,

Best regards,

Pascal

--
You received this message because you are subscribed to the Google Groups "GeoAdminCh API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geoadmin-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geoadmin-api/CANEMPHUCAMSRd_SrBFJGX9ppxo4yrjay2eKEVPBeZBQkUKtRhw%40mail.gmail.com.