<?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 Re: Runtime API Renders Fewer Features than JavaScript in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/runtime-api-renders-fewer-features-than-javascript/m-p/674804#M8471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Runtime does support paging the result of queries.&amp;nbsp; Works fine if you are doing a query&amp;nbsp;and want to draw or do something with the results.&amp;nbsp; If the feature layer in question is simply a layer in a webmap that you are loading, it won't&amp;nbsp;help you.&amp;nbsp; More info here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.esri.com/thread/228285-queryfeaturesasync-paging"&gt;https://community.esri.com/thread/228285-queryfeaturesasync-paging&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Jul 2019 17:42:35 GMT</pubDate>
    <dc:creator>Mike_Quetel</dc:creator>
    <dc:date>2019-07-24T17:42:35Z</dc:date>
    <item>
      <title>Runtime API Renders Fewer Features than JavaScript</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/runtime-api-renders-fewer-features-than-javascript/m-p/674803#M8470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have had several customers complaining that our app is rendering fewer features than they see in AGOL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a screenshot of both at the same extent and scale.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/453232_pastedImage_1.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-2 jive-image" src="https://community.esri.com/legacyfs/online/453245_pastedImage_2.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way we can configure the Runtime SDK to render more features, like the ArcGIS JavaScript API does? It looks like the JS API chunks up the requests into tiles, so that even though you can still hit the 1000 feature limit for a given tile, because it's broken up into tiles, you get more features overall. To our customers, this looks like a bug in our software.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2019 20:33:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/runtime-api-renders-fewer-features-than-javascript/m-p/674803#M8470</guid>
      <dc:creator>JeffSiemens</dc:creator>
      <dc:date>2019-07-16T20:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime API Renders Fewer Features than JavaScript</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/runtime-api-renders-fewer-features-than-javascript/m-p/674804#M8471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Runtime does support paging the result of queries.&amp;nbsp; Works fine if you are doing a query&amp;nbsp;and want to draw or do something with the results.&amp;nbsp; If the feature layer in question is simply a layer in a webmap that you are loading, it won't&amp;nbsp;help you.&amp;nbsp; More info here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.esri.com/thread/228285-queryfeaturesasync-paging"&gt;https://community.esri.com/thread/228285-queryfeaturesasync-paging&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jul 2019 17:42:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/runtime-api-renders-fewer-features-than-javascript/m-p/674804#M8471</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2019-07-24T17:42:35Z</dc:date>
    </item>
  </channel>
</rss>

