Fields not successfully written due to large number with respect to field width

NatCap Software Support
1

Dear NatCap Developers,

I am currently running the InVEST SDR model on a global scale. I successfully ran the model, but at the very end (starting from 2023-09-28 13:59:51,658) encountered some of these error messages:

2023-09-28 13:59:51,658 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Creating a 256th field, but some DBF readers might only support 255 fields
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1040000010 of field HYBAS_ID of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1040000010 of field NEXT_SINK of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1040000010 of field MAIN_BAS of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 15138.7000000000007 of field ria_ha_ssu of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 99168.6000000000058 of field riv_tc_ssu of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 4868.85000000000036 of field pop_ct_ssu of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 54.4339999999999975 of field pop_ct_usu of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,673 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 20.5120000000000005 of field ppd_pk_sav of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,674 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 6771.25 of field ppd_pk_uav of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,675 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 20056200000 of field gdp_ud_ssu of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,675 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1726720000 of field gdp_ud_usu of feature 0 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,676 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1040003990 of field HYBAS_ID of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,676 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1040003990 of field NEXT_SINK of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,676 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 1040003990 of field MAIN_BAS of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,677 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 8114.4399999999996 of field ria_ha_ssu of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,678 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 24.0189999999999984 of field ria_ha_usu of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,678 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 29818.4000000000015 of field riv_tc_ssu of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,678 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 49.0499999999999972 of field riv_tc_usu of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,678 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 2011.84999999999991 of field pop_ct_ssu of feature 1 not successfully written. Possibly due to too larger number with respect to field width
2023-09-28 13:59:51,679 (osgeo) utils._log_gdal_errors(97) WARNING [errno 1] Value 18.4959999999999987 of field ppd_pk_sav of feature 1 not successfully written. Possibly due to too larger number with respect to field width

The full documentation is attached.

InVEST-natcap.invest.sdr.sdr-log-2023-09-28–12_03_18.txt.zip (414.4 KB)

I was wondering what do these errors mean and how did they affect my results.

I look forward to your input(s).

Best regards,

Maulana

2

Hi @maulanapajie , good question, these are warnings about some of the values being written to the attribute table of a shapefile that the model created. Given the schema of the fields of the table, some of the values do not fit into the table.

It looks like these are all fields that originate from the watersheds input dataset, and the model is simply trying to copy over all those fields & values to one of the output datasets. I don’t think you need to worry about this, and if you wanted these warnings to go away, you could consider removing all those fields from the watersheds layer before passing it into the model.

3

Hi @dave !

Thanks for your answer. I don’t mind these warnings. Just wanted to make sure they are not “messing” with my output values.

Anyways, thanks for clarifying!

Best,
Maulana

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.