Web hosting Custom Email SiteBuilder

JSWeb Oracle/Spatial Cartridge Server Extension Architecture :

Features :

• Including a Shapefile-to-Spatial Cartridge loader utility, which loads the ".shp" and ".dbf" shapefiles into Oracle Spatial Cartridge. The loaded Oracle data can be accessed with either JShape programs or other Oracle Spatial Cartridge applications.
• The Spatial Cartridge data can be retrieved either from JShape client directly, or through JSWeb Oracle/Spatial Cartridge Server Extension.
• JSWeb Oracle/Spatial Cartridge Server Extension has the following extra advantages:
  • No Oracle JDBC driver required to install on client machines
  • Support WWW JShape applets directly

JSHape Oracle/Spatial Cartridge Client Extension :

JSCLayer : A Shapefile To Oracle Spatial Cartridge Loader Utility

JSCLayer 1.0, Copyright 1999 by JShape Software, http://shiuhlin.ml.org
Usage Syntax : java jsclayer [options], Available Options :
-d [JDBC Driver : THIN/OCI7/OCI8 (default : THIN)]
-s [Oracle Database Server Name or Address]
-r [Oracle Database Server Port (default : 1521)], Only For JDBC THIN Driver
-i [Oracle Database Server ID (default : ORCL)], Only For JDBC THIN Driver
-u [Oracle Database Server User Name]
-p [Oracle Database Server User Password]
-o [Operations], Available Operations :
     create : create a Spatial Cartridge layer
     drop   : drop a Spatial Cartridge layer
     list   : list Spatial Cartridge layers
     reset  : reset the Spatial Cartridge query window layer
-l [Layer Name]
-f [Path and Name of Shapefile]
-t [Tile Index Level]
-c [Commit Rate (default : 100)]
-e [Layer Extent : XMin,YMin,XMax,YMax]
-a [Auto Index, TRUE/FALSE (default : TRUE)]
-q [Query Window, TRUE/FALSE (default : TRUE)]
-x [Compress Point, TRUE/FALSE (default : TRUE)]
Example 1 : create a SCROAD layer from ROAD.SHP/ROAD.DBF
  java jsclayer -d oci8 -s MyOracle -u scott -p tiger -o create -l scroad -f road -t 5
Example 2 : drop a SCROAD layer
  java jsclayer -d oci8 -s MyOracle -u scott -p tiger -o drop -l scroad
Example 3 : list available Spatial Cartridge layers
  java jsclayer -s orasc.xyz.com -u scott -p tiger -o list
Example 4 : reset the Spatial Cartridge query window layer
  java jsclayer -s 205.227.44.38 -u scott -p tiger -o reset -l scroad

Technical Notes For JSCLayer

• JSCLayer is implemented under the following environment :
  • JDK 1.1.6
  • Oracle 8.0.3 (NT)
  • Oracle Spatial Cartridge 8.0.3
  • Oracle JDBC 8.0.4 (THIN/OCI)
• The primary goals of JSCLayer are to allow users to load their shapefiles into Oracle Spatial Cartridge. JSCLayer will create the standard Spatial Cartridge table structures and optionally create JShape specific Oracle tables and fields. Generally, JSCLayer will work both with JShape specific applications and other Oracle Spatial Cartridge compliant applications.
• JSCLayer is a Java application. To run it, users need to install JDK 1.1+ and Oracle JDBC driver on their machines.
• JSCLayer is completely implemented in Java. It will be somewhat slower than its C/C++ counterparts, but it can run on most computer platforms.
• JSCLayer can support two type Oracle JDBC drivers :
  • THIN : user needs to specify server "host" name (optional : server port and server ID).
  • OCI7 or OCI8 : user needs to specify server SQL*Net name (defined in TNSNAMES.ORA).
• The default Oracle tables created by JSCLayer :
  • Standard Spatial Cartridge tables : layer_SDOLAYER, layer_SDODIM, layer_SDOGEOM and layer_SDOINDEX.
  • Query Window tables : layer_QW_SDOLAYER, layer_QW_SDODIM, layer_QW_SDOGEOM and layer_QW_SDOINDEX. These tables can be omitted by JSCLayer option "-q false".
  • Attribute information table : layer_SDOINFO. The table structure is the following :

    
            layer_SDOINFO
            (SDO_GID NUMBER,
             Fields from (layer.dbf) attribute file)

  • Packed points' table : layer_SDOPACK. This table can be omitted by JSCLayer option "-x false". This table contains the compressed spatial data points for faster data retrieval. The table structure is the following :

    
            layer_SDOPACK
            (SDO_GID NUMBER,
             POINTS LONG RAW)

• The default Oracle table indexes created by JSCLayer :
  • layer_SDOGEOM_SDO_GID (create a SDO_GID index field on the layer_SDOGEOM table)
  • layer_SDOINDEX_SDO_GID (create a SDO_GID index field on the layer_SDOINDEX table)
  • layer_SDOINDEX_SDO_CODE (create a SDO_CODE index field on the layer_SDOINDEX table)
  • layer_SDOINFO_SDO_GID (create a SDO_GID index field on the layer_SDOINFO table)
  • layer_SDOPACK_SDO_GID (create a SDO_GID index field on the layer_SDOPACK table)
• The data values in layer_SDODIM and layer_QW_SDODIM tables :
  • By default, the values of SDO_LB and SDO_UP of each row are set with the values of input shapefile extent (Bounding Box).
  • User can use JSCLayer option "-e" to specify the values of SDO_LB and SDO_UP. For example : "-e -180,-90,180,90" will set the following values in layer_SDODIM and layer_QW_SDODIM tables.

    
              SDO_DIMNUM   SDO_LB   SDO_UB   SDO_TOLERANCE   SDODIMNAME
              ----------   -------  ------   -------------   ----------
                       1      -180     180       5.000E-09            X
                       2       -90      90       5.000E-09            Y

• Auto (Spatial) Index : when JSCLayer inserts spatial records into the Oracle Database, by default, it will create the related spatial indexes on the fly. Sometime the Auto (Spatial) Index processes are very time consuming. JSCLayer has an option "-a false" which allows users to disable Auto (Spatial) Index mode, and run the spatial index process in the batch mode.
• Query Window Layer Tables : by default, JSCLayer will create Query Window Layer Tables to ease the spatial queries for applications. However, depends on applications, the size of Query Window Layer table may grow bigger and bigger. Users can verify the size of Query Window Layer Tables with JSCLayer "-o list" function, and users can reset (delete records) the size of Query Window Layer Tables with JSCLayer "-o reset" function.
• Tile Index Level : JSCLayer uses Fixed Index mechanism to spatial index the data. The Tile Index Level is used to specify the size of index tile matrix. Here is the lookup list for Tile Index Level :

  
        Tile Index Level   Index Tile Matrix
        ----------------   -----------------
                       1                 2X2
                       2                 4X4
                       3                 8X8
                       4               16X16
                       5               32X32
                   .....               .....
                       N             2^NX2^N

• Tile Index Level Factor For Applications : usually, the bigger Tile Index Level specified, the more detail spatial index tiles are created. But the bigger Tile Index Level Level specified, the bigger layer_SDOINDEX table will be created and the longer index process time will be required. Depends on applications, sometimes, the bigger Tile Index Level won't guarantee the better results.
• Commit Rate : by default, JSCLayer will commit the database each time after loaded 100 records. Depends on the setting (RollBack Segment) of the database, users can tune up this parameter accordingly.