Naming Conventions for FGDB tables/relationship classes/etc.
Is there any chance that we can get the naming of the related tables, relationship classes, etc cleaned up so that when we look at the fgdb, we can easily see which related tables are actually related? We have a survey that has 3 repeat sections. I have attached a screencap of the fgdb from the survey. When looking at this in catalog, it is almost impossible to determine what is related to what. The survey is called AboveGround_PipelineInspection and the three repeat sections in the survey are dpi_repeat1, dpi_repeat2 & dpi_repeat3.
Typically when a relationship class for attachments is created in a FGDB, the related table name and relationship class name all use the feature class name with the suffix of _ATTACH or _ATTACHREL. It is easy to know which table is related to which feature class.
Thanks,
--gary
