Ordering and downloading imagery draws down your plan. Some assets and some tools add to what you are charged, and others are free. This article covers which is which.
Which applies to you
Accounts on the current packages are metered in monitoring credits. Accounts bought before that change are metered in download quota, measured in square kilometres, and keep it until they are migrated.
If your plan uses monitoring credits
Credits are drawn by the following actions:
- Ordering imagery — metered on the total area ordered.
- Data activation — charged per input item, with a 24-hour grace period, so working with the same item again inside a day is not charged twice.
- Clip — charged per input item.
- Ordering tools — Band Math, Composite, Harmonization, Reproject, TOAR and Co-register are charged per input item, and Merge per input quad. File Format is not charged.
- Egress — charged per GB downloaded or sent to third-party cloud storage. Data kept in platform data collections incurs no egress charge.
Basic actions — activation, clipping and egress — are not charged on Reserved plans. Current credit rates for each action are published in the platform documentation.
Two things to watch if you are moving from download quota. Top of Atmosphere Correction (TOAR) and delivery to third-party cloud storage never consumed download quota, but they did consume processing units. Under monitoring credits both are charged in the single currency, so they now show up in the same balance as your ordering. Keeping data in platform data collections avoids the egress charge.
If your plan uses download quota (sq km)
Applies to plans bought before Planet moved to monitoring credits.
The Orders API provides tools to perform functions on Planet's infrastructure. Operations may affect the quota charged for a download, but there is no individual charge for each operation used.
Operations that affect quota
- Composite — the area of the input scenes is charged, not the area of the output.
- Coregister — the area of the anchor item and the area of the requested imagery are both charged for each order. Anchor items may be charged multiple times.
- Clip — see the clip section below.
Operations that do not affect quota
- Top of Atmosphere Correction (TOAR)
- Tiling — split a file into a regular set of tiles based on a user-defined tiling system
- Cloud delivery — deliver to Amazon S3, Microsoft Azure or Google Cloud Storage
- Email and webhook notifications
- Order zipping
Clip tool charges
- Starter — no access to the clipping tool, and charged for the full outline of each scene downloaded.
- Preferred — can clip to any size, down to one pixel, but charged a minimum of 100 sq km per intersecting scene.
- Premium — can clip to any size, down to one pixel, and charged a minimum of 0.01 sq km per intersecting scene.
Clipping level is set at the organisation level, by the organisation's administrators or by the Customer Success Manager on the account.
Scene-to-scene overlaps
You are charged for overlapping areas in clipped scenes. When you specify a clip geometry through the Orders API, that geometry is applied to every scene in the order, and any area falling inside it is delivered.
Scenes collected within the same satellite pass are called a strip, and orders often span several scenes from one pass. Each image prepared for download is evaluated individually for quota, so an overlapping area is charged once for each clipped image it appears in.
Assets that do not consume quota
Downloading these returns a quota charge of 0 sq km. This includes UDM2 files downloaded through the Data API, and metadata and browse assets.
analytic_5b_xmlanalytic_8b_xmlanalytic_dn_xmlanalytic_xmlbasic_analytic_4b_rpcbasic_analytic_4b_xmlbasic_analytic_8b_xmlbasic_analytic_dn_rpcbasic_analytic_dn_rpc_nitfbasic_analytic_dn_xmlbasic_analytic_dn_xml_nitfbasic_analytic_rpcbasic_analytic_rpc_nitfbasic_analytic_scibasic_analytic_udmbasic_analytic_udm2basic_analytic_xmlbasic_analytic_xml_nitfbasic_panchromatic_dn_rpcbasic_panchromatic_rpcbasic_panchromatic_udm2basic_udmbasic_udm2browsemetadata_auxmetadata_txtortho_analytic_4b_xmlortho_analytic_8b_xmlortho_analytic_udmortho_analytic_udm2ortho_panchromatic_udmortho_panchromatic_udm2ortho_pansharpened_udmortho_pansharpened_udm2ortho_udm2udmudm2visual_xml
Assets that consume quota
Downloading one of these is charged in square kilometres, for the size of the scene or the clipped area downloaded. When you place an order for an item you are charged per asset for the area.
analyticanalytic_5banalytic_8banalytic_8b_sranalytic_b1analytic_b10analytic_b11analytic_b12analytic_b2analytic_b3analytic_b4analytic_b5analytic_b6analytic_b7analytic_b8analytic_b8aanalytic_b9analytic_bqaanalytic_dnanalytic_msanalytic_sratmcorrectedbasic_analyticbasic_analytic_4bbasic_analytic_8bbasic_analytic_b1basic_analytic_b1_nitfbasic_analytic_b2basic_analytic_b2_nitfbasic_analytic_b3basic_analytic_b3_nitfbasic_analytic_b4basic_analytic_b4_nitfbasic_analytic_b5basic_analytic_b5_nitfbasic_analytic_dnbasic_analytic_dn_nitfbasic_analytic_nitfbasic_l1a_all_framesbasic_l1a_panchromatic_dnbasic_l1a_panchromatic_dn_rpcbasic_panchromaticbasic_panchromatic_dnortho_analyticortho_analytic_4bortho_analytic_4b_srortho_analytic_8bortho_analytic_8b_srortho_analytic_dnortho_analytic_srortho_analytic_vhortho_analytic_vvortho_panchromaticortho_panchromatic_dnortho_pansharpenedortho_visualvisual
The clear coverage endpoint
Using the Data API clear coverage endpoint with mode estimate or UDM2 does not consume download quota. Download quota is consumed only when imagery assets are downloaded.
Comments
Please sign in to leave a comment.