SDO_ELEM_INFO_ARRAY

Dear friends,
does anybody know how can I manage to update the SDO_ELEM_INFO_ARRAY(1,1003,1) to SDO_ELEM_INFO_ARRAY(1,3,1) in a Oracle Spatial geometry object?
Thank you very much for your help.
Rosa
null

Dan,
This didn't work when I tried it:
update gps_test a set a.geom.sdo_elem_info=mdsys.elem_info_array(1,3,1)
ERROR at line 1:
ORA-00904: invalid column name
I can update a single geometry this way:
create or replace procedure elem_info_proc as
myGeomIn MDSYS.SDO_GEOMETRY := null;
begin
select a.GEOM into myGeomIn from gps_test a;
myGeomIn.sdo_elem_info(1) := 1;
myGeomIn.sdo_elem_info(2) := 3;
myGeomIn.sdo_elem_info(3) := 1;
commit;
insert into gps_test_copy values(myGeomIn);
End;
And the resulting geometry is in another table.
This is no good for updating a table with more than one geometry.
Dave

Similar Messages

  • Ora-13033 Invalid data in the sdo_elem_info_array in sdo geometry object

    Hi,
    I am getting this error when I am creating spatial index on geometry.
    I suspect I have some problem with some rows of my geometry data. I have identified and fixed these problems so far. but I still getting error on spatial index creation.
    -emptry Gtype in some rows
    -wrong Gtype in some rows
    Complete Error.
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13249: internal error in Spatial index: mdidxrbd
    ORA-13249: iError in Spatial Index: index build fialed
    ORA-13200: Internal error RowID:AAANZE/AAFAAALFaAAP..... in spatial indexing
    ORA-13206: internal error [] while creating the spatial index
    ORA-13033: Invalid data in the sdo_elem_info_array in sdo geometry object
    ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
    I have line data for this table and below is the sample data.
    GEOMETRY(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
    SDO_GEOMETRY(2002, 2958, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(
    598520.994, 4837106.63, 598462.359, 4837164.63))
    SDO_GEOMETRY(2002, 2958, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(
    599229.43, 4837127.13, 599089.675, 4837264.62))
    SDO_GEOMETRY(2002, 2958, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(
    599280.002, 4837024.46, 599295.689, 4837048.09, 599296.21, 4837055.13, 599294.64
    5, 4837062.43, 599229.43, 4837127.13))
    SDO_GEOMETRY(2002, 2958, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(
    GEOMETRY(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
    599089.675, 4837264.62, 599028.567, 4837324.34))
    SDO_GEOMETRY(2002, 2958, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(
    595925.144, 4839146.42, 596002.765, 4839128.11, 596007.989, 4839126.85, 596013.5
    22, 4839123.09, 596056.926, 4839089.74, 596100.769, 4839065.62, 596106.694, 4839
    063.81, 596110.438, 4839064.27, 596115.548, 4839066.47, 596181.122, 4839135.22,
    596183.623, 4839140.59, 596183.706, 4839145.03, 596183.319, 4839148.15, 596181.1
    78, 4839152.64, 596174.794, 4839163.26, 596165.136, 4839174.75, 596143.191, 4839
    194.57))
    Please also note that I have correct dimension in "sdo user geom meta data" table and in my table.
    Any help is greatly appreciated.
    Rose

    Hi Rose
    If you take a look at the error message, you will find a line there that starts with ORA-13200
    ORA-13200: Internal error RowID:AAANZE/AAFAAALFaAAP
    This points to the ROW containing the geometry that triggers this error (described in the error message).
    So if you could post the geometry of that specific row that might help. Use the following sql statement:
    Select geometry from YOUR_TABLE_NAME WHERE ROWID = 'AAANZE/AAFAAALFaAAP';
    tx
    Luc

  • Spatial query w/ logical operators in a subquery on Linux using Oracle 1

    Hello...
    I'm being given XML that I need to parse and create SQL from it. Below my signature is the SQL that I generate (its a simple example) and can be more elaborate due to the logical operators (AND and OR) given in the XML.
    The problem that we're seeing is performance-based: when one of the logical operator queries is Spatial-based, like below. Running it in JDBC, the query never returns.
    The spatial query just by itself returns ~300 rows (takes approximately 0.2 seconds). The "PERCENTAGE" query by itself returns about ~40000 rows (takes approximately ~.8 seconds).
    If we run the query below with 2 non-spatial subqueries, the result returns and performance is very acceptable (~ 0.9 seconds)-- the result set is about 80000 rows.
    Thanks,
    Jim
    =========================
    SELECT
    COLUMN_WE_WANT , RESULTS
    FROM
    TABLE_A
    WHERE
    COLUMN_WE_WANT IN
    SELECT
    COLUMN_WE_WANT
    FROM
    TABLE_A
    WHERE
    SDO_OVERLAPBDYINTERSECT(TABLE_A.MY_SPATIAL_COLUMN,
    SDO_GEOMETRY(2003,
    4326,
    null,
    SDO_elem_info_array( 1 , 3 , 1 ),
    SDO_ORDINATE_ARRAY( lng_1,lat_1 , lng_2,lat_2 , lng_3,lat_3 , lng_4,lat_4 , lng_1,lat_1 )
    ) = 'TRUE'
    OR
    COLUMN_WE_WANT IN
    SELECT
    COLUMN_WE_WANT
    FROM
    TABLE_B
    WHERE
    SOME_PERCENTAGE_RATE_COLUMN < 90
    )

    Its difficult to comment without seeing the execution plan. You should trace this query to get a better idea of exactly what's happening.
    Depending on the complexity of the logical operators, I would look at doing this using set operations. So for an OR you might have...
    SELECT COLUMN_WE_WANT, RESULTS
    FROM TABLE_A
    WHERE COLUMN_WE_WANT IN (
         SELECT COLUMN_WE_WANT
         FROM TABLE_A
         WHERE SDO_OVERLAPBDYINTERSECT(TABLE_A.MY_SPATIAL_COLUMN,SDO_GEOMETRY(2003,4326,
         NULL, SDO_elem_info_array( 1 , 3 , 1 ),
         SDO_ORDINATE_ARRAY( lng_1,lat_1 , lng_2,lat_2 , lng_3,lat_3 , lng_4,lat_4 , lng_1,lat_1 ) )) = 'TRUE'
    UNION
         SELECT COLUMN_WE_WANT
         FROM TABLE_B
         WHERE SOME_PERCENTAGE_RATE_COLUMN < 90)For an AND, you would use INTERSECT.
    Edited by: Reggie to remove the extra INTERSECT

  • Spatial query w/ logical operators in a subquery on Linux using Oracle 10g

    Hello...
    I'm being given XML that I need to parse and create SQL from it. Below my signature is the SQL that I generate (its a simple example) and can be more elaborate due to the logical operators (AND and OR) given in the XML.
    The problem that we're seeing is performance-based: when one of the logical operator queries is Spatial-based, like below. Running it in JDBC, the query never returns.
    The spatial query just by itself returns ~300 rows (takes approximately 0.2 seconds). The "PERCENTAGE" query by itself returns about ~40000 rows (takes approximately ~.8 seconds).
    If we run the query below with 2 non-spatial subqueries, the result returns and performance is very acceptable (~ 0.9 seconds)-- the result set is about 80000 rows.
    Thanks,
    Jim
    =========================
    SELECT
    COLUMN_WE_WANT , RESULTS
    FROM
    TABLE_A
    WHERE
    COLUMN_WE_WANT IN
    SELECT
    COLUMN_WE_WANT
    FROM
    TABLE_A
    WHERE
    SDO_OVERLAPBDYINTERSECT(TABLE_A.MY_SPATIAL_COLUMN,
    SDO_GEOMETRY(2003,
    4326,
    null,
    SDO_elem_info_array( 1 , 3 , 1 ),
    SDO_ORDINATE_ARRAY( lng_1,lat_1 , lng_2,lat_2 , lng_3,lat_3 , lng_4,lat_4 , lng_1,lat_1 ) )
    ) = 'TRUE'
    OR
    COLUMN_WE_WANT IN
    SELECT
    COLUMN_WE_WANT
    FROM
    TABLE_B
    WHERE
    SOME_PERCENTAGE_RATE_COLUMN < 90
    )

    There is a spatial forum. You will likely have a far better experience there.

  • Can't display Georaster in Oracle Maps

    Please help!
    I'm trying to display a georaster in Oracle Maps, without success. The georasters in question display normally in PCI's Focus, eSpatial's iSMART, and MapBuilder preview, but nothing is display in Oracle Maps.
    I have copied jai_codec.jar, jai_core.jar, jai_imageio-1.1.2.jar into
    D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\lib. I don't get any errors in mapviewer.log set to finest (appended to bottom of post).
    I'm using AS 10.1.3.1.0, MapViewer 10.1.3.1 from patch 6453515, and the 10.1.0.3.1 enterprise database.
    In Oracle Maps I have this code:
         foi = new MVThemeBasedFOI('MOSAIC2','MOSAIC2');
         this.mapview.addThemeBasedFOI(foi);
    The georaster has spatial extents:
    SQL> SELECT g.GEORASTER.spatialextent FROM MOSAICS g WHERE g.MOSAICID=2;
    GEORASTER.SPATIALEXTENT(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO,
    SDO_GEOMETRY(2003, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_ARRAY(-83.5357, 31.4825, -83.5357, 31.472635, -83.5357, 31.462765, -83.52891, 31.462765, -83.522115, 31.462765, -83.522115, 31.472635, -83.522115, 31.4825, -83.52891, 31.4825, -83.5357, 31.4825))
    The spatial extent is in USER_SDO_GEOM_METADATA and is indexed:
    SQL> select * from USER_SDO_GEOM_METADATA where TABLE_NAME='MOSAICS';
    TABLE_NAME
    COLUMN_NAME
    DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)
    SRID
    MOSAICS
    GEORASTER.SPATIALEXTENT
    SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X', -180, 180, .0005), SDO_DIM_ELEMENT('Y', -90, 90, .0005))
    8307
    The georaster has metadata:
    select TO_CLOB(m.GEORASTER.METADATA) from MOSAICS m where m.MOSAICID=2;
    <georasterMetadata xmlns="http://xmlns.oracle.com/spatial/georaster">
    <objectInfo>
    <rasterType>21001</rasterType>
    <isBlank>false</isBlank>
    <defaultRed>1</defaultRed>
    <defaultGreen>2</defaultGreen>
    <defaultBlue>3</defaultBlue>
    </objectInfo>
    <rasterInfo>
    <cellRepresentation>UNDEFINED</cellRepresentation>
    <cellDepth>8BIT_U</cellDepth>
    <totalDimensions>3</totalDimensions>
    <dimensionSize type="ROW">
    <size>3947</size>
    </dimensionSize>
    <dimensionSize type="COLUMN">
    <size>2717</size>
    </dimensionSize>
    <dimensionSize type="BAND">
    <size>3</size>
    </dimensionSize>
    <ULTCoordinate>
    <row>0</row>
    <column>0</column>
    <band>0</band>
    </ULTCoordinate>
    <blocking>
    <type>REGULAR</type>
    <totalRowBlocks>8</totalRowBlocks>
    <totalColumnBlocks>6</totalColumnBlocks>
    <totalBandBlocks>3</totalBandBlocks>
    <rowBlockSize>512</rowBlockSize>
    <columnBlockSize>512</columnBlockSize>
    <bandBlockSize>1</bandBlockSize>
    </blocking>
    <interleaving>BIP</interleaving>
    <pyramid>
    <type>DECREASE</type>
    <resampling>NN</resampling>
    <maxLevel>5</maxLevel>
    </pyramid>
    <compression>
    <type>NONE</type>
    </compression>
    </rasterInfo>
    <spatialReferenceInfo>
    <isReferenced>true</isReferenced>
    <isRectified>true</isRectified>
    <SRID>8307</SRID>
    <spatialResolution dimensionType="X">
    <resolution>5e-006</resolution>
    </spatialResolution>
    <spatialResolution dimensionType="Y">
    <resolution>5e-006</resolution>
    </spatialResolution>
    <modelCoordinateLocation>UPPERLEFT</modelCoordinateLocation>
    <modelType>FunctionalFitting</modelType>
    <polynomialModel rowOff="0" columnOff="0" xOff="0" yOff="0" zOff="0" rowScale="1" columnScale="1" xScale="1" yScale="1"
    zScale="1">
    <pPolynomial pType="1" nVars="2" order="1" nCoefficients="3">
    <polynomialCoefficients>6296500.000000001 0 -200000</polynomialCoefficients>
    </pPolynomial>
    <qPolynomial pType="1" nVars="0" order="0" nCoefficients="1">
    <polynomialCoefficients>1</polynomialCoefficients>
    </qPolynomial>
    <rPolynomial pType="1" nVars="2" order="1" nCoefficients="3">
    <polynomialCoefficients>16707140 200000 0</polynomialCoefficients>
    </rPolynomial>
    <sPolynomial pType="1" nVars="0" order="0" nCoefficients="1">
    <polynomialCoefficients>1</polynomialCoefficients>
    </sPolynomial>
    </polynomialModel>
    </spatialReferenceInfo>
    <layerInfo>
    <layerDimension>BAND</layerDimension>
    <subLayer>
    <layerNumber>1</layerNumber>
    <layerDimensionOrdinate>0</layerDimensionOrdinate>
    <layerID>Not Specified</layerID>
    </subLayer>
    <subLayer>
    <layerNumber>2</layerNumber>
    <layerDimensionOrdinate>1</layerDimensionOrdinate>
    <layerID>Not Specified</layerID>
    </subLayer>
    <subLayer>
    <layerNumber>3</layerNumber>
    <layerDimensionOrdinate>2</layerDimensionOrdinate>
    <layerID>Not Specified</layerID>
    </subLayer>
    </layerInfo>
    </georasterMetadata>
    Nothing displays at any zoom level in Oracle Maps.
    The georaster has pyramids generated by:
    DECLARE
    gr sdo_georaster;
    BEGIN
    SELECT georaster INTO gr
    FROM MOSAICS WHERE MOSAICID = 2 FOR UPDATE;
    sdo_geor.deletePyramid(gr);
    sdo_geor.generatePyramid(gr, 'rLevel=5, resampling=NN');
    UPDATE MOSAICS SET georaster = gr WHERE MOSAICID = 2;
    COMMIT;
    END;
    The georaster validates:
    SQL> select sdo_geor.validateGeoraster(a.georaster),sdo_geor.schemaValidate(a.ge
    oraster) from MOSAICS a where MOSAICID=2;
    SDO_GEOR.VALIDATEGEORASTER(A.GEORASTER)
    SDO_GEOR.SCHEMAVALIDATE(A.GEORASTER)
    TRUE
    TRUE
    Thanks very much for any suggestions!
    -Bruce
    mapviewer.log from a session, set to "FINEST"
    Jan 25, 2008 5:24:16 PM oracle.lbs.mapserver.core.MapperConfig loadMapViewerConfig
    FINEST:
    Allowed IPs:
    Excluded IPs:
    Jan 25, 2008 5:24:16 PM oracle.sdovis.GlobalVisContext <clinit>
    WARNING: will use 96 as default dpi.
    Jan 25, 2008 5:24:16 PM oracle.lbs.mapserver.core.MapperConfig registerNSDataProviders
    FINEST: Non-Spatial Data Provider registered: defaultNSDP
    Jan 25, 2008 5:24:16 PM oracle.sdovis.SDataProviderMgr registerProvider
    INFO: Spatial Provider shapefileSDP has been registered.
    Jan 25, 2008 5:24:16 PM oracle.lbs.mapserver.core.MapperConfig registerSDataProviders
    FINEST: Spatial Data Provider registered: shapefileSDP
    Jan 25, 2008 5:24:17 PM oracle.sdovis.SRS <clinit>
    INFO: Using 96 as default dpi.
    Jan 25, 2008 5:24:18 PM oracle.sdovis.DBSRSCache loadGeodeticSrids
    FINEST: Number of geodetic srids loaded: 748.
    Jan 25, 2008 5:24:18 PM oracle.sdovis.CacheMgr2 init
    INFO: Spatial Data Cache opened. Region=SDOVIS_DATA.
    Jan 25, 2008 5:24:18 PM oracle.sdovis.CacheMgr2 init
    INFO:      max_cache_size=32 MB.
    Jan 25, 2008 5:24:18 PM oracle.sdovis.CacheMgr2 createSubRegion
    INFO: sub region sdovis_subreg_mvdemo_jdbc:oracle:thin:@jmsdb5:1521:jmsdb created in cache.
    Jan 25, 2008 5:24:18 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=mvdemo]
    Jan 25, 2008 5:24:18 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=mvdemo]
    Jan 25, 2008 5:24:18 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=mvdemo]
    Jan 25, 2008 5:24:18 PM oracle.sdovis.DBSRSCache loadGeodeticSrids
    FINEST: Number of geodetic srids loaded: 130.
    Jan 25, 2008 5:24:18 PM oracle.sdovis.CacheMgr2 createSubRegion
    INFO: sub region sdovis_subreg_grim_jdbc:oracle:thin:@odm2:1521:odm2 created in cache.
    Jan 25, 2008 5:24:18 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=grim]
    Jan 25, 2008 5:24:18 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=grim]
    Jan 25, 2008 5:24:18 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=grim]
    Jan 25, 2008 5:24:19 PM oracle.sdovis.DBSRSCache loadGeodeticSrids
    FINEST: Number of geodetic srids loaded: 130.
    Jan 25, 2008 5:24:19 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=wms]
    Jan 25, 2008 5:24:19 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=wms]
    Jan 25, 2008 5:24:19 PM oracle.lbs.mapserver.core.MapperPool addMapper
    INFO: added a mapper instance to the pool [data src=wms]
    Jan 25, 2008 5:24:19 PM oracle.lbs.mapserver.core.MapperConfig loadConfigFile
    INFO: Map Recycling thread started.
    Jan 25, 2008 5:24:19 PM oracle.lbs.mapserver.oms$ColdStart run
    INFO: *** Oracle MapViewer started. ***
    Jan 25, 2008 5:24:20 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:/private/scratch\. Cache root directory will be set to default root directory.
    Jan 25, 2008 5:24:20 PM oracle.sdovis.DBSRSCache register
    INFO: Loading SRS information from MDSYS.cs_srs (srid=8307).
    Jan 25, 2008 5:24:20 PM oracle.sdovis.DBSRSCache parseAndAdd
    FINER: Registering srs 8307, isGeodetic=true, unit=DECIMAL DEGREE
    Jan 25, 2008 5:24:21 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:/scratch/mapcache\. Cache root directory will be set to default root directory.
    Jan 25, 2008 5:24:21 PM oracle.sdovis.DBSRSCache register
    INFO: Loading SRS information from MDSYS.cs_srs (srid=8307).
    Jan 25, 2008 5:24:21 PM oracle.sdovis.DBSRSCache parseAndAdd
    FINER: Registering srs 8307, isGeodetic=true, unit=DECIMAL DEGREE
    Jan 25, 2008 5:24:21 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadAdapterClass
    INFO: D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\mapcache\adapterlibs\grim.USGS_DOQ.jar
    Jan 25, 2008 5:24:21 PM oracle.lbs.foi.FOIServer init
    INFO: *** Oracle Feature of Interest (FOI) Server started. ***
    Jan 25, 2008 5:24:21 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:21 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadAdapterClass
    INFO: D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\mapcache\adapterlibs\grim.USGS_DRG.jar
    Jan 25, 2008 5:24:21 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:21 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadAdapterClass
    INFO: D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\mapcache\adapterlibs\grim.USGS_URBAN.jar
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:/scratch/mapcache\. Cache root directory will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.sdovis.DBSRSCache register
    INFO: Loading SRS information from MDSYS.cs_srs (srid=8307).
    Jan 25, 2008 5:24:22 PM oracle.sdovis.DBSRSCache parseAndAdd
    FINER: Registering srs 8307, isGeodetic=true, unit=DECIMAL DEGREE
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadAdapterClass
    INFO: D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\mapcache\adapterlibs\wms.USGS_DOQ.jar
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadAdapterClass
    INFO: D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\mapcache\adapterlibs\wms.USGS_DRG.jar
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadAdapterClass
    INFO: D:\APPSVR\j2ee\MapViewer\applications\MapViewer10131\web\WEB-INF\mapcache\adapterlibs\wms.USGS_URBAN.jar
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:/scratch/mapcache\. Cache root directory will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:/private/scratch\. Cache root directory will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:/scratch/mapcache\. Cache root directory will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.config.CacheInstanceConfig loadCacheStorageDef
    WARNING: Invalid cache root directory:D:APPSVRj2eeMapViewerapplicationsMapViewer10131webmapcache\. Cache root directory
    will be set to default root directory.
    Jan 25, 2008 5:24:22 PM oracle.lbs.mapcache.MCSServlet$ColdStart run
    INFO: *** Oracle MapCacheServer started. ***
    Jan 25, 2008 5:26:21 PM oracle.lbs.mapcache.MCSServlet doPost
    FINER: <request type="unknown request type" data_source="MVDEMO"/>
    Jan 25, 2008 5:26:21 PM oracle.lbs.mapcache.MCSServlet doPost
    FINER: <request type="unknown request type" data_source="MVDEMO"/>
    Jan 25, 2008 5:26:22 PM oracle.lbs.mapcache.MCSServlet doPost
    FINER: <request type="unknown request type" data_source="MVDEMO"/>
    Jan 25, 2008 5:26:22 PM oracle.lbs.mapcache.MCSServlet doPost
    FINER: <request type="unknown request type" data_source="MVDEMO"/>
    Jan 25, 2008 5:26:22 PM oracle.lbs.mapcache.MCSServlet doPost
    FINER: <request type="unknown request type" data_source="MVDEMO"/>
    Jan 25, 2008 5:26:59 PM oracle.lbs.foi.FOIServlet dumpURLParams
    FINEST: Servlet URL parameters (/foi):
    [width] [2048]
    [height] [1536]
    [theme] [grim.MOSAIC2]
    [dstsrid]
    [8307]
    [cachefoi] [yes]
    [bbox] [-84.1257287289893:30.988239674744463:-82.76821692338207:32.006373528949894]
    [request] [getfoi]
    [area] [no]
    [clickable] [yes]
    [version] [1.0]
    End of servlet URL parameters (/foi).
    Jan 25, 2008 5:26:59 PM oracle.lbs.foi.FOIServlet doPost
    FINEST: user making foi request: null
    Jan 25, 2008 5:26:59 PM oracle.lbs.mapserver.core.MapperPool getMapper
    FINER: getMapper(grim) begins...
    Jan 25, 2008 5:26:59 PM oracle.lbs.mapserver.core.MapperPool getMapper
    FINER: getMapper() succeeded.
    Jan 25, 2008 5:26:59 PM oracle.sdovis.DBMapMaker addPredefinedTheme
    FINEST: adding predefined theme [name=MOSAIC2]
    Jan 25, 2008 5:26:59 PM oracle.sdovis.ThemeTable getCommonAttributes
    FINEST: key_column using default: ROWID
    Jan 25, 2008 5:26:59 PM oracle.sdovis.ThemeTable getGeoRasterTheme
    FINER: Operation name: normalize
    Jan 25, 2008 5:26:59 PM oracle.sdovis.LoadThemeData run
    FINER: LoadThemeData running thread: Thread-37
    Jan 25, 2008 5:26:59 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINEST: Theme definition SRID: 8307
    Jan 25, 2008 5:26:59 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: Original query window: -84.1257287289893,30.988239674744463,-82.76821692338207,32.006373528949894
    Jan 25, 2008 5:26:59 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: [Query] select grt.GEORASTER from MOSAICS grt where grt.GEORASTER.rasterid = ?
    Jan 25, 2008 5:26:59 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: Fetch size: 10
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINEST: Data SRID: 8307
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer isDataWithinScale
    FINER: [Master scale] 0.06363336588783941 [Scale factor for theme MOSAIC2] 1.0
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer isDataWithinScale
    INFO: Screen resolution: 0.0027150236112144814
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: ULT offset: 0,0
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getSpatialResolution
    FINEST: Res X: 5.000000001587068E-6 Res Y: 5.000000001587068E-6 Pyramidlevel: 0
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINEST: Upper Left Model Coordinate: -83.5357 , 31.4825
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getSpatialResolution
    FINEST: Res X: 5.000000001587068E-6 Res Y: 5.000000001587068E-6 Pyramidlevel: 0
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getPyramidLevel
    FINEST: Pyramid level: 5 GeoRaster: 102.0 for screen resolution: 0.0027150236112144814
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getSpatialResolution
    FINEST: Res X: 1.6000000005078618E-4 Res Y: 1.6000000005078618E-4 Pyramidlevel: 5
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINEST: GeoRaster Dimension: width= 2717.0 height= 3947.0
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: [DimX] 83[DimY] 122
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: Converting to cell coordinate: [pyramidLevel] 5 [X] -84.1257287289893 [Y] 32.006373528949894
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getCellCoordinate
    FINEST: getCellCoordinate query: SELECT
    sdo_geor.getCellCoordinate(grt.GEORASTER,?,sdo_geometry(2001,8307,sdo_point_type(?,?,null), null,null)) coord FROM MOSAICS
    grt WHERE grt.GEORASTER.rasterid = ? and grt.GEORASTER.rasterdatatable = ?
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getCellCoordinate
    FINEST: Row:-3275 Column: -3688
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: Converting to cell coordinate: [pyramidLevel] 5 [X] -82.76821692338207 [Y] 30.988239674744463
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getCellCoordinate
    FINEST: getCellCoordinate query: SELECT
    sdo_geor.getCellCoordinate(grt.GEORASTER,?,sdo_geometry(2001,8307,sdo_point_type(?,?,null), null,null)) coord FROM MOSAICS
    grt WHERE grt.GEORASTER.rasterid = ? and grt.GEORASTER.rasterdatatable = ?
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeDefinition getCellCoordinate
    FINEST: Row:3089 Column: 4796
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: Calling JGeoRaster.getRasterImage - area: 0 , 0 , , 83 , 122
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINER: End of JGeoRaster.getRasterImage call.
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer performImageProcessing
    FINER: Operation name: normalize
    Jan 25, 2008 5:27:00 PM oracle.sdovis.theme.GeoRasterThemeProducer performImageProcessing
    FINER: Normalize operation.
    Jan 25, 2008 5:27:02 PM oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FINEST: # image loaded: 1
    Jan 25, 2008 5:27:02 PM oracle.lbs.mapserver.core.MapperPool freeMapper
    FINER: freeMapper() begins...
    Jan 25, 2008 5:27:02 PM oracle.lbs.foi.FOIServlet sendGZippedResponse
    FINEST: Sending FOI response in gzip format.

    Hi Bruce,
    for GeoRaster themes you can define a specific pyramid level to render, or you can leave the pyramid level null on the theme definition, and in this case MapViewer calculates the best level to render. The second option is recommended as it avoids loading unnecessary data given the current display parameters. If you are seeing your image get blocked, most likely at this zoom level and up you have reached the highest pyramid level of the GeoRaster. Even in MapBuilder if you keep zoom in, you get a blocked image after reaching the highest resolution level.
    Joao

  • MapBuilder Error:Can not find a GeoRaster object with specified rdt and rid

    Hello,
    I can't GeoRaster data in the preview of the MapBuilder and MapViewer. The GeoRasterViewer shows the Raster images without problems.
    MapBuilders error message:
    19.11.2008 13:07:11 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    SCHWERWIEGEND: GeoRaster load Exception:
    oracle.spatial.georaster.GeoRasterException: Can not find a GeoRaster object with specified rdt and rid.
         at oracle.spatial.georaster.JGeoRaster.validateConn(JGeoRaster.java:608)
         at oracle.sdovis.theme.GeoRasterThemeProducer$JGeoRasterGTP.<init>(GeoRasterThemeProducer.java:2037)
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:694)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    19.11.2008 13:07:11 oracle.sdovis.LoadThemeData run
    SCHWERWIEGEND: Exception fetching data for theme RAS_DGK.
    Message:GeoRaster load Exception: Can not find a GeoRaster object with specified rdt and rid.
    Description:
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:1109)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    19.11.2008 13:07:11 oracle.sdovis.MapMaker buildDataMBR
    WARNUNG: null MBR resulted from buildDataMBR.
    The errror message of MapViewer is nearly the same with some more informations about the spatial query and the coordintes of the query window. If I run that spatial query in the sqldeveloper it returns a result!
    I did following stebs:
    - saved a tiff-Image in a GeoRaster table with pyramid an tiled images.
    - checked the sdo_geom_metadata --> they are correct
    - checked the sdo_georaster object for the rdt table name and rasterid --> they are correct
    - checked the rdt table --> objects with that rid are saved
    - checked the mdsys.sdo_geor_sysdata table --> entry is correct
    - validate the geraster with the sdo_geor.validategeoraster function --> object is valid
    - updated the spatial extend of the image and try again the preview functio--> the same error
    The databse server is a virtual Linux server with Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit.
    The web server is a Window 2003 R2 Server with a weblogic server and mapviewer patch 5 (Ver1033p5_B081010).
    For a test I did the same (the same table script, the same raster data, the same import method) on a developer pc (WinXP Pro SP2) with Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 (32bit) the same mapbuilder version but with the MapViewer QuickStartKid and it works fine!!!
    Has anyone an idea?
    Greeting,
    Cord
    Edited by: Corti on Nov 19, 2008 2:14 PM

    Hi Joao,
    Thanks so far.
    I'm previewing a GeoRaster theme. I created it with the MapBuilder GeoRaster wizard. The theme difinition is (out of the export file):
    RAS_DGK|
    null|
    RAS_DGK|
    GEORASTER|
    <?xml version="1.0" standalone="yes"?>
    <styling_rules theme_type="georaster">
    </styling_rules>|
    (GeoRaster table name is "RAS_DGK", theme name is also "RAS_DGK")
    I get following log information:
    preview without a coordinate or scale:
    MapBuilder Error (as pop up): MAPVIEWER 01005: no spatial data to render
    log file:
    20.11.2008 10:17:27 oracle.sdovis.LoadThemeData run
    FEINER: LoadThemeData running thread: Thread-43
    20.11.2008 10:17:27 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: Original query window: -Infinity,-Infinity,NaN,NaN
    20.11.2008 10:17:27 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: [Query] select grt.GEORASTER, grt.GEORASTER.metadata.getClobVal() from RAS_DGK grt
    20.11.2008 10:17:27 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: Fetch size: 100
    20.11.2008 10:17:27 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    SCHWERWIEGEND: GeoRaster load Exception:
    oracle.spatial.georaster.GeoRasterException: Can not find a GeoRaster object with specified rdt and rid.
         at oracle.spatial.georaster.JGeoRaster.validateConn(JGeoRaster.java:608)
         at oracle.sdovis.theme.GeoRasterThemeProducer$JGeoRasterGTP.<init>(GeoRasterThemeProducer.java:2037)
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:694)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    20.11.2008 10:17:27 oracle.sdovis.LoadThemeData run
    SCHWERWIEGEND: Exception fetching data for theme RAS_DGK.
    Message:GeoRaster load Exception: Can not find a GeoRaster object with specified rdt and rid.
    Description:
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:1109)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    20.11.2008 10:17:27 oracle.sdovis.MapMaker buildDataMBR
    WARNUNG: null MBR resulted from buildDataMBR.
    preview with a center coordinate of the image and a scale:
    20.11.2008 10:18:43 oracle.sdovis.SRS getOptimalQueryWindow
    AM FEINSTEN: *** isGeodetic=false, unit=METER
    20.11.2008 10:18:43 oracle.sdovis.LoadThemeData run
    FEINER: LoadThemeData running thread: Thread-45
    20.11.2008 10:18:43 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: Original query window: 2550045.7746478873,5608500.0,2551954.2253521127,5609500.0
    20.11.2008 10:18:43 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: [Query] select grt.GEORASTER, grt.GEORASTER.metadata.getClobVal() from RAS_DGK grt WHERE MDSYS.SDO_FILTER(grt.GEORASTER.spatialextent, MDSYS.SDO_GEOMETRY(2003, 31466, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1, 1003, 3), MDSYS.SDO_ORDINATE_ARRAY(?,?,?,?)), 'querytype=WINDOW') = 'TRUE'
    20.11.2008 10:18:43 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: Fetch size: 100
    20.11.2008 10:18:43 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    SCHWERWIEGEND: GeoRaster load Exception:
    oracle.spatial.georaster.GeoRasterException: Can not find a GeoRaster object with specified rdt and rid.
         at oracle.spatial.georaster.JGeoRaster.validateConn(JGeoRaster.java:608)
         at oracle.sdovis.theme.GeoRasterThemeProducer$JGeoRasterGTP.<init>(GeoRasterThemeProducer.java:2037)
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:694)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    20.11.2008 10:18:43 oracle.sdovis.LoadThemeData run
    SCHWERWIEGEND: Exception fetching data for theme RAS_DGK.
    Message:GeoRaster load Exception: Can not find a GeoRaster object with specified rdt and rid.
    Description:
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:1109)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    20.11.2008 10:18:43 oracle.sdovis.DBMapMaker renderEm
    INFO: **** time spent on loading features: 234ms.
    20.11.2008 10:18:43 oracle.sdovis.RenderingEngine prepareForRendering
    AM FEINSTEN: xfm: 0.284 0.0 0.0 -0.284 -724212.9999999999 1593097.9999999998
    20.11.2008 10:18:43 oracle.sdovis.ImageRenderer renderGeoRasterTheme
    WARNUNG: GeoRaster theme RAS_DGK has no rendered images.
    20.11.2008 10:18:43 oracle.sdovis.VectorRenderer render
    FEINER: time to render theme RAS_DGK with 0 styled features: 0ms
    20.11.2008 10:18:43 oracle.sdovis.DBMapMaker renderEm
    INFO: **** time spent on rendering: 16ms
    If I run the sql statement in the log file, it returns a result.
    select grt.georid, grt.GEORASTER, grt.GEORASTER.metadata.getClobVal()
    from ras_dgk grt
    WHERE MDSYS.SDO_FILTER(grt.GEORASTER.spatialextent,
    MDSYS.SDO_GEOMETRY(2003, 31466, NULL,
    MDSYS.SDO_ELEM_INFO_ARRAY(1, 1003, 3),
    MDSYS.SDO_ORDINATE_ARRAY(2550045.7746478873,5608500.0,2551954.2253521127,5609500.0)), 'querytype=WINDOW') = 'TRUE';
    GEORID
    2
    GEORASTER
    MDSYS.SDO_GEORASTER(20001,MDSYS.SDO_GEOMETRY(2003,31466,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(2550000,5608000,2552000,5610000)),RDT_RAS_DGK,522,oracle.xdb.XMLType@194a7ec)
    GEORASTER.metadata.getClobVal()
    <georasterMetadata xmlns="http://xmlns.oracle.com/spatial/georaster">
    <objectInfo>
    <rasterType>20001</rasterType>
    <isBlank>false</isBlank>
    <defaultRed>1</defaultRed>
    <defaultGreen>1</defaultGreen>
    <defaultBlue>1</defaultBlue>
    </objectInfo>
    <rasterInfo>
    <cellRepresentation>UNDEFINED</cellRepresentation>
    <cellDepth>8BIT_U</cellDepth>
    <totalDimensions>2</totalDimensions>
    <dimensionSize type="ROW">
    <size>6299</size>
    </dimensionSize>
    <dimensionSize type="COLUMN">
    <size>6299</size>
    </dimensionSize>
    <ULTCoordinate>
    <row>0</row>
    <column>0</column>
    </ULTCoordinate>
    <blocking>
    <type>REGULAR</type>
    <totalRowBlocks>4</totalRowBlocks>
    <totalColumnBlocks>4</totalColumnBlocks>
    <rowBlockSize>2048</rowBlockSize>
    <columnBlockSize>2048</columnBlockSize>
    </blocking>
    <interleaving>BSQ</interleaving>
    <pyramid>
    <type>DECREASE</type>
    <resampling>NN</resampling>
    <maxLevel>6</maxLevel>
    </pyramid>
    <compression>
    <type>NONE</type>
    </compression>
    </rasterInfo>
    <spatialReferenceInfo>
    <isReferenced>true</isReferenced>
    <SRID>31466</SRID>
    <modelCoordinateLocation>UPPERLEFT</modelCoordinateLocation>
    <modelType>FunctionalFitting</modelType>
    <polynomialModel rowOff="0" columnOff="0" xOff="0" yOff="0" zOff="0" rowScale="1" columnScale="1" xScale="1" yScale="1" zScale="1">
    <pPolynomial pType="1" nVars="2" order="1" nCoefficients="3">
    <polynomialCoefficients>17668678.695368 0 -3.14949718277477</polynomialCoefficients>
    </pPolynomial>
    <qPolynomial pType="1" nVars="0" order="0" nCoefficients="1">
    <polynomialCoefficients>1</polynomialCoefficients>
    </qPolynomial>
    <rPolynomial pType="1" nVars="2" order="1" nCoefficients="3">
    <polynomialCoefficients>-8031218.31607409 3.14949718277477 0</polynomialCoefficients>
    </rPolynomial>
    <sPolynomial pType="1" nVars="0" order="0" nCoefficients="1">
    <polynomialCoefficients>1</polynomialCoefficients>
    </sPolynomial>
    </polynomialModel>
    </spatialReferenceInfo>
    <layerInfo>
    <layerDimension>BAND</layerDimension>
    <subLayer>
    <layerNumber>1</layerNumber>
    <layerDimensionOrdinate>0</layerDimensionOrdinate>
    <layerID>1</layerID>
    <colorMap>
    <colors>
    <cell value="0" blue="255" red="255" green="255" alpha="255"/>
    <cell value="1" blue="0" red="0" green="0" alpha="255"/>
    </colors>
    </colorMap>
    </subLayer>
    </layerInfo>
    </georasterMetadata>
    I checked also the content of rdt table and it contains entries with that raster id (= 522).
    Finally the log file when I use the preview directly on the GeoRaster table without a theme:
    20.11.2008 10:23:46 oracle.sdovis.LoadThemeData run
    FEINER: LoadThemeData running thread: Thread-55
    20.11.2008 10:23:46 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: Original query window: -Infinity,-Infinity,NaN,NaN
    20.11.2008 10:23:46 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: [Query] select grt.GEORASTER from RAS_DGK grt where grt.GEORASTER.rasterid = ? and grt.GEORASTER.rasterdatatable = ?
    20.11.2008 10:23:46 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    FEINER: Fetch size: 100
    20.11.2008 10:23:46 oracle.sdovis.theme.GeoRasterThemeProducer prepareData
    SCHWERWIEGEND: GeoRaster load Exception:
    oracle.spatial.georaster.GeoRasterException: Can not find a GeoRaster object with specified rdt and rid.
         at oracle.spatial.georaster.JGeoRaster.validateConn(JGeoRaster.java:608)
         at oracle.sdovis.theme.GeoRasterThemeProducer$JGeoRasterGTP.<init>(GeoRasterThemeProducer.java:2037)
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:694)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    20.11.2008 10:23:46 oracle.sdovis.LoadThemeData run
    SCHWERWIEGEND: Exception fetching data for theme RAS_DGK.
    Message:GeoRaster load Exception: Can not find a GeoRaster object with specified rdt and rid.
    Description:
         at oracle.sdovis.theme.GeoRasterThemeProducer.prepareData(GeoRasterThemeProducer.java:1109)
         at oracle.sdovis.GeoRasterTheme.prepareData(GeoRasterTheme.java:95)
         at oracle.sdovis.LoadThemeData.run(LoadThemeData.java:75)
    20.11.2008 10:23:46 oracle.sdovis.MapMaker buildDataMBR
    WARNUNG: null MBR resulted from buildDataMBR.
    If you need more information - please ask for it.
    Cord

  • How to find nearest point on polyline

    Hi,
    I have to find the nearest point to my standing point on a polyline. I have Oracle Locator installed, but my data is not in a locator format. Is it possible to do this by using Locator's functionality by for example puting the polyline and standing point coordinate values into a spatial type variable and calling some locator functionality?
    Or I have to coordinate data into a "spatial enabled" table, create spatial index etc and then call some Locator procedure.
    Tamas

    Luc,
    Thanks for the reference.
    When the data is converted, finding the nearest vertex in an sdo_geometry object could be done this way (of, of course, many):
    select f.vertex_id,f.dist,f.min_dist,f.a_vertex
      from (select p.vertex_id,
                   sdo_geom.sdo_distance(p.the_point,p.a_vertex,0.005) as dist,
                   min(sdo_geom.sdo_distance(p.the_point,p.a_vertex,0.005)) over (order by sdo_geom.sdo_distance(p.the_point,p.a_vertex,0.005) asc) as min_dist,
                   p.the_point,
                   p.a_vertex
              from (select t.id as vertex_id,
                           mdsys.sdo_geometry(2001,NULL,mdsys.sdo_point_type(358615,5407047,null),null,null) as the_point,
                           mdsys.sdo_geometry(2001,NULL,mdsys.sdo_point_type(t.x,t.y,t.z),null,null) as a_vertex
                      from table(sdo_util.getVertices(
                                MDSYS.SDO_GEOMETRY(2002,null,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,2,1),MDSYS.SDO_ORDINATE_ARRAY(362253.9,5409676.63,355608.12,5407615.16,358063.37,5407673.48,355276.53,5407361.08,360471.08,5408880.79,362483.4,5406024.69,362359.16,5408840.11,354570.21,5406219.18,360204.62,5405849.14,359214.51,5408283.5,358761.06,5406683.88,356739.05,5405590.46,358615.79,5407047.29,355978.02,5407326.33,356240.87,5409898.7,363159.35,5405510.46,358588.81,5406536.54,354822.42,5408643.75,357690.2,5408872.57,359839.29,5407253.86,355236.29,5409711.53,355342.54,5407448.87,360290.53,5405111.51,354677.02,5407916.83,361651.27,5409178.26,361730.18,5407553.5,357402.33,5409065.5,361546.51,5407278.41,361915.65,5408942.57,361974.74,5405464.91,357794.3,5406979.33,356106.58,5405481.32,357604.96,5407407.72,360718.31,5406765.8,359745.49,5406568.16,363005.29,5407557.46,355844.01,5407095.47,362749.66,5405041.82,359714.13,5408898.69,354509.69,5406113.6,360041.59,5406204.24,360380.17,5408751.21,356621.4,5409603.06,355156.27,5405401.98,354441.35,5409090.68,356376.45,5407472.81,363877.1,5405582.72,361883.83,5409696.17,356363.41,5406434.53,362078.96,5406617.37,362714.59,5409800.2,362703.49,5408513.33,358317.64,5408170.64,359294.27,5409197.53,360240.93,5406333.84))
                                )) t
                    ) p
            ) f
      where f.dist = f.min_dist;Hope this helps.
    Simon

  • How to find a second point on a line given a point and distance

    Hi All,
    My requirement is: Given a point on a line and distance, I have to find the second point. All geometries are in LRS.
    I tried using SDO_LRS.LOCATE_PT, it is returning the second point from the start of the segment but I want to locate the point from the given start point. Kindly suggest in how to solve this.
    SQL Used:
    SELECT SDO_LRS.LOCATE_PT(a.shape, m.diminfo, 9, 0)
    FROM lrs_access_fiber a, user_sdo_geom_metadata m
    WHERE m.table_name = 'LRS_ACCESS_FIBER' AND m.column_name = 'SHAPE' AND a.unique_id = 1996;
    Regards
    Venkat

    Hi Luc,
    Thanks for the information. I have implemented this in a slightly different way like:
    1. Firstly, found the distance (Distance_a of the point selected from the start point of the segment using:
    SELECT SDO_LRS.GET_MEASURE(SDO_LRS.PROJECT_PT(a.shape, m.diminfo,MDSYS.SDO_GEOMETRY(2301, 8307, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1, 1, 1), MDSYS.SDO_ORDINATE_ARRAY(xa,ya, NULL)) ), m.diminfo ) into Distance_a FROM LRS_ACCESS_FIBER a, user_sdo_geom_metadata m WHERE m.table_name = 'LRS_ACCESS_FIBER' AND m.column_name = 'SHAPE' AND a.unique_id = Input_Fiber_Id;
    2. Then added the given distance (b) to this computed distance (Distance_a ) to get the distance of the second point (Distance_b).
    Distance_b := abs (Distance_a + b);
    3. Then used SDO_LRS.LOCATE_PT with offset=0 and distance=Distance_b to get the second point.
    select SDO_LRS.LOCATE_PT(a.shape, distance_pt, 0) into point_geometry from LRS_ACCESS_FIBER a where a.unique_id = input_fiber_id;
    Please give your inputs and feedback.
    Regards
    Venkat

  • Calculating the length of the longest side of a polygon

    If you want to calculate the length of the longest side of a polygon -- for example a rectangle -- how can that be done using the standard geometrical functions of spatial in an oracle 10g2 database?
    SDO_LENGHT delivers the outline of the polygon. If have looked at the LRS functions, but could not come up with a combination that delivers me what I am looking for. Any suggestion is appreciated.

    What do you see as the longest side?
    Is that the longest stretch between 2 consecutive vertices?
    If this is the case, this sql could be of help, which could need maybe some optimisation and extension (calculates straigth distance between 2 consecutive vertices).
    select id, p_side_nr, p_side,  p_side_length
    from
    select id,  p_side_nr, p_side, sdo_geom.sdo_length(p_side, 0.005) p_side_length,  max(sdo_geom.sdo_length(p_side, 0.005)) over (partition by id) max_p_side_length
    from
    select id, p_side_nr,
           sdo_geometry(2002, NULL, NULL,
                 SDO_ELEM_INFO_ARRAY(1,2,1),
                 SDO_ORDINATE_ARRAY(startx, starty, endx, endy)
                ) p_side
    from
         select
               startp.id, startp.x startx, startp.y starty, startp.v_id p_side_nr, endp.x endx, endp.y endy, endp.v_id
         from
              select  s.id, t.id v_id, t.x, t.y
              from your_table_name s, table(sdo_util.getvertices(geometry)) t
              ) startp
              select s.id, t.id v_id, t.x, t.y
              from your_table_name s, table(sdo_util.getvertices(geometry)) t
              ) endp
         where startp.id = endp.id
         and startp.v_id = endp.v_id - 1
    ) where p_side_length = max_p_side_lengthif you do not need the geometry of that longest side, you could follow Ivan's suggestion as a shortcut by using Pythagoras.
    Edited by: lucvanlinden on Sep 2, 2008 7:48 PM

  • Get all vertices from a geometry of multiple polygons

    I tried to use sdo_util.GetVertices to retrieve all the vertices from a geometry column. Some of the geometries of gType 2007 that contains more than one element. The getVertices function seems to give back the vertices of the first element only. How can I get all the vertices then?
    Edited by: 937152 on May 29, 2012 11:56 AM

    Why do you have all the NULLs in your sdo_elem_info_array and sdo_ordinate_array? This is very very wrong - see http://docs.oracle.com/cd/E11882_01/server.112/e17766/e12700.htm#sthref3897
    Despite that I am able to get all the "vertices" back from your sample geometry - note that I changed your SELECT statement a little.
    jot_test@JOHNOT> create table assessment_parcel_merged (
      2  id number,
      3  geometry sdo_geometry);
    Table created.
    jot_test@JOHNOT>
    jot_test@JOHNOT> insert into assessment_parcel_merged
      2  (id, geometry)
      3  values
      4  (506833,
      5  mdsys.sdo_geometry(2007,82232,null,
      6  mdsys.sdo_elem_info_array(1,1003,1,13,1003,1,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null),
      7  mdsys.sdo_ordinate_array(632941.3695,5536245.0144,632939.95209944,5536241.97593627,633251.020958124,5536096.38289373,633369.443364573,5536040.95632826,633371.0274,5536043.9168,632941.3695,5536245.0144,631892.0616,5536736.1337,631892.8842984,5536702.62493823,632873.47478553,5536243.66593412,632884.740084103,5536267.81696815,632886.1576,5536270.8559,631892.0616,5536736.1337,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null)));
    1 row created.
    jot_test@JOHNOT>
    jot_test@JOHNOT> select sdo_geom.validate_geometry_with_context(geometry, 0.0005) as geom_validate
      2  from assessment_parcel_merged;
    GEOM_VALIDATE
    13033
    1 row selected.
    jot_test@JOHNOT>
    jot_test@JOHNOT> set null null
    jot_test@JOHNOT> select o.x, o.y
      2  from assessment_parcel_merged a, table(sdo_util.getvertices(a.geometry)) o
      3  where a.id = 506833;
             X          Y
    632941.37 5536245.01
    632939.952 5536241.98
    633251.021 5536096.38
    633369.443 5536040.96
    633371.027 5536043.92
    632941.37 5536245.01
    631892.062 5536736.13
    631892.884 5536702.62
    632873.475 5536243.67
    632884.74 5536267.82
    632886.158 5536270.86
    631892.062 5536736.13
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    null       null
    50 rows selected.John

  • How to get all the values of the SDO_ORDINATE_ARRAY of a Oriented Point

    Hi,
    I'm trying to get the values of a Geometry wich is an Oriented Point. To that, i'm using SDO_UTIL.GETVERTICES, but this utility only obtains the point X,Y, it doesn't obtain the values of the orientation vector.
    The Geometry is this:
    MDSYS.SDO_GEOMETRY(
         2001,8307,NULL,
         MDSYS.SDO_ELEM_INFO_ARRAY(1,1,1,3,1,0),
         MDSYS.SDO_ORDINATE_ARRAY(-75.586088632813272,6.1794352615514194,0.57278169530235967,-0.81970795380217887,0)
    The query is this:
    SELECT c.ipid, c.nombre, t.X, t.Y, t.Z, t.W
    FROM Hidrantes c,
    TABLE(SDO_UTIL.GETVERTICES(c.geometria)) t
    where c.ipid = 4691117
    ORDER BY c.ipid, t.id;
    Result:
    4691117          -75,5860886328133     6,17943526155142          (null) (null)
    As you can see, it only obtains the X,Y values but not the values of the orientation vector, how can I get the values?.
    Thanks in advance

    Tobonale,
    Sql-Only approaches:
    *[1] Return Oridinate Array*
    Append .SDO_ORDINATES to your geometry object or column name:
    SELECT MDSYS.SDO_GEOMETRY(
         2001,8307,NULL,
         MDSYS.SDO_ELEM_INFO_ARRAY(1,1,1,3,1,0),
         MDSYS.SDO_ORDINATE_ARRAY(-75.586088632813272,6.1794352615514194,0.57278169530235967,-0.81970795380217887,0)
    ).SDO_ORDINATES
    FROM dualResult:
    SDO_ORDINATE_ARRAY(-75.586089, 6.17943526, .572781695, -.81970795, 0)*[2] Return Flattened Oradinate Array*
    SELECT * FROM
    TABLE (
         MDSYS.SDO_GEOMETRY(
         2001,8307,NULL,
         MDSYS.SDO_ELEM_INFO_ARRAY(1,1,1,3,1,0),
         MDSYS.SDO_ORDINATE_ARRAY(-75.586088632813272,6.1794352615514194,0.57278169530235967,-0.81970795380217887,0)).SDO_ORDINATES
    )Result:
      -75.586089
      6.17943526
      .572781695
      -.81970795
               0Regards,
    Noel

  • GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

    Folks,
    I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
    GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
    via a download fro the GeoRaptor website.
    No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
    and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
    We are still looking for people to:
    1. Provide translations of the English dialog menus etc.
    2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
    you have found out all its functionality and quirks, contact us and offer to write a few pages of
    documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
    make screen captures and annotate with text.
    3. Conduct beta testing.
    Here are the things that are in the new release.
    New functionality:
    Overhaul of Validation Functionality.
    1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
    2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
    3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
       NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
       to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
    4. Main validation table allows:
       a. Sorting (click on column header) and
       b. Filtering.
       c. Copying to Clipboard via right mouse click sub menu of:
          - Geometry's SDO_ELEM_INFO array constructor.
          - SDO_GEOMETRY constructor
          - Error + validation string.
       d. Access to Draw/Zoom functions which were previously buttons.
       e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
          it can process - along with the ring / element that is host to the error (if it can) - and displays
          them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
          The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
       f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
       g. Table now has only one primary key column, and has a separate error column holding the actual error code.
       h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
       i. Optimisations added to improve performance for large error lists.
    5. Functionality now has its own validation layer that is automatically added to the correct view.
       Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
    Improved Rendering Options.
    1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
    2. Marking of SDO_GEOMETRY objects overhauled.
       - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
         option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
         could be shown as: <25> or {x,y} or <25> {x,y}
       - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
       - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
         edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
       - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
    3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
       rather than previously fixed markers.
    4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
    5. Positioning of the arrow for linestring/polygons has extra options:
       * NONE
       * START    - All segments of a line have the arrow positioned at the start
       * MIDDLE   - All segments of a line have the arrow positioning in the middle.
       * END      - All segments of a line have the arrow positioning in the END.
       * END_ONLY - Only the last segment has an arrow and at its end.
    ScaleBar.
    1. A new graphic ScaleBar option has been added for the map of each view.
       For geographic/geodetic SRIDs distances are currently shown in meters;
       For all SRIDs an attempt is made to "adapt" the scaleBar units depending
       on the zoom level. So, if you zoom right in you might get the distance shown
       as mm, and as you zoom out, cm/m/km as appropriate.
    2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
       to the map's right most status bar element.
    3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
       click menu.
    Export Capabilities.
    1. The ability to export a selection from a result set table (ie result of
       executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
       adds TAB file "wrapper" over SHP) has been added.
    2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
       added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
       automatically adds a field that holds a unique row number.
    3. When exporting to KML:
       * one can optionally export attributes.
       * Web sensitive characters < > & etc for KML export are replaced with &gt; &lt; &amp; etc.
       * If a column in the SELECTION or table/view/Mview equals "name" then its value is
         written to the KML tag <name> and not to the list of associated attributes.
         - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
    4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
    5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
       in GeoTools is corrected (working with GeoTools community to fix).
    6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
       Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
    7. Export directory is remembered between sessions in case a user uses a standard export directory.
    8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
       Example:
       SELECT a.geom.sdo_point as point
         FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
                 FROM DUAL) a;
       SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
         FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
    9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
       than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
       the number of points exported, and multipoints skipped will be displayed.
    10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
        However, this does not currently apply to the associated DBASE records.
    11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
        Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
        to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
    12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
        Please read the Oracle documentation on how to project your data is this is necessary. An example is:
        SELECT OBJECTID,
               CODIGO as name,
               NOME as description,
               MI_STYLE,
               SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
          FROM MUB.REGIONAL;
    13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
        circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
        to use this.
    Miscellaneous.
    1. Selection View - Measurement has been modified so that the final result only shows those geometry
       types that were actually measured.
    2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
       Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
    3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
    4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
       and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
       in map display): everything within that distance is returned.
    5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
       a preference.
    6. New View Menu options to switch all layers on/off
    7. Tools/Preferences/GeoRaptor layout has been improved.
    8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
       has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
       what the layer is set to being.
    9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
       and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
       In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
       right mouse click menu.
    10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
        has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
        index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
        which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
    Some Bug Fixes.
    * Error in manage metadata related to getting metadata across all schemas
    * Bug with no display of rowid in Identify results fixed;
    * Some fixes relating to where clause application in geometry validation.
    * Fixes bug with scrollbars on view/layer tree not working.
    * Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
      schema of the current user, as it could happen that a user opens the tree for another schema that
      has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
    * Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
      in a recordset.  Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
      register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
      column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row.  It appears
      that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
      cells in the row.
    * Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
    * Column based colouring of markers fixed
    * Bunch of performance improvements.
    * Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
    If you want to help with testing, contact us at our website.
    My thanks for help in this release to:
    1. John O'Toole
    2. Holger Labe
    3. Sandro Costa
    4. Marco Giana
    5. Luc van Linden
    6. Pieter Minnaar
    7. Warwick Wilson
    8. Jody Garnett (GeoTools bug issues)
    Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
    for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
    Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
    In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
    please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
    expressing ideas for future functionality and integration opportunities.
    regards
    Simon
    Edited by: sgreener on Jun 12, 2011 2:15 PM

    Thank you for this.
    I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
    I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
    I have stumbled to few bugs:
    1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
    I found this because in my language settings , is the decimal operators
    2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
    3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
    - if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
    Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
    4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

  • Imminent Release of new GeoRaptor Version

    Folks,
    I am pleased to announce, after 4 months of development and testing, that a new release of GeoRaptor should be released hopefully before
    the 2011 Oracle Spatial User Conference in Washington DC this Thursday 19th.
    The release manager will make that release but firstly we have to work out how to handle support for SQL Developer 2.1 (which a lot of you
    use) and 3.0 (which has recently been released). The reason for this is that the SQL Developer team changed some API calls such that
    we have to make separate compilations. We are not sure how to support these within the SQL Developer extensions distribution framework.
    It may be that we support download of the 3.0 version via the Oracle extension publication mechanism and the 2.1 version via direct download
    from our Sourceforge website. We will inform you when this has been resolved.
    No release notes have been compiled as the principal developer (oops, that's me!) will be leaving Australia tomorrow to attend the DC User Conference.
    More extensive notes (with images) will be compiled when I get back.
    We are still looking for people to:
    1. Provide translations of the English dialog menus etc.
    2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think you have found out all its functionality and quirks, contact
    us and offer to write a few pages of documentation on it. (Open Office or Microsoft Word is fine.)
    Here are the things that are in the next release.
    New functionality:
    Overhaul of Validation Functionality.
    1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
    2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
    3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
       NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
       to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
    4. Main validation table allows:
       a. Sorting (click on column header) and
       b. Filtering.
       c. Copying to Clipboard via right mouse click sub menu of:
          - Geometry's SDO_ELEM_INFO array constructor.
          - SDO_GEOMETRY constructor
          - Error + validation string.
       d. Access to Draw/Zoom functions which were previously buttons.
       e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
          it can process - along with the ring / element that is host to the error (if it can) - and displays
          them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
          The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
       f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
       g. Table now has only one primary key column, and has a separate error column holding the actual error code.
       h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
       i. Optimisations added to improve performance for large error lists.
    5. Functionality now has its own validation layer that is automatically added to the correct view.
       Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
    Improved Rendering Options.
    1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
    2. Marking of SDO_GEOMETRY objects overhauled.
       - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
         option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
         could be shown as: <25> or {x,y} or <25> {x,y}
       - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
       - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
         edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
       - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
    3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
       rather than previously fixed markers.
    4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
    5. Positioning of the arrow for linestring/polygons has extra options:
       * NONE
       * START    - All segments of a line have the arrow positioned at the start
       * MIDDLE   - All segments of a line have the arrow positioning in the middle.
       * END      - All segments of a line have the arrow positioning in the END.
       * END_ONLY - Only the last segment has an arrow and at its end.
    ScaleBar.
    1. A new graphic ScaleBar option has been added for the map of each view.
       For geographic/geodetic SRIDs distances are currently shown in meters;
       For all SRIDs an attempt is made to "adapt" the scaleBar units depending
       on the zoom level. So, if you zoom right in you might get the distance shown
       as mm, and as you zoom out, cm/m/km as appropriate.
    2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
       to the map's left most element in the status bar.
    3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
       click menu.
    Export Capabilities.
    1. The ability to export a selection from a result set table (ie result of
       executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
       adds TAB file "wrapper" over SHP) has been added.
    2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
       added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
       automatically adds a field that holds a unique row number.
    3. When exporting to KML:
       * one can optionally export attributes.
       * Web sensitive characters < > & etc for KML export are replaced with &gt; &lt; &amp; etc.
       * If a column in the SELECTION or table/view/Mview equals "name" then its value is
         written to the KML tag <name> and not to the list of associated attributes.
         - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
    4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
    5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
       in GeoTools is corrected (working with GeoTools community to fix).
    6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
       Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
    7. Export directory is remembered between sessions in case a user uses a standard export directory.
    8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
       Example:
       SELECT a.geom.sdo_point as point
         FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
                 FROM DUAL) a;
       SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
         FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
    9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
       than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
       the number of points exported, and multipoints skipped will be displayed.
    10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
        However, this does not currently apply to the associated DBASE records.
    11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
        Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
        to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
    12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
        Please read the Oracle documentation on how to project your data is this is necessary. An example is:
        SELECT OBJECTID,
               CODIGO as name,
               NOME as description,
               MI_STYLE,
               SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
          FROM MUB.REGIONAL;
    13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
        circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
        to use this.
    Miscellaneous.
    1. Selection View - Measurement has been modified so that the final result only shows those geometry
       types that were actually measured.
    2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
       Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
    3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
    4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
       and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
       in map display): everything within that distance is returned.
    5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
       a preference.
    6. New View Menu options to switch all layers on/off
    7. Tools/Preferences/GeoRaptor layout has been improved.
    8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
       has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
       what the layer is set to being.
    Some Bug Fixes.
    * Error in manage metadata related to getting metadata across all schemas
    * Bug with no display of rowid in Identify results fixed;
    * Some fixes relating to where clause application in geometry validation.
    * Fixes bug with scrollbars on view/layer tree not working.
    * Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
      schema of the current user, as it could happen that a user opens the tree for another schema that
      has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
    * Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
      in a recordset.  Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
      register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
      column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row.  It appears
      that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
      cells in the row.
    * Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
    * Column based colouring of markers fixed
    * Bunch of performance improvements.
    * Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
    If you want to help with testing, contact us at our website.
    regards
    Simon

    Hi buddy,
    > Yes, it is: Intel site not Toshiba, I'm sorry!
    No problem but not its clear what we talk about ;)
    > why Toshiba don't pretest latest driver and I must install it on my own risk? The last update is from 1,5 years ago...
    I think because Tecra A10 is older model and there is already a successor on the market, Tecra A11.
    Well, dont worry about this. Usually the Intel drivers also work. I have tested this on my Satellite U400 and its running with Intel display driver. No problems so installation is worth a try.
    Please send some feedback after Intel display driver installation, its really interesting! :)

  • Poor performance and increase CPU on UNIX 64 bit

    Hi
    I have moved one of my 300GB test databases from a 4GB RAM 2x DUAL zeon 3GHz processors LINUX machine to a UNIX 64 bit 6GB RAM 2x1GHz USIIIi processor machine. Both have the oracle data stored on RAID 5 disk.
    Both Oracle versions are the same. The data was transered via export/import.
    Running exactly the same queries the UNIX box is up to 3 times slower and sits at 100% CPU, wheras LINUX machine sits between 30-50% CPU and performance is really good. No other users are accessing the machines.
    Statspack reports look very similar, both have 100%/near 100% instance efficiency. top wait events on both machines are control file parallel write and db file sequential read, but even the values for these do not look worrying. The only difference is there is more memory allocated to the SGA of the UNIX server.
    Any ideas as to why the UNIX 64bit server is slower and using 100%CPU would be greatly received.
    Thanks

    LINUX
    SELECT
    count(*)
    FROM
    mastermap.topographicline
    WHERE
    descriptivegroup like :"SYS_B_00"
    and
    descriptiveterm like :"SYS_B_01"
    and
    physicalpresence = :"SYS_B_02"
    AND
    sdo_filter(geom, mdsys.sdo_geometry(:"SYS_B_03", :"SYS_B_04", null,
    mdsys.sdo_elem_info_array (:"SYS_B_05", :"SYS_B_06", :"SYS_B_07"),
    mdsys.sdo_ordinate_array (:"SYS_B_08", :"SYS_B_09", :"SYS_B_10",:"SYS_B_11")), :"SYS_B_12")=:"SYS_B_13"
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.00 0 2 0 0
    Execute 1 0.01 0.01 0 11 2 0
    Fetch 2 0.20 0.18 0 10713 0 1
    total 4 0.21 0.19 0 10726 2 1
    UNIX
    SELECT
    count(*)
    FROM
    mastermap.topographicline
    WHERE
    descriptivegroup like :"SYS_B_00"
    and
    descriptiveterm like :"SYS_B_01"
    and
    physicalpresence = :"SYS_B_02"
    AND
    sdo_filter(geom, mdsys.sdo_geometry(:"SYS_B_03", :"SYS_B_04", null,
    mdsys.sdo_elem_info_array (:"SYS_B_05", :"SYS_B_06", :"SYS_B_07"),
    mdsys.sdo_ordinate_array (:"SYS_B_08", :"SYS_B_09", :"SYS_B_10",:"SYS_B_11")), :"SYS_B_12")=:"SYS_B_13"
    call count cpu elapsed disk query current rows
    Parse 1 0.00 0.00 0 0 0 0
    Execute 1 0.03 0.02 0 42 2 0
    Fetch 2 0.24 0.34 0 10707 0 1
    total 4 0.27 0.36 0 10749 2 1
    The elapsed time is twice as slow on unix, and it seems to be a fetch issue. Any ideas?

  • CLOB as Storage for Ordinates?

    Hi,
    I have a table that has a column called COORDS it is a CLOB type.
    I want to make a query that uses these coordinates (example value -123,49,0,-123.5,49.5,0)
    my select statement doesn't work...
    select MDSYS.SDO_GEOMETRY(3002,8307,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,1002,1),MDSYS.SDO_ORDINATE_ARRAY(COORDS )
    from eelgrass
    But this works though..but I need it a more like above - I would like it as a view:
    select 'MDSYS.SDO_GEOMETRY(3002,8307,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,1002,1),MDSYS.SDO_ORDINATE_ARRAY(' || COORDS || '));'
    from eelgrass
    Is there an EVAL in oracle I can use for the COORDS column?
    thanks
    gordon
    Edited by: user520811 on Nov 27, 2008 6:03 AM
    Edited by: user520811 on Nov 27, 2008 7:20 AM

    Don't think you can do that directly in SQL, you probably have to go to pl/sql
    Example...
    CREATE TABLE clob_test (
    ID NUMBER,
    GEOMETRY MDSYS.SDO_GEOMETRY);
    INSERT INTO clob_test VALUES (
    1, SDO_GEOMETRY(2002, 2157, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(583887.231, 768049.448, 583983.61, 768005.606, 584010.988, 768030.582)));
    INSERT INTO user_sdo_geom_metadata VALUES ('clob_test','GEOMETRY', 
    MDSYS.SDO_DIM_ARRAY(MDSYS.SDO_DIM_ELEMENT('X',0,0,0.0005), MDSYS.SDO_DIM_ELEMENT('Y',500000,1000000,0.0005)), 2157);
    CREATE INDEX clob_test_spind ON clob_test(GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
    DECLARE
    l_coord CLOB;
    l_sql VARCHAR2(4000);
    l_count NUMBER;
    BEGIN
    l_coord := '583887.231, 768049.448, 583983.61, 768005.606';
    l_sql :=
         'SELECT COUNT(*)
         FROM clob_test
         WHERE SDO_ANYINTERACT(geometry,
         MDSYS.SDO_GEOMETRY(2002, 2157, null, MDSYS.SDO_ELEM_INFO_ARRAY(1, 2, 1),
         MDSYS.SDO_ORDINATE_ARRAY(' || l_coord ||' )))     = ''TRUE''';
         EXECUTE IMMEDIATE l_sql INTO l_count;
         DBMS_OUTPUT.PUT_LINE(l_count);
    END;
    /

Maybe you are looking for

  • Office 2013 (C2R) Connect to the server to view them

    I have an Outlook 2013 Click-to-Run installation (version 15.0.4641.1003) that will not download all emails from the server. At the bottom of folders it says, "There are more items in this folder on the server. Connect to the server to view them." Th

  • REPORT showing the RE contract status

    Hi All, Is there any report/table  in SAP REFX which shows the contracts status. Regards Sri

  • How to generate 10K invoices per day ?

    Dear All, My quary How are you doing then 10K invoice pre day in SAP , and how you maintain the system responce time I am working in a telcom company and every day we are generatirg moer then 10K invoice for handset and vouchers which contains 500K o

  • Getting sigill failure using Matlab exc_bad_access

    I keep getting this crash message while running a matlab script to preprocess 800 dicom images and turn them into png images. Process:         MATLAB [375] Path:            /Applications/MATLAB_R2013b.app/bin/maci64/../../Contents/MacOS/MATLAB_maci64

  • Currency translation code at transformations

    hi i ahve written this code for source currency to target currency usd based on system date. please and let me know any modifications nedd DATA : w_to_amt     TYPE /bi0/oiamount,            w_from_curr  TYPE /bi0/oicurrency,            calmonth type