Opened 10 years ago
Closed 8 years ago
#5405 closed defect (fixed)
[PATCH] Error while read mid/mif files with empty values in data columns
Reported by: | drons | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | 2.0.2 |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | mitab |
Cc: | Daniel Morissette |
Description
When we try to read mid/mif file with empty fields in first several columns GDAL reported error "Error during reading Record". But in fact it is correct mid/mif dataset and MapInfo can read it.
I found an old ticket (#954) in which it is offered to skip tabulation symbols at the beginning of lines in the MIF file (for now tab symbols are skiped in mitab_middatafile.cpp:218). But the symbol of tabulation is a default delimiter of fields ( we can it see at MapInfo ® Data Interchange Format pp 677&693 ) and if we skip it, we won't read empty fields. And in this case feature will be corrupted.
Attachments (2)
Change History (8)
by , 10 years ago
Attachment: | layer1_bad.ZIP added |
---|
comment:1 by , 10 years ago
Cc: | added |
---|---|
Component: | default → OGR_SF |
Keywords: | mitab added |
by , 10 years ago
Attachment: | mitab.diff added |
---|
comment:3 by , 9 years ago
After reading a few of these tickets I feel that every time when a GDAL ticket leads to a mitab ticket and things get corrected on that side, the info never gets back here and GDAL tickets will stay open forever.
What might be the situation with this issue?
comment:4 by , 9 years ago
Summary: | Error while read mid/mif files with empty values in data columns → [PATCH] Error while read mid/mif files with empty values in data columns |
---|
comment:5 by , 8 years ago
Milestone: | → 2.0.2 |
---|
comment:6 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Batch closing of MITAB tickets fixed in GDAL. They were kept open because not merged into MITAB separate repository, but the latter one is inactive, so let's close them definitely.
Buggy mid/mif dataset