Latest Contributions by UmaHarano

Hi Daniel I shared your question with the 3D Team. He recommends contacting technical support if possible. He says it would be much easier to troubleshoot this problem with support. Thanks Uma ... View more

Hi  Arcade parser is not currently available through the Pro SDK. Uma ... View more

Hi! I am assuming you want to display Pro's coordinate system control in a dockpane or a dialog in your add-in. The sample displays this control in a "ProWindow" - which is like a "Dialog". These are the rough steps to accomplish this: * Add a dockpane or a ProWindow to your add-in using the SDK Item template. * In the XAML that gets stubbed out for you, you will add the reference to ArcGIS.Desktop.Mapping.Controls dll. xmlns:mapping="clr-namespace:ArcGIS.Desktop.Mapping.Controls;assembly=ArcGIS.Desktop.Mapping"‍ * You will be able to "display" the coordinate system picker "UserControl" that is in this assembly.  You will do that using something like this in the xaml:  <mapping:CoordinateSystemsControl x:Name="CoordinateSystemsControl" ConfigureControl="{Binding Path=ControlProperties}"/>‍‍ In the sample I mentioned, check out the file - Geometry/CoordinateSystemDialog/UI/CoordSysDialog.xaml This is the "ProWindow" that displays the control. It has a code behind file, and a View/ViewModel associated with it. All these are in the UI folder of the sample. These items together implement the logic for the control. Let me know if you need any help. Thanks Uma ... View more

The output points from both tools would be the same. The output lines, on the other hand, might not be split at the same locations because the intention of the analysis differs. The output lines for LOS, when not using any multipatches, are split based on the logic illustrated in the cross-sectional view below.   The LOS tool profiles the input line on the surface and the point at which the surface goes out of view to the observer, at the crest of the hill, is where the line gets split (green is visible to the observer, red is not). So, I recommend using Intersect3DLineWithSurface since both the point output and line split locations will always be the same.   We know that 3D Analyst tools aren’t supporting Pro’s surface layers yet. This will happen in an upcoming release. In the meantime, you need to use regular file based raster layers. If you’re wanting to use elevation service based data you can use the CopyRaster tool to extract an AOI from an elevation service as a local raster. And yes, you need to use Geoprocessing.ExecuteToolAsync to run GP tools. ... View more

Abel, Not sure if you have seen this sample - CoordinateSystemDialog sample Thanks Uma ... View more

Hi Tim, Thank you for the detailed repro steps and the video. I see this issue too with standalone tables. If you reopen the Map, the chart shows up in the TOC. I will get back to you soon. Thanks Uma ... View more

Hi Tim, I tried to do the same thing you are doing - I modified Stephen's code to use the layer name to create the chart. I then iterated through each feature layer and applied the Chart method. The TOC was updated for me correctly. I had about 9 feature layers (from File GDBs).  I was on Pro 2.5. To track down where the issue is happening, can you please give me more information? Some code snippets, info about the data you are using, etc might help us track this down. Thank you! Uma ... View more

Hi Simon This limitation still exists. The Pro development team is looking at fixes. In the meantime, you can access the LayerDocument and the CIM Definition to accomplish what you need - // create a layer and add it to a groupLayer string urlLyrx = @"\\path\States.lyrx"; QueuedTask.Run( () => { var layerDoc = new LayerDocument(urlLyrx); var cimlyrDoc = layerDoc.GetCIMLayerDocument(); var defn = cimlyrDoc.LayerDefinitions[0] as CIMFeatureLayer; defn.Visibility = false; defn.Name = "Test Layer"; //defn.Renderer = .. //defn.DisplayFilters = //etc var createParams = new LayerCreationParams(cimlyrDoc); FeatureLayer flyr = LayerFactory.Instance.CreateLayer<FeatureLayer>(createParams, MapView.Active.Map); });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Thanks Uma ... View more

Hi Simon LayerDocument class allows you to configure a layer's properties prior to adding it to the map.  You can either create a new LayerDocument (using the available constructors) from an existing lyrx file or an existing feature layer in a map. Note: You also have the option of creating a blank LayerDocument and configuring all the properties from scratch if you want. But this is rare. You can then use the configured LayerDocument and Create a layer (or Group Layer)  using the CreateLayer method. The specific overload you will need is this: https://pro.arcgis.com/en/pro-app/sdk/api-reference/index.html#topic26527.html  I will post a snippet on how to do this if you need further help with this. Thanks Uma ... View more

Hi Barbara I modified the sample project referenced in that wiki page to save a project using the SaveAsync method. The OnWriteSettingsAsync method was called for me. Is there anything specific about how you are calling SaveAsync? Thanks Uma ... View more

Hi Alex, I have attached a modified DragAndDrop sample that shows you how to drag and drop content from the Map's TOC. To use the sample: 1. From the Add-In tab, click the Drag and Drop TOC Items button. A dockpane with a text box will show up. 2. Drag any layer(s) from the active map's TOC into the dockpane's text box.. 3. The text box in the dockpane will list information about the map members being dragged and dropped. Thanks Uma ... View more