<?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 Horrible and wrong results from the Address Standardizer!!!! in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/horrible-and-wrong-results-from-the-address/m-p/98409#M5708</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am taking a TIGER2010 Roads file, I am Address Standardizer to use 'US Address - One Range', and then I feed it the 'FULLNAME' field, and set the output to be 'PreDir,PreType,StreetName,SufType,SufDir' and set it to run!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Now; I see results like this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'Muse Rd' &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,null,null,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'W Muse Rd'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,Muse,Rd,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'John Wayne Trl'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,null,null,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'E Schoessler Rd'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,Schoessler,Rd,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'US Rte 12'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = S,Sthy,12,null,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The version 10 engine is butchering PrefixDirection and PrefixType values. I have had a critical bug open for over a year (opened less than a month after 10 shipped) and still can not get any kind of support for this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I can easily repeat this over and over, there is even a NIM for this issue; why can't we get serious support for this major part of the software (yes, you see in the forums major issues across geocoding) and yet we are seeing no traction on the issue.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Aug 2011 00:26:31 GMT</pubDate>
    <dc:creator>DEWright_CA</dc:creator>
    <dc:date>2011-08-24T00:26:31Z</dc:date>
    <item>
      <title>Horrible and wrong results from the Address Standardizer!!!!</title>
      <link>https://community.esri.com/t5/data-management-questions/horrible-and-wrong-results-from-the-address/m-p/98409#M5708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am taking a TIGER2010 Roads file, I am Address Standardizer to use 'US Address - One Range', and then I feed it the 'FULLNAME' field, and set the output to be 'PreDir,PreType,StreetName,SufType,SufDir' and set it to run!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Now; I see results like this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'Muse Rd' &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,null,null,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'W Muse Rd'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,Muse,Rd,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'John Wayne Trl'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,null,null,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'E Schoessler Rd'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = null,null,Schoessler,Rd,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Input = 'US Rte 12'&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output = S,Sthy,12,null,null&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The version 10 engine is butchering PrefixDirection and PrefixType values. I have had a critical bug open for over a year (opened less than a month after 10 shipped) and still can not get any kind of support for this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I can easily repeat this over and over, there is even a NIM for this issue; why can't we get serious support for this major part of the software (yes, you see in the forums major issues across geocoding) and yet we are seeing no traction on the issue.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2011 00:26:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/horrible-and-wrong-results-from-the-address/m-p/98409#M5708</guid>
      <dc:creator>DEWright_CA</dc:creator>
      <dc:date>2011-08-24T00:26:31Z</dc:date>
    </item>
  </channel>
</rss>

