Go to content Go to navigation and search

Home

Current SQL Server Blog Articles

    SQL Server Spatial: STFlipVectors
    SQL Server Spatial: Extract LineStrings in GeometryCollection to create LineString
    SQL Server Spatial: Converting a LineString to COGO XML
    SQL Server Spatial: Creating (Multi)LineStrings geometries from COGO XML instructions
    New Version of Package of TSQL Spatial Functions
    Vectorize/Segmentize SQL Server 2012
    Coordinate Editing Functions for SQL Server Spatial
    Function to Scale a geometry object for SQL Server Spatial
    TSQL String Tokenizer Function for SQL Server
    geography/geometry to MBR helper functions
    generate_series for SQL Server 2008
    Extract Polygons from result of STIntersection in SQL Server Spatial
    Function to round ordinates of a SQL Server Spatial geometry object
    Extract elements of SQL Server Spatial geometry object
    Counting number of polygon rings SQL Server Spatial
    Filtering Polygon Rings in SQL Server Spatial
    Function to Move a geometry object in SQL Server Spatial
    Alternate Centroid Functions for SQL Server Spatial
    Function to Rotate geometry objects in SQL Server Spatial
    A GetVertices wrapper for DumpPoints in SQL Server 2008 Spatial
    Creating a Morton number Space Key generator for SQL Server
    Gridding a geometry or geography object (SQL Server Denali)
    On hinting spatial indexes
    Random Search Procedure (SQL Server 2008 Spatial)
    COGO: Converting (Google Earth) Formatted Longitude/Latitude points to decimal degrees (SQL Server)
    COGO: Convert Degrees, Minutes and Seconds values to Decimal Degrees
    COGO: DD2DMS Formatting a latitude/longitude decimal degree value
    COGO: Create point from bearing and distance
    COGO: Compute number of vertices required to stroke circle or circular arc
    COGO: Calculating the bearing between two points (SQL Server 2008 Spatial)
    COGO: Compute arc length subtended by angle centre of circle
    COGO: Compute chord length of segment of a circle (arc)
    COGO: Computing Arc To Chord (Arc2Chord) Separation
    COGO: Creating a stroked polygon from a circle's centre x,y and radius
    COGO: Finding centre and radius of a curve defined by three points: FindCircle function
    Identifying Tight Radius Curves sections within LineString geometry data
    Generating random point data for SQL Server 2008 Spatial
    New Presentation on Active (Searchable) Spatial Metadata for SQL Server 2008 Spatial and FreeText
    Checking is a column in a table or a view is of type geometry or geography
    Extracting geometry type string values from geometry/geography objects in SQL Server 2008 Spatial
    Vectorising geometry objects in SQL Server 2008
    MBR to geography/geometry helper functions
    Extracting geometry types from geometry/geography objects in SQL Server 2008
    Getting the number of coordinate dimensions of a geometry/geography object in SQL Server 2008
    A Dump Points Function for SQL Server 2008 Spatial
    toGeography and toGeography Conversion Functions for SQL Server 2008 Spatial
    Write text file with spatial data from SQL Server 2008
    Loading Shapefiles into Geography type column in SQL Server 2008
    Tip #6: Correcting invalid geometries
    Tip #5: Where or where has my little column gone
    Tip #4: What Coordinate System is that?
    Tip #3: What object is that?
    Tip #2: Spatial Indexing and Primary Keys
    Tip #1: SQL Server 2008 "Katmai" - Setting SRIDs

Search

    Browse

RSS / Atom

Email me

textpattern

Creative Commons License
All Blog Articles, Data Models and Free Source Code by Simon Greener, The SpatialDB Advisor is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

geography/geometry to MBR helper functions

Thursday April 12 2012 at 00:50

Keywordsmbr lower left upper right x y access geometry geography sql server spatial
Summary

This article introduces two simple functions for returning the Minimum Bounding Rectangle (Mbr) of any geometry or geography object.

SQL Server Spatial’s STEnvelope() function returns the minimum bounding rectangle of a geometry object but as a 5 vertex polygon.

  1. SELECT geometry::STGeomFromText('POLYGON((2300 -700, 2800 -300, 2300 700, 2800 1100, 2300 1100, 1800 1100, 2300 400, 2300 200, 2100 100, 2500 100, 2300 -200, 1800 -300, 2300 -500, 2200 -400, 2400 -400, 2300 -700), (2300 1000, 2400  900, 2200 900, 2300 1000))',0).STEnvelope().STAsText() AS mbr;
  2. -- Results
  3. mbr
  4. POLYGON ((1800 -700, 2800 -700, 2800 1100, 1800 1100, 1800 -700))

To access the lower left and upper right XY ordinates requires use of the STPointN() and STX/STY methods against the relevant vertices of the polygon as follows:

  1. WITH MbrPoly AS (
  2.   SELECT geometry::STGeomFromText('POLYGON((2300 -700, 2800 -300, 2300 700, 2800 1100, 2300 1100, 1800 1100, 2300 400, 2300 200, 2100 100, 2500 100, 2300 -200, 1800 -300, 2300 -500, 2200 -400, 2400 -400, 2300 -700), (2300 1000, 2400  900, 2200 900, 2300 1000))',0).STEnvelope() AS mbr
  3. )
  4. SELECT a.mbr.STPointN(1).STX AS llx,
  5.        a.mbr.STPointN(1).STY AS lly,
  6.        a.mbr.STPointN(3).STX AS urx,
  7.        a.mbr.STPointN(3).STY AS ury
  8.   FROM mbrPoly AS a;
  9. -- Results
  10. llx lly urx ury
  11. 1800  -700  2800  1100

Which is long winded, indirect and error prone.

Why not wrap all this processing into a function? First for the geometry data type.

  1. USE [GISDB]  -- Change this to your database
  2. GO
  3. -- Create function
  4. --
  5. CREATE FUNCTION [dbo].[GEOMETRY2MBR] ( @p_geometry   geometry )
  6. RETURNS @TABLE TABLE
  7. (
  8.   minx       FLOAT,
  9.   miny       FLOAT,
  10.   maxx       FLOAT,
  11.   maxy       FLOAT
  12. )
  13. AS
  14. BEGIN
  15.    IF ( @p_geometry IS NULL )
  16.      RETURN;
  17.    INSERT INTO @TABLE ( minx, miny, maxx, maxy )
  18.    VALUES(@p_geometry.STEnvelope().STPointN(1).STX,
  19.           @p_geometry.STEnvelope().STPointN(1).STY,
  20.           @p_geometry.STEnvelope().STPointN(3).STX,
  21.           @p_geometry.STEnvelope().STPointN(3).STY);
  22.    RETURN;
  23. END;
  24. GO

Testing we get

  1. SELECT m.*
  2.   FROM [dbo].[GEOMETRY2MBR](geometry::STGeomFromText('POLYGON((2300 -700, 2800 -300, 2300 700, 2800 1100, 2300 1100, 1800 1100, 2300 400, 2300 200, 2100 100, 2500 100, 2300 -200, 1800 -300, 2300 -500, 2200 -400, 2400 -400, 2300 -700), (2300 1000, 2400  900, 2200 900, 2300 1000))',0)) AS m;
  3. -- Results
  4. minx  miny  maxx  maxy
  5. 1800  -700  2800  1100

What about geography objects? The SQL Server Spatial type system does not support the return of the Envelope (STEnvelope) of geography objects before 2012. While “rough and ready” we can still get an MBR of a geography object by a bit of casting…

  1. CREATE FUNCTION [dbo].[GEOGRAPHY2MBR] ( @p_geography geography )
  2. RETURNS @TABLE TABLE
  3. (
  4.   minx       FLOAT,
  5.   miny       FLOAT,
  6.   maxx       FLOAT,
  7.   maxy       FLOAT
  8. )
  9. AS
  10. BEGIN
  11.    DECLARE
  12.       @v_geometry geometry = dbo.toGeometry(@p_geography,0);
  13.    IF ( @p_geography IS NULL )
  14.      RETURN;
  15.    INSERT INTO @TABLE ( minx, miny, maxx, maxy )
  16.    VALUES(@v_geometry.STEnvelope().STPointN(1).STX,
  17.           @v_geometry.STEnvelope().STPointN(1).STY,
  18.           @v_geometry.STEnvelope().STPointN(3).STX,
  19.           @v_geometry.STEnvelope().STPointN(3).STY);
  20.    RETURN;
  21. END;
  22. GO

Testing it we get:

  1. SELECT m.*
  2.   FROM [dbo].[GEOGRAPHY2MBR](geography::Parse('Polygon((-10 -10, 10 -10, 10 10, -10 10,-10 -10))')) AS m;
  3. -- Results
  4. minx  miny  maxx  maxy
  5. -10 -10 10  10

Hope this helps someone out there.

Creative Commons License

post this at del.icio.uspost this at Diggpost this at Technoratipost this at Redditpost this at Farkpost this at Yahoo! my webpost this at Windows Livepost this at Google Bookmarkspost this to Twitter

Comment [1]

A very helpful little article. Thanks.

— Rik · 30 May 2012, 13:38 · #