AnsweredAssumed Answered

Multipath pointcount seems to skip number one

Question asked by paul.haakma on May 31, 2016
Latest reply on Jun 10, 2016 by NManocha-esristaff

Can anyone else verify this and is it expected behaviour for some reason or possibly a bug?

 

When creating a multipath object (e.g. a Polyline or a Polygon), the pointcount seems to skip from 0 to 2 without registering the first point.

E.g. I'm drawing a feature by capturing mouse clicks on screen, the empty Polyline json might look like this:

{"paths":[],"spatialReference":{"latestWkid":3857,"wkid":102100}}

Then I click once, and the json stays exactly the same, and the pointcount remains at zero, although that first click *is* stored in the object. Because, then when I click a second time, the json jumps to something like:

{"paths":[[[3944884.454986632,6214117.358888438],[12586059.927814495,5838414.077461138]]],"spatialReference":{"latestWkid":3857,"wkid":102100}}

and the pointcount jumps to 2.

A polygon exhibits similar behaviour.

I discovered this while trying to implement a simple "if pointcount is zero then startpath else lineto" logic. I can get around it easily enough with a separate bool property, something like isFirstPoint and manually set it, but it just seems like something isn't catching that first point properly.

 

Cheers,

-Paul

Outcomes