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

Slides:



Advertisements
Similar presentations
5-1 5 Tour of ArcMap and ArcCatalog ArcGIS for Assessors 1.
Advertisements

KEYS TO SUCCESS DATA PREPARATION AND ORGANIZATION
Intro to ArcMap. What is ArcMap? Accessing ArcMap Data used by ArcMap SymbologyLabelsGraphics Printing/Exporting maps.
Concepts of Maintaining Your Data Simple Ways to Edit Your Data By Lorne Woods.
Using GIS for Utility Mapping and Asset Management Sanitary Sewer, Storm Sewer, and Water Distribution City of Mason City Jessy Willadsen - Mason City.
Intro to ArcGIS for New Users. ArcGIS Desktop Advanced GeoprocessingArcInfo ArcReader Data Access Map Viewing Query Advanced EditingArcEditor ArcView.
Annotation & Nomenclature By Corey Fortezzo for PG&G GIS Workshop, 2010.
ISP 121 Access Normalization and Relationships. Normalization Say we’re operating a pet day-care and we need to keep information on our pets/customers.
Technical Support: (989) GIS and Mapping Procedures in ArcMap 9.x Creating an ArcMap Project Editing an ArcMap Project Printing an ArcMap Project.
Modeling Data The Entity Relationship Model (ER) For Database Design.
Entity-Relationship Model and Diagrams (continued)
ArcCatalog and Geodatabases
Motivation for IDEF1X Simplicity Common Standard Useful when relational model is target Air Force 1985 or thereabouts.
©2007 Austin Troy Lecture 7: Introduction to GIS 1.Queries and table operations for a single layer in Arc GIS 2.Intro to queries in Access Lecture by Austin.
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
ArcEditor ArcInfo ArcView Display map, query & analyze spatial relationships, features & attributes Same functions as ArcView, plus abilty to create, &
Introduction To ArcMap ArcMa p. ArcMap is a Map-centric GUI tool used to perform map-based tasks Mapping –Create maps by working geographically and interactively.
Database Relationships Objective 5.01 Understand database tables used in business.
Database Relationships Objective 5.01 Understand database tables used in business.
Indiana University Migrating from AutoCAD to a Geodatabase Theresa Thompson
March 14, 2007 First Steps For Starting Your Parcel Database: Aurora Case Study Indiana GIS Conference Dearborn County GIS Ileana Abot.
FINDING LOST CUSTOMERS Mike Morris Rick Ehlin City of Noblesville Utility IGIC Conference 2008.
GIS Concepts ‣ What is a table? What is a table? ‣ Queries on tables Queries on tables ‣ Joining and relating tables Joining and relating tables ‣ Summary.
Attribute Data in GIS Data in GIS are stored as features AND tabular info Tabular information can be associated with features OR Tabular data may NOT be.
The Attribute Table! Without the attribute table, a polygon is just a polygon, a point is a point The attribute table defines what points, lines, or polygons.
Creating the Leased Site database This will be a database that has: Leased Site ID Parent Parcel ID Township Range Section Etc. Some Counties have the.
How does a community maintain a storm
XP Chapter 2 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Building The Database Chapter 2 “It is only the farmer.
Database Relationships. Types of Relationships One to one – Person to Driver’s License, Country to President, Person to Social Security Number (in theory)
Practical Applications for Highway Infrastructure and Asset Management Prepared by: Steven J. Hook, Noble County GIS Coordinator 101 N Orange St. Courthouse,
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Data Modelling – ERD Entity Relationship Diagram’s Entity Relationship Diagrams and how to create them. 1.
Threats Database V4 Model Geodatabase Relation Class Creation and Data Population June 25, 2007 Marlene McKinnon, GIS Specialist.
Introduction In ArcGIS, there are three basic data structures:
Exploring Microsoft Access Chapter 4 Relational Databases, External Data, Charts, and the Switchboard.
Microsoft Access 2003 Define some key Access terminology: Field – A single characteristic or attribute of a person, place, object, event, or idea. Record.
Major parts of ArcGIS ArcView -Basic mapping, editing and Analysis tools ArcEditor -all of ArcView plus Adds ability to deal with topological and network.
RELATIONSHIPS Generally there are two main database types: flat-file and relational.
Geodatabase Relationships & Relationship Classes GIS 458 Spring 2006 Larry Clamp.
GIS in Water Resources Consortium Attaching Behavior to Objects and Programming in the Geodatabase Tom Wesp, AICP Henry Hagemeier ESRI San Antonio.
Intro to GIS and ESRI Trainers: Randy Jones, GIS Technician, Douglas County Jon Fiskness, GISP GIS Coordinator, City of Superior.
Sewer System Geodatabase Adding line and point features.
Chapter 8. ATTRIBUTE DATA INPUT AND MANAGEMENT
Introduction to Databases Trisha Cummings. What is a database? A database is a tool for collecting and organizing information. Databases can store information.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Introduction to ArcGIS
Matt Eitrem GIS Coordinator City of Ashland Wisconsin.
The Fellowship of Asset Management By: Mike Morris and Rick Ehlin.
Relational Database. Database Management System (DBMS)
Wausau Department of Public Works - GIS Division Application of GIS Technology to Municipal Utility Operations Developing a Digital Inventory for Water,
Microsoft Access Intro Class 6 Relationships.
® Microsoft Access 2010 Tutorial 9 Using Action Queries and Advanced Table Relationships.
Enhancing Forms with OLE Fields, Hyperlinks, and Subforms – Project 5.
ArcCatalog and Geodatabases Francisco Olivera, Ph.D., P.E. Srikanth Koka Department of Civil Engineering Texas A&M University.
INFORMATION TECHNOLOGY DATABASE MANAGEMENT. Adding a new field 1Right click the table name and select design view 2Type the field information at the end.
Database revision.
Jozef Kuper.  Describe a Database  Entities  Atributes  Relationships.
ENTITY RELATIONSHIP DIAGRAM ENTITY RELATIONSHIP DIAGRAM IS A SPECIALIZED GRAPHIC THAT ILLUSTRATES THE INTERRELATIONSHIPS BETWEEN ENTITIES IN A DATABASE.
Relational Theory and Design
ArcGIS: ArcCatalog. Agenda The ArcCatalog Interface General ArcCatalog ▫Navigating directories ▫Preview data ▫View metadata Advanced ArcCatalog ▫Modifying.
Lecture 7 Basic GIS Analysis Operations
@2007 Austin Troy Lecture 2: Introduction to the Architecture of ArcGIS By Weiqi Zhou University of Vermont Thanks are due to Prof. Troy, upon whose lecture.
SMALL BUSINESS OPPORTUNITY FORUM Water Department 2015 Capital Program & 2016 Outlook.
Introduction to Geodatabases
Relationship Class What is a Relationship Class (3)
Key Terms Attribute join Target table Join table Spatial join.
Physical Structure of GDB
ArcCatalog and Geodatabases
Introduction To ArcMap
ArcCatalog and Geodatabases
Presentation transcript:

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 Located in Hamilton County Population of 51,969 (2010) Population of 51,969 (2010) Approximately 33 sq mi. 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.” 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.”

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

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

WHY RELATIONSHIP TABLES?

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

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

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

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

Convert existing Access tables to Excel Needed to bring data not currently in GIS in geodatabase tables. Needed to bring data not currently in GIS in geodatabase tables. PumpsPumps HVACHVAC FansFans ValvesValves Access database used by plant operators Access database used by plant operators Needed to convert to excel Needed to convert to excel

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

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. 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.

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

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.

Create.gdb table fields

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

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

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

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

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

Label the relationship from the parent table to the child table Label the relationship from the parent table to the child table Label the relationship from the child table to the parent table Label the relationship from the child table to the parent table

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-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 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. 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.

Select the primary field for the parent table Select the primary field for the parent table Select the foreign key field for the child table Select the foreign key field for the child table

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

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