Hi,
this comes from https://trac.osgeo.org/gdal/ticket/4458
The full list of laundered field name is at
https://github.com/OSGeo/gdal/blob/94625cba3367c5709175e5b7a037febe737742f0/ogr/ogrsf_frmts/filegdb/FGdbUtils.cpp#L522
There's a hidden -lco LAUNDER_RESERVED_KEYWORDS=FALSE layer creation
option (will only work if you just created the layer. to be opposed to
updating an existing one) to disable this, but this might apparently
cause issues with ArcMap. At least it did in the past
Even
Le 13/05/2022 à 19:11, adamgutonski via gdal-dev a écrit :
Hello,
I am attempting to create an ogr.OFTDateTime field named "date",
within a file geodatabase table. However anytime a field definition
is created with the name "date", once the layer tries to create the
field, I get receive a warning:
*Warning 6: Normalized/laundered field name: 'date' to 'date_'*
Why does this field need to be normalized? Is there anyway to
suppress this warning and retain the "date" string that is expected as
the field name? Are there other field names besides *date* that will
always be normalized?
Below is my code snippet:
/field_defn = ogr.FieldDefn("date", ogr.OFTDateTime)/
/layer.CreateField(field_defn)/
Thank you for your time as always!
Sincerely,
Adam Gutonski
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
