[gdal-dev] RFC 21: OGR SQL type cast and field name alias
Even Rouault
even.rouault at mines-paris.org
Fri Jan 25 14:43:24 EST 2008
Tamas,
I'm probably missing something as I have never used the OGR styling
capability, but as far the specific motivation explained in the RFC is
concerned, couldn't it be possible, and more simple, to hack directly in
ogrfeature.cpp a width big enough for the OGR_STYLE special field (it can be
made very big as the shape driver automatically crop it to 255) ?
Your proposal suggests that the user is aware that DBF strings cannot be
bigger than 255 characters, which is not obvious (for example, we don't even
document that in drv_shapefile.html. Would be good to do ;-) )
If I remember well too, FrankW also proposed to add an option to ogr2ogr that
would scan all the features to compute the required with in case it's not set
by the input driver. That could also help in your use case. One drawback is
that ogr2ogr would need to run in 2 passes when this option is used.
Best regards,
Even.
Le Thursday 24 January 2008 23:33:48 Tamas Szekeres, vous avez écrit :
> Folks,
>
> I've put together an RFC to provide support for specifying field name
> alias and the type in the OGR SQL select list. The RFC can be found
> here:
>
> http://trac.osgeo.org/gdal/wiki/rfc21_ogrsqlcast
>
> The corresponding tracking bug that contains the proposed patch:
>
> http://trac.osgeo.org/gdal/ticket/2171
>
> Any comments and ideas about the proposal would be helpful.
>
> Best regards,
>
> Tamas
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
More information about the gdal-dev
mailing list