Static Versions for Change Detection in the UN

Question

Hi all -

In our current implementation use use several "static" versions to assist with Geodatabase change detection.  For example, there is a nightly process that compares a static version with SDE.Default to determine which feeders have changed in order to inform the OMS interface which feeders need to be extracted and updated in the OMS database.

There are other static versions for other, somewhat similar purposes.

For OMS we might be using ArcFM GDBM/Feeder Services to detect changes.  But for other, non-feeder change purposes, we're wondering if we need to keep static versions around.

Any thoughts/experiences on this would be much appreciated.

Thanks,

Ed

EdwardBlair · Answer

@gis_KIWI4   Pretty interesting.   Thanks much for the detail. We will check out these options!

GIS_kiwi4 · Answer

@EdwardBlair - I am assuming your non-UN feature classes have versioned data. You can continue using static copies to get version differences but if you didn't want to keep the static copies then use the ExtractChanges or Query(with Historic Moment) or simply using the EditDate query?

Each one comes with it's own set of advantages and disadvantages.

ExtractChanges - Most robust and gives you the "delta" so you don't have to find differences within a FME process. This is slightly more complex to implement because you have to store generation states (layerservergens) and use them for the next query.

Query(with Historic Moment) - Simple but you have to read the entire dataset twice (current and historic) and then set up change detection. If the dataset is sizable then you risk running the process longer.

EditDate query - Simplest of the lot but you have to figure out how you will account for deletes.

Our datasets are pretty modest in size and we have used Query with the FME CHANGEDETECTOR transformer.

EdwardBlair · Answer

Hi @gis_KIWI4 ... thanks much for the feedback.

I should have been clearer.   For subnetwork change detection we *hope to* use the SE GDBM framework.

Thing is, we also need to detect changes to other, non-Utility Network feature classes.   This is, at the moment, what I'm most interested in.

Ed