Skip to main content
Question

Attribute type message when opening 2016.1 Workspace in 2017.0

tim_wood
Contributor
Forum|alt.badge.img+8

I've just opened one of my 2016.1 Workspaces that reads a ShapeFile in 2017.0 and some ArcSDE layers and writes to 2 File Geodatabases (FGDBs). I got the following message in the translation log:

Attribute type 'fme_char' not found in ATTR_TYPE_MAP. Trying 'fme_int8'

 

Attribute type 'fme_int8' not found in ATTR_TYPE_MAP. Trying 'fme_int16'

I've still got 2016.1 installed so I'll run the Workspace in that, but I'd appreciate any explanations of what this means. I'll try re-creating the Readers and Writes in 2017.0 when I get a chance.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

4 replies

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Contributor
  • April 10, 2017

Have you tried re-creating the File geodatabase writer in FME 2017?

I have a PR with Safe. Some things got broken in the File geodatabase API.

Might be related.

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Contributor
  • April 10, 2017
erik_jan wrote:

Have you tried re-creating the File geodatabase writer in FME 2017?

I have a PR with Safe. Some things got broken in the File geodatabase API.

Might be related.

And I should have read the last lines of your question a bit more carefully.

 

Let us know if re-creating worked.

 

 

tim_wood
Contributor
Forum|alt.badge.img+8
  • tim_woodContributor
  • Author
  • Contributor
  • April 10, 2017
erik_jan wrote:

Have you tried re-creating the File geodatabase writer in FME 2017?

I have a PR with Safe. Some things got broken in the File geodatabase API.

Might be related.

Thanks. However the Writers in my Workspace are File Geodatabase (ArcObjects) so maybe not the same problem...

 

tim_wood
Contributor
Forum|alt.badge.img+8
  • tim_woodContributor
  • Author
  • Contributor
  • June 12, 2017

The same thing happens opening a 2016.1 Workspace in 2017.0.1.1 (32-bit and 64-bit). Does @erik_jan or anyone else have an update on this?

My Workspace does 2 things:

1) Reads a ShapeFile, processes it and writes out various File Geodatabase layers using the File Geodatabase ArcObjects Writer.

2) Reads several ArcSDE layers using the ArcSDE Geodb Reader and writes them to a backup File Geodatabase, again using the ArcObjects Writer.

Most fields are data type Char, with some Double and a few Integer and Smallint.

Helpful Members This Week

Community Stats

31,841
Posts
120,933
Replies
39,474
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
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.