<?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: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339569#M3980</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reporting this issue -&amp;nbsp;the team is investigating in our current sprint (I've linked your Support BUG report above to our internal development&amp;nbsp;issue).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Jan 2019 02:15:55 GMT</pubDate>
    <dc:creator>MichaelBranscomb</dc:creator>
    <dc:date>2019-01-09T02:15:55Z</dc:date>
    <item>
      <title>ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339567#M3978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;[EDIT2]&amp;nbsp; Esri tech support has logged&amp;nbsp;&lt;STRONG&gt;BUG-000118762&lt;/STRONG&gt; in reference to this issue&lt;/P&gt;&lt;P&gt;[EDIT]&amp;nbsp; Visual studio project added, which demonstrates issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This behavior is with .NET Runtime 100.4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When querying a service feature table using a complex geometry, the &lt;STRONG&gt;QueryFeatureAsync()&lt;/STRONG&gt; method throws an error (shared below)&amp;nbsp;which indicates that the Uri is too long.&amp;nbsp; I can regularly run simpler geometries through this code, so my assumption is that there is a problem with the volume of information being handled when this method URL encodes and/or attempts to post to the server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The query parameters sent into the query is straightforward, consisting of the geometry and&amp;nbsp;a spatial relationship of intersects.&amp;nbsp; As I mentioned, the geometry is a complex one. Something like a 244 part polygon consisting of about 24,500 points.&amp;nbsp; I've attached the JSON for this polygon below as &lt;EM&gt;buffers.json&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can point the query with that geometry at this endpoint:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.portlandmaps.com/arcgis/rest/services/Public/Basemap_Color_Complete/MapServer/8" title="https://www.portlandmaps.com/arcgis/rest/services/Public/Basemap_Color_Complete/MapServer/8" rel="nofollow noopener noreferrer" target="_blank"&gt;Layer: Taxlots (ID: &lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt;&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an aside, this issue sounds alot like &lt;A href="https://stackoverflow.com/questions/38440631/httpclient-the-uri-string-is-too-long" rel="nofollow noopener noreferrer" target="_blank"&gt;a post on stack overflow&lt;/A&gt;&amp;nbsp;related to System.Net.Http.HttpClient. I don't see anything actionable in there since the exception is being thrown out of an Esri method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;&lt;CODE&gt;HResult: -2146233033
Message: "Invalid URI: The Uri string is too long."
Source: "Esri.ArcGISRuntime"
StackTrace:

&amp;nbsp;&amp;nbsp; at Esri.ArcGISRuntime.ArcGISException.HandleCoreError(CoreError error, Boolean throwException)
&amp;nbsp;&amp;nbsp; at RuntimeCoreNet.GeneratedWrappers.Interop.CheckError(IntPtr errorHandle, Boolean throwOnFailure, GCHandle wrapperHandle)
&amp;nbsp;&amp;nbsp; at RuntimeCoreNet.GeneratedWrappers.CoreTask.Get()
&amp;nbsp;&amp;nbsp; at Esri.ArcGISRuntime.Internal.CoreTaskExtensions.TaskCompletedCallbackHandler`1.OnCompleted(Object sender, EventArgs e)
--- End of stack trace from previous location where exception was thrown ---
&amp;nbsp;&amp;nbsp; at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
&amp;nbsp;&amp;nbsp; at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
&amp;nbsp;&amp;nbsp; at Esri.ArcGISRuntime.Internal.CoreTaskExtensions.TaskCompletedCallbackHandler`1.&amp;lt;CreateInternal&amp;gt;d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
&amp;nbsp;&amp;nbsp; at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
&amp;nbsp;&amp;nbsp; at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
&amp;nbsp;&amp;nbsp; at Esri.ArcGISRuntime.Data.ServiceFeatureTable.&amp;lt;QueryFeaturesInternal&amp;gt;d__45.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
&amp;nbsp;&amp;nbsp; at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
&amp;nbsp;&amp;nbsp; at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
&amp;nbsp;&amp;nbsp; at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
&amp;nbsp;&amp;nbsp; at MapWorks.LayerSelection.SelectableItem.&amp;lt;ExecuteQuery&amp;gt;d__35.MoveNext() in C:\GitHub\MapWorks\MapWorks\LayerSelection.xaml.cs:line 1285‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your assitance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Dec 2021 16:03:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339567#M3978</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2021-12-11T16:03:23Z</dc:date>
    </item>
    <item>
      <title>Re: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339568#M3979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've also opened a tech support case:&amp;nbsp;Esri Case #02231288&amp;nbsp; for this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2018 16:32:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339568#M3979</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2018-12-10T16:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339569#M3980</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reporting this issue -&amp;nbsp;the team is investigating in our current sprint (I've linked your Support BUG report above to our internal development&amp;nbsp;issue).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2019 02:15:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339569#M3980</guid>
      <dc:creator>MichaelBranscomb</dc:creator>
      <dc:date>2019-01-09T02:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339570#M3981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/4061"&gt;Michael Branscomb&lt;/A&gt;‌&amp;nbsp; We talked at the recent dev summit and I was inquiring if this issue was fixed in the upcoming release.&amp;nbsp; The scope of this issue was that a query parameter object is provisioned with either a very complex geometry or a where clause that is very long such as an IN statement with many values.&amp;nbsp; Each scenario could cause the error reported here.&amp;nbsp; Thanks for the update.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Mar 2019 17:43:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339570#M3981</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2019-03-12T17:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339571#M3982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has this been confirmed to be fixed in 100.5?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2019 19:52:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339571#M3982</guid>
      <dc:creator>DavidHaines</dc:creator>
      <dc:date>2019-05-07T19:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339572#M3983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It seems to be fixed in my use cases which were: query via geometries with very high vertex counts as well as where clauses such as [field] IN (1,2,3,....1000,1001)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2019 19:58:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339572#M3983</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2019-05-07T19:58:52Z</dc:date>
    </item>
    <item>
      <title>Re: ServiceFeatureTable.QueryFeaturesAsync()  error - Invalid URI: The Uri string is too long</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339573#M3984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes - this was fixed in v100.5.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 May 2019 16:38:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/servicefeaturetable-queryfeaturesasync-error/m-p/339573#M3984</guid>
      <dc:creator>MichaelBranscomb</dc:creator>
      <dc:date>2019-05-08T16:38:19Z</dc:date>
    </item>
  </channel>
</rss>

