search

kcigeospatial / MDOT-SHA-NPDES-Next-Gen

Code and issues related to the MDOT SHA NPDES Project. Project codes: Config = 31, Management = 32.
0 stars 0 forks source link

Updates in FTS_EDIT_LOG #411

Closed KCI-Ablowers closed 5 years ago

KCI-Ablowers commented 5 years ago

@johnshiu For the edit log, what is considered an update?

We have a couple of firms coming back with comments saying that they have SWMFACs that they did not inspect which showed up in their "Inventory QC" sheet. I set up the sheets by joining the FTS_EDIT_LOG to the SWMFAC and breaking them up by the firm.

WBCM for example -

image

We noticed this with KCI_1 as well. I haven't had a chance to investigate further, but what I know right now is that the KCI_1 QC shows some BMPs that were inspected by MES, but show up as being edited by KCI_1 in the edit log. MES also noted that they had BMPs in their QC sheet which they did not inspect. I'm waiting for them to send me a list so I can compare it with our data.

There are also a few instances where two firms have the same facility in the inventory QC sheet. I'm guessing this is either related to what an update actually is? or maybe happened during an internal QC process.

johnshiu commented 5 years ago

@KCI-Ablowers, the edits that are committed and shown in the FTS_EDIT_LOG are based on the last edit date within the database. If any activity triggers an change that would update this date/time in the database, then it counts as the feature being edited.

In the AGOL webmap, this might get triggered by simply selecting a SWMFAC and touching one of the fields, even if no actual values were updated. It really depends on the application. I'm not sure what conditions would cause Collector, for example, to register an edit back to the inventory feature service, but it could be similar.

This may require some testing to be done to determine what actions could inadvertently trigger an update of a feature. I think for now, however, you can assume that there will be some SWMFACs that were not 'really' edited but just selected/viewed, which caused an edit to get registered in the database, even if no actual data values were updated.

CC: @talllguy

KCI-Ablowers commented 5 years ago

@johnshiu I would agree. I think we need to test this out with some different methods/applications. On my end, I think we will need to modify how we are going about doing this inventory QC against production after the field QC versions are rec/posted.

From the ArcMap help page -

When values are recorded ArcGIS automatically records new editor tracking values whenever a feature or record is inserted or modified in any way. This includes modifications to user-defined attribute columns, system columns not defined by the user, and the shape column that stores feature geometry.

Most types of operations record tracking values, including those that automatically update data behind the scenes. For example, deleting an origin in a simple relationship automatically updates the foreign key column in the related feature, and so records new tracking values for the related feature.

For now, I will let the firms know that there may be some "false positives" so to speak in the inventory sheets for all features, not just SWMFAC.