You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good idea and as it goes for implementation, it should be doable in this view with something like highlightLayer.addFeatures(featureCollection.map(f => f.getGeometry()). That's where the potential problem arises. But I think the map() operation shouldn't be too expansive, given that we typically limit the amount of features returned by the OGC service to something like 100 or maybe 200 features. 👍
Well, source.addFeatures() accepts an array of features, not an array of geometries.
As it goes for implementation, well........ I will implement it. Or actually I'm already 90% finished.
In the InfoClick listview, features on the map gets highlighted when hovered in the list.
Request has come in to add this highlighting to the collection list view as well.
Due to the fact that it theoretically can be many features to highlight, this function should be optional and throttled if activated.
Example of the feature collection list view for reference.
In this case, the performance problems would be tiny tiny and not noticable.
The text was updated successfully, but these errors were encountered: