Presented by: Ben Zietlow and Lindsey Danielson

1. ArcSDEGeodatabase Design for the Zoning Department. Presented by: Ben Zietlow and Lindsey Danielson

2. Introduction • An ArcSDEgeodatabase provides a uniform framework for data storage and management • Through the use of subtypes and domains data can be categorized and maintain rules for data integrity. • Relationship classes help ensure referential integrity. • Multiple users can edit data, and different versions can be made. • Archiving provides the user a way to record and access changes made to data in a versioned geodatabase. (ESRI 2011)

3. Methods • Collection of Background Information • Conceptual / Logical Design • PhysicalDesign • Created zoning feature classes, subtypes, and domains in ArcCatalog and imported it into ArcGISDiagrammer • Created remaining schema in ArcGISDiagrammer • Published as an .xml document • Imported into ArcSDEgeodatabase • Connected to SQL Sever Management Studio

4. Methods The geodatabase will be organized into different feature classes or tables. • Zoning • Parcels • Zone codes • Violations • Owners • Planners • Zoning Change Requests • Approved Zoning Changes • Denied Zoning Changes • Tabled Zoning Changes • Clerks Zoning Records Feature Classes Tables

5. Zoning Feature Class Zoning_ID = Primary Key Parcel_ID= Foreign Key This feature class has been assigned subtypes with in the zone_code field. Each subtype has also been given a coded value domain, which is chosen in the landuse_code field

6. Parcel Feature Class Parcel_ID = Primary Key Owner_ID = Foreign Key This feature class contains each parcels’ spatial and tabular information. It was created because a parcel may have multiple zoning codes but only one parcel number per zoning polygon. An alternative to our current design would be to combined the parcels feature class with the zoning feature class by utilizing concatenated fields this would change some relationships

7. Zone Codes Table Zone Codes Table Primary Key = Violation_ID Foreign Key = Zoning_ID Zone_Code Planner_ID Primary Key = Zone_Code

8. Owners Table Planners Table Primary Key = Planner_ID Primary Key = Owner_ID

9. Zoning Change Requests Clerk Zoning Changs Primary Key = Entry_ID Foreign Key = Clerk_ID Recorder_ID Primary Key = Request_ID Foreign Key = Zoning_ID Planner_ID

10. Approved Zoning Changes Denied Zoning Changes Tabled Zoning Changes Primary Key = Tabled_ID Foreign Keys = Request_IDPlanner_ID Primary Key = Denied_ID Foreign Key = Request_ID Zoning_ID Planner_ID Primary Key = Approved_ID Foreign Keys = Request_IDZoning_IDPlanner_ID These three tables share the same coded value domain for the Planner_ID field

11. Relationships

12. Versioning • Versioning allows simultaneous multiuser editing in ArcSDEgeodatabases (Law 2010). • “A version of the geodatabase represents an alternative, independent, persistent view of the geodatabase” (Law 2010). The zoning department and the GIS department can edit data at the same time. Once finished the versions can be reconciled and saved.

13. ArcGISDiagrammer Pros and Cons

14. References ESRI. 2011. Web Based Help. Online. (http://resources.arcgis.com/content/web-based-help). Accessed 22 June 2011. Law, D. 2010. Versioning 101: essential information about ArcSDEgeodatabases. ArcUserWinter 2010. p 42-48.