F.A.Q.
The Planet Community Public Ideation Process
Planet is excited to collaborate with our user community in order to continuously improve by taking in your ideas and feedback! The Planet Community P...
17732
Build better products with our product team
Right now, we have to have account IDs of users we want to share collections with. We have some collections that need to share with many users and we have to ask each to provide their account ID, which is often confused with user ID. Also, it looks like we have to share each collection at a time. It'd be convenient to be able to share a collection with email addresses instead of only account IDs. It'd be great to be able to share multiple collections with the same set of users at a time.
It would be beneficial if notifications from the Tasking Dashboard could be sent to multiple users, rather than being limited to the individual who placed the order.
One thing I'd love to see Planet address is the usability of imagery over small Caribbean islands, specifically Saint Vincent and the Grenadines.Two issues come up repeatedly:Cloud cover -The Caribbean sits in a persistently cloudy belt, and for small islands, this is a real problem. Unlike a large landmass where you can often find a usable portion of a scene, when cloud obscures a small island, the whole image is essentially lost. Given how frequently this happens, getting a clean, usable image can be genuinely difficult.Resolution-Small islands have small features. Agricultural plots in SVG are often compact and fragmented across hilly terrain. At 3–5m resolution, it can be hard to distinguish individual crop types or detect meaningful change at the field level.For agricultural monitoring in particular -whether that's tracking crop health or understanding land use both of these limitations compound each other. A clearer image is only useful if you can actually get one.Would love to know if others working in the Caribbean are running into the same thing, and whether Planet has any plans to prioritise tasking or processing improvements for this region.
The global monthly mosaic generation pipeline currently ranks and selects imagery scenes based on data validity metrics derived from the Usable Data Mask (UDM2.1). While cloud pixels are properly identified as invalid and masked, snow pixels are treated as valid surface data.In equatorial regions—such as Singapore, where snow is a physical impossibility—the UDM2.1 classifier systematically misclassifies highly reflective, optically thick cloud patches as snow. Because the mosaic scene-ranking algorithm treats snow as valid, a cloudy scene containing these misclassified "snow" patches can mistakenly outrank a cleaner, less-cloudy alternative scene. This results in corrupted, saturated surface reflectance data permanently propagating into the final monthly composite product with no warning flags for downstream consumers.Proposed SolutionImplement an algorithmic check directly within the mosaic generation and scene-ranking pipeline to account for regional geographic realities without requiring a full retraining of the underlying UDM2.1 core classifier: Latitude-Gated Rule: When processing imagery or generating mosaics for Areas of Interest (AOIs) within the tropical belt, the scene-ranking pipeline must treat any pixel flagged as suspect or cloud-equivalent. Scene Re-ranking: Scenes with high "snow" percentages in these restricted tropical zones should have their quality scores penalized identically to cloud cover. This ensures the pipeline selects a truly clear alternative scene during compositing rather than a cloudy scene mislabeled as snow.
When subscribing to data and routing deliveries directly to the Planet Insights Platform/Image Collections, the system automatically simplifies and truncates geometries to a maximum of 100 vertices. While the Planet’s Subscriptions API explicitly allows up to 1,500 vertices per polygon/multipolygon subscription, any complex agricultural boundaries or multi-field groupings that leverage this higher limit get severely mangled and distorted during platform ingestion. This rendering issue forces customers to revert to creating hundreds of fragmented, individual subscriptions for separate fields just to keep the geometry clean and accurate under 100 points, causing them to rapidly approach active subscription ceilings. Proposed Solution / OptionsRaise the Ingestion Vertex Cap: Increase the ingestion vertex limit from 100 points to align closer with the Subscriptions API limit (up to 1,500 vertices) to natively accommodate complex agricultural plots.
How about offering description of your plans that clearly explains which plans allow downloads.
For Planet Stories: it would be great to add some filters by tags or categories for easier browsing of the time lapses and comparisons. Also great to improve the sharing options for social medias like LinkedIn (in this case, the preview of the post is not showing any thumbnails or any imagery).
On behalf of customer: Would like the ability to view a single band from a BYOC you have to write custom evalscript (as far as I can tell).Would be great to add a tab for single band viewing with some built-in color maps. The screenshot below shows the current options. It would be great if next to "Composite", "Index", "Custom Script", there was another tab called "Single Band". And then, under that tab you could check with band you want view, the scale (ie 0-1, 10-30, etc.) and the cmap (viridis, magma, grayscale, etc. )
on behalf of customer: As a Planet Insights Platform user, if I have a Platform Plan (say Exploration), it's not entirely clear to me how to purchase imagery without clicking around to figure out where it's hiding.Currently, the purchase section locates monitoring plans under "Preselected Packages". As a user, I have no context for what this means, and this is not intuitive.Ideally, should update the name of this tab to something more descriptive. For example: "Planet Imagery Packages" or similar.
Posted on behalf of a customer.When managing tiles into a BYOC collection, it would be useful to have a button for delete all tiles. At the moment you can either delete each tile separately, or delete the collection and create a new one.
Posted on behalf of a customer.Currently, APIs require the geometry to be explicitly provided as a GeoJSON in the request payload. This forces users to maintain their own geometry storage and ingestion systems, even if those same geometries are already managed within the Planet Feature API. This redundancy increases the risk of geometry mismatch and adds unnecessary overhead to the request size. We propose allowing the input.bounds.geometry or a new input.features field to accept a Feature or Collection Reference URI. This would allow the API to fetch the geometry directly from a managed collection.
Just a simple quality of life detail: for users working on analysis of satellite imagery over a time-range, it may be useful to actively display the date of images contained within an order, not just the date the order was placed. In the “my orders” sidebar on the explorer page, between the “Imagery Source” and “Assets” fields, a field named “Capture Date” would be useful to check scene capture times at a glance. Thanks!
GET https://api.planet.com/tasking/v2/pricing/ has a response that contains empty values for "estimated_quota_cost" and "available_quota” Ideally, if we expose the "available_quota" and “estimated_quota_cost” fields it should have a corresponding value.The current workaround to this is to use the underlying accounts page endpoint like this:GET https://api.planet.com/account/v1/tasking/contracts/<PL-number>and the response contains the quota used and quota pending
Our lab is interested in ordering unrectified images (basic_analytic_4b) of an AOI where the AOI is typically < 0.07km^2. Because the cropping tool is only available for rectified images, we end up wasting 10000x the scene quota every month which is a huge blow. Is there a way to download cropped unrectified images or future plans to implement the cropping tools for unrectified images?
It would be nice to have an option in the Subscriptions API to validate or test a request before submitting it. Thanks!
On behalf of a customer:mistakenly went over quota - for example forgot to clip and ended up downloading the scenes.This leads to a problem in showing the real usage.Currently the work around: need to delete the whole package on Planet’s side and then customer needs to download the previous AOIs downloaded.Idea: disable overusage
On behalf of a customer:It is difficult to get clear insights of the areas subscribed to during specific periods of times.This is even more complex when an area is subscribed to by mistake.
Feedback from a customer (conversation to be continued through further discussions):“After evaluating the above-ground biomass product at 30m spatial resolution from Planet to detect forest harvests, we concluded that although it has a high harvest detection rate, it also has a high amount of noise (pixels classified as harvest in areas that were not harvested) (context: we classified pixels as harvest vs non-harvests by setting a threshold based on biomass change). Therefore, we decided to move forward with a different product to accomplish this task. However, we’ll keep evaluating the best products in the market, including Planet’s, on an annual basis to make sure we have the most suitable product for our purpose. I hope to touch base with you again later this year and I’m sure by then you’ll have an even better product!” @david.marvin
On behalf of the customer, Tasking Dashboard does not have a column “coordinates/Lat-long” hence it is difficult to link order/scene-id with coordinates once an order is fulfilled. Having a column coordinates/Lat-long will help the customer to connect/link the scene id/orders while extracting the report from Tasking dashboard, Even when we receive only Lat-long from our customer to get update on order, it becomes really tedious job to identify the order ingested against that order. anyways Tasking dashboard shows Lat-long under geometry in info tab. we request here to add this info in a column at Tasking Dashboard.
Tasking Dashboard does not have a column “coordinates/Lat-long” hence it is difficult to link order/scene-id with coordinates once an order is fulfilled. Having a column of coordinates/Lat-long will help the customer to connect/link the scene id/orders while extracting the report from Tasking dashboard, Tasking dashboard shows Lat-long under geometry in info tab. We request here to add this info in a column at Tasking Dashboard's report so ask is while extracting the report from tasking dashboard, a column/field needs to have coordinates(x, y value) of the order.
When I read about Aparheid Clyde turning off Ukraine’s access to Starlink to favor Russia in a critical moment. I was livid. How can one @%#$#^$ person have that much power and abuse it on a whim or a for $$$ at the expense expense of lives?After learning about Planet Labs via the HBO Documentary “Wlld Wild Space,” I wondered if it would be possible to upgrade Dove sats to have Starlink type sat comm capabilities that would be in the hands of an altruistic company that would not abuse their power and could easily rival and surpass Starlink especially if cost to create was less and could be made available to everyone on earth for low or no cost. Coupled with your image tech having instant access to sat comms would be life saving in natural disasters, conflicts, people stranded in remote locations and the potential to enhance and foster communication to unite people rather than divide. Have no clue if this is at all doable but the idea of marrying your amazing image tech with Sat Comms tech would be awesome.
If for example the bucket region is being specified as per Google cloud's nomenclature (eg: us-west2 as compared to AWS' us-west2), the error message returned is as below: 500 Server Error: Internal Server Error for url: https://services.sentinel-hub.com/api/v1/statistics/batchServer response: "{"status": 500, "reason": "Internal Server Error", "message": "Something went wrong. Incident id: null", "code": "COMMON_EXCEPTION"}"Issue here has to do with Error messaging and how it could more accurately help identify the issue rather than a simple internal server error.
© 2026 Planet Labs PBC. All rights reserved.
| Privacy Policy | California Privacy Notice |California Do Not Sell
Your Privacy Choices | Cookie Notice | Terms of Use | Sitemap
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK