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

The beta 2 release File Geodatabase API includes 64 bit support.

Esri says arcobjects is still the "preferred" method to interact with the file gdb. However, arcobjects has no 64 bit support.

Assuming licensing is not a factor, in what situations would it be better to use the 64 bit file gdb api rather than arcobjects?

share|improve this question
up vote 9 down vote accepted

It's all about the memory limitations of 32-bit architectures. The benefit of 64-bit support is that you get access to 16 terabytes of virtual memory compared with 4 gigabytes in a 32-bit architecture. You also get access to more paging file space, system cache, etc.

It would be necessary to use the 64-bit version of the File Geodatabase API if you were reading a very large geodatabase into memory. That said, for general use the 32-bit version will likely be preferable even on 64-bit platforms.

share|improve this answer
Thanks Ray. I suppose it should be possible to write a 64 bit implementation of a mapservice that complies with Esri's REST api that would out-perform ArcGIS Server mapservices, which are 32 bit. – Kirk Kuykendall Feb 15 '11 at 20:01
I like the way you think, Kirk. ;) – Ray Vernagus Feb 15 '11 at 20:12

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.