Editing Error in Cemetery Data Management Solution Pro Project

[BrianShepard]

I'm not sure this is a "Solutions" issue, but that's what I'm experiencing this issue with. I'm receiving an error (Move failed. Geometry cannot have Z values.) when trying to move Gravesite features in the Cemetery Data Management Pro Project.

I'm currently adding new gravesite features and have been able to copy/paste special/move and edit attributes to add the new features. However, after they've been moved initially or if I try to move another existing feature, I receive that error and cannot move the feature.

I can, however, move the feature in an ArcGIS Online webmap. What's very odd to me is that the features I've moved in AGO show either in their new position or old position depending on the scale of the Pro Project (i.e., the location of the features changes as I zoom in and out). I've also selected a feature in Pro to see if I could then move it (after it was moved in AGO) and it showed the selection in one spot and the feature in another. Screenshot attached.

The feature service feature class I'm editing is not Z enabled. The features are in the same dataset, so I'm not trying to add features with Z values to a dataset that doesn't allow them. I have closed and reopened the Pro Project. I don't understand why I'm able to move newly created features, but not existing ones.

[DanielWickens]

Hi @BrianShepard -

Can you check to see if the source of the Gravesites feature class in ArcGIS Pro is the same in ArcGIS Online? They should both be using a hosted feature service as the source. Can you also confirm that the settings for Z values is No? Screenshot example attached. 

[BrianShepard]

@DanielWickens Yes. That's the first thing I checked. The edits do show up in both places - if I make an edit in Pro, the AGO webmap shows the same edit; if I move a feature in AGO, it shows up in Pro, but only at some scales.

I checked the Z value setting even though I didn't see how it was possible to copy a feature from the dataset and have it's Z value differ from the feature I was copying. It only made sense to me that this could occur when copying features between datasets with different settings.

[BrianShepard]

It may not be super easy to tell, but at 1:19.06 1-50-72-A shows in it's original location.

At 1:29.77 it is in the location where I moved it in AGO. I don't believe this behavior is consistent (different scales, changes when panned). Seems like it may be cached somewhere.

That issue isn't as much of a priority as being able to edit features in Pro, however.

[DanielWickens]

Hi - That is some behavior I have not seen in the solution before. I'm happy to look more with you if you want to write me at dwickens@esri.com and maybe we can find a time to screenshare later this week?

[BrianShepard · Accepted solution]

I have been able to reproduce and resolve the issue I was having, and it wasn't related to the Cemetery Data Management Solution but converting my point data to polygons to use in the Solution.

I can recrate the issue by creating circular buffers of a point feature class (between 12 and 24 inches). The resultant polygon feature class contains features with 1 vertex or 2 vertices connected by a true curve. Any feature class of this type that I've published to ArcGIS Online creates a situation where features in the hosted feature layer cannot be moved in ArcGIS Pro or ArcGIS Online. Adding a vertex to the features or using the Densify tool on the feature class before publishing to AGO resolves the issue - Densify adds additional vertices to the features and creates straight line segments between them, rather than true curves.