Presentation is loading. Please wait.

Presentation is loading. Please wait.

Enterprise Addressing System. Spatial Data for the Enterprise (Imagery, Demographic Data) Enterprise Addressing System.

Similar presentations


Presentation on theme: "Enterprise Addressing System. Spatial Data for the Enterprise (Imagery, Demographic Data) Enterprise Addressing System."— Presentation transcript:

1 Enterprise Addressing System

2 Spatial Data for the Enterprise (Imagery, Demographic Data) Enterprise Addressing System

3 Why an Enterprise Addressing System (EAS)? Departments are focused on their primary business Addresses critical but secondary Current ad hoc situation leads to inefficiencies and confusion An enterprise solution

4 Current State DBI – Issues permits for an address – new address for a building: $262 – Maintains own address database (AVS) 311 CSC – Creates service request for an address – Maintains own address table DPW – Services requests for Graffiti removal etc.; Issues permits – Maintains own set of address lists and databases Emergency Management – send Fire and Police to address – Maintains own address database Assessor – Appraises property by block and lot – Site address in Parcel Database varies in accuracy TTX, SFMTA, Real Estate, Recreation and Park, etc.

5 EAS is … Funded initially by COIT, now funded by SFGIS Focused solely on address management Shared source of address information Available across departments Easy to use Adopted by DBI (Director Day at COIT 4/14)

6 An address in San Francisco Assessor/Recorder Public Works Parcels (Assessor Parcel Number) Streets (Street Name) Department of Building Inspection Address Number Block 1244 Lot 022 Ashbury St 600 – 698 634 Ashbury St per City Charter

7 Demonstration

8 EAS 1.0 in production (eas.sfgov.org)eas.sfgov.org – Production environment on VMWare – Regularly scheduled load of DBI’s data into EAS – Nightly load of parcels and streets from DPW into EAS – Active Open Source Project (http://code.google.com/eas)http://code.google.com/eas EAS 1.1 – Real-time integration with DBI’s permitting system – MOU/SLA between DT and DBI EAS 1.2 and beyond – Integration with 311 Call Service Center database – Integration with DPW – Integration with other departments – Mail Merge services, etc. – Leverage development work of other municipalities through the EAS Open Source Project – Civic Commons, Code for America, Sacramento, Bellevue, Virginia Beach, San Mateo – Add imagery, building footprints Schedule

9 Questions?

10

11 Esri ELA software* DepartmentsDollar amount of software deployed @ FY10 maintenance prices City Planning $ 169,500 DPH-Env Health $ 39,100 DPH-IT $ 73,500 DPH-SFAIDS Office $ 67,900 DPW-BSM $ 157,500 Emergency Management $ 6,900 Environment $ 1,200 GSA-IT $ 120,000 SFFD $ 45,500 SFMTA - MUNI $ 56,500 SFO $ 60,000 SFUSD $ 15,000 Grand Total $ 812,600 *not including SFGIS

12

13

14 VMware Infrastructure

15 EAS – Cost since Jan 2009 professional services Phase I: $445K (COIT funding) professional services Phase II: $78K (SFGIS funding) hosting services (1) $99K (COIT) hosting services (2) $76K – AppLogic (SFGIS) hosting services (3) $38K – AppLogic > VMWare (SFGIS) hosting services (4) $38K – VMWare (12 months, if needed) (SFGIS) 3D building datasets for entire City: $133k (COIT) Total: $907K, COIT $677K, SFGIS $230K Staff time – 1 full-time developer – Project management, DBA, Operations – DBI developer time

16 Extract - Transform - Load ETL app_db map_db Public Works parcels streets Assessor ownership Enterprise GIS transform

17 Messaging Web Services Address System Web Server look up change notification Client System Web Server

18 Data Model

19 Feature: Simple, Adequate Data Model – parcel to address (many to many) apartments timeshares multi-story condos tenants in common – mailing address – status (official, provisional...)

20 Feature: Address Lineage Main Street 150 152154156 change request

21 Feature: Address Point Table street based geo-coding falls short Main Street 198100 101 199 Add Constraint: point must be within a polygon

22 Why Open Source?

23 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)

24 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

25 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

26 EAS - 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.)

27 Why use the Cloud? Necessity Opportunity to evaluate offerings Virtualized Data Center Development to QA to Production Hot Site potential


Download ppt "Enterprise Addressing System. Spatial Data for the Enterprise (Imagery, Demographic Data) Enterprise Addressing System."

Similar presentations


Ads by Google