Latest Contributions by PeterNasuti

@ArmstKP I have traced down the cause of this to a few things The "95." on line 13 should be 95 or 95.0 Taking a square root of a negative number generating an imaginary number on line 13 is also causing failure. To address this I wrapped the calculation in another ABS() function before the SQRT() function I changed the logic pattern to IIf() functions that update the "HI" variable and also handle the false case. I often recommend this IIf() function in Arcade configurations of Velocity var dictempF = $feature.last_values var dicvartempF = Dictionary(dictempF) var tempF = Round((dicvartempF.field1.value * 9/5) + 32,1) var dichumidity = $feature.last_values var dicvarhumidity = Dictionary(dichumidity) var humidity = Round((dicvarhumidity.field2.value),1) var T = tempF var RH = humidity var HI = -42.379 + 2.04901523*T + 10.14333127*RH - .22475541*T*RH - .00683783*T*T - .05481717*RH*RH + .00122874*T*T*RH + .00085282*T*RH*RH - .00000199*T*T*RH*RH; HI = IIf((RH < 13 && T > 80 && T < 112), HI - (((13-RH)/4)*SQRT(ABS((17-ABS(T-95))/17))), HI); HI = IIf((RH > 85 && T > 80 && T < 87), HI + (((RH-85)/10) * ((87-T)/5)), HI); HI = IIf((HI < 80), (0.5 * (T + 61.0 + ((T-68.0)*1.2) + (RH*0.094))), HI); return Round(HI, 1); Let me know if this addresses the validation error on your side as well and if there is anything else that comes up. Thanks, Peter Nasuti ... View more

@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

@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

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