If your output image would be smaller, e.g. If you look at pricing, you will see that the Exploration package is enough for 10 172 PUs, as it gives you 30 000 PU per month. The calculation: 20,34 PU x 500 = ~10 172 PU per 500 requests If parameters for each image are equal as above, we can simply multiply our calculation with 500 and see, that 500 similar requests would use about 10 172 PU in sum. for time series), you would need to create 500 separate processing requests. See the multiplication factors and the calculation below: Parameter Example 1ġ request that outputs an image 2000 x 2000 px large, with 2 bands ordered, 16 bit tiff format and orthorectification applied, would result in 20,34 PUs used. The following are detailed calculation examples for Sentinel-1, exploring three different scenarios, including a simple 1 image request, many small requests, long time ranges and large area processing. See documentation on how processing units are defined and calculated here. This in turn depends on how large your images are in pixels, how many of them you order, how many bands you order, the format used and whether some more complex processing options are enabled. If we only focus on rate limiting, the subscription package you need depends on how many processing units (PU) and requests per minute or month you intend to use. * additional costs and restrictions might applyĮach request is worth a certain amount of processing units. Open collections (Sentinel, Landsat, MODIS, etc.) Sharable private collections (access control) See some typical conversions bet_ween processing units and km 2 Compare plansĬonsumes 3x less processing units than Process API
0 Comments
Leave a Reply. |