Go to content Go to navigation and search


Free Software Download

Download Code, Packages and Installers

Object Documentation

Package Documentation

Spatial Companion For Oracle (SC4O)


    New versions of LINEAR, CENTROID and GEOM etc packages
    TESSELATE and CENTROID package updates
    Applying and Extending Oracle Spatial: Source Code Problem
    CENTROID package use with ESRI's sde.st_geometry
    Changes to CENTROID and TESSELATE packages
    CENTROID Package now returns centroid of multi-linestring
    New versions of PL/SQL packages uploaded
    New Release of Free PL/SQL Packages
    New version of PL/SQL packages released
    New Version PL/SQL Spatial packages released
    New PL/SQL Package Upload
    PL/SQL Spatial Types and Packages
    Update to PL/SQL Packages
    New PL/SQL Packages
    VB6 Oracle Spatial or Locator OO4O code
    Spatial PL/SQL Packages by Example
    Catalog Registry Tool
    Image Catalog Tool
    Oracle Spatial PL/SQL and VB6 Source Code



RSS / Atom

Email me


Creative Commons License
All Blog Articles, Data Models and Free Source Code by Simon Greener, The SpatialDB Advisor is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

PL/SQL Spatial Types and Packages

Thursday March 01 2007 at 21:49

Some customers notified me of a problem they were experiencing with downloading my free spatial types and PL/SQL packages from this site. The problem was that their corporate net-nannies were reporting the zip file as having suspicious executables and scripts within it.

I suspected that it might be the Windows .cmd files which are using when installing the packages. But also the zip file contained a Java .class file (I noted that the original .java file was missing from the zip file so I have added it in). To address the problem, I have uploaded a new version of the file in which:

  1. The compiled java class utilities.class has been removed (a script will recompile it from the included source – utilities.java)
  2. All *.CMD files have been renamed to *_CMD
  3. A ReadMe.Txt file has been created that informs users that the *_CMDs must be renamed to *.CMD.

This zip file has been tested by customers and passes their net-nanny tests!

Thanks to all who reported this problem.

Creative Commons License

post this at del.icio.uspost this at Diggpost this at Technoratipost this at Redditpost this at Farkpost this at Yahoo! my webpost this at Windows Livepost this at Google Bookmarkspost this to Twitter