Latest Contributions by Matt-Goodman

Non-existent attributes stored as null are visually represented in the UX as <Null> (attribute table, attribute pane, etc.) There are multiple reasons I prefer displaying records with legitimately no attribute as blanks, instead of nulls, but the primary reason is for the ability to scan/read attribute interfaces more quickly: the blank cells are intuitively dismissed and prominence is given to the populated attribute cells. Consider programmatically using a more subtle mid-tone gray for the text font of these <Null> cells.  Concept sample image of null values in the last column on the right (this example happens to be while using 'dark mode'):   ... View more

Within the Damage Assessment Solution, the Damage Assessment Operations app includes the ability for the user ("assessment coordinator") to drag a marquee box over the points in order to generate a alpha-numeric grid that can be used to assign the points to users in the field. Instead of generating an arbitrary alpha-numeric grid overlay, could the assessment coordinator select USNG (MGRS) rectangles, at their choice of scale? ... View more

Currently, if a user attempts an edit (i.e. creating a new feature) that violates a constraint rule, the edit is rejected outright with an error explaining why it was rejected.  Instead, the dialog should warn the user of the constraint violation and allow them to either (a) continue editing the feature to correct the violation or (b) discard the edit.  Example 1: the user painstakingly digitizes a detailed lake shoreline perimeter based on aerial imagery, but when they finish the edit they receive an error message based on a constraint requiring that the lake name must not be <Null>. Instead of discarding the editor's sketch, the user has the opportunity to enter the lake name attribute and then again try to commit the edit to the database.   Example 2: some editing workflows mean that it's easiest for editors to simple copy/paste an existing feature (effectively just duplicating it) and then change one or two attributes. However, a constraint rule prohibiting certain duplicate attributes would not allow the user to paste (create) the feature; it would just discard the edit. Instead the user should be able to paste (create) the feature and then receive a warning that the certain attribute has violated the 'no duplicates' constraint, forcing them to change the attribute in the new feature before the edit is committed.   ... View more

I'm using ArcGIS Pro 2.9.2 I'm having trouble with my 'Locate' tool behaving badly. I have it configured with a couple of address locator services, as well as a few specific attribute fields in some of my map layers. This allows me to enter an address, a parcel ID, or lease ID into the search box and quickly find the property location on the map....it works fairly well, except.... Normally, the tool is supposed to list matches in a result list (even if just one single matching feature) below the search box and pan/flash the matching feature on the map. The results list allows users to see which map layer the attribute match was made within, and to right-click a record and choose from a context menu (select feature, zoom to feature, pan to feature, etc.). But my Locate tool never lists results anymore, when searching map layers, even when successful matches are made, and it doesn't flash the feature on the map (it does still pan to the feature). I'm not sure what has cause this change. I does still correctly list matches when entering an address, utilizing the address locator services.  I have tried several tests in new Pro projects and I can replicate the problem, but it seems to happen when numerous layers are configured in the Locate tool. Screenshot shows a successfully matched parcel ID search, but nothing listed in the results space: Is this a known issue? Bug? Are there known limitations that I'm not aware of? I've tested similar setups in other .aprx documents  ... View more