1 / 16

A spatial DBMS buyer’s guide

A comprehensive guide for buyers of spatial database management systems, covering functionality, performance, ease of use, documentation, total cost of ownership, integration, and scalability.

gmoody
Télécharger la présentation

A spatial DBMS buyer’s guide

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. A spatial DBMS buyer’s guide Wim de Haas - RWS Wilko Quak - TUDelft Maarten Vermeij - TUDelft

  2. Overview • Short CV • Example: A camera buyer’s guide • Towards a spatial DBMS buyer’s guide • Discussion Spatial DBMS Buyer's Guide

  3. Background • 1994: PhD student in spatial DBMS performance • 1995: Wrote spatial extension to MonetDB (was fastest in the world back then) • 2000-now: work at GIS-technology department and test various DBMS for various reasons: • Products: Ingres, Oracle, Oracle topology, Oracle Point Cloud, Informix, PostGIS, MySQL, ArcSDE, … • Datasets: Cadastral, Laser Scanning Points, GPS logs, road maintenance data. Spatial DBMS Buyer's Guide

  4. Use feature matrix Example: A camera buyer’s guide Figure out your profile Check out the specs that matter Spatial DBMS Buyer's Guide

  5. Towards a spatial DBMS buyer’s guide? • Buyer’s Guide (does not exist) • Feature Matrix: • Last version compares only (SQLServer, MySQL and PostGIS. • Based on documentation and not verified Spatial DBMS Buyer's Guide

  6. Let’s write a ‘buyer’s’ guide: • Make categories of users: • Done: FOSS4G2007: Server Builders, GIS Users, Dataset Maintainer, Power User • Figure out relevant feature for each category: • Todo: See rest of presentation • Fill feature matrix: • Continuous JOB: For community? Spatial DBMS Buyer's Guide

  7. Buyer’s guide Feature list • Functionality • Performance • Ease of Use • Documentation • Hardware needs • Total Cost of Ownership • Integration in business environment • Scaleability • Open Source vs Closed Source Spatial DBMS Buyer's Guide

  8. Same co-ordinate transformation gives meters of difference Functionality • Check the documentation. • Run cross check or test: Spatial DBMS Buyer's Guide

  9. Performance (= benchmarking) • Not as important as you would expect • In most cases performance is not an issue • Moore’s law helps a lot • There are big differencesbetween query optimizers Spatial DBMS Buyer's Guide

  10. Ease of Use • For 1 day of consultancy to improve performance you can buy a lot of hardware! • A cumbersome system is not fun: • A self organizing DBMS might save a lot of work: • Adherance to standards saves time (Learn another dialect of SQL, Please: polygons in WKT) • Readable documentation helps Spatial DBMS Buyer's Guide

  11. PostGIS Documentation Oracle Spatial DBMS Buyer's Guide

  12. Total Cost of Ownership • Open Source = free • Cost for support • Hard to find support staff Spatial DBMS Buyer's Guide

  13. Integration • How well does the DBMS integrate with other products: • SOAP • JDBC • Hibernate • The rest of the GIS stack Spatial DBMS Buyer's Guide

  14. Scaleability There might be another breakpoint here • Very hard to predict without testing. • Most functions look like this: There is a breakpoint here Spatial DBMS Buyer's Guide

  15. Open Source or not? Marks from old non-standard sized toilet paper dispenser • Vendor Lock-in is EVERYWHERE: Spatial DBMS Buyer's Guide

  16. Discussion Spatial DBMS Buyer's Guide

More Related