Hello,
I would like some help on warning messages coming up while running the model.
The messages I am talking about are the following, they can also be found in the attached log file (from my 1st run):
Warnings regarding masking values from bathymetry and reflief exposure calculation (reprojections):
WARNING [errno 1] The definition of projected CRS EPSG:3035 got from GeoTIFF keys is not the same as the one from the EPSG registry, which may cause issues during reprojection operations. Set GTIFF_SRS_SOURCE configuration option to EPSG to use official parameters (overriding the ones from GeoTIFF keys), or to GEOKEYS to use custom values from GeoTIFF keys and drop the EPSG code.
Warnings regarding seagrass shapefiles:
WARNING [errno 1] Ring Self-intersection at or near point …
WARNING [errno 1] Self-intersection at or near point …
WARNING [errno 1] organizePolygons() received an unexpected geometry. Either a polygon with interior rings, or a polygon with less than 4 points, or a non-Polygon geometry. Return arguments as a collection.
WARNING [errno 1] Geometry of polygon of fid 4821 cannot be translated to Simple Geometry. All polygons will be contained in a multipolygon.
WARNING [errno 1] organizePolygons() received an unexpected geometry. Either a polygon with interior rings, or a polygon with less than 4 points, or a non-Polygon geometry. Return arguments as a collection.
I tried to resolve these issues by reprojecting the bathymetry and DEM files (although I initially already had set the right CRS) and by using a geometry fixing tool on the seagrass shapefile. After running the model again (all the other files and parameters were left the same), no warning messages appeared. I also did a quick check on the exposure results of the two cases (with and without the warnings or before and after fixing the aforementioned files) and it seemed that they were the same.
My questions is: are the warnings auto-treated adequately by the model and thus do not affect the results? If so, it won’t be necessary to fix other files when such messages come up or if not being sure about how the GIS fixing tools affect the quality of the original seagrass file.
I would appreciate any comment on the above.
All the best
InVEST-natcap.invest.coastal_vulnerability-log-2024-09-09–09_25_28.txt (419.7 KB)