Latest Contributions by RichardFairhurst

@ChrisFoxI had never tried the SQL syntax you outlined, but this expression does work in ArcMap and ArcGIS Pro for related data in the same geodatabase.  This syntax is only briefly discussed in the Subqueries section of the SQL reference for query expressions used in ArcGIS website.  That section doesn't include an example that was quite as clear or useful to me as the one you have given.  I frankly would like to see your example added to that section, since if it had been there years ago I would have been much more likely to see the usefulness of this approach and not had to develop some of the workarounds I came up with. Your example works for file geodatabases as well, despite the warning that file geodatabases only offer limited support for subqueries.  The Subqueries section basically says that help for using them is specific to the DBMS documentation of my enterprise geodatabase.  Since I've mostly worked with file geodatabases that limitation warning had kept me from even trying to figure out or use Subqueries, but based on the example you have outlined I believe I actually now have a use for them.  Thanks. ... View more

I also figured out how to implement a property that can set the IsSelected property of the ListBoxItems of a ListBox so that it supports a TwoWay update when the Selection Mode is set to Extended and it does not have to be passed as a CommandParameter to an ICommand button.  I found that the Extended SelectionMode only mostly worked properly when I included the ListBox parameter for VirtualizingStackPanel.IsVirtualizing="False" along with setting the SelectionMode="Extended".   It does not appear to trigger a notification when the user actually extends their multiselection in the ListBox, so as far as I can tell the  evaluation or programmatic use of the ListBox IsSelected property has to be triggered by Methods and Actions you design in your code. In this example code I am presenting a list of Lot numbers so I made my ItemSource binding to an ObservableCollection called Lots.  This ObservableCollection contains ListBoxItems based on a custom class called LotSelector.  I had to set up an ItemTemplate for the ListBox so the list would display the Item property of the LotSelector custom class in the ListBox and an ItemContainerStyle of ListBoxItems that would assign the IsSelected property of each ListBoxItem to the IsSelected property of my LotSelector custom class.  Here is the xaml for the ListBox:   <ListBox x:Name="lbxLots" VirtualizingStackPanel.IsVirtualizing="False" SelectionMode="Extended" ItemsSource="{Binding Lots, Mode=TwoWay}" SelectedItem="{Binding SelectedLot}"> <ListBox.ItemTemplate> <DataTemplate> <TextBlock Text="{Binding Item}"></TextBlock> </DataTemplate> </ListBox.ItemTemplate> <ListBox.ItemContainerStyle> <Style TargetType="{x:Type ListBoxItem}"> <Setter Property="IsSelected" Value="{Binding Mode=TwoWay, Path=IsSelected}" /> </Style> </ListBox.ItemContainerStyle> </ListBox>   I then added a Class Item to my project named LotSelector and defined two classes in the file.  The first class is named LotSelector and stores the values and IsSelected state of each ListBoxItem.  The second class is named LotItemComparer based on the IComparer class so that the LotSelector instances could be sorted and kept unique using a SortedSet<LotSelector> ViewModel property.  Here is the LotSelector.cs file code:   using System; using System.Collections.Generic; using ArcGIS.Desktop.Framework.Contracts; namespace RivCoSearchForms { public class LotSelector : PropertyChangedBase { private string _item; public String Item { get { return _item; } set { _item = value; NotifyPropertyChanged(() => Item); } } private bool _isSelected; public bool IsSelected { get { return _isSelected; } set { _isSelected = value; NotifyPropertyChanged(() => IsSelected); } } } public class LotItemComparer : IComparer<LotSelector> { public int Compare(LotSelector x, LotSelector y) { // TODO: Handle x or y being null, or them not having Items return x.Item.CompareTo(y.Item); } } }   For the ViewModel I added standard code for my Lots ObservableCollection<LotSelector> property for the ListBox ItemSource and a SelectedLot string property for the SelectedItem property of the ListBox.  I also added a SortedSet<LotSelector> private property of the ViewModel to ensure the Lots were distinct and sorted and could be manipulated on the MTC thread.  I have included a Command implementation to show how the ListBox could be populated based on the Lot data in a Layer.  (I tried to simplify the code of the Command from a more complex version and have not tested it, so the Command code may not run correctly and need correction.)   Here is the ViewModel code:   private ObservableCollection<LotSelector> _lots = new ObservableCollection<LotSelector>(); public ObservableCollection<LotSelector> Lots { get { return _lots; } set { SetProperty(ref _lots, value, () => Lots); } } private string _selectedLot; public string SelectedLot { get { return _selectedLot; } set { SetProperty(ref _selectedLot, value, () => SelectedLot); // Blank out Book, Page list and text block Message = null; } } private SortedSet<LotSelector> ListLotsSelected; public ICommand CmdCancel => new RelayCommand((proWindow) => { // TODO: set dialog result and close the window (proWindow as ProWindow).DialogResult = false; (proWindow as ProWindow).Close(); }, () => true); public ICommand CmdListLotsInLayer => new RelayCommand(async (proWindow) => { ListLotsSelected = new SortedSet<LotSelector>(new LotItemComparer()); // Get the Active Mapview var ActMap = MapView.Active; // Get the search layer from its name var fLayer = ActMap.Map.GetLayersAsFlattenedList().OfType<FeatureLayer>().FirstOrDefault(l => l.Name.Equals("Search Lot Layer")); // If layer exists proceed if (fLayer != null) { // Set up a Queued Task for map changes int iCount = await ArcGIS.Desktop.Framework.Threading.Tasks.QueuedTask.Run(() => { // Execute a Search on the layer using (RowCursor RecMapCursor = fLayer.Search()) { int cnt = 0; // Iterate the found cursor rows while (RecMapCursor.MoveNext()) { // Get current row as a feature using (Feature feature = (Feature)RecMapCursor.Current) { // Get the APN value of the feature LotSelector Lot = new LotSelector(); int number; bool success = int.TryParse(feature[LotField].ToString(), out number); if (success) { Lot.Item = feature[LotField].ToString().PadLeft(4); } else { Lot.Item = feature[LotField].ToString(); } // Set the IsSelected property to select the ListBoxItem Lot.IsSelected = true; // Update the ListLotsSelected parameter ListLotsSelected.Add(Lot); cnt += 1; } } return cnt; } }); if (iCount > 0) { Lots.Clear(); foreach (LotSelector _Lot in ListLotsSelected) { Lots.Add(_Lot); } } } }, () => true);     ... View more

Also, the BindingContext is set up properly in my xaml file since my bindings and code are working property and giving change notifications from my textboxes, buttons and listboxes in response to the get and set code of the properties I set up for them.  Only the radiobuttons and checkboxes bindings and notifications are not working.   However, you are right that I copy/pasted properties that were set to private and didn't notice it.  Changing it to public solved the issue. ... View more

I have adapted my code to generally follow the the example you provided and was able to get the buttons to close the ProWindow the way I wanted.  However, I am not sure I have adapted the code in a way that is fully consistent with keeping the Model separate from the ViewModel.  In the example provided the Show button class generated with the ProWindow class seems to have been used as the Model class for the MVVM interactions with the map and/or data.  However, I am not using the Show button class created for the ProWindow to launch it.  Instead I am using a class that sets up the map with layers that support multiple ProWindow options and launch the appropriate ProWindows based on the choice the user makes in a combobox.  That class already has extensive code and I don't want to expand it with the code that the example used in the Show button class.  But I am willing to create a new class or call the Show button class to handle the Model portion of the MVVM approach for each ProWindow, if that is recommended. The Cancel button that just closes the ProWindow is fine and fully consistent with the purpose of  the ViewModel since it does not interact with the map or any data.  The other button, called the Locate button, currently is working the way I want it to work, but it is performing map and data operations in the ViewModel that may be better handled in a separate Model class according to MVVM.  I would appreciate comments on which portions of this code should be moved from the ViewModel into a separate Model class to make it more consistent with the approach recommended for MVVM.  Here is the code:     public ICommand CmdLocate => new RelayCommand(async (proWindow) => { String layerName = "Search PLUS Cases"; var ActMap = MapView.Active; var fLayer = ActMap.Map.GetLayersAsFlattenedList().OfType<FeatureLayer>().FirstOrDefault(l => l.Name.Equals(layerName)); if (fLayer != null) { if (PLUSCase != null && PLUSCase != "") { string whereClause = "CASE_ID = '" + PLUSCase.Replace("'", "''") + "'"; var iCount = await ArcGIS.Desktop.Framework.Threading.Tasks.QueuedTask.Run(() => { // Set up Definition Query filter for the layer Module1.SetLayerDefinition(fLayer, whereClause, "PLUS Cases"); // Count the filtered features in the layer var cnt = 0; using (var cursor = fLayer.Search()) { while (cursor.MoveNext()) cnt++; }; if (cnt > 0) { // Pause Drawing ActMap.DrawingPaused = true; // Clear all selected features in the map ActMap.Map.SetSelection(null); // Select the filtered features fLayer.Select(); // Zoom to Selection ActMap.ZoomToSelected(); // Reset the camera zoom to zoom out slightly MapView mapView = ActMap; // Get the camera for the Active MapView Camera camera = mapView.Camera; // Increase the scale by 40%. camera.Scale *= 1.4; // Zoom to the camera scale mapView.ZoomToAsync(camera, TimeSpan.Zero); //Make the layer visible fLayer.SetVisibility(true); // Resure Drawing ActMap.DrawingPaused = false; } else { //Make the layer invisible fLayer.SetVisibility(false); } return cnt; }); // If no selected features if (iCount == 0) { // Show message that No Case Match was found Message = "No Match Found!"; } else // If there are selected features { // TODO: set dialog result and close the window (proWindow as ProWindow).DialogResult = true; (proWindow as ProWindow).Close(); } } } }, () => true);             ... View more

The code works in Python 2.7 32 bit, which ArcMap uses, and in Python 3.X 64 bit which ArcGIS Pro uses.  The ArcGIS Pro Python requires that you maintain an active connection to ArcGIS Online through ArcGIS Pro to work, so whether or not you normally use ArcGIS Pro you have to periodically open it to maintain the AGOL connection for Python. The Python version you use makes no difference in how you code the dictionary Data Transfer portion of the script.  You do have to enclose in parenthesis the outputs of all the print statements in Python 3.X to avoid an error.  The advantage of using Python 3.X for this code is that it supports access to more than 2 GB of RAM and is much less likely to fail due to an out of memory error when you work with very large datasets. ... View more

I voted for your idea and would have a use for this.  Please also vote for my idea, which gives other examples of how it would be useful to be able to use Arcade for some of the parameters of other tools. Allow Arcade Expressions in Parameters of Geoprocessing Tools ... View more