Topology Editing Errors in 10.1 SDE GDB

[BradOleson]

Hello -

I am seeing strange problems with pretty simple topology edits in ArcGIS 10.1 in and ArcSDE GDB.

The features are very simple: line feature class and a point feature class that has coincident points matching line vertices.  INitially everything works fine in the topology.  When I zoom in and start moving the points, they are correctly connected to the line and move properly.  Panning down the line to the next point or points, however, shows that the next points that USED to be coincident with the line are now OFF the line.  I have worked with the same data in a file GDB and did not experience this issue.

Has this happened to anyone else, and is there a fix for it?  ArcGIS 10.1 with SP 1 has been applied to the desktop environment.  Oracle 11g DB for the SDE instance.

Thanks in advance for any help!

Brad

[MarcoBoeringa]

Brad,

I don't know if this is part of your issue, but you may wish to read the section "Example projected editing scenario and results"  and "Editing features in a geodatabase topology" about topologies and projections on this Help page:

About editing data in a different projection (projecting on the fly)

In all cases, as recommended on that page, it is best to set the Data Frame's coordinate system to the one used by the Topology. This will avoid unexpected results.

Another possible issue, and why you aren't seeing similar issues with a FGDB, may have to do with the set "X,Y" resolution and whether the data is high precision, or legacy low precision. Feature coordinates in an ArcSDE enterprise geodatabase won't be more precise than the set X,Y resolution (e.g. meters, centimeters, millimeters), meaning vertices will be "snapped" to these coordinate values when editing and moving.

[BradOleson]

Thanks, Marco - I will set the data frame to the data projection and see if that helps.

I don't think it is a precision issue because the topology layers come in with the correct errors found during validation, and whatever point - line combos I initially move behave correctly.  The error occurs usually after panning to work on another area of the data.

I'll see if the data frame projection issue fixes things.  Otherwise I may try a support ticket and see if that works.

Thanks again for your suggestion!  I'll post results here after I have a chance to check things out.

Brad