Professional Documents
Culture Documents
Les06 - Comparsion
Les06 - Comparsion
• 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, ®
• 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)
• 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)
• 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
• 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
• Conventional GIS
– Most of them cannot provided
– Not easy to implement
• Oracle Spatial
– Experience on long transaction
– Use Native tool (Oracle Workspace Manager)