SpatialDB Advisor
|
Current Oracle Spatial Blog Articles • Changing all DIMINFO sdo_tolerance values for all metadata records in one go. • Building Polygons from Incomplete Linestrings using ST_PolygonBuilder • Computing Cardinal Directions to nearby geometries • Intersecting two aggregated polygon layers with SC4O • Spatial and Oracle 12c • Update Triggers and SDO_GEOMETRY Equality • Duplicate Geometry data and Data Models • CENTROID package update • How to calculate cumulative length of a linestring • Useful Package of Wrapper Functions for Sdo_Util.AffineTransforms • Compute Location from known Lat/Long point using delta easting and northing in miles • SDO_AGGR_SET_UNION • Sorting SDO_GEOMETRY data using the ORDER BY clause of a SELECT statement • Creating linestrings (2002) from points (2001) • Rounding Coordinates or Ordinates in SDO_GEOMETRY • Effects of Sdo_Geometry Ordinate Precision on Performance • Effects of Sdo_Geometry Ordinate Precision on Storage • The Spatial filtering of geometries: The effect of tolerances on relationships • Application of Delaunay Triangulation and Inverse Distance Weighting (IDW) in Oracle for Soils Interpolation • Selecting all SDO_GTYPE values for all tables/sdo_geometry columns in a schema • CENTROID package - Tips for Use • Announcing the Spatial Companion For Oracle (SC4O) • Filtering Rings (Oracle Spatial) • Splitting a polygon using one or more linestrings • isValid, isSimple, Dimension and CoordDim methods for SDO_Geometry • Line Merging or Collecting lines together: ST_LineMerger • ST_DeleteVertex 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 - ST_Relate based on JTS • 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 / Spatial • 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 • 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
|
Over on the Oracle Spatial Forum at the Technology Network, Wojciech asked the following question:
8307, -- SDO_SRID
SDO_ORDINATE_ARRAY ( -77, -- Longitude 39 -- Latitude )
There is a function in the SDO_UTIL package – SDO_UTIL.POINT_AT_BEARING -that allows you to create a new point at a bearing and distance from a known point, but there is no function that allows one to compute a new point from an existing point using a delta distance in x and y. Obviously for projected data one can do this via Pythagoras on the X and Y ordinates but for geographic/geodetic there is no method available to do this accurately. You have to write it yourself. Which is what this blog article is all about. Approach Now, the function presented will only generate an approximate location for the new point but it may suffice for some. The approach requires us to convert miles into decimal degrees in both longitude and latitude at the actual location of the known point. Why? Because the length subtended by a degree of longitude changes as you move from the Equator to the Pole. And at any one point on the globe that length in longitude is different from that in latitude. So, how can I compute this value. The following method takes the starting point and creates two points a whole number of degrees of longitude and latitude away from it (in the case below 0.1 degrees). Then, Oracle’s sdo_geom.sdo_distance method is used to find out how many miles each of these decimal degree values subtends.
OK, now that we know the distances in miles we can compute the number of degrees of longitude and latitude covered by the required delta of 50 miles east and 30 miles north from that point.
We can compute the new point via the following SQL:
Now, let’s put this all together into a function.
Testing this we get:
Don’t forget that the ROUGHDISTCHECK is just a Pythagoras of the delta east and north on a flat plane. This approach isn’t all that accurate. Alternate method using SDO_UTIL POINT_AT_BEARING There is an alternate approach that writing this article reminded me was possible. And that is to use the SDO_UTIL.POINT_AT_BEARING function as follows:
That is, go either 90 degrees to the East for +Eastings and 0 degrees to the North for +northings (or -90/270 for -Eastings and 180 degrees south for -northings). Note that the distance difference between the two methods is 58.178 for my method and 58.571 for the method using the Oracle function. Knowing that a distance in longitude changes by latitude this may be affecting the second method as the conversion routine from Miles to Meters (SDO_UTIL.POINT_AT_BEARING requires distances in Meters) will not take this into account. Something could be done using spherical or spheroidal math, but you would have to approach me directly to see if I would be interested coding something. Anyway, I hope this is of help to someone. ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
![]()
![]() |
Comment