Opened 21 months ago

Closed 17 months ago

Last modified 17 months ago

#6392 closed defect (fixed)

Honor the limits of decimal number field in MapInfo

Reported by: Jukka Rahkonen Owned by: warmerdam
Priority: normal Milestone: 1.11.5
Component: OGR_SF Version: unspecified
Severity: normal Keywords: mitab
Cc:

Description

In the file formats of Mapinfo the maximum field width of a decimal number is 20 characters, and the maximum precision is width - 2 (for decimal point and sign), up to a maximum of 16 characters. Thus the largest valid number format is (20,16). However, GDAL can write Mapinfo files which define the field for example as (23,15). This makes Mapinfo to crash.

Issue was found from gis.stacexchange http://gis.stackexchange.com/questions/180627/qgis-ogr-shp-to-tab-export-crashing-mapinfo-due-to-number-format-issues

Change History (5)

comment:1 Changed 17 months ago by Even Rouault

Resolution: fixed
Status: newclosed

In 34413:

MITAB: limit (width, precision) of numeric fields on creation to (20,16) for compatibility with MapInfo? (fixes #6392)

comment:2 Changed 17 months ago by Even Rouault

In 34414:

MITAB: limit (width, precision) of numeric fields on creation to (20,16) for compatibility with MapInfo? (fixes #6392)

comment:3 Changed 17 months ago by Even Rouault

In 34415:

MITAB: limit (width, precision) of numeric fields on creation to (20,16) for compatibility with MapInfo? (fixes #6392)

comment:4 Changed 17 months ago by Even Rouault

In 34416:

MITAB: limit (width, precision) of numeric fields on creation to (20,16) for compatibility with MapInfo? (fixes #6392)

comment:5 Changed 17 months ago by Even Rouault

Component: defaultOGR_SF
Keywords: mitab added
Milestone: 1.11.5
Note: See TracTickets for help on using tickets.