Download as pps, pdf, or txt
Download as pps, pdf, or txt
You are on page 1of 7

6

Compare Oracle Spatial Data


Storage and Manipulation with
Conventional GIS

Copyright  Intergraph Hong Kong Limited, ® ®

Oracle Corporation, 2002. All rights reserved.


Storage format and Data Conversion

• Conventional GIS
– File Based
– Graphics and Textual Data are separate
– Need data conversion when sharing data with other
GIS application

• Oracle Spatial
– Native Database storage (tables, records)
– Graphics and Textual data are stored in single
instance
– No data conversion is needed (with OGIS compliant
GIS application)
Copyright  Intergraph Hong Kong Limited, ®

Oracle Corporation, 2002. All rights reserved.


6 -2
Indexing and Tuning

• Conventional GIS
– Limited indexing capabilities
– Different indexing technique for graphics and
textual data
– Poor Performance for huge amount of data

• Oracle Spatial
– Using native Oracle capabilities
– Similar indexing technique
– Excellent performance with good indexing (with the
aids of Primary and Secondary filtering)

Copyright  Intergraph Hong Kong Limited, ®

Oracle Corporation, 2002. All rights reserved.


6 -3
Integration with Database

• Conventional GIS
– Separate system
– Connect through middleware or ODBC
– Or use database file instead of RDBMS

• Oracle Spatial
– Single instance
– Native database connection (SQL Net)

Copyright  Intergraph Hong Kong Limited, ®

Oracle Corporation, 2002. All rights reserved.


6 -4
Spatial Query

• Conventional GIS
– Performed by GIS application
– Poor performance when huge amount of data

• Oracle Spatial
– Native spatial functions
– Can integrate with GIS applications
– Good performance

Copyright  Intergraph Hong Kong Limited, ®

Oracle Corporation, 2002. All rights reserved.


6 -5
Database Maintenance

• Conventional GIS
– Data backup for graphics and textual data should be
performed separately
– Orphan linkage
– Data rollback is not allowed

• Oracle Spatial
– Use native database features, such as backup,
restore, rollback, etc.
– Single record for one spatial object to prevent
orphan linkage

Copyright  Intergraph Hong Kong Limited, ®

Oracle Corporation, 2002. All rights reserved.


6 -6
Long Transaction

• Conventional GIS
– Most of them cannot provided
– Not easy to implement

• Oracle Spatial
– Experience on long transaction
– Use Native tool (Oracle Workspace Manager)

Copyright  Intergraph Hong Kong Limited, ®

Oracle Corporation, 2002. All rights reserved.


6 -7

You might also like