AnsweredAssumed Answered

Why does Pro send geometry queries out of WGS84 valid ranges?

Question asked by jkerr@marklogic.com on Sep 3, 2018
Latest reply on Sep 4, 2018 by jkerr@marklogic.com

I am developing a feature service and testing with Pro and am seeing invalid geometries sent from in from Pro. When zoomed out to a world-level view, the following "geometry" parameter is passed in as a feature service query:

     geometry:

      { rings:

         [ [ [ -170.471965544496, -170.471965544496 ],

             [ -170.471965544496, 170.471965544496 ],

             [ 170.471965544496, 170.471965544496 ],

             [ 170.471965544496, -170.471965544496 ],

             [ -170.471965544496, -170.471965544496 ] ] ],

        spatialReference: { wkid: 4326, latestWkid: 4326 } },

     geometryType: 'esriGeometryPolygon',

     spatialRel: 'esriSpatialRelIntersects'

 

I also noticed that if I turn off caching for the layer, it still sends in an invalid envelope like this

     geometry:

      { xmin: -157.59328548468832,

        ymin: -157.59328548468838,

        xmax: 157.59328548468847,

        ymax: 157.59328548468844,

        spatialReference: { wkid: 4326, latestWkid: 4326 } },

     geometryType: 'esriGeometryEnvelope',

     spatialRel: 'esriSpatialRelIntersects'

This is with a viewport with the following extents:

 

xmin = -134.8305848

ymin = -82.5060047

xmax = 81.7476774

xmax = 79.7760266

 

Can you explain why Pro would pass in points outside the WGS84 valid range for both of these case?

Outcomes