#2584: Vectors skipping columns (character limit !!!) while exporting to OGR data
----------------------------+-----------------------------------------------
Reporter: spareeth | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: LibVector | Version: svn-trunk
Keywords: OGR, shapefile | Platform: Linux
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Hi
I am trying to export a vector data with many columns to shape format. But
it seems it is avoiding all the columns with greater than 10 characters
(from the pattern, not sure). Tried in GRASS 6.4.5, GRASS 7.0 svn and
GRASS 7.1 svn, giving the same error.
Please find attached the packed vector layer which i tried.
{{{
v.out.ogr input=test output=test_output.shp
}}}
gives me following error, but finishes the job with remaining columns.
{{{
ERROR 6: Failed to add field named 'int_minimum'
ERROR 6: Failed to add field named 'int_maximum'
ERROR 6: Failed to add field named 'int_average'
ERROR 6: Failed to add field named 'int_variance'
ERROR 6: Failed to add field named 'int_coeff_var'
ERROR 6: Failed to add field named 'int_first_quartile'
ERROR 6: Failed to add field named 'int_third_quartile'
ERROR 6: Failed to add field named 'int_percentile_90'
}}}
On Tue, Feb 10, 2015 at 12:13 PM, GRASS GIS <trac@osgeo.org> wrote:
#2584: Vectors skipping columns (character limit !!!) while exporting to OGR data
----------------------------±----------------------------------------------
Reporter: spareeth | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: LibVector | Version: svn-trunk
Keywords: OGR, shapefile | Platform: Linux
Cpu: Unspecified |
----------------------------±----------------------------------------------
Hi
I am trying to export a vector data with many columns to shape format. But
it seems it is avoiding all the columns with greater than 10 characters
(from the pattern, not sure). Tried in GRASS 6.4.5, GRASS 7.0 svn and
GRASS 7.1 svn, giving the same error.
Please find attached the packed vector layer which i tried.
{{{
v.out.ogr input=test output=test_output.shp
}}}
gives me following error, but finishes the job with remaining columns.
{{{
ERROR 6: Failed to add field named ‘int_minimum’
ERROR 6: Failed to add field named ‘int_maximum’
ERROR 6: Failed to add field named ‘int_average’
ERROR 6: Failed to add field named ‘int_variance’
ERROR 6: Failed to add field named ‘int_coeff_var’
ERROR 6: Failed to add field named ‘int_first_quartile’
ERROR 6: Failed to add field named ‘int_third_quartile’
ERROR 6: Failed to add field named ‘int_percentile_90’
}}}
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
On Thu, Feb 12, 2015 at 6:58 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Wed, Feb 11, 2015 at 12:32 PM, Luca Delucchi <lucadeluge@gmail.com>
wrote:
> On 10 February 2015 at 18:58, Newcomb, Doug <doug_newcomb@fws.gov>
wrote:
>> The shape file format has a 10 character limit on field name length.
The
>> smallest field name I see above is 11.
...
> Yes, but If I remember well v.out.ogr was cutting the field name
> length more then 10. Am I wrong?
I also seem to remember that before v.out.ogr would export all columns,
even if they had field names of more than 10 characters. In those cases it
would simply use the first 10 characters as column name. Or am I confusing
this with other software I have used in the past? I think it would in any
case be better to export those fields with truncated field names than to
skip them.
On 12 February 2015 at 20:20, Paulo van Breugel <p.vanbreugel@gmail.com> wrote:
I also seem to remember that before v.out.ogr would export all columns, even
if they had field names of more than 10 characters. In those cases it would
simply use the first 10 characters as column name. Or am I confusing this
with other software I have used in the past? I think it would in any case be
better to export those fields with truncated field names than to skip them.
