Using a clusterfeaturelayer based on a FeatureService results in a wrong presentation on mobile/tablet layout. Just a few features/clusters are displayed while the others just disappear.
When users create own content viewer definitions for the clusterFeatureLayer, these are not taken into account. Instead, a default featureinfo window gets opened.
When the clusterFeatureLayer is turned off in the toc and turned on again in a different map section or a different scale the icons don't appear unless the user moves the map section or changes the scale again.
Clicking on a cluster to dissolve it and zoom into the map queries underlying features (such as an area-layer) and results in opening a popup-window when queryable features are hit.
Clusterfeaturelayer ignores scale dependent visibility settings on the underlying Feature-Service. As well the clusterlayer is not affected by using the sublayer-properties "minScale" or "maxScale".
In der aktuellen Version 3.4.1 wird für Objekte, die vom spiderfying betroffen sind, kein popup angezeigt. Dieser Effekt lässt sich auch in der sample-App nachvollziehen.
Die Version 3.3.1 verursacht in unseren Themenkarten einen Fehler. Der Start der Themenkarte bricht ab.
Wir setzen folgende Versionen ein:
map.apps: 4,11,1
firefox: 91.5.0esr
In der Konsole wird folgender Fehler gelistet:
https://...../mapapps/resources/jsregistry/root/esri/4.18.1/rest/support/Query.js -> Fehler: 404 Not Found