POST
|
@ArmstKP Happy to help on this one - but I would need a sample of $feature.last_values to replicate the issue to be provided for the Arcade field sample value. Can you either email it to me (pnasuti@esri.com), Esri Community private message a sample, or post here if it is data that can be seen by the public? Thanks!
... View more
10-03-2023
11:42 AM
|
0
|
1
|
530
|
POST
|
@ArmstKP Thanks for making this post, I would agree with @brudo 's first question. For a "string/text" type field in Velocity, the Arcade default sample value to be evaluated is the string "Pacific" which would not pass your expression and return your desired data type. The sample values (your JSON in the field) must be provided on the right side for the corresponding field. If you have done this and are still encountering issues, please reach out here or log a support case. Thanks!
... View more
09-26-2023
07:14 PM
|
0
|
0
|
648
|
POST
|
@Teresa_Blader Thanks for posting this question. ArcGIS Velocity feature layer feeds and sources are able to connect to feature layer items stored in or referenced in ArcGIS Online, or unsecured services via URL. In order to connect to secured feature layers, an item must be created in ArcGIS Online that references the service and stores credentials. I would suggest logging a support case to get assistance configuring ArcGIS Online items that store credentials to your services so that they can then be used by Velocity.
... View more
09-20-2023
05:12 AM
|
1
|
0
|
710
|
POST
|
@JeffSilberberg Thanks for the question. These options are not mutually exclusive. Publish a feature layer that keeps the latest observation for each Track ID In addition to the stream layer, Velocity also publishes a feature layer. For each unique value of the user-defined Track ID field, Velocity will keep the most recent observation. This is helpful for a map/application of "where is my moving entity right now?" Select a related feature layer to provide geometry when the stream layer is drawn in a map This is common for "stationary sensor" scenarios where location/geometry is fixed, but attribute values continue to change. It would be excessive to repeatedly send geometry data through with every sensor observation. So, a user would configure a feature layer that has entity locations. There would be a join field that matches values from the feed join field. You select your related feature layer in the feed interface then choose your join fields to match up the values. Esri web clients like the map viewers and more are smart enough to look at the stream layer definition, also load the data from the related feature layer, and render the features as attributes and geometry when the Velocity feed is just processing the attribute data updates. Related documentation: https://doc.arcgis.com/en/iot/disseminate-and-notify/stream-layer.htm
... View more
09-13-2023
08:05 AM
|
1
|
0
|
333
|
POST
|
Thanks @MattGeorge1 & @ArmstKP for your time today on separate calls. For the case reported by @MattGeorge1 this was identified as being caused by Editor tracking being disabled on your output online hosted feature layers around the time of the last ArcGIS Online update. Once this was re-enabled by you, the analytic resumed successful processing. For the case reported by @ArmstKP we are continuing to work together to isolate the cause of intermittent issues when Velocity is trying to write to the ArcGIS Online hosted feature layer REST API and receiving errors from ArcGIS Online. Investigation is ongoing and we will continue working directly to find a resolution. For our Velocity users, please continue to log a support case if any issues are encountered with the product. Additionally, from the real-time product team we encourage posts to ask questions or present issues to engage with the real-time product team here on the Esri Community space so that we can ensure your success. Please also feel welcome to direct message on Esri Community myself, @JeffEismanGIS @Yini_Song or other Esri representatives that you see active in the Velocity and GeoEvent space. Thanks!
... View more
08-18-2023
06:04 AM
|
2
|
0
|
974
|
POST
|
@ArmstKP When Velocity throws this log message, it is simply indicating that it is not getting a valid response from the destination layer. I can facilitate coordination with the ArcGIS Online team to see what additional information we can pull from these failure events. I will reach out via Esri Community direct message to provide my email address so that we could review together on a call and find a resolution.
... View more
08-14-2023
05:41 AM
|
0
|
0
|
394
|
POST
|
@ArmstKP If the issue is still present, can you please direct message me the item ID (available in the URL of the analytic or the ArcGIS Online item details URL)?
... View more
08-09-2023
01:27 PM
|
0
|
2
|
488
|
POST
|
@ArmstKP If any issues are persisting or any such issues are witnessed again, please reach out to Esri Support Services to create a support case for immediate assistance. In the meantime, I will reach out to the Velocity operations team to check your environment at this point in time.
... View more
08-09-2023
12:56 PM
|
0
|
0
|
506
|
POST
|
@ArmstKP The update today is for a Velocity system component. The upcoming release (Velocity 4.2 Patch 1) is schedule for next Wednesday (8/9/23) which addresses the table source issue and other items. Sorry for any confusion introduced regarding these two different updates.
... View more
08-02-2023
01:02 PM
|
1
|
0
|
487
|
POST
|
@ArmstKP Thanks for reporting - there were Velocity system upgrades today for which notifications went out that caused this behavior despite running items continuing to function. The issue should now be resolved and I am in communication with the support analyst assigned to the case that you opened. Apologies for the inconvenience.
... View more
08-02-2023
12:43 PM
|
0
|
0
|
804
|
POST
|
Absolutely! I put together some samples in Arcade (using the Calculate Field tool) to show what it would look like to grab values for specific fields. You would need to ensure to provide sample values for the fields for the Arcade expression builder to successfully evaluate an expression. Example 1: Acquire "fn_battery" value from "metadata" stringified JSON block // Sample workflow to acquire the "fn_battery" field from "metadata" escaped JSON object field
// Sample value for metadata field:
// {\"fn_th\":300,\"fn_light\":900,\"fn_mag\":0,\"fn_mag_int\":0,\"fn_acc_tap1\":0,\"fn_acc_tap2\":0,\"fn_acc_act\":0,\"fn_acc_min\":10,\"fn_bt\":0,\"fn_ext_t\":600,\"fn_battery\":7200,\"fn_dp\":300,\"cg_data_led\":1,\"wifi_mode\":1,\"no_net_fn\":0,\"time_zone\":-5}
// Step 1: Remove the backslashes from the stringified JSON
var slashReplace = Replace($feature.metadata,'\\','');
// Step 2: Convert the non-escaped "proper" JSON to a JSON dictionary, and grab the element of interest
FromJSON(slashReplace)['fn_battery']; Example 2: Acquire "field4 > value" value from "last_values" stringified JSON block // Sample workflow to acquire the "field4 > value" field from "last_values" escaped JSON object field
// Sample value for last_values field:
// {\"field4\":{\"value\":5,\"created_at\":\"2023-07-25T11:45:15Z\"},\"log\":{\"value\":507,\"created_at\":\"2023-07-24T17:03:02Z\"},\"field3\":{\"value\":226.4,\"created_at\":\"2023-07-25T12:55:25Z\"},\"field1\":{\"value\":21.5606,\"created_at\":\"2023-07-25T12:55:34Z\"},\"field2\":{\"value\":57.0855,\"created_at\":\"2023-07-25T12:55:34Z\"},\"field5\":{\"value\":-36,\"created_at\":\"2023-07-25T12:50:38Z\"},\"wifi\":{\"value\":\"ee:55:a8:0a:40:ef,-38;fe:55:a8:0a:40:ef,-38;ee:55:a8:0a:40:bf,-57;fe:55:a8:0a:40:bf,-58;02:18:4a:8c:49:62,-61\",\"created_at\":\"2023-07-24T17:07:49Z\"}}
// Step 1: Remove the backslashes from the stringified JSON
var slashReplace = Replace($feature.last_values,'\\','');
// Step 2: Convert the non-escaped "proper" JSON to a JSON dictionary, and grab the element of interest
FromJSON(slashReplace)['field4']['value']; I then confirmed the success of this expression to an output. Let me know if there are any other questions!
... View more
07-25-2023
12:26 PM
|
1
|
0
|
1411
|
POST
|
Thanks for the reply and for providing the full sample Taking a closer look, the fields metadata, status, last_values, vconfig, vpref are "stringified/escaped" JSON and not true JSON. This is the reason that the flattening is not able to break that apart as JSON when evaluating the complete element.
... View more
07-25-2023
06:39 AM
|
1
|
3
|
1202
|
POST
|
@ArmstKP For this case you would be clicking "Flatten" instead of "Flatten Arrays". Flatten arrays is only to flatten items contained in square brackets [/] as an array that actually contains data values. Flatten is to flatten {/} objects. Additionally, you may choose to specify an element such as "last_values" as a root node if you want to "drill down" into a JSON set to get a deeper element. If you have further questions feel free to log a support case or reach out to me over Esri Community direct message or on this thread. It would also help to be able to provide a full sample of your JSON - you could of course replace values with fake values of the same type.
... View more
07-25-2023
04:02 AM
|
0
|
5
|
1216
|
POST
|
@Jim_Wei Thank you for your post! The Feature Layer (existing) output was designed to require any Velocity layers that it writes to have data retention enabled. This includes feature layers that have "Keep only the latest feature for each Track ID" configured. Many real-time cases work with Track ID values that are not finite, but will continue to grow over time. Consider for example thunderstorm watch/warning polygons with a unique identifier for each polygon. The Track ID uniquely identifies each polygon and only keeps the latest value for each, but the number of thunderstorms will only continue to grow as time goes on. There are many other real-time cases where the values for unique ID/Track ID are not finite. For this reason, a data retention policy must be specified. Therefore, the workflow available is to recreate the layers with a data retention policy. You could use a big data analytic to populate the values from your "old" layer to this new layer as desired or reach out to Esri Support for assistance on this step as needed.
... View more
07-17-2023
04:28 AM
|
0
|
0
|
400
|
POST
|
Hi @JoshBillings thanks for the question. Posting a link from the documentation below and adding some thoughts on the end. How is ArcGIS Velocity different from ArcGIS GeoEvent Server or ArcGIS GeoAnalytics Server? ArcGIS Velocity differs from ArcGIS GeoEvent Server and ArcGIS GeoAnalytics Server in many ways, including product capabilities and business model. On a high level, GeoEvent Server and GeoAnalytics Server are on-premises software, while Velocity is a software-as-a-service (SaaS). Other differences include the following: Velocity has built-in high availability and disaster recovery. Velocity is deployed automatically, taking only 30-60 minutes to get access. Data stored by Velocity is stored in the cloud. Velocity is not directly extensible due to its nature as a SaaS. Velocity is geared toward operations and geospatial analysts as opposed to just GIS administrators. Velocity is offered via a subscription as opposed to a software license. Additionally: Velocity has a redesigned and updated user experience including analytic validation that will protect the user from misconfiguration Velocity offers big data analytics to process data sources that can contain anywhere from small amounts of data to hundreds of millions of features Velocity offers the use of easily configurable Arcade expressions in multiple tools including Calculate Fields, Map Fields, and other tools Let me know if you have any follow-up questions on the differences
... View more
07-17-2023
04:23 AM
|
3
|
0
|
1435
|
Title | Kudos | Posted |
---|---|---|
1 | 08-20-2024 06:07 AM | |
1 | 07-31-2024 11:51 AM | |
1 | 07-31-2024 11:58 AM | |
1 | 07-08-2024 05:36 AM | |
1 | 03-18-2024 04:10 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|