<?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 How do I model uncommon attributes in a UN Feature Class in Electric Questions</title>
    <link>https://community.esri.com/t5/electric-questions/how-do-i-model-uncommon-attributes-in-a-un-feature/m-p/219158#M197</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi UN Technical Support,&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Please advice me on best practice to model common and uncommon attributes under the same Utility Network Feature Class.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;For example, I have devices A and B where there are common and uncommon attributes between the two devices (A and B) and I am to model both devices under the single UN Feature Class, how best I can deal with the uncommon attributes in such a way that I don't end up creating a long list of attributes that would not relate to ALL the devices under the Utility Network Devices Feature Class.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Kindly find attached snapshot and observe my vertical scrollbar that shows a very very long attribute list i have added because of the uncommon attributes in the individual features. Currently stuck and thought it wise to seek for technical advice.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Thank you for advice&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Oct 2018 15:19:18 GMT</pubDate>
    <dc:creator>Isaac_NewtonKissiedu</dc:creator>
    <dc:date>2018-10-29T15:19:18Z</dc:date>
    <item>
      <title>How do I model uncommon attributes in a UN Feature Class</title>
      <link>https://community.esri.com/t5/electric-questions/how-do-i-model-uncommon-attributes-in-a-un-feature/m-p/219158#M197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi UN Technical Support,&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Please advice me on best practice to model common and uncommon attributes under the same Utility Network Feature Class.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;For example, I have devices A and B where there are common and uncommon attributes between the two devices (A and B) and I am to model both devices under the single UN Feature Class, how best I can deal with the uncommon attributes in such a way that I don't end up creating a long list of attributes that would not relate to ALL the devices under the Utility Network Devices Feature Class.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Kindly find attached snapshot and observe my vertical scrollbar that shows a very very long attribute list i have added because of the uncommon attributes in the individual features. Currently stuck and thought it wise to seek for technical advice.&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Thank you for advice&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Oct 2018 15:19:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/electric-questions/how-do-i-model-uncommon-attributes-in-a-un-feature/m-p/219158#M197</guid>
      <dc:creator>Isaac_NewtonKissiedu</dc:creator>
      <dc:date>2018-10-29T15:19:18Z</dc:date>
    </item>
  </channel>
</rss>

