"Layer did not draw completely" unless editing is enabled with NaN m-values

1661
6
Jump to solution
10-08-2020 12:29 PM
WillHouston
New Contributor III

EDIT: NaNs for m-values seem to be the culprit. After moving the features to a class with m-values disabled, everything is drawing properly.

The feature class that is drawing correctly is the route layer for a (now deprecated) linear referencing system. All the m-values are correct. I moved away from the LRS for our street model because ArcGIS Pro lacks good editing features for LRSs, but I left the m-values. After making edits to the routes, there were vertices with NaN m-values. Those NaN m-values seem to cause this drawing issue.

Original post:

I have a layer of street centerlines that is not drawing beyond the 200ft scale in an AGOL web map when editing is turned off or in a view layer. It does draw at small scales when editing is enabled. In the Visualization tab for the feature layer, the entire layer is drawn correctly. I have tried the layer as multipart and single part features. I have tried turning on optimized layer drawing (and it has been multiple hours since, so I assume that is complete). As single part there are 531 features with a total of 24,932 vertices, and the largest single line vertex count is 725.

A few months back I uploaded a very similar feature layer (the layer's local source was corrected, and that corrected layer is the one causing problems) with nearly identical features. This layer has 391 multipart features with 24,796 total vertices and a single line vertex count max of 1,047. This layer draws at all scales and never had optimized layer drawing enabled. This layer works with editing on or off and has a functional view layer.

Have I misconfigured my feature layer somehow?

Here is a map with both the view layers: https://arcg.is/1WXWCr 

Tested in Chrome and Edge.

0 Kudos
1 Solution

Accepted Solutions
WillHouston
New Contributor III

That was causing the issue with mine. You can try running the feature class to feature class script with "Output has M Values" as "Disabled" under the Environments tab (as at the bottom of the attached image) and publishing the result to AGOL.

 

View solution in original post

6 Replies
WillHouston
New Contributor III

Here's some more information I left out. The feature class is in a file geodatabase, and I published it to AGOL in ArcGIS Pro v2.6.2. I have also used the "feature class to feature class" tool to copy the troublesome features to a different file geodatabase with no luck. I also tried copying just the geometry to a new feature class with no luck.

0 Kudos
ReidReininger
New Contributor

I am having the exact same problem as you; almost same number of features, posted from a GDB through ArcGIS Pro, visualization works but not in a map unless editing is enabled. I was searching for solutions through Google today and came across your post. I guess it's time for us to open a help ticket.

0 Kudos
WillHouston
New Contributor III

I opened up a ticket yesterday. I have a call with ESRI support today. I'll keep you posted.

0 Kudos
WillHouston
New Contributor III

Reid, does your layer have m-values, and are any of those m-values NaN for your features?

0 Kudos
ReidReininger
New Contributor

Yes to both of your questions, is that what is causing the issue? I actually opened up a help ticket this morning as well, they weren't sure what the problem was on the first phone call and are currently researching further.

0 Kudos
WillHouston
New Contributor III

That was causing the issue with mine. You can try running the feature class to feature class script with "Output has M Values" as "Disabled" under the Environments tab (as at the bottom of the attached image) and publishing the result to AGOL.

 

View solution in original post