Latest Contributions by Robert_LeClair

Although I don't have an answer for this question, it was discussed with geodatabases about 2 years ago in this thread.  If there are orphaned locks in place, then you can use the Compact geoprocessing tool to delete LOCK files. ... View more

EHSA does not apply extra “weight” to 99% vs 90% when it assigns the pattern categories (New/Consecutive/Persistent/Sporadic/etc.). For the pattern logic, each time step is effectively treated as hot / cold / not significant based on the Gi_Bin significance classification (after FDR, if you enabled it). The strength (90 vs 95 vs 99) affects whether a bin is considered significant, but once it is significant, the temporal pattern rules don’t further differentiate 90% from 99% for category assignment. So in your examples: A: …, H(90), H(90), H(90) B: …, H(99), H(99), H(99) If both meet the definition of Consecutive Hot Spot (final time step is a hot spot and there’s an uninterrupted run of hot spots at the end, with the run not long enough to be “persistent”), then EHSA will categorize them the same. The 99% sequence doesn’t get special priority for being “more confident,” aside from being less likely to flip to not significant. The “fuzzy weighting between 90/95/99” concept exists in a different tool: Hot Spot Analysis Comparison, which explicitly provides options like Combine 90/95/99 significant, Exact matching, etc., and documents the similarity weighting approach. EHSA’s pattern categories are not based on those similarity weights. ... View more

If you check the "Change missing values to NoData" box, does the "extra" class disappear?  If any values fall outside your defined ranges (for example, min/max slightly beyond what you assumed, or gaps between ranges), they can be written out as their original values, creating an extra output value (“6th class”). ... View more

VirtualRepository.CreateClone is an internal ArcGIS Pro operation you can see in Diagnostic Monitor when Pro is cloning (copying) the layout/map state into a temporary “virtual” workspace to render/export (for example, to isolate each map series page/export so it can draw consistently). It isn’t a layer/service call itself—more like Pro preparing an internal export “snapshot.” When it suddenly becomes very slow, it’s usually because something in that export snapshot is expensive to resolve (commonly complex symbology, lots of vector content, or raster content), or you’ve hit a version-specific performance issue. There was BUG-000167349 for ArcGIS Pro that was found in 3.2.2 but fixed at 3.6 and 3.5.8 versions. You could try a flattened PDF export to see if that reduces the processing time. ... View more

Agree @MichaelVolz - I'll keep digging around. ... View more

Yes.  In the Convert Labels To Annotation (Cartography Tools) | ArcGIS Pro documentation help documenatation, it states:   - Label class scale ranges are respected. When the tool generates annotation for a specific map scale, it will only convert label classes that are turned on and visible at that scale. - If you are producing annotation at a variety of reference scales, design the map for each of those scales and avoid setting a reference scale in the map. You can then convert the labels to annotation for each scale and name them appropriately, for example, CitiesAnno_1000, CitiesAnno_100000, and so on.  I understand your disappointment.  There is an ArcGIS Idea here - ability to set different scales for different anno... - Esri Community - you can upvote so it gets some traction with the Pro Dev team. ... View more

In ArcGIS Pro, Set Data Source is intended to repoint layers to a workspace-based datasource (file GDB, enterprise GDB/SDE, folder, etc.). A Portal hosted feature layer is a web layer item, so it often won’t behave like a selectable “datasource” in that dialog—leading to what you’re seeing (OK becomes Open, and opening the item shows “this container is empty”). One workflow to consider is in the Catalog Pane, browse to the hosted feature layer and add it to the current map.  Then reapply the symbology from the "old layer" to the "new layer" using the Apply Symbology from Layer command.  Finally, remove the "old layer" and save your project. ... View more

Convert Labels To Annotation is working as designed here: it only converts label classes that are turned on and visible at the conversion scale. So at 1:8500, only your 1:6001–1:9000 label class is eligible to be converted; the other 4 classes are out of scale and won’t generate annotation.  What you could do is run the "Convert Labels to Annotation" GP tool once per scale range with the name of each FC identified by the scale.  I have not worked with the Tiled Labels To Annotation (Cartography Tools) | ArcGIS Pro documentation GP tool but it may be worth looking into as well. ... View more

That purple border is the chart view focus/active selection indicator in ArcGIS Pro (it’s not a “chart border” formatting setting), so there isn’t an option in the Chart Properties pane to turn it off. A workflows to consider so the purple border doesn't show.  Click a different view/pane first (for example, click your Map tab or the Contents pane) to remove focus from the chart, then try Export -> Capture To Clipboard again. ... View more

An easy way to do this is: 1.  Duplicate the layer in the Contents Pane 2.  For the newly created copy that is above the existing layer, create a Definition Query Genus='Stump' 3.  Symbolize the top layer with your desired "stump" symbol. 4.  Keep the original layer below, symbolized by planting season.   I "think" this would work.  Question - do you need the stump symbol to be a single symbol or by season year as well? ... View more

Since it seems that the shapefile is "somewhat" working in ArcGIS Pro, a few things I would try before exporting to a geodatabase. Recover a Corrupt Shapefile (ignor the ArcMap stuff in the document but run the Check Geometry and Repair Geometry GP tools and retry the export) From CoPilot - "The warning is generic and does not list the failed records directly — instead, it points to a file containing the full list of Object IDs of the records that could not be processed ." The file it's throwing an error message for is G-Manhole-20255.fid.  Open that file in notepad/wordpad and review the ObjectsID's / FID's.  Are there missing or strange ID's? ... View more

I think this may be related to BUG-000131663 for ArcGIS Pro - try the workaround in the link and see if that addresses the wavy line issue. If not, then try this.  If the callout (or anything underneath it) uses transparency, export a Flattened PDF (Share > Export Layout > Flattened PDF) to remove transparency tiling artifacts. ... View more

Or this workaround would work too -  Overlay the header with a manual multi-line text box (layout-only) Layout: Insert > Graphics and Text > Rectangle text Place it over the header; set background to white to hide the original header text ... View more