Federated Data Model Follow-Up DC GIS Steering Committee - PDF document

Federated Data Model Follow-Up DC GIS Steering Committee • Distributed Email – January 2005 4-28-2005 • Discussed at Steering Committee • Included Data Listing by Agency • Activities: – Some Agency Feedback – EMA and OCTO reviewed the Agency Data List – Full Data Catalog is on DC GIS Intranet (dcgis.in.dc.gov) – Currently has 830 Datasets, 200 for distribution Barney Krucoff, GIS Director Office of The Chief Technology Officer Barney.Krucoff@dc.gov Slide 1 Intranet Data Catalog Federated Data Model Review S t a n d a r d s s e r u d e c o r P Slide 2 Agency Action Items Federated Data Model Follow-Up Review • Review and comment on the Federated 1 • Anticipated changes/additions to the Data Model document Federated Model – Accuracy and Precision • Identify a primary GIS contact(s) at the – Snapbase agency – Cluster Tolerance – Metadata • Coordinate the layers that each agency – Topology will own and maintain and determine – Cartography (print and web) update cycles for each – Data Catalog • Maintain a consolidated geospatial data maintenance plan Slide 4 Slide 5 Slide

Updated Data Data Update - OwnerPoints • Dun and Bradstreet 12/2004 • CAMA 12/2004 • Incorporates ITS Public Extract • Charter School 1/2005 • New Table Schema • Public School 1/2005 • Impacts Applications and Services • School Attendance Zone 2/2005 • 205 Columns, down from 254 • Metro Station 2/2005 • Available as OwnerPt_42705 and SalePt_42705 • Metro Entrance 2/2005 • Currently updating Metadata • CAMA 1/2005 • Owner Point (draft) 4/2005 • Sales Point (draft) 4/2005 Slide 6 Slide 7 New Data Current Data Update • Street Centerline • Polling Place • Military Areas • Places of Worship 10/2004 • Embassy • Parking Meter • Points of Interest • Library 11/2004 • DC Quad • Property Lines CAD – Update • Dun and Bradstreet • Owner Point 4/2005 • Sale Point » May 2005 publication Slide 8 Slide 9 Data Update - Street Centerline Geographic Information System & 2 • Before - 5 layers (Street, Alley, Service Enterprise System Architecture Road, Drive, and Ramp) • Now - One Consolidated Layer • Extracted from DDOT geodatabase • Updated Table Schema • Includes DDOT Centerline Updates Zhen Lo, GIS Systems Architect Slide 10 Slide

Central GIS System (Currently) Presentation • Review of the current enterprise architecture • Improved access and visibility of geospatial data within the District • Support federated data model • Establish a framework for data sharing (ESRI) • One stop for geospatial data, services, and • Enabled District employees to use GIS support technology via the Intranet • Increase reliability and performance of the GIS • Formed a GIS user community for infrastructure collaboration Slide 12 Slide 13 The Approach Issues to resolve • Difficulty performing data maintenance • Use the ESRI Enterprise suite software – Data access • Build upon current data standards – Data integration • Adopt OCTO server consolidation approach • Communication between data provider(Agency) and host (OCTO) • Work with Agencies independently to comply with architecture framework to enable data and • Turn around time for expanding data inventory services sharing • Lack of application framework or standards Slide 14 Slide 15 Enterprise Architecture Requirements Data 3 • Establish data standards • Frequency of updates • Metadata standards Portal Federated Data Model • Common interface or methodology to services • Method of service discovery Application Development Framework • Development standards, coding languages common interfaces System Infrastructure • Servers, networks, software Slide 16 Slide 17 Slide

Data Interoperability Methods GeoDatabase Design Process Used by OCTO and Agencies: • Conceptual Design – Data sources, metadata, application – Scale, spatial reference, symbology • Logical Design – Business rules, relationships, database schema – Feature classes, topology, domains • Physical Design – Actual tables, spatial objects, and views Slide 18 Slide 19 DCOZ Feature Dataset Example Central GIS Geodatabases Central GIS Portal Zoning Feature dataset Topology Syncrohization Planning ArcSDE + Oracle Spatial Enforced Zoning layer topology rules for Default Default version data precision and business Syncrohization rules DDOT Zone overlay Metadata Catalog Web Service Catalog Default version Syncrohization Posted version for data display/ Zoning Syncrohization data distribution Posting version GENERATION 1 Syncrohization Versioned layer for editing Editing version Upload and Manage Parks Disconnected GENERATION 2 editing version Version checked ArcSDE Editing out into personal geodatabase for Versioned Database offline editing (contractor) Slide 20 Slide 21 DC GIS Portal and User Experience 4 Distributed Users Search and find GIS data/ services 2 Gateway to GIS Services The DC GIS Portal DCGIS Portal Connect, download, and use 3 GIS services Connect to agency GIS services 3 GIS Catalog 1 1 Central GIS Agency Agency Publish data, services and document GIS GIS In GIS catalog Datasets Datasets Maps Maps Locators Locators Slide 22 Slide 23 Slide

Central GIS Portal Application Framework Slide 25 DC GIS Portal Framework PlumTree Portal Enterprise System Infrastructure Slide 26 Slide 27 Current DC GIS Production Systems Proposed System Hardware 2TB Hitachi SAN 5 DC WAN Intranet Internet DCGuide EIC www.dc.gov rrc.dc.gov Gigabit Fibre Switch Internet Content Switch Z Z Content Switch M M D D 4 IBM 445 x series Servers 2 1 OpenPower Web2 web3 Web1 web4 C C D D WAN Switch Optical Fibre connection O O OpenPower Db1 Db2 db3 DMZ Switch OpenPower Oracle Replication service for EIC features table only OpenPower 4 x 3.0 GHz Xeon processors 16 GB RAM 2 x 146.8 GB SCSI 3 Hard Disk Slide 28 Slide 29 Slide

Virtual Server Concept Proposed DCGIS Enterprise System VMOTION IMS App IMS App server server SDE Application 3DGIS AD/DNS WIN2K WIN2K WIN2K OS WIN2K WIN2K 3DGIS AD/DNS ArcServer SDE Application Application IMS App IMS App server server WIN2K WIN2K WIN2K3 WIN2K OS OS WIN2K WIN2K Virtual Layer 2TB SAN CPU NIC RAM CPU NIC RAM CPU NIC RAM Server Server Server Physical Architecture Slide 30 Slide 31 Summary: New GIS Enterprise Architecture • A framework for GIS application development, data sharing, and agency cooperation • Continue to expand and improve the District’s geospatial data and services – Increased flexibility – Increased reliability – Increased in performance and quality of service Slide 32 Slide 33 Agency GIS Strategic Plan Outline 6 • Mission • GIS-related Agency Goals (FY2005 budget • Agency GIS Goals Agency GIS Strategic Planning • Applications Process • FY 2005 Projects • Accomplishments NOTE: THIS IS OCTO’S FIRST DRAFT OF A GIS STRATEGIC PLAN FOR YOUR AGENCIES. PLEASE CHANGE THIS AS YOU WISH TO MAKE IT YOURS. We think the focus on using GIS to achieve this year’s agency goals can increase agency awareness of GIS Slide 35 Slide

Inventories Data • Datasets are listed in the inventory if your agency is an Automated Routing Originator, GIS Lead, or Cooperating Agency Streamlines Bulk Trash • Please review, correct, and add to the inventory Collection in Washington DC GIS Applications & Software Inventory • Inventory A lists relevant ESRI GIS software licenses and maintenance agreements • Inventory B is for GIS applications or customizations of standard ESRI packages Office of Information 37 Technology Services Slide 36 Without Computerized Routing Project Background 1) Citizens call for bulk trash collection 2) From 200 to 300 citizen appointments through the appointments are assigned Mayor’s Call Center at 727-1000. The Department of Public Works (DPW) is developing an for collection each day, and an appointment sheet for automated routing and reporting system based on each one is printed from the Geographic Information System (GIS) and Routing Hansen System for SWMA. software; 3) Appointment sheets are distributed by hand DPW successfully implemented computerized bulk trash to 10 different crews for collection (approximately 20 – 30 appointment sheets per routing in the period from November 2003 to crew) This step adds a day to the lag between a November 2004; citizen’s call and their bulk collection. Now DPW is seeking to automate the steps to make the process user friendly and to extend it to other 5) There is an average of 6 days operations. 4) At times crews have difficulty finding between a citizen’s call and the addresses and the the distribution of stops collection of their bulk trash. among the crews is not always efficient. This limits the number of stops they can get Slide 38 to per day. 39 With computerized routing, the 200 – 300 appointments are delivered from the Hansen Each crew receives a succinct checklist of their stops…… System as computer files and are assigned to crews in moments. 7 Slide 40 Slide 41 Slide