I created what I thought was a basic AGOL feature layer of lines representing projects and their attributes. I set up a webmap for my coworkers and they have been happy with it. There are a few editing features not available through the webmap (such as merging separate features into one multi-part feature, or creating a multipart feature in the first place), but I have used ArcGIS Pro for these edits. Recently, we added projects in a neighboring state, but when I went to edit these in ArcGIS Pro, I get a "The coordinates or measures are out of bounds" error. I am at my wits end on this, as I can't understand how a feature layer can't be used to for lines that are far enough away to be in different states; seems like a basic ask.
I do not want to recreate the layer as I already put a lot time into developing the Form and the webmap. I have tried to overwrite the layer (https://doc.arcgis.com/en/arcgis-online/manage-data/manage-hosted-feature-layers.htm#ESRI_SECTION1_1...) but I don't get the option even though I turned off 'sync' and 'enable data change tracking'.
Any ideas on how to get a AGOL feature layer to be editable even when features are hundreds of miles away from each other?
Hi,
Have you checked what coordinate system you used for that layer? projected or geographic one?
Regarding overwriting the layer, have you tried to publish/overwrite it from ArcGIS pro?
Good luck!
Cheers,
Thanks e_mcc. The coordinates system is just whatever AGOL defaults to, I don't think it gives you a choice when creating. I was about to try overwriting via ArcGIS Pro (attempted this the other day but the tool is confusing, and acts like you want all your arcpro layers to replace the one you selected), but when I loaded the data into a new project to perform the overwrite, I found what was causing the editing out-of-bounds error. For some reason, each problematic feature had a single vertex with an M value set to some Engineering value (i.e. -2.335425253 E24) instead of 0 or -100000. I have no idea why there are different M values across the features, or how a vertex got the weird value, as I don't think anything we've done would use or edit M values (they aren't a useful thing for my data). Anyway, for posterity for anyone whose data randomly throws errors during editing, check your M values.
If you still have the issue and you don't want to lose your map settings, I would suggest the following:
Cheers,
E.