I too have encountered this issues.
I also noticed that when adding certain layers to TOC snapping fails also.
... it sucks.
A coworker is experiencing the same issues with snapping. It's not everyday, it does not occur at a specific point in her editing, workflow or methods. But when it does happen it is VERY time consuming. It has never happened to myself unless I turn on my Address Points file, that is short lived though. We all connect to same server and have our own PGB versions.
In using parcel editing every day we rely on snapping for virtually every move. We don't use the parcel editing tools specifically. We use our standard construction tools for line, polygon, etc and draw them based on surveyor entries on their plats, maps and surveys. So if there is a starting point from an intersection we begin by snapping there and use the Traverse tool to run the bearings, distances and see if it closes.
Any help would be great.
Bud
Snapping problems with 10.2.2 also, especially after getting a new computer with Windows 8.1 upgrade. So to summarize:
No joined tables
No reprojected layers
No large data sets (too many vertices)
Not too many layers
Tweek your SQL spatial types
Work in a clean MXD
Build spatial indexes
Work from shape files or file geodatabases.
WOW! Seems simple enough. Just change your entire workflow.
I know, cynical.
Dear Angela,
I also face with this problem when editing with snapping enable. if we use snapping window can help but really not convenience to work because whenever edit each layer have reset up snapping window.
Do esri help with this issue?
thanks,
I'm using ArcMap 10.4. Pulling all the files I was using into a feature dataset in a file geodatabase solved the problem for me.