Skip to main content
Question

Translation very slow if Coordinate system is added to writer parameters

  • September 27, 2017
  • 3 replies
  • 24 views
L
Forum|alt.badge.img

Hello, me again, I am doing my first fme steps and need to ask so much...

I have this workspace (PATH > AttrbuteFilter > FeatureReader > Tif writer):

1. I runs nicely, but if I add a coordinate system to the writer in the navigator, the translation takes 10 times longer.

2. Why is there no Coordinate System to be set in the FeatureReader? If I add a normal reader, it can/has to be set!?

3. Why can a Coordinate System be set in the navigator in the Directory and File pathnames reader? I thought it only reads pathnames and not the data itself which would have a Coordinate System....

thank you!

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

david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • September 27, 2017

1) If you look carefully in the FME log, I suspect you'll see that there's some implicit reprojection going on when you specify a coordinate system on the writer. This happens when the specified output coordinate system doesn't match the coordinate system of the incoming features. As you've discovered, this can have a huge impact on performances.

2) It's indeed possible to set the coordinate system on the FeatureReader:

3) I suspect that's because all readers and writers inherit some basic parameters from a parent definition somewhere. You can safely ignore it.

L
Forum|alt.badge.img
  • ludhil
  • Author
  • 5 replies
  • September 27, 2017

1) If you look carefully in the FME log, I suspect you'll see that there's some implicit reprojection going on when you specify a coordinate system on the writer. This happens when the specified output coordinate system doesn't match the coordinate system of the incoming features. As you've discovered, this can have a huge impact on performances.

2) It's indeed possible to set the coordinate system on the FeatureReader:

3) I suspect that's because all readers and writers inherit some basic parameters from a parent definition somewhere. You can safely ignore it.

Oh god, would help if I weren't blind.... @david_r: Sorry and thanks!
david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • September 27, 2017
Oh god, would help if I weren't blind.... @david_r: Sorry and thanks!
Haha, no problem, happens to all of us from time to time!

Community Stats

32,093
Posts
121,875
Replies
39,731
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.