Latest Contributions by KevinPiraino2

I currently have published (non-hosted) feature service that connects to my enterprise geodatabase that is used to manage tree inventory data published using ArcGIS Server 10.9.1 and the feature service being added to ArcGIS Online. This feature service has three layers: 1 point feature class, 1 non-spatial related table, and 1 attachments table. The related table is a 1 to many relationship where 1 point (tree) can have many records (tree maintenance records). I have instituted an attribute rule where the latest (or last added) maintenance record's "condition" field is used to attribute a "condition" field in the parent point feature class.  This attribute rule works fine in ArcGIS Pro and the results from the attribute rule can be seen nearly automatically. The issue I am running into is when trying to test the workflow in ArcGIS Field Maps of adding a point --> adding maintenance record (or just adding a maintenance record to an existing point) and the maintenance record's attributes not being saved / sent / submitted on the first try. Only after the second attempt is the maintenance record's attributes being saved / sent / submitted and thus the attribute rule being executed.  It's unclear to me if its an attribute rule issue, a feature service issue, a data issue, or just a general bug / issue with my version of Field Maps.  ... View more

Looking to get some insight into how attribute rules (specifically calculations) are effected by the use of python. How are attribute rules treated when new records are added to a table (or feature class) using python? We have a fair number of process that truncate and append records from one table to another on a nightly basis and I was wondering if an attribute rule (calculation) would be adhered to when inserting records using the append GP tool through python? Would this be the case to have the attribute rule only set for bulk execution at a later time (sometime after the python script runs)? ... View more

Our organization is currently utilizing Velocity to deploy the Winter Weather Operations solution. One of our Transportation manager's goals for using this solution is to more accurately track material usage across an event and across a season. While reviewing our AVL data return, we found that all of the material values returned by the AVL system are summed values from when the device was first field deployed (day 1) making these raw material values not useful in their current form.  I currently am attempting to employ a workflow that would capture the first record for a track when an event starts and storing this information in a separate stream or feature layer. This "First Record" stream or feature layer would then be used as the "zero" or starting value for each track in which to calculate the running total of material use across an event.  I have so far attempted two separate workflows to capture this "First Record" data. Those two workflows can be seen in the attached screenshots.  Use the "Detect Incidents" tool in a real time analytic (RTA) to determine when a vehicle has entered/exited a pre-defined static "Operational Boundary" polygon (see screenshot for configuration of "Detect Incidents" tool). Then filter the records based on the returned "Incident Status" value using a where clause of "Incident Status == 'Started'". Store filtered records in a separate stream or feature layer. Use the "TrackFieldWindow" Arcade function to find the first record in an RTA. Use the calculate field tool to build a new field that uses the "TrackFieldWindow" Arcade function to return a boolean (true/false) value (see screenshot for this Arcade expression). Filter subsequent records based on this boolean field, only returning the records that contain a True value for this field.  So far workflow 1 seems the most promising and works to some degree when testing during non-events, but during an actual event with many more active vehicles I am finding that while values are being calculated, they are not always accurate over long durations. I am finding that the "First Record" is being reset after a certain time frame. I am not sure if this is an issue with how I have the output Stream or Feature Layer configured or if it may be an issue with the Stateful configuration not able to handle that many records over that duration of time. I have had less time to test Workflow 2 and am less confident in it's ability to capture the "First Record", but wanted to try something different in case workflow 1 wouldn't function. I am looking for any advice or suggestions on how to accomplish the capture of the "First Record" values as well as any additional suggestions on how to best accomplish calculating the running material total values for an event/season using the "First Record" values as the zero value. ... View more

We are currently working in Parcel Fabric in ArcGIS Pro and we’re looking to use a parcel hook symbol.  We are looking for a simple 2 point line that will have a hook on one end.  The symbology should be line based as that is easier for us to work with, however, if there is a point based solution; that would work well. The symbol does need to be easily adjustable in terms of line thickness; we are looking for a minimum of a small, medium and large size.  At this point, we do not have an ideal line thickness, that will be determined during testing. I have been able to create a style file in ArcMap with limited success.  In ArcMap, I used the <-- -->  predefined arrow line, then gave the line no color, no fill.  I manipulated the arrowhead to use an alternate symbol, then added multiple levels with symbology, adjusting the X,Y to create a hook symbol. It works when imported to Pro, but it is crude.  We’re looking for any tips or tricks to create such a symbol for use in ArcGIS Pro. ... View more