<?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: Using LocatorTask.GeoCodeAsync to query a Pro locator for sub addresses in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/using-locatortask-geocodeasync-to-query-a-pro/m-p/1193936#M11150</link>
    <description>&lt;P&gt;I published the locator to an ArcGis 10.8.1 server and tried both single line and multiple line inputs on the published service also.&amp;nbsp; I have no trouble getting expected results for a standard address, but I have yet to find a way to submit an input that returns a subaddress from the published locator service.&amp;nbsp; I had some scenarios with a pro locator service where I needed to use a search extent, so I tried that, but it does not make a difference in these cases.&lt;/P&gt;&lt;P&gt;I have tried numerous variations on both single line and multiple line inputs with no luck.&lt;/P&gt;&lt;P&gt;It certainly appears that esri has neglected to support subaddresses in Pro locators via either ArcGis Server 10.8.1 or ArcGisRuntime 100.14.&amp;nbsp; Is that the case?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jul 2022 14:10:53 GMT</pubDate>
    <dc:creator>NWSCAD4</dc:creator>
    <dc:date>2022-07-20T14:10:53Z</dc:date>
    <item>
      <title>Using LocatorTask.GeoCodeAsync to query a Pro locator for sub addresses</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/using-locatortask-geocodeasync-to-query-a-pro/m-p/1193651#M11148</link>
      <description>&lt;P&gt;I created a point address locator in ArcGis Pro 2.9.&amp;nbsp; I am able to use the locator tab to query for and find sub address locations using my locator.&amp;nbsp; But when I try to use the LocatorTask to query for the same sub address locations, using the same single line input, I get no results.&amp;nbsp; I have started trying to use multiple line inputs also, but so far no luck.&amp;nbsp; I am using ArcGisRuntime 100.14 for this test.&lt;/P&gt;&lt;P&gt;I have no trouble finding standard addresses using the locator task, but I have not yet seen it return a subaddress location.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jul 2022 20:29:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/using-locatortask-geocodeasync-to-query-a-pro/m-p/1193651#M11148</guid>
      <dc:creator>NWSCAD4</dc:creator>
      <dc:date>2022-07-19T20:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: Using LocatorTask.GeoCodeAsync to query a Pro locator for sub addresses</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/using-locatortask-geocodeasync-to-query-a-pro/m-p/1193936#M11150</link>
      <description>&lt;P&gt;I published the locator to an ArcGis 10.8.1 server and tried both single line and multiple line inputs on the published service also.&amp;nbsp; I have no trouble getting expected results for a standard address, but I have yet to find a way to submit an input that returns a subaddress from the published locator service.&amp;nbsp; I had some scenarios with a pro locator service where I needed to use a search extent, so I tried that, but it does not make a difference in these cases.&lt;/P&gt;&lt;P&gt;I have tried numerous variations on both single line and multiple line inputs with no luck.&lt;/P&gt;&lt;P&gt;It certainly appears that esri has neglected to support subaddresses in Pro locators via either ArcGis Server 10.8.1 or ArcGisRuntime 100.14.&amp;nbsp; Is that the case?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 14:10:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/using-locatortask-geocodeasync-to-query-a-pro/m-p/1193936#M11150</guid>
      <dc:creator>NWSCAD4</dc:creator>
      <dc:date>2022-07-20T14:10:53Z</dc:date>
    </item>
  </channel>
</rss>

