Select to view content in your preferred language

Features jumping on map

241
9
12-02-2024 12:10 PM
mshanaghan
Frequent Contributor

Hello. I am working with the electric utility network. Sometimes, when I change an attribute for a feature and click apply, that feature will jump a few feet north on the map. I know some kind of rule is firing, but I can't understand why or how to stop it.

For example, I create a new low voltage underground conductor line, double click to finish and apply the geometry. Then when I use the attribute pane to add a maximum voltage of 240 volts and click apply, the line jumps a few feet north and disconnects from any vertices it was snapped to. Very frustrating! How can I figure out what is happening here?

All ideas are appreciated. Thank you. 

0 Kudos
9 Replies
gis_KIWI4
Frequent Contributor

@mshanaghan - You could review the rules in Attribute Rules assigned to the layer.
Hopefully they have the key words "240V" or "offset" in the description or where the trigger is = Insert

gis_KIWI4_1-1733173970481.png

 

gis_KIWI4_2-1733174000133.png

gis_KIWI4_3-1733174098622.png

 

The other way I thought this might happen is if you have a group template. 
But I don't think it fits what you are describing. 
The offset setting group template would trigger as soon as you finish drawing the geometry.

  

 

 

0 Kudos
mshanaghan
Frequent Contributor

Thank you for the thoughtful response. I'm now realizing that this jumping behavior is happening with every attribute edit I make, with every feature in the electric utility network. I don't think there would be any attribute rules set up in the default configuration that would change geometry if, for example, the owner of an asset is changed. Which leads me to believe this is not an attribute rule problem. 

Can you think of any other reasons that this may be happening? Maybe a coordinate system problem? 

0 Kudos
gis_KIWI4
Frequent Contributor

Your case is very peculiar! Hard to say where the issue might be originating from.
This is what I would do - 

1) Check if this behavior is also affecting other users (I am assuming you are using Enterprise?)
2) Check is this behavior is confined in your project, try creating a new one
3) Try copying the data to a mobile GDB and see if the see issue is resolved.

If nothing else works raise a ticket with support. 
All the best, I look forward to hearing back if you find the cause of this issue 🙂 

0 Kudos
mshanaghan
Frequent Contributor

Thank you!

Yes, I'm using Enterprise. I'm working with the utility network via a feature service hosted on our enterprise portal. The data is stored in an enterprise geodatabase on SQL server.

This jumping behavior is affecting the one other editor of the service. (We use branch versioning.)

When I copied the data from the enterprise geodatabase into a mobile geodatabase, the behavior did not persist. What does this tell me?

0 Kudos
gis_KIWI4
Frequent Contributor

I am afraid it still doesn't narrow it down much. So some editors have this issue and some don't? 
That would suggest the problem is localized to your ArcGIS Pro projects.

If all the users were facing it I would think there would be an attribute rule firing on update on the egdb side.

Did you have a chance to save a new project using the same feature service? It will be interesting to issue carries over.


I must say I have never experienced this and hence the trial and error solutions. Are you able to screenshot a video that might give us some ideas.

What version of ArcPro and Enterprise are you using? 
Are you using anything like ArcFM on top to do the editing? 

0 Kudos
mshanaghan
Frequent Contributor

All users are having this issue. When I added the service to a new Pro project, the behavior persisted. 

I'm using Enterprise portal 11.3 and Pro version 3.4.0. I'm not using any editing software beyond Pro. 

Check it out in the attached video, crazy! This happens with every feature in every layer and every attribute.

0 Kudos
gis_KIWI4
Frequent Contributor

@mshanaghan - I must say this is looking more like a attribute rule problem. 
Can you confirm if it's moving  in the same direction and always by the same distance? 

If that's the case then you could use the Export Attribute Rules GP tool search for the distance. 
Use any layer that you are facing that issue with. 

The last thing I can think of is to use Portal Logs. 
Set the logging to verbose and check the logs at the timestamp this is happening. 

 

mshanaghan
Frequent Contributor

Thank you for these suggestions. I can confirm that the features always jump 1.27 meters in the same direction. There is nothing in the exported attribute rule file that contains these measurements. 

I've opened a support case with esri. I'll post here with a solution if they find one! Thanks for all of your help.

gis_KIWI4
Frequent Contributor

@mshanaghan - were you able to find the root cause for the Curious Case of the Moving Features 😃

0 Kudos