Latest Contributions by Robert_LeClair

In full transparency, the Esri Support AI Chatbot came back with this below.  It's somewhere to start in troubleshooting your expression: Use Distinct() on a FeatureSet and pass both field names to get unique combinations of `Naziv` + `TipAlteracije`: var u = Distinct($layer, ["Naziv", "TipAlteracije"]) return u If you need it as a text list (for a report/dynamic text), concatenate the distinct rows: var u = Distinct($layer, ["Naziv", "TipAlteracije"]) var s = "" for (var r in u){ s += r.Naziv + " | " + r.TipAlteracije + TextFormatting.NewLine } return s Reference: [Arcade FeatureSet functions — Distinct](https://developers.arcgis.com/arcade/function-reference/featureset_functions) ... View more

If you don't need to run Python, then the Frequency (Analysis Tools) | ArcGIS Pro documentation will do the job easily enough. ... View more

ArcGIS Pro 3.5 generally does not recognize the Autodesk coordinate system definition stored in a DWG from AutoCAD Map/Civil 3D (including “NAD83 California Zone 5 (US Survey Feet)”). When Pro can’t detect an Esri spatial reference for a CAD dataset, it treats it as Undefined and may assume it matches the map’s coordinate system. One option to consider: Create an Esri-format projection file for your target coordinate system. Place it in the same folder as the DWG. The name must match the DWG exactly, e.g. MyPolyline.dwg MyPolyline.prj Pro will then use that PRJ to define the CAD dataset’s coordinate system. Per the documentation that Dan mentioned - "an AutoCAD file may contain coordinate system information in the DWG or DXF file created using the Esri ArcGIS for AutoCAD plug-in application, or as a result of the Export To CAD geoprocessing tool. " ... View more

Understand.  So, sadly, in ArcGIS Pro, there isn’t a built-in dynamic spatial filter that continuously re-evaluates a layer as another layer’s geometry changes (including “within a distance”).  I know one can do this running a series of GP tools to ultimately get to the updated list point of points within 10 miles of a wildfire perimeter.  Presumably one could script the workflow and schedule the Python script to execute daily via Windows Task Scheduler.  Could do the same thing in ModelBuilder too. ... View more

Okay.  So Experience Builder can do “points within a straight-line distance of polygons” using the Query widget (not the Filter widget). Here are some steps you can try: Add a Query widget and set the data source to your points layer. In the Query widget, add a Spatial filter and choose Selected features from data source (the option that returns features that have a spatial relationship with features in another layer). Add filter layer = your polygons layer. Turn on Enable buffer and set the distance and units (this is the “within a distance” part). Use the Query result (output data source) to drive what the user sees (connect your Map/List/Table widgets to the query result). You can learn more about the Query widget here - Query widget—ArcGIS Experience Builder | Documentation ... View more

Gotcha.  So question then - what type of map application will you be using?  Experience Builder?  Instant Apps?  Other? Related - straight line distance or drive time/distance? ... View more

I wonder if this workflow, Spatially Filter Feature Layers with Definition Queries, would work for you? ... View more

Question:  Are you using an Enterprise GDB or a File GDB?  For an Enterprise geodatabase you must be the data owner. To create or manage attribute rules, you must access the Attribute Rules view “from the geodatabase as the data owner.” If you connect as a user who is not the data owner, the Attribute Rules view is read-only. It’s also read-only from a web feature layer.  In addition, the Attribute Rules view is read-only when accessed with an ArcGIS Pro Basic license. ... View more

ArcGIS Pro 3.7.1 doesn’t have a setting to make the Calculate Field toolbar in an attribute table persist (stay enabled) or automatically reopen when you close and reopen the attribute table. It’s a per-table-view UI state, so you currently have to click Calculate again after reopening the table.  You may want to contribute an ArcGIS Pro Idea for this functionality if it's not already listed there. ... View more

Yes—this is a common symptom when ArcGIS Pro is run via Azure Virtual Desktop and the environment isn’t optimized for latency + GPU acceleration. Even with high bandwidth, ArcGIS Pro interactivity can feel “seconds behind” if round-trip latency (RTT) is high, if the session is CPU-rendering (no effective GPU), or if the VM/GPU is oversubscribed. Here are some steps you can try (based on Esri guidance): Check network latency first (not just bandwidth) Esri notes remote desktop user experience is very sensitive to latency and typically needs ≤ 200 ms RTT for responsive interaction. If users/hosts/storage are in different Azure regions, move them closer (same region/subnet where possible). Source: ArcGIS Pro on Microsoft Azure Cloud (3.7) Confirm ArcGIS Pro is actually using hardware acceleration (GPU) If hardware acceleration isn’t available, Pro falls back to software rendering (CPU), which often causes stutter/lag in virtual sessions. Source: Machine performance optimizations (3.7) Right-size the AVD session hosts (CPU/RAM/GPU) and reduce contention Esri advises a discrete GPU with at least 4 GB dedicated memory and notes undersized/shared CPU/RAM/GPU can cause lag and delayed response. Source: ArcGIS Pro on Microsoft Azure Cloud (3.7) Apply AVD-specific optimizations Esri calls out Use FSLogix for profiles and enable UDP short path; validate performance with the ArcGIS Pro Performance Assessment Tool (PAT). Source: ArcGIS Pro on Microsoft Azure Cloud—ArcGIS Pro (3.6) ... View more

I'm glad it worked out!  All the best! ... View more

Yes—teams do sometimes see different selection results across ArcGIS Pro versions, and there are a couple of common causes. 1) Make sure you’re comparing patched builds, not just “3.7 vs 3.5.4.” There is a confirmed defect where Select By Attributes can return incorrect/partial results for layers sourced from SQL Server: BUG-000177183 (found in Pro 3.5.1, fixed in 3.6 and 3.5.6). If any of your data is coming from SQL Server/enterprise geodatabase, this is worth reviewing: BUG-000177183 2) Check for “Invert Where Clause” being on in any of the Select tools in the model. That will make it look like “too many/wrong” features are selected. Related KB: Problem: Select Layer By Attribute returns the opposite records 3) If there are joins (especially one-to-many), “too many rows” can be expected. Selections are stored by ObjectID; a one-to-many join can make many table rows highlight for the same selected feature: BUG-000154798 ... View more

Try these checks—each one can cause Field Calculator / Calculate Field / Calculate Geometry Attributes to be disabled in ArcGIS Pro: Confirm the layer is editable In the Contents pane, switch to List By Editing and make sure the layer is checked (editable). Ref: Problem: The Calculate and Calculate Field options are disabled in ArcGIS Pro Make sure you’re calculating a supported field Calculate Geometry Attributes only enables for certain field types (short/long/double/float/big integer/text) and not for system fields (OBJECTID, Shape, Shape_Length, Shape_Area). Ref: Problem: The Calculate Geometry option is disabled in ArcGIS Pro Check the field isn’t set to Read Only Open the layer’s Fields view and uncheck Read Only for the target field, then Save. Ref: Problem: The Calculate Geometry option is disabled in ArcGIS Pro If it’s a feature service, don’t run Calculate Field in an edit session The geoprocessing Calculate Field tool can be blocked for feature services when you’re in an edit session / Enable Undo is on (unless using a supported branch-versioned workflow). Ref: 003307: Calculate Field is not supported against a feature service within an edit session Verify coordinate system isn’t “Unknown” If the map/dataset has an unknown coordinate system, calculate options may be disabled. Ref: Problem: The Calculate and Calculate Field options are disabled in ArcGIS Pro Repair geometry (for Calculate Geometry being disabled) Run Repair Geometry on the feature class. Ref: Problem: The Calculate Geometry option is disabled in ArcGIS Pro   ... View more