I love the addition of the 3D tiles in the latest release! It looks absolutely wonderful!
But I see there is a limit to the amount of sessions daily. It makes sense, I can imagine the integration with Cesium isn’t for free.
Now for many use cases, I believe that it is not necessary to have the 3D tiles. For example to verify the georeference location of a project, to do visualisation of building site equipment in a more rural terrain, … For those cases it would be really nice to have a 2D satellite image (like google satellite), OpenStreetmaps or even WMS/WMTS option.
Since there are many (more) free/opensource/… options for 2D compared to 3D I believe this would be a very nice thing to have side by side.
Hi @Johan_De_Cock,
The integration isn’t free indeed, hence the daily limit. This is a first version, just to make it easy for users to try out the feature without too much setup.
Our next step is to allow users to log in to their Cesium account through Qonic; this would lift this restriction of 5 sessions per day, and will also allow you to load in other tilesets like 2D satellite images or 2D Maps data. The free version of Cesium comes with a good library of open source datasets that can be streamed in, so it should open up a lot of possibilities at no additional cost!
Thanks Jacob for the reply!
In summary, everything geocontext related will always go trough Cesium?
I have been looking at their “Cesium Ion” pricing tiers and it looks like the free version is only for non-commercial use though … With the first paid tier being relatively expensive for sporadic use. So that’s why I was asking about alternatives like WMS/WMTS that can be freely available (like our Flanders/Belgium government datasets).
Hi @Johan_De_Cock,
I can’t speak for the future so will confirm nor deny your question here 
It’s definitely useful feedback which we will take into account for our next iteration. This integration with Cesium is meant as a first proof of concept of the technical possibilities and to gather further feedback from users.
If these datasets you mentioned are based on the same standard dataformat then I don’t see why we shouldn’t be able to support this. If this is a completely different type of implementation it might require more work (and thus time 
) to get this into Qonic.
So in short, no promises but we’ll take it into account!