Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

persistent error : Invalid product selection. Please check the 'product_available' dataframe #13

Open
saberioon opened this issue Jun 4, 2020 · 7 comments

Comments

@saberioon
Copy link

When I try espa_order function, it gives me Invalid product selection. Please check the 'product_available' datagram.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

Context (Environment)

Detailed Description

Possible Implementation

@robinh92
Copy link

robinh92 commented Jun 9, 2020

I've also been having the same issue and have been unable to find a solution. Debugging the espa_order() function it looks like it's returning an error in the first step when it's checking (sum(product %in% colnames(valid)) != length(product)).

product_id <- c("LC08_L1TP_145049_20180605_20180615_01_T1")
prod_order <- espa_order(product_id, product = "sr")

valid = espa_products(input_ids = input_ids, host = host, 
    username = username, password = password)
  if (!is.null(valid)) {
    valid = valid$master
    if (sum(product %in% colnames(valid)) != length(product)) {
      cat("Invalid product selection. Please check the 'product_available' dataframe\n")
      return(list(order_details = list(), response = NA, 
        product_available = valid))
    }
...
...

For the above example (and every attempt I've made), valid$master is a matrix with the product_id(s) as BOTH row and column headers. So when it checks the product (i.e. "sr") in column names it can't find a match despite the product being available. I haven't dug into espa_products() to see how it's creating valid. Maybe there's been a slight change in the format of the API output?

@fishish1
Copy link

fishish1 commented Aug 5, 2020

I'm seeing this as well

@zhayuan87
Copy link

me too...

@fishish1
Copy link

fishish1 commented Aug 7, 2020

After some digging, there is a discrepancy between what is available via NASA Earth Explorer and AWS. I'm seeing a dataset from 2020-08-03 which still isn't on AWS.

@fishish1
Copy link

fishish1 commented Aug 7, 2020

Pretty much everything I've seen accesses data via aws rather than directly.

@ErikKusch
Copy link

ErikKusch commented Oct 22, 2020

Exact same issue here. Even when running the Example code off the front page for the project here on github:

result = landsat_search(min_date = "2018-01-01", max_date = "2018-01-16", country = "India")
espa_creds("yourusername", "yourpassword")
prods = espa_products(result$product_id)
prods = prods$master
result_order = espa_order(result$product_id, product = c("sr","sr_ndvi"),
projection = "lonlat",
order_note = "All India Jan 2018")
order_id = result_order$order_details$orderid

This results in order_id == NULL and I am sure it should not

@erdavis1
Copy link

erdavis1 commented Jul 3, 2021

Chiming in as well-this issue is still occurring with the example code (as noted by Erik Kusch). Any chance this will be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants