Introduction The ordinates stored in an geometry objects, across all spatial data types do not have any rounding applied to their values. This is one aspect of data management that is seldom considered by most practitioners. Other articles in this website deal with how to round their values. This article is about a related topic”Read More
This article shows how to create a GeoJSON Document from Selection of SDO_Geometry objects.
While there is always a need for software like Safe Software’s Awesome FME to automate import and export tasks from your database, the ability to do so just using Oracle can also be enormously useful. I have implemented the approach described below many times over the years, in different customer sites. At one customer site,Read More
Previously I created the following Java stored procedures to enable the import/export of ZM aware WKT. ST_GeomFromText ST_GeomFromEWKT ST_AsText ST_AsEWKT These functions are necessary if one wishes to exchange geometry data with users of other databases that support WKT functions for 2D, 3D or 4D (ZM). For example, PostGIS supports the EWKT format and providesRead 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
Recently, like many before me, I had need to create a function that converted a single SDO_GEOMETRY object to GeoJSON. The function I created is below. Note that this function: Does not support attributes (it could do via passing in a refCursor or table of record); Nor does nor does it address how to createRead More