Object-based spatial database: Difference between revisions

Revision as of 04:52, 16 March 2013

Latest revision as of 19:59, 5 August 2025

(9 intermediate revisions by 8 users not shown)

Line 1:

{{Short description|Spatial database}}<!-- this section need many updates and it will not be completed soon -->

-->{{No footnotes|date=August 2025}}

An '''object-based spatial database''' is a [[spatial database]] that stores the ___location as [[Object database|objects]]. The object-based spatial model treats the world as surface littered with recognizable objects (e.g. cities, rivers), which exist independent of their locations.

The object-based spatial model treats the world as surface littered with recognizable objects (e.g. cities, rivers), which exist independent of their locations.

Objects can be simple as [[polygon]]s and lines, or be more complex to represent cities.

Line 8:

While a field-based data model sees the world as a continuous surface over which features (e.g. elevation) vary, using an object-based spatial database, it is easier to store additional attributes with the objects, such as direction, speed, etc. Using these attributes can make it easier to answer queries like "find all tanks whose speed is 10 km and oriented to north". Or "find all enemy tanks in a certain region".

Storing attributes with objects can provide better result presentation and improved manipulation capabilities in a more efficient way. In a field-based data model, this information is usually stored at different layers and it is harder to extract different information from various layers. This data model can be applied above the ER as in GERM model and GISER.

S.Shekhar introduces direction as a spatial object and presents a solution to object-direction-based queries.

==Data model representation==

The most common representations for the data model follow.

===PostGIS===

{{mainMain|PostGIS}}

An open-source software program that adds support for geographic objects to the PostgreSQL object-relationalobject–relational database. PostGIS follows the Simple Features for SQL specification from the Open Geospatial Consortium.

===OMT-G===

Provides a UML representation for geographic applications, it can represent the concept of field, object and provides a way to differentiate between spatial relation and simple association.

===Entity RelationshipEntity–Relationship===

===GraphDB===

Represents a framework of objects as classes that are partitioned into three kinds of classes: simple classes, link classes, and path classes. Objects of a simple class are on the one hand just like objects in other models. They have an object type and an object identity and can have attributes whose values are either of a data type (e.g. integer, string) or of an object type (that is, an attribute may contain a reference to another object). So the structure of an object is basically that of a tuple or record. On the other hand, objects of a simple class are nodes of the database graph – the whole database can also be viewed as a single graph. Objects of a link class are like objects of a simple class but additionally contain two distinguished references to source and target objects (belonging to simple classes), which makes them edges of the database graph. Finally, an object of a path class is like an object of a simple class, but contains additionally a list of references to node and edge objects which form a path over the database graph.

Line 34:

===GeoOOA===

===Oracle spatial ===

{{mainMain|Oracle Spatial}}

Oracle spatial is a component of enterprise Oracle 10g and provides support to stores object such as road on top of the current implentendimplemented construction, but it used network data model to store geographic data as nodes and links (a graph representation) with each node or links it has a set of attributes. For example, a route object can be added to the database.

===GRASS GIS===

{{mainMain|GRASS GIS}}

It supports raster and some set of vector representation.

==See also==

* [[Object database]]

* [[Object-relationalObject–relational database]]

==References==

*[httphttps://dx.doi.org/10.1023/A:1011482030093 Borges, K. A., Davis, C. A., and Laender, A. H. 2001. OMT-G: "An Object-Oriented Data Model for Geographic Applications."] ''Geoinformatica 5'', 3 (Sep. 2001), 221-260.

*Flick, S. 1996. "An object-oriented framework for the realization of 3D geographic information systems." In ''Proceedings of the Second Joint European Conference &Ampamp; Exhibition on Geographical information (Vol. 1) : From Research To Application Through Cooperation: From Research To Application Through Cooperation'' (Barcelona, Spain). M. Rumor, R. McMillan, and H. F. Ottens, Eds. IOS Press, Amsterdam, Thethe Netherlands, 187-196.

*[http://doi.acm.org/10.1145/248448.248465 Shekhar, S., Coyle, M., Goyal, B., Liu, D., and Sarkar, S. 1997. "Data models in geographic information systems." ''Commun. ACM'' 40, 4 (Apr. 1997), 103-111.]

===Oracle spatial documentation===

*[http://doi.acm.org/10.1145/181550.181566 Medeiros, C. B. and Pires, F. 1994. "Databases for GIS." ''SIGMOD Rec.'' 23], 1 (Mar. 1994), 107-115.

*[http://doi.acm.org/10.1145/16894.16886 Orenstein, J. A. 1986. "Spatial query processing in an object-oriented database system."] In ''Proceedings of the 1986 ACM SIGMOD international Conference on Management of Data'' (Washington, D.C., United States, May 28 - 3028–30, 1986). C. Zaniolo, Ed. SIGMOD '86. ACM Press, [[New York, NY]], 326-336.

[[Category:DatabaseObject-oriented database management systems]]

[[Category:Spatial databases]]