LGIM Relationships

[PatrickLockwitz]

In the following post, http://forums.arcgis.com/threads/83079-Sign-Inventory-in-LGIM-anyone?highlight=relationships, Scott talks about possibly flattening out the GDB schema or joining feature classes in ArcMap instead of using relationship classes because of the multiple relationships while also factoring in the use of the data set for end user applications.

In looking at the FacilitySite FC, the description mentions creating other tables in order to relate other information that doesn't fit in the simple attribute table of the FacilitySite FC.  If I were to create another stand alone table that would contain data like that found in the GovServiceInfo - TABLE, what is the suggestion for setting up the relationship?  In ArcMap using a Join?  With a relationship class?  Something else?

Also, in looking at the Workspace-Level tables, some have "__ATTACH - Table" at the end of the name.  In looking at the tables in ArcCatalog, it looks like some tables are attached to other tables using relationship classes, I'm looking at the Parks & Rec tables, but then the tables don't appear to be attached to any spatial features, points or polygons.  How do these disparate data sources connect to each other?  Is there a diagram that shows all of this that you can provide?

Taking it even further, if I have to set up all these complex relationships and maintain them, does it make sense to completely get rid of the FacilitySite FC as ESRI has it set up and break it down further by creating a new FC based on each of the FacilitySite subtypes and add in the fields needed for each particular type of FacilitySite type.  i.e.  I track different attributes for parks, government facilities, nursing homes, retail centers, etc.  In this case, attributes for a particular site type would be internally related to 1 FC with no external  relationship type functionality at all.

[KATIEATKINSON]

Why has nobody replied? I am also interested in a map or outline showing what data, in what format, is joined by what means to what and why. Plus what to do if your data is not in that format? I have base parcels in polygon and Assessor's, PW, Election data in SQL databases. Are there docs for the maps on where to start to bring in our data?

[ScottOppmann]

I would encourage you to start with the maps and layers required for each editing map or application, then use the map dictionaries to determine which feature classes and tables are required in the underlying local government information model.  The map dictionaries will also indicate whether map joins are used, or whether actual geodatabase relationship classes are used.  The Data Dictionary provided with the information model provides additional detail on each feature class, relationship class, etc. 

To address the specific questions about the _Attach tables in the GDB.  These are system defined tables for features that have geodatabase attachments (photos, videos, etc.) enabled.  From a schema perspective, you don't need to worry about these. 

The FacilitySite features are modeled in a consolidated way because these features are used in a variety of applications throughout local government and a simple flexible design is necessary for an enterprise implementation.  We have also found that many of the attributes for the core features (government buildings, parks, schools, etc.) are the same; and the detailed characteristics for each of these features (park services, hours of operation, contact information, etc.) can be maintained independently and then related to the features in a focused map or application.

So in summary, don't start with the data model and the details within. Start with the maps and apps and then work your way back in to the specific features in the information model.   Here is more information that may be helpful.