Only a subset of data included in .geodatabase

7173
13
Jump to solution
05-09-2014 05:22 PM
MichaelDavis3
Occasional Contributor III
I'm attempting to create an offline geodatabase using the desktop pattern to display ~13k property ownership polygons in an iPad app.

It seems like all of the records are not displaying in the map, and I confirmed this by checking out the .geodatabase file in a sqlite viewer... only about 10% of the records are actually included.

Is there some sort of limit on the number of records that can be exported via the desktop tools?
0 Kudos
1 Solution

Accepted Solutions
JamesRichards1
Occasional Contributor
I think Share As - Runtime Content... limits the records to the current map extent in ArcMap. Were you zoomed in when creating the geodatabase? If so, try setting the zoom level to include all of the parcels you want to export before running the tool.

View solution in original post

0 Kudos
13 Replies
MichaelDavis3
Occasional Contributor III
Using the toolbox tool to do the export works as expected.  Using the "Share" method only exports a subset - and the number of records exported seems to vary with the moon phase or something...

Anyway, for now the answer is pretty clear.
0 Kudos
JamesRichards1
Occasional Contributor
I think Share As - Runtime Content... limits the records to the current map extent in ArcMap. Were you zoomed in when creating the geodatabase? If so, try setting the zoom level to include all of the parcels you want to export before running the tool.
0 Kudos
DavidGreene
New Contributor III
I have 3 feature classes with approximately 162,000 features between them.  I'm using ArcGIS Desktop/Server 10.2.2.  No matter what method I use, I get a different number of features in the runtime .geodatabase. 

Using ArcMap "Share as ... Runtime Content", I end up with about 90% of the source features.  Using ArcToolbox "Create Runtime Content", I only get about 50% of the features.  Publishing it to ArcGIS Server 10.2.2 and using the "Create Replica" REST endpoint, I get about 98% of the features exported.

I've zoomed in to show a subset of the features and the export is limited to those extents (somewhat as expected).  However, zooming out to "the world", I still end up missing between 2-10% of the source features.  What is going on???

I've tried rebuilding the spatial index, exporting from file-geodatabase and a SQL Server geodatabase.

I've also noticed that during the export, the .geodatabase will shoot up to 90MB before being reduced to 35MB.  If I make a copy before the "shrink", I see that 1 feature class has all 85498 features.  Afterwards it only has 42498.  What is happening?

I'm at a loss.  Short of writing my own SQLite exporter, is there something I can do to RELIABLY export this content?
0 Kudos
mikedavis2
New Contributor II
I've had 100% success doing the following for read-only base layer data:
1. Zoom to extent of my data in ArcMap
2. Set Full Extent of data frame in Layers->Properties to the current display
3. Save MXD
4. Use "Create Runtime Content" ArcToolbox commend and be sure to select "Current Display" as the extent to export.

For editable feature data (from a feature service) I'm not sure why you aren't getting everything - is it possible that you have data with invalid geometries or no geometry?  We haven't experienced any issues pulling a geodatabase using a feature service source.
0 Kudos
DavidGreene
New Contributor III
Unfortunately, that resulted in the same truncated export.  I watched it more closely this time.  The process seems to go something like this:

  • Create the schema (around 80KB)

  • Fill in the feature rows one feature class at a time (gets to around 70MB)

  • Creates a new MXD named "CacheTemp.mxd"

  • Pauses for a few seconds

  • The .geodatabase then grows to about 100MB and immediately shrinks to the amount it grew by (around 35MB)

Some kind of post-processing step is clearing out 50% of my features.
The REALLY strange part is the feature counts of the original compared to the export:
[INDENT]
Meters        61184   30184
Lights         15414     7414
Structures   85498   42498
[/INDENT]

The export feature count is exactly: (INT(numFeatures / 2000) * 1000) + MOD(numFeatures,1000)
Something is very odd about that.
0 Kudos
mikedavis2
New Contributor II
Are you using the optimize for size option?
0 Kudos
DavidGreene
New Contributor III
No.  In fact, I had to copy the 3 feature classes to a new geodatabase before I could even get this far.  They were participating in a few relationship classes.

The source file-geodatabase has only the 3 point feature classes.  No domains, relationships, or other special data.  Just a bunch of points and attributes.

I've been using and developing against Esri products since 1989.  I've managed to find a few bugs and work around them, but this problem has me temporarily stumped.
0 Kudos
mikedavis2
New Contributor II
If you just export 1 layer do you get the whole thing?  If so you could always do multiple .geodatabase files.
0 Kudos
DavidGreene
New Contributor III
Exporting a single layer didn't work either.  😕
0 Kudos