<?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: Alias Table in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/alias-table/m-p/615542#M34731</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Is it possible to set up an alias table so that all possible addresses within a range point to a single address?&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;BR /&gt;150 A st, Fakecity, NY 12345 &lt;BR /&gt;&lt;BR /&gt;If the user type 144 A st, I want the point to show at the same location that 150 A st show. Like wise if they type 149 B st (opposite side of building) should create a point at 150 A st.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The way alias tables have been traditionally used is the reference data is aliased.&amp;nbsp; For example, let's say you have a segment of Main St that is AKA ESRI St; the user can type in 1234 Main St or 1234 ESRI St and get a hit.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think the way you might want to approach your issue is with a series of locators within a composite.&amp;nbsp; Depending how many of these sorts of multi-address-one-location addresses you need to deal with, you'll be spending an awful lot of time building them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Good luck-&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 22 Oct 2011 11:13:48 GMT</pubDate>
    <dc:creator>JoeBorgione</dc:creator>
    <dc:date>2011-10-22T11:13:48Z</dc:date>
    <item>
      <title>Alias Table</title>
      <link>https://community.esri.com/t5/data-management-questions/alias-table/m-p/615541#M34730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Is it possible to set up an alias table so that all possible addresses within a range point to a single address?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;150 A st, Fakecity, NY 12345 &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If the user type 144 A st, I want the point to show at the same location that 150 A st show. Like wise if they type 149 B st (opposite side of building) should create a point at 150 A st.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Oct 2011 14:21:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/alias-table/m-p/615541#M34730</guid>
      <dc:creator>ScottBlankenbeckler</dc:creator>
      <dc:date>2011-10-21T14:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: Alias Table</title>
      <link>https://community.esri.com/t5/data-management-questions/alias-table/m-p/615542#M34731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Is it possible to set up an alias table so that all possible addresses within a range point to a single address?&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;&lt;BR /&gt;150 A st, Fakecity, NY 12345 &lt;BR /&gt;&lt;BR /&gt;If the user type 144 A st, I want the point to show at the same location that 150 A st show. Like wise if they type 149 B st (opposite side of building) should create a point at 150 A st.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The way alias tables have been traditionally used is the reference data is aliased.&amp;nbsp; For example, let's say you have a segment of Main St that is AKA ESRI St; the user can type in 1234 Main St or 1234 ESRI St and get a hit.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think the way you might want to approach your issue is with a series of locators within a composite.&amp;nbsp; Depending how many of these sorts of multi-address-one-location addresses you need to deal with, you'll be spending an awful lot of time building them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Good luck-&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Oct 2011 11:13:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/alias-table/m-p/615542#M34731</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2011-10-22T11:13:48Z</dc:date>
    </item>
  </channel>
</rss>

