Latest Contributions by Robert_LeClair

So one possible workflow to consider: 1. If the data is in multiple feature classes, you the Merge (Data Management) GP tool to merge them into a new, single feature line feature class. 2. Using the new, single line feature class, use the Snap (Editing) GP tool to pull near coincident enpoints and vertices together using a small tolerance. If you have the Production Mapping extension, you can go a little further... 3. Create a corridor for all passes by using the Buffer tool by a short distance that matches the trail width under tree canopy. 4. Dissolve the buffer polygons so you get one continuous corridor polygon. Then use the Polygon to Centerline (Topographic Production) GP tool to get a new centerline.

In reviewing Esri Support cases, there was a recent case using ArcGIS Pro 3.7 where there was an incompatibiilty issue with an Xtools Pro Add-in. Do you have XTools installed by chance? If so, disable it and try again. Maybe related (maybe not): ArcGIS Pro 3.7 Moves to .NET 10 001270: Consolidating the data failed.—ArcGIS Pro | Documentation

As you may know, Enable COGO (Data Management Tools) | ArcGIS Pro documentation adds 5 new attribute fields to your line feature class. As a result, the new fields will be part of the branch's attribute table and visible and editable by all users. You may want to test in a non-production branch before enabling COGO on production data to see if there are any negative items. From what I've read, enabling COGO on a line feature class in a branch version is fine and is a common practice for survey data/land information data.

HI @MariaDube - I see you submitted a Esri Support Services request recently on this item. In reviewing the case, the analyst was not able to reproduce the issue you're experiencing. It may (or may not) be related but I would try a Perform an ArcGIS pro Soft Reset as you recently updated to ArcGIS Pro 3.7. This "might" resolve the issue.

There's a couple ways to accomplish this: 1. In ArcMap, create a layer file (*.lyr) from the layer in the Data Frame that has your predefined category rules. Then in ArcGIS Pro, add that layer to a new map view and use the Apply Symbology From Layer (Data Management Tools) | ArcGIS Pro documentation to recreate the layer symbology in ArcGIS Pro. 2. Or in ArcGIS Pro, use the Unique Values option and set the attribute field for Field 1. Then click Add Field for Fields 2 and 3.

In ArcGIS Pro 3.7, there is a new Extract Scanned Lines (Conversion Tools) | ArcGIS Pro documentation geoprocessing tool that creates line features from a scanned and georeferenced image - jpg - in your case.

Not a programmatic solution but I found this on the Esri Support page: "PatchFinder “will list all products, hot fixes, and patches installed on your local machine.” Download: PatchFinder for Windows That’s the most reliable Esri-provided approach to confirm the patch is present without relying on the Programs & Features product version."

For a DGN CAD feature layer in a 2D map, the usual reason “formatting symbols/sizes” doesn’t seem to work is that size is being driven by a size variable or you’re running into symbol display unit expectations. Try these checks: 1. Remove any attribute driven size Contents pane → right‑click the CAD layer → Symbology Go to Vary symbology by attribute → expand Size (or Marker size / Outline width) → set Field to <None> Point Feature Size Updates Are Not Reflected in ArcGIS Pro 2. Be consistent about symbol display units In 2D, point “size” is in the current symbol display units (for example points), which won’t necessarily match CAD/DGN design units 1:1. Vary symbology by size—ArcGIS Pro | Documentation 3. If symbology changes won't stick, recreate the layer Export/duplicate the data and re-symbolize (don’t re-import the same symbology if the layer is behaving inconsistently). Symbology of a Layer Does Not Match along ArcGIS Pro/ArcMap Interface

Yes. You can create a output layer file (*.lyrx) from the GP tool - Save to Layer File (Data Management). It will store many layer properties including labeling. Save To Layer File (Data Management)—ArcGIS Pro | Documentation

That checkbox is part of the Pyramid geoprocessing environment, which is a global raster-storage setting used by many geoprocessing tools that create/modify raster outputs. It lets you centrally control whether outputs should have pyramids built automatically (and with what levels/resampling/compression), so the same model/script can be run with pyramids on or off without editing each tool. In the specific Build Pyramids GP tool, the environment checkbox is essentially redundant—because that tool’s job is to build pyramids—but it still appears because environments are applied consistently across tools in the geoprocessing framework.

Question: Prior to upgrading to 3.7, did you update to the required .NET framework version described here - ArcGIS Pro 3.7 Moves to .NET 10

‎05-15-2026

Another workflow to consider, create a new target attribute table in the target geodatabase with a GlobalID field and set the geoprocessing environment Preserve GlobalIDs. The target GlobalID must have a unique attribute index as referenced here 003340: The target dataset must have a GlobalID field with a unique index in order to use the Preserve GlobalIDs geoprocessing environment setting.—ArcGIS Pro | Documentation

‎05-14-2026

Yes, typically by converting the multipatch to a 2D footprint polygon, then converting that polygon to lines. Run the Multipatch Footprint (3D Analyst Tools) | ArcGIS Pro documentation first then run the Polygon To Line (Data Management Tools) | ArcGIS Pro documentation second.

‎05-14-2026

Certainly! I'm glad the explanation helped. I would encourage you to search for an existing ArcGIS Pro Idea on this community and if there is not, then add one so it gets visiblility to other customers. The more upvotes it gets, the more likely it will get visibility to the Pro developers. If you feel my answer was correct, you can mark it as "Accept as Solution" to close out this post.

‎05-14-2026

Hmmm...I did get the CONTAINS working on the text field. The key is creating the perhaps LONG list of combinations you mentioned but this is just picking on the initial creation.

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by Robert_LeClair

Re: Multiple Polygons into One -- Averaging best lines

Re: ArcGIS 3.7 - Staging failed error when publishing web layer

Re: Enable COGO on a line feature class with branch version

Re: Using the Append tool on a hosted feature layer with "Optimize performance for feature services" enabled causes ArcGIS Pro to crash

Re: How to use the draw categories function in ArcGIS Pro

Re: Uploading Autocad into Arc Gis Pro

Re: Verify version after Patch install

Re: Symbology

Re: Label Classes: Copy to Multiple Maps?

Re: Build Pyramids environmental setting

Re: ArcGIS Pro Desktop 3.7 Update Issue

Re: Exporting/Copying stand alone table from one GDB to another converts GlobalID to text

Re: Convert a Multipatch feature into Line feature

Re: ArcGIS Pro - Renaming project file breaks toolbox connection with no repair prompt

Re: Sorting data by a predefined list

Re: Create a different symbology based on an attri...

Re: Select by Location in ArcGIS Pro on a multi-la...

Re: Distance Accumulation attributes

Re: Set layer visibility in a map frame - Allow be...

Re: "Holding" Tank Question

Esri Forestry Group (EFG)