Storing Geodatabase Point Feature Class Records With No Point Feature

534
2
Jump to solution
10-27-2016 01:32 PM
Highlighted
Occasional Contributor II

Although I never needed or wanted to do this previously, I now find myself in a situation where it would be nice if I could store records containing project history within the same table as my point feature class.  I reached out to support and at first they said this was no problem at all, but as the conversation went on it was left as though it might work.  So, I'll ask anyone who cares to read this one for their thoughts on this topic. 

Without severely damaging the integrity of the geodatabase, can you store non-spatial records within a point feature class attribute table or, can you mix spatial and non-spatial records in a single point feature class, within a personal geodatabase?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Esri Contributor

It is possible to store both spatial and non-spatial data together. To insert empty geometries, just double-click the empty row at the bottom of the attribute table, which is supported in ArcMap and ArcGIS Pro. Please keep in mind, however, that personal geodatabases are not supported in ArcGIS Pro. 

Although, its possible to store both together, there are some issues that you may experience, such as errors in analysis stating the operation was performed on an empty geometry or in Python, the null geometry will be returned as a Nonetype. 

Simply put, all a non-spatial record represents to the geodatabase is a NULL record (except for in SDE). As long as you are aware that those records are there and the potential issues or errors you may encounter, it should not damage the geodatabase on the existence of null geometry records alone. 

View solution in original post

2 Replies
Highlighted
Esri Contributor

It is possible to store both spatial and non-spatial data together. To insert empty geometries, just double-click the empty row at the bottom of the attribute table, which is supported in ArcMap and ArcGIS Pro. Please keep in mind, however, that personal geodatabases are not supported in ArcGIS Pro. 

Although, its possible to store both together, there are some issues that you may experience, such as errors in analysis stating the operation was performed on an empty geometry or in Python, the null geometry will be returned as a Nonetype. 

Simply put, all a non-spatial record represents to the geodatabase is a NULL record (except for in SDE). As long as you are aware that those records are there and the potential issues or errors you may encounter, it should not damage the geodatabase on the existence of null geometry records alone. 

View solution in original post

Highlighted
Occasional Contributor II

Thank you for the confirmation Christian Wells‌. 

I am familiar with the Personal-Gdb limitations and the unsupported database formats, but I do appreciate your pointing them out here, thank you again. 

In this case I will use Access to feed the map point features in ArcMap (*.mdb), while allowing program staff to manage their clients needs.  I was fairly certain I could store these mixed records, but I was not sure if the Personal-Gdb would break (if you will). 
"Simply put, all a non-spatial record represents to the geodatabase is a NULL record (except for in SDE)" - Thanks again for the confirmation.

0 Kudos