615:, plus some spatial functions implemented according to the OpenGIS specifications. However, in MySQL version 5.5 and earlier, functions that test spatial relationships are limited to working with minimum bounding rectangles rather than the actual geometries. MySQL versions earlier than 5.0.16 only supported spatial data in MyISAM tables. As of MySQL 5.0.16, InnoDB, NDB, BDB, and ARCHIVE also support spatial features.
1411:
1997 OGC released the OpenGIS Simple
Features Specification, which specifies the interface that enables diverse systems to communicate in terms of 'simple features' which are based on 2D geometry. The supported geometry types include points, lines, linestrings, curves, and polygons. Each geometric
578:
Geodetic and
Spatial datablade extensions auto-install on use and expand Informix's datatypes to include multiple standard coordinate systems and support for RTree indexes. Geodetic and Spatial data can also be incorporated with Informix's Timeseries data support for tracking objects in motion over
164:, spatial databases must also allow for the tracking and transformation of coordinate systems. In many systems, when a spatial column is defined in a table, it also includes a choice of coordinate system, chosen from a list of available systems that is stored in a lookup table.
175:
that are available in traditional GIS software. In most relational database management systems, this functionality is implemented as a set of new functions that can be used in SQL SELECT statements. Several types of operations are specified by the
190:
Predicates: Allows true/false queries about spatial relationships between geometries. Examples include "do two polygons overlap?" or 'is there a residence located within a mile of the area we are planning to build the landfill?' (see
359:
queries in several important ways. Two of the most important are that they allow for the use of geometry data types such as points, lines and polygons and that these queries consider the spatial relationship between these geometries.
115:(GIS). Almost all current relational and object-relational database management systems now have spatial extensions, and some GIS software vendors have developed their own spatial extensions to database management systems.
499:(Enterprise, Mobile) - a proprietary spatial database structure and logical model that can be implemented on several relational databases, both commercial (Oracle, MS SQL Server, Db2) and open source (PostgreSQL, SQLite)
517:
is a document-based database system that supports two types of geo data: geo_point fields which support lat/lon pairs, and geo_shape fields, which support points, lines, circles, polygons, multi-polygons,
1799:"Neo4j Spatial is a library of utilities for Neo4j that facilitates the enabling of spatial operations on data. In particular you can add spatial indexes to already located data, and perform spatial"
233:. Database systems use indices to quickly look up values by sorting data values in a linear (e.g. alphabetical) order; however, this way of indexing data is not optimal for
1888:
448:
561:
supports geometry types and spatial indices as of version 1.3.173 (2013-07-28). An extension called H2GIS available on Maven
Central gives full OGC
367:, a free geodatabase which is a PostgreSQL extension (the term 'geometry' refers to a point, line, box or other two or three dimensional shape):
1682:
1907:
1634:
288:– an m-tree index can be used for the efficient resolution of similarity queries on complex objects as compared using an arbitrary metric.
752:
187:
Geoprocessing: Modify existing features to create new ones, for example by creating a buffer around them, intersecting features, etc.
1875:
1861:
1843:
1531:
1452:
1412:
object is associated with a
Spatial Reference System, which describes the coordinate space in which the geometric object is defined.
167:
The second major functionality extension in a spatial database is the addition of spatial capabilities to the query language (e.g.,
454:
438:
SELECT ST_Intersection(veg.shape, soil.shape) int_poly, veg.*, soil.* FROM veg, soil where ST_Intersects(veg.shape, soil.shape)
422:
between a points layer of cities and a polygon layer of countries could be performed in a spatially-extended SQL statement as:
144:, which allow for the storage of spatial data as attribute values in a table. Most commonly, a single spatial value would be a
492:- A MPP SQL query engine for querying large datasets. Drill supports spatial data types and functions similar to PostgreSQL.
473:
201:
Observer
Functions: Queries that return specific information about a feature, such as the location of the center of a circle.
112:
85:, such databases require additional functionality to process spatial data types efficiently, and developers have often added
78:
1748:
1064:
yes (contain, cover, covered by, cross, disjoint, intersect, intersect window, overlap, touch, within and within distance)
198:
Geometry
Constructors: Creates new geometries, usually by specifying the vertices (points or nodes) which define the shape.
1928:
1896:
1334:
1303:
1249:
1185:
638:
1314:
309:: Typically the preferred method for indexing spatial data. Objects (shapes, lines and points) are grouped using the
1469:
128:
specification (first released in 1997) and sets standards for adding spatial functionality to database systems. The
1923:
1853:
1584:
1096:
310:
177:
132:
ISO/IEC standard is a part of the structured query language and multimedia standard extending the Simple
Features.
119:
643:
251:
245:
874:
1177:
1128:
756:
602:
363:
The function names for queries differ across geodatabases. The following are a few of the functions built into
161:
706:
is a commercial spatiotemporal database built on top of the proprietary multidimensional index similar to the
572:
can be spatially-enabled to implement the OpenGIS spatial functionality with SQL spatial types and functions.
472:
which provides a mechanism for efficient storage and retrieval of two-dimensional geospatial coordinates for
1354:
1329:
713:
family, but created using the bottom-up approach and adapted to particular space-time distribution of data.
1228:
1319:
1161:
1112:
985:
944:
313:(MBR). Objects are added to an MBR within the index that will lead to the smallest increase in its size.
156:
specification for representing geometric primitives. Some spatial databases also support the storage of
51:
1373:
The term "geodatabase" may also refer specifically to a set of proprietary spatial database formats,
1224:
948:
716:
588:
262:
205:
Some databases support only simplified or modified sets of these operations, especially in cases of
1324:
742:
502:
145:
39:
241:
index designed specifically for multi-dimensional ordering. Common spatial index methods include:
1893:
1867:
1374:
1077:
924:
862:
817:
1638:
1444:
1871:
1857:
1839:
1770:
1597:
1527:
1448:
1008:
889:
877:
1731:
1436:
1344:
582:
544:
355:
supported by spatial databases, including geodatabases. The queries differ from non-spatial
172:
149:
58:
1756:
1608:
1703:
1339:
1154:
1105:
1058:
917:
562:
552:
525:
511:
a document-based database system that can be spatially enabled by a plugin called
Geocouch
336:
157:
153:
124:
108:
62:
1660:
1496:
907:
653:
622:
469:
431:
352:
272:
81:(TINs). While typical databases have developed to manage various numeric and character
70:
1620:
646:
has supported SQL/MM since version 6.01.3126, with significant enhancements including
184:
Measurement: Computes line length, polygon area, the distance between geometries, etc.
1917:
1437:
634:
585:
supports spatial types and spatial functions according to the OpenGIS specifications.
529:
514:
234:
230:
104:
74:
57:
Most spatial databases allow the representation of simple geometric objects such as
952:
812:
665:
to implement OGC-compliant spatial functionality, including standardized datatype
575:
548:
533:
489:
465:
419:
43:
1901:
140:
The core functionality added by a spatial extension to a database is one or more
1399:
1349:
1138:
505:
extends the Raima Data
Manager with spatial datatypes, functions, and utilities.
496:
426:
SELECT * FROM cities, countries WHERE ST_Contains(countries.shape, cities.shape)
1572:
829:
745:
includes 2D spatial functionality (OGC-compliant) in its data warehouse system.
1904:
Sajimon
Abraham, P. Sojan Lal, Published by Springer Berlin / Heidelberg-2008.
1087:
786:
726:
697:
690:
658:
1635:"MySQL 5.5 Reference Manual - 12.17.1. Introduction to MySQL Spatial Support"
1902:
A Trigger Based Security Alarming Scheme for Moving Objects on Road Networks
1309:
1244:
963:
793:
736:
678:
647:
558:
111:(or geodata, i.e., data associated with a location on Earth), especially in
82:
1798:
17:
1547:
316:
1195:
931:
857:
707:
684:
630:
540:
483:
408:
301:
277:
35:
1818:
1849:
1142:
1091:
902:
748:
662:
598:
594:
569:
521:
508:
364:
326:
321:
296:
257:
214:
210:
66:
1835:
1585:"Geo queries | Elasticsearch Guide [7.15] | Elastic"
1803:
730:
720:
626:
537:
477:
331:
306:
291:
285:
267:
237:
in two- or three-dimensional space. Instead, spatial databases use a
192:
27:
Database optimized for data representing objects in a geometric space
160:. Because all geographic locations must be specified according to a
1894:
PostgreSQL PostGIS as components in a Service Oriented Architecture
1870:
Pouria Amirian, Anahid Basiri and Adam Winstanley. Springer. 2014 (
434:
operation (a core element of GIS software) could be replicated as:
1045:
703:
672:
618:
608:
206:
47:
841:
1717:
1423:
1205:
969:
805:
693:
69:. Some spatial databases handle more complex structures such as
486:- a multi-model database which provides geoindexing capability.
152:. The datatypes in most spatial databases are based on the OGC
1784:
1683:"New Releases of Virtuoso Enterprise and Open Source Editions"
1201:
1181:
1013:
973:
847:
356:
168:
1868:
Evaluation of Data Management Systems for Geospatial Big Data
650:
in Open Source Edition 7.2.6, and in Enterprise Edition 8.2.0
764:
Table of free systems especially for spatial data processing
524:
is a cloud-based spatio-temporal database built on top of
1838:, Shashi Shekhar and Sanjay Chawla, Prentice Hall, 2003 (
755:, adds OGC-compliant spatial features to the relational
1470:"DM-03 - Relational DBMS and their Spatial Extensions"
1147:
Mozilla public license and GNU general public license
1661:"9.34. Geometry Data Types and Spatial Index Support"
661:
DBMS (database management system) uses the extension
107:
spatial database, used for storing and manipulating
1910:
ArcGIS Resource Center description of a geodatabase
414:
ST_Intersection(geometry, geometry) : geometry
1852:Philippe Rigaux, Michel Scholl and Agnes Voisard.
733:with spatial datatypes, functions, and utilities.
1522:Güting, Ralf Hartmut; Schneider, Markus (2005).
1435:Kresse, Wolfgang; Danko, David M., eds. (2010).
591:has support for spatial types since version 2008
386:ST_Intersects(geometry, geometry) : boolean
372:functionName (parameter(s)) : return type
398:ST_Contains(geometry, geometry) : boolean
395:ST_Overlaps(geometry, geometry) : boolean
383:ST_Disjoint(geometry, geometry) : boolean
739:supports geospatial queries with RTREE index.
392:ST_Crosses(geometry, geometry) : boolean
389:ST_Touches(geometry, geometry) : boolean
377:ST_Distance(geometry, geometry) : number
248:(BSP-Tree): Subdividing space by hyperplanes.
8:
380:ST_Equals(geometry, geometry) : boolean
173:query, analysis, and manipulation operations
171:); these give the spatial database the same
1850:Spatial Databases – With Application to GIS
1439:Springer handbook of geographic information
1236:own defined function in enterprise edition
601:adds OGS Simple Features to the relational
1443:(1. ed.). Berlin: Springer. pp.
767:
476:data. It includes an extension syntax for
229:is used by a spatial database to optimize
148:(point, line, polygon, etc.) based on the
830:Drill Geospatial Functions Documentation
1574:Drill Geospatial Function Documentation
1390:
1366:
940:parts of the functions, a few examples
1889:An introduction to PostgreSQL PostGIS
1609:H2 create spatial index documentation
46:that represents objects defined in a
7:
1819:"ReQL command reference - RethinkDB"
625:that can build 1D and 2D indexes as
42:) that has been enhanced to include
1173:PostGIS: yes, Postgres-XL: briefly
988:and custom functions for H2Network
449:Spatial database management systems
443:Spatial database management systems
1051:GNU affero general public license
681:supports geospatial indexes in 2D.
25:
401:ST_Length(geometry) : number
1681:OpenLink Software (2018-10-23).
1526:. Morgan Kaufmann. p. 262.
1019:yes (if extension is installed)
955:are all kinds of tasks solvable
751:, the geo-spatial extension for
1217:raster manipulation with rasql
687:supports geospatial with SPS08.
404:ST_Area(geometry) : number
79:triangulated irregular networks
1598:H2 geometry type documentation
474:Resource Description Framework
113:geographic information systems
1:
1335:Object-based spatial database
1304:Geographic information system
1025:Geometry Engine, Open Source
723:spatially enables Sybase ASE.
611:DBMS implements the datatype
551:). GeoMesa supports full OGC
1548:"PostGIS Function Reference"
669:and corresponding functions.
1718:"Command reference – Redis"
1501:GIS&T Body of Knowledge
1474:GIS&T Body of Knowledge
1315:Glacio-geological databases
54:and analyzing such data.
1945:
1854:Morgan Kaufmann Publishers
1097:GNU General Public License
452:
446:
411:(geometry) : geometry
311:minimum bounding rectangle
178:Open Geospatial Consortium
120:Open Geospatial Consortium
1836:Spatial Databases: A Tour
1208:, enterprise proprietary
252:Bounding volume hierarchy
246:Binary space partitioning
1524:Moving Objects Databases
1497:"DM-66 Spatial Indexing"
1400:"OGC History (detailed)"
1176:SQL, in connection with
1127:SQL, in connection with
1022:yes (custom, no raster)
982:yes (custom, no raster)
930:no (manufacturable with
878:query language functions
162:spatial reference system
1704:"OGC Certified PostGIS"
1355:Spatiotemporal database
1330:Nearest neighbor search
1285:official documentation
555:and a GeoServer plugin.
77:, linear networks, and
50:, along with tools for
1621:"GeoSpatial – MonetDB"
1229:Web Processing Service
1164:and raster functions)
1115:and raster functions)
455:Geographical databases
1398:McKee, Lance (2016).
1320:Location intelligence
1162:Simple Feature Access
1113:Simple Feature Access
986:Simple Feature Access
945:Simple Feature Access
875:capabilities overview
351:is a special type of
75:topological coverages
34:is a general-purpose
1929:Geometric algorithms
1225:Web Coverage Service
949:Java Virtual Machine
717:Spatial Query Server
589:Microsoft SQL Server
370:Function prototype:
263:Grid (spatial index)
122:(OGC) developed the
1659:OpenLink Software.
1325:Multimedia database
743:Teradata Geospatial
146:geometric primitive
97:Geographic database
40:relational database
1773:. 2 December 2015.
1771:"HP Vertica Place"
1495:Zhang, X.; Du, Z.
1375:Geodatabase (Esri)
863:Apache License 2.0
818:Apache License 2.0
1924:Spatial databases
1732:"SAP Help Portal"
1468:Yue, P.; Tan, Z.
1295:
1294:
783:Spatial functions
675:with the Geo API.
644:OpenLink Virtuoso
583:Linter SQL Server
150:vector data model
142:spatial datatypes
16:(Redirected from
1936:
1823:
1822:
1815:
1809:
1808:
1795:
1789:
1788:
1781:
1775:
1774:
1767:
1761:
1760:
1755:. Archived from
1745:
1739:
1738:
1736:
1728:
1722:
1721:
1714:
1708:
1707:
1700:
1694:
1693:
1691:
1689:
1678:
1672:
1671:
1669:
1667:
1656:
1650:
1649:
1647:
1646:
1637:. Archived from
1631:
1625:
1624:
1617:
1611:
1606:
1600:
1595:
1589:
1588:
1581:
1575:
1570:
1564:
1563:
1561:
1559:
1544:
1538:
1537:
1519:
1513:
1512:
1510:
1508:
1492:
1486:
1485:
1483:
1481:
1465:
1459:
1458:
1442:
1432:
1426:
1421:
1415:
1414:
1408:
1407:
1395:
1378:
1371:
1345:Spatial analysis
972:3 (since v1.3),
768:
696:, the native GE
637:directly in the
545:Apache Cassandra
439:
427:
32:spatial database
21:
1944:
1943:
1939:
1938:
1937:
1935:
1934:
1933:
1914:
1913:
1885:
1832:
1830:Further reading
1827:
1826:
1817:
1816:
1812:
1797:
1796:
1792:
1783:
1782:
1778:
1769:
1768:
1764:
1747:
1746:
1742:
1734:
1730:
1729:
1725:
1716:
1715:
1711:
1702:
1701:
1697:
1687:
1685:
1680:
1679:
1675:
1665:
1663:
1658:
1657:
1653:
1644:
1642:
1633:
1632:
1628:
1623:. 4 March 2014.
1619:
1618:
1614:
1607:
1603:
1596:
1592:
1583:
1582:
1578:
1571:
1567:
1557:
1555:
1546:
1545:
1541:
1534:
1521:
1520:
1516:
1506:
1504:
1494:
1493:
1489:
1479:
1477:
1467:
1466:
1462:
1455:
1434:
1433:
1429:
1422:
1418:
1405:
1403:
1397:
1396:
1392:
1387:
1382:
1381:
1372:
1368:
1363:
1340:Simple Features
1300:
1265:getIntersecting
1155:Simple Features
1106:Simple Features
1059:Simple Features
1037:with C and OME
1031:with MapScript
1016:or proprietary
997:yes (homepage)
918:Simple Features
780:Spatial objects
766:
568:Any edition of
563:Simple Features
553:Simple Features
532:(also supports
526:Apache Accumulo
462:
457:
453:Main category:
451:
447:Main category:
445:
437:
425:
345:
337:Z-order (curve)
235:spatial queries
231:spatial queries
223:
154:Simple Features
138:
136:Characteristics
125:Simple Features
109:geographic data
48:geometric space
28:
23:
22:
15:
12:
11:
5:
1942:
1940:
1932:
1931:
1926:
1916:
1915:
1912:
1911:
1905:
1899:
1891:
1884:
1883:External links
1881:
1880:
1879:
1865:
1847:
1831:
1828:
1825:
1824:
1810:
1790:
1776:
1762:
1759:on 2014-12-13.
1740:
1723:
1709:
1695:
1673:
1651:
1626:
1612:
1601:
1590:
1576:
1565:
1552:PostGIS Manual
1539:
1532:
1514:
1487:
1460:
1453:
1427:
1416:
1389:
1388:
1386:
1383:
1380:
1379:
1365:
1364:
1362:
1359:
1358:
1357:
1352:
1347:
1342:
1337:
1332:
1327:
1322:
1317:
1312:
1307:
1299:
1296:
1293:
1292:
1289:
1286:
1283:
1280:
1277:
1276:
1275:
1272:
1269:
1266:
1263:
1258:
1255:
1252:
1247:
1241:
1240:
1237:
1234:
1233:detailed wiki
1231:
1221:
1218:
1215:
1212:
1209:
1198:
1192:
1191:
1188:
1174:
1171:
1168:
1165:
1158:
1151:
1148:
1145:
1135:
1134:
1131:
1125:
1122:
1119:
1116:
1109:
1102:
1099:
1094:
1084:
1083:
1080:
1074:
1071:
1068:
1065:
1062:
1055:
1052:
1049:
1042:
1041:
1038:
1035:
1032:
1029:
1026:
1023:
1020:
1017:
1011:
1005:
1004:
1001:
998:
995:
992:
989:
983:
980:
977:
967:
960:
959:
956:
941:
938:
935:
928:
921:
914:
911:
908:Apache License
905:
899:
898:
895:
892:
886:
883:
880:
871:
868:
865:
860:
854:
853:
850:
844:
838:
835:
832:
826:
823:
820:
815:
809:
808:
803:
800:
797:
790:
784:
781:
778:
775:
772:
765:
762:
761:
760:
746:
740:
734:
724:
714:
701:
688:
682:
676:
670:
656:
654:Oracle Spatial
651:
641:
623:graph database
616:
606:
597:extension for
592:
586:
580:
573:
566:
556:
519:
512:
506:
500:
493:
487:
481:
470:graph database
461:
458:
444:
441:
432:vector overlay
430:The Intersect
416:
415:
412:
405:
402:
399:
396:
393:
390:
387:
384:
381:
378:
353:database query
344:
341:
340:
339:
334:
329:
324:
319:
314:
304:
299:
294:
289:
283:
275:
273:Hilbert R-tree
270:
265:
260:
255:
249:
222:
219:
203:
202:
199:
196:
188:
185:
137:
134:
130:SQL/MM Spatial
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
1941:
1930:
1927:
1925:
1922:
1921:
1919:
1909:
1906:
1903:
1900:
1898:
1895:
1892:
1890:
1887:
1886:
1882:
1877:
1876:9783319091563
1873:
1869:
1866:
1863:
1862:1-55860-588-6
1859:
1855:
1851:
1848:
1845:
1844:0-13-017480-7
1841:
1837:
1834:
1833:
1829:
1820:
1814:
1811:
1807:. 2019-02-18.
1806:
1805:
1800:
1794:
1791:
1786:
1780:
1777:
1772:
1766:
1763:
1758:
1754:
1753:tarantool.org
1750:
1744:
1741:
1733:
1727:
1724:
1719:
1713:
1710:
1705:
1699:
1696:
1684:
1677:
1674:
1662:
1655:
1652:
1641:on 2013-04-30
1640:
1636:
1630:
1627:
1622:
1616:
1613:
1610:
1605:
1602:
1599:
1594:
1591:
1586:
1580:
1577:
1573:
1569:
1566:
1553:
1549:
1543:
1540:
1535:
1533:9780120887996
1529:
1525:
1518:
1515:
1502:
1498:
1491:
1488:
1475:
1471:
1464:
1461:
1456:
1454:9783540726807
1450:
1446:
1441:
1440:
1431:
1428:
1425:
1420:
1417:
1413:
1401:
1394:
1391:
1384:
1376:
1370:
1367:
1360:
1356:
1353:
1351:
1348:
1346:
1343:
1341:
1338:
1336:
1333:
1331:
1328:
1326:
1323:
1321:
1318:
1316:
1313:
1311:
1308:
1305:
1302:
1301:
1297:
1290:
1287:
1284:
1281:
1278:
1273:
1270:
1267:
1264:
1261:
1260:
1259:
1256:
1253:
1251:
1248:
1246:
1243:
1242:
1238:
1235:
1232:
1230:
1226:
1222:
1219:
1216:
1213:
1210:
1207:
1203:
1199:
1197:
1194:
1193:
1189:
1187:
1183:
1179:
1175:
1172:
1169:
1166:
1163:
1159:
1156:
1152:
1149:
1146:
1144:
1140:
1137:
1136:
1132:
1130:
1126:
1123:
1120:
1117:
1114:
1110:
1107:
1103:
1100:
1098:
1095:
1093:
1089:
1086:
1085:
1081:
1079:
1075:
1073:just briefly
1072:
1069:
1066:
1063:
1060:
1056:
1053:
1050:
1047:
1044:
1043:
1039:
1036:
1034:just briefly
1033:
1030:
1027:
1024:
1021:
1018:
1015:
1012:
1010:
1007:
1006:
1002:
999:
996:
993:
990:
987:
984:
981:
978:
975:
971:
968:
965:
962:
961:
957:
954:
950:
946:
942:
939:
936:
933:
929:
926:
922:
919:
915:
912:
909:
906:
904:
901:
900:
896:
893:
891:
890:documentation
887:
884:
881:
879:
876:
872:
869:
866:
864:
861:
859:
856:
855:
851:
849:
845:
843:
842:Documentation
839:
836:
833:
831:
827:
824:
821:
819:
816:
814:
811:
810:
807:
804:
801:
799:Documentation
798:
795:
791:
788:
785:
782:
779:
776:
773:
770:
769:
763:
758:
754:
750:
749:Vertica Place
747:
744:
741:
738:
735:
732:
728:
725:
722:
718:
715:
712:
710:
705:
702:
699:
695:
692:
689:
686:
683:
680:
677:
674:
671:
668:
664:
660:
657:
655:
652:
649:
645:
642:
640:
636:
635:Hilbert curve
632:
628:
624:
620:
617:
614:
610:
607:
604:
600:
596:
593:
590:
587:
584:
581:
577:
574:
571:
567:
564:
560:
557:
554:
550:
546:
542:
539:
535:
531:
530:Apache Hadoop
527:
523:
520:
516:
515:Elasticsearch
513:
510:
507:
504:
501:
498:
494:
491:
488:
485:
482:
479:
475:
471:
467:
464:
463:
459:
456:
450:
442:
440:
435:
433:
428:
423:
421:
413:
410:
406:
403:
400:
397:
394:
391:
388:
385:
382:
379:
376:
375:
374:
373:
368:
366:
361:
358:
354:
350:
349:spatial query
343:Spatial query
342:
338:
335:
333:
330:
328:
325:
323:
320:
318:
315:
312:
308:
305:
303:
300:
298:
295:
293:
290:
287:
284:
282:
280:
276:
274:
271:
269:
266:
264:
261:
259:
256:
253:
250:
247:
244:
243:
242:
240:
236:
232:
228:
227:spatial index
221:Spatial index
220:
218:
216:
212:
209:systems like
208:
200:
197:
194:
189:
186:
183:
182:
181:
179:
174:
170:
165:
163:
159:
155:
151:
147:
143:
135:
133:
131:
127:
126:
121:
116:
114:
110:
106:
105:georeferenced
102:
98:
94:
93:data types.
92:
88:
84:
83:types of data
80:
76:
72:
68:
64:
60:
55:
53:
49:
45:
41:
37:
33:
19:
1813:
1802:
1793:
1779:
1765:
1757:the original
1752:
1743:
1726:
1712:
1698:
1686:. Retrieved
1676:
1664:. Retrieved
1654:
1643:. Retrieved
1639:the original
1629:
1615:
1604:
1593:
1579:
1568:
1556:. Retrieved
1551:
1542:
1523:
1517:
1505:. Retrieved
1500:
1490:
1478:. Retrieved
1473:
1463:
1438:
1430:
1424:OGC Homepage
1419:
1410:
1404:. Retrieved
1393:
1369:
1214:just raster
1157:and raster)
1108:and raster)
953:Apache Spark
813:Apache Drill
757:column-store
708:
700:GIS database
666:
612:
603:column-store
576:IBM Informix
549:Apache Kafka
534:Apache HBase
490:Apache Drill
466:AllegroGraph
436:
429:
424:
420:spatial join
417:
371:
369:
362:
348:
346:
278:
238:
226:
224:
204:
166:
141:
139:
129:
123:
117:
100:
96:
95:
90:
86:
56:
44:spatial data
31:
29:
1908:geodatabase
1688:October 24,
1666:October 24,
1350:Spatial ETL
1139:Postgres-XL
777:Distributed
595:MonetDB/GIS
497:Geodatabase
158:raster data
101:geodatabase
38:(usually a
18:Geodatabase
1918:Categories
1645:2013-05-01
1406:2016-07-12
1385:References
1274:intersects
1268:getNearest
1088:PostgreSQL
802:Modifiable
787:PostgreSQL
753:HP Vertica
727:SpatiaLite
698:Smallworld
691:Smallworld
659:PostgreSQL
180:standard:
71:3D objects
1558:4 January
1507:5 January
1480:5 January
1310:GeoSPARQL
1245:RethinkDB
1204:, client
1124:detailed
1048:-spatial
976:3 before
888:official
840:Official
796:interface
794:MapServer
789:interface
759:database.
737:Tarantool
704:SpaceTime
679:RethinkDB
648:GeoSPARQL
605:database.
1856:. 2002 (
1298:See also
1288:forking
1271:includes
1262:distance
1196:Rasdaman
1076:fork of
966:(H2GIS)
932:GeoTools
858:ArangoDB
729:extends
685:SAP HANA
667:geometry
631:Quadtree
613:geometry
565:support.
541:Bigtable
484:ArangoDB
480:queries.
418:Thus, a
409:Centroid
302:Quadtree
87:geometry
67:polygons
52:querying
36:database
1749:"RTREE"
1554:. OSGeo
1503:. UCGIS
1476:. UCGIS
1200:server
1143:PostGIS
1092:PostGIS
903:GeoMesa
774:License
711:-d tree
663:PostGIS
599:MonetDB
570:IBM Db2
522:GeoMesa
509:CouchDB
503:Caliper
365:PostGIS
327:UB-tree
322:R* tree
317:R+ tree
297:PH-tree
281:-d tree
258:Geohash
239:spatial
215:CouchDB
211:MongoDB
103:) is a
91:feature
1874:
1860:
1842:
1804:GitHub
1785:"GEOS"
1530:
1451:
1186:Python
1009:Ingres
873:yes -
828:yes -
731:Sqlite
721:Boeing
627:B-tree
547:, and
538:Google
478:SPARQL
332:X-tree
307:R-tree
292:Octree
286:m-tree
268:HHCode
193:DE-9IM
59:points
1735:(PDF)
1447:–83.
1402:. OGC
1361:Notes
1306:(GIS)
1223:with
1160:yes (
1153:yes (
1141:with
1111:yes (
1104:yes (
1090:with
1057:yes (
1046:Neo4J
943:with
923:yes (
916:yes (
846:ANSI
719:from
673:Redis
639:graph
619:Neo4j
609:MySQL
579:time.
495:Esri
254:(BVH)
207:NoSQL
63:lines
1872:ISBN
1858:ISBN
1840:ISBN
1690:2018
1668:2018
1560:2023
1528:ISBN
1509:2023
1482:2023
1449:ISBN
1257:yes
1254:yes
1250:AGPL
1220:yes
1211:yes
1206:LGPL
1170:yes
1167:yes
1150:yes
1121:yes
1118:yes
1000:SQL
991:yes
970:LGPL
958:yes
951:and
913:yes
910:2.0
894:AQL
870:yes
867:yes
852:yes
834:yes
825:yes
822:yes
806:HDFS
792:UMN
694:VMDS
633:and
621:– a
528:and
518:etc.
468:– a
460:List
213:and
118:The
99:(or
65:and
1897:SOA
1291:no
1282:no
1279:no
1239:no
1227:or
1202:GPL
1190:no
1184:or
1182:Tcl
1180:or
1133:no
1101:no
1082:no
1078:JTS
1070:no
1067:no
1054:no
1040:no
1028:no
1014:GPL
1003:no
994:no
979:no
974:GPL
947:in
937:no
925:JTS
897:no
885:no
882:no
848:SQL
837:no
771:DBS
407:ST_
357:SQL
169:SQL
89:or
1920::
1801:.
1751:.
1550:.
1499:.
1472:.
1445:82
1409:.
1061:)
964:H2
934:)
927:)
920:)
629:,
559:H2
543:,
536:,
347:A
225:A
217:.
73:,
61:,
30:A
1878:)
1864:)
1846:)
1821:.
1787:.
1737:.
1720:.
1706:.
1692:.
1670:.
1648:.
1587:.
1562:.
1536:.
1511:.
1484:.
1457:.
1377:.
1178:R
1129:R
709:k
279:k
195:)
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.