Currently, the project_crs must be set by hand in the .yml config file and the default is only suitable for California and the nearby regions. For the time being, users can identify the UTM zone by hand using a tool such as this, and then determine the corresponding EPSG CRS code.
However, since we assume that our images have geospatial reference data (e.g. from EXIF metadata or GCPs), we could determine an appropriate UTM zone and corresponding CRS automatically. A python example of this computation is here.
I finally found data where I needed to update this.
Currently, the
project_crsmust be set by hand in the.ymlconfig file and the default is only suitable for California and the nearby regions. For the time being, users can identify the UTM zone by hand using a tool such as this, and then determine the corresponding EPSG CRS code.However, since we assume that our images have geospatial reference data (e.g. from EXIF metadata or GCPs), we could determine an appropriate UTM zone and corresponding CRS automatically. A python example of this computation is here.
I finally found data where I needed to update this.