Latest Contributions by Robert_LeClair

As stated above, no.  But this Learn ArcGIS lesson provides another workflow to do something similar - Extract high-resolution land cover with GeoAI | Documentation ... View more

I did search the Esri Support Services cases for the "Stop Code..." error but besides your case, do not see any previous cases listing this item.   In full transparency, I did use the Esri Support AI chatbot asking for an explanation of the error message and this is what it returned: <CLIP> `Stop Code: KERNEL_SECURITY_CHECK_FAILURE (0x139)` is a **Windows Blue Screen (bugcheck)**. It means Windows detected **kernel-level corruption or an illegal operation**—most commonly caused by a **faulty/buggy device driver** (often GPU, storage, network, USB), **security/antivirus filter drivers**, or **RAM/disk issues**. It’s **not an ArcGIS Pro-specific error code**. If this happens while using ArcGIS Pro, Pro is usually just **triggering** an underlying driver/system problem (heavy GPU drawing, lots of I/O, security scanning temp/workspaces, etc.). Try these checks: - **Update or roll back drivers** (start with GPU, then chipset/storage/network). - If allowed by IT, **test without third‑party antivirus/EDR** or with temporary folder exclusions (Esri notes security software can interfere with Pro’s file access): [Troubleshooting General Function Failure errors in ArcGIS Pro](https://support.esri.com/en-us/knowledge-base/000040196) - Run Windows integrity checks: `sfc /scannow` and `DISM /Online /Cleanup-Image /RestoreHealth` - Test **RAM** (Windows Memory Diagnostic) and **disk** (SMART/CHKDSK). - Check `C:\Windows\Minidump\` and Event Viewer/Reliability Monitor; the minidump usually points to the **specific driver**. <END CLIP>:   I then followed up with I'm using 3.7 and this was it's response: <CLIP> ArcGIS Pro 3.7 itself doesn’t generate KERNEL_SECURITY_CHECK_FAILURE (0x139)—that’s a Windows BSOD usually tied to a driver or hardware issue. For Pro 3.7, the most relevant troubleshooting is GPU/driver stability: Try these Pro-specific checks Update your GPU driver from the manufacturer (NVIDIA/AMD/Intel). If you’re on a laptop, use the laptop OEM driver track first. Esri guidance: Troubleshooting Performance Issues in ArcGIS Pro In ArcGIS Pro, switch the Rendering engine (this can avoid a problematic DirectX 12 driver path): Pro: Project > Options > Display Change Rendering engine from DirectX 12 (default) to DirectX 11 or OpenGL, then restart Pro. Doc: Set display options—ArcGIS Pro If Pro reports graphics adapter issues, Esri notes this can be due to a corrupted/out-of-date driver: Compatible graphics adapter not found <END CLIP> So it's a start and something to bring up with the Esri Support Services analyst when you speak with them.  Hope this helps a little bit. ... View more

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. ... View more

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. ... View more

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. ... View more

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.   ... View more

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." ... View more

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. ... View more

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 ... View more

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   ... View more