Latest Contributions by Robert_LeClair

No—ArcGIS Pro does not currently provide a built-in way to limit who can use Mark As Exception in the Error Inspector pane (for topology errors or attribute rule errors) based on a role (admin/supervisor vs editor). What Mark As Exception does is update the stored error feature’s isException value (True/1), and Clear Exception sets it back to False/0: Manage attribute rule errors—ArcGIS Pro. Practical workaround: If you're working with an Enterprise geodatabase, control it with data permissions, since marking an exception is an edit to the underlying error records. If editors only have read access to the error datasets/tables, they can review errors but won’t be able to mark/clear exceptions. ... View more

Yes but.... Normally, In ArcGIS Pro > Symbology (Unique Values) you can manually add a class for a value that doesn’t currently occur in the data. Open the layer Symbology pane and set Primary symbology = Unique Values (with your Arcade expression in Field 1). On the Classes tab, click the Green Plus sign. Click the the Options dropdown, add new value.  And from here it throws an error - "requested operation could not be completed"...normally you'd go to Step 4 and be done... Click Add new value and type the value you want to symbolize (in your case, add the missing returned value, e.g. 6, and set the label to Planned). Assign the symbol you want for that class. But here's what I learned...there's a BUG.  "BUG-000161636 : Add unlisted value options triggers an error message 'Requested operation could not be completed' while adding a new value, under the symbol class using custom arcade expression." Not sure when it will be fixed as it's listed "under consideration." ... View more

There’s no current ArcGIS Online incident reported, so this is unlikely to be an AGO outage. When one sublayer in a hosted feature layer consistently fails spatial selection in both ArcGIS Pro (Select By Location) and ArcGIS Online (Find by Attributes and Location)—but works after exporting to a file geodatabase—that strongly suggests the hosted sublayer contains problem geometries (for example null/empty geometry, self-intersections, bad ring ordering, unclosed rings) and/or true curve geometry that’s not being handled as expected server-side. Try these steps: Export just the failing polygon sublayer to a file geodatabase (you’ve already proven this helps). Run Check Geometry on the exported feature class to identify bad features. Run Repair Geometry on that exported feature class (review the “Delete features with null geometry” option). If curves are involved (CAD/freehand/elliptical/Bezier), densify/convert curves before republishing. (Curves can cause issues in hosted workflows.) Overwrite/republish the hosted feature layer (or publish a clean copy) using the repaired data, then re-test the spatial selection in Pro and AGO. Retest workflow. ... View more

If it’s the same map opened in two views (for example, View 1 and View 2 of Map) - yes—symbology is shared, so a change in one view updates the other automatically. If it’s the same data/layer added to two different maps (for example, Map A and Map B) - no—there’s no built-in “synchronize symbology across maps” setting. Each map has its own layer properties. Alternatives to keep them consistent across different maps Copy/Paste layer properties (Symbology, Labeling, etc.) between layers, even between maps: Copy and paste properties between layers or tables—ArcGIS Pro Use Apply Symbology From Layer / import symbology: Import symbology from another layer—ArcGIS Pro ... View more

ArcGIS Pro doesn’t have an application setting to prevent a layout from opening another view/tab when you double-click it in the Catalog pane. A layout can have multiple open views, so each open action can create another tab. Here are some options you can use instead: Switch to the already-open layout tab rather than reopening Close duplicates quickly (right-click a layout tab > Close, or close the tab group). ... View more

I wish I had a good answer for you, but I do not.  The only "why" I found in support cases are "Map Notes are intended for visualization and annotation purposes only and are not recommended for data that will be shared or used in Web Maps." ... View more

You bet - all the best! ... View more

With regards to a Map Notes layer not being shareable as a web layer - correct - this is not possible.  According to the Help documentation - "Map notes are not supported when sharing as a web scene or web layer. Use the Copy Features tool to copy a map notes layer to a new feature class." 24078: Layer's data source is not supported: <value> | ArcGIS Pro documentation ... View more

Question:  Is the map view closed?  If so, go to the Catalog Pane, on the Project tab at the top of the Catalog Pane, expands Maps, and you "should" see your maps in your Project file.  If you don't see the Catalog Pane, click the View tab at the top and in the Windows group, click Catalog Pane. ... View more

In the Copy and paste properties between layers or tables Help documention here - Copy and paste properties between layers or tables | ArcGIS Pro documentation - there is a Paste Properties commend where you can paste only the display filters to the other layer.  Would this work? ... View more

In full transparency, I did a somewhat deep dive using the Esri Support AI Chatbot for this question as it falls outside of my expertise. Testing of suggested workflows below are strongly recommended: <CLIP> Let me know if this works (or does not work) and I'll examine support cases for you. Large min/max EVI values in ArcGIS Pro with Landsat 8/9 **Collection 2 Level-2 SR** are usually caused by one (or more) of these: 1) **Computing EVI on unscaled integer DN values (or not forcing float math)** L2 SR bands are stored as integers; EVI should be computed on **scaled reflectance as floating point**: **SR = DN * 0.0000275 + (-0.2)** 2) **Including invalid pixels (clouds/shadows/water-fill) or SR values outside a valid range (often negatives)** Those pixels can blow up the EVI denominator and produce extreme outputs. Esri recommends masking out unwanted pixels using the QA band and excluding out-of-range SR values because they can cause band indices to be wrong. Reference workflow: [Clean up your Landsat imagery: removing cloud and cloud shadow](https://www.esri.com/arcgis-blog/products/arcgis-pro/imagery/clean-up-your-landsat-imagery-removing-cloud-and-cloud-shadow) 3) **Wrong band mapping/order** EVI expects **NIR, Red, Blue**. For Landsat 8/9 that is **B5 (NIR), B4 (Red), B2 (Blue)**. EVI formula reference: [Band Arithmetic function—ArcGIS Pro](https://pro.arcgis.com/en/pro-app/3.4/help/analysis/raster-functions/band-arithmetic-function.htm) ## How to obtain valid EVI Try this approach: - Mask clouds/shadows (and other unwanted categories) using the **QA** product (set unwanted to NoData). - Optionally mask SR DN outside a reasonable range (commonly **0–10000** in DN space) before scaling (per Esri’s guidance in the blog above). - Scale B2/B4/B5 to float reflectance (DN * 0.0000275 - 0.2). - Compute EVI: **2.5 * (NIR - Red) / (NIR + 6*Red - 7.5*Blue + 1)** <END CLIP> ... View more

There was a BUG-000135326 for ArcGIS Pro that was non-reproducible in November 2020 seen at 2.6.3 with a workaround of "Adding the geocoding service URL as a geocoding service in the ArcGIS Online organization's settings ensures the geocoding works with no issue. The issue only seems to occur when adding it as an item in ArcGIS Online." Further, there is an Analyzer message of 00339 that lists items/solutions that may be relevant to version compatibility - 00339: Locator was built with roles or capabilities not compatible for sharing to this version of ArcGIS Server | ArcGIS Pro documentation ... View more