Latest Contributions by PeterNasuti

Thanks for submitting this idea, we will consider this in future product direction planning ... View more

@brudo We had a call with @JeffEismanGIS and @ArmstKP to implement the workaround for the frontend limitation at the current 3.3 release. As soon as 4.1 goes live in late February this limitation will no longer be present. You are correct that in real-time analytics positive values are not valid for backend evaluation, but they are valid for big data analytics. At the current release we do not have a way to insert that nuance to the Arcade expression evaluation but we are considering validation inspection options for future releases. Expect more examples, conference demos, and community videos from the real-time time moving forward on the use of track functions highlighting use cases and configurations. In the meantime feel free to log a support case or direct message a Velocity team member for assistance with the workaround for this negative value specification at the current release. ... View more

@ArmstKP @brudo At the 3.3 Velocity release (current) the Arcade expression evaluation code is not capable of evaluating negative index values for Track functions. This shortcoming has already been fixed for our 4.1 release that will go live in production late February.  The workaround is to build your expression with positive values such as [1,2], and then to use the Velocity API to modify the value set in the analytic configuration for that expression. For assistance with that process please either create an Esri Support case or reach out to myself or @JeffEismanGIS directly via Esri community direct message to exchange contact information and schedule a call. As soon as our next release goes live in February, this extra step will no longer be required. As an update to this, see @JeffEismanGIS 's edited comment above and @brudo 's suggestion We can use an "if" function determination to assess the array length an if less than 1, we can return a false boolean type and not require any API level modifications prior to the Feb 2023 Velocity update. // Get the prior observation value for the field using TrackFieldWindow var priorValueArray = TrackFieldWindow('driverName', -1, 0)[0]; // Get the current feature observation value for the currentValue field var currentValue = $feature.driverName; // Handle the case where the first value does not have a prior feature // If there is a prior value, determine if the value changed if(count(priorValueArray) < 1){ return false; } else { return IIf(priorValueArray[0] != currentValue, true, false); }   ... View more

@Meyer @brudo As an update, we have implemented this and it will go live with the 4.1 late February 2023 update of ArcGIS Velocity Our Select Fields tool has been enhanced to offer an option to remove geometry from features in a real-time or big data analytic. ... View more

@Teresa_Blader Thanks so much for your suggestion! This is something we are continuing to consider for the addition of future real-time and big data tools. Here are the related tools that are already offered in the product: Calculate Density calculate a magnitude-per-unit area from point features that fall within a neighborhood around each cell  https://doc.arcgis.com/en/iot/analyze/calculate-density.htm Find Hot Spots  identify statistically significant hot spots and cold spots in the spatial pattern of the data using the Getis-Ord Gi* statistic https://doc.arcgis.com/en/iot/analyze/find-hot-spots.htm Generalized Linear Regression Perform Generalized Linear Regression (GLR) to generate predictions or to model a dependent variable in terms of its relationship to a set of explanatory variables. This tool can be used to fit Continuous (Gaussian), Count (Poisson), and Binary (Logistic) model types. https://doc.arcgis.com/en/iot/analyze/generalized-linear-regression.htm Forest-based Classification and Regression Create models and generates predictions using an adaptation of Leo Breiman's random forest algorithm, which is a supervised machine learning method. Predictions can be performed for categorical variables (classification) and continuous variables (regression). Explanatory variables can take the form of fields in the attribute table of the training features. In addition to validation of model performance based on the training data, predictions can be made to features. https://doc.arcgis.com/en/iot/analyze/forest-based-classification-and-regression.htm ... View more

Hi @MattGeorge1 thanks for your reply and the info and screenshots. If your Map Fields is working with the AVL data, there is no need for us to remove or modify that tool. Multiple tools can be configured across multiple pipelines. What I would propose is adding the Filter by Geometry tool to the model, and dragging the output of your Map Fields to the top (target) input of Filter by Geometry. Then, add your Pit Stops/Depots polygon layer as a data source, and connect that to the bottom (join) input of Filter by Geometry. This must be the same spatial reference as data from your feed. If needed, you can use the Project tool on the data coming in from the feed. Then, configure Filter by Geometry with the Disjoint operator, and any outputs connected to the Filter by Geometry tool will only contain features that do not intersect with your polygons. ... View more

@MattGeorge1 Thanks for posting your question to the Velocity community! The key component I took away from your described scenario above is "The layer has 15 polygons which represent Pit Material locations and Road shop facility’s where the plows go to get salt and sand.  I want to exclude those locations from my output layers." Pit Material locations and road shop facility polygons sound like relatively static locations to me, that are not added or removed or changed that frequently. Is that correct for your case? If so, this would be best added as a data source rather than a data feed. When configured as such, this polygon data would only be fetched when you restarted the real-time analytic (or when we updated the Velocity version, a few times a year). If the goal is to simply remove any vehicle location points where they intersect with these polygons, I would utilize our Filter by Geometry tool with the Disjoint spatial operator. Disjoint is the inverse of intersects. This tool configuration could be added in any analytic pipeline where you want to keep the points that do not intersect a polygon. Here is an image of this in action. The black dots are the original points simulating AVL. The light blue points are the features that are processed and pass the Filter by Geometry disjoint.  ... View more

@JeffSilberberg Thanks for posting your question! I would suggest simply deleting the HTTP Output (after noting your relevant configuration details to facilitate future reconfiguration) and replacing it with a different output like a Stream Layer output. Nobody needs to use that stream layer output, but that will then preserve your analytic pipeline that led to the HTTP Output. Let me know if there are further questions related to this ... View more

When a WHERE clause is configured for a feature layer feed or source, Velocity simply passes the specified clause along to the REST API query operation when it repeatedly queries the feature layer at the designated polling interval. If you are not seeing success with this and have confirmed that these are new features being written to the output (rather than older features that were previously written), I would suggest logging a support ticket with Esri Support Services as this would require a call and screenshare to review your configuration. Additionally, I would encourage you to test your WHERE clause at the REST endpoint of the ArcGIS Online hosted feature layer to ensure that only the desired features are returned by your where clause expression directly at that query endpoint. This will help isolate if there is an issue independent of ArcGIS Velocity, or specific to ArcGIS Velocity. ... View more

When configuring the "Where clause" parameter for an ArcGIS Velocity feature layer feed or source, Velocity is sending the exact query to the REST API query operation for the referenced service. You mentioned that you are configuring a Feature layer feed to reference an ArcGIS Online hosted feature service. Therefore I would encourage in such a circumstance testing your expression at the REST endpoint of the ArcGIS Online hosted feature service as Velocity simply hands the expression along to query at the REST call. In testing on my end, I would also expect the % characters to work with the "LIKE" operator rather than "=" operator. I confirmed success in testing with an expression such as incidentnm LIKE 'baltimore%' AND inspector = 'peter'     ... View more

Thanks for posting - I am not seeing a screenshot, can you provide a screenshot for context? Is this with a Feature layer feed/source where clause? Are you querying a Velocity layer or an ArcGIS Online or ArcGIS Server service? ... View more

Happy to clarify a few items: Velocity-backed layers (map, feature, or stream layers) cannot be shared to the public, however they can be shared to the Organization ArcGIS Velocity can write to/create new ArcGIS Online hosted feature layers (uncheck store in spatiotemporal as you had mentioned), which can be shared with the public ArcGIS Velocity can write to existing ArcGIS Online hosted feature layers which can be shared with the public, using the Feature layer (existing) output ArcGIS Velocity can write to existing ArcGIS Server feature services using the Feature layer (existing) output, and of course your ArcGIS Server feature services can be shared to the public Additionally, Feature layer (new) or Feature layer (existing) Velocity outputs to ArcGIS Online hosted feature layers only allow outputs of up to 120 records written per minute. This is an ArcGIS Online limitation. ... View more