april 2009 oracle spatial user conference · oracle spatial user conference april 23, 2009 westin...
TRANSCRIPT
April 2009
Oracle Spatial User
Conference
Oracle Spatial User Conference
April 23, 2009
Westin Tampa Harbour Island Hotel
Tampa, Florida USA
Glenn KronschnablChief Information Officer
First American Spatial
Solutions
April 2009
Oracle Spatial User Conference
Managing
ParcelPoint® on
Oracle Spatial 11g
-Lessons Learned
April 2009
Oracle Spatial User Conference
First American Corporation
• A diversified, international
services provider and a
Fortune 500® company with
over $6.5 Billion in annual sales
• The largest provider of business and real
estate information – First American products
touch over 90% of all property transactions
that occur in the US every year
• First American provides information solutions
to the largest Mortgage and Insurance
companies in the US
First American Spatial
Solutions• Small “Start-up” Division, spun off from Flood
Division along with acquisition of Proxix
Solutions, with vision:
• Focus on spatial data and solutions leveraging
core expertise of accurate location
• Some Products:
• Locational accuracy: ParcelPoint®, PxPoint
• Risk solutions: Flood Risk Score, Flood Model,
Wildfire
• Tax solutions: Premium Tax
“Spatial” is the essential ingredient for our organization to sustain growth
as all new applications feature spatial analysis and analytics
ParcelPoint® Components
•Can be used to attach related information (not necessarily the geometric centroid of the parcel)
•Gives a general point location of the parcel.
1
•Standardized code used by the county to track each property
3
•Latitude and longitude
•Descriptive visual layering
2
•Accurate address processed through our proprietary database
4
ParcelPoint® Coverage & Roadmap
• TO BE ADDED
Technology/Skill Sets
• Develop custom enterprise applications – for
external & internal use
• Oracle 10g, 11g – on-site DBA’s
• BEA WebLogic
• J2EE – on/off-shore development
• GIS
• ESRI Desktop, ArcIMS, ArcSDE – on-site support
• SQL Server
• Geographers/GIS development staff
• Open source (GeoServer, Geotools, uDig)
The Problem
Traditional
GIS Enterprise
Solutions
Silos: Technology & Staff
Spatial
Data
Transactional
Data
Desktop GIS applications
Enterprise applications
Early Solutions: Limited
Success• Early solutions failed - too limited
• How to best move forward?
• Criteria
• Investment, skill sets, enterprise capable (including
mapping), integration of transactional and spatial
data sets, spatial data access
• Option 1: use ESRI SDE (SDE_BINARY) on
top of Oracle 10g
• Option 2: migrate SDE (SQL Server) data to
Oracle 11g Spatial (SDO_GEOM)
Options: Pros/Cons
• Option 1: use ESRI SDE on top of existing
Oracle 10g, using SDE_BINARY format
• Pros: easiest, least costly
• Cons: black box, limited integration between
spatial and business data, results do not take into
account Earth's curvature (less accurate)
• Option 2: migrate SDE (SQL Server) data to
Oracle 11g, using SDO_GEOM
• Pros: better integration, SQL access, leverage
existing Oracle investments, results take into
account the Earth's curvature (more accurate)
• Cons: Oracle spatial learning curve (Dev & DBA’s)
Database Configuration
HP ProLiant DL580 G5 server
32GB RAM
4 quad-core Intel Xeon 2.4GHz
SUSE Linux 10.2 64-bit
Oracle 11.1.0.7 64-bit
HP ProLiant DL580 G5 server
20GB RAM
2 quad-core Intel Xeon 2.4GHz
SUSE Linux 10.2 64-bit
Oracle 11.1.0.7 64-bit
LGWR ASYNC
DataGuard
GigaMAN
Primary
Database
Physical Stand-By
Database
Content Overview
• Spatial layers (all in WGS 84):
• Parcel, Parcel_point, Parcel_load_summary
• FEMA Flood (not Q3 [far superior], includes
LOMA/R’s)
• Streets
• County, State, Zipcode
• Dams & levees
• Others
• NED, National Hydrography Dataset [USGS]
• Wildfire, Storm Surge, Coastline, …
Challenges
• Some of the original difficulties we faced:
• Partitioning for spatial indexes unusable
• We did not use partitioned spatial indexes because
of partition overhead bug; each partition scan takes
around 1ms – (e.g., to scan all 3219 partitions takes
around 3.2s to do simple SDO_RELATE
“mask=ANYINTERACT” query
• Fixed with Patches 6501889 and 6504890
• SDO_AGGR_MBR poor performance on 100+
million (geodetic) layer
• Inability to use Materialized Views w/ Fast Refresh
for join query that includes SDO_GEOMETRY type
in SELECT query (documented limitation)
Applications
• Parcel-Level Geocoding
• Web Mapping Service (WMS)
• Data Layers; Parcel polygons & Points, Flood
polygons, Dam/Levee, National Hydrography
Dataset
• Use open-source GeoServer 1.6.x
• Wrap with security, usage, billing, etc.
• Support for Oracle isn’t on par with PostGIS, etc.
• Provide clients enhanced JavaScript SDK for
use in Google/Virtual Earth
Geocoding Accuracy
Traditional Parcel-Level
Parcel Level Geocoding
Concrete Example
Legacy Interpolated Geocode ParcelPoint Geocode
vs.
A Parcel-based Geocode is the
fundamental building block for
determining the right answer to any
number of analytical questions when
combined with other spatial data sets
24266 Malibu Rd., Malibu, CA 90265
34° 01’49.66” N 118° 42’15.24” W, APN
812870702: Rating Terr: 89, Dist to Coast:
100ft, Surge: Extreme, WildFire: Extreme,
Sinkhole: Low, Hail/Tornado: Low, Property Info:
2-story, Built 1989, Owner: Susanne Summers,
Roof Composition: Cement/Tile, Building
Composition: Masonary/Stucco, Utilities: Gas &
Electric, Valuation: $2.5M, Loan information….
Advantages of Parcel-Level
Geocoding
D E M O N S T R A T I O N
Web Mapping Application
April 2009Oracle Spatial User Conference
Web Mapping
• Government
• Insurance
• Underwriting
• Navigation
• Mapping
• Oil and Pipeline
• Real Estate
• Routing
• Tax
• Utility
• Wireless
Google Earth
Conclusions
• First American Spatial Solutions was at a
decision point
• Needed to choose its spatial platform for the
decade ahead
• Went with x86, SUSE Linux 10, Oracle 11g w/
Spatial
• Successfully navigated thru the transition and
thus far have been pleased with our decision
• Oracle is committed to “spatial” – finally a
viable enterprise solution