File Geodatabase Updates

[DunnGIS]

Hey all. I was looking for some guidance on best practices for editing file geodatabase assets. Let's say that I'd like to incorporate some new data that was captured using Field Maps or remove information from feature classes. I know that I can turn on editor tracking, but from what I've read, there isn't any versioning, archiving, or replicating support for non-enterprise geodatabases. So, is there any way to roll back changes to a feature class from a FGDB that I'm editing in Pro? If not, are there any procedures that you would recommend? I'm looking to make updating the original data systematic and clear to alleviate mistakes from erroneous field capture, outside information, or data editing.

[MarceloMarques · Accepted solution]

is there any way to roll back changes to a feature class from a FGDB that I'm editing in Pro?

No, there is not. You cannot perform undo for editing operations if using FGDB. You will need to keep a copy of the FGDB before the edits if you want to revert the changes. You will need to move to an Enterprise Geodatabase in Oracle, SQL Server, PostgreSQL and then enable Geodatabase Archiving (Traditional or Branch) and edit the data using Geodatabase Versions and the capability to undo edits during an edit session will be available.

[RhettZufelt]

Not a Roll Back option, but I have a python script that copies my important FGDB's each night to a backup folder, then removes them after a certain amount of time.

This way, I at least have a snapshot of the data from previous days.

R_