Adding support for MVT source using WMS protocols about ol-cesium HOT 2 OPEN

Hi @xevxx, alias Mendoza ;),

Thanks for sharing your code, it may be useful to someone in the community.

The reason we request tiles in a grid is to take into accoung the heterogeneous levels of details of a 3D scene.
Contrary to 2D where the resolution is the same for every pixel in the viewport, these are different in 3D:

• we need precise data for what is close to the camera;
• less and less precise data for what is farther away (to not be overwhelmed with data).

I only looked quickly to your code so I am not sure exactly what it does.
In 3D, are you sending several requests to your geoserver MVT endpoint?
What the issue with using the TMS grid?

from ol-cesium.

Thanks for the reply, we are displaying user editable data in our 2d/3d map which can be updated / edited on the fly by users in 2d and had originally setup our app to use GWC TMS and had a cache invalidation of -1. (All edits are made on full vector features pulled for editing at the time) but when not editing data is displayed as MVT.

I'm pretty sure the MVT tiles are still generalised by GeoServer for the different zoom levels, same as TMS.

We were informed by the good fellows at Geosolutions that GWC TMS and with a cache invalidation of -1 was very inefficient setup and they recommended using the MVT as WMS method for this user editable data as shown above.

The changes to ol-cesium are my attempt to display these layers on the 3d map based on your existing code.

I had then extended the ol.source.vectortile to allow me to use the WMSGetfeatureInfo method to show the attribute info of the rasterized MVT features on the 3d Map.

from ol-cesium.