Feature extent keeps getting out of whack

[MikeSchonlau]

We have staff who edit our sewer manhole points daily. Every month or two, the feature extent on this layer gets way out of whack. We haven't been able to pinpoint any specific editing process that we think would cause this. I typically just recalculate the feature extent and move on, but we'd like to find a permanent solution to this issue. Has anyone else experienced something similar? Our point feature class is stored in a feature dataset using our local state plane coordinate system. The data is always edited in a map document using the same coordinate system.

[MichaelSnook]

We are having the same problem with our Parcel Fabric.  We are also in a local State Plane Coordinate system (Meters) and edit it as such.  Nearly every edit session will push the Line feature extents Min X and Min Y to the maximum of the domain....it doesn't seem to affect the Max Y/X.  The data is in a SQL Server 2014 geodatabase.

Oddly...this doesn't happen when the same data is in a PostGres database.

Also, editing/viewing performance slows tremendously once this happens.

Any help would be great.

Thanks!

Mike

[Robert_LeClair]

By chance, are you projecting on the fly with your layers in the data frame?  For example, you're dataframe coordinate system is WGS1984 while the layers are in your local state frame?  If so, then this may explain the issue you're seeing.

[MichaelSnook]

We are editing in the same coordinate system for all layers and dataframe.  We have tried both editing without any other layers (ESRI basemap for example) and with...same results.

[Robert_LeClair]

Michael - another suggestion.  Is your data being stored in a multiuser geodatabase?  From my research, there could be a version with invalid geometries.  If so, delete the features.  Delete the spatial grid index.  Recreate a new spatial grid index.  Recalculate the spatial extent of the feature class.