TransWikia.com

Why does AttributeRenamer cut data type width?

Geographic Information Systems Asked by N.Varela on April 6, 2021

I’m importing data from a ArcGIS .gdb to a POSTGIS DB using FME Desktop 2016. For this I need first to rename single attribute names using the AttributeRenamer transformer. My problem is that, reader attributes with width 254 (data type “text”) are automatically transformed to writer width 200 (type “varchar”). Why does FME cut the width of the attributes, is it a bug?

However, this issue only appears when I use an AttribruteRenamer. I also tried the BulkAttributeRenamer, which retrieves the same. Any ideas?

One Answer

I think you're probably using the writer with an Automatic schema:

enter image description here

So anything that connects to the writer gets an attribute. However, unless it came from the original schema, FME doesn't know what data type it should be.

In my screenshot (above) Name got renamed to parkname (and ID to parkid). Because of the automatic mode, parkname gets a definition on the writer; but because there is no such attribute on the source schema FME doesn't know what data type it should be. It defaults to varchar200.

Ideally we (I work for Safe Software) would improve FME's behaviour. It certainly ought to notice that parkname is just a rename of a source attribute. But in the meantime you could turn off the automatic attribute definitions; either turn it to manual completely or turn it to manual before running the workspace and edit the field widths manually at that point.

Answered by Mark Ireland on April 6, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP