Example: Convert an ESRI File Geodatabase into a .map Project

 

Example: Convert an ESRI File Geodatabase into a .map Project

This topic shows how to convert data in ESRI's current file geodatabase format into a  Manifold .map project in a single step.  We convert ESRI's example NapervilleGas GDB geodatabase, all 857 files, into a single, unified Manifold .map project.

 

ESRI's file geodatabase format is new "geodatabase" format introduced by ESRI in ArcGIS 9.2.    Data in a file geodatabase is stored within a folder in the Windows file system in the form of very many files, all of which must travel together in an ensemble to avoid damage.   The tiny NapervilleGas example published by ESRI and used in this topic requires 857 separate files.  

 

Despite the obvious risk of storing valuable data in the form of hundreds and hundreds of Windows files, all of which must travel together as a unified ensemble, ESRI file geodatabase format has become the standard for current ESRI products and is promoted by ESRI over personal geodatabase format.  ESRI users seem to agree that personal geodatabases as a format are on their way out, being replaced by file geodatabases.   

 

Manifold users will want to convert their file geodatabases into either Manifold .map projects for immediate, high-speed use or into ultra-compact Manifold .mxb archive files for archival storage and exchange.    While personal geodatabases only require keeping track of a single .mdb file, the sheer inconvenience and risk of dragging along hundreds of files within a file geodatabase will make conversion into a single, totally reliable, ultra high speed .map file or ultra compact .mxb file a priority in the case of file geodatabases.

 

Lucky for us, Manifold's Export  capability can convert an entire ESRI file geodatabase into a .map or .mxb project in a single step.   Here is how:

 

We will use the NapervilleGas geodatabase published by ESRI.

 

eg_convert_esri_gdb_map01_00.png

 

The "geodatabase" consists of a Windows folder called NapervilleGas.gdb that contains 857 files, or 858 files as in the illustration above if the ESRI gdb driver has the geodatabase open and has created one more file, a lock file, in the folder.  

 

One, and only one, of those 857 files has the name gdb without any extension.   That file is the entry point to the geodatabase and is the file we choose when linking a file geodatabase into Manifold.

Link the File Geodatabase as a Data Source

eg_convert_esri_gdb_map01_01.png

 

We launch Manifold and choose File - Link.  

 

eg_convert_esri_gdb_map01_02.png

 

Choose GDB Files as the type of file and navigate into the NapervilleGas.gdb folder that holds the geodatabase files.   Since we have selected GDB Files as the type of file Manifold will spare us the need to scroll through hundreds of files and will show only the gdb file.  We click on that and then choose Link.

 

eg_convert_esri_gdb_map01_03.png

 

A new data source called gdb appears in the project.  

Export the Data Source

We click on the + box by the name of the data source to expand the data source, to see the many drawings and tables that are stored in the geodatabase.    Next, we Right-click onto the gdb data source.

 

eg_convert_esri_gdb_map01_04.png

 

From the context menu that appears we choose Export.

 

eg_convert_esri_gdb_map01_05.png

 

In the Export dialog, we can choose between .map, .mml and .mxb formats.  .mml is a specialized format used for development.   .mxb is a compressed, archival form of .map format.   .map is regular Manifold .map format.  If we want to export to a .map file we choose MAP Files as the type.   We provide a name for the new .map file and we press Export.   Done!

 

eg_convert_esri_gdb_map01_06.png

 

In the Export dialog, if we want to export to an .mxb file we choose MXB Files as the type.   We provide a name for the new .mxb file and we press Export.   Done!

Verify Export by Opening the Exported Project

We can verify that the data source has been exported into  a new .map project by opening the newly-created .map file in a new project.

 

eg_convert_esri_gdb_map01_07.png

 

In a new, blank Manifold session we choose File - Open.

 

eg_convert_esri_gdb_map01_08.png

 

We navigate to where we saved our .map and, if we also exported it, our .mxb files.   We click on the .map and choose Open.

 

eg_convert_esri_gdb_map01_09.png

 

The .map project opens instantly, and we see that the export process did, indeed, convert all of the NapervilleGas file geodatabase content into a single, high-performance .map project.    In the illustration below we have used Style to color the areas in the TaxParcel Drawing using the OBJECTID field using the equal count method with 8 breaks and the CB Paired palette.

 

eg_convert_esri_gdb_map01_09a.png

 

If we had opened the Manifold .mxb archive, we would have reconstituted the above project as well.   The only difference would be that the .mxb would not open instantaneously as does Manifold's everyday working format, .map, since the .mxb compressed archive file must first automatically be decompressed into .map form.

Operational File Sizes Compared

We can compare file sizes when storing the same spatial data in ESRI form or Manifold form.

 

eg_convert_esri_gdb_map01_10.png

Right-clicking onto the NapervilleGas.gdb folder and choosing Properties gives the above report from Windows.   The file geodatabase in native ESRI file geodatabase format, ready for use within ArcGIS, occupies about 60 MB and requires 857 files.

 

eg_convert_esri_gdb_map01_11.png

 

Converted to a .map the spatial data occupies about 131 MB, roughly twice the size of the original ESRI file geodatabase, but only one file is required.   That one file, of course, is also fully parallel Radian technology delivering speed many times faster than possible with  geodatabase format.

Archival File Sizes Compared

Manifold's MXB archive and exchange format has been designed to compress Manifold projects as good as or better than zip technology.    When converting a personal geodatabase into a Manifold project the resulting .mxb archive file will usually be significantly smaller than a zip file containing the personal geodatabase in Microsoft Access .mdb format.   With file geodatabases a zipped geodatabase will often be about the same size as an equivalent .mxb archive file or even slightly smaller.

 

In the case of the NapervilleGas file geodatabase, when ESRI's 857 files are zipped together into a single zip file they occupy under 21 MB.   The equivalent Manifold .mxb file is 24 MB, slightly bigger.     As file geodatabases get bigger, the difference between the zip file and the .mxb tends to get smaller, with the .mxb becoming smaller in some cases depending on the file geodatabase.

 

Notes

ESRI Geodatabase Formats - ESRI products utilize three forms of "geodatabase" format for storing spatial data:

 

 

 

 

Manifold can link into a project as a data source all of the above three ESRI geodatabase formats.

 

Viewer is Free - Manifold Viewer provides a free viewer to explore and to analyze sophisticated databases.   Although Viewer is perfectly capable of connecting to the above three different forms of ESRI geodatabases, it makes way more sense to publish such data in the form of .mxb files for people who are using Viewer.     

See Also

File - Export

 

File - Export Project

 

File - Link

 

Example: Convert an ESRI Personal Geodatabase into a .map Project