Skip to main content
Best Answer

Geometry traits question

  • November 25, 2020
  • 3 replies
  • 36 views
stalknecht
Contributor
Forum|alt.badge.img+22

The task is to migrate data from smallworld and oracle to sql-server.

The data contains multiple geometry columns. So I've followed Writing to Database Tables that contain Multiple Geometry Columns

I managed to insert the records but the geometry trait information is missing.

Here is an example of Oracle:AfbeeldingOracleAnd here an example of Smallworld:

AfbeeldingSMallThe FME translation results in sql server:

AfbeeldingSqlSo the traits information is lost.

Can I keep the trait information stored in Smallworld as "Text Rotation" or in Oracle called "oracle_orientation" into the sql db?

Is there an sql-server equivalent?

 

Best answer by markatsafe

@stalknecht​ I think you have taken the right approach. It's only Oracle and Smallworld that support oriented points and Oracle and SQL Server don't support text - only Smallworld does.. So you have to move those geometry characteristics (traits) to attributes if you want to preserve them in SQL Server

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

paalped
Contributor
Forum|alt.badge.img+5
  • paalpedContributor
  • Contributor
  • April 22, 2021

I am new to this way of storing what I see as attributes but named traits and spread across different geometry parts. My key take on traits to make everything simple, is just to convert them brutally to attributes, if they conflict by name just enumerate them. much easier to work with them as attributes I think.

stalknecht
Contributor
Forum|alt.badge.img+22
  • stalknechtContributor
  • Author
  • Contributor
  • April 23, 2021

I am new to this way of storing what I see as attributes but named traits and spread across different geometry parts. My key take on traits to make everything simple, is just to convert them brutally to attributes, if they conflict by name just enumerate them. much easier to work with them as attributes I think.

Thanks @Paal Pedersen​,  that's exactly what I did to solve it. I still don't know if there is a sql-server equivalent.

M
Forum|alt.badge.img+2
  • markatsafe
  • Best Answer
  • April 29, 2021

@stalknecht​ I think you have taken the right approach. It's only Oracle and Smallworld that support oriented points and Oracle and SQL Server don't support text - only Smallworld does.. So you have to move those geometry characteristics (traits) to attributes if you want to preserve them in SQL Server

Community Stats

32,182
Posts
122,181
Replies
39,856
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.