Jody,
Did you get this sorted out? Do you need some info? Did you want some help (If you point me at your sql generation routines I can take a look for you)?
I also forgot to mention one thing, there is a very good reason to clump all the Clob, Blob and mdsys.sdo_geometry cols at the end of the geom list ... chaining. If you are going to chain on disk, you want to ensure all of your search criteria (or atleast most) is in the first block. For most installs, if chaining is going to happen it's from a blob, clob, geometry, (complex object) col ... so pushing these to the right tells the db to store them last in the block on disk. Just though I'd mention it because it sounded like you wanted to create ora tables on the fly.
David
On 2/3/06, David Zwiers <[EMAIL PROTECTED]> wrote:
Jody,If you need some help, just let me know.For each table, you need to create it, add one record to the metadata table for each geom column (the one below is actually a view, but works well). Next is the tricky part if you want to do spatial (bbox) queries, you need to create a spatial index for each geom col ... but there are some caveats to this, most notably how the index grows w.r.t the bounds in your metadata table. The index may invalidate itself after some number of transactions, and cause quries to fail, so I try to insert 4 dummy geoms into the four corners of my bounds, then create the index, and lastly remove the 4 dummy geoms (sets up the tree correctly). You may also want to analyze the table for performance reasons.
Along the way, you referenced the id of a SRID record (can't recall the table off the top of my head), which is defined using a varient of WKT. If you want to include a non standard Oracle SRID you need to add the srid BEFORE metadata definitions ... and you need dbsys access.Lastly, many or our clients like using Oracle Locator (subset of Oracle Spatial) with SDE. This adds it's own set of complications ... but beware that SDE modifys the metadata table (insert, delete, update ...) and may invalidate you index, causing spatial query errors (both in oracle and sde).Hope this helps, I know it was a bit of a ramble.David
On 2/1/06, Jody Garnett <[EMAIL PROTECTED] > wrote:I am going to keep notes on the wiki somewhere - and ask questions as I go.
So far I have learned:
- MDSYS.SDO_GEOMETRY (not SDO_GEOMETRY)
- We need to add an entry into USER_SDO_GEOM_METADATA for each geometry
column
On the bright side I am placing this kind of knowledge into
OracleDataStore.createSchema ( FeatureType ), on the downside
the method signature will need to change to provide bounds (I hope I can
determine SRID from the DefaultGeometry CRS definition).
I am currently stuck with a database trigger yelling at me when I try
and add my first feature, near as I can tell this is due to the SRID table
not being populated. If anyone knows how to set up this table in oracle
I would love some guidance.
Jody
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
