OGC Feature Layer Selection changing randomly

Question

Hi,

I have tried to display the Daara TransportationGroundCrv Collection in my WinUI Project. I have a problem where every time I call OgcFeatureCollectionTable.PopulateFromServiceAsync the selection on the layer changes seemingly randomly.

As described in the Display OGC API collection sample, I call PopulateFromServiceAsync on the MapView.NavigationCompleted Event. The Features are populated correctly but the selection somehow changes. This is my code:

var selectedFeatures = await featureLayer.GetSelectedFeaturesAsync();
_logger.LogInformation(" Before: Selected Feature: Count {count}, Attributes {attributes}", selectedFeatures.Count(),
    string.Join(", 
", selectedFeatures.FirstOrDefault()?.Attributes.Select(a => $"{a.Key}: {a.Value}") ?? []));

await ogcFeatureTable.PopulateFromServiceAsync(wfsVisibleExtentQuery, true, null, ct);

selectedFeatures = await featureLayer.GetSelectedFeaturesAsync();
_logger.LogInformation(" After: Selected Feature: Count {count}, Attributes {attributes}", selectedFeatures.Count(),
    string.Join(", 
", selectedFeatures.FirstOrDefault()?.Attributes.Select(a => $"{a.Key}: {a.Value}") ?? []));

The selected feature before calling PopulateFromServiceAsync is not the same as the selected feature after calling PopulateFromServiceAsync.

I want the feature selection because I display the attributes of the selected feature, and I want the user to be able to see which feature is selected. The selection is implemented using mapView.IdentifyLayerAsync and featureLayer.SelectFeature

The OgcFeatureCollectionTable is initialized as follows:

var ogcFeatureTable = new OgcFeatureCollectionTable(new Uri("https://demo.ldproxy.net/daraa"), "TransportationGroundCrv")
{
    FeatureRequestMode = FeatureRequestMode.ManualCache,
};
new FeatureLayer(ogcFeatureTable)

I'm using net8.0 WinUI and Esri.ArcGISRuntime.WinUI 200.6.0

Could this be a bug in the ArcGIS Runtime?

TimScheiber · Answer

Hi Preeti,

Do you have any updates on the status of the issue? Is there any possibility this will be resolved in the next release?

Thank you!
Tim

PreetiMaske · Answer

Hi Tim,

Thanks for the reproducer, we were able to reproduce this. We have logged an issue internally and assigned to the team responsible for this area. We appreciate your feedback. We will continue to investigate this and try to resolve it.

In the meantime, I do have a workaround that you can use, not the best one but will at least unblock youfor now. The workaround below finds the first selected feature and reselects the feature by looking for a matching attribute name `id`. Note my code only selects the first selected feature. You can alter the code to reselect all features as needed. This is just to show the how you we workaround the issue for now. See the updated code below:

var currentExtent = MyMapView.VisibleArea.Extent;
    // Create a query based on the current visible extent.
    var visibleExtentQuery = new QueryParameters();
    visibleExtentQuery.Geometry = currentExtent;
    visibleExtentQuery.SpatialRelationship = SpatialRelationship.Intersects;
    // Set a limit of 5000 on the number of returned features per request,
    // because the default on some services could be as low as 10.
    visibleExtentQuery.MaxFeatures = 5000;
    // Get the selected features.
    var selectedFeatures = await _ogcFeatureLayer.GetSelectedFeaturesAsync();
    // Get the id of the first selected feature.
    var firstSelectedFeature = selectedFeatures.FirstOrDefault();
    Int32 id_value = -1;
    if (firstSelectedFeature != null)
    {
        var attributes = firstSelectedFeature.Attributes;
        id_value = Convert.ToInt32(attributes["id"]);
    }
    // Populate the table with the query, leaving existing table entries intact.
    await _featureTable.PopulateFromServiceAsync(visibleExtentQuery, false, null);
    // Find the previously selected feature by its ID. 
    var previously_selected_feature = await _featureTable.QueryFeaturesAsync(new QueryParameters() { WhereClause = "id = " + id_value });
    // Reselect the previously selected features.
    _ogcFeatureLayer.SelectFeatures(previously_selected_feature);

If you questions please feel free to reach out.

Thanks again,

Preeti

TimScheiber · Answer

The ClearCache parameter changes the selection behavior, but I do not think it should? When I set ClearCache=false, the selection is cleared completely.

I want the selection to remain intact after loading new Features from the Service. I do not want the selection to be cleared just because I zoomed in/out on the Map.

WFS Feature Tables retain their selection after calling PopulateFromServiceAsync, unless ClearCache is set to true and the selected feature is no longer within the current viewpoint.

I've attached a modified Display OGC API collection sample with selection.

You also mentioned selection using and ID of a feature. Is there a way to select a feature on a layer other than FeatureLayer.SelectFeature(Feature) ?

OgcApiMapExample.zip