Latest Contributions by DwayneKuykendall

We have been using the ArcGIS Toolkit "Preview" Table of Contents in our WPF application.  As we load layers, we set the "Layer.ShowInLegend" property to true or false base on some business logic.  This was working great. We recently discovered that Windows Location Services does not provide an accurate GPS location.  The release notes for .Net SDK 100.10 indicates the possibility to utilize a NMEA data source, such as a COM port GPS.  This motivated us to finally upgrade the applications to 100.10.  We also upgraded to the 100.10 Toolkit and associated Toolkit Preview.  Once the projects were upgraded, we noticed that all layers on the map show in the Table of Contents, regardless of the "ShowInLegend" setting. We have downgraded to SDK 100.9, 100.8, and 100.7 with corresponding Toolkits.  It appears this functionality is broken at least in these versions.   I have attempted to compare the 100.4 toolkit source code with the 100.10 code.  There are few similarities.  Where 100.4 has an "ObservableLayerContentList", there is no such object in 100.10. I would like to think I'm not the only person using the TOC.  Has anyone else experienced this issue?  Does this issue also exist in the "Legend" toolkit control? What to do? ... View more

We have spent quite a bit of effort converting our ArcEngine applications to .Net Runtime.  On of the greatest challenges is working with related data.  I have opened a few tickets with ESRI regarding this in the past, but have been presented with no solutions. For clarity, we work almost exclusively offline using replicas. Our challenge:  Join the attributes of two tables so the resulting table can be used in a definition expression to filter child layers on the map. The problem:  We frequently work with map layers that are related.  In general, there is a "Parent" layer.  Other layers are related to the parent.  There are many cases where we need to show a subset of the parents an only the child layer data that is related to this subset.  For example, suppose the map consisted of a parent layer, US "States" and one child layer containing State "Parks".  If the States layer has a "Population" attribute, we may want to set a definition expression on the "States" layer and also filter the "Parks" layer to the resulting States. We were presented with a solution from ESRI that requires querying the States layer for the required parent results.  Then we iterating through each result executing  "QueryRelatedFeaturesAsync" to get the child features and add each child feature to a feature collection.  Needless to say, this is EXTREMELY SLOW. Surely there's a better way. Any suggestions are welcome.  We remain hopeful that the .Net Runtime will mature into a product that truly does embrace related data. Thanks, ... View more