That worked, Dasa. Thanks.
I do see that queryByGeometry doesn't seem to work on that layer. It might be good to enhance the documentation on that score. (Right now it only says "Does not support queries that need to be performed on the server, e.g. queries with a where clause.")
protected function map_mapClickHandler(event:MapMouseEvent):void
{
// set the selection query based on the click
queryByGeometry.geometry = event.mapPoint;
blocks.selectFeatures(queryByGeometry);
}
I imagine that I can replicate that functionality by querying the original source layer instead, inspecting the attributes of the feature selected there, and then selecting the features in the locally-hosted featureLayer. Before I go that route: (1) What are the limitations in the types of selections I can do against the locally-hosted featureLayer? I wouldn't want to be restricted to selecting by IDs, because as I understand it the local layer gets all new IDs. (2) Am I right in assuming that the AttributeInspector won't work on a locally-hosted featureLayer? I can certainly get by without it, but I'll miss the convenience of it.
Many thanks for your very timely assistance!
Charlie Richman
DC Office of Planning