Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-users] problem displaying Oracle layer in udig

Hi Jody. Thanks for the reply. I don't know Oracle all that well, but I should note this is Oracle Locator on 10g, not a full-blown Oracle Spatial database. Not sure if that makes a difference or not.

I downloaded & installed udig-1.2-RC1.macosx.cocoa.x86.zip, and I'm not having any success displaying Oracle data here either. It actually seems a lot worse than 1.1.1.

Here's what I've done:
 - File > New > New Map
 - Layer > Add
 - Select 'Oracle Spatial'
- Enter connection information. I notice the wizard no longer automatically populates the list of available schema, as it did in uDig 1.1.1. When I enter a database name and click 'Lookup', I get a list of available schemas, but the 'Database' value I entered disappears. - I select the correct schema, re-enter the database name, and click 'Connect', and then 'Next >'. - I see a message telling me there are no features available, or words to that effect. This is at the same time that I'm able to view polygons from this same schema in uDig 1.1.1.

If I manually enter the name of my schema, rather than selecting it from the list, uDig hangs and becomes unresponsive when I click 'Next >'. I've left it sitting for several minutes and never seen it recover. I end up having to force quit uDig and start over.

When I repeat all the steps above, I cannot get the auto-population of schema names to work at all, even after I click the 'Lookup' button. It doesn't blank out the database name like it did last time. 'Lookup' appears to not do anything at all.

Are there log files I could capture or other ways I could help you troubleshoot this further? I wish I could give you better steps to reproduce the problem, but the behavior of the application seems quite inconsistent and hard to understand. Let me know if I can provide more information which might be helpful.

best,
alex

On Mar 10, 2010, at 7:07 PM, Jody Garnett wrote:

Hi Alex:

We have been really focused on releasing uDig 1.2 (indeed you will find a release candidate on the website). The oracle datastore has been completly rewritten for uDig 1.2 (by Justin of the GeoTools project). So the good news is that we can now get fixes for Oracle related issues; the bad news is we have not had anyone test ...

Personally I want to make sure the Oracle connection wizard works; the new implementation of Oracle datastore seems really solid and is well received by the GeoServer community.

I am a little familiar with Oracle and the metadata. The Bounds information is used to indicate where the information is (and uDig will only bother requesting from oracle when it is showing the indicated area of the world). Oracle itself uses the bounds information when creating a spatial index I think.

Rather then scanning through every single row - the old DataStore would look at this index bound information as an indication of where the information was on the world.

That said we are going to have to test with the new Oralce DataStore; I am not sure if it looks at the oracle metadata at all.

Jody


On 11/03/2010, at 4:55 AM, Alex Dean wrote:

Anyone?

On Mar 6, 2010, at 8:52 PM, Alex Dean wrote:

I'm using uDig 1.1.1 on Mac OSX 10.5. I occasionally have trouble displaying data from Oracle in uDig, and I can't figure out what the problem is.

- There is data in the table. I can view the non-spatial data in the 'Table' view. - I've checked that there is a spatial index on the geometry column, and the proper meta-data exists in the user_sdo_geom_metadata view. - The user_indexes view gives this index an opstatus of 'VALID', so I don't think there's anything wrong with it.

If I left-click on the layer name, and select 'Properties', the summary info includes a 'Bounds' value of '(0.0,0.0)(-1.0,-1.0)'. This definitely seems like a problem, but I'm not sure what it means or how I can troubleshoot it further.

At the same time that data from this table (offshore_marine_zones) will not display, I am able to display data from other layers in the same database. I can't figure out what's different about this one. If I import the same offshore_marine_zones data into Postgis, I'm able to display it in uDig with no issues.

How can I troubleshoot this further?

thanks,
alex
_______________________________________________
udig-users mailing list
udig-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.refractions.net/mailman/listinfo/udig-users

_______________________________________________
udig-users mailing list
udig-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.refractions.net/mailman/listinfo/udig-users



Attachment: PGP.sig
Description: This is a digitally signed message part


Back to the top