Object-based spatial database: Difference between revisions

Revision as of 01:31, 4 July 2020

Latest revision as of 19:59, 5 August 2025

(5 intermediate revisions by 4 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 16:

===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===

Line 36:

===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==

*[https://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 &amp; 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.]

Line 57:

*[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–30, 1986). C. Zaniolo, Ed. SIGMOD '86. ACM Press, [[New York, NY]], 326-336.

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

[[Category:Spatial databases]]