1

I have a multipart polyline in an ArcGIS Pro 2.9.2 FGDB feature class (NAD83 UTM):

enter image description here

I can set the M-values to the cumulative distance of the line by using the Set As Distance tool (setting "Starting M" to zero):

enter image description here

That works as expected. Part #2's M-values are in the correct order (ascending).

enter image description here

However, if I do a different test, the results are unexpected:

  • Drop the measures.

  • Try a slightly different feature:

    Change the X-coordinate of part #1, vertex 2...from 130 meters to 135 meters.

  • Re-do the test:

    Set the M-values to the cumulative distance of the line by using the Set As Distance tool (setting "Starting M" to zero).

Now, part #2's M-values are in the incorrect order (descending):

enter image description here


Why are the M-values in the incorrect order? (descending)

I would expect the M-value order to be the same as the vertex index's order (ascending).

3
  • 1
    I would fire this off to ESRI support, looks like a bug.
    – Hornbydd
    Commented Mar 22, 2022 at 11:27
  • 1
    @Hornbydd - Esri confirmed it's a defect: BUG-000148390.
    – User1974
    Commented Apr 11, 2022 at 15:43
  • 2
    Good! Well done, rattle that cage! Rage against the machine and all that.
    – Hornbydd
    Commented Apr 11, 2022 at 16:53

1 Answer 1

0

Esri says a defect: BUG-000148390.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.