Utilities and helper objects for the manipulation and maintenance of Oracle Spatial topologies. For the most up-to-date documentation see the auto-build dz_topo_deploy.pdf.
Simply execute the deployment script into the schema of your choice. Then execute the code using either the same or a different schema. All procedures and functions are publically executable and utilize AUTHID CURRENT_USER for permissions handling.
Please note that the Oracle Spatial Topology Data Model requires the full Oracle Spatial and Graph license. Please verify your rights to utilize topologies before any use in production.
Generic automated testing of complex data structures such a topologies is fairly daunting task and my code packages deliver very little on the matter. I divide tests into "inmemory" and "scratch" functions. Checks that can be performed in memory (e.g. such as converting SDO to GML) are fairly easy to provide (see the DZ_WKT packages for a good example). However, topologies are complex data structures on disk and walking through any testing requires rights and resources you may not have. Additionally generating sample test topology data from code would probably require a package of its own. Thus the scratch tests in the DZ_TOPO package need quite a bit more infrastructure than most. In the constants in the DZ_TOPO_TEST package, C_TEST_SCHEMA should point to a schema where you can create, drop and modify topologies. C_DZ_TESTDATA needs to point to a schema containing my DZ_TESTDATA resources. If you don't have those items handy, the scratch tests will just not run. I am interested in these topics and if you have any feedback or suggestions please send them along.
Forks and pulls are most welcome. The deployment script and deployment documentation files in the repository root are generated by my build system which obviously you do not have. You can just ignore those files and when I merge your pull my system will autogenerate updated files for GitHub.
Oracle places the burden of matching functionality usage with server licensing entirely upon the user. In the realm of Oracle Spatial, some features are "spatial" (and thus a separate purchased "option" beyond enterprise) and some are "locator" (bundled with standard and enterprise). This differentiation is ever changing. Thus the definition for 11g is not exactly the same as the definition for 12c. If you are seeking to utilize my code without a full Spatial option license, I do provide a good faith estimate of the licensing required and when coding I am conscious of keeping repository functionality to the simplest licensing level when possible. However - as all such things go - the final burden of determining if functionality in a given repository matches your server licensing is entirely placed upon the user. You should always fully inspect the code and its usage of Oracle functionality in light of your licensing. Any reliance you place on my estimation is therefore strictly at your own risk.
In my estimation functionality in the DZ_TOPO repository requires the full Oracle Spatial option for 10g, 11g and 12c.