## Top 5 Recent Articles

##### ARTICLES CATEGORIES

- Biography (1)
- Blog (41)
- Changes (1)
- Customers (1)
- Data Models (1)
- Education (2)
- General Software (21)
- Georaptor Blog (5)
- Image Catalog (2)
- Licensing (1)
- ManifoldGIS (3)
- MySQL Blog (4)
- MySQL Spatial (3)
- Networking and Routing (including Optimization) (3)
- Oracle Spatial (171)
- Philosophy (1)
- PostGIS (30)
- Press Releases (1)
- Source code (24)
- Space Curves (1)
- Spatial DB comparison (1)
- SQL (1)
- SQL Server Blog (58)
- SQL Server Spatial (General) (15)
- SQL Server Spatial (LRS) (37)
- Stored Procedure (2)
- Training (1)
- XML (5)

# COGO: Creating a stroked polygon from a circle’s centre x,y and radius

The relevant standards covering spatial data types within databases provide functionality at many levels (and miss some that is required by pratitioners like myself) from object definition through to API specification.

One area within those standards that has limited support within commercial GIS software and database implementations is the case of circular arcs (line and polygon boundary) and circles. Oracle Spatial has always supported them (though they aren’t that easy to work with for the newcomer). Some database implementations, like PostGIS 1.x, support circular arcs though not comprehensively; Microsoft’s SQL Server’s “strict” implementation of OGC SFS 1.1 does not support them at all.

Why do we need circular arcs and circles you may ask?

Where man (or woman if the generic English noun grates) has engineered structures in the natural world, those structures (buildings, roads, railways etc) use many Euclidean geometric forms in the definition. Thus we most often see straight lines defining rectangles and squares (or combinations thereof) in buildings, and we have always seen circles in buildings (think of the unglazed circular opening at the top of the Pantheon in Rome). The Sydney Opera House initially tried to use parabolas and ellipsoids to define the pre-cast segments of its “sail” roof – impossible mathematics and construction in pre-computing Sydney – before finally settling on segments derived from a much simpler spheres). Horizontal and vertical curves in roads and railways are just that: curves! In forestry, circular plots are often used when conducting in statistical inventory in the field.

Given all this, the reasons why there is such patchy support is perplexing. But that is for another day. But what is important to note is that some spatial software (not just SQL Server 2008) simply do not support them.

Many years ago I was required to expose circular forest inventory plots, stored in an Oracle database as as three columns in a table (long,lat and radius) into something the enterprise GIS mapping software could use to produce maps. That software did not support Oracle circles so we had to find a method for representation. We ended up using synchronized materialized views and a function I wrote in PL/SQL called CIRCLE2POLYGON (this is available in my free COGO package). Here is a version of that function for SQL Server 2008.

Note that I have a schema call **cogo** in which I create functions like this. You can use anything you like.

/** * @function : Circle2Polygon * @precis : Returns 2003 Polygon shape from Circle Centre XY and Radius * @version : 1.0 * @usage : FUNCTION Circle2Polygon ( @p_dCentreX float, * @p_dCentreY float, * @p_dRadius float, * @p_iSegments integer, * @p_srid integer, * @p_precision integer) * RETURNS GEOMETRY * eg select cogo.circle2polygon(100,100,5.0,12,0,3); * @param : p_dCentreX : X Ordinate of centre of Circle * @paramtype : p_dCentreX : FLOAT * @param : p_dCentreY : Y Ordinate of centre of Circle * @paramtype : p_dCentreY : FLOAT * @param : p_dRadius : Radius of Circle * @paramtype : p_dRadius : FLOAT * @param : p_iSegments : Number of arc (chord) segments in circle (+ve clockwise, -ve anti-clockwise) * @paramtype : p_iSegments : INTEGER * @param : p_srid : SRID of output shape * @paramtype : p_srid : INTEGER * @param : p_precision : Precision of any XY value ie number of significant digits. If null then 3 is assumed (ie 1 mm): 3456.2345245 -> 3456.235 * @paramtype : p_precision : INTEGER * @return : geometry : Polyon geometry with required rotation of outer shell. * @rtnType : geometry : GEOMETRY * @note : Does not throw exceptions * @note : Assumes planar projection eg UTM. * @history : Simon Greener - Feb 2005 - Original coding. * @history : Simon Greener - May 2011 - Converted to SQL Server * @copyright : Licensed under a Creative Commons Attribution-Share Alike 2.5 Australia License. (http://creativecommons.org/licenses/by-sa/2.5/au/) */ Create Function cogo.Circle2Polygon( @p_dCentreX float, @p_dCentreY float, @p_dRadius float, @p_iSegments integer, @p_srid integer, @p_precision integer) Returns geometry etc

The function can be used to generate a coarse circle of 3 segments per 90 degree slice (4 quarters of circle to give 3 * 4 = 12 segments or slices) as follows:

select cogo.circle2polygon(100,100,5.0,12,0,3);

Which looks like this:

Or, having a bit of fun:

select cogo.circle2polygon(100,100, a.intValue/6 + 5.0, a.intValue, 0,3) from dbo.generate_series(144,0,-12) a;

select b.Radius, cogo.circle2polygon(100 + b.Radius/2, 100 + b.Radius/2, b.Radius, b.segments, 0,3) from (select (a.intValue/6 + 5.0) as Radius, a.intValue as segments from dbo.generate_series(144,0,-12) a ) b;

If anyone is interested in this function or would like me to create custom TSQL functions to meet your spatial business requirements, please contact me.

## Documentation

- MySQL Spatial General Function Documentation
- Oracle Spatial Exporter Package Documentation
- Oracle Spatial Object Function Documentation
- Oracle Spatial Object Function Documentation (Multi Page Version)
- PostGIS pl/pgSQL Function Documentation
- SC4O Oracle Java Topology Suite (Stored Procedures) Package Documentation
- SQL Server Spatial General TSQL Function Documentation
- SQL Server Spatial LRS TSQL Function Documentation