The display in the ArcGISPro table does not show the extra decimal point. In fact, they are the desired values. They are the same as the original double field, it is what I expect to see when I inspect the float field with arcpy.da.SearchCursor.
I tried the following ways in calculating the value in the float field
1. using arcpy.da.UpdateCursor
with arcpy.da.UpdateCursor(in_table = feat_cls_fp, field_names = [field_name, new_field_name]) as cursor:
for row in cursor:
row[1] = row[0]
cursor.updateRow(row)
2. Using arcpy.management.CalculateField
arcpy.management.CalculateField(
in_table = feat_cls_fp,
field = new_field_name,
field_type = new_field_type,
expression=f"!{field_name}!",
expression_type="PYTHON3",
enforce_domains="NO_ENFORCE_DOMAINS"
)
In the above code, The new_field_name is the float field name, the field_name is the double field name.
and I check their consistency by the following custom function, which is basically using arcpy.da.SearchCursor
def get_field_values(cls, feat_cls_fp: str, field_name:str) -> list:
table = arcpy.da.SearchCursor(
in_table = feat_cls_fp,
field_names = field_name,
spatial_reference = arcpy.Describe(feat_cls_fp).spatialReference
)
return [row[0] for row in table]
field_values = get_field_values(feat_cls_fp, field_name)
new_field_values = get_field_values(feat_cls_fp, new_field_name)
assert field_values == new_field_values, f'Field {field_name} values changed after changing data type.'
but none of them produces the desired output and passes the assertion check.
the field_values are the same with the op fieldA value, which is the original double values
the new_field_values are the same with the op fieldB value, which is the converted float value, which has the extra decimal point after update/calculation.
I have also tried to create a new field with arcpy.management.AddField, specifying the field type as 'FLOAT' and the field_precision and field_scale as 6. but it does not suppress the extra decimal point either.
