Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're using file geodatabase for tax mapping. we save building photos and there are 6000 buildings. The size of this data 2GB. So loading the data takes a lot of time we are not unable to do work easily. If there is any options to solve this problem, please share them with me .

share|improve this question
may be compressing and compacting file geaodatabase help you.right click your file geodatabase click compact database .click compress file geodatabase – wetland Dec 4 '12 at 11:37
what's your rasters format ? Jpg,Tiff,Png ,.... – wetland Dec 4 '12 at 11:43
Thanks for your guidence.We were using JPG format . – RajGovind Dec 4 '12 at 11:57
why don't you use png ? png is good format for storing images . because you can store an image with high quality and low size storage in windows . for example if you store image x in JPEG format and 450 dpi .the image size in windows will be nearly 1.5 megabyte or higher but with PNG format and 450 dpi resolution the size of image will be nearly 250 kb . – wetland Dec 4 '12 at 12:04
your welcome . another way is using raster catalog to save and manage images . right click in the file geodatabase. click raster catalog. load your image in raster catalog and manage them . it's good for georeferenced rasters. – wetland Dec 4 '12 at 13:44

You may even want to consider splitting your geodatabase into two parts, if possible. One for the tax maps, another for photographs. However, if your photos are attributes to your tax layer features, then your you should consider compacting and compressing your file geodatabase, as already mentioned in the comments.

A couple of notes about compact vs compress.

Compacting tidies up storage of records in files by reordering them and eliminating empty space. If you frequently add and delete data in a file or personal geodatabase, you should compact your geodatabase on a monthly basis. This can reduce file sizes and improve performance.

  • If your data is organized in such a manner that some of it is read-only, then you can consider "compressing" your data. It should be noted that all features in a compressed state are not editable, read-only. Therefore if your images are attributes to your tax data, you will not be able to compress the featureclass if you want to continue editing (which I assume you will want to be doing). Compress is really great for base data that won't change very often. You can compress the entire geodatabase, a feature dataset, or just the featureclass that contains your images.

To reduce storage requirements, you can compress vector file geodatabase feature classes and tables (collectively referred to as datasets in the rest of this topic) to a read-only format. Once compressed, display and query performance is comparable to decompressed data. You might find it provides slight performance improvements in some operations but slows slightly in others.

share|improve this answer
Thank u Mr. RyanDalton – RajGovind Dec 5 '12 at 5:35

Try to compress database :

share|improve this answer

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.