|
⇤ ← Revision 1 as of 2014-04-01 12:55:15
Size: 474
Comment:
|
Size: 1044
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 22: | Line 22: |
| * SQL must parse All WKT into it's own internal binary format. Parsing takes additional time making this method '''slower''' than binary creation methods. Methods of instantiating Spatial data from WKT: ||'''Geometry'''|| '''Static Method'''|| ||Point ||STPointFromText()|| ||LineString|| STLineFromText()|| ||Polygon|| STPolyFromText()|| ||MultiPoint|| STMPointFromText()|| ||MultiLineString|| STMLineFromText()|| ||MultiPolygon|| STMPolyFromText()|| ||GeometryCollection|| STGeomCollFromText()|| ||Any supported geometry|| STGeomFromText() / Parse()|| |
Creating Spatial Data
SQL provides methods to create data in several formats:
- Well-Known Text (WKT)
- Well-known Binary (WKB)
- Geography Markup Language (GML)
- Programatically
SqlGeometryBuilder class
SqlGeographyBuilder class
Well-Known Text
Advantages:
- Simple format
- Human readable
Disadvantage:
loss of precision due to rounding of text-based representation of floating point coordinate values
SQL must parse All WKT into it's own internal binary format. Parsing takes additional time making this method slower than binary creation methods.
Methods of instantiating Spatial data from WKT:
Geometry |
Static Method |
Point |
STPointFromText() |
STLineFromText() |
|
Polygon |
STPolyFromText() |
STMPointFromText() |
|
STMLineFromText() |
|
STMPolyFromText() |
|
STGeomCollFromText() |
|
Any supported geometry |
STGeomFromText() / Parse() |