<?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 Relationship class questions in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631808#M97119</link>
    <description>&lt;P&gt;I am working to create a database and I need help figuring out the correct type of relationship classes to make.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am tracking activity of ships. I have a point feature class of ports, a table of ship names, and I was hoping to create a table of activities ( unload, load up, cargo type ect) of these ships.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My original thought was to create a one to many between the ports and ships, then another one to many between the ships and activities.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But this results in duplicate ship records in the ship table.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this solvable with a many to many between the ports and ships maybe?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any feedback&lt;/P&gt;</description>
    <pubDate>Wed, 09 Jul 2025 21:46:35 GMT</pubDate>
    <dc:creator>matchjohn</dc:creator>
    <dc:date>2025-07-09T21:46:35Z</dc:date>
    <item>
      <title>Relationship class questions</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631808#M97119</link>
      <description>&lt;P&gt;I am working to create a database and I need help figuring out the correct type of relationship classes to make.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am tracking activity of ships. I have a point feature class of ports, a table of ship names, and I was hoping to create a table of activities ( unload, load up, cargo type ect) of these ships.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My original thought was to create a one to many between the ports and ships, then another one to many between the ships and activities.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But this results in duplicate ship records in the ship table.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this solvable with a many to many between the ports and ships maybe?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any feedback&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jul 2025 21:46:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631808#M97119</guid>
      <dc:creator>matchjohn</dc:creator>
      <dc:date>2025-07-09T21:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: Relationship class questions</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631889#M97131</link>
      <description>&lt;P&gt;What is the relationship between ports and ships?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Does a ship have a "home" port it should be linked to?&lt;UL&gt;&lt;LI&gt;If so, you could do this with a 1:M relationship class between ports (origin) and ships (destination).&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Should a ship be linked to every port it's ever been to?&lt;UL&gt;&lt;LI&gt;If so, you could do this with a M:M relationship class (origin and destination doesn't matter so much here).&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Should a ship be linked to every port it's ever been to, but with dates of arrival and departure?&lt;UL&gt;&lt;LI&gt;If so, you could do this with a M:M relationship class, with attribution on the relationship class.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;An attributed relationship class could also be an option for associating activities with a port/ship pairing.&amp;nbsp; If it had dates in there, you could even have activities associated with each visit.&lt;/P&gt;&lt;P&gt;Another consideration is how this will be used downstream.&amp;nbsp; For example, will this be used in Pro exclusively?&amp;nbsp; Will it be used with mobile or web applications in ArcGIS Online?&amp;nbsp; That kind of thing is important to consider because M:M relationships and attributed relationships may not do what you need in those contexts, support for them isn't as good as it is for simple 1:1/1:M relationships in my experience.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 08:26:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631889#M97131</guid>
      <dc:creator>MobiusSnake</dc:creator>
      <dc:date>2025-07-10T08:26:18Z</dc:date>
    </item>
    <item>
      <title>Re: Relationship class questions</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631909#M97132</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/743327"&gt;@matchjohn&lt;/a&gt;&amp;nbsp;The modelling can be simplified : does ships have to be related to ports? what is the use case? what will you gain from this? perhaps eliminate this relationship; port at which ship is docked can be a domain list.&amp;nbsp;&lt;SPAN&gt;one to many between the ships and activities makes sense.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Great suggestions&amp;nbsp; from&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/115587"&gt;@MobiusSnake&lt;/a&gt;&amp;nbsp;. agree that M:M&amp;nbsp;relationship maintenance has some overhead.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 11:11:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/relationship-class-questions/m-p/1631909#M97132</guid>
      <dc:creator>AyanPalit</dc:creator>
      <dc:date>2025-07-10T11:11:32Z</dc:date>
    </item>
  </channel>
</rss>

