Validate FGDBs after copy to production

agrc / forklift

:tractor::package::sparkles: Slinging data all over the place :tractor::package::sparkles:

MIT License

27 stars 3 forks source link

Validate FGDBs after copy to production #350

Open stdavis opened 2 years ago

stdavis commented 2 years ago

Periodically we've seen FGDBs that are corrupted when they are copied to production (or perhaps receiving?). We should add some sort of arcpy validation (arcpy.ListFeatureClasses()?) to our copy function to make sure that we at least know about it when happens.