<?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: IdentifyLayersAsync tolerance in pixel unit is bad in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/identifylayersasync-tolerance-in-pixel-unit-is-bad/m-p/1276981#M11769</link>
    <description>&lt;P&gt;Identify typically is a user-interaction where you "click" the map, which is why this value is in pixels, so you can always use the same physical screen tolerance without having to adapt to the current map scale.&lt;BR /&gt;If you want to do a spatial query with a physical geometry, use the query operations on the feature tables.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2023 16:42:27 GMT</pubDate>
    <dc:creator>dotMorten_esri</dc:creator>
    <dc:date>2023-04-10T16:42:27Z</dc:date>
    <item>
      <title>IdentifyLayersAsync tolerance in pixel unit is bad</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/identifylayersasync-tolerance-in-pixel-unit-is-bad/m-p/1276927#M11767</link>
      <description>&lt;P&gt;I get the following exception when I zoom in due to the tolerance is in pixel unit.&amp;nbsp;&amp;nbsp; It should be the map unit.&amp;nbsp; Can you change?&lt;/P&gt;&lt;P&gt;Exception: Esri.ArcGISRuntime.ArcGISRuntimeException: Invalid argument: 'tolerance' must be greater than or equal to zero and less than or equal to 100.&lt;BR /&gt;, Exception Message: Invalid argument: 'tolerance' must be greater than or equal to zero and less than or equal to 100.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 13:56:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/identifylayersasync-tolerance-in-pixel-unit-is-bad/m-p/1276927#M11767</guid>
      <dc:creator>noodle</dc:creator>
      <dc:date>2023-04-10T13:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: IdentifyLayersAsync tolerance in pixel unit is bad</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/identifylayersasync-tolerance-in-pixel-unit-is-bad/m-p/1276981#M11769</link>
      <description>&lt;P&gt;Identify typically is a user-interaction where you "click" the map, which is why this value is in pixels, so you can always use the same physical screen tolerance without having to adapt to the current map scale.&lt;BR /&gt;If you want to do a spatial query with a physical geometry, use the query operations on the feature tables.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 16:42:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/identifylayersasync-tolerance-in-pixel-unit-is-bad/m-p/1276981#M11769</guid>
      <dc:creator>dotMorten_esri</dc:creator>
      <dc:date>2023-04-10T16:42:27Z</dc:date>
    </item>
  </channel>
</rss>

