Skip to main content
Solved

Reader does not recognize the MapInfo TAB files

  • August 23, 2016
  • 10 replies
  • 138 views
T
Forum|alt.badge.img

Dear FME friends,

I am using FME 2016 64-bit 16174. My workspace throws up an error with the following message.

0.0|ERROR |No specified layers were found in MapInfo Dataset

I removed the readers and inserted them again. Still do not read. Any idea?

Thanks in advance.

Best answer by itay

@thiru I would also recommend contacting safe about this issue, hopefully they can have a look at it too.

1 Attachments
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.

10 replies

itay
Supporter
Forum|alt.badge.img+18
  • itaySupporter
  • Supporter
  • August 23, 2016

Hi,

Have you tired reading it in a new workspace?

T
Forum|alt.badge.img
  • thiru
  • Author
  • August 23, 2016

Hi,

Have you tired reading it in a new workspace?

Yep, tried. Still it is not reading. 487491 MapInfo LINE objects present in this 26 mb file.

 

 

It certainly worked before in the same workspace that I am trying to run.

 

 

Now, even a simple translation is not successful.
T
Forum|alt.badge.img
  • thiru
  • Author
  • August 23, 2016

Hi,

Have you tired reading it in a new workspace?

 

I am going to install the latest 32-bit version and try this.
srg
Forum|alt.badge.img+10
  • srg
  • August 23, 2016

Did you try viewing the dataset using FME Data Inspector (64 bit)?

itay
Supporter
Forum|alt.badge.img+18
  • itaySupporter
  • Supporter
  • August 23, 2016

very annoying! Any luck after restarting the machine and purging the temp files (Tools > Purge Temporary Files)?

itay
Supporter
Forum|alt.badge.img+18
  • itaySupporter
  • Supporter
  • Best Answer
  • August 23, 2016

@thiru I would also recommend contacting safe about this issue, hopefully they can have a look at it too.

mark2atsafe
Safer
Forum|alt.badge.img+59
  • mark2atsafeSafer
  • Safer
  • August 24, 2016

@thiru I would also recommend contacting safe about this issue, hopefully they can have a look at it too.

Yes, I think this is a good idea. However, that particular reader uses a library from MapInfo that we have no control over. If the problem is in there we will report it to them, but there is no way to know when it would get fixed.

 

 

An alternative solution is to use the MapInfo (MITAB) reader. It should read the MapInfo data almost identically, but may not have the same problem as the MapInfo (MAPINFO) reader.

 

FME Evangelist to the Rich and Famous!!
T
Forum|alt.badge.img
  • thiru
  • Author
  • August 28, 2016
Yes, I think this is a good idea. However, that particular reader uses a library from MapInfo that we have no control over. If the problem is in there we will report it to them, but there is no way to know when it would get fixed.

 

 

An alternative solution is to use the MapInfo (MITAB) reader. It should read the MapInfo data almost identically, but may not have the same problem as the MapInfo (MAPINFO) reader.

 

Using the MITAB reader fixes the issue. Great tip. Thanks @Mark2AtSafe

 

T
Forum|alt.badge.img
  • thiru
  • Author
  • August 28, 2016

very annoying! Any luck after restarting the machine and purging the temp files (Tools > Purge Temporary Files)?

Thanks @itay for your suggestions. Appreciate your time and efforts in suggesting workarounds. Was on break, back at work today.
mygis
Supporter
Forum|alt.badge.img+14
  • mygisSupporter
  • Supporter
  • August 16, 2017

Hi @thiru . Do you have MapInfo? Have you tried opening the file with MapInfo ? Sometimes it is just that the file is corrupted.

Community Stats

32,154
Posts
122,043
Replies
39,812
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.