SpatialDB Advisor
|
Current Oracle Spatial Blog Articles • isValid, isSimple, Dimension and CoordDim methods for SDO_Geometry • Line Merging or Collecting lines together: ST_LineMerger • ST_RemovePoint for Oracle SDO_Geometry based on Jaspa/JTS • 3D/4D and SRID aware Conversion functions for SDO_Geometry: WKT and EWKT • Topological vs Non-Topological Simplification/Generalization of Aggregated Area Geometies in Oracle • Filtering very short linestrings via bitmap function index • CENTROID For Oracle • Gridding a sdo_geometry line/polygon object (Oracle) • Finding centre and radius of a circular geometry • Constraining geometry type for sdo_geometry column in a table. • CASE Statements and SDO_GEOMETRY • The Power of Constraints and Indexes for Spatial Constraints: stopping duplicate points • SURVEY: The Future of GeoRaptor • Replacement for SDO_GEOM.RELATE - JTS Relate • Changing Oracle Spatial Index Parameters on existing index • Writing Excel Spreadsheets files from within the Oracle database using Java and PL/SQL • Writing xSV (eg csv) files from within the Oracle database using Java and PL/SQL • A simple spike finder for Spatial/Locator • JTS Java class compilation for 11g and above • Random Spatial Search Procedure • Geometry Snapping using JTS in Oracle • Exposing JTS's MinimumBoundingCircle functionality • Exposing JTS's Densifier functionality • Using JTS's Comparison Functions - HausdorffSimilarityMeasure & AreaSimilarityMeasure with SDO_GEOMETRY • Free JTS-based Area/Length Functions • Handy way of systematically fixing polygon geometries with 13349 and other errors • Standalone CENTROID package now available for download • Free Union, Intersection, Xor and Difference Functions for Oracle Locator - Part 4 Processing Geodetic data • Configurable Buffer: JTS and Oracle • Free Union, Intersection, Xor and Difference Functions for Oracle Locator - Part 3 • Free Union, Intersection, Xor and Difference Functions for Oracle Locator - Part 2 • Free Union, Intersection, Xor and Difference Functions for Oracle Locator - Part 1 • Building Lines into Polygons in Oracle Locator • Saving Storage Space Part 1: Storage Effects of Sdo_Geometry Coordinate Precision • Finding Intersection Points between Line and Polygon • SDO2GeoJSON • Free version of sdo_length • Alternative to my SQL based GetNumRings function • External Tables and SDO_Geometry data. • layer_gtype keyword issue when indexing linear data on 11g • String Tokenizer for Oracle • Free Aggregate Method for Concatenating 2D Lines in Oracle Locator 10g • Reducing 5 Vertex Polygon to Optimized Rectangle • Square Buffer • GeoRaptor 3.0 Officially released. • Converting decimal seconds to string • SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT - 13356 Issues • Valid conversion unit values for Oracle sdo_geom.sdo_length() • Removing Steps in Gridded Vector Data - SmoothGrid for Oracle • Oracle Spatial DISJOINT search/filtering • Creating SDO_Geometry from geometric data recorded in the columns of a table • Concave Hull Geometries in Oracle 11gR2 • Projecting SDO_GEOM_METADATA DIMINFO XY ordinates • Instantiating MDSYS.VERTEX_TYPE • New PL/SQL Packages - Rotate oriented point • GeoRaptor Development Team • Fast Refreshing Materialized View Containing SDO_GEOMETRY and SDO_GEOM.SDO_AREA function • Performance of PL/SQL Functions using SQL vs Pure Code • Implementing the BEST VicGrid Projection in Oracle 10gR2 • Making Sdo Geometry Metadata Update Generic Code • ORA-13011 errors when using SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT() • Extract Polygons from Compound Polygon • Detecting sdo_geometries with compound (3-point Arcs) segments • GEOMETRY_COLUMNS for Oracle Spatial • Convert GML to SDO_Geometry in Oracle 10gR2 • Spatial Sorting of Data via Morton Key • Swapping Ordinates in an SDO_GEOMETRY object • New To_3D Function • Extend (Reduce/Contract/Skrink) Function for Oracle • Loading and Processing GPX 1.1 files using Oracle XMLDB • Loading Spatial Data from an external CSV file in Oracle • Calling the Oracle Spatial shapefile loader from within the Oracle database itself • Converting Google Earth Formatted Longitude/Latitude points to decimal degrees • Implementing SDO_VertexUpdate/ST_VertexUpdate for Oracle • Implementing SDO_RemovePoint/ST_RemovePoint for Oracle • Implementing SDO_AddPoint/ST_AddPoint for Oracle • ESRI ArcSDE Exverted and Inverted Polygons and Oracle Spatial • Funky Fix Ordinates By Formula • Implementing a SetPoint/ST_SetPoint function in Oracle • Implementing an ST_SnapToGrid (PostGIS) function for Oracle Spatial • Generating random point data • Implementing an Affine/ST_Affine function for Oracle Spatial • Implementing a Scale/ST_Scale function for Oracle Spatial • Implementing a Parallel/ST_Parallel function for linestring data for Oracle Spatial • Implementing a Rotate/ST_Rotate function for Oracle Spatial • Limiting table list returned when connecting to Oracle Database using ODBC • Filtering Rings (Oracle Spatial) • ST_Azimuth for Oracle: AKA Cogo.Bearing • Implementing a Translate/ST_Translate/Move function for Oracle Spatial • Elem_Info_Array Processing: An alternative to SDO_UTIL.GetNumRings and querying SDO_ELEM_INFO itself • Minumum Bounding Rectangle (MBR) Object Type for Oracle • How to extract elements from the result of an sdo_intersection of two polygons. • How to restart a database after failed parameter change • Fixing failed spatial indexes after import using data pump • generate_series: an Oracle implementation in light of SQL Design Patterns • Multi-Centroid Shootout • Oracle Spatial Centroid Shootout • On the use of ROLLUP in Oracle SELECT statements • Surrounding Parcels • Spatial Pipelining • Using Oracle's SDO_NN Operator - Some examples • Converting distances and units of measure in Oracle Locator • Split Sdo_Geometry Linestring at a known point • Forcing an Sdo_Geometry object to contain only points, lines or areas • Unpacking USER_SDO_GEOM_METADATA's DIMINFO structure using SQL • Generating multi-points from single point records in Oracle Spatial • Object Tables of Sdo_Geometry • Oracle Locator vs Oracle Spatial: A Reflection on Oracle Licensing of the SDO_GEOM Package • FAST REFRESHing of Oracle Materialized Views containing Sdo_Geometry columns • Australian MGA/AMG Zone Calculation from geographic (longitude/latitude) data • Loading Shapefiles (SHP) into Oracle Spatial • Oracle Spatial Mapping and Map Rendering Performance Tips • The significance of sdo_lb/sdo_ub in USER_SDO_GEOM_METDATA: Do I need it? • Oracle Spatial Forum - Melbourne April 2007 • Layer_GTypes for spatial indexes • Oracle's SQL/MM Compliant Types • Tips and Tricks
|
This article is about how three things: 1. The fact that the intersection between two polygon (area) can be a combination of points, lines and polygons (a *> sdo_geometry object). *> Firstly, here are two polygons that we will intesect using Oracle’s *> function:
Here is how to execute an intersection between our two polygons.
Note, the the result is a compound (or collection) object, composed of a line (1,2,1), a point (5,1,1) and a polygon with a single outer shell (7,1003,1) *> Often, we would like the result of the intersection to be three separate geometries so that we can extract one or more and use them in other processes. This can be achieved, if you have 10g, as follows:
However, if you only have 9i or earlier, you have to write a custom PL/SQL function such as the “Explode” function in my free GEOM package:
Which you would use as follows:
Now, what if we only wanted the polygon geometry from the result? Using 10g only this could be done as follows:
But, for 9i and below, this could be done in this way:
There is a fair bit of detail in these two different approaches to extracting a polygon. The detail can be wrapped up inside a PL/SQL function as in the *> function in my free PL/SQL packages:
Now, why would we want to extract only the polygon from the intersection of two polygons? All these things depend on the business problem the SQL is being developed to solve. But we could use the extracted polygon to generate a centroid of the intersecting area as in the following example (that uses the mentioned ExtractPolygon function):
*> I have mentioned the SDO_UTIL.EXTRACT function already in this article. We saw how we can use it to extract individual polygon objects from a collection. But what if we wanted to extract the *> elements within an SDO_Geometry object, how can we do this? The SDO_UTIL.EXTRACT function, and the documented description of the *> and *> parameters, is as follows:
*> *> _.> _.> _.> So, note that the definition of *> does not count the *> (inner ring). Holes need to be extracted via the *> parameter. The following SQL will show you this in reality:
Note that there are *> results: the first is all of the first element of the multipolygon including its outer shell (1005) and inner shell – hole – (2005), with the second and third being the extraction of the first element’s outer shell (1005) and inner shell (2005). I deliberately chose this polygon to hightlight a shortcoming in the sdo_util.extract() function. That is, it is unable to extract the sub-elements that make up a higher element. Thus, above, it cannot extract the individual arc types that make up the shells of the polygon elements. To do this we have to have recourse to some PL/SQL programming. I have done this in my free PL/SQL packages, encapsulating the result of my work in a function called ExtractElements (or ExtractElementsPiped). Here is it being used to “explode” the compound multi-polygon above into its constituent parts:
I hope this is helpful to someone. ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
![]()
![]() |
Comment [5]
Recently had to generate centroids for polygon data loaded from a GIS application. Turns out that some of the records where actually a collection of either point/polygon or line/polygon geometries. This resulted in no centroid being created. After a email chat with Simon, ended up saving myself a couple of hours work in not having to write a extract polygon routine, by just using the explode function from his Oracle package, and a simple select statement.
Thanks Simon keep up the good work.
Cheers
Jamie
— Jamie Keene · 24 November 2008, 10:37 · #
Thanks Simon, this has been a godsend. Its going to make clipping data to our boundary childsplay!
— Thomas Baxter · 3 December 2008, 15:46 · #
I’m pleased that you find this posting useful. Let me know if you have any implementation or use issues.
regards
Simon
— Simon Greener · 5 December 2008, 16:26 · #
Thanks for this! But is there an error in the section “Now, what if we only wanted the polygon geometry from the result? Using 10g” on line 8? (i.geometry) should be (i.geom) ???
— Mark · 1 July 2010, 05:05 · #
Quite right.
I have fixed it.
Thanks for noticing it.
Simon
— Simon · 1 July 2010, 13:08 · #