Latest Contributions by Robert_LeClair

As this data is coming from ArcGIS Online, do you have the name of the layer so I may test it on my side?  For the exported layer from the original layer, was it based upon a selection? ... View more

For the Environment Setting, Transfer field domain descriptions (Environment settting), this only works if you're output is a shapefile or a dBASE output.  What is your output format? ... View more

To add to what Eugene said - here's the Help documenation of label basics and how to turn on labels - Labeling basics—ArcGIS Pro | Documentation ... View more

BUG-000165171 was initially reported in ArcGIS Pro 3.2.1 and reproducible in ArcGIS Pro 3.4.  Current workaround is to add an extra vertex to ensure the endpoint of the sketch avoids the edge of the feature being split.  Not ideal I know... ... View more

With the 3D Analyst extension licensed, I can confirm that the "Feature to 3D by Attribute" is in the 3D Analyst toolbox and the Conversion toolset.  The other one, 3D Features to 2D Features" I'm not seeing in ArcMap nor ArcGIS Pro which leads me to believe it could be a custom tool perhaps? ... View more

Interesting...for the polgon feature class in question in the Feature Dataset, is it registered as versioned or is it nonversioned? ... View more

Great to hear from a long time Esri user!  I too started my career a long time ago - 1992 with Arc/Info 5.0, saw the transition to PC Arc/Info, ArcView GIS, ArcMap and ArcGIS Pro with a few years of Atlas GIS too! From scouring the help documentation, I found 4 instances where buildling pyramids are not beneficial. 1. Storage Space: Pyramids require additional storage space. If disk space is limited, you might opt not to create pyramids to conserve space. 2. Processing Time: Creating pyramids can be time-consuming, especially for very large datasets. If you need to quickly access or process the data without delay, you might skip building pyramids initially. 3. Data Sensitivity: In some cases, the additional files created by pyramids might not be desirable, especially if the data is sensitive or needs to be kept in its original form for compliance reasons. 4. Temporary Use: If the raster data is only needed for a short-term project or a quick analysis, building pyramids might not be necessary. ... View more

That is correct - ArcGIS Pro 2.9.x has this BUG but when you upgrade to ArcGIS Pro 3.x (current version is 3.4) then the bug is no longer present. ... View more

Sadly, I think the file geodatabase is lost based upon your screen grab. ... View more

Hi @JairoCordero - thank you for the screen grab.  Question - what release of ArcGIS Pro was this captured from?  Please advise. ... View more

I reviewed BUG-000146074's update and this is not reproducible in ArcGIS Pro 3.x releases now.  It was an issue with ArcGIS Pro 2.8, 2.9 and 2.9.1. ... View more

If you have ArcMap still installed on your computer, you can continue using it for as long as you want.  Even though the program is no longer supported, it continues to work as it always did. ... View more

I'm not seeing those tools in ArcGIS Pro so that leads me to believe that there is a new workflow for 3d to 2d conversion.  Here are a few resources to consider... How To: Convert 3D Features to 2D in ArcGIS Pro Convert 3D Features to 2D in ArcGIS Pro - Esri Videos: GIS, Events, ArcGIS Products & Industries ... View more

@AllenDailey1 - do you have any schema changes prior to rebuilding the address locator?  From the internals:  use the Rebuild Address Locator (Geocoding) tool for updating the locator with the current reference data and use the Create Locator (Geocoding) tool to re-build the locator when a schema change (e.g., adding a field) is made to the reference data feature classes. ... View more