|
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
|
2434
|
|
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
|
2448
|
|
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
|
926
|
|
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
|
3358
|
|
POST
|
@JeffSilberberg Yes, there is a realtime module for the ArcGIS API for Python with start() and stop() methods for a real-time analytic https://developers.arcgis.com/python/api-reference/arcgis.realtime.html#realtimeanalytics
... View more
07-03-2023
07:16 AM
|
0
|
0
|
1276
|
|
POST
|
Thanks for posting this question, this is something we continue to consider from the product side. As you have found, when designing a real-time analytic, for some data inputs you need to choose between configuring this as a feed or as a source. Sources only go fetch the source data when the real-time analytic is started or restarted. Therefore, if your real-time analytic is started, and sits there running for weeks, it is evaluating against data that is hours to days to weeks old. This is by design, and expected to be used for something relatively static. Think zip codes, census block polygons, and such. Whereas with feeds, you can configure a polling interval for polling type feeds such as feature layer feed or HTTP poller feeds. This can be as frequent as every 10 seconds, to much less frequent such as every 1 day or every 12 hours. However, you advised this did not work. Please feel free to log a support ticket for assistance. But also be aware, if you start the real-time analytic referencing these two feeds, data will not be available from this "every 23 hour" join feed until it hits its polling interval. What quite possibly is happening is that you started your real-time analytic but the secondary feed has not yet pushed any data into the real-time analytic for evaluation as the polling interval has not yet been encountered. Instead of refreshing that feature layer feed every 23 hours, I would suggest setting something between every 30min - every 2 hours. For a longer term product perspective, we are investigating enhancement possibility to enable real-time analytic source data refresh without having to restart the analytic.
... View more
07-03-2023
04:54 AM
|
1
|
0
|
1281
|
|
POST
|
This issue should now be resolved, thanks for raising it!
... View more
06-29-2023
10:04 AM
|
0
|
2
|
1573
|
|
POST
|
@ArmstKP Thanks for reporting this, the Velocity operations team is actively investigating. Can you please log a support case for tracking purpose?
... View more
06-29-2023
07:03 AM
|
1
|
4
|
1605
|
|
BLOG
|
Why add administrative contacts? As a cloud-native add-on capability for ArcGIS Online, ArcGIS Velocity enables users to build feeds and analytics to ingest, analyze, and process real-time data. In addition to these powerful features, ArcGIS Velocity also leverages the ArcGIS Online administrative contacts functionality. This enables users to notify organization administrators about a number of ArcGIS Velocity scenarios including: Scheduled updates including the scheduled upgrade time window Upgrade or maintenance completion Compute and storage capacity related notifications Important notifications requiring user or administrator attention. For example, feed or analytic inability to reach an item dependency such as a source feature layer. By expanding notifications beyond a single person, ArcGIS Velocity's use of administrative contacts provides a seamless method to keep key stakeholders informed about essential information. Through this alerting of relevant contacts, organizations can mitigate downtime and ensure smooth operation of their real-time and big data analysis flows. How to add administrative contacts: To add administrative contacts to receive ArcGIS Velocity notifications, first log in to ArcGIS Online as an organization administrator Click the Organization tab Select Settings Review the General tab Find the section Administrative contacts Choose and add the administrator or administrators who will be listed as points of contact The specified administrators and their email addresses are then listed as points of contact in the automatic email notifications sent to organization members when the Velocity organization. In addition to these specified administrators, relevant users are independently notified for scenarios such as item or authentication alerts that trigger notifications. Below you can see an example of an ArcGIS Velocity upgrade notification that is sent out to notify prior to an upgrade window. By adding organization administrators to the administrative contacts element, these additional administrators will also receive these notifications among others. Interested in learning more? Check out the other ArcGIS Velocity blogs and read more about relevant administrator information in the product documentation. You can also learn how to get started with ArcGIS Velocity using this Learn ArcGIS lesson. Please reach out and let us know if you have any questions about any capabilities in ArcGIS Velocity.
... View more
06-27-2023
09:22 AM
|
1
|
3
|
1019
|
|
POST
|
Hello @ArmstKP! there were lots of user interface changes with our recent release that went out last week. Please clear your browser cache and reopen Velocity in a new tab. If the issue persists please log an Esri Support Services case for the reported issue for assistance and a workaround if needed. Thanks!
... View more
06-20-2023
05:25 AM
|
2
|
0
|
1748
|
|
POST
|
@Jim_Wei If you ever witness a feed or analytic go down and stop functioning as expected, please make sure to log an Esri Support Services ticket so the root cause can be addressed by the product team. A combination of Map Fields to designate the relevant Track ID field with Detect Gaps > Control Event Volume can be used to limit the number of emails sent in the event of features coming through that pipeline. The ArcGIS Velocity product team is committed to continuing to enhance product level notifications and alerts and we will take this request under consideration. In the meantime, a feed configured on your output feature layer with Detect Gaps > Control Event Volume in a separate real-time analytic would achieve the core goal of automatically notifying if features are not flowing as desired and be contained in separate elements from your processing analytic.
... View more
05-03-2023
05:49 AM
|
1
|
0
|
2157
|
|
POST
|
@SimonGIS Thanks for your post and for raising this need! Currently the ArcGIS Velocity WebSocket feed type does not support authentication. I have entered an item on our side for the Velocity team to research expanding this functionality to offer a user-configurable JSON subscription message as well as exploring other authentication options to expose for this feed type.
... View more
04-27-2023
09:33 AM
|
4
|
0
|
3188
|
|
IDEA
|
@WilliamKeever As an update, I have been in communication with Verizon about this enhancement/idea request. While the Verizon web application currently supports groups, there is enhancement still needed on the Verizon side to make the group field available through the underlying communication component. Because the ArcGIS Velocity Verizon feed type depends on this underlying communication component, we cannot add this feature until it is present on the Verizon side. We will remain in contact with Verizon and explore adding this functionality when the requisite enhancement is made by Verizon.
... View more
04-14-2023
11:10 AM
|
0
|
0
|
2715
|
|
IDEA
|
@AW_Grove From the Velocity side, ArcGIS Velocity does not use credits and is instead operates on a subscription model. ArcGIS Velocity can write to multiple output feature layer types: ArcGIS Velocity layers - do not use credits ArcGIS Online hosted feature layers - there is a credit consumption associated with these type of layers, see this documentation for more details on that ArcGIS Enterprise layers - do not use credits From the Velocity side, we will be investigating the pathway to add the group field for Verizon Connect Reveal, thanks for adding this idea!
... View more
04-05-2023
06:39 AM
|
0
|
0
|
2766
|
|
POST
|
@ArmstKP Thank you for raising this issue with us, we are actively investigating. Can you please log an Esri Support case for tracking purposes? This will let Velocity product and operations team know which organization you are working with to facilitate resolution.
... View more
03-01-2023
06:41 AM
|
1
|
1
|
795
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-04-2025 05:55 AM | |
| 2 | 04-25-2025 11:39 AM | |
| 1 | 04-08-2025 05:23 AM | |
| 1 | 01-28-2025 06:21 AM | |
| 1 | 01-24-2025 02:34 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|