Make compress file geodatabase compatible with new field formats

[DuncanHornby]

I often compress file geodatabases to reduce data volume for static datasets. I am also being supplied , in ever increasing regularity datasets supplied as geopackages. When I import such data into a file geodatabase it takes on the field formats but the compression tool errors with this message:

ERROR 161003: Cannot compress ea_detailed_watersheds. Compression not supported on 64-bit object ID, big integer, date only, time only or timestamp offset fields.

So my idea is to update the compression tool to work with 64-bit object ID, big integer, date only, time only or timestamp offset fields as these will become increasingly more common.

[BSBlagojevic]

Yes!

[AlfredBaldenweck]

I'm surprised that that wasn't taken care of when the new field types were introduced.

[SSWoodward]

Thank you for the idea @DuncanHornby.

After technical review, this idea has been closed. There are no foreseeable plans to enable compression on classes containing the new field types using the Compress File Geodatabase Data GP tool. Compress File Geodatabase Data is intended for mature datasets.

When importing or copying data using the Copy tool, Geopackage and SQLite data will transfer over with a 64-bit OID since a Big Integer data type is used as their unique ID column by default. If possible, try using the Copy Features, or Copy Rows GP tools to create 32-bit OID classes in your file geodatabase and maintain compressibility when no other new field types are present.