Request Builder - Third Party Data Import - Single date not working

Bugs & Features
1

Hello!

We noticed that single date option when trying to create a subscription for Planet is not working. Even though we turn that switch on, the payload still has a timeRange.to:

    "data": [
      {
        "itemType": "PSScene",
        "productBundle": "analytic_8b_sr_udm2",
        "dataFilter": {
          "timeRange": {
            "from": "2022-02-03T00:00:00Z",
            "to": "2022-04-25T23:59:59Z"
          },
          "maxCloudCoverage": 100
        },
        "harmonizeTo": "NONE"
      }
    ]

(search request also keeps the to so the search doesn’t find anything since from and to end up being defined as the same day)

We cannot even edit that manually and our subscription is getting created incorrectly. Also, with analytic_8b_sr_udm2 we could also user harmonizeTo right? We would like to put the Sentinel-2 option there but we can’t do that either. The request is not being parsed when modified.

Is there any workaround for this right now? Or our best option would be to use an HTTP Client like Postman for now?

Besides this, we’ve noticed another bug that happens sometimes, where searching for Planet available data enters in an infinite requests loop:

Screen Shot 2022-04-25 at 12.09.53
Screen Shot 2022-04-25 at 12.09.531280×1766 283 KB

Not exactly sure how this happens, but we need to cancel the search request to stop this. We just filled all the fields, mark the single date option and the search enters the loop (doesn’t happen every time).

Please, if there’s anything we’re missing on our side or if you need more info let us know.

Thanks!

2

Hi @minian.matias ,

Thank you for reporting the bug, we will investigate and fix it asap.

Meanwhile, to workaround you can simply set the time interval to a single date, i.e., from "2022-02-03T00:00:00Z" to "2022-02-03T23:59:59Z".

Regarding the infinite loop, it doesn’t seem to be really infinite but very long because your query returns a lot of hits. Our recommendation would be narrowing down your query if you want to stick use Request Builder (until this is fixed).

Best Regards

3

Hey!

Thanks for the quick reply. Regarding the single date, we tried using that, but that’s the issue. AFAIK turning single date on would delete the timeRange.to from the request, but it’s not doing that, hence each subscription being created has an end date instead of an indefinite one.

Related to the infinite loop, it seems that it’s not because the request is getting a lot of hits. Since all the calls have the same request payload and the same amount of hits (63) in the response which seem to be the total for that lapse.

Anyway, our workaround for now would be to build most of it through Request Builder and copy the request preview and work with an HTTP client to make the final call and tune the last params that can’t be changed through the app until it’s fixed.

Thank you!