Go to content Go to navigation and search

Home

Current Oracle Spatial Blog Articles

    Tip: Drop that Spatial Index!
    Convert Single Geometry to Multi-part Geometry in Oracle Spatial
    Optimized Rectangle to 5 Point Polygon
    Centroid Package now supports Y ordinate seeding
    Convert GeoJSON document to Sdo_Geometry objects
    Implementation Of Travelling Salesman Problem
    Create Polygon From Bearings And Distances
    Function That Returns a Compass Point From a Whole Circle Bearing
    Playing around with Centroids by using different seed values
    GeoRaptor 4.x Update 2
    Simple Oracle C Sprintf or Java String.format
    Some Oriented Point Functions
    Extracting Inner Rings Changed Ordinate Ordering: A Trap For Players Who Don't Read Documentation!
    PLS-00306: wrong number or types of arguments in call to 'SDO_GEOMETRY'
    Converting Google Earth Formatted Longitude/Latitude points to decimal degrees
    Oracle Business Intelligence Warehousing and Analytics - Spatial Summit
    How far inside, is inside? Measuring actual distance.
    Noding and building a polygon from single, overlapping linestrings
    Analyzing Spatial Query Performance Improvements in Oracle Spatial and Graph 12c Through Cross-Vendor Comparison
    ST_VertexN / ST_PointN - Extracting a specific point from any geometry
    Convert Single Point stored in SDO_ORDINATES to SDO_POINT_TYPE
    Aggregate APPEND Islands and XOR polygons
    Circular Arcs in Geodetic Polygons
    Some SDO_GEOMETRY/DIMINFO handling functions
    Applying And Extending Oracle Spatial - Book Released
    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 from points
    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
    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
    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
    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

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.

Loading Spatial Data from an external CSV file in Oracle

Friday February 20 2009 at 01:14

There have been many, many articles written on the web describing how to access external data (data held in operating system files not under the control of Oracle and not stored within its own datafiles and tablespaces) from within Oracle such that one can query the data using SQL.

In short, Oracle allows a user to access external data by wrapping a table definition over the top of the external data files and using its SQL loader and DataPump technologies to convert the data “on the fly” as users query it. As the Oracle documentation notes, this is a read-only table whose metadata is stored in the database but whose data in stored outside the database.

The table “wrapper” is achieved by using the CREATE TABLE statement to define the columns of the table in the normal manner, but the appending to the definition its physical_properties, in particular, the ORGANIZATION EXTERNAL clause.

This clause is made up of two dependent sub-clauses, the external_table_clause and the external_data_properties that allows you to specify the properties so described. For example, the TYPE clause of external_table_clause allows you to indicate the driver to be used to access external table’s data. Oracle database provides two access drivers: ORACLE_LOADER and ORACLE_DATAPUMP. Whereas the ACCESS PARAMETERS clause of “external_data_properties” allows you to describe the physical layout of the file (what type of delimiter, number of fields etc).

The best way to describe the external data loading capability of Oracle is to show you how to use it to load a small sample of LiDAR data (after it has been post-processed).

Firstly, we need to place our data in an operating system directory which Oracle can access, (in this example I have placed a file called ground.csv in C:\Temp\Lidar), and then create an Oracle Directory object and grant the user that will create and load the data (here my standard “CODESYS” user), read access on that directory.

-- Create directory that points to actual data file.
CREATE OR REPLACE DIRECTORY EXTERNAL_DATA_DIRECTORY AS 'C:\temp\lidar';

CREATE OR REPLACE DIRECTORY succeeded.

-- If create directory done by DBA as SYSTEM then you would need to grant the user doing the processing the ability to read from that directory via:
GRANT READ ON DIRECTORY EXTERNAL_DATA_DIRECTORY TO codesys;

GRANT READ succeeded.

Now we need to define our table object in Oracle. We also need to describe its external properties as part of the one definition.

DROP   TABLE lidar;

DROP   succeeded.

CREATE TABLE lidar(
  easting NUMBER,
 northing NUMBER,
   height NUMBER
)
ORGANIZATION EXTERNAL
(TYPE ORACLE_LOADER
DEFAULT DIRECTORY DATA_PUMP_DIR
ACCESS PARAMETERS (
         RECORDS DELIMITED BY NEWLINE 
         FIELDS TERMINATED BY ',' 
         MISSING FIELD VALUES ARE NULL 
         (easting, northing, height)
	)
LOCATION (EXTERNAL_DATA_DIRECTORY:'ground.csv'))
REJECT LIMIT UNLIMITED;

CREATE TABLE succeeded.

--Note that if our external file was TAB delimited we would use the following clause:
-- FIELDS TERMINATED BY 0x'09' 

Now we execute SQL SELECT statements against the table.

SELECT count(*) 
  FROM lidar;

COUNT(*)               
---------------------- 
40401                  

SELECT count(*)
  FROM lidar l
 WHERE l.easting  BETWEEN 478040  AND 478060
   AND l.northing BETWEEN 5228050 AND 5228070
   AND l.height   BETWEEN 200     AND 600;

1 rows selected
COUNT(*)               
---------------------- 
301                    

1 rows selected

I will now demonstrate that you cannot create spatial indexes on this table. Firstly, note that I have no SDO_GEOMETRY column in this table that I can index. However, I could try creating a function-based index (even though I doubt it would work because Oracle indexes normally contain ROWIDs that link the index to the actual row in the table holding the data. External tables do not have ROWIDs.)

It is worth noting the following from the Oracle documentation.

Restrictions on External Tables
External tables are subject to the following restrictions:

  • An external table cannot be a temporary table.
  • You cannot specify constraints on an external table.
  • An external table cannot have object type, varray, or LONG columns.

(I will look at the last limitation at the end of this article.)

Let’s create the function based index in the common manner, including the metadata.

-- Create Function that returns a point geometry so we can create a function-based index
--
create or replace function observation(p_srid in number,
                                       p_x    in number, 
                                       p_y    in number, 
                                       p_z    in number )
       return mdsys.sdo_geometry deterministic
Is
Begin
  Return MDSYS.SDO_GEOMETRY(3001,p_srid,mdsys.sdo_point_type(p_x,p_y,p_z),NULL,NULL);
End observation;
/
show errors

function observation(p_srid Compiled.
No Errors.

-- Generate sdo_geom_metadata entry
--
DELETE FROM USER_SDO_GEOM_METADATA
      WHERE table_name = 'LIDAR';

1 rows deleted
COMMIT;

COMMIT succeeded.

-- Generate USER_SDO_GEOM_METADATA entry based on actual extent of data in external table.
DECLARE
  v_minx Number;
  v_maxx Number;
  v_miny Number;
  v_maxy Number;
  v_minz Number;
  v_maxz Number;
BEGIN
  SELECT min(easting),max(easting),min(northing),max(northing),min(height),max(height)
    INTO      v_minx,      v_maxx,       v_miny,       v_maxy,     v_minz,     v_maxz
    FROM LIDAR;
  INSERT INTO USER_SDO_GEOM_METADATA(
    TABLE_NAME,
    COLUMN_NAME,
    DIMINFO,
    SRID
    ) VALUES (
    'LIDAR',
    'OBSERVATION(28355,EASTING,NORTHING,HEIGHT)',
    MDSYS.SDO_DIM_ARRAY(
      MDSYS.SDO_DIM_ELEMENT('X',v_minx,v_maxx,0.005),
      MDSYS.SDO_DIM_ELEMENT('Y',v_miny,v_maxy,0.005),
      MDSYS.SDO_DIM_ELEMENT('Z',v_minz,v_maxz,0.005)
      ),
    28355
  );
END;
/
SHOW ERRORS

anonymous block completed
No Errors.

COMMIT;

COMMIT succeeded.

-- Let's check to make sure the entry has been created
SELECT TABLE_NAME,COLUMN_NAME,DIMINFO 
  FROM USER_SDO_GEOM_METADATA 
 WHERE TABLE_NAME = 'LIDAR';

TABLE_NAME COLUMN_NAME                                DIMINFO
---------- ------------------------------------------ --------------------------------------------------------------------------------------------------------------------------------------------------------------
LIDAR      OBSERVATION(28355,EASTING,NORTHING,HEIGHT) MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT(X,478000,478100,0.005),MDSYS.SDO_DIM_ELEMENT(Y,5228000,5228100,0.005),MDSYS.SDO_DIM_ELEMENT(Z,1.019,1999.959,0.005))

1 rows selected

-- Now try and create an index on this function

DROP INDEX LIDAR_GEOM;

Error starting at line 84 in command:
DROP INDEX LIDAR_GEOM
Error report:
SQL Error: ORA-01418: specified index does not exist
01418. 00000 -  "specified index does not exist"

CREATE INDEX LIDAR_GEOM
       ON LIDAR(OBSERVATION(28355,EASTING,NORTHING,HEIGHT))
       INDEXTYPE is mdsys.spatial_index 
       parameters('sdo_indx_dims=2, layer_gtype=point');

Error starting at line 85 in command:
CREATE INDEX LIDAR_GEOM
       ON LIDAR(OBSERVATION(28355,EASTING,NORTHING,HEIGHT))
       INDEXTYPE is mdsys.spatial_index 
       parameters('sdo_indx_dims=2, layer_gtype=point')
Error at Command Line:86 Column:10
Error report:
SQL Error: ORA-30657: operation not supported on external organized table
30657.0000 -  "operation not supported on external organized table"
*Cause:    User attempted on operation on an external table which is
           not supported.
*Action:   Don't do that!

Don’t you love the recommended Action!

OK, so our external data of LiDAR points can really on read via full-table scans as one cannot create an index on an externally organized table.

If we want to spatially index we have to bring the data inside the database which we will now do.

-- Rename our existing LiDAR table to LiDAR_EXT
DROP TABLE lidar_ext;

Error starting at line 90 in command:
drop table lidar_ext
Error report:
SQL Error: ORA-00942: table or view does not exist
00942. 00000 -  "table or view does not exist"

RENAME lidar TO lidar_ext;

rename lidar succeeded.

CREATE TABLE lidar
AS 
SELECT sdo_geometry(3001,28355,sdo_point_type(easting,northing,height),null,null) as geom
  FROM lidar_ext;

create table succeeded.

-- Change column name in existing USER_SDO_GEOM_METADATA
UPDATE user_sdo_geom_metadata
   SET column_name = 'GEOM'
 WHERE table_name = 'LIDAR';

1 rows updated

COMMIT;

commit succeeded.

-- Now, rebuild index.
  DROP INDEX LIDAR_GEOM;

Error starting at line 104 in command:
DROP INDEX LIDAR_GEOM
Error report:
SQL Error: ORA-01418: specified index does not exist
01418. 00000 -  "specified index does not exist"

CREATE INDEX LIDAR_GEOM
       ON LIDAR(GEOM)
       INDEXTYPE is mdsys.spatial_index 
       parameters('sdo_indx_dims=2, layer_gtype=point');

CREATE INDEX succeeded.

DROP TABLE LIDAR_EXT;

DROP TABLE LIDAR_EXT succeeded.

So, now we can query the data.

SELECT count(*)
  FROM lidar l
 WHERE SDO_ANYINTERACT(l.geom,sdo_geometry(2003,28355,null,sdo_elem_info_array(1,3,3),sdo_ordinate_array(478040,5228050,478060,5228070))) = 'TRUE'
   AND l.geom.sdo_point.z BETWEEN 200 AND 600;

COUNT(*)
---------------------- 
301

1 rows selected

Data Other than Points

Our example is based on point data that is loaded into three numeric attributes rather than to an SDO_GEOMETRY object directly. As noted above:

  • An external table cannot have object type, varray, or LONG columns.

Instead of modifying my existing example to try and define the SDO_GEOMETRY object directly on the X, Y and Z fields in the CSV, I thought I would attempt to load the linear data associated with my article on executing shp2sdo from within the database.

The shp2sdo utility creates a SQL Loader control file with the actual data stored in-line inside the control file or externally in a data file. This is controlled by the “-d” parameter. I re-ran the tool so that I got the shapefile’s data in the separate data file. I the opened the CTL file, grabbed the load parameters and constructed an appropriate CREATE TABLE statement from it inside Oracle database. Here is that statement:

CREATE OR REPLACE DIRECTORY TEMP_DATA_DIRECTORY AS 'C:\temp';

-- GRANT READ ON DIRECTORY TEMP_DATA_DIRECTORY TO codesys;

CREATE TABLE GEODATA250K_TAS_ROADS 
   (	GID NUMBER(38,0), 
	CLASS VARCHAR2(20 BYTE), 
	FEATWIDTH VARCHAR2(20 BYTE), 
	NRN VARCHAR2(20 BYTE), 
	PID VARCHAR2(20 BYTE), 
	FEATREL VARCHAR2(20 BYTE), 
	FORMATION VARCHAR2(20 BYTE), 
	ATTRREL VARCHAR2(20 BYTE), 
	RETIRED VARCHAR2(20 BYTE), 
	SRN VARCHAR2(20 BYTE), 
	SOURCE VARCHAR2(20 BYTE), 
	SHAPE_LENG VARCHAR2(20 BYTE), 
	NAME VARCHAR2(20 BYTE), 
	TEXTNOTE VARCHAR2(20 BYTE), 
	FEATTYPE VARCHAR2(20 BYTE), 
	PLANACC VARCHAR2(20 BYTE), 
	SYMBOL VARCHAR2(20 BYTE), 
	CREATED VARCHAR2(20 BYTE), 
	PEANO NUMBER, 
	GEOM MDSYS.SDO_GEOMETRY
)
ORGANIZATION EXTERNAL
(TYPE ORACLE_LOADER
DEFAULT DIRECTORY TEMP_DATA_DIRECTORY
ACCESS PARAMETERS (
 CONTINUEIF NEXT(1:1) = '#'
 FIELDS TERMINATED BY '|'
 TRAILING NULLCOLS (
   GID INTEGER EXTERNAL,
   CLASS 	NULLIF CLASS = BLANKS,
   FEATWIDTH 	NULLIF FEATWIDTH = BLANKS,
   NRN 	NULLIF NRN = BLANKS,
   PID 	NULLIF PID = BLANKS,
   FEATREL 	NULLIF FEATREL = BLANKS,
   FORMATION 	NULLIF FORMATION = BLANKS,
   ATTRREL 	NULLIF ATTRREL = BLANKS,
   RETIRED 	NULLIF RETIRED = BLANKS,
   SRN 	NULLIF SRN = BLANKS,
   SOURCE 	NULLIF SOURCE = BLANKS,
   SHAPE_LENG 	NULLIF SHAPE_LENG = BLANKS,
   NAME 	NULLIF NAME = BLANKS,
   TEXTNOTE 	NULLIF TEXTNOTE = BLANKS,
   FEATTYPE 	NULLIF FEATTYPE = BLANKS,
   PLANACC 	NULLIF PLANACC = BLANKS,
   SYMBOL 	NULLIF SYMBOL = BLANKS,
   CREATED 	NULLIF CREATED = BLANKS,
   PEANO,
   GEOM COLUMN OBJECT 
   (
     SDO_GTYPE       INTEGER EXTERNAL, 
     SDO_SRID        INTEGER EXTERNAL, 
     SDO_ELEM_INFO   VARRAY TERMINATED BY '|/' 
       (X            FLOAT EXTERNAL), 
     SDO_ORDINATES   VARRAY TERMINATED BY '|/' 
       (X            FLOAT EXTERNAL) 
   )
)
)
LOCATION (TEMP_DATA_DIRECTORY:'GeoData250K_Tas_roads.dat'))
REJECT LIMIT UNLIMITED;

On execution this is what happened.

Error starting at line 4 in command:
CREATE TABLE GEODATA250K_TAS_ROADS 
   (	GID NUMBER(38,0), 
	CLASS VARCHAR2(20 BYTE), 
	FEATWIDTH VARCHAR2(20 BYTE), 
	NRN VARCHAR2(20 BYTE), 
	PID VARCHAR2(20 BYTE), 
	FEATREL VARCHAR2(20 BYTE), 
	FORMATION VARCHAR2(20 BYTE), 
	ATTRREL VARCHAR2(20 BYTE), 
	RETIRED VARCHAR2(20 BYTE), 
	SRN VARCHAR2(20 BYTE), 
	SOURCE VARCHAR2(20 BYTE), 
	SHAPE_LENG VARCHAR2(20 BYTE), 
	NAME VARCHAR2(20 BYTE), 
	TEXTNOTE VARCHAR2(20 BYTE), 
	FEATTYPE VARCHAR2(20 BYTE), 
	PLANACC VARCHAR2(20 BYTE), 
	SYMBOL VARCHAR2(20 BYTE), 
	CREATED VARCHAR2(20 BYTE), 
	PEANO NUMBER, 
	GEOM MDSYS.SDO_GEOMETRY
)
ORGANIZATION EXTERNAL
(TYPE ORACLE_LOADER
DEFAULT DIRECTORY TEMP_DATA_DIRECTORY
ACCESS PARAMETERS (
 CONTINUEIF NEXT(1:1) = '#'
 FIELDS TERMINATED BY '|'
 TRAILING NULLCOLS (
   GID INTEGER EXTERNAL,
   CLASS 	NULLIF CLASS = BLANKS,
   FEATWIDTH 	NULLIF FEATWIDTH = BLANKS,
   NRN 	NULLIF NRN = BLANKS,
   PID 	NULLIF PID = BLANKS,
   FEATREL 	NULLIF FEATREL = BLANKS,
   FORMATION 	NULLIF FORMATION = BLANKS,
   ATTRREL 	NULLIF ATTRREL = BLANKS,
   RETIRED 	NULLIF RETIRED = BLANKS,
   SRN 	NULLIF SRN = BLANKS,
   SOURCE 	NULLIF SOURCE = BLANKS,
   SHAPE_LENG 	NULLIF SHAPE_LENG = BLANKS,
   NAME 	NULLIF NAME = BLANKS,
   TEXTNOTE 	NULLIF TEXTNOTE = BLANKS,
   FEATTYPE 	NULLIF FEATTYPE = BLANKS,
   PLANACC 	NULLIF PLANACC = BLANKS,
   SYMBOL 	NULLIF SYMBOL = BLANKS,
   CREATED 	NULLIF CREATED = BLANKS,
   PEANO,
   GEOM COLUMN OBJECT 
   (
     SDO_GTYPE       INTEGER EXTERNAL, 
     SDO_SRID        INTEGER EXTERNAL, 
     SDO_ELEM_INFO   VARRAY TERMINATED BY '|/' 
       (X            FLOAT EXTERNAL), 
     SDO_ORDINATES   VARRAY TERMINATED BY '|/' 
       (X            FLOAT EXTERNAL) 
   )
)
)
LOCATION (TEMP_DATA_DIRECTORY:'GeoData250K_Tas_roads.dat'))
REJECT LIMIT UNLIMITED
Error at Command Line:24 Column:1
Error report:
SQL Error: ORA-30656: column type not supported on external organized table
30656.0000 -  "column type not supported on external organized table"
*Cause:    Attempt to create an external organized table with a column
           of type LONG, LOB, BFILE, ADT, or VARRAY.
*Action:   These column types are not supported, change the DDL.

Note, as per the documentation, “These column types are not supported”. For non-point geometry data you must use other methods for loading.

I hope this is useful to someone.

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 [2]

Hello, I am looking for list of companies worldwide who are feeding lidar data to Oracle Spatial.

It would be great if you could help me out. New to Oracle Spacial and need to do a research on how this product is being exploited by companies to provide better services and how successful they are doing so.

Thanks,

Victor Nair

— Victor Nair · 19 September 2009, 13:48 · #

Victor,

I would suggest you ask you question on the Oracle Spatial Forum

I have heard of people loading LiDAR into Oracle but I cannot see what business value it would have to a lot of organisations. In most of the work I have been involved with, the processed results of LiDAR data eg a Kriged surface represented as a 2D grid is of more use inside an Oracle database as it can then be combined with vector data, such as a polygon defining a business entity, to calculate new variables or measures such as average elevation etc.

Sorry I can not help you in any other way.

regards
Simon

Simon · 20 September 2009, 08:50 · #