POST
|
In case anyone else is having this same issue, I believe I found a solution to this problem by using the "Control Event Volume" tool in a separate Real Time Analytic and ingesting the output from the RTA into a the main RTA. See below for the generic workflow I have employed for my own project: Real Time Analytic (RTA) "Get First Value": Input --> Live Feed (AVL data from snow plows). Control Event Volume --> set to as long as RTA is running and "Max Events Per Interval" equal to 1 Output --> Feature Layer "First Value" Real Time Analytic (RTA) "Ingest First Value": Input --> Live feed (AVL Data from snow plows) & Feature Layer "First Value" Join Live feed to "First Value" based on TrackID Summarize joined "First Value" fields by "MAX" value Calculate new running total fields by using "Material Value" - "First Value" = "Material Total" Output --> Feature Layer "Tracks"
... View more
01-17-2024
08:54 AM
|
0
|
0
|
234
|
POST
|
Hi @DanielFox1, Thanks for this information. Relating to the "Parse Dates" toggle, is there a way to parse on weeks? I have an end user that is trying to visualize data that is recorded on a weekly basis and the format of the date is Year-Week.
... View more
12-15-2023
09:12 AM
|
0
|
0
|
229
|
POST
|
Yes, I would agree that 7 days may be a little extreme. I initially set it for 7 days as more of a fail safe to always capture the starting record regardless of how long the event typically lasts. I may end up changing it back to may be 1-2 days to see if that changes anything. Regarding the reset of values, I agree that it may not be the "Detect Incidents" tool thats causing the resetting of the starting values. It may be how I have the subsequent Winter Fleet Tracking RTA set up to ingest the "First Record" stream or feature layer as this is where the summation calculation is completed and where I noticed the "resetting" of the zero value. It was unclear to me what type of input I should use in the Winter Fleet Tracking RTA for the "First Record" data (stream layer or feature layer). Do you have any suggestions? My main goal in this post was to try and find if any other users were having similar issues with their data streams from their AVL systems not being "zeroed" out at the beginning of each "event" and if any other users had set up similar workflows to record the "First Record".
... View more
12-06-2023
11:36 AM
|
0
|
0
|
398
|
POST
|
Jeff, Thanks for the quick response. I forgot to mention in my original post, but the "Target Time Window" of 10 minutes is actually an adjustment I made after the first snow event / live test event. The original "Target Time Window" was set at 7 days in order for the auto close/end condition wouldn't be met until after the event ended. Even with the much longer "Target Time Window", I found that values were be reset after what seemed to be a few hours. Unfortunately, I also think having a long "Target Time Window" may affect the performance of the RTA due to the Stateful configuration settings and too many features being stored in memory, although this is only an assumption, but I am not positive on this aspect. According to the ESRI documentation, (https://doc.arcgis.com/en/iot/analyze/perform-real-time-analysis.htm), the "Target Time Window" does effect how many features are stored in memory and used in the comparison process, but I couldn't find any information about when the features are purged if they get set back to their original state (in the case of Detect Incidents, if this would mean the first feature following a purge would have a status of "Started").
... View more
12-06-2023
09:31 AM
|
0
|
0
|
446
|
POST
|
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
12-06-2023
09:01 AM
|
0
|
6
|
502
|
POST
|
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
12-04-2023
12:31 PM
|
0
|
0
|
133
|
POST
|
Thank you for this input. With the change to the new naming pattern for the Web Adaptors, what will happen to the content that is already in Portal site from the existing federated server? As it stands now, those services use the "arcgis" web adaptor name (EX: https://gis.domain.org/arcgis/rest/services/pointsLayer ). Will I need to un-federate & re-federate my AGS with Portal? Will I need to remove and re-add these layers?
... View more
07-19-2023
10:10 AM
|
0
|
1
|
677
|
POST
|
Thank you for the clarification on the order of upgrading each component. One question I had regarding the naming of each web adaptor, currently in the existing Enterprise site, the single web adaptor uses the name "arcgis" (the default name). If I were to change the web adaptor for both Portal and Server to something other than "arcgis" as you suggested, would this not cause issues with the existing services in the deployment?
... View more
07-19-2023
09:50 AM
|
0
|
3
|
692
|
POST
|
Looking to get some guidance on upgrading an ArcGIS Enterprise site from 10.7.1 to 10.9.1 when the existing site only uses a single web adaptor. As it stands the Portal and Server site both share the same web adaptor (arcgis) and as dictated by ESRI documentation, this isn't supported anymore. My thought was to follow the below workflow to complete this upgrade, but was looking for any additional guidance or advice. 1. Unregister existing web adaptor with ArcGIS Server 2. Upgrade Portal 3. Uninstall/Re-install web adaptor for Portal --> use "arcgis" name 4. Upgrade ArcGIS Server (AGS) 5. Install web adaptor for AGS --> use "server" name 6. Upgrade datastore
... View more
07-19-2023
09:33 AM
|
0
|
12
|
825
|
POST
|
Mackenzie, Unfortunately no, this is not configuration/setting option I am looking for. This setting is for features selected in the map using the "Select" tool that is available in the map. The configuration/setting I am looking for is to change the color of the selected feature from the "Query" widget. As it stands now, the default color/fill of the selected feature from the "Query" widget results pane is yellow and the developer does not have any control on color, fill, or transparency of the selected feature.
... View more
12-12-2022
06:14 AM
|
2
|
0
|
647
|
POST
|
Yes, thank you. I just open the EB application the other day and noticed this feature had been implemented.
... View more
12-12-2022
06:06 AM
|
0
|
0
|
372
|
POST
|
I am looking to see if it is possible to change the "Highlight" color for the selected feature in the map. Currently it is a semi-transparent yellow color and we have a client that is looking to use a different or custom color. So far looking through any and all documentation as well as the widget itself within EB, I was unable to find any option to change this color.
... View more
12-02-2022
12:49 PM
|
1
|
3
|
718
|
POST
|
Hello, I am in the middle of developing a Nearby App using the Instant App builder in ArcGIS Online. While developing this app, I noticed that when the "Header" option under "App Details" was disabled, the scrolling functionality of returned results pane was disabled. Only once the "Header" option was re-enabled was the scrolling functionality of the results pane re-enabled as well. Is this an intended functionality or is this a bug? See the screenshots for the example functionality.
... View more
08-09-2022
06:39 AM
|
0
|
1
|
529
|
POST
|
I am currently in the middle of developing an Experience Builder application for a client in which the application utilizes the built in Query Widget. I am looking for any guidance on how to configure the results pane of the Query Widget to open/expand all returned results by default. Looking through the existing settings in Experience Builder, I have been unable to find a setting or switch specific to this option. I have also had no luck finding any information on ESRI support documentation or through Google.
... View more
07-13-2022
06:58 AM
|
0
|
3
|
451
|
Title | Kudos | Posted |
---|---|---|
2 | 12-12-2022 06:14 AM | |
1 | 12-02-2022 12:49 PM | |
1 | 05-05-2022 08:41 AM | |
1 | 08-10-2021 11:44 AM | |
1 | 08-10-2021 11:41 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|