Currently, the ard_dir storage scheme follows the pattern
for example
32UMG/S1A_IW_NRB__1SDV_20221230T170954_046564_059481_32UMG_1E7E
It would be good to give flexibility to the user to adjust this.
Potential solution
Introduce a new configuration parameter storage_scheme, which could look like this to reproduce the above:
storage_scheme = {mgrs}/{pid}
where
mgrs: the full name of the MGRS tile
pid: the product identifier
Additional keys for adjusting the scheme could be (including examples following the above):
utm: the UTM zone (32)
gzd: the grid zone designator (32U)
lid: the latitude band identifier (U)
sid: the square identifier (MG)
year: the acquisition year (2022)
month: the acquisition month (12)
The above could also be expressed as
storage_scheme = {utm}{lid}{sid}/{pid}
or
storage_scheme = {gzd}{sid}/{pid}
A more complex example:
storage_scheme = {utm}/{lid}/{sid}/{year}/{month}/{pid}
translating to
32/U/MG/2022/12/S1A_IW_NRB__1SDV_20221230T170954_046564_059481_32UMG_1E7E
Currently, the
ard_dirstorage scheme follows the patternfor example
It would be good to give flexibility to the user to adjust this.
Potential solution
Introduce a new configuration parameter
storage_scheme, which could look like this to reproduce the above:storage_scheme = {mgrs}/{pid}where
mgrs: the full name of the MGRS tilepid: the product identifierAdditional keys for adjusting the scheme could be (including examples following the above):
utm: the UTM zone (32)gzd: the grid zone designator (32U)lid: the latitude band identifier (U)sid: the square identifier (MG)year: the acquisition year (2022)month: the acquisition month (12)The above could also be expressed as
storage_scheme = {utm}{lid}{sid}/{pid}or
storage_scheme = {gzd}{sid}/{pid}A more complex example:
storage_scheme = {utm}/{lid}/{sid}/{year}/{month}/{pid}translating to