Latest Contributions by NobbirAhmed

Thanks for the suggestion - we'll document.  ... View more

The expected result can be achieved by passing a flag to Geoprocessing.ExecuteToolAsync(...) method. Here is the code snippet: // inputs: symbologyLayer could be a layer file (*.lyrx) or a layer in the map var parameters = Geoprocessing.MakeValueArray(inputLayer, symbologyLayer); // set flags GPExecuteToolFlags flags = GPExecuteToolFlags.GPThread;   // call ExecuteToolAsync var gp_result = await Geoprocessing.ExecuteToolAsync("ApplySymbologyFromLayer_management", parameters, null, null, null, flags); ... View more

What are the parameters of the tool? I see there is only one GP tool named Calculate Statistics in the Data Management - are you talking about that tool (I guess not as this tool only takes a raster as input)? Or a custom tool? ... View more

If you need help with Python scripting please shoot me a mail at nahmed@esri.com (also some sample data will be helpful) ... View more

Each tool having a class approach is not taken in ArcGIS Pro SDK. I'll pass this info to the team. ... View more

Let’s communicate via email until we find a solution – if it is okay with you. Thanks. nahmed@esri.com ... View more

Could you please try this way (without a comma between FEET and Sum so that it matches Python syntax)? var statistics_fields = "FEET Sum"; ... View more

Most probably you are right about: *****syntax of these variables is assumed to be the failure***** I'll forward this to appropriate team. Meanwhile, I'll try to find a workaround. Thanks for your patience. ... View more

Just to be sure that issue is NOT caused by other parameter settings, I'm asking - have you called MakeValueArray on the spatial_ref object before passing it to MakeEnvironmentArray? var spatial_ref = await QueuedTask.Run(() => {            return SpatialReferenceBuilder.CreateSpatialReference(3857); }); // call MakeValueArray on spatial_ref so that ExecuteToolAsync can internally use the object var sr_param = Geoprocessing.MakeValueArray(spatial_ref); ... View more

Have you used your code or the code in the sample? In the sample code (from the documentation link) a QueuedTask.Run(...) is used to created the spatial reference object. ... View more

As your sp_ref is an object you need to pass it through MakeValueArray(..). Could you please try with these changes: var sp_ref = Geoprocessing.MakeValueArray(SpatialReferenceBuilder.CreateSpatialReference(102629)); var args = Geoprocessing.MakeValueArray(in_table, out_table, statistics_fields, case_field); var envi = Geoprocessing.MakeEnvironmentArray(outputCoordinateSystem: sp_ref); If you follow the documentation you'll find which objects are supported directly. https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-Geoprocessing#create-an-array-of-environment-settings If you scroll down the above documentation you'll find this example: // example of using ArcGIS.Core.Geometry.SpatialReference objectvar spatial_ref = await QueuedTask.Run(() => {     return SpatialReferenceBuilder.CreateSpatialReference(3857); });// call MakeValueArray on spatial_ref so that ExecuteToolAsync can internally use the objectvar sr_param = Geoprocessing.MakeValueArray(spatial_ref); ... View more

Assuming you are trying to deploy a .Net Add-in, you can use System.IO.Directory.GetCurrentDirectory() method to get the path of the ArcGIS Pro Project where the default geodatabase and the toolbox reside: string spath = System.IO.Directory.GetCurrentDirectory(); The Project folder looks something like this: For this particular folder structure, the spath value (under C: directory) will be: C:\temp\AddinMovedHere\OneDown\TwoDown From there, using C# (or VB) concatenating functions, you can derive other paths such as to Geodatabase and Toolbox. ... View more

Could you try first converting the polygons to polylines and then using the polylines to compare? If you want you can use Polygon to Line under Data Management Toolbox, in Features toolset. http://support.esri.com/en/technical-article/000007707 ... View more

Hi Darren, sorry to inform you that this issue started showing up after 10.4 and resolved in 10.5.1 Most of the time your workaround works: "The only way I can get the extension to be activated is to open the Extensions dialog, which fires the __init__ event handler (without even clicking on the extension to turn it on!)." ... View more