meebparker wrote: > > I have been using MiTab since 2002 to read road files for a routing > application. Recently I came across a corrupt fileset that was > causing mitab_c_next_feature_id to return -1 at the corrupt record. >
How do you know it's corrupt? And how do you know it's the .DAT and not the .MAP or another file that's corrupt? What error message does MITAB return if you call mitab_c_getlasterrorno() after you got -1? > > My question: is there a better way to deal with the corrupt file? > i.e., better than continuing until I get a whole bunch of EOFs in a row? > The best way would be to go back to the data provider and get a clean file of course, or to clean/fix the file if possible. > Is there any way to get more information about the corruption? Would > the C++ interface help me out in this regard? > You could try using the tabdump program to examine your files, but unless MITAB spits out some meaningful error message right away, you would need to understand the structure of the format in order to understand the output. (FYI tabdump.cpp is in the mitab directory but is not compiled by default) Daniel -- ------------------------------------------------------------ Daniel Morissette [EMAIL PROTECTED] DM Solutions Group http://www.dmsolutions.ca/ ------------------------------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/mitab/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
