Latest Contributions by Robert_LeClair

ArcGIS Pro can read DGN as a read-only CAD feature dataset, but it may not maintain the exact “same symbology” you see in MicroStation because Pro renders CAD using extracted CAD attributes (level, color, weight, linestyle, etc.), not the CAD application’s full display rules. This is a known limitation for CAD symbology preservation in Pro (documented for CAD in general; example bug for DWG): BUG-000139735. Also: Introduction to CAD data.

@MRJ1 - in reviewing BUG-000137329 - "The edits of the points for positions in Route Event Layer in ArcGIS Pro are not displayed unless the cache settings are changed", it's listed as "under consideration" within the "internals" with the current workaround to "change the cache settings of the layer to any other option." No time frame for a fix that I know of...

Good morning - I believe this workflow will work for you: 1. Stop the image service so it's not being used while you're updating the MDS. 2. Run the Add Rasters To Mosaic Dataset (Data Management Tools) | ArcGIS Pro documentation GP to add the new single ortho photo to the large existing MDS. 3. Run the Build Overviews (Data Management)—ArcGIS Pro | Documentation but use the Query Definition parameter to select the only the newly added ortho photo to build overviews for. 4. Restart the Image Service.

The Resampling setting in the Rendering group controls display resampling (on-the-fly)—how ArcGIS Pro draws your raster to the screen when the raster grid does not map 1:1 to your current view. Even when you “just pan and zoom,” Pro often has to compute a new value/color for each screen pixel because: Zooming changes the pixel-to-pixel relationship: at most scales, one screen pixel corresponds to a fraction of a raster cell or multiple raster cells, so Pro must decide how to sample/average values to draw the image. The map may be in a different coordinate system than the raster: if so, Pro is also doing an on-the-fly reprojection for display, which requires interpolation. The goal is visualization quality vs speed, and the “best” method depends on whether the raster is categorical (classes) or continuous (imagery/elevation). That’s why the method matters for display: Nearest neighbor: fastest; best for discrete/categorical rasters; preserves original values but can look blocky/jagged. Bilinear: smoother for continuous rasters; alters values (can blur). Cubic: sharper than bilinear but slower; can introduce values outside the input range. Majority: often used for discrete rasters to smooth class “speckle.” Hope this helps!

If you open your Catalog Pane in ArcGIS Pro, navigate to the geodatabase where the annotation is stored, you see icons representing feature classes, anno, maybe rasters and one icon that shows two tables with arrows going between them. See image below:

Yes, there is a way to do this as referenced in this Esri Community post - Create Replica with Different Output Coordinate Sy... - Esri Community - but the technical article referenced in the post no longer exists for some reason. I'll continue to look for it though.

Question for you - when you see the geodatabase in the Catalog Pane, is the relationship class for the feature linked annotation there or is it missing? Please advise.

In ArcGIS Pro, the Map Tips toggle only appears for layer types that support attribute-based map tips (typically feature layers). For LiDAR point cloud layers (for example, a LAS Dataset layer or a Point Cloud Scene Layer (.slpk)), it’s normal to not see a Map Tips option in Layer Properties, because those layers are driven more by filtering/symbology than per-point attribute popups. If you need to see the attributes for a single point, click the Map tab->Explore and click on a *.las point.

Hmmm...the layer that you're applying the *.lyr file to have the same attribute values as the originating source?

This usually happens because the RedEdge-P bands aren’t being treated as one multispectral “scene”—they’re getting added as separate single-band rasters (often with slightly different footprints/pixel sizes), which can display as grayscale, clip unexpectedly, or look misregistered. Try this (best option for MicaSense RedEdge/RedEdge-P) Create/keep your mosaic dataset. Add the imagery using the RedEdge raster type (instead of adding each band manually): Imagery tab > Add Rasters (or Add Rasters To Mosaic Dataset) Raster Type = RedEdge Input Data = the folder with the band TIFFs (typically *_1.tif … *_5.tif) Choose a processing template like Multispectral or All bands This raster type is designed to group the single-band files into one multispectral raster item so the bands align correctly in the mosaic dataset. Reference: Aerial imagery raster types (RedEdge)

For me, if I know I'm creating a project for a specific purpose, I then create a project from a default template such as Map. This gives me the opportunity to create the project and have the geodatabase named after the saved project name. By doing this, I don't have to worrry about renaming the default.gdb and having ArcGIS Pro create a new default.gdb. You can read more about the workflows mentioned here - Create a project | ArcGIS Pro documentation

Certainly. Hopeful the support analyst has additional ideas to assist. In the meantime, you can try a Perform an ArcGIS pro Soft Reset and see if this helps.

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

This behavior is intentional/expected in ArcGIS Pro, not a known defect based on current documentation scope. In Pro, the contextual Versioning ribbon is surfaced for web feature layers that participate in branch versioning with Version Management enabled. A service that contains only tables (no geometry layers) can still expose a 'VersionManagementServer' endpoint, but Pro’s Versioning UI typically won’t light up unless there is at least one feature layer in the map/service. References: Manage branch versions | ArcGIS Pro documentation Branch version scenarios | ArcGIS Pro documentation Workaround: publish/include at least one branch-versioned feature layer (geometry) in the same service (with Version Management enabled); then add the service to Pro and manage versions from that layer while editing/relating to the tables as needed.

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.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by Robert_LeClair

Re: Symbology

Re: Route event layer sometimes not refreshing on map

Re: Build Overviews on a single new raster in a large Mosaic Dataset — how to be truly selective?

Re: Why do raster datasets need to be resampled when panning and zooming in ArcGIS Pro?

Re: Does Feature Linked GDB Anno Upgraded to Pro Lose Feature Linking?

Re: Replication with Automatic Coordinate Transformation in ArcGIS Pro

Re: Does Feature Linked GDB Anno Upgraded to Pro Lose Feature Linking?

Re: Map Tips for Lidar Point Cloud data

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

Re: Multispectral Raster Alignment

Re: Default.GDB

Re: ArcGIS Pro causing Kernel Security Check Failure after update to 3.7

Re: Extracting Polygons from Basemap

Re: Are table-only feature services designed to be published with branch versioning?

Re: ArcGIS Pro causing Kernel Security Check Failure after update to 3.7

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)