Skip to main content
Solved

Writer truncates attribute values

  • August 14, 2020
  • 2 replies
  • 255 views

umapper1
Contributor
Forum|alt.badge.img+5

warnings2warnings1writer tab2writer tab1Hi community, I could use some help.

I'm reading an xml, doing some geometric and attribute manipulation before writing out to OGCgeopackage format. I'm having trouble with the writer truncating the attribute values. My understanding is that by default, FME takes the character width from the reader however this seems to be too short for my final values so I've switched over the attribute definition from automatic to manual in the writer and increased the width. It seems to be ignoring this and coming up with a lot of warnings. Anyone know how to fix? Images attached.

Best answer by ebygomm

Have you tried changing the Table Handling to drop and create? Currently it is set as create if needed, so it looks like the table probably already exists without the changed attribute widths. Hence the warnings

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.

2 replies

ebygomm
Influencer
Forum|alt.badge.img+45
  • Influencer
  • Best Answer
  • August 14, 2020

Have you tried changing the Table Handling to drop and create? Currently it is set as create if needed, so it looks like the table probably already exists without the changed attribute widths. Hence the warnings


umapper1
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • August 14, 2020

Have you tried changing the Table Handling to drop and create? Currently it is set as create if needed, so it looks like the table probably already exists without the changed attribute widths. Hence the warnings

Your a star @ebygomm​ ! That was the issue ;)

Explains why it worked the first time and then stopped working after that too.