<?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 address locator and coded domains in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/address-locator-and-coded-domains/m-p/576245#M32644</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The data I am using to build an address locator is structured in a standard relational database model structure. Some of the fields that I need to provide e.g. Left City or Place are stored as codes in my feature class that point to an external lookup table which stores the real text name. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I do not want to flatten the data as the geodatabase is used for other tasks, is updated fairly regularly and is a large dataset. Coded domains are not recognised by the address locator and simply return the original code in the search results, which is not very useful. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I thought about using views but unfortunately this is not possible using a file geodatabase - only when using SDE. Do I have any other options, without flattening the data using a python script? (This is what I am trying to avoid).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 May 2014 16:33:14 GMT</pubDate>
    <dc:creator>AndyJones</dc:creator>
    <dc:date>2014-05-16T16:33:14Z</dc:date>
    <item>
      <title>address locator and coded domains</title>
      <link>https://community.esri.com/t5/data-management-questions/address-locator-and-coded-domains/m-p/576245#M32644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The data I am using to build an address locator is structured in a standard relational database model structure. Some of the fields that I need to provide e.g. Left City or Place are stored as codes in my feature class that point to an external lookup table which stores the real text name. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I do not want to flatten the data as the geodatabase is used for other tasks, is updated fairly regularly and is a large dataset. Coded domains are not recognised by the address locator and simply return the original code in the search results, which is not very useful. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I thought about using views but unfortunately this is not possible using a file geodatabase - only when using SDE. Do I have any other options, without flattening the data using a python script? (This is what I am trying to avoid).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2014 16:33:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/address-locator-and-coded-domains/m-p/576245#M32644</guid>
      <dc:creator>AndyJones</dc:creator>
      <dc:date>2014-05-16T16:33:14Z</dc:date>
    </item>
  </channel>
</rss>

