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