Attributions not showing in 3D

[jmgomezpoveda]

I have added attributions to all the layers in my map. In 2D I can see the "i" icon that on clicking it the list of attributions expands.

Once I switch to 3D, the whole icon is not visible. Even if I manually remove its "display: none" settings, attributions are empty.

Are attributions not supported in 3D? The Cesium map is still using the same layers, so I need to give the right credit.

[XiaofengZeng]

Hi, @jmgomezpoveda.

The "i" icon you mentioned might refer to features in a vector layer where images are used for styling.

• The olcesium vector synchronizer converts each feature into a primitive for rendering. When the synchronization is about to finish, it associates the primitive, layer, and feature using the setReferenceForPicking(). However, the logic for triggering click events in 3D needs some adjustments.

I hope this helps you out.

[jmgomezpoveda]

The control is a normal "ol-control", which when going to 3D is getting a "display: none" property. When disabling that property, I can see the "i" box, but when clicking on it I get no attributions. It's like attributions linked to layers are not reflected in 3D, so ol-cesium just hides the "i" altogether.

[XiaofengZeng]

In olcesium, there are two types of data synchronizers:

• The Raster Synchronizer handles raster data sources from an ol map. It synchronizes the raster data by calling the attributionsFunctionToCredits method, which converts all attributes into Credit in Cesium.
• The Vector Synchronizer creates a mapping for the corresponding layers if it's a vector data source from ol. This is done using the setReferenceForPicking method mentioned earlier.

In both 2D and 3D scenarios, the framework differences lead to varied interaction logic for events, so it's important to handle cases depending on the current scene to ensure that the desired attributes can be displayed. Thus, specific situations need to be debugged and analyzed using developer tools.

[gberaudo]

Hi @jmgomezpoveda ,
Attributions correctly shows up in the MVT example:
2D

3D

You should compare the code between the examples and your application.
There is certainly something different which explains the different behaviour.