Category to group SQL Server Spatial General posts.
SQL Server Spatial, unlike spatial database type systems such as PostGIS, does not provide coordinate editing functions: STAddPoint STUpdatePoint STDeletePoint These functions are not a part of either the SQL or OGC standards. In fact neither provide an API for the SQL editing of geometry objects. If one wishes to do so, one must programRead More
SQL Server Spatial, unlike spatial database type systems such as PostGIS, does not provide coordinate editing functions: STAddPoint STUpdatePoint STDeletePoint These functions are not a part of either the SQL or OGC standards. In fact neither provide an API for the SQL editing of geometry objects. If one wishes to do so, one must programRead More
SQL Server Spatial, unlike spatial database type systems such as PostGIS, does not provide coordinate editing functions: STAddPoint STUpdatePoint STDeletePoint These functions are not a part of either the SQL or OGC standards. In fact neither provide an API for the SQL editing of geometry objects. If one wishes to do so, one must programRead More
SQL Server Spatial, unlike spatial database type systems such as PostGIS, does not provide coordinate editing functions: STAddPoint STUpdatePoint STDeletePoint These functions are not a part of either the SQL or OGC standards. In fact neither provide an API for the SQL editing of geometry objects. If one wishes to do so, one must programRead More
SQL Server Spatial, unlike spatial database type systems such as PostGIS, does not provide coordinate editing functions: STAddPoint STUpdatePoint STDeletePoint These functions are not a part of either the SQL or OGC standards. In fact neither provide an API for the SQL editing of geometry objects. If one wishes to do so, one must programRead More
In the past I have found use for the ability to “flip” vectors in a polygon in order to provide an independent check on the topological integrity of planar enforced polygons. What I mean by topological integrity is that there are no gaps or overlaps between adjacent polygons. A simple method for doing this reliesRead More
I had need today to create a function that extracts all linestring elements from a GeometryCollection and returns a LineString or a MultiLineString. The function is called STConvertToLineString as is described as follows: Its documentation can be seen see here. Here are some examples of how to use it: I hope this function is ofRead More
Previously I wrote about a function that converted the segments of a (Multi)LineString into a COGO XML document that contains all the instructions (bearing, distances, move deltaZ etc) to create a (Multi)LineString. Today I present a function that does the reverse: takes the COGO XML and creates the (Multi)LineString. The instructions are provided to theRead More
I have just written a useful function for my new package of TSQL functions for SQL Server Spatial called STLine2Cogo which converts (exports) a (Multi)LineString into a set of instructions (bearing, distances etc) that can be shared with other COGO functions. The function’s documentation can be seen at this STLine2Cogo Here are some examples: TheRead More
I demonstrated in this article the usefulness of having a vectorising function in one’s spatial database kitbag (there are Vectorize functions in my CENTROID and GEOM packages – in particular the Vectorize function is vital to the implementation of the algorithm in my CENTROID.ST_CENTROID function). So, I have also added one to my SQL ServerRead More