File geodatabase api raster

Asked 7 years ago. Active 1 year, 11 months ago. Viewed 3k times. Improve this question. From erouault. Thus, probably doable but not done. Can gdal 2 read rasters in gdb? I'm not aware of it, but would be interested to find out.

Add a comment. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Visit chat. Linked 5. Related Hot Network Questions.

Question feed. Stack Overflow works best with JavaScript enabled. When you specify a geodatabase as input, this tool compresses all vector feature classes and tables in the geodatabase. It does not compress raster catalogs or raster datasets. If it encounters these in the specified geodatabase, it skips over them.

You can individually compress a raster catalog or raster dataset with this tool; however, it makes little sense since the data does not reduce in size.

This support is provided strictly as a means to allow ArcPublisher to package to compressed and locked file geodatabase raster catalogs and datasets. You cannot individually compress or uncompress a feature class in a feature dataset to produce a mixed state where some feature classes are compressed and others are not. Compressed feature datasets allow you to add an uncompressed feature class through operations such as creating a new, empty feature class, copying and pasting, and importing.

However, you cannot edit the uncompressed feature class if there are compressed feature classes in the same feature dataset. Once you've finished adding one or more uncompressed feature classes, you can recompress or uncompress the feature dataset so all its feature classes are either compressed or uncompressed.

When you display compressed feature class records, they may not display in the same order as they did before you compressed the data.

The records display in the order in which they are compressed and stored. When using lossless compression, floating-point values will be preserved, but compression will not be as effective. With non-lossless compression, floating-point values will be changed, but not below the limit of adequate precision.