Hi Even,
And what about string list field subtype?
I.e. I need restricted String field to accept only predefined strings
from the list?
Also for integer or dates fields the value range(s) or time period(s)
set will be worth adding. I.e. the tube_width (Integer) can only be in
range 100-183 and etc.
And finally I think the default field value is the subtype
responsibility too.
Best regards,
Dmitry
20.11.2014 01:14, Even Rouault пишет:
Hi,
This is a call for discussion on RFC 50: OGR field subtypes
http://trac.osgeo.org/gdal/wiki/rfc50_ogr_field_subtype
Below the summary :
"""
This RFC aims at adding the capability of specifying sub-types to OGR fields,
like boolean, 16 bit integers or 32 bit floating point values. The sub-type of
a field definition is an additional attribute that specifies a hint or a
restriction to the main type. The subtype can be used by applications and
drivers that know how to handle it, and can generally be safely ignored by
applications and drivers that do not.
"""
Even
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
