Latest Contributions by ThomasCox

I am surprised and disappointed this did not make it in already.  Setting a selection symbol (beyond simply color) seems a basic requirement.  I have written numerous applications that rely on this. It is unfortunate we have to lobby (vote) for it be there. ... View more

I definitely have egg on my face. Some revisions by an associate set the outline color to white that I wasn't aware of, essentially overwriting my earlier symbol assignment.  Sorry for the post and the time spent. Thanks for inquiring regarding this.  The symbols are behaving as advertised. ... View more

Thanks Charles.  I have looked at the github link you kindly provided.  That will definitely get me started.  Additionally, the sample "CustomCatalogContext" from the community samples has provided a great launching point.  I have found the samples very helpful.  ... View more

I need the same functionality.  Has there been any movement on this issue for you? Thanks    ... View more

My post did not accept all of the content I had included.  I had attached a screen shot showing the output window showing I could evaluate the name and type of the feature class and the table requests.  Any insight regarding this would be appreciated. Thanks for your time. ... View more

Following a suggestion by Charles MacLeod of ESRI, I posted this same question to the imagery and remote sensing forum that provides more targeted exposure for this topic.  The imagery and remote sensing version of this post resides at: https://community.esri.com/message/722378-pro-geoprocessing-raster-flip-command-slow ... View more

Charles, thanks for the suggestion.  I have posted this question to the imagery forum you suggested.  The imagery forum posting resides at: https://community.esri.com/message/722377-proper-parameter-value-of-managementdelete-tool I appreciate your time. ... View more

Thanks for your input Curtis.  I have tried numerous strategies to clean up the intermediate raster files with limited results.  I changed the raster type to .tif and attempted to remove the intermediate files with an operating system delete.  This works for the initial files, but encounters locks on the later ones and throws a message the files are being used by ArcPro. I long for the 'old' days when you could simply delete a dataset such as:             IWorkspace pWorkspace = (IWorkspace)ws;             IEnumDataset pEnumDataset = pWorkspace.get_Datasets(esriDatasetType.esriDTRasterDataset);             IDataset pDS;             try             {                 pDS = pEnumDataset.Next();                 while (pDS != null)                 {                     if (ListOfGridNamesToRemove.Contains(pDS.Name))                     {                         pDS.Delete();                     }                     pDS = pEnumDataset.Next();                 }             }             catch (Exception ex)             {                 RemoveGRIDSListErr.Add(ex.Message);             }             System.Runtime.InteropServices.Marshal.ReleaseComObject(pWorkspace);             System.Runtime.InteropServices.Marshal.ReleaseComObject(pEnumDataset); In the Pro SDK, I have not found any object based method that allows this. I understand the Pro paradigm is to call tools to perform these tasks.  Unfortunately, I have not been able to get the "management.delete" tool to behave from code.  Additionally, I am finding in some instances, the geoprocessing tools performance is quite poor compared to their ArcObjects equivalent object methods. Look for an upcoming forum post regarding the raster 'Flip' command.  This poor performance is seen running the tool natively as well through code. Perhaps, this delete issue might have to wait for the developer's summit.    I will update when I gain more insight as to how this process should work. Thanks again to everyone for their input. ... View more

Thanks for responding Curtis. I appreciate your time. I thought the dataset was the proper object from the beginning.  I have written ArcObjects applications that allow this behavior through the dataset, when that didn't work in Pro, I started experimenting with other parameters. As I mentioned, to test the Delete tool free from any sr.lock files associated with having the GRID in the Pro session as a layer, I created the dataset from disk: I passed the raster dataset as a parameter to the tool and encounter the results posted above.  So it seems, independent of any 'layer' intrusion, the tool does not navigate the raster dataset, based off the GPResults message .  As the tool does not call for any environment parameters, I am not clear what else the it requires.  Thanks again for input. ... View more

Thanks again for your input.  I guess I am unclear regarding the Environments setting regarding the Delete tool.  I did look at the Environments setting and it stated No Environments were necessary.  Migrating to the .tif would be a bit arduous, but perhaps I will have to down that road. It is a bit frustrating as the Pro interactive Delete tool doesn't struggle with any of it.  Perhaps one of our friends from esri could enlighten.  Thanks again Dan.  I know you are a strong contributor to the forum and I appreciate you taking the time. ... View more

Thanks Dan for your input. I have spent a good bit of time trying to make this behave.  I have temporarily abandoned the effort to have the delete tool remove GRIDs that have been iteratively created during processing. Instead I have tried to run the tool programmatically against a GRID that has not been touched by the Pro Session. I have tried the rater dataset as a parameter.  The GPResults object IsFailed shows false.  However, when I look at the rest of the parameters of the Results.Messages, it indicates that the GRID I am after does not exist, it appears to ignore the _connectionPath property of the raster dataset.  I checked this during a run and found it be correctly populated.  The ugly screen shot below shows this. When I execute the geoprocessing Delete tool, and examine the GResults, I see a warning message the GRID I am trying to delete does not exist.  The Delete tool does not seem to navigate the rasterdataset and use the _connectionPath. I have looked at the Delete tool and note that it does not call for any environment settings.  I am generating the raster dataset directly from the directories, so the raster is never added to the Pro Session as a layer.  I believe I need to pass more to the ValueArrayList than just the raster dataset, but am not clear as to what. var parameters = Geoprocessing.MakeValueArray(pBasRasDataSet); var gpResults = await Geoprocessing.ExecuteToolAsync("management.Delete", parameters); When I look at the tool in Pro, it only calls for one parameter.  The following screen shot depicts this. I guess the Input Data Element is expecting more than I am providing in my code attempt to execute the tool. I am transitioning an ArcObjects application to Pro where I am able to remove GRIDS created during the ArcMap session.  Any input to resolve the error of my ways would be welcome. ... View more