You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In landsat_prep_path_row.py the path for the wrs2_tile_utm_zones.json is hardcoded to the footprint workspace. The problem with this is that this JSON file is provided as part of the repository, but the footprints can be downloaded to a different folder (i.e. outside of pymetric). This path could be set as part of the project INI, the path could be set relative to the script location, or we might just need to add some text to the docs making it clear that the footprints should always be downloaded to the pymetric\landsat\footprints folder.
The text was updated successfully, but these errors were encountered:
I added code to the download_footprints.py script that will attempt to copy this file to the output folder (if the output folder is set and the file doesn't exist). I don't think this is the best solution or closes the issue, but hopefully it will reduce the impact of this issue a little.
In landsat_prep_path_row.py the path for the wrs2_tile_utm_zones.json is hardcoded to the footprint workspace. The problem with this is that this JSON file is provided as part of the repository, but the footprints can be downloaded to a different folder (i.e. outside of pymetric). This path could be set as part of the project INI, the path could be set relative to the script location, or we might just need to add some text to the docs making it clear that the footprints should always be downloaded to the pymetric\landsat\footprints folder.
The text was updated successfully, but these errors were encountered: