Skip to content

Commit 3213809

Browse files
authored
Update 04-curcapabilities.adoc
1 parent db5bc2d commit 3213809

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

document/sections/04-curcapabilities.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -107,11 +107,11 @@ image::../figures/Dimensions_FIG02.png[align="center"]
107107
GeoSPARQL 1.1 also does not restrict the usage of coordinate reference systems with 3D support.
108108
There are currently almost 300 coordinate reference systems in the database https://epsg.io/?q=%20kind%3AGEOG3DCRS[epsg.io] which can be used to describe 3D data encoded in the GeoSPARQL graph literals listed above.
109109

110-
GeoSPARQL allready supports linking multiple geometries (e.g., 2D and 2.5D) to a single feature. We aim to extend this with 3D geometries.
110+
GeoSPARQL allready supports linking multiple geometries (e.g., 2D and 2.5D) to a single feature. We aim to extend this with 3D geometries.
111111

112-
For example, a tree in the real world may be represented in databases with both a 2D and a 3D geometry.
112+
For example, a tree in the real world may be represented in databases with both a 2D and a 3D geometry.
113113

114-
This should not require duplication of the tree entity — there can be one tree instance with both geometries linked, avoiding redundancy in the data model.
114+
This should not require duplication of the tree entity — there can be one tree instance with both geometries linked, avoiding redundancy in the data model.
115115

116116

117117
===== Query functions with 3D support

0 commit comments

Comments
 (0)