Hi all -
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.
I changed the code to continue to increment the required fId until it
gets 20 consecutive -1 returns. This now runs fine and tells me that
my file has 6 corrupt records starting around record # 90000, but I
can continue and read the rest of the file (146,000 records).
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?
Is there any way to get more information about the corruption? Would
the C++ interface help me out in this regard?
Any help is greatly appreciated...
mp
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/
