#5192 closed defect (fixed)
FileGDB driver creates fields with a weird Length
Reported by: | Even Rouault | Owned by: | Even Rouault |
---|---|---|---|
Priority: | normal | Milestone: | 1.11.0 |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | filegdb |
Cc: |
Description
Reported as http://lists.osgeo.org/pipermail/gdal-dev/2013-August/036826.html
Length is in bytes per doc of FileGDB_API/xmlResources/FileGDBAPI.xsd. Typical values are given in FileGDB_API/samples/XMLsamples/OneOfEachFieldType.xml
Change History (8)
comment:1 by , 11 years ago
follow-up: 4 comment:2 by , 11 years ago
Milestone: | → 2.0 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
No feedback from reported. Assuming it is OK
comment:3 by , 10 years ago
Milestone: | 2.0 → 1.11.0 |
---|
comment:4 by , 9 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Replying to rouault:
No feedback from reported. Assuming it is OK
I've tried with 1.11.1 and it's seem to have the same behavior.
comment:5 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Your issue is different and about string fields, whereas the fix in that ticket was about non-string fields. Please check if there's not another ticket about that (I remember a recent exchange on that) and open a dedicated ticket.
comment:6 by , 9 years ago
I guess you're right.
According to this ticket: https://trac.osgeo.org/gdal/ticket/4448
This issue will be solve in gdal 2.x?
Thanks.
comment:7 by , 9 years ago
At that time of the ticket, "GDAL 2" should be now understood as GDAL 1.10. Your issue is more about the width of a string field not being reported (i.e. being set to 0) when reading a filegdb file
trunk r26283 "FileGDB: when writing <Length> of an attribute, use size in bytes (#5192)"