 |
|
We have compared our product (spatialdb) to several other products available on the market (Open Source and Non-Open Source). The products we have included ranges from Oracle Spatial, PostGIS, Informix, MySQL, DB2, MS SpatialSQL and ESRI – ArcSDE. Our approach follows from Design and Architecture to Enterprise Implementation.
| |
|
Oracle Spatial
|
Oracle Spatial is the most popular non-open source spatial database solution; however it is jeopardized by its pricing model since the spatial options are only available in its enterprise incarnation.
|
|
|
|
PostGIS
|
PostGIS is the spatial add-on for PostgreSQL, which is a very popular open source database.
|
|
|
|
Informix, MySQL, DB2
|
These products are all either open source products or not, but in some measure similar products to Oracle Spatial and PostGIS, but generally with less functionality. Most of the points mentioned above apply to these products in a greater or lesser degree and it doesn’t bear discussing these in great detail at this point, as these products are not market leaders.
|
|
|
|
MsSqlSpatial
|
This product is an open source recent development on CodePlex, Microsoft’s Open Source Site. MsSqlSpatial attempts to do what we have done with Spatialdb which is to provide SQL Server with spatial capabilities, but only in a 2D arena.
|
|
|
|
ESRI – ArcSDE
|
ESRI deals with the problem of spatial data storage by providing a Spatial Data Engine (SDE) called ArcSDE that is a layer above any standard relational database. Though this gives ESRI database independence, it does provide the problem that spatial data is stored separately from other related business data.
|
|
|