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.
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