1 / 0

Agenda

Agenda. Getting MAD: San Francisco’s Master Address Database Project. BAAMA January 28, 2010. Jeff Johnson Enterprise GIS Coordinator, Department of Technology, City and County of San Francisco With City since 1993. SFGIS. Getting MAD.

storm
Download Presentation

Agenda

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

  2. Getting MAD: San Francisco’s Master Address Database Project

    BAAMA January 28, 2010
  3. Jeff Johnson Enterprise GIS Coordinator, Department of Technology, City and County of San Francisco With City since 1993 SFGIS
  4. Getting MAD Why the City needs an enterprise-level address system The key data (streets, parcels, and address numbers) Extract, Transform and Load (ETL) Why Open Source Why the Cloud
  5. Why does the City need an enterprise-level address system?
  6. An Address Problem
  7. Assessor/Recorder Board of Supervisors Mayor PUC – Hetch Hetchy District Attorney Public Defender Treasurer/Tax Collector Children, Youth & Families City Attorney Sheriff Juvenile Probation Children and Families Commission Law Library Ethics Commission Department of Emergency Management Police – Office of Citizen Complaints Board of Appeals Art Commission Health Services System Public Utilities Commission Rent Arbitration Board Dept. of Status of Women Human Rights Commission MTA – Parking and Traffic Asian Art Museum Civil Service Commission Environment Taxi Commission Economic & Workforce Development PUC – Wastewater Enterprise Department of Technology Human Resources Retirement System PUC – Water Department Elections Fine Arts Museums Child Support Services War Memorial Department of Building Inspection Administrative Services (Real Estate, et al.) City Planning Adult Probation Police Public Works Controller Port of San Francisco MTA - MUNI Recreation and Park Fire Department Human Services Public Health
  8. many address lists in the City varying needs and uses varying formats, standards, and levels of accuracy or completeness The Situation
  9. Duplicate Address Data Data inconsistencies No central coordination No trust Silos of Data The Issues
  10. “Another silo successfully deployed” – Sam Valdez
  11. What’s needed? MAD Master Address Database system (or EAS) An authoritative, reliable source of common address information Easily maintained and updated Enterprise-based, i.e., benefits more than one department and utilized by all departments Data model incorporates key datasets Web services for application development and system integration at department level
  12. Who’s responsible for what? (according to City Code) Assessor/Recorder Department of Building Inspection Parcels (Assessor Parcel Number) Address Number Public Works Streets (Street Name)
  13. Key Data Elements Assessor/Recorder Block 1244 Lot 022 Parcels (Assessor Parcel Number) 634 Ashbury St Department of Building Inspection Address Number Public Works Ashbury St 600 – 698 Streets (Street Name)
  14. Why SFGIS for MAD? Existing enterprise function Well-developed key datasets Parcels Street Centerline Network Address Points Ability to ramp up ETL from existing data store to MAD
  15. Why SFGIS for MAD? SFGIS: established relationships with departments in place Funding made available through City’s IT steering committee, COIT (Formerly EISPC) Not tied to a particular business process or application or vendor platform
  16. Why Open Source?
  17. Good timing for Open Source Open source standards are prevalent Web Feature Service (WFS), vector Web Map Service (WMS), raster ‘Legacy’ open source paves the path Apache most popular webserver since April 1996 54% websites use Apache today Netcraft Web Server Survey (January 2010)
  18. Maturity of Open Source options Linux ~ University of Helsinki, 1991 Apache ~ NCSA, 1994 PostgreSQL ~ Cal 1970’s PostGIS ~ Refractions Research, 2001 MapServer ~2000 Python ~1667
  19. Cost Software licensing is available to the City free of charge Bulk of funding could go to development work and creating solution Free to share with other organizations (GPL3) What about support? So far, not an issue; in fact a plus. Support options available
  20. MAD Open Source Software PostgreSQL/PostGIS: An Open Source, spatially enabled relational database management system GeoServer: An Open Source application server capable of delivering spatial data using standard formats (such as Web Mapping Services and Web Feature Services) as specified by the Open Geospatial Consortium. OpenLayers: An Open Source JavaScript Library that permits the development of web mapping applications similar to Google Maps Django/GeoDjango: A spatially enabled Open Source web application development framework ExtJS: A modern javascript library (ajax, etc.)
  21. Why the Cloud?
  22. Why use the Cloud? Necessity Opportunity to evaluate offerings Virtualized Data Center Development to QA to Production Hot Site potential
  23. MAD on the Cloud Provider: 3Tera Cloud product: AppLogic Granular security access Granular control over allocated resources Drag and drop interface for designing and deploying all elements (VMs) of an application Grids in Dallas and San Diego
  24. Enterprise Address System (EAS) Roll out to departments for integration Perfect Periodic ETL of key datasets into MAD Work with other municipalities on improvements to system (open source) Migrate to internal cloud Incorporate building geometry
  25. Thank you Jeff.Johnson@sfgov.org
More Related