drc_

Feature geometry vs Popup graphic geometry

Discussion created by drc_ on Nov 15, 2013
Latest reply on Nov 20, 2013 by drc_
What is the popup doing to my geometry? It appears to be rounding coordinates to whole numbers. I'm using JSAPI 3.7.

When I retrieve a feature from the server via a query the geometry looks like this:

{"paths":[[[2254219.6886,9307566.589100003],[2314023.484099999,9268954.027900003],[2407213.6961999983,9205433.806999996]]],"spatialReference":{"wkid":102100,"latestWkid":3857}}


...but when I use the default Popup behavior (i.e. user clicks on feature, feature is associated with Popup and highlighted with a graphic) the graphic.geometry for the exact same feature looks like this:

{"paths":[[[2254220,9307567],[2314023,9268954],[2407214,9205434]]],"spatialReference":{"wkid":102100,"latestWkid":3857}}


...in other words the Popup graphic is rounding the coordinates to whole numbers. Why? Can I override this somehow? I want to use the geometry of popup.getSelectedFeature() as a spatial parameter for a query to another service but don't get the expected results because of rounded coordinates.

Outcomes