@swolny yeah CV is kind of unique in this respect because while it has a few raster input requirements, it’s main computations are not based on a stack of aligned rasters like many other invest models. The individual raster inputs (DEM, bathymetry, population) are never involved in a computation that includes more than one of those rasters at a time. For each raster, values are extracted at or around the shore point vector (<-- that’s an oversimplification). So it’s not neccesarry for the rasters to be exactly aligned with one another, or to have the same resolution as one another.
If a raster needs to be transformed from a geographic projection, the target pixel size comes from the user-input
model resolution. That input’s main purpose being to specify the spacing of shore points along the coastline, but it serves double-duty in this case.
If we want to, we could add to that warning message to also say: “WARNING D:/coastalvulnerable/DEM_xiamen.tif is unprojected and will be warped to match the AOI and resampled to a pixel size of 1000 meters. If that is not an appropriate pixel size for this raster, you may use a raster with a projected coordinate system and it will not be resampled.”