I’m experiencing this problem, exporting a vector file with a table associated, several columns are exported but two of them are dropped, and the error is not informative:
ERROR 6: Failed to add field named ‘wetness_idx’
ERROR 6: Failed to add field named ‘elevabovestr’
I’m struggling to ask it why, but it doesn’t speak, even in verbose mode. I’m on G 7.1.svn (r63559)
Any pointers please
···
Best regards,
Dr. Margherita DI LEO
Scientific / technical project officer
European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261
Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.
I'm experiencing this problem, exporting a vector file with a table
associated, several columns are exported but two of them are dropped,
and the error is not informative:
ERROR 6: Failed to add field named 'wetness_idx'
ERROR 6: Failed to add field named 'elevabovestr'
I'm struggling to ask it why, but it doesn't speak, even in verbose
mode. I'm on G 7.1.svn (r63559)
Are you exporting to shapefile ?
There is a 10-letter limit to column names and apparently also a 255 columns limit:
Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.
Oops, thanks! that solved. is there no way to get grass speak that, at
least in verbose mode?
AFAICT, the error message comes from OGR, not GRASS. So best would be to get OGR to provide a more helpful error message. I don't think it would be very practical for GRASS to check for OGR errors and then translate them to something more understandable.
AFAICT, the error message comes from OGR, not GRASS. So best would be to
get OGR to provide a more helpful error message. I don't think it would be
very practical for GRASS to check for OGR errors and then translate them
to something more understandable.
Moritz/Madi:
Perhaps the most practical solution, at least for the interim, would be to
add a note to the module man page that if exporting to shapefiles ensure
column names are no loger than 10 characters. Unfortunate limitation in this
day and age, but we gotta' live with it.
On Wed, Dec 17, 2014 at 4:57 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
On Wed, 17 Dec 2014, Moritz Lennert wrote:
AFAICT, the error message comes from OGR, not GRASS. So best would be to
get OGR to provide a more helpful error message. I don't think it would be
very practical for GRASS to check for OGR errors and then translate them
to something more understandable.
Moritz/Madi:
Perhaps the most practical solution, at least for the interim, would be to
add a note to the module man page that if exporting to shapefiles ensure
column names are no loger than 10 characters. Unfortunate limitation in this
day and age, but we gotta' live with it.