How to Convert from Esri Mobile Geodatabases

Liz Sanderson
Liz Sanderson
  • Updated

Introduction

FME supports converting from Esri Mobile Geodatabases into any format. In addition, we also support converting to Esri Mobile Geodatabases. Esri Mobile Geodatabases are ArcGIS Pro geodatabases stored in a single file within a folder of a SQLite database. 

In this tutorial, we will explore one approach for reading data in any format and writing it to a geodatabase using an XML workspace document as a template.

Requirements

  • Licensed ArcGIS Pro on the same machine as FME Form

Step-by-step Instructions

1. Add an Esri Mobile Geodatabase Reader

Open a blank workspace in FME Workbench. Add a reader to the canvas and set it to the Esri Mobile Geodatabase format, then browse to the Vancouver.geodatabase dataset, which you can download from this article under the Files section in the top-right corner. Then click on Parameters.

Reader.png

In the parameters dialog, click on the ellipsis next to Tables and select:

  • main.Neighborhoods
  • main.Parcels
  • main.VancouverLandBoundary

ReaderParams.png

Click OK three times to finish adding the reader. 

2. Add Esri Shapefile Writer

Add an Esri Shapefile writer to the canvas and browse to a folder to save the shapefile. Leave the Shapefile Definition as Copy from Reader, then click OK.

Writer.png

In the Select Feature Type dialog, click Select All and click OK.

SelectReader.png

3. Connect Reader and Writer Feature Types

Connect the reader feature types to their associated writer feature types.

Connections.png

4. Modify Output Attributes

Since we are writing out to shapefile, there is a maximum attribute character limit, so we will need to modify a few attributes.

ModifyAttributes.png


Add an AttributeManager between each of the connections (a total of three). If you click on the connection line before typing AttributeManager, it will automatically connect. 

In the AttributeManager connected to Neighborhoods, change the st_area(SHAPE) attribute to st_area and then change st_perimeter(SHAPE) to st_perim.
AttributeMan_Neighborhood.png

Change the same two attributes for the AttributeManager connected to Parcels. 

Finally, for the AttributeManager connected to VancouverLandBoundary, change the following:

Input Attribute Output Attribute
VancouverID VanID
main.VancouverLandBoundary.Area Area
st_area(SHAPE) st_area
st_perimeter(SHAPE) st_perim

5. Modify Writer Feature Types

One final step before we can run the workspace is to modify the writer feature types. Open the main.Neighborhoods writer feature type. Remove main. from the Shapefile Name.

ShapefileName.png

Then, switch to the User Attributes tab and change the Attribute Definition to 'Automatic'. Click OK.

AttributeDefinition.png

After clicking OK, all attributes on the writer feature type should display a green arrow, indicating that they are mapped correctly.

MappedOutput.png

Repeat this step with the main.Parcels and main.VancouverLandBoundary writer feature types. 

6. Run the Workspace and Inspect Output

Run the workspace, then inspect the output using Visual Preview or Esri ArcMap or ArcPro.
Output.png

Data Attribution

The data used here originates from open data made available by the City of Vancouver, British Columbia. It contains information licensed under the Open Government License - Vancouver.

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.