Re: [GRASS-dev] Fwd: [QGIS Application - Bug report #19733] v.rast.stats is broken due to parsing error of double underscore in column names

2018-09-01 Thread Markus Neteler
On Sat, Sep 1, 2018 at 7:14 PM Markus Metz
 wrote:
> On Sat, Sep 1, 2018 at 6:07 PM Markus Metz  
> wrote:
...
> > this is a GDAL error message also happening in GRASS directly:
> >
> > [...]
> > > v.out.ogr --overwrite -s -e input=tmp15356101025715 
> > > output="/tmp/processing5113522d9c174e7bb445f24ef38c5f5a/135e78c4ae1d430da568b502506b4ab0"
> > >  format=ESRI_Shapefile output_layer=output
> > > [...]
> > > ERROR 6: Failed to add field named 's_third_quartile'
> > > ERROR 6: Failed to add field named 's_percentile_2'
> >
> > the underscores are not the problem because exporting columns like 's_t_q' 
> > and 's_p_2' works. The field names are too long for dbf (max 10 characters).

Oh, in fact I didn't try with SHP file format (meanwhile I tend to
forget about it :-)

> > The solution would be to allow that "the field may be created in a slightly 
> > different form depending on the limitations of the format driver" [0] in 
> > v.out.ogr. The ERROR 6 would then change to e.g.
> >
> > Warning 6: Normalized/laundered field name: 's_third_quartile' to 
> > 's_third_qu'
>
> another solution would be that QGIS uses GeoPackage instead of ESRI Shapefile 
> as vector data exchange format

I have proposed the latter in the now updated QGIS ticket:
https://issues.qgis.org/issues/19733

Thanks for your analysis!

markusN
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [QGIS Application - Bug report #19733] v.rast.stats is broken due to parsing error of double underscore in column names

2018-09-01 Thread Markus Metz
On Sat, Sep 1, 2018 at 6:07 PM Markus Metz 
wrote:
>
>
>
> On Sat, Sep 1, 2018 at 7:58 AM Markus Neteler  wrote:
> >
> > Hi devs,
> >
> > does anyone have an idea how to fix this issue in QGIS processing?
>
> this is a GDAL error message also happening in GRASS directly:
>
> [...]
> > v.out.ogr --overwrite -s -e input=tmp15356101025715
output="/tmp/processing5113522d9c174e7bb445f24ef38c5f5a/135e78c4ae1d430da568b502506b4ab0"
format=ESRI_Shapefile output_layer=output
> > [...]
> > ERROR 6: Failed to add field named 's_third_quartile'
> > ERROR 6: Failed to add field named 's_percentile_2'
>
> the underscores are not the problem because exporting columns like
's_t_q' and 's_p_2' works. The field names are too long for dbf (max 10
characters). The solution would be to allow that "the field may be created
in a slightly different form depending on the limitations of the format
driver" [0] in v.out.ogr. The ERROR 6 would then change to e.g.
>
> Warning 6: Normalized/laundered field name: 's_third_quartile' to
's_third_qu'

another solution would be that QGIS uses GeoPackage instead of ESRI
Shapefile as vector data exchange format

>
> Markus M
>
> [0] https://gdal.org/ogr__api_8h.html#aab585ef1166c61c4819f7fd46ee4a275
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [QGIS Application - Bug report #19733] v.rast.stats is broken due to parsing error of double underscore in column names

2018-09-01 Thread Markus Metz
On Sat, Sep 1, 2018 at 7:58 AM Markus Neteler  wrote:
>
> Hi devs,
>
> does anyone have an idea how to fix this issue in QGIS processing?

this is a GDAL error message also happening in GRASS directly:

[...]
> v.out.ogr --overwrite -s -e input=tmp15356101025715
output="/tmp/processing5113522d9c174e7bb445f24ef38c5f5a/135e78c4ae1d430da568b502506b4ab0"
format=ESRI_Shapefile output_layer=output
> [...]
> ERROR 6: Failed to add field named 's_third_quartile'
> ERROR 6: Failed to add field named 's_percentile_2'

the underscores are not the problem because exporting columns like 's_t_q'
and 's_p_2' works. The field names are too long for dbf (max 10
characters). The solution would be to allow that "the field may be created
in a slightly different form depending on the limitations of the format
driver" [0] in v.out.ogr. The ERROR 6 would then change to e.g.

Warning 6: Normalized/laundered field name: 's_third_quartile' to
's_third_qu'

Markus M

[0] https://gdal.org/ogr__api_8h.html#aab585ef1166c61c4819f7fd46ee4a275
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev