Skip to content

Product list error #14

@sheilasaia

Description

@sheilasaia

Thank you very much for developing this package! I'm very glad it's around and being supported by rOpenSci. 😄

I wanted to ask if it would be possible to pull/provide metadata in a lookup dataframe for the products names that are available as well as the second level of products (I'm calling them subproducts) available? For example, for Landsat data, you could select "landsat_ot_c2_l2" or "landsat_etm_c2_l2" as well as a numbers of others. I got the formatting for these from another package called getSpatialData. This would be helpful since I'm new to these datasets and don't necessarily know what the required formatting and case is. For the "landsat_ot_c2_l2" product the list of available sub products would also be helpful to have as a lookup table. Something like subproduct_list <- c("l1", "sr_ndvi", "sr_evi", "sr_savi", "sr_msavi", "sr_ndmi", "sr_nbr", "sr_nbr2", "sr_ndsi", "stats", "et") as well as how to download specific/all bands.

I'm posting this suggestion because I'm running into an error that I posted below. I think more information on the subproducts could be helpful for solving this. Specifically, I noticed that the args input in the rsat_download() function documentation isn't spelled out and (for landsat data at least) the product is being used to define the subproduct, which is likely why I'm getting an error. Once I run the code with product = c("sr_ndvi", "sr") then my code will run ok and place the image order.

Error was:

Warning: Defined products are not available for image LANDSAT_IMAGE_NAME Warning: Products l1, sr_ndvi, sr_evi, sr_savi, sr_msavi, sr_ndmi, sr_nbr, sr_nbr2, sr_ndsi, stats, et, LANDSAT_IMAGE_NAME Error in con$espaOrderImage(names(x[i]), verbose = verbose, product = product) : no loop for break/next, jumping to top level

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions