Rather than using the gbucket_to_gcloud_*.sh scripts to upload images into the GEE storage under my personal account (which is limited to 250GB), assets can be created which use google gloud storage (GCS).
A combination of the python code from this article and the gee-uploads/gbucket_to_gee_w_metadata_rookery_rrs.sh will allow us to create an imageCollection asset full of image assets which are stored in GCS and have the full metadata properties taken from the .xml files associated with each .tif.
This all seems straightforward until the "configuration" section, wherein requirements for sizing of square tiles are given. Does this mean we need to convert our irregularly sized pass images into square tiles in order for them to be considered "COGs"?
Rather than using the
gbucket_to_gcloud_*.shscripts to upload images into the GEE storage under my personal account (which is limited to 250GB), assets can be created which use google gloud storage (GCS).A combination of the python code from this article and the
gee-uploads/gbucket_to_gee_w_metadata_rookery_rrs.shwill allow us to create an imageCollection asset full of image assets which are stored in GCS and have the full metadata properties taken from the .xml files associated with each .tif.This all seems straightforward until the "configuration" section, wherein requirements for sizing of square tiles are given. Does this mean we need to convert our irregularly sized pass images into square tiles in order for them to be considered "COGs"?