SSP All Edits Report Shows Feature Level Audit History

January 1, 2017 — Colton Frazier Skye Perry  [6:28]

The SSP All Edits Report & QA/QC Tool (now called SSP Delta) has been updated to allow users to search for an individual feature’s audit history across multiple versions. This allows us to see when a feature was created, updated, and deleted. Check out the new tools which will soon be available to customers. Get an overview of the new feature level audit history in this short video.

Are you curious how the SSP Delta product helps actual utilities like yours resolve errors before they are introduced into the production geodatabase? Learn how IREA is using SSP Delta at its Colorado coop to catch errors in one out of every eight designs before they are posted into production.


Hi this is Skye Perry with SSP Innovations. I'm here to talk to you today about an exciting enhancement to our SSP All Edits Report & QA/QC tool. I can't take credit for this myself, but I am happy to show it off today. The development was done by our development team led by Colton Frazier. If you know Colton, you know he always does a great job. With that said, lets jump in.

We of course had an SSP All Edits Report & QA/QC tool since the beginning of our company, 10 years ago. The key focus of the historical usage of the tool was around providing All Edits report on a versioned level, meaning we can determine which edits occurred in a version, save those off, and we can reload them at a later point in time. With that said, the evolution in the tool is to allow us to track edits at the individual record level. Think of an audit level for an individual record of tracking that over a period of time. I'll show that to you in an example here. I have zoomed to an area on the map, and you can see the primary on the left.

This is actually a color by feeder map, indicating this is an energized feeder, in orange here. If you look over here I have a transformer and a piece of secondary going to this building on the right. It is gray indicating that it is not currently energized. So, something has happened here. If I came into this scenario, and I'm in SDE.Default. So, what happened here? Who edited what? Why is this deenergized? And why is there an orphaned island within the data?

Well let’s find out using our tools. The first thing I can do here is to select the individual secondary. The first new tool I want to show is the ability to do a feature search report on the selected feature. So, this allows me to search the history for this individual secondary record, and it is not a specific version. It is searching across all versions in the past that have been posted in this case. So, if I take a look at this report in more detail. I can now see that the new record was created here in the DBO Edit 1 version, and we can see that it occurred yesterday.

We can then see two updates that have also occurred yesterday, of course this is a sample environment where I have mocked up the data, so that makes sense. One version here DBO Edit 2 actually changed the job cost number, whereas the DBO Edit 3 version we can actually see that it changed the value of the feeder from MC-4 to a null value. So, that is what de-energized it. So, something happened and that happened in DBO Edit 3 version that caused this error for this de-energized section. So, now I can certainly go into DBO Edit 3, and explore that some more.

Before we jump into that, I want to show you another tool we've built which is the SSP Find Deleted Features Within Area. This will actually allow me to select an area on the map. I can just draw a box like this, and it will actually query the all edits table to determine if there are any deleted features on the map that were are not seeing, and sure enough I see one primary overhead conductor with object id 549859. So, now we can load the same form for that record, and take a look at the details behind it. Now we are seeing the primary overhead record that was created here, and we can visualize it with the tool. We can see that overhead record was certainly created there and did feed that location. That was created here in DBO Edit 1. We can see here in DBO Edit 2, it was updated.

We can see that the job cost number was updated as well as a fused property on it, and if we visualize that we can also see that it was re-shaped. In the All Edits as you remember the darker or wider orange color represents the old shape, and the later the smaller green color represents the new shape. So, the shape was updated there, but no de-energized issues have occurred. Finally, we can see that it did get deleted here in DBO Edit 3, if you visualize that record we can see the red record that actually deleted within that version. So, we've got that issue, and we can see all the attributes here at the time. That clearly tells us that there was an issue in DBO Edit 3. Let me do one more thing here. We are going to close this out.

We are now going to go back and search our record here, and I'm just going to go ahead and grab the version name to make it an easy search. This version has a long been posted, but we can actually search this record, and we can see a past posted version. We can actually see all of the edits that have occurred within that version. If I visualize that we can see, sure enough, that the primary record was deleted. We can also see that the secondary record as well as the transformer both lost circuit id, which is causing it to be de-energized. So, that is absolutely our culprit.

Finally, if I wanted to go and re-create that record because maybe it was deleted accidently, and it is part of the QA I am doing. I am going to just create a new version here, and we are going to call it "Fix Edits", and I'll make this public and switch into the version. Now within this version I'm going to go and start editing. I'm going to run that same find by spatial search one more time to get that primary record back. We can hit search. Again, I'm going to take this deleted record and flash it. I can actually use our restore delete functionality to re-create that record on the map. You can see that the record has been re-created. Now it does get a new object id. It is technically a new record. Let’s check this out.

We can now see that a new energized primary has been created. It has also further energized the transformer and the secondary. If I want to be extra clear, I can take a few more steps. Let’s go ahead and save these edits, and I'll do an interactive report on this version just to make sure everything looks good. Now sure enough, if I investigate this, I can see and visualize the entire report. You can see my new record up top. If I flash that record, we can see that new primary that has been created. Of course, we can show the fields or not.

We can see the updates and now go from a missing circuit number to a MC-4 meaning that is now being re-energized on both the secondary and transformer. So, just that easily we have repaired the issue in question using the All Edits Report to determine what the issue was, get the exact information we needed to QA, and then to re-create the record without having to mainly edit the underlying data. So, this is one of the new cool benefits of the All Edits tool, definitely check it out. Call us for another updated demo. We can talk through a lot more scenarios.

We Wrote the Book

The Indispensible Guide to ArcGIS Online

Download It for Free

Colton Frazier

Colton Frazier

Skye Perry

What do you think?

Leave a comment, and share your thoughts

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

This site uses Akismet to reduce spam. Learn how your comment data is processed.