converting oracle geometry from one projection to other using FME desktop 2014 sp2 version.
While doing so ,some of the arc segments (3 vertices) automatically gets converted to linear segments with (~ 30 to 40 vertices) . How can we avoid this ?Is there any parameter to disable these type transformations ? (req : Arcs segment need to be maintained)
You may want to retry using a more current version of FME, there was a lot of work done in how arcs are handled around FME 2016.
You can download and install a more recent version in a separate directory on your pc, thereby preserving your "official" version while you test.
You'll find the most recent versions of FME here: https://www.safe.com/support/support-resources/fme-downloads/
You may want to retry using a more current version of FME, there was a lot of work done in how arcs are handled around FME 2016.
You can download and install a more recent version in a separate directory on your pc, thereby preserving your "official" version while you test.
You'll find the most recent versions of FME here: https://www.safe.com/support/support-resources/fme-downloads/
You might want to consider doing the projection in the database when reading the data (using a function). This would impact the read performance for sure but if it is a small amount of records it would be barely noticeable. Check out SDO_CS.TRANSFORM and SDO_CS.TRANSFORM_LAYER.
If it is involving a large number of records you might consider creating a materialized view (vs a view which would still impact read performance). The materialized view would maintain read performance but would require some backend database effort (more physical storage).
As David_R has correctly indicated, a never version of FME could get you past this issue. Let us know if you can test with a newer version of FME.
On behalf of Safe Software & the community, we would appreciate the update on this.
You might want to consider doing the projection in the database when reading the data (using a function). This would impact the read performance for sure but if it is a small amount of records it would be barely noticeable. Check out SDO_CS.TRANSFORM and SDO_CS.TRANSFORM_LAYER.
If it is involving a large number of records you might consider creating a materialized view (vs a view which would still impact read performance). The materialized view would maintain read performance but would require some backend database effort (more physical storage).
As David_R has correctly indicated, a never version of FME could get you past this issue. Let us know if you can test with a newer version of FME.
On behalf of Safe Software & the community, we would appreciate the update on this.