Top 5 Recent Articles
ARTICLES CATEGORIES
- Algorithms (22)
- All (399)
- Biography (1)
- Blog (44)
- Business Requirements (1)
- Commentary (1)
- Conversion (2)
- Customers (2)
- Data Models (1)
- Education (2)
- GeoRaptor (13)
- GPS (1)
- Image Processing (2)
- Import Export (8)
- Licensing (2)
- LiDAR (1)
- Linear Referencing (4)
- Manifold GIS (3)
- Mapping (1)
- MySQL Spatial (7)
- Networking and Routing (including Optimization) (5)
- Open Source (18)
- Oracle Spatial and Locator (194)
- Partitioning (1)
- PostGIS (36)
- Projections (1)
- Published Articles (1)
- qGIS (1)
- Recommendations (1)
- Services (1)
- Software Change Log (1)
- Source Code (37)
- Space Curves (9)
- Spatial Database Functions (109)
- Spatial DB comparison (1)
- Spatial XML Processing (11)
- SQL Server Spatial (92)
- Standards (3)
- Stored Procedure (17)
- Tessellation or Gridding (10)
- Tools (2)
- Topological Relationships (1)
- Training (2)
- Triangulation (2)
STInsertN: Insert single vertex into a geometry
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
STUpdateN: Update (replace) a single vertex within a geometry object.
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
STUpdate: Replace all points equal to the supplied point with replacement point.
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
STDeleteN: Delete single vertex from geometry
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
STDelete: Deleting vertices in geometry objects
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
STFlipVectors: Normalize direction of linestring vectors
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
STConvertToLineString: Extract LineStrings in GeometryCollection to create LineString
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
STCogo2Line: Creating (Multi)LineStrings geometries from COGO XML instructions
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,
STLine2Cogo: Converting LineStrings to COGO XML
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
STVectorize: Break Linestring/Polygon elements into 2 point vectors (or 3 point circular curves)
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
Documentation
- MySQL Spatial General Functions
- Oracle LRS Objects
- Oracle Spatial Exporter (Java + pl/SQL)
- Oracle Spatial Object Functions
- Oracle Spatial Object Functions (Multi Page)
- PostGIS pl/pgSQL Functions
- SC4O Oracle Java Topology Suite (Java + pl/SQL)
- SQL Server Spatial General TSQL Functions
- SQL Server Spatial LRS TSQL Functions