<?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: Spelling Sensitivity in Geocoding in 911 GIS Questions</title>
    <link>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785057#M208</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are seeing the SOUNDEX algorithm at work, it isn't all that smart, consonants tend to have high value.&lt;/P&gt;&lt;P&gt;It is publicly documented, it will be on the web somewhere.&lt;/P&gt;&lt;P&gt;Technically you can also use the Metaphone function, but I would have to come out of retirement with 9.x locators to figure out how and whether it would help.&lt;/P&gt;&lt;P&gt;You can't use 10.x locators?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Dec 2015 19:01:31 GMT</pubDate>
    <dc:creator>BruceHarold</dc:creator>
    <dc:date>2015-12-03T19:01:31Z</dc:date>
    <item>
      <title>Spelling Sensitivity in Geocoding</title>
      <link>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785056#M207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a question regarding spelling sensitivity as I have experienced something that really has me scratching my head:&amp;nbsp; right now I'm still using 9.3 locators in version 10.0 ArcGIS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically, I use the out of the box defaults for Spelling, Candidate, and Match with a US Streets locator (80, 10, 60).&amp;nbsp; This allows a little wiggle room for spelling and they've always worked for me.&amp;nbsp; At one of the PSAPs I work at, the communities use Presidents names for streets. So&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1600 S Lincoln Ave and&lt;/P&gt;&lt;P&gt;1600 S Monroe Blvd&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are valid addresses&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can misspell Monroe with Monroee or Monre and get a hit.&amp;nbsp; But if I spell Lincoln as Lincon, it won't find it; Lincol works.&amp;nbsp; I've been misspelling others slightly and they seem to work, but LINCON is the holdout.&amp;nbsp; As anyone in 9-1-1 knows, a slight misspelling is easy when you are working a LE channel and it's traffic stop time...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/3241"&gt;Bruce Harold&lt;/A&gt;​&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/43900"&gt;Tim Witt&lt;/A&gt;​&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/8249"&gt;Jeff Ward&lt;/A&gt;​&lt;A href="https://community.esri.com/migrated-users/84114"&gt;Chris Donohue, GISP&lt;/A&gt;​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;​&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 18:54:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785056#M207</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2015-12-03T18:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: Spelling Sensitivity in Geocoding</title>
      <link>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785057#M208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joe&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are seeing the SOUNDEX algorithm at work, it isn't all that smart, consonants tend to have high value.&lt;/P&gt;&lt;P&gt;It is publicly documented, it will be on the web somewhere.&lt;/P&gt;&lt;P&gt;Technically you can also use the Metaphone function, but I would have to come out of retirement with 9.x locators to figure out how and whether it would help.&lt;/P&gt;&lt;P&gt;You can't use 10.x locators?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 19:01:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785057#M208</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2015-12-03T19:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: Spelling Sensitivity in Geocoding</title>
      <link>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785058#M209</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bruce:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm curious - are the 10.x locators using a different process that produces better results?&amp;nbsp; I only know bits and pieces of this....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris Donohue, GISP&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 19:10:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785058#M209</guid>
      <dc:creator>ChrisDonohue__GISP</dc:creator>
      <dc:date>2015-12-03T19:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: Spelling Sensitivity in Geocoding</title>
      <link>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785059#M210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, yes they sure are.&amp;nbsp; Soundex was only ever marginally suitable for English language locators, at 10.x we got real about going global and got into computational linguistics and common spelling issues that crop up in the call center scenario - what people hear versus how it should be spelled.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 19:15:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785059#M210</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2015-12-03T19:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: Spelling Sensitivity in Geocoding</title>
      <link>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785060#M211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm actually doing a beta/pilot project with the CAD vendor and their new 10.2 implementation, so it's on the way; for now I'm stuck with 9.3 locators....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 19:21:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/911-gis-questions/spelling-sensitivity-in-geocoding/m-p/785060#M211</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2015-12-03T19:21:32Z</dc:date>
    </item>
  </channel>
</rss>

