<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ArcGIS Server 11.5 query problem in ArcGIS REST APIs and Services Questions</title>
    <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1700578#M5111</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m experiencing what appears to be inconsistent spatial query behavior in ArcGIS Server 11.5 against a polygon feature class stored in SQL Server.&lt;/P&gt;&lt;P&gt;I would like to know whether this is expected behavior, a known limitation, or potentially a bug.&lt;/P&gt;&lt;P&gt;Environment:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ArcGIS Server / Enterprise 11.5&lt;/LI&gt;&lt;LI&gt;SQL Server enterprise geodatabase&lt;/LI&gt;&lt;LI&gt;Layer is a normal polygon feature class (not a query layer/view)&lt;/LI&gt;&lt;LI&gt;Query performed against /MapServer/{layerId}/query&lt;/LI&gt;&lt;LI&gt;Spatial relation: esriSpatialRelIntersects&lt;/LI&gt;&lt;LI&gt;Geometry type: esriGeometryMultipoint&lt;/LI&gt;&lt;LI&gt;Requests are sent using POST&lt;/LI&gt;&lt;LI&gt;Spatial index rebuilt&lt;/LI&gt;&lt;LI&gt;Statistics updated&lt;/LI&gt;&lt;LI&gt;Feature class extent recalculated&lt;/LI&gt;&lt;LI&gt;Service restarted&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;The issue:&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Individual point queries work correctly.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;However, when multiple points are combined into a single multipoint geometry, ArcGIS Server starts returning inconsistent results.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The strange part is:&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Adding additional points can REMOVE previously returned OBJECTIDs from the result set.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://servername/webgis/rest/services/Int/NG_Intern/MapServer/188/query" target="_blank" rel="noopener"&gt;https://servername/webgis/rest/services/Int/NG_Intern/MapServer/188/query&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Post body:&lt;/P&gt;&lt;P&gt;{&lt;BR /&gt;"where": "1&amp;gt;0",&lt;BR /&gt;"geometry": {&lt;BR /&gt;"points": [&lt;BR /&gt;[518458.872, 6091340.096],&lt;BR /&gt;[529008.6611, 6096497.8727],&lt;BR /&gt;[518340.468, 6091537.346]&lt;BR /&gt;],&lt;BR /&gt;"spatialReference": {&lt;BR /&gt;"wkid": 25832&lt;BR /&gt;}&lt;BR /&gt;},&lt;BR /&gt;"geometryType": "esriGeometryMultipoint",&lt;BR /&gt;"inSR": 25832,&lt;BR /&gt;"spatialRel": "esriSpatialRelIntersects",&lt;BR /&gt;"units": "esriSRUnit_Meter",&lt;BR /&gt;"outFields": "objectid",&lt;BR /&gt;"returnGeometry": true,&lt;BR /&gt;"returnTrueCurves": false,&lt;BR /&gt;"returnIdsOnly": false,&lt;BR /&gt;"returnCountOnly": false,&lt;BR /&gt;"returnZ": false,&lt;BR /&gt;"returnM": false,&lt;BR /&gt;"returnDistinctValues": false,&lt;BR /&gt;"returnExtentOnly": false,&lt;BR /&gt;"sqlFormat": "none",&lt;BR /&gt;"returnUniqueIdsOnly": false,&lt;BR /&gt;"featureEncoding": "esriDefault",&lt;BR /&gt;"f": "json"&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;Example 1 — returns 3 polygon features:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "points": [&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518458.872&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091340.096&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;529008.6611&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6096497.8727&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518340.468&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091537.346&lt;/SPAN&gt;&lt;SPAN&gt;]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  ],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "spatialReference": {&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    "wkid": &lt;/SPAN&gt;&lt;SPAN class=""&gt;25832&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  }&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;Example 2 — same points + one additional point:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "points": [&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518458.872&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091340.096&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;529008.6611&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6096497.8727&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518340.468&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091537.346&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;521703.189&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6102741.1&lt;/SPAN&gt;&lt;SPAN&gt;]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  ],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "spatialReference": {&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    "wkid": &lt;/SPAN&gt;&lt;SPAN class=""&gt;25832&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  }&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;This second query returns only 1 polygon feature???&lt;/P&gt;&lt;P&gt;The polygons returned from Example 1 disappear completely in Example 2, even though all original points are still included.&lt;/P&gt;&lt;P&gt;This seems logically incorrect - or am I missing something?&lt;/P&gt;&lt;P&gt;I can also reproduce similar behavior using multipart polygon geometries (rings) instead of multipoints.&lt;/P&gt;&lt;P&gt;Additional observations:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Results appear sensitive to point order&lt;/LI&gt;&lt;LI&gt;Individual point queries always return correct polygons&lt;/LI&gt;&lt;LI&gt;Problem only occurs with combined geometries&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Has anyone seen similar behavior with:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ArcGIS Server MapServer query engine&lt;/LI&gt;&lt;LI&gt;SQL Server spatial backend&lt;/LI&gt;&lt;LI&gt;multipoint or multipart geometries&lt;/LI&gt;&lt;LI&gt;candidate pruning / spatial indexing&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I’m especially interested in whether:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;this is a known bug/limitation of MapServer queries&lt;/LI&gt;&lt;LI&gt;there are known bugs related to spatial decomposition multipoint geometries&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Thu, 07 May 2026 15:50:29 GMT</pubDate>
    <dc:creator>LarsSøe</dc:creator>
    <dc:date>2026-05-07T15:50:29Z</dc:date>
    <item>
      <title>ArcGIS Server 11.5 query problem</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1700578#M5111</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m experiencing what appears to be inconsistent spatial query behavior in ArcGIS Server 11.5 against a polygon feature class stored in SQL Server.&lt;/P&gt;&lt;P&gt;I would like to know whether this is expected behavior, a known limitation, or potentially a bug.&lt;/P&gt;&lt;P&gt;Environment:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ArcGIS Server / Enterprise 11.5&lt;/LI&gt;&lt;LI&gt;SQL Server enterprise geodatabase&lt;/LI&gt;&lt;LI&gt;Layer is a normal polygon feature class (not a query layer/view)&lt;/LI&gt;&lt;LI&gt;Query performed against /MapServer/{layerId}/query&lt;/LI&gt;&lt;LI&gt;Spatial relation: esriSpatialRelIntersects&lt;/LI&gt;&lt;LI&gt;Geometry type: esriGeometryMultipoint&lt;/LI&gt;&lt;LI&gt;Requests are sent using POST&lt;/LI&gt;&lt;LI&gt;Spatial index rebuilt&lt;/LI&gt;&lt;LI&gt;Statistics updated&lt;/LI&gt;&lt;LI&gt;Feature class extent recalculated&lt;/LI&gt;&lt;LI&gt;Service restarted&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;The issue:&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Individual point queries work correctly.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;However, when multiple points are combined into a single multipoint geometry, ArcGIS Server starts returning inconsistent results.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The strange part is:&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Adding additional points can REMOVE previously returned OBJECTIDs from the result set.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://servername/webgis/rest/services/Int/NG_Intern/MapServer/188/query" target="_blank" rel="noopener"&gt;https://servername/webgis/rest/services/Int/NG_Intern/MapServer/188/query&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Post body:&lt;/P&gt;&lt;P&gt;{&lt;BR /&gt;"where": "1&amp;gt;0",&lt;BR /&gt;"geometry": {&lt;BR /&gt;"points": [&lt;BR /&gt;[518458.872, 6091340.096],&lt;BR /&gt;[529008.6611, 6096497.8727],&lt;BR /&gt;[518340.468, 6091537.346]&lt;BR /&gt;],&lt;BR /&gt;"spatialReference": {&lt;BR /&gt;"wkid": 25832&lt;BR /&gt;}&lt;BR /&gt;},&lt;BR /&gt;"geometryType": "esriGeometryMultipoint",&lt;BR /&gt;"inSR": 25832,&lt;BR /&gt;"spatialRel": "esriSpatialRelIntersects",&lt;BR /&gt;"units": "esriSRUnit_Meter",&lt;BR /&gt;"outFields": "objectid",&lt;BR /&gt;"returnGeometry": true,&lt;BR /&gt;"returnTrueCurves": false,&lt;BR /&gt;"returnIdsOnly": false,&lt;BR /&gt;"returnCountOnly": false,&lt;BR /&gt;"returnZ": false,&lt;BR /&gt;"returnM": false,&lt;BR /&gt;"returnDistinctValues": false,&lt;BR /&gt;"returnExtentOnly": false,&lt;BR /&gt;"sqlFormat": "none",&lt;BR /&gt;"returnUniqueIdsOnly": false,&lt;BR /&gt;"featureEncoding": "esriDefault",&lt;BR /&gt;"f": "json"&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;Example 1 — returns 3 polygon features:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "points": [&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518458.872&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091340.096&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;529008.6611&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6096497.8727&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518340.468&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091537.346&lt;/SPAN&gt;&lt;SPAN&gt;]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  ],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "spatialReference": {&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    "wkid": &lt;/SPAN&gt;&lt;SPAN class=""&gt;25832&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  }&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;Example 2 — same points + one additional point:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "points": [&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518458.872&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091340.096&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;529008.6611&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6096497.8727&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;518340.468&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6091537.346&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    [&lt;/SPAN&gt;&lt;SPAN class=""&gt;521703.189&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt;6102741.1&lt;/SPAN&gt;&lt;SPAN&gt;]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  ],&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  "spatialReference": {&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    "wkid": &lt;/SPAN&gt;&lt;SPAN class=""&gt;25832&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;  }&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;This second query returns only 1 polygon feature???&lt;/P&gt;&lt;P&gt;The polygons returned from Example 1 disappear completely in Example 2, even though all original points are still included.&lt;/P&gt;&lt;P&gt;This seems logically incorrect - or am I missing something?&lt;/P&gt;&lt;P&gt;I can also reproduce similar behavior using multipart polygon geometries (rings) instead of multipoints.&lt;/P&gt;&lt;P&gt;Additional observations:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Results appear sensitive to point order&lt;/LI&gt;&lt;LI&gt;Individual point queries always return correct polygons&lt;/LI&gt;&lt;LI&gt;Problem only occurs with combined geometries&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Has anyone seen similar behavior with:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ArcGIS Server MapServer query engine&lt;/LI&gt;&lt;LI&gt;SQL Server spatial backend&lt;/LI&gt;&lt;LI&gt;multipoint or multipart geometries&lt;/LI&gt;&lt;LI&gt;candidate pruning / spatial indexing&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I’m especially interested in whether:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;this is a known bug/limitation of MapServer queries&lt;/LI&gt;&lt;LI&gt;there are known bugs related to spatial decomposition multipoint geometries&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2026 15:50:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1700578#M5111</guid>
      <dc:creator>LarsSøe</dc:creator>
      <dc:date>2026-05-07T15:50:29Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS Server 11.5 query problem</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1701143#M5113</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/2620"&gt;@TanuHoque&lt;/a&gt;&amp;nbsp;Should I report this as a potential bug?&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 07:50:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1701143#M5113</guid>
      <dc:creator>LarsSøe</dc:creator>
      <dc:date>2026-05-11T07:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS Server 11.5 query problem</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1701189#M5114</link>
      <description>&lt;P&gt;You could publish the same service using a different back-end data source, e.g., file GDB instead of SQL Server, to see if the issue is isolated to a particular type of data source.&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 14:55:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1701189#M5114</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2026-05-11T14:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS Server 11.5 query problem</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1701363#M5115</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/137017"&gt;@LarsSøe&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;yes, pls open a ticket and we will take a look at this. I can't say much with the trying with the exact data. Thank you!&lt;/P&gt;&lt;P&gt;Also I do agree with Joshua. If you don't mind, please give this a try with file gdb and see how it behaves.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 23:59:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-server-11-5-query-problem/m-p/1701363#M5115</guid>
      <dc:creator>TanuHoque</dc:creator>
      <dc:date>2026-05-11T23:59:00Z</dc:date>
    </item>
  </channel>
</rss>

