I have a problem when I do a shape-zip export (with the getfeature request)
from a postgis data source. When a fieldname is too long, the converter
truncate this field. The problem is the content of this field is emptied(I
don’t see the data of this field).
Extract of the log :
2009-06-12 10:35:52,924 WARN [data.shapefile] - FieldName cfa_site_adress is
longer than 10 characters, truncating to cfa_site_a
Is it possible to conserve data alike the namefield is too long??
I do not believe so, as the dbf file format itself limits column names to 10 characters.
-Justin
Loïc E wrote:
Hello everybody,
I’m french, excuse for my approximate english.
I have a problem when I do a shape-zip export (with the getfeature request)
from a postgis data source. When a fieldname is too long, the converter
truncate this field. The problem is the content of this field is emptied(I
don’t see the data of this field).
Extract of the log :
2009-06-12 10:35:52,924 WARN [data.shapefile] - FieldName cfa_site_adress is
longer than 10 characters, truncating to cfa_site_a
Is it possible to conserve data alike the namefield is too long??
Thank’s
Regards, Loïc
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I have a problem when I do a shape-zip export (with the getfeature request)
from a postgis data source. When a fieldname is too long, the converter
truncate this field. The problem is the content of this field is emptied(I
don’t see the data of this field).
Extract of the log :
2009-06-12 10:35:52,924 WARN [data.shapefile] - FieldName cfa_site_adress is
longer than 10 characters, truncating to cfa_site_a
Is it possible to conserve data alike the namefield is too long??
I believe it can be fixed, but it's certainly tricky, as the shapefile
changes the structure of the original feature type (the geometry position is moved, and this is accounted for, some field names are
truncated, and this is not accounted for unfortunately).
Can you open a bug report on jira.codehaus.org and, if possible,
attach a sample data source I can use to test the bug has
actually been solved?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.