Planetscope subscription insufficient quota

Hi,
looking at your orders it seems that you have done one in EOmw (86 ha) and then four in UK, which cover more or less the same area amounting to 330-360 ha. The total exceesa the 400 ha, which triggered this alert.
That said, you are right to expect you can get new data over same AOI. You should now be able to do so.
Best,

Hi,

Thanks a million for your reply, I could get the subscription started over the same AOI.

I had set the start date to be 1st March 2018, with some added naive filtering options like ''clear_confidence_percent". I am noticing that the new data acquired is only from September 2020, missing data previous to that. Am I doing something wrong here or is there a fix for this?
For your reference:

`
bbox = BBox(bbox=BoundingBox, crs=CRS.UTM_29N) # bbox value = 632978.4394059083,5777654.570358913,635488.3425241278,5784083.919153325
search_date  = datetime(2020, 1, 1)
search_date1  = datetime(2020, 12, 1)

search_time_interval = (search_date, search_date1)

search_iterator = catalog.search(collection=data_collection_byoc, bbox=bbox, time=search_time_interval)

results = list(search_iterator)`

Hi,

Since the productBundle analytic_8b_udm2 is used for your subscription, you will only get 8-band data in this case.

According to Planet’s documentation, 8-band data is acquired via the newer PSB.SD instrument which has the earliest imagery available from mid-March 2020. This explains why there is no data from 2018 to 2019.

To obtain 4-band data acquired from earlier days, you need to make a subscription over the same AOI with the productBundle set to analytic_udm2 or analytic_sr_udm2. With the PlanetScope Hectares under management, this should not increase the cost as long as you’re using the exact same AOI for the two subscriptions.

Hi,
Thank you for your response. I rectified my mistake and got a new subscription running for the 4 band data using ‘analytic_sr_udm2’, but on completion it does not return any deliveries. When I do a native search using the same parameters, as mentioned here, I can see search results (117 results found) and thumbnails of satellite images.
How can I correct this? Here is the input JSON:

{
  "bounds": {
    "geometry": {
      "type": "MultiPolygon",
      "coordinates": [
        [
          [
            [
              -7.04180170946644,
              52.1580384042705
            ],
            [
              -7.04226633102818,
              52.1520757608948
            ],
            [
              -7.03506469682117,
              52.1478941668391
            ],
            [
              -7.0359165030177,
              52.1443320681991
            ],
            [
              -7.03467751218638,
              52.1417766496095
            ],
            [
              -7.03196721974288,
              52.1407699695591
            ],
            [
              -7.03521957067508,
              52.135426821599
            ],
            [
              -7.03498725989421,
              52.1321744706668
            ],
            [
              -7.02290709928889,
              52.1360463170147
            ],
            [
              -7.02631432407501,
              52.1402279110704
            ],
            [
              -7.01818344674451,
              52.1424735819521
            ],
            [
              -7.01864806830625,
              52.14812647762
            ],
            [
              -7.03498725989421,
              52.1585804627592
            ],
            [
              -7.04180170946644,
              52.1580384042705
            ]
          ]
        ],
        [
          [
            [
              -7.05606521111935,
              52.1852312759052
            ],
            [
              -7.05319855565026,
              52.1799149330353
            ],
            [
              -7.04913311698501,
              52.1777258506771
            ],
            [
              -7.04037678755218,
              52.1901827717155
            ],
            [
              -7.04517192033683,
              52.192893064159
            ],
            [
              -7.05132219934323,
              52.1873682372549
            ],
            [
              -7.05299007161615,
              52.1862215750673
            ],
            [
              -7.05606521111935,
              52.1852312759052
            ]
          ]
        ]
      ]
    },
    "properties": {}
  },
  "data": [
    {
      "dataFilter": {
        "timeRange": {
          "from": "2018-03-01T00:00:00Z",
          "to": "2020-03-01T00:00:00Z"
        },
        "maxCloudCoverage": 100,
        "nativeFilter": {
          "type": "AndFilter",
          "config": [
            {
              "type": "RangeFilter",
              "config": {
                "lte": 15
              },
              "field_name": "cloud_percent"
            },
            {
              "type": "RangeFilter",
              "config": {
                "gte": 70
              },
              "field_name": "clear_percent"
            },
            {
              "type": "StringInFilter",
              "config": [
                "standard"
              ],
              "field_name": "quality_category"
            },
            {
              "type": "PermissionFilter",
              "config": [
                "assets:download"
              ]
            }
          ]
        }
      },
      "itemType": "PSScene",
      "productBundle": "analytic_sr_udm2",
      "harmonizeTo": "NONE"
    }
  ],
  "provider": "PLANET"
}

Hi,

This is a result of PlanetScope products are filtered by published time instead of acquired time. We would recommend expanding the time range for your subscription to get the data.