Latest Contributions by Wolf

Hi Than,  Pro is using the 7 zip library.  I attached a sample project to unzip a project file that appears to work for me, it should work for templates too.  Since Pro ships with the 7z dll you can set the path for the extractor to the Pro install bin folder (c:\ArcGIS is my install location): // set 7z.dll path: SevenZipExtractor.SetLibraryPath(@"C:\ArcGIS\Bin\7z.dll");‍‍ I also used the following NuGet: NuGet Gallery | SevenZipSharp.Interop 19.0.0   ... View more

Hi Lars,   Just to re-iterate the issue one more time: after converting a set of polygons from GML these polygons can be rendered as 'distinct' polygon records as shown below, showing all the expected detail (extrusions etc.):    If we take these 'distinct' polygon records and create one 'multi-part' polygon record using the 'distinct' polygons as parts, the rendered representation has 'holes' as compared to the rendering of the 'distinct' records. I showed the data to the development team and here is the gist of their reply: ArcGIS Pro only renders multipart polygons without 'holes' if these polygons are 'simple' polygons.  One of the requirements of a 'simple' polygon is that 'rings cannot overlap'.  If there's an overlap of parts, rendering can exhibit 'holes' because ArcGIS Pro uses the even-odd rule when rendering polygons.  As defined by this rule overlapping parts will produce holes when rendered.  Here is a definition of the Even-Odd rule: https://en.wikipedia.org/wiki/Even%E2%80%93odd_rule So in order to render the converted GML you have two options: add a 'distinct' polygon for each part of the building (and use an id field to identify polygons belonging to a specific building) or union the polygon parts of a building into a single building polygon (in which case you only get the footprint outline of the building). For the next release, we will try to update our ProConcept documentation to address these rendering behaviors in more detail. ... View more

You can use the snippet below to get this result when searching for these accounts (type string) ' "Test 0", "Test 1", "Test x"' - Note that only Test x doesn't exist: In essence you first do your selection and then search through the selected set one by one to find the 'missing' item. protected override async void OnClick() { Tuple<int, string> selectionInfo = null; try { var accounts = new List<string>() { "Test 0", "Test 1", "Test x" }; selectionInfo = await SelectByAttributeAsync("TestPoints", accounts); } catch (Exception ex) { MessageBox.Show(ex.ToString()); } _ = MapView.Active.ZoomToSelectedAsync(new TimeSpan(0, 0, 3), true); MessageBox.Show($@"{selectionInfo.Item1} records were selected - {selectionInfo.Item2}"); } public static Task<Tuple<int, string>> SelectByAttributeAsync(string featureLayerName, List<string> accounts) { return QueuedTask.Run(() => { var firstLyr = MapView.Active.Map.FindLayers(featureLayerName).FirstOrDefault() as FeatureLayer; if (firstLyr == null) throw new Exception(string.Format("The feature class: {0} does not exist", featureLayerName)); // make list of accounts into 'in' clause var commaList = string.Join(",", accounts.Select(p => $@"'{p}'")); var qf = new QueryFilter() { WhereClause = $@"description in ({commaList})", SubFields = "*" }; var selection = firstLyr.Select(qf); // remainingAccounts tracks first all accounts and each found account will be removed var remainingAccounts = new List<string>(accounts); using (var foundCursor = firstLyr.Search(new QueryFilter() { ObjectIDs = selection.GetObjectIDs() })) { while (foundCursor.MoveNext()) { using (var row = foundCursor.Current) { var foundAccount = row["description"].ToString(); remainingAccounts.Remove(foundAccount); } } } var msg = string.Empty; if (remainingAccounts.Count == 0) msg = "All records found"; else msg = $@"Not found: {string.Join (",", remainingAccounts)}"; return new Tuple<int, string> (selection.GetCount(), msg); }); }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more