Select to view content in your preferred language

Error message when calculating geometry

2213
8
05-17-2022 04:07 AM
ClayTurner
Emerging Contributor

I get an error message (see attachment) when attempting to calculate the geometry for certain point features when using ArcPro. Other point features will calculate geometry successfully.

0 Kudos
8 Replies
JohannesLindner
MVP Alum

Please share a screenshot of your tool parameters, that might make troubleshooting easier.

 

certain point features

Do you mean feature classes, as in "feature class 1 works, feature class 2 does not"? Or do you mean actual features as in "this point works, but this point in the same feature class does not"?

 

Things to check off the top of my head:


Have a great day!
Johannes
0 Kudos
ClayTurner
Emerging Contributor

Thanks for the reply. Different feature classes. Meters and fittings work when calculating geometry, but valves and hydrants won't. Another oddity is that this error only occurs when using Pro. All features geometry can be calculated in ArcMap. 

I don't have write access to the feature classes, but our DBA is looking into the RepairGeometry tool you suggested.

0 Kudos
RobertBorchert
Honored Contributor

compress your database and try again.

0 Kudos
ClayTurner
Emerging Contributor
Thank you. We'll give that a try
0 Kudos
RobertBorchert
Honored Contributor

We used to get an issue every now and then with ArcMAP where it would create phantom rows in the database.  i.e. when you delete a feature it actually retains it in the database until you compress it.

That phantom row would sometimes cause erroneous issues such as this.

Our SDE Enterprise Databases are now set to compress every day sometime after midnight. 

I would also check to see if you have any multipart features. 

0 Kudos
ClayTurner
Emerging Contributor
Thanks so much for your reply. We’re having our DBA schedule the database compression for this evening.
0 Kudos
RobertBorchert
Honored Contributor

In the mean time perhaps you could export the feature class to a different database and see if the error persists.

Sometimes when I have had an issue I have exported the feature class and truncated the original and re-loaded it to solve a problem 

However, not always a possible or viable option. 

0 Kudos
ClayTurner
Emerging Contributor
We may try that also.
Thanks again for your assistance.
0 Kudos