Nil v null geometries. Which one does ArcMap create when only entering attribute data

716
4
05-02-2012 02:06 AM
TimLangner
Occasional Contributor III
Hi there

I am currently working with some spatial data, where there are developments at a stage where I cannot plot them on the map but I still need to record their details in the attribute table. Currently I simply enter the attribute details and it creates a new row with 0 in the shape and length fields. Could anyone tell me if this new row contains a nil geometry or a null geometry?

I am using ArcMap 10.0.4 and ArcSDE 9.3.1, with the back end being Oracle 10g. I came across an interesting article which talked about null v nil geometries for ArcMap 8 through to 9.3.1 and Oracle.
http://support.esri.com/en/knowledgebase/techarticles/detail/32237

Kind regards

Tim
0 Kudos
4 Replies
VinceAngelo
Esri Esteemed Contributor
I'd expect it to be NULL, but the answer may depend on the version and geometry
storage format. You can determine this yourself easily enough by using 'sqlplus' to
SELECT the geometry column and see what it returns.

- V
0 Kudos
TimLangner
Occasional Contributor III
Thank you for your reply

vangelo

I'm not 100% certain of the storage format off hand. Also I don't have access to SQLplus myself at the moment and I can't check in ArcGIS because geometry checks on the SDE are not allowed.

However I was able to do a dissolve geoprocess of the feature class and it said it successfully completed it. It may be that null geometries are allowed when running  dissolve geoprocess. Thus it may not actually matter going forward that they are stored as null.


Kind regards

0 Kudos
VinceAngelo
Esri Esteemed Contributor
Well, it depends on the application of course, but from a processing standpoint (especially a dissolve),
there isn't much difference between a NULL column and a nil geometry (you wouldn't union either).

- V
0 Kudos
JoeBorgione
MVP Emeritus
Just an additional $00.02:  I make it a practice of scanning my data for and then deleting null geometries through the attribute table; look for the feature size (area or length) value that tips you off.
That should just about do it....
0 Kudos