FileGDB has broken extents when features with no geometries are present.

[cdestigter]

I have a CSV with 100 geometries, some of which are empty/null.

When I convert to FileGDB:

    ogr2ogr -nlt POLYGON -f FileGDB csv2gdb.gdb null-geoms-head2.csv

I get a broken extent (note the (0, 0):

ogrinfo -so -al csv2gdb.gdb/
Warning 1: Empty Spatial Reference
INFO: Open of `csv2gdb.gdb/'
      using driver `FileGDB' successful.

Layer name: null_geoms_head2
Geometry: Multi Polygon
Feature Count: 99
Extent: (0.000000, 0.000000) - (2437341.000000, 5683455.000000)
Layer SRS WKT:
(unknown)
FID Column = OBJECTID
Geometry Column = SHAPE
WKT: String (0.0)
id: String (0.0)

the CSV and GDB are in this zip (~100kb):

​https://dl.dropbox.com/u/2649727/null-geoms.zip

With one much bigger layer, I also get some -MAXINT bits in my extent, but so far I haven't been able to reproduce that with a small enough sample to share here:

Feature Count: 1051140
Extent: (-2147483648.000000, -2147483648.000000) - (2496130.000000, 6223157.000000)

I tried shapefile and mapinfo tab and both are fine, appears this is FGDB specific.

Using gdal from ubuntugis - 1.9.1-2~precise4

[cdestigter]

aha, with the filegdb api 1.2 I get something even crazier:

Layer name: null_geoms_head2
Geometry: Multi Polygon
Feature Count: 99
Extent: (0.000000, 0.000000) - (2437340.380162, 17599482270366625991174440508157674004685900733593819351200808903984042008327394057038596299010613444608.000000)
Layer SRS WKT:
(unknown)
FID Column = OBJECTID
Geometry Column = SHAPE
WKT: String (0.0)
id: String (0.0)

[Robert Coup]

I've done some digging into this today - it seems that NULL/Empty geometry handling causes all sorts of weirdness with the FileGDB API - extents are broken, geometries are mysteriously duplicated, and IsEmpty() doesn't seem to round-trip.

There's also several ways to do things (geometryNull, shapeNull, shapeNull+SetEmpty(), SetNull("myGeomField")) so I need to find out which are the "right" ways to deal with these values.

[Robert Coup]

Submitted upstream at: ​http://forums.arcgis.com/threads/68082-Null-amp-Empty-Geometries Test code for the above: ​https://gist.github.com/3813984

[Robert Coup]

My proposed patch:

• turn EMPTY geometries into NULL
• set NULL geometries via Row.SetNull(geometryFieldName)
• tests for the above

I'll wait until I hear from ESRI before I commit it.

[Robert Coup]

[25078] commits this fix to trunk.

[Robert Coup]

Committed to 1.9 in [25080]