Skip to main content
Archived

Improved File Geodb API Reader Error Detection

Related products:Integrations
  • rylanatsafe
    rylanatsafe
  • siennaatsafe
    siennaatsafe
  • davideagle
    davideagle
  • chriswilson
    chriswilson
  • mark_f

Recently have an example where an attribute for a feature in an Esri Geodatabase where the GDB could be read by FME 2014 SP3 but with FME 2015, 2016 and 2017 the Reader dropped features with no warning message. Opening the GDB in FME 2014 Data Inspector shows some unusual characters in an attribute value.

Tried the File Geodb ArcObjects reader and it writes a useful warning into the log:

2017-08-10 17:30:45|   1.5|  0.0|WARN  |Unable to retrieve feature from table/feature class 'IC_POINT'. This feature, and any other feature from 'IC_POINT' that cannot be read, will be skipped. The error number from ArcObjects is: '-2147418113'. The error message from ArcObjects is: {Unexpected operation [IC_POINT]}

Requesting better messages/error detection when reading the GDB with the File Geodb API reader similar to the File Geodb ArcObjects or stop reading the file. It would be then possible to manage rather than losing data.


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.

5 replies

rylanatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • August 10, 2017

Hi @mark_1spatial - I agree that this isn't expected (or desired) behaviour. I did an internal search and this is recorded internally as PR#38342. I suggest contacting Safe Support to open a Support Ticket and request to receive notification regarding progress. I have elevated the priority of the aforementioned internal pr.

(Assuming that I have not misinterpreted that development ticket...)


Forum|alt.badge.img+2
  • Author
  • August 11, 2017
Already opened ticket C129863

 

 


david_r
Celebrity
  • August 11, 2017

Out of curiosity, what happens to those features when read by a FeatureReader? Are they also dropped, or do they exit the <Rejected> port?


Forum|alt.badge.img+2
  • Author
  • August 11, 2017
Dropped - nothing out of the <Rejected> port for both formats (API and ArcObjects)

 

Nice idea though!

david_r
Celebrity
  • August 11, 2017
Thanks for testing! Personally I'd call that bug that really ought to be fixed.

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