Opened 15 years ago
Last modified 15 years ago
#2746 closed defect
.dbf files; inconsistencies with date formats — at Version 1
Reported by: | j03lar50n | Owned by: | ashrafroni |
---|---|---|---|
Priority: | normal | Milestone: | 1.6.1 |
Component: | OGR_SRS | Version: | 1.6.0 |
Severity: | normal | Keywords: | .dbf shape date |
Cc: | warmerdam, Markus Neteler |
Description (last modified by )
Inconsistencies in date formats within .dbf's of shapefiles have been noticed when loading a particular .shp in QGIS, OpenJump, MapWindow and OGR.
In particular the sample .dbf file has a installe_1 date field for which the first record is reported by OGR as 0000/00/04 while the actual text in the file (as reported by shapelib's dbfdump) is "04/25/1989".
Change History (2)
by , 15 years ago
Attachment: | water_main_dist.zip added |
---|
comment:1 by , 15 years ago
Cc: | added |
---|---|
Component: | default → OGR_SRS |
Description: | modified (diff) |
Keywords: | shape added |
Owner: | changed from | to
Version: | unspecified → 1.6.0 |
Roni,
Please treat this as your top priority bug report to work on. You will need to review the literature on dbf file date formatting to figure out if there is some systematic way to know date formats in .dbf formats. The OGR Shapefile driver uses shapelib for dbf access (http://shapelib.maptools.org) (also maintained by me), but the date support is quite new. http://www.clicketyclick.dk/databases/xbase/format/ may be a useful resource on dbf formats.
We must take care not to break other dbf files with dates while fixing this ticket. Note that this file is properly supported by some other applications (mapwindow, and excel) which presumably use some microsoft supplied dbf parser.
.dbf file for Ticket #2746