The most important factor for feature classes is the average number of vertices per feature. The makeup of coordinates and the number of attribute fields and their contents determine the amount of compression possible.
The amount of compression possible in feature classes and tables can range from a negligible amount to a ratio exceeding 4:1. Benefits of compressionĬompressed file geodatabase data takes up less disk space than decompressed data while still offering comparable display and query performance. The General tab states whether the data is compressed. A compressed feature class or table inlcudes the word (compressed) in the Type column.Īnother way you can tell is by opening either the feature class or table Properties dialog box. Both tools are in the File Geodatabase toolset, in the Data Management toolbox.Ī compressed feature class or table looks the same as when it was decompressed, but you can tell whether data is compressed by viewing a list of feature classes and tables on the ArcCatalog Contents tab. You can also compress using the Compress File Geodatabase Data geoprocessing tool and decompress using the Uncompress File Geodatabase Data geoprocessing tool. When you compress a feature dataset, all its feature classes are compressed. When you compress a geodatabase, all feature classes and tables within it are compressed. To perform a lossy compression, uncheck the Lossless compression check box. The default compression type is lossless. To compress a feature dataset, or stand-alone feature class or table, right-click it in the Catalog tree, click Manage > Compress File Geodatabase, and click OK. To compress a file geodatabase, right-click the geodatabase in the Catalog tree, click Administration > Compress File Geodatabase, and click OK. You can compress a geodatabase, feature dataset, stand-alone feature class, or table. However, if required, a compressed dataset can always be decompressed to return it to its original, read/write format. The compressed data is a direct-access format, so you do not have to decompress it each time you access it ArcGIS and ArcReader read it directly.Ĭompression is ideally suited to datasets that do not require further editing. Also, apart from editing, you work with it the same way. Once compressed, a dataset looks the same in ArcCatalog and ArcMap as when it was decompressed. Where compressed datasets differ from decompressed data is in editing: a compressed dataset is read-only and therefore cannot be edited or modified in any way except for changing its name and modifying attribute indexes and metadata.
#Geopackage arcgis file size limitation full
Lossy compression is a good choice if you require maximum compression and your data is not particularly accurate, or you're not worried about maintaining the full precision of your data, for example, if you're compressing data at a scale of 1:1,000,000 or greater. Lossy compression allows for up to 20 percent better compression of file geodatabase data, but floating-point values will be changed. With lossless compression, when you compress data, no information is lost, regardless of the coordinate system or types of attribute data the feature class or table contains and all floating-point values will be preserved. There are two types of compression that can be applied to file geodatabase data: lossless and nonlossless (or lossy). You might find it provides slight performance improvements in some operations but slows slightly in others.
Once compressed, display and query performance is comparable to decompressed data. To reduce storage requirements, you can compress tables and vector file geodatabase feature classes (collectively referred to as datasets in the rest of this topic) to a read-only format. Restrictions when working with compressed data.