3D polygon in oldfashioned context

[jbigdata-git]

Hi,

I use OLCS in an old-fashioned context : pure HTML and JS.

I encounter a first problem with the rendering. As you can see in screenshot 00 if I use two DIV to render, one 2D and one 3D, like the example, everything goes well.

On the other hand, if I delete DIV for 2D at this point no more layers are displayed (image 01). I found a workaround by "hiding" a DIV of size 1x1, I did a lot of different tests, but in the absence of the 2D DIV, nothing is displayed in the 3D DIV.

Do you have any advice for me to resolve this problem properly?

Back to the main subject

I want to make 3D renderings of geojson, everything goes well with the use of the olcs_extutded_height property. I would like to know if there is a way to offset the height of the base of the polygon (image 02). Some kind of ocls_extruded_base property: The ground is at 0, the polygon starts at the ocls_extruded_base height and stops at the olcs_extruded_height as is currently the case.

[gberaudo]

Hi @jbigdata-git,

You say you are using the oldfashioned way.
This way of doing is deprecated and will be removed in next release.
I have no information about how people use the lib. Could you please let me know:

• why you are using the oldfashioned ways?
• can you move to using the ES modules? Or if there is a blocker.

What version of ol-cesium are you using?

Regarding ocls_extruded_base, yes it should be possible to add this to ol-cesium.
I don't know if it is a usual use-case though. Why do you add this offset?
Also, are you doing it atop some terrain or on the ellisoid?

[jbigdata-git]

Thanks for your return.

I will try to answer your questions.

I use the Oldfashioned way because it’s more efficient for me. From my experience for certain applications integrating heterogeneous components which must interact if we want to be in control of all interactions, it is uninteresting to remain low level: HTML and pure JS. My opinion is based, among other things, on the creation of this application: AirMeteo.fr.
I therefore prefer to stay low level and above all I have to stay in an HTTP server.

I don't know if I answered your question, but if I can give an opinion it's a real shame to eliminate this simple and efficient way of using your components which corresponds to a need.

I use the openlayers-ol-cesium-d1fb3b6.zip archive that I retrieved on January 6. I see there is a new version (openlayers-ol-cesium-a64440c.zip) and those files in OFashioned way:

• https://cdn.jsdelivr.net/npm/ol@v8.2.0/ol.css
• ./libs/openlayers-ol-cesium-d1fb3b6/olcs.css
• https://cdn.jsdelivr.net/npm/ol@v8.2.0/dist/ol.js
• ./libs/openlayers-ol-cesium-d1fb3b6/olcesium.js
• ./libs/openlayers-ol-cesium-d1fb3b6/_common.js
• https://cdn.jsdelivr.net/npm/cesium@1.113.0/Build/Cesium/Cesium.js

About ocls_extruded_base or ocls_extruded_offset.
I'm benchmarking a full opensource version of a data analysis application created for the French government's opendata platform: 4001 Explorer.

On this application you can see a use case of the desired offset, if necessary I can detail more, I have put a screenshot too. You can also access the new Cesium version currently in development for which I am trying to have the same level of functionality.

If I may allow myself to seek your expertise again, I am also missing the selection at the layer for which I made a post "GeoJSON layer highlight, mousenter, mousover”. and other points which are more detailed that I will see later, for example a setting to tilt the map at the initial display.

JB.