PRODUCT UPDATES

We have updated your SuperDove Visual product by implementing a new sharpening methodology. This update improves the clarity and focus of our Visual (also known as ortho_visual) imagery to visualize more details and textures.   Read more about the new sharpening method in our knowledge base article New Sharpening Method for Ortho Visual Products. For additional information and support, please contact your Customer Success Manager or submit a support ticket to Planet Support.  

Planet is excited to announce the release of Analysis-Ready PlanetScope version 1.0. This release lays a strong foundation for future enhancements. It provides stable metadata and additional delivery options, like direct access to Sentinel Hub through the Subscriptions API.ContentsChanges since version 0.2.0 and version 0.3.0 Several image quality optimizations and bug fixes Additional resources What’s New in This ReleaseAnalysis-Ready PlanetScope version 0.3.0 addressed issues with cloud mask boundaries, incorporating extensive fixes to ensure that radiometry in masked regions matches that of clear-sky regions. This improvement is one of the most significant changes in the v0.3.0 release. Both releases also greatly improved radiometric consistency in land areas near large bodies of water. The metadata delivered in the STAC item has been updated to include solar azimuth and elevation. QA Band 3, the number of reference calibration scenes, was also removed as it is not considered beneficial to users. Improvements to Image QualityFix radiometry over masked regionsAnalysis-Ready PlanetScope v0.2.0 was the first implementation of removing the cloud masking process, introducing issues. v0.3.0 has addressed these concerns, incorporating extensive fixes to ensure that radiometry in masked regions matches that of clear-sky regions. This improvement is one of the most significant changes in this release.Fix for radiometric harmonization in quadrants with significant water coverageA bug was discovered with radiometric harmonization over tile quadrants containing large amounts of water. This bug caused calibration errors and occasional serious blunders over land. Beginning with Analysis-Ready PlanetScope v0.3.0, average radiometry errors over tile quadrants containing large quantities of water have significantly improved, and the incidence of blunders has dramatically decreased. Additional tweaks to the algorithm improved radiometric harmonization, especially in water-heavy tiles and reduced the appearance of anomalous coloration over water. Topographic correctionsIn prior versions, FORCE validation in regions with significant snow, terrain, and clouds indicated relatively high radiometric uncertainties. Analysis-Ready PlanetScope v0.3.0 introduces corrections for topography. Running this process significantly improves the agreement against day coincident FORCE data over AOIs with significant terrain.More accurate reference digital elevation model As of Analysis-Ready PlanetScope v1.0.0, the algorithm uses the Copernicus DEM for topographic corrections. Transitioning to a more accurate reference should enhance the accuracy of cloud masking and radiometric corrections. Set pixels with sensor issues to NODATAAs of Analysis-Ready PlanetScope v1.0.0, we will set pixels marked as “suspect” in the PlanetScope scene's mask to NODATA (0) to ensure data integrity in the final product. This change addresses previous practices where these pixels were masked but retained a value of 7, leading to inconsistencies. This adjustment may lead to oddly shaped patches of NODATA values in the output.Improved inter-quadrant radiometric and geometric consistencyAnalysis-Ready PlanetScope creates daily composites of PlanetScope imagery. Previously, each quadrant of an Analysis-Ready PlanetScope tile independently selected one of the TOA reflectance scenes acquired over that quadrant as a radiometric and geometric reference for compositing the scenes. Beginning with Analysis-Ready PlanetScope v0.3.0, the algorithm now selects, where possible, the same scene as a reference for each quadrant. This results in a slight improvement in inter-quadrant consistency.Fix a bug that omitted small numbers of pixels at scene boundariesv0.3.0 of Analysis-Ready PlanetScope fixes a bug that caused small numbers of pixels to be lost along scene boundaries while compositing. Increase slope threshold for topographic correction Analysis-Ready PlanetScope v1.0 addressed topographic correction-induced artifacts due to over-correction by increasing the slope threshold for processing from 5 degrees to 10 degrees. This adjustment is expected to reduce the occurrence of artifacts and improve the overall quality of the corrected data.Fix a bug that caused ARPS to miss delivering valid dataWe identified an important issue where missing data in one Analysis-Ready PlanetScope processing chunk prevented the creation of the entire Analysis-Ready PlanetScope tile, which is not ideal for consistent data availability. As of Analysis-Ready PlanetScope v0.3.0, the issue has been addressed, ensuring tiles will be created if data from one or more chunks is present.Remove seam lines between chunks via blendingInter-chunk blending is introduced in Analysis-Ready PlanetScope v0.3.0, aiming to minimize sharp boundaries while addressing the risk of contaminating clear-sky pixels due to differing cloud masks at the chunk borders. The solution maintains cloud mask values during QA tile merging to create an overlap mask that matches the centerline between chunks.Improvements to MetadataRemoved QA band 3Analysis-Ready PlanetScope v1.0: QA band 3 reports the number of calibration reference scenes. In practice, we've rarely, if ever, used it for QA checks, so we removed it from the Analysis-Ready PlanetScope both to avoid confusion from users and to reduce the maintenance burden on ourselves.Include metadata from the QA tif in STAC itemsAnalysis-Ready PlanetScope v1.0: Metadata from the QA TIFF files is now in STAC items. This enables metadata-only access, which allows systems to filter data before download. This feature can enhance efficiency by reducing unnecessary data transfers. Include solar azimuth and elevation in QA tiff metadataAnalysis-Ready PlanetScope v1.0: Average solar azimuth and average solar elevation per scene is now available in the metadata. Values for each key are formatted as comma-separated lists of "key[scene_index]", where the angle is rounded to two decimals. Allow daily deliveries to run through high-latitude blackout periodsAnalysis-Ready PlanetScope v1.0: We addressed a bug for blackout periods where the sun angle might be too low for imaging. We now allow daily deliveries to run through high-latitude blackout periods rather than returning errors. Analysis-Ready PlanetScope will only provide data only when a PlanetScope observation is available.Include color interpretation metadata Analysis-Ready PlanetScope v0.3.0: Include color interpretation metadata in tiff delivery to aid in displaying data in programs such as QGIS.Fix to band central wavelengths reported Analysis-Ready PlanetScope v0.3.0: The central wavelengths of each band were corrected in the data’s STAC items. Consistent NODATA values between cloud mask and scene mask Analysis-Ready PlanetScope v0.3.0: Changes to ensure that the QA layers (cloud mask, scene traceability mask, and number of references) consistently have NODATA values.Additional ResourcesIntro to Analysis Ready PlanetScope (ARPS), Planet University Analysis-Ready PlanetScope documentation Analysis-Ready PlanetScope Technical Specification  PlanetScope Overview   

We’re excited to announce a new feature in the tasking dashboard: Archive Tasking Ordering! With this enhancement, you can now order SkySat imagery from our archive of previously tasked images through the Tasking Dashboard and Tasking API. To get started, simply open the Tasking Dashboard and the user interface will automatically suggest an option to order Archive tasks your requested geometry. If you are using the APIs, we’ve included an example in the documentation to help you integrate this new functionality into your workflows: Planet Tasking - Archive Order Creation. We look forward to seeing how archive tasking enhances your experience!

Multi-Factor Authentication (MFA)Planet is excited to announce multi-factor authentication (MFA) support for web logins.What’s New?MFA is a security feature that requires more than one type of user validation (For example, username/password, one-time password, and SMS notifications). This feature protects accounts from bad actors, even if they've acquired the username and password.Currently, Planet MFA protects web logins to your Planet Account using the one-time password authentication factor. Adding additional factors and expanding MFA to API access is not included in this release but in consideration for future enhancements. Additional ResourcesCheck out this article to learn how to enable multi-factor authentication Enabling or Disabling Multi-Factor Authentication for your Planet account. 

Reserve Quota for Planetary VariablesPlanet is excited to share some improvements we’ve made to make it easier to access and deliver Planetary Variables from the Planet Insights Platform.What’s New?We are introducing several key enhancements to streamline your workflow: You no longer need to reach out to your Customer Success Manager or Technical Support to reserve quota for your areas of interest in Features Manager. You can reserve quota directly using the Features Manager app or the Quota API. You can request data via the Subscriptions API immediately after reserving quota for your areas of interest. You no longer need to contact your Customer Success Manager or Technical Support to know when data has been created for your areas of interest. Your Subscriptions API request will show a pending status while data is being prepared. How Does It Work?Follow these steps to enable access to Planetary Variables in your areas of interest by reserving quota, and to deliver your data via the Subscriptions API. These steps can be fully automated using Planet APIs.Log in to Features Manager at Planet.com/features and upload your areas of interest to a Feature Collection. You can also upload using the Features API. After you save your Areas of Interest (AOI) open the Feature Collection that contains the AOI you would like to reserve quota for. Next to Search by feature name, click Reserve Quota and the Manage Quota panel opens. Select the data product from the Manage Quota panel you want to reserve quota for. For example, Land Surface Temperature 100 m. Optionally, you can review the Features AOI and then click Reserve Quota. After quota is reserved for your Features AOI, request to deliver Planetary Variables data from the Subscriptions API using a GeoJSON or a Feature Reference ID (recommended). After you request Planetary Variables data using the Subscriptions API, your data may need to be created first. You can check the status of your delivery. A pending status may indicate that your data is being created for your AOI. Note: Steps 3 through 5 can also be automated using the Quota API.Additional ResourcesPlease explore the following documentation for further details:Features Manager documentation Features API documentation Quota API documentation Subscriptions API documentation 

Sentinel Hub Batch Processing Version 2Planet is excited to announce the latest enhancement to our data processing capabilities: Sentinel Hub Batch Processing V2.The Sentinel Hub Batch Processing (Batch API) enables you to request and process data over large areas and longer time periods—scaling your analysis while saving on time and Processing Units (PUs). With Sentinel Hub Batch Processing, you can: Automate the processing of large datasets Schedule batch jobs for efficient resource use Track and manage batch processing tasks through an intuitive dashboard  Additional ResourcesPlease take a look at the following Sentinel Hub Batch Processing capabilities resources for more information.Webinar: Batch Processing API Scale-up your eo-learn workflow using Batch Processing API blog post to learn how it can help you scale your processing. What’s New?The key new feature of Batch API V2 is that you can specify your tiling grid (including “sparse” tiling grids) to focus only on your area of interest, saving you time and processing units. This new version also brings many smaller improvements, such as finer S3 access management, detailed execution reports, standardized BYOC ingestion, and more! You can find more information about the changes in our BatchV2 API documentation and this Webinar: Scaling Data Access with Batch Processing V2. Some examples of custom tiling grids: legal boundaries over Germany with a sparse version for testing/training, and a combination of 2 UTM regions over Austria.What About Sentinel Hub Batch Processing V1?Batch Processing V1 is now entering maintenance mode and will be sunsetted on September 17, 2025. Please take action as early as possible to ensure that your integration is migrated to the V2 of the service. To facilitate your transition, please use the following resources:The migration documentation The BatchV2 API Demo sample notebook The last sentinelhub-py version  

Planet Hosted Data ExpirationPlanet-hosted data in Planet Explorer reaches the end of life on January 31st, 2025. After that date, you can no longer perform the following data options.Place orders in hosted data folders Apply data visualizations to hosted data in Planet Explorer  Stream hosted data from Planet Explorer using tile service links Sentinel Hub MigrationPlanet encourages users of hosted data to migrate their workflows over to Sentinel Hub by selecting to deliver to an image collection in Sentinel Hub instead of hosted data in the Explorer order modal.Sentinel Hub provides the following capabilities that are similar to hosted data.Organize and share data in Image Collections Apply multispectral visualizations in EO Browser Create and manage tile streaming links using the Sentinel Hub Configuration Utility As end-of-life approaches for hosted data, Planet will follow up with users and provide more information about migrating existing hosted data to Sentinel Hub. If you do not have Sentinel Hub and are interested in using it, Planet offers a Sentinel Hub 6 Month Access for Planet Customers. Sign up todayUSG Customers For USG Customers, there are no planned changes if you access Planet data through your ongoing USG workflows. If you physically host data with Planet, your customer success team is available to discuss your needs, requirements, and future changes to your workflow.Additional Resources Please take a look at the Planet Explorer Overview for more information.Refer to the following support resources: Planet Support FAQSentinel Hub FAQ

Deliver Imagery from Planet Explorer to Sentinel Hub  Planet Explorer now supports delivery to Sentinel Hub imagery collections at image checkout. Use the Sentinel Hub option to deliver images. The following requirements allow you to deliver to Sentinel Hub from the Explorer Orders window.You must have linked your user accounts. See Linking Planet User to Sentinel Hub User. Optional: You can provide a collection ID to deliver to an existing SH collection. You can find your collections from the SH Collections Dashboard. If you don’t have an existing collection, click Continue. Your order creates a new collection for you.  Complete the order imagery steps.After your data is delivered to a collection, use the imagery analysis and visualization tools in the EO Browser or the Python SDK to create insights from your data. Accessing Data in the EO BrowserComplete the following steps to access PlanetScope data in the EO Browser.Access the Configuration Utility to set up the data visualization options. Click New Configuration and name your configuration. Create a configuration based on one of the template instances and scroll down to My PlanetScope Data - PSScene.  Specify a collection. You can search by name or ID. Click Create Configuration. The following page displays the different layers created. Options include true color, NDVI, and false color. If you select a template instance, other options will be displayed. Select Open in EO Browser from the saved configuration in the bottom left Service Endpoints section. The EO Browser opens, and you can visualize and perform light spectral analysis using your planet data.To learn more about creating custom configuration instances, refer to the Dashboard application help. Viewing Data in the EO BrowserNavigate to the spatial extent of your data on the map and set the time of interest range to encompass the date your imagery was captured. In the left panel, select the configuration as the data source and click search to find imagery that matches this criteria. From the search results, click Visualize to see your data. You can switch between different layers to visualize with different spectral analyses or band combinations. You can change the date to explore more imagery you deliver to the same collection.Additional Resources Please take a look at the Planet Explorer Overview for more information.Refer to the following frequently asked questions in our support resources: Planet Support FAQSentinel Hub FAQ 

  Cloud Forecast Data VisibilityPlanet now provides an updated cloud forecast time, enhancing your visibility of the latest cloud data on the Tasking Dashboard.Order entry: When you select the Assure window or in the order summary, hover on the cloud tag to view information about the last cloud update. Non-fulfilled Assure order: The Order detail now provides the scheduled time, chance of cloud, information when the cloud data was last updated, and estimated off-nadir. Fulfilled: After a successful collection, the order detail displays the collected data, the cloud cover over AOI at collection with the previously estimated cloud forecast value, and the off-nadir angle at collection with the estimated off-nadir value. 

Planet Labs is performing engineering maintenance on the systems used for user authentication, which will result in user-visible changes to the platform. These changes will be deployed between early July and the end of August. User credentials (API keys and passwords) will continue to work without disruption. Important! Most of these changes are not expected to require user-facing downtime, but a brief outage in the functionality that links Planet and Sentinel Hub accounts will be required.User-visible ChangesThe user-visible changes include the following: User authentication services will be migrating from account.planet.com to login.planet.com Deep links into account.planet.com will not be maintained.  Please bookmark www.planet.com as the platform homepage and use the login link on this page. The format of the login prompts will be changing. The format of authentication emails (password reset, etc.) will change. Users who have not logged in within the last several years must perform a “forgotten password” password reset. The user must opt into this from the login screen, which is not automatic.Additionally, new user account security features will be enabled to protect accounts from brute-force attacks.What to ExpectUsers may experience additional authentication prompts during this maintenance period as systems gradually migrate on the back end. Depending on the user’s activity and status vis-a-vis the underlying platform maintenance work, users may experience new and old authentication services. This is to be expected and does not indicate a problem with the service.Thank you for your patience as we perform this system maintenance. These changes have prepared our internals better to serve future security needs, including enhanced user account attack detection/protection features, end-user multi-factor authentication, OAuth2 authentication for API access, and enterprise user federation. Note: None of these features are part of this migration, but this migration prepares engineering infrastructure for future work in these areas.

Features Manager is a new application that helps you upload and manage areas of Interest (AOIs) on the Planet Insights Platform. The application is built on Planet APIs, including the Features API. Features Manager is designed to help you manage your AOIs on the Planet Insights Platform so that you can use them as references in downstream applications, such as requesting data through the Orders and Subscription APIs. As a Planetary Variable user, Features Manager also provides a special view into quota management, enabling you to determine how much quota you have used for your AOIs. Features Manager CapabilitiesUpload and save AOI Features  Validate and simplify AOI Features  Organize Features in Feature Collections and add metadata  Share Feature Collections with your organization Copy Feature Reference IDs to use in downstream APIs like Subscriptions  For Planetary Variable customers, preview PV quota for your AOIFeatures Manager & Planetary Variables Quota To access Planetary Variables for your AOIs, upload your AOIs using Features Manager or Features API. Once uploaded, ask your Planet support manager to “reserve” the PV quota for your Feature Collection. Upload your AOIs using Features Manager or API.  To share Feature Collection(s) with your support manager, click the More menu on your collection and click copy link. Email your support manager a link to your Feature Collection and specify which Planetary Variable you want to access for those AOIs.Once your quota is reserved and data is created in those areas, your support manager will let you know that you can start requesting PV data through the Subscriptions API. Additional Resources Please take a look at the Features Documentation for more about this release. 

 What’s NewPlanet introduces support for delivery from the Orders API to a Sentinel Hub collection. You can now order PlanetScope and SkySat Imagery and send it to Sentinel Hub for further analysis. Interested in learning more about how to configure your delivery options? Get the details in the Orders Delivery documentation Read about Planet APIs at Get Started with Planet APIs Find a collection of guides and tutorials on Planet University

Planet is excited to announce the implementation of an advanced security feature for your collections. This enhancement guarantees that your data remains safe and secure.What’s New Default ProtectionFrom now on, all newly created collections will be protected by default. Your new collections are automatically limited only to your user account, even if you share your collection ID with others.Note: The existing collections and configurations with these collections remain the same.Protect Your Existing CollectionsNow, you can manage how your existing collections are shared! To protect them, open your Dashboard and click My Collections. Click the icon with an unlocked lock to enable this feature. Note: Once you enable this feature, any users with whom you have previously shared your collection ID will lose access.Selective SharingPlanet is introducing the option to share your protected collections with specific users. By specifying a list of users with their account IDs, you have complete control over who can access your collections.Important ReminderOnce you have protected a collection, it cannot be changed back to unprotected by you. Only Sentinel Hub Support has the authority to change this setting. If you ever want to make a protected collection unprotected again, contact support@planet.com, and we’ll be happy to assist you. Need Help or More Information?Check out our Protected Collections documentation for more details about our advanced security features.If you have any questions or need assistance with this new feature, please do not hesitate to contact our support team at support@planet.com.

On July 31, 2024, public data will no longer be available through the Planet API, Planet Explorer, or Planet Integrations. This change allows Planet to improve your experience by streamlining access to public data through single-source Sentinel Hub services.If you do not access Landsat8, Sentinel-2L1C, Sentinel1, and MODIS data through Planet API, Planet Explorer, or Planet Integrations, you do not need to make any changes to your account. There is no impact on your workflows or ability to access orthorectified imagery through PSScene, SkySat, and RapidEye.  If you access Landsat8, Sentinel-2L1C, Sentinel1, and MODIS data through Planet API, Planet Explorer, or Planet Integrations, please register for Sentinel Hub 6 Month Access for Planet Customers to access this data. More InformationRefer to our Public Dataset Deprecation and Migration Plan for additional information.Please get in touch with your Customer Success Manager or submit a support ticket to Planet Support.  

If you disagree with the quality evaluation for a tasking order, the Tasking Dashboard allows you to request an additional review (according to the respective Flexible or Assured Tasking Terms of Service) of the capture within two weeks from the capture publication date. Considerations for Additional ReviewApplied to Input Area - The rules are applied to the user’s input area, which could be as small as 25 square kilometers or as large as the full collection. Less than your contracted Cloud Cover Threshold - Collections must be less than or equal to (<=) the contracted cloud cover threshold. This does not include haze and shadows. Exceptions include Assured tasks. Scene Alignment - We do not guarantee scene alignment where we cannot create tie points for rectification. For example, significant clouds or the scene has <= 10% land intersection. We should be able to align where haze is present. UDM2.1 as a Starting Point - If you believe UDM2.1 has mislabeled your collection, please dispute and we will review it. For example, if UDM2.1 mislabels clouds as haze.Planet might re-task or re-process the image if our quality commitments are not met. We will assess if your collection is a good candidate for reprocessing. Other outcomes include declining the request, quota adjustment, or refund.For More InformationPlease review our Terms of Service Enforcement Rules Refer to the Flexible and Assured Tasking Capture Review Terms of Service Enforcement knowledge base article

This product release announces Crop Biomass version 4In this new version, Planet improved the spatial distribution of the data by adding PlanetScope as a source of optical data, and by increasing the contribution of spatial information from Sentinel-1, especially during periods of persistent cloud cover.Also, integrating our pipeline with Sentinel Hub enables instantaneous on-demand data delivery. In other words, we are removing all the steps involved in data activation, simplifying the provisioning, and significantly reducing the time required to deliver data in new areas. Crop Biomass FeaturesCloud-free vegetation biomass estimation at a 10-meter resolution daily Analysis-ready data An archive dating back to January 1, 2019Interested in learning more about the Crop Biomass Planetary Variable?Crop Biomass in Subscriptions API Planetary Variables in EO Browser  

This product release announces the Forest Carbon Diligence version 1.1New FeaturesThis Forest Carbon Diligence version update improves year-over-year consistency for the Canopy Height and Aboveground Carbon Density products in undisturbed landscapes and fixes two known dataset bugs. The underlying models for each product remain unchanged, and these updates solely implement post-processing changes.For more information, refer to the following documentation: Planet Forest Carbon Diligence Technical Specification Planet Forest Carbon Diligence Release Notes Forest Carbon Diligence Workflows

This product release announces the Forest Carbon Diligence product validation and intercomparison report The Forest Carbon Diligence Validation and Intercomparison report provides a multi-scale, multi-method assessment of the quality of Planet’s Forest Carbon Diligence data products, with an emphasis on jurisdictional and voluntary carbon monitoring applications, using a combination of intercomparison and validation approaches.Refer to the Validation and Intercomparison report for more information. 

Planet is announcing an important change in our communication strategy regarding product releases. We have decided to deprecate the practice of announcing product updates in the Planet Changelog. Instead, we will be moving our product release announcements to the Planet Community site.Effective immediately, all product release announcements will be posted on our community site at Planet Product Announcements.This change enables us to streamline our communication process and also provide a central hub for product updates. By consolidating all release information on the Planet Community site, you will have access to the most up-to-date information and can collaborate and discuss among our community members.We look forward to your feedback in the Planet Community forum!

Planet introduces support for delivery from the Subscriptions API to the Sentinel Hub collection. You can now subscribe to Planetary Variables and Imagery and send it to Sentinel Hub for further analysis. Interested in learning more about how to configure your delivery options? Get the details in the Subscriptions Delivery documentation. Read about Planet APIs at Get Started with Planet APIs.Find a collection of guides and tutorials on Planet University.

  The Planet Field Boundaries new data set is now available through the Subscriptions API. Field Boundaries provide critical infrastructure for agriculture solutions, including regional crop monitoring and yield estimation over broad areas, serving customers in civil government, commercial agriculture, finance, and consumer packaged goods industries. Field Boundaries automatically trace the boundaries of agricultural parcels for a specified area and Time of Interest (TOI). To do this, the Planet proprietary algorithm estimates a parcel’s extent and perimeter from a time series of satellite images. This dataset can be generated globally dating back to 2018.ImageryThe first version of the Field Boundaries PV uses Sentinel-2 data with 10 m resolution input. Interested in learning more about the Field Boundaries Planetary Variable?Review an example of subscribing to Field Boundaries using the Subscriptions API Get the details in the Field Boundaries Technical Specification Read about Planet APIs at Get Started with Planet APIs Find a collection of guides and tutorials on Planet University

The Planet Mission Operations team recently managed the final operations and re-entry of two of our decommissioned SkySats. As a part of our commitment to responsible space use, bringing these SkySats down from space ensured that they would not pose a risk to other spacecraft or further contribute to space debris.As a reminder, this was a planned re-entry and does not have any notable impact on our high-resolution fleet’s capacity or your tasking abilities, given the Planet team’s continued efforts to innovate and improve the tasking capabilities across the program. We are able to apply learnings from the SkySat fleet as we look forward to launching additional high-resolution Pelican satellites. 

Planet Features API (Beta) Planet recently released its Features API (Beta). The Features API is a great way to improve the efficiency of your data discovery and delivery workflows by enabling you to store your Areas of Interest (AOIs) once and reference them, as needed, across the platform. Planet discovery and delivery APIs that now support saved Feature references include:Orders API  Subscriptions API  Data API The Features API also includes endpoints for validating and simplifying your AOIs so that they meet the Planet geometry rules (such as max 1500 vertex limit) before saving them. After a Feature is saved, it can be accessed as an OGC-compliant Features API.API docs for the Planet Features API can be found in the Planet Features API documentation. Example Features API workflow Note: For more detailed workflow examples, refer the Planet Jupyter Notebook.  To create a Feature Collection make a POST to the Collection endpoint and include a Collection name and description.  POST to https://api.planet.com/features/v0/ogc/my/collections To validate that your Features (AOIs) meet the Planet geometry requirements, make a POST request to the /validate endpoint. The API response provides more details if your Feature does not meet the geometry rules.  POST https://api.planet.com/features/v0/ogc/my/collections/validate To add Features (AOIs) to your Feature Collection, make a POST to the items endpoint. You can include Title, ID, and Description properties.  POST https://api.planet.com/features/v0/ogc/my/collections/:collectionID/items  To share a Feature Collection so that other users in your Organization can find and access the AOI Features, make a POST request to the permission endpoint: POST https://api.planet.com/features/features/v0/ogc/my/collections/:collectionID/permission  After a Feature is saved, you can reference it in the Planet delivery APIs. For example, make a POST request to the Orders API to deliver data where you need it.  POST https://api.planet.com/compute/ops/orders/v2 Feature Reference: A reference (URL, ID) to a specific Feature.Learning ResourcesFor information on working with Planet APIs, see Get Started with Planet APIs.Note: The Planet Features API is currently in Public Beta and future releases may not be backwards compatible. Following the General Availability (GA) release of the API, we will provide support for a duration of six months.FeedbackHave feedback? Please let us know using the Planet Features API Beta Feedback form.

 Planetary Variables and Sentinel HubNew datasets are available in Sentinel Hub! Land Surface Temperature Soil Water Content Crop BiomassForest CarbonPlanetary Variables are now a supported data layer in Sentinel Hub. You can order Planetary Variables with the Sentinel Hub Third Party Data Import API to be delivered to your Sentinel Hub collections to benefit from all the analysis and streaming capabilities of the Sentinel Hub APIs.You can provide an area of interest, time of interest, and specific Planetary Variable and the data that matches the criteria is delivered to a specified Sentinel Hub collection.Refer to Third Party Data Import API documentation for more information.Interested in learning more about Planetary Variables in Sentinel Hub? Check out this recent blog from Matt Ballard, Technical Marketing Manager at Planet, for a deep dive into our Sentinel Hub datasets! 

Planet implemented an improved normalization approach for surface reflectance basemaps that use Sentinel-2 as a normalization target.Why is this important?PlanetScope imagery is collected using a constellation of different satellites—including different satellite generations—that have different relative spectral responses (RSRs). The different RSRs are due to the different sensors, and the variability in PS surface reflectance (SR) data. SR correction for PS data relies on MODIS estimates of the atmospheric optical thickness, which is collected at a different time of day and at a coarser spatial resolution when compared with PS imagery. This leads to significant variability in PS SR data even for images that have the same RSR. For example, same satellite generation and sensor. Therefore, we apply normalization to correct for the variability of SR data leading to more consistent time series.What did we change?We processed the entire Sentinel-2 imagery catalog between 2017 and 2023 using the Framework for Operational Radiometric Correction for Environmental monitoring (FORCE) method then created monthly-cadence, multi-year composites by estimating the 30th percentile for each pixel location using only cloud-free data. How does this improve the product?Sentinel-2 normalized basemaps will have better correlation to FORCE making them more consistent and accurate for time series use.  The improvements were intentionally made to be fully backwards compatible with our current normalization models so existing customer and archive data is still 100% valid and usable.Are there any possible impacts?The new approach works best when there are a high number of observations to build the model. In areas where observations are limited due to clouds or other conditions, the algorithm may produce inaccurate results that manifest as artifacts in the final product. Examples of this are shown in the technical datasheet. If you notice this or any other artifacts please file a ticket and the customer support team will address the issue. This is not expected to be widespread so there is minimal risk of impact.For additional information, refer to the Surface Reflectance Basemaps Technical Datasheet.