Skip to main content
Solved

For writing a geodatabase schema feature, what is the native data type for a BLOB? Can FME even write (create) a BLOB attribute?

  • October 19, 2022
  • 2 replies
  • 69 views
tcrossman
Contributor
Forum|alt.badge.img+1

Just found that a workspace I thought was working perfectly is not writing out BLOB attributes. The workspace creates schema attributes and writes out to a geodatabase. Unfortunately, the schema features for BLOB attributes--currently set with native_data_type = blob--are not writing out. So:

  • Can FME even write out Blob attributes in schema features to a geodatabase?
  • If so, what is the native_data_type to use for a BLOB attribute?
  • Is the native_data_type value in the case of a BLOB (or in any case for that matter) case-sensitive?

I have not been able to get FME to read BLOB fields from and existing geodatabase, so I don't have a native_data_type value to inspect. My BLOB attributes in the schema features currently have a native_data_type value of "blob" and an fme_data_type of fme_binarybuffer. Any insights? Thanks in advance for your help.

Best answer by david_r

As far as I can tell, what you're describing should work. Try checking that it's not the reader that skips the blob contents. If nothing else works, consider escalating the issue with your FME Reseller or Safe Support.

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

david_r
Celebrity
  • david_rCelebrity
  • 8391 replies
  • Best Answer
  • October 20, 2022

As far as I can tell, what you're describing should work. Try checking that it's not the reader that skips the blob contents. If nothing else works, consider escalating the issue with your FME Reseller or Safe Support.

tcrossman
Contributor
Forum|alt.badge.img+1
  • tcrossmanContributor
  • Author
  • Contributor
  • 35 replies
  • October 20, 2022

As far as I can tell, what you're describing should work. Try checking that it's not the reader that skips the blob contents. If nothing else works, consider escalating the issue with your FME Reseller or Safe Support.

@david_r​ As is so often the case, your intuition on this problem is spot on: it is the FeatureReader that is skipping the BLOB fields in my workspace. The workspace is comparing the schema of an input GDB with the schema of a blank, standard GDB, in effect doing schema validation. The BLOB fields in several annotation feature classes are dropping out of the analysis as being not shared by the two schemas. I know this not to be the case. As you suspected, I was assuming that the standard GDB was at fault, that my original building of the standard GDB from schema features was flawed. Well, it is undoubtedly flawed in multiple ways, but this isn't one of them. Now, the fact that the FeatureReader schema reading skips BLOB fields--along with not reading attribute aliases as it is supposed to and not reading feature class aliases or feature datasets--is a different but no less major problem for me. Back to the grindstone! Thanks, David.

Community Stats

32,064
Posts
121,727
Replies
39,690
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.