creating flat structure GeoEvent Definition from Verizon Networkfleet
Accepted Solutions
Hello Folks
We have been using Verizon NetworkFleet inputs with GeoEvent for about the past 18 months. I'm happy to share what we've learned (mostly the hard way). We currently have public snow plow maps displaying live vehicle locations around the City. Here a few notes that we have discovered along the way:
- The Verizon GPS payload is really the only one we care about
- For adding attributes like a vehicle id, vehicle group, or driver names, we found using the Field Enricher (feature service) is the most reliable way to go
- It is a good idea to come up with a data retention policy for AVL data because it can grow large fast and it will ultimately slow your feature service down if you don't truncate/archive it
Here is some information I recently shared with another user about we setup our GeoEvent services to add vehicle id's and other custom attributes:
Hi Eric and Erik
Thanks for asking this, it has made me finally document our primary GeoEvent service! With GeoEvent, even a simple sounding task often winds up being quite convoluted.
For your main question the type of output connector you will need is Update a Feature. This will require that you have created a featureclass in an SDE geodatabase and published it with ArcServer (or Portal?) with at least query, add, and update access.
The bit about "GPSFix.Speed[0].Value" has to do with the data coming in as an array (or series of arrays, if I understand correctly). Hooking your input up directly to a text output (JSON) will let you see what the raw data looks like. In this case, you have two levels of array: GPSFix has several values (VIN, MessageTime, Latitude, Speed, etc.) Thus you have "GPSFix.Speed." However, there are three different speed readings: instantaneous, average, and maximum (since the last message, I think). Thus "GPSFix.Speed[2].Value" will give you the number for the maximum speed; you could also ask for "GPSFix.Speed[2].Units to learn that this is in MPH.
I'm attaching a screenshot of our service and another of a JSON. I have more I can share if you like.
One word of advice: you will want to pay close attention to GeoEvent Definitions. Some processors work best if you have created the definition yourself (say, when you are using the Field Mapper to ensure that you output matches the schema of your feature class), while other processors will want to create their own (like the field enricher).
Good luck!
Nathan -
Thank you very much for sharing your GeoEvent service workflow, more questions on that later.
My struggle early was that I kept trying to create our output as a streaming service, nothing worked. Early last week I decided to do what you just shared – I created an Output “Add Feature to the Spatiotemporal Big Data Store”
With that done we were able to create a GeoEvent Service – this is where the Field Mapper Processor comes into play in order to ‘flatten’ the Verizon hierarchical field structure. We created our own GeoEvent definition to match the desired fields as outlined in the Verizon training document.
In the original Source Fields for the field mapping processor the values were all GPSFix.Speed.Value. update those source fields with the respective [0], [1], [2] doing so appeared to resolve correctly.
Now, after reading Nathan's post, I’m wondering if what we need to do is create a new service that will Update the feature ?
The existing Add a Feature appears to be working in that we have points on the map now… a lot of points.
Nathan, would you be willing to share the details in the various processors you use in your GeoEvent service? The Current Time, Add Fleet Data, Pass Through…all of those have me very curious about what more we can do with this.
I know I need to read the GeoEvent Tutorials, but I’d just like to get something up for our street department.
Thank you for your response – very much appreciated.
