Latest Contributions by MattGeorge1

Hello, I was hoping someone could spot something going on with my Velocity workflow, or perhaps something has changed since the end of July 2023 update.  I’ve had no problems until recently with my workflows.  I haven’t changed how things are setup either. I seem to be having problems along every step with the feed, Realtime analytic and feature service outputs.  I’m not able to get anything to work.    My workflow is as follows. I have a feed that runs in the Realtime analytic with two feature service outputs.  Both outputs are Non spatiotemporal because they are used in public facing web maps.  Never had a problem with this setup before but now I can’t get anything to work. I have errors in the feature service data tables, sometimes I have no records, but sometimes if I refresh the feature service records will come back temporarily.  Also, the layers would intermittently display the assets on the map sometimes for a few minutes and now they no longer display at all. The output feature services have always ran great the way they are setup I didn’t change anything.  This started happening after the last update, but I don’t want to rule out that something else has gone sideways because there are a lot of pieces that go into the workflow. Errors I’m seeing: Feed and Realtime analytic. Feed:  The feed is running at 0.4f/s with 1.75 on avg attributes/second.  The feed ingests 54 total public works fleet trucks.  I understand Velocity recommends no more than 2 events per second when running non spatiotemporal workflows.  The recommendation or limitation is governed by our bronze level Velocity subscriptions at the 20K per year price point.  At first, I thought maybe I’m ingesting too many attributes/features but I’m below the threshold, so I think that’s ruled out. FEED SCREENSHOTS: REALTIME ANALTYIC SCREENSHOTS BELOW: FEATURE SERVICE OUTPUTS The top FS output SnowFleet_outputComp is setup for Keep existing features and schema with add all new features, False for spatiotemporal feature layer. The bottom FS output SnowFleet_outputCurrent is setup for Replace existing features and schema, keep only the latest feature for each Track ID value and again false for spatiotemporal. The feature services are added to a webmap, they are styled using filters off Reportime to display current truck locations defined by the filters of different hours of time to display breadcrumbs.  This setup has served us well. I’m seeing errors everywhere.  Also, in the webmap I’m using the Map Viewer, Not classic.  And the feature service output layers are constantly updating but not showing anything on the map.  The blue dot in the webmap layer flashes nonstop like a pinball machine gone haywire.  Sometimes data shows up in the table other times not. Is anyone else having a similar experience where an otherwise normal functioning workflow has stopped working how it should? This all started at the end of July.  I was able to get it to work on and off the last week or so, but now I can’t get anything to work. Sometimes if I stop the feed and analytic and then start them back up, and I’ll see data show up on the map, but then it goes sideways shortly after.  Thanks for taking the time to try and make sense of this.  I could really use some help to figure out how to resolve this.  Or is there something going on out of my control that we are not aware of. Matt   ... View more

I’m looking for advice on setting up the best approach to create a Geofence in Velocity.  I have a real time analytic setup with two output layers.  I created a winter operations public facing snow plow map which is running in an ArcGIS solutions insta app frame.  Our County Public Works winter ops fleet is made up of 54 vehicle assets, and the two output layers in the real time analytic show vehicle observations.  One of the outputs keeps the latest observation displaying current location, it updates 2 minutes.  The other layer is very similar except it keeps all location observations and adds to the feature service to create a history of vehicle point locations along our primary snow routes.  I also have a new layer I want to use to isolate vehicle points in some specific locations.  The new layer is not in the real time analytic yet.  I’m trying to figure out how to setup a geofence with it but I don’t think it’s the traditional geofence workflow or maybe I’m misunderstanding the right approach to take in setting up a geofence for my purpose. 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. My workflow setup: I run both outputs as non-spatial temporal so that I can share publicly on our County home page.  We have the green light to share the web app out but I need to first figure out how to accomplish one more action item before it’s ready.  I need to hide vehicles when at pits and facilities.   In the web map / web app I run the current observation layer with a directional arrow icon using heading degrees to indicate the vehicle direction of travel.  I then copy the other output layer (3x) which shows all observations in the webmap and filter each copy by a different amount of time to create a layered effect showing points as breadcrumb trails for the Last Hour, Last 1-4 hours, and 4-12 hours ago.  It works really well and everyone seems to like it.  The first hour uses a much more contrasted symbol to pop it off the map and subsequent times layers use a faded color with some transparences. The Points get real busy in the pits and road shop facility areas and we only want to display vehicle points publicly when they are on our primary snow plow routes.  I’ve thought about using Snap to Network to clean up the points where our vehicles travel, but truthfully the points are actually clean and display nicely when they update.  I’m wondering which path to take to accomplish this; a Geofence of some sort or snap to network. I wonder if what I’m trying to accomplish is like a reverse geofence? if such a thing exists.  If I was to use the polygon feature service with pits and shop locations  where would that go in the Velocity real time analytic, before the map fields piece and after the feed, or after the mapping fields and before the output layers?  Or should I be thinking about snap to network more so than a geofence option?  I’ve read about Filter by Geometry and I’m learning about those geofencing parameters.  That would require to me add a join ID field to the polygon pits shop layer I assume if I need to also apply some logic with the Join time Windows, End time parameters piece etc. I never saw where I could simply throw that layer into the analytic and logically not display trucks when within those polygons. That seems like a long way around to accomplish not displaying the trucks at certain locations.  I think of Geofences as areas I want to capture something when a truck enters the area.  I want to exclude the oppositive in this situation.  Should I add a Join ID field to my Pits and Shop polygon layer so that I’m prepared to connect it somewhere in the real time analytic.  Does anyone have suggestion on which path I should take to accomplish this.  Here’s what the web app frame looks like showing the observations mentioned above.  Thanks for your help if anyone can give me some pointers. Pic attachments show the app running on my iPhone from the Insta web app and one is from an OpsDash I made for internal use.  The second pic is a great example of truck traffic when at our facility coming in for Salt loads.  The map changes drastically throughout the day and night when things are happening.  Some of the time there are no points to display if enough hours have passed outside my time filters on the layers without any truck assignments. Thanks, Matt George     ... View more

While entering/updating attribute field information from domains stored in SDE the Collector for iOS form resets itself with no consistency each time the user attempts to complete the form.  It happens after filling out 1 to many fields.  The occurrence is random each time the user enters an edit session in collector.  If the user is lucky enough to populate all fields in the form it will also leave a ghost image of the form when submitting the changes.  Some users can reach 2, 3, 4..8..12 fields before the form resets itself.  If the user is lucky enough to fill out all fields and submit changes the data is stored in the database but this doesn't always happen. This began after the 10.3 update but is not specific to iOS 8.1.3 or 8.2 since the newer version of iOS was released the same day 10.3 Collector was released on March 9th, 2014.  Is anyone experiencing similar issues?  I've rebooted devices, tried other feature services, all respond the same.  In house hosted ArcGIS Server is running on 10.2.2  For what's it's worth, the first edition iOS ArcGIS application works as a backup option for updating and editing feature services until Collector issues are fully resolved.  Note:  The last update to ArcGIS for iOS was in August of 2013 and it seems to be bulletproof as a viewer/editor although a little of the slow side compared to Collector.    Thanks, Matt ... View more