I'm looking at the new Electric Utility Network Foundation Naperville demo data and have noticed
- Some relationship classes under the feature dataset and some are not
- The tables become versioned when the dataset is versioned. Assume this is done due to the relationship class
- There are 2 relationship classes doing the same thing
Without knowing what tools are available to manage the data in these related tables as I can't find any documentation on these, is there standard/preferred way of how this should be structured as the current layout of the feature classes/tables looks misleading?
My original thought would be to have all feature classes, relationship classes and tables that participate in the UNF would be placed all under the feature dataset.
Based on what is currently there, can anybody expand the capability with user defined tables & relationship classes?