1 / 34

A START OF A BEAUTIFUL “RELATIONSHIP”

A START OF A BEAUTIFUL “RELATIONSHIP”. Mike Morris, GISP Rick Ehlin, GISP City of Noblesville Utility IGIC Conference 2011. Let’s Fix Your Relationship. City of Noblesville. Located in Hamilton County Population of 51,969 (2010) Approximately 33 sq mi.

tad
Download Presentation

A START OF A BEAUTIFUL “RELATIONSHIP”

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A START OF A BEAUTIFUL “RELATIONSHIP” Mike Morris, GISP Rick Ehlin, GISP City of Noblesville Utility IGIC Conference 2011

  2. Let’s Fix Your Relationship

  3. City of Noblesville • Located in Hamilton County • Population of 51,969 (2010) • Approximately 33 sq mi. • Noblesville is in the No. 10 spot in the book, “Best Places to Raise Your Family: The Top 100 Affordable Communities in the U.S.”

  4. Noblesville Utilities • Class 4 Wastewater Utility • Approx. 16,400 Customers • 453 Miles of Sanitary and Storm Pipe • 5 million gallons per day • Activated Sludge Plant • 23 Lift Stations

  5. CITYWORKS by Azteca • Cityworks is an Enterprise GIS- based Asset Management System. • It has the ability to do the following: • Work Orders (address or feature specific) • Service Requests (address or feature specific) • Inspections • Storeroom • Manage equipment, contractors, employees, etc.

  6. WHY RELATIONSHIP TABLES?

  7. Modify existing GIS Layers • Add fields (AssetID) to all layers • Breakup layers into individual layers • Sanitary line file had to be split into gravity lines, force mains, interceptor, etc. • Storm structures “Other” file needed to be broken up into flapgate, cleanout, etc.

  8. AssetID field is the field Cityworks uses to link assets (features) to work orders.

  9. Create new GIS layers • Plant Buildings • Fences for plant and lift stations

  10. Attribute fields created • Bldg_Name and AssetID most important • Important to get naming correct

  11. Convert existing Access tables to Excel • Needed to bring data not currently in GIS in geodatabase tables. • Pumps • HVAC • Fans • Valves • Access database used by plant operators • Needed to convert to excel

  12. Access to Excel • All assets in one access database • Data was very inconsistent • Assets needed to be split up into individual types

  13. The naming convention used for the AssetID field was to start with a building code HW (headworks), EF (effluent pump station)….the second part was asset type HVAC, AC (air compressor), PUMP…the final part was a description of equipment type EFFL1 (effluent pump motor #1), RAW4 (raw sewage pump #4). The name that is in the LocationID field is simply the AssetID for our Maint_Building layer.

  14. The RelateID is the AssetID of the “Parent” asset. The “Parent” and “child” analogy was used to clarify relationships between two assets.

  15. In Arc Catalog right click on the file geodatabase (.gdb) you want the new table to be located in and go to new  Table. Once you select this a new box will open up…the naming convention we used to this was maint_air_compressor.

  16. Create .gdb table fields

  17. Load data from excel into .gdb table Right click on the .gdb table you want to load the data into. Select Load  Load Data.

  18. Creating a Relationship Table • Can only be done in ArcInfo or ArcEditor • ESRI help menu is great source

  19. In ArcCatalog, right- click on the geodatabase that contains your tables • Go to New • Click Relationship Class

  20. Name your relationship class • Select the table or feature class that is the origin (parent) • Select the destination table or feature class (child)

  21. Select the type of relationship • We used a Simple (peer to peer) relationship • ESRI gives good definition of both

  22. Label the relationship from the parent table to the child table • Label the relationship from the child table to the parent table

  23. Cardinality • One-to-one: One parent object can relate to only one child object. For example a parcel can only have one legal description • One-to-many: One parent object can relate to multiple child objects. For example a building can have multiple pumps • Many-to-many: One parent object can relate to multiple child objects as well as one child object can relate to multiple parent objects. For example a property can have many owners and an owner can own many properties.

  24. Select the primary field for the parent table • Select the foreign key field for the child table

  25. Examples of relationships • Pump (child) is related to the building (parent)

  26. Motor (child) is related to a pump (child/ parent) which is related to a building (parent)

More Related