<?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 10.1 Geocode Service Issues in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/10-1-geocode-service-issues/m-p/613359#M34595</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Is anyone else trying to use a geocode service in 10.1? Are you having any issues? I currently have 3 issues. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Batch Geocoding wioth a composite locator only uses one of the locators unless using a single line input.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) When batch goecoding over 2000 records your ID numbers must start at 1. If you start at 0 the resulting IDs do not match. Less than 2000 you can use 0 or 1 and it doesn't matter&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Reversegeocoding does not work. Using the same input as the Reverse Geocode API sample I get a message that the query inputs are incorrect. It looks like the API reference for reverse geocoding did not change from 10.0 to 10.1. Did the parameter input format change?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd be curious to see if anyone else is having similar issues.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Sep 2012 14:02:36 GMT</pubDate>
    <dc:creator>BrianLeroux</dc:creator>
    <dc:date>2012-09-18T14:02:36Z</dc:date>
    <item>
      <title>10.1 Geocode Service Issues</title>
      <link>https://community.esri.com/t5/data-management-questions/10-1-geocode-service-issues/m-p/613359#M34595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Is anyone else trying to use a geocode service in 10.1? Are you having any issues? I currently have 3 issues. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Batch Geocoding wioth a composite locator only uses one of the locators unless using a single line input.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) When batch goecoding over 2000 records your ID numbers must start at 1. If you start at 0 the resulting IDs do not match. Less than 2000 you can use 0 or 1 and it doesn't matter&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Reversegeocoding does not work. Using the same input as the Reverse Geocode API sample I get a message that the query inputs are incorrect. It looks like the API reference for reverse geocoding did not change from 10.0 to 10.1. Did the parameter input format change?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd be curious to see if anyone else is having similar issues.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2012 14:02:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/10-1-geocode-service-issues/m-p/613359#M34595</guid>
      <dc:creator>BrianLeroux</dc:creator>
      <dc:date>2012-09-18T14:02:36Z</dc:date>
    </item>
  </channel>
</rss>

