Sdo_elem_info
I'm trying to query sdo_elem_info from a Spatial's geometry column. I can execute this query:
select a.shape.sdo_gtype from gen.us_states_spat a;
However, I cannot execute this query:
select a.shape.sdo_elem_info(1) from gen.us_states_spat a;
The error message says that I have an invalid column name.
Also, what is a good way to determine the number of values in the array?
Thanks!
DECLARE
v_shape MDSYS.SDO_GEOMETRY;
x NUMBER;
y NUMBER;
BEGIN
SELECT a.shape
INTO v_shape
FROM my.sdotable a
WHERE ...
x := v_shape.SDO_ELEM_INFO.COUNT;
y := v_shape.SDO_ELEM_INFO(1);
END;
Similar Messages
-
How to access sdo_geometry.sdo_elem_info with occi
if I use occi,how to access a varray of number(sdo_geometry.sdo_elem_info) in a table such as cola_markets.
Hi,
First check whether the given object is supported by streams are not by querying DBA_STREAMS_UNSUPPORTED.
If it is supported then we can set the negative rule to avoide the problematic column.
Thanks and Regards,
Satish.G.S
http://gssdba.wordpress.com -
Hi
I have following question:
In an Oracle Spatial Database I have to get the values located in the SDO_ELEM_INFO array. Does anyone have an example SQL statement on how to get the data stored in this array? Eventually we have to load the data into Java, code regarding this matter is also appreciated.
Regards
joHiya Jo. Try the following....this should work for you.
select a.geom.sdo_elem_info from table_name a;
where geom is the name given to the sdo_geometry column
in your spatial table "table_name". Hope this helps joe -
Hello,
I would like to select the data in the sdo_elem_info.
When I use this query:
select a.geom.sdo_elem_info
from test a where rownum =1
I get:
SDO_ELEM_INFO_ARRAY(1, 1003, 1, 605, 2003, 1)
I want to select it so it looks like this:
1|1003|1|605|2003|1
I have tried several ideas, and searched the archives.
None of these work:
select a.geom.sdo_elem_info(0)
from test a where rownum =1
select a.geom.sdo_elem_info_array(0)
from test a where rownum =1
select a.geom.sdo_elem_info.sdo_elem_info_array(0)
from test a where rownum =1
I am using sdo_util.getvertices to get the sdo_ordinates.
Any help is appreciated.
Thank you.
SHello
For plain SQL the difficulty is dealing with varying length of the array sdo_elem_info. This is how far I got. As you will see this will only return the concatenated first 3 elements.
In order to have it working in more flexible way you have to make some flexible Pivot table function.
So it is easier using the function of Dan.
select id,
max(decode(rn, 1, column_value)) || '|' ||
max(decode(rn, 2, column_value)) || '|' ||
max(decode(rn, 3, column_value)) elem_info
from
(select id, column_value,
row_number() over (partition by rowid order by rowid) Rn
from your_table r, table(r.GEOMETRY.SDO_ELEM_INFO)
) T
group by id
In case you're ok with a normal table record output, you can use Reggie's query or this one listing also the array position of the element for every feature.
select id, column_value,
row_number() over (partition by rowid order by rowid) position
from your_table r, table(r.GEOMETRY.SDO_ELEM_INFO)Luc -
Hi,
I like to select all sdo_geomeries from a table (with attribute geometry) where the sdo_elem_info_array equals (1,2,2). I tried statements like:
select * from table t
where t.geometry.sdo_elem_info = (1,2,2);
select * from table t
where t.geometry.sdo_elem_info = sdo_elem_info_array(1,2,2);
and all kind of other variations, but most of the time I receive the error message:
ORA-00932: inconsistent datatypes: expected - got MDSYS.SDO_ELEM_INFO_ARRAY
which is quite vague as it is not mentioning the expected datatype.
Does somebody knows the correct statement?
FrisoSdo_elem_info_array is a varray. You cannot compare varrays. You have to write your own function to compare the varrays.
-
SQL Load SDO_GEOMETRY, constant SDO_ELEM_INFO
Hi all,
I'm loading a large amount of spatial data, in the form of 2D polygons, into a 12c database.
All is fine when the SDO_ELEM_INFO data is in the data file. But I was hoping to find a way to express this as a constant VARRAY in the control file, rather than having to repeat the exact same data on every row in the data file.
Is there any way syntactically to do this in the control file?Many thanks, that works fine.
(Only works in conventional path though). -
Change SDO_ELEM_INFO (1,4,1,1,2,1) to (1,2,2) ?
Hi !
I'd like to change some records in the wrong SDO_ELEM_ARRAY
from the SDO_ELEM_INFO (1,4,1,1,2,1) to SDO_ELEM_INFO(1,2,2)
I've read doc from the link select/update sdo_elem_info where Sqreener has created a very 'nice' script to change SDO_ELEM.But it just can change the first 3 records in SDO_ELEM_INFO and it seems to be not right with my situation.
Thanks for any advice !!
Best regard!Assume your table schema
table test (geom sdo_geometry);
-- create a function to check if a given geometry is a candidate
create or replace function candidate_geometry(geom in sdo_geometry)
return varchar2 is
elem_info sdo_elem_info_array;
begin
if ( geom is null) then
return 'FALSE';
end if;
elem_info := geom.sdo_elem_info;
-- return 'TRUE' for the ones you want to update, 'FALSE' otherwise
if ( elem_info(1) = 1 and elem_info(2) = 4 and elem_info(3) = 1 and
elem_info(4) = 1 and elem_info(5) = 2 and elem_info(6) = 1) then
return 'TRUE';
else
return 'FALSE';
end if;
end candidate_geometry;
-- update the candidates with sdo_elem_info you want (1,2,2)
update test a set a.geom.sdo_elem_info = mdsys.sdo_elem_info_array(1,2,2)
where candidate_geometry(a.geom) = 'TRUE';
Similar post for changing srid can be found as follows:
Update GRAG table that is messy
jack -
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 -
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 > < & 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 PMThank 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 > < & 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
SimonHi 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! :) -
How to create geofence at the start of a geometry segment?
I want to create a geofence at the start (and end) of each of our road sections.
The geofence would extend exactly x(specified) metres at right angles to the segment direction at the start point.
Is there any Oracle functionality to construct a line (or 2 points) at right angles to a point on a line?
I can find the start point using this construction
SELECT SDO_LRS.GEOM_SEGMENT_START_PT(geom)
FROM ROAD_CENTRELINE_SDO WHERE id = 82;
The only way I have found of creating the geometry is by using some trigonometry to calculate the angle subtended and create two equidistant points. This is rather clumsy and I wondered if anyone knew how to do this more efficiently using Oracle Spatial functionality.
PhilipPhil,
I can understand that you found the packages complex. There is quite a bit of work gone into them over the years. Once you are over the install, and grow in your understanding of Spatial, you might find one or two of the functions quite useful. I am working on documentation... not enough hours in the day!
Wrt you immediate question.
Assuming that these two queries return the points you need:
SELECT SDO_LRS.LOCATE_PT(a.geom, 0, -7) FROM ROAD_CENTRELINE_SDO a
SELECT SDO_LRS.LOCATE_PT(a.geom, 0, 7) FROM ROAD_CENTRELINE_SDO a
Then, because these functions return a point in the sdo_ordinate_array and not in SDO_POINT, you should be able to construct a line as follows:
SELECT sdo_geometry(2002,l.SRID,NULL,sdo_elem_info_array(1,2,1),
sdo_ordinate_array(l.column_value.x,l.column_value.y,
r.column_value.x,r.column_value.y))
FROM ( SELECT a.ID, a.geom.sdo_srid as srid, b.*
FROM ROAD_CENTRELINE_SDO a,
TABLE( SDO_UTIL.GET_VERTICES( SDO_LRS.LOCATE_PT(a.geom,0,-7) ) )
) l,
( SELECT c.ID, c.geom.sdo_srid as srid, d.*
FROM ROAD_CENTRELINE_SDO c,
TABLE( SDO_UTIL.GET_VERTICES( SDO_LRS.LOCATE_PT(c.geom,0, 7) ) )
) r
WHERE r.id = l.id;I have not tested this as I do not have an operational LRS in place but it should work. Of course, if the SDO_LRS.LOCATE_PT returned the data in an sdo_point structure all this complexity could be avoided. But this approach does not require the construction of a function that returns an sdo_point from an sdo_geometry with a point coded in sdo_ordinate_array (which would be result in nicer SQL). If you coded a function that did this:
create or replace Function ToSdoPoint( p_geometry IN MDSYS.SDO_GEOMETRY )
RETURN MDSYS.SDO_GEOMETRY DETERMINISTIC
IS
v_element number;
v_elements number;
v_geometry MDSYS.SDO_Geometry;
v_SdoPoint MDSYS.SDO_Point_Type := MDSYS.SDO_Point_Type(0,0,NULL);
v_Ordinates MDSYS.SDO_Ordinate_Array;
Begin
IF ( MOD(p_geometry.sdo_gtype,10) not in (1,5) ) Then
v_geometry := NULL;
ELSIF p_geometry.sdo_point is not null THEN
v_geometry := mdsys.sdo_geometry(p_geometry.sdo_gtype,p_geometry.sdo_srid,p_geometry.sdo_point,NULL,NULL);
ELSE
v_ordinates := p_geometry.sdo_ordinates;
v_SdoPoint.X := v_ordinates(1);
v_SdoPoint.Y := v_ordinates(2);
IF ( FLOOR(p_geometry.sdo_gtype/1000) = 3 ) THEN
v_SdoPoint.Z := v_ordinates(3);
END IF;
v_geometry := mdsys.sdo_geometry(p_geometry.sdo_gtype,p_geometry.sdo_srid,v_SdoPoint,NULL,NULL);
END IF;
RETURN v_geometry;
END ToSdoPoint;
show errors
select toSdoPoint(mdsys.sdo_geometry(2001,null,null,
sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,2)))
from dual;Then the SQL becomes:
SELECT sdo_geometry(2002,SRID,NULL,sdo_elem_info(1,2,1),
sdo_ordinate_array(left.x,left.y, right.x,right.y)) as geom
FROM ( SELECT a.geom.sdo_srid as srid,
ToSdoPoint(SDO_LRS.LOCATE_PT(a.geom, 0, -7)) as left,
ToSdoPoint(SDO_LRS.LOCATE_PT(a.geom, 0, 7)) as right
FROM ROAD_CENTRELINE_SDO a )Hope this helps.
regards
Simon -
SPATIAL_RELATE DOES NOT WORK ON VIEW ?
Hi
The following statement does not work correct - it claims that there are no spatial indexes. The view is very complex (including union all). The view is put into user_sdo_geom_metadata.
Whats wrong ?
SELECT GEOM FROM MISE_A_JOURPFP3 WHERE FID=70491;
This returns
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2003, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 1005, 11, 1, 2, 1, 3, 2, 2, 7, 2, 1, 13, 2, 2, 17, 2, 1, 27, 2, 2, 31, 2, 1, 103, 2, 2, 107, 2, 1, 111, 2, 2, 115, 2, 1, 119, 2005, 10, 119, 2, 1, 125, 2, 2, 129, 2, 1, 131, 2, 2, 135, 2, 1, 163, 2, 2, 167, 2, 1, 169, 2, 2, 173, 2, 1, 177, 2, 2, 183, 2005, 3, 183, 2, 1, 191, 2, 2, 195, 2, 1), SDO_ORDINATE_ARRAY(575526,016, 184396,522, 575522,171, 184370,728, 575522,191, 184370,674, 575522,247, 184370,662, 575678,571, 184417,747, 575774,588, 184446,858, 575869,409, 184475,451, 575869,442, 184475,474, 575869,452, 184475,513, 575866,134, 184514,875, 575863,237, 184550,71, 575863,237, 184550,712, 575863,236, 184550,715, 575855,625, 184597,93, 575855,603, 184597,968, 575855,56, 184597,98, 575817,694, 184594,079, 575817,693, 184594,079, 575779,647, 184589,561, 575779,644, 184589,56, 575779,642, 184589,56, 575760,713, 184585,669, 575760,711, 184585,668, 575760,709, 184585,668, 575742,776, 184580,811, 575742,774, 184580,81, 575711,463, 184571,042, 575681,849, 1845
61,823, 575681,848, 184561,823, 575653,299, 184552,366, 575653,299, 184552,366, 575624,364, 184542,482, 575624,362, 184542,481, 575608,52, 184536,628, 575608,518, 184536,627, 575608,516, 184536,626, 575594,546, 184530,149, 575594,544, 184530,149, 575594,542, 184530,148, 575580,796, 184522,588, 575580,794, 184522,586, 575580,792, 184522,585, 575568,694, 184514,569, 575568,692, 184514,568, 575568,69, 184514,566, 575557,75, 184506,036, 575557,748, 184506,035, 575557,747, 184506,033, 575547,93, 184497,069, 575547,928, 184497,068, 575547,927, 184497,067, 575540,772, 184489,753, 575540,755, 184489,711, 575540,773, 184489,668, 575541,753, 184488,693, 575539,485, 184486,399, 575539,474, 184486,384, 575539,469, 184486,366, 575526,016, 184396,522, 575456,142, 184567,991, 575581,098, 184603,851, 575663,938, 184627,624, 575753,329, 184653,277, 575753,375, 184653,271, 575753,404, 184653,236, 575770,26, 184594,501, 575770,254, 184594,454, 575770,216, 184594,426, 575759,18, 184591,871, 575741,055, 184586,909, 575709,707, 18
4577,166, 575680,93, 184568,419, 575679,878, 184568,099, 575651,254, 184558,428, 575622,3, 184548,627, 575606,091, 184542,531, 575599,557, 184539,564, 575591,605, 184535,955, 575577,419, 184528,038, 575564,828, 184519,711, 575553,658, 184510,986, 575543,325, 184501,439, 575543,313, 184501,43, 575543,299, 184501,425, 575479,972, 184484,946, 575479,927, 184484,952, 575479,899, 184484,987, 575465,302, 184535,853, 575456,101, 184567,916, 575456,107, 184567,962, 575456,142, 184567,991, 575490,379, 184553,269, 575487,99, 184561,46, 575516,025, 184569,447, 575519,283, 184558,023, 575495,012, 184551,068, 575494,977, 184551,039, 575494,971, 184550,993, 575495,03, 184550,79, 575494,928, 184550,761, 575490,379, 184553,269))
This select fails:
Select /*+ ordered */ A.fid from MISE_A_JOURPFP3 A, MISE_A_JOURPFP3 B where B.FID= 70491 AND mdsys.sdo_relate(B.geom, A.GEOM ,'mask = anyinteract querytype=window') = 'TRUE' ;
output:
Select /*+ ordered */ A.fid from MISE_A_JOURPFP3 A, MISE_A_JOURPFP3 B where B.FID= 70491 AND mdsys.sdo_relate(B.geom, A.GEOM ,'mask = anyinteract querytype=window') = 'TRUE'
FEHLER in Zeile 1:
ORA-13226: Oberfläche ohne räumlicher Index nicht unterstützt
ORA-06512: in "MDSYS.MD", Zeile 1723
ORA-06512: in "MDSYS.MDERR", Zeile 8
ORA-06512: in "MDSYS.SDO_3GL", Zeile 58
DB is 9.2.0.5 on Windows XPThis might be related to bug 3561140 - we are working with the appropriate folks in Oracle to try to resolve it. If you can post your view definition then we can try to ensure this is fixed at the same time (a small test case would be appreciated).
-
Problem with direction of points in sdo_ordinate_array
i have created a polygon selection tool to create a polygon . I use sdo_relate function to get another point geometry from the polygon.
SELECT a.cust_id
FROM T_S_CUSTOMERS a
WHERE SDO_RELATE(a.geometry,SDO_GEOMETRY(2003, 8307, NULL,
SDO_ELEM_INFO_ARRAY(1,1003,1),
SDO_ORDINATE_ARRAY("+lstcoordinates+")),
'mask=anyinteract querytype=window') = 'TRUE';
I want to find cust_id from this polygon .If i draw the polygon in anti clock wise direction , the query works but if i draw the polygon in clockwise direction , the query fails .
Since the polygon will be drawn by user at the front end , I cannot restrict the direction in which user draws the polygon .User can also start drawing the polygon in clock wise direction then shift to anti clock wise direction to complete it. Is there any way
through which i can get the result irrespective of user direction sense .The easiest way to ensure the polygon is counter-clockwise is to use this:
SDO_MIGRATE.TO_CURRENT(
geom IN SDO_GEOMETRY,
dim IN SDO_DIM_ARRAY
) RETURN SDO_GEOMETRY;
Example:
SELECT sdo_migrate.to_current (SDO_GEOMETRY (2003,
8307,
NULL,
sdo_elem_info_array (1, 1003, 1),
sdo_ordinate_array (1, 1, 1, 2, 2, 2, 2, 1, 1, 1)
sdo_dim_array (sdo_dim_element ('Longitude', -180, 180, .05),
sdo_dim_element ('Latitude', -90, 90, .05)
) ccgeom
FROM DUAL;
CCGEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2003, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_ARRAY(1, 1, 2, 1, 2, 2, 1, 2, 1, 1)) -
Spatial query in a distributed environment
We want to compare two spatial tables.
We have (at present identical) tables on two computers GEOSRV0 and NB25.
On both we have Oracle 10.1.0.2. GEOSRV0 has the WINDOWS 2000 operating system installed, on NB25 there is WINDOWS XP Professional.
The table is EZG:
GEOMETRY MDSYS.SDO_GEOMETRY
GEOMETRY_SK VARCHAR2(15)
EZG_NR NOT NULL NUMBER
FLAECHE FLOAT(126)
The primary key is EZG_NR.
There is a private database link for the user WLKREP on NB25 to user WLKREP on GEOSRV0.
The USER_SDO_GEOM_METADATA are the same on both machines (same SRID, same DIMINFO).
The following query â we check, if for each record on NB25 is a record on GEOSRV0 - works normally:
SQL> select ezg_nr from
2 ezg a where not exists
3 (select 1 from wlkrep.ezg@wlk where ezg_nr=a.ezg_nr);
no rows selected
This is correct.
We can read the geometry on the remote database:
SQL> select * from wlkrep.ezg@wlk where rownum=1;
GEOMETRY(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
GEOMETRY_SK EZG_NR FLAECHE
SDO_GEOMETRY(3003, 1040001, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_ARRAY(182285.489, 405672.889, 0, 182248.701, 405644.889, 0, 182241.984, 405639.771, 0, 182171.753, 405538.805, 0, 182130.953, 405498.016, 0, 181971.1, 405274.91
6, 0, 182223.796, 405176.609, 0, 182292.701, 405204.37, 0, 182439.028, 405451.66
, 0, 182573.506, 405628.153, 0, 182643.64, 405726.59, 0, 182718.945, 405764.608,
0, 182780.371, 405805.57, 0, 182862.191, 405843.931, 0, 182966.69, 405933.13, 0
, 183131.065, 406064.852, 0, 183205.098, 406160.637, 0, 183231.535, 406220.959,
0, 183266.473, 406265.415, 0, 183308.669, 406303.524, 0, 183295.305, 406364.696,
0, 183204.283, 406331.35, 0, 183161.835, 406299.691, 0, 183134.554, 406243.403,
GEOMETRY(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
GEOMETRY_SK EZG_NR FLAECHE
0, 183080.454, 406171.548, 0, 183027.376, 406123.698, 0, 182914.558, 406039.291
, 0, 182770.335, 405973.138, 0, 182593.691, 405886.413, 0, 182443.506, 405795.85
2, 0, 182343.293, 405713.991, 0, 182285.489, 405672.889, 0))
13 304906.065
Now we want to compare the geometry and get
SQL> select a.ezg_nr from
2 wlkrep.ezg@wlk b, ezg a where a.ezg_nr=b.ezg_nr and
3 sdo_equal(a.geometry,b.geometry) != 'TRUE';
select a.ezg_nr from
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Only comparing two elements gives the same result
SQL> select a.ezg_nr from
2 wlkrep.ezg@wlk b, ezg a where a.ezg_nr=640 and
3 b.ezg_nr = 640 and
4 sdo_equal(a.geometry,b.geometry) = 'TRUE';
select a.ezg_nr from
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Even if we query a non existing element
select count(*) from ezg where ezg_nr=99999;
COUNT(*)
0
SQL> select a.ezg_nr from
2 wlkrep.ezg@wlk b, ezg a where a.ezg_nr=99999 and
3 b.ezg_nr = 99999 and
4 sdo_equal(a.geometry,b.geometry) = 'TRUE';
select a.ezg_nr from
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Is this a bug or is a distributed spatial query not supported?
The following statement works:
SQL> select a.ezg_nr from
2 wlkrep.ezg@wlk a where not exists
3 (select 1 from ezg b where
4 b.ezg_nr=a.ezg_nr and
5 sdo_equal(b.geometry,a.geometry)='TRUE');
no rows selected
Regards
KarlActually, I have filed a TAR to Oracle on this. I also spoke to Steve Muench about it at OracleWorld, briefly. As of today, I'm trying to add to DataScroller.java to make it implement java.io.Serializable (with no luck...maybe someone can comment on what I'm doing wrong).
Here's what I have done so far.
Changed DataScroller.java (located in bc4jhtmlsrc.zip) to the following:
public class DataScroller implements java.io.Serializable
I added the following members per the docs on java.io.Serializable
private void writeObject(java.io.ObjectOutputStream out)
throws IOException
// really don't need to save state. Next call will recompute what's necessary
private void readObject(java.io.ObjectInputStream in)
throws IOException, ClassNotFoundException
// really don't need to load state. Next call will recompute what's necessary
I then used jar xvf to "unjar" datatags.jar, replaced DataScroller.class with my version and used
jar cv0Mf datatags.jar META-INF/* oracle/*
to recreate the datatags.jar. My file is not 100% the exact same as their file, but it looks to be right to me. I ended up doing it this way because the oracle\ord\* classes are not in the bc4jhtmlsrc.zip, only in the jar file and felt this was the "safest" way to include the correct contents of the file.
HOWEVER -- I'm sorry to say that I've then tried to run my app and get the same issue.
Thanks,
Jeff -
GeoRaptor 3.2.1 Released for SQL Developer 3.x
Spatialites!
After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
The release notes for this release are:
* Fixed issues with validate geometry functionality in particular the update dialog box.
* Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
* Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
* SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
-- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
* Spatial Layer Draw has been modified to use NLS based decimal formatting.
* New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
-- Cumulative length
-- Measure (M)
-- Z value
-- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
* You can also label each vector/segment of a linestring/polygon with:
-- Length
-- Cumulative Length
-- Bearing (approximate for geodetic/geographic data)
-- Distance (approximate for geodetic/geographic data)
-- Bearing and Distance (approximate for geodetic/geographic data)
* The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
* New feature labelling options have been provided:
-- First/middle/last vertex,
-- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
-- Calculated by GeoRaptor on the client side using Java Topology Suite.
* Result sets now have the ability to:
-- Copy to clipboard all geometries across many rows and columns.
-- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
* New GeoRaptor Preferences:
-- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
-- Colours of orphan, missing and correct metadata entries for Metadata Manager;
-- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
-- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
* Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
* Help pages added to the following dialogs with more to follow:
-- Metadata Manager,
-- Shapefile Importer and
-- Layer Properties dialogs.
* GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
* Spatial Index creation dialog now supports additional index parameters and parallel build settings.
* Metadata Manager overhauled:
a. Shows:
1. Metadata entries which have no underlying oracle object (orphan)
2. Metadata entries for existing underlying objects (existing case)
3. Database objects with sdo_geometry for which no metadata entry exists (new)
b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
c. All actions for main (bottom) metadata table are in a single right mouse click menu.
Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
e. Buttons revamped.
* Tab/Shapefile export:
a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
b. Some work attempted on export of NLS strings (still not corrected).
c. Objects with no rows now correctly processed.
* Shapefile Import
-- Bug relating to Linux file names corrected.
* Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
* Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
* Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
* Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
We don't get paid for what we do so are always looking for additional help.
Here are some of the requests we have had for improvements:
1. MySQL access
2. WMS access;
3. Ability to import shapefile data into an existing table;
4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
5. Ability to export/import layer definitions to give to others;
6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
Thanks to the following for their invaluable assistance:
Holger Labe, Germany
John O'Toole, Ireland
Vladimir Pek, Czech Republic
Pieter Minnaar, Holland
Olaf Iseeger, Germany
Sandro Costa, Brazil;
Marco Giana, Australia.regards
Simon Greener
Principal GeoRaptor Developer
Edited by: Simon Greener on Sep 10, 2012 2:43 PMSimon,
I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
Thanks for the effort,
Bryan
Maybe you are looking for
-
"Permission to access" error messages when coping folders
When I try to drag my Home directory to another drive to keep a backup copy, I get the no "Permission to access" error message on various programs. "Get Info" has the option of making me the owner but it is grayed out on any of those programs I can't
-
Pb PDF Filename : AcroPDF.dll + VB6
We use the component AcroPDF.dll (Adobe Acrobat 7.0 Browser Control type library 1.0) in a VB6 program. We use the method LoadFile to display PDF file in form. This method works fine. The problem is after some LoadFile request, when we display the pr
-
HI I have a problem with syncing between my devices. photos from my iPhone sync to the cloud and appear there, but doesn't appear on my mac. does anyone has an idea on solving that? thanks
-
[ASK] Show Object with Drag and Drop Condition
Hello guys, I just finished making my simple drag and drop quiz which i've already mentioned in the previous thread. But i still have a problem. I've searched through the Internet, but i didn't find any case similar with my case. Please take a look a
-
Leopard 10.5.2 Graphics Update Screws up Resolution?
I have an outboard Viewsonic 22" Monitor and after installing the 10.5.2 Leopard Graphics Update that just released today, my monitor shows as a generic "Color LCD" rather than the Viewsonic. I'm connected using a DVI connector. The display works, bu