Skip to main content
Solved

Oracle Spatial Object Reader VS SQLCreator when reading geometry

R

Hi,

I've received an FME workbench from a colleague which uses an SQLCreator to read an Oracle Spatial database. I wanted to recreate the steps by reading from the database using the Oracle Spatial Object Reader, however when inspecting the same tables and features there seems to be no geometry related to (some of the) objects.

The weird thing is one table does show geometry, and others don't. I have also tried reading the database using an SQLExecutor as well as a FeatureReader and these two also don't read any geometry.

Does anyone know what might cause this problem/difference between transformers and readers, and knows how to solve it?

Thanks in advance.

Best answer by roetem

I seem to have found the solution based on this post . When adding the Oracle Spatial Reader there is an option under Advanced named "Handle multiple geometry columns". This allowed the geometry to be read.

View original
Did this help you find an answer to your question?

4 replies

M
Forum|alt.badge.img+2

@roetem At guess, the spatial tables created (perhaps using SQLExecutor) without populating the appropriate metadata tables. The FME Oracle Spatial reader would need these. The FME Oracle Spatial writer would ensure that the appropriate tables are populated.

R
  • roetem
  • Author
  • March 9, 2020

@markatsafe Thanks for your answer. I'm not sure i completely understand your answer, but if I am right the metadata tables are not populated with geometry appropriately?

 

Is there a way to overcome this? Writing through the Oracle Spatial is not really an option because i have no permission to overwrite the database. Also, i want to review any changes in between.

 

Strangely one of my colleagues is using another software program calling the same database tables and he is also having trouble reading geometry.

R
  • roetem
  • Author
  • Best Answer
  • March 9, 2020

I seem to have found the solution based on this post . When adding the Oracle Spatial Reader there is an option under Advanced named "Handle multiple geometry columns". This allowed the geometry to be read.

R
  • roetem
  • Author
  • March 9, 2020
roetem wrote:

@markatsafe Thanks for your answer. I'm not sure i completely understand your answer, but if I am right the metadata tables are not populated with geometry appropriately?

 

Is there a way to overcome this? Writing through the Oracle Spatial is not really an option because i have no permission to overwrite the database. Also, i want to review any changes in between.

 

Strangely one of my colleagues is using another software program calling the same database tables and he is also having trouble reading geometry.

I seem to have found the solution based on this post . When adding the Oracle Spatial Reader there is an option under Advanced named "Handle multiple geometry columns". This allowed the geometry to be read.

Reply


Helpful Members This Week

Community Stats

31,073
Posts
117,799
Replies
38,834
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.