Latest Contributions by PeterNasuti

@AmberBard Thanks for posting and I agree with @JeffSilberberg above. Most APIs have an endpoint that can return multiple devices with a single call, either as a GET or a POST. Other APIs allow comma separation for a parameter such as https://yourVendorURL.com/data?devices=1,2,3,4,5  If you can provide documentation from this vendor/provider I'd be happy to skim through to see if any compatible options stand out to me. ... View more

Hi @JeffSilberberg the following tools do and do not have a geometry configuration requirement. I'll add an item for us on the product side to update documentation to make it more clear for each tool when geometry is required. For any circumstances where you see an analytic crash as opposed to a feature being skipped for processing with a corresponding and explanatory log message thrown, please log a support bug so that Velocity can continue to be enhanced for all these conditions.  Require geometry: Create Range Fans Add XYZ Values Calculate Distance Calculate Motion Statistics Create Buffers Feature to Point Filter by Geometry Project Snap to network Do not require geometry: Calculate Fields Control Event Volume Delay and Reorder Tracks Detect Incidents (assuming no spatial condition configured) Detect Gaps Filter by Expression Filter by Time Range Join Fields (assuming no spatial join configured) Map Fields Merge Multi-merge Route by Expressions Select Fields ... View more

@JeffSilberberg The Velocity UI uses that call to collect feed/analytic item status of all items of that type in the Velocity org. Then it does an ArcGIS Online content search "/sharing/rest/search" with structure such as:  https://arcgis.com/sharing/rest/search?f=json&q=(type: "Real Time Analytic") AND (orgid: <yourOrgID>)&num=100&start=0&sortField=title&sortOrder=descending&token=<yourToken> and joins the owner name from matching the item ID.  ... View more

@JeffSilberberg Appending ?view=admin to the status requests AND providing an administrative authorization header token will bring back status of all items, not just items your user owns. This request mechanism is how the "Organization content" pages are populated. I tested the below in postman and confirmed success. /iot/feed/status /iot/feed/status?view=admin /iot/analytics/realtime/status /iot/analytics/realtime/status?view=admin ... View more

@wchou_esrica Yes - try this such as  https://yourSite.com/yourURL/$feed.FeedScheduledStartTime OR https://yourSite.com/yourURL/$feed.FeedLastScheduledStartTime And also specify the Global variables date formatting string: I am seeing success with this in testing where the value ends up being substituted for the request. ... View more

Hi @wchou_esrica I just did some testing on this - While not documented, Velocity HTTP Poller feed type does replace timestamp values in the URL when using the feed global variables. However, for the URL feed global variables, the date formatting string is not honored and all dates will be sent as an epoch millisecond. I'll check with a developer to see if this is something we can enhance for. In the meantime, does your API support epoch MS time reference in the URL? Related documentation, see section under feed global variables: https://doc.arcgis.com/en/velocity/ingest/website-poll-feed.htm ... View more

Hi @DrewDowling This is in the longer term product plan to offer "rate drop or failure" notifications as part of Velocity feeds and analytics to notify users if their upstream systems fail to send data or if there is any run status change (like a feed or analytic in a failure state). ... View more

@SimonGIS @SeanOBriain As an update on this thread, for the Velocity 6.2 release (late June 2025) we are adding a subscription message element to the WebSocket feed type. We are also adding a parameter "ignore first message received" for cases where the API returns a subscription confirmation message before data flows. However, I have seen with this WebSocket AIS stream provider independent of Velocity that it sends disconnect messages every two minutes or so (even testing with postman). Velocity automatically reestablishes the connection but thought you should be aware to investigate the disconnects further with them. ... View more

Hi @AndrewMurdoch1 The ArcGIS GeoEvent Server and ArcGIS Velocity products do not currently offer compression on stream layers. We will explore parameterizing this for a future release. Is there currently a rate or load that you are unable to keep up with that pushed you towards investigating compression with this Stream layer web socket? ... View more

We added custom headers support for WebSocket feed type a few releases back. Mostly, I have seen APIs that use API key passed in a custom header as the authentication mechanism for WebSocket. Does this meet your use case? Something with multi-step custom authentication responses is less commonly witnessed and unlikely to be implemented in ArcGIS Velocity in the near-term. ... View more

@SimonGIS Yes, @JeffSilberberg is correct that this is not currently available out-of-the-box in Velocity within real-time analytics. We will continue to evaluate it for future product enhancement. Feel free to submit through the Ideas page or an Esri Support enhancement request. ... View more

 Hi @SimonGIS thanks for the additional details - send me an email at pnasuti@esri.com and we will get a product engineer assigned to help investigate what you have reported. Please also log a support ticket for tracking purposes. ... View more

Hi @SimonGIS thanks for posting! You will need to specify on the Configure HTTP Poller > Confirm Schema page: a root node of results This tells Velocity to only process data and records from within the "results" array check the box of Flatten This reduces the "{"lon": 150.82906,"lat": -34.06914}" string down to location_lon and location_lat field Additional documentation on flattening and root nodes available here Then, click next and proceed to Identify Key Fields and specify the geometry fields: The above is the expected way to configure geometry from this source provided. Regarding your query about Arcade, Arcade is evaluating that value of "{"lon":150.81224,"lat":-34.01287}" as a string rather than a dictionary. Therefore when you call "$feature.location[0]" it is calling for the 0 index value of the string which is the { character that starts the string. To convert a string to a dictionary in Arcade use the dictionary function. ... View more

@Teresa_Blader Hi Teresa, please log an Esri Support case whenever that message is witnessed so we can address this. Depending on what is found in troubleshooting, the product team may get involved to help provide a resolution. ... View more