Select to view content in your preferred language

Move Edge Vertex Fails in Utility Network Database

913
3
Jump to solution
01-19-2026 08:27 AM
EdwardBlair
Frequent Contributor

I’ve been trying to track this one down for a while and I’m stumped.  Any suggestions would be *greatly* appreciated.

The error I’m getting is this when attempting to move or delete a vertex on a line feature in the PipelineLine feature class :

EdwardBlair_0-1768839951523.png

We’ve all seen this, or some variation over the years.  We try to add a feature whose geometry is outside the defined feature class extent and Arc barks at us.

This one *seems* to be different.   Here are my steps.

  1.  I load data into an asset package FGDB based on the UPDM model.  Points, lines and annotation.
  2. I can modify line geometries in the asset package to my heart’s content.  No errors.
  3. I then a) Stage Utility Network in a new file geodatabase, b) Apply Asset Package to this new UN database from my asset package, and c) append feature classes from the asset package to the UN database.  
  4. I’m to a point where there a very few dirty areas, but when editing in the UN geodatabase I consistently get the “Modify vertices failed” error on any line feature.

I’ve verified that the spatial references in the asset package and UN db are identical.  I’ve also taken these steps:

  1. Re-built the spatial index on the PipelineLine feature class.
  2. Re-calculated the spatial extent of the PipelineLine class.

Note that I can delete a line and create a new line at the same location without error.   I can also create, move and delete point features without error.

Again, any thoughts on this would be much appreciated.

Ed

 

0 Kudos
1 Solution

Accepted Solutions
EdwardBlair
Frequent Contributor

I found it!

My map projection matches the data that I am editing.  I had checked this multiple times.

HOWEVER, I had several other projections in my Favorites list that were *far* from my current map project.   Once I removed these Favorites I was able to update vertices.  

Holy cow!  I don't know why the editor would be looking at the Favorites rather than the assigned projection, but apparently it was.

Ed

EdwardBlair_0-1769019628170.png

 

View solution in original post

0 Kudos
3 Replies
Lorne_Dmitruk
Occasional Contributor

Are the vertexes within the service territory? If they aren't, that could be causing the problem..

0 Kudos
EdwardBlair
Frequent Contributor

Thanks for the reply.   The vertices and all other geometry are within the bounds of the ServiceTerritory.

Ed

0 Kudos
EdwardBlair
Frequent Contributor

I found it!

My map projection matches the data that I am editing.  I had checked this multiple times.

HOWEVER, I had several other projections in my Favorites list that were *far* from my current map project.   Once I removed these Favorites I was able to update vertices.  

Holy cow!  I don't know why the editor would be looking at the Favorites rather than the assigned projection, but apparently it was.

Ed

EdwardBlair_0-1769019628170.png

 

0 Kudos