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
|
I have implemented an SDO_SetPoint/ST_SetPoint (PostGIS) function for Oracle. But in so doing I discovered the SE_VertexUpdate(geom ST_LineString,old ST_Point, new ST_Point) function that IBM has implemented. The interesting difference is that the ST_SetPoint function requires you to supply the original geometry, the new point value and the position of the point in the existing geometry that you want to update: the VertexUpdate version simply requires you to provide the before and after point values. The problem with the PostGIS approach is apparent and explains why PostGIS has only implemented the function for LineString geometries. The reaons is that if you want to update a polygon geometry and can only supply a single point position, you can end up with a polygon that has its start and end points with different values. An example from my article shows this:
Note that you have to call the function twice AND know the position of the first and last coordinate. The alternate approach, implemented in the IBM function, is to provide actual values of the existing point and its replacement and to replace all possible old values with new values wherever they occur. My coding of such a function for Oracle is as follows. First, the declarations:
And the body:
(At 10gR2 a point does not have Z and M values.) Note that I continue to make extensive use of SQL in my functions. I find using SQL makes it easy to develop solutions in SQLPlus/SQL Developer and transfer into PL/SQL. It is most likely more efficient (in terms of processing resources) to manipulate the sdo_ordinate array directly in PL/SQL but the speed of development (and understanding to ordinary users) is most likely less than via straight SQL. I will investigate this aspect of algorithm development in a later article. Now, let’s run through some examples.
Conclusion I have to admin that, having implemented the PostGIS *_SetPoint functions and the IBM *_VertexUpdate functions, I think that the IBM versions are far better than the PostGIS ones because one does not have to worry about the complexity of start/end points for polygon geometry elements (inner and outer rings). I hope this article is of use to someone. ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
![]()
![]() |
Comment [6]
Simon,
Interesting point about *_SetPoint vs. *_VertexUpdate, though I can see the benefit in both approaches.
I think in some cases such as when you have duplicate vertexes, you may only want to set one or remove one, not both. Then again as you said the simplicity of vertexupdate is nice and is the common case.
One other observation — though has nothing to do with this so much.
You use mdsys.OGC_LineStringFromText
and
mdsys.OGC_PointFromText
I assume there is an
mdsys.OGC_GeomFromText.
Is there a penalty in oracle with using the POintFromText, LineFromText vs GeomFromText.
I tend to avoid using those in PostGIS ans just stick with ST_GeomFromText because there is a noticable speed penalty with the added checking that those do over the ST_GeomFromText and also its just more fluff to remember.
— Regina · 18 February 2009, 05:02 · #
Regina,
I agree with your comments about *_SetPoint and *_VertexUpdate both having benefits. My last paragraph was written too quickly: I should have described the benefits of both as you succinctly do in your second paragraph. (I am a big believer in “both/and” solutions rather than “either/or”.)
With regards to your latter comments, the Oracle mdsys.OGC_* functions are there to return true points, linestrings and polygons (+ multi*) as the standard Oracle constructors associated with their subtype in the ST_Geometry type hierachy produce ST_Geometries and not ST_Points etc. Constructing proper ST_LineStrings etc is important if one wants to access type-specific methods eg ST_InteriorRingN() of ST_LineString.
Only the OGC_LineFromText() etc functions do this hence why I use them.
I will, however, have a look at the performance issues and report back.
Thanks for commenting.
Simon
— Simon Greener · 18 February 2009, 11:01 · #
Interesting. So all Polygons, Lines and Points are not created the same.
Is there a reason why you would use ST_GeomFromText then to create a Polygon, Point etc except when stuffing in a collection?
I guess I’m so used to thinking in PostGIS terms where a Line is a Line regardless of which function you use to create it.
I should try this in SQL Server 2008. Hadn’t given it much thought.
— Regina · 19 February 2009, 20:07 · #
Hope this helps. regards Simonselect mdsys.st_geometry(sdo_geometry('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL)).st_numinteriorring() geom from dual;
Error starting at line 1 in command:
select mdsys.st_geometry(sdo_geometry('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL)).st_numinteriorring() geom
from dual
Error at Command Line:1 Column:102
Error report:
SQL Error: ORA-00904: "MDSYS"."ST_GEOMETRY"."ST_NUMINTERIORRING": invalid identifier
00904. 00000 - "%s: invalid identifier"
*Cause:
*Action:
select a.geom.st_numinteriorring() as geom
from (select mdsys.st_geometry(sdo_geometry('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL)) geom
from dual ) a;
Error starting at line 4 in command:
select a.geom.st_numinteriorring() as geom
from (select mdsys.st_geometry(sdo_geometry('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL)) geom
from dual ) a
Error at Command Line:4 Column:7
Error report:
SQL Error: ORA-00904: "A"."GEOM"."ST_NUMINTERIORRING": invalid identifier
00904. 00000 - "%s: invalid identifier"
*Cause:
*Action:
select a.geom.st_numinteriorring() as geom
from (select mdsys.st_polygon(sdo_geometry('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL)) geom
from dual ) a;
GEOM
----------------------
1
1 rows selected
select a.geom.st_numinteriorring() as geom
from (select mdsys.OGC_PolygonFromText('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL) geom
from dual ) a;
GEOM
----------------------
1
1 rows selected
select mdsys.OGC_PolygonFromText('POLYGON((2 2, 2 7, 12 7, 12 2, 2 2))',NULL).st_numinteriorring() geom
from dual;
GEOM
----------------------
1
1 rows selected
— Simon Greener · 19 February 2009, 20:46 · #
hiiii
i have to write a report about IBM primary function and i dnt knw what to write
can u gyz help me plz
— Silent girl · 6 November 2010, 23:28 · #
I am not sure what you mean by an “IBM primary function” but the DB2 Spatial Extender version of my function is called ST_ChangePoint (related ones are ST_RemovePoint and ST_AppendPoint – there is no ST_InsertPoint)
regards
Simon
— Simon Greener · 7 November 2010, 09:55 · #