Copy for LLM[View as Markdown](https://docs.planet.com/develop/apis/processing/) # Processing API The Processing API is the most commonly used API to access data collections, as it provides images based on satellite data. Users can request raw satellite data, simple band combinations such as false colour composites, calculations of simple remote sensing indices like NDVI, or more advanced processing such as calculation of Leaf Area Index (LAI). This API abstracts users away from the complexity created by the different satellite constellations scenes and tiles formats. It simply makes the data available over the chosen area of interest and temporal period of interest. Scenes and tiles are automatically stitched together based on defined parameters (AOI, time period, cloud coverage, priority, etc., depending on the data type). ## Deployments | Deployment | API endpoint | Region | | ------------------ | ------------------------------------------------------ | ------------ | | AWS EU (Frankfurt) | | eu-central-1 | | AWS US (Oregon) | | us-west-2 | ## Rate Limiting The Processing API follows the general rate limiting policies described in [Rate Limiting](https://docs.planet.com/develop/rate-limiting.md). ## Data Sources Restrictions [Data fusion](https://docs.planet.com/develop/evalscripts/data-fusion.md) across different regions (for example, Sentinel-2 L1C with Landsat 8-9 L2) is supported only by the Processing API. Other APIs require all sources to be in the same region. ## Examples Clicking the links below will take you to the examples of `processing` API requests: * [Processing API Examples](https://docs.planet.com/develop/apis/processing/examples.md) - ARPS, PlanetScope, SkySat * [Sentinel-2 Examples](https://docs.planet.com/data/public-data/copernicus/sentinel-2/examples.md) * [Landsat 8-9 Examples](https://docs.planet.com/data/public-data/usgs-nasa/landsat-8-9/examples.md) * [DEM Examples](https://docs.planet.com/data/public-data/other-datasets/dem/examples.md) ## CRS Support The list of coordinate reference systems supported by the API is provided below. The coordinate reference system must be set with a URL starting with and it must be set under the field `input.bounds.properties.crs`. For example, you must request in the WGS 84 reference system, defined with the URL : * JSON ``` { "input": { "bounds": { "bbox": [ 12.8114318847656, 41.9663828501025, 12.8732299804687, 42.0046623333086 ], "properties": { "crs": "http://www.opengis.net/def/crs/EPSG/0/4326" } }, "data": [ { "type": "sentinel-2-l1c" } ] }, ... } ``` ### WGS 84 * * ### WGS 84 / Pseudo-Mercator * ### UTM Northern Hemisphere * * * ... * The last two digits of EPSG codes above represent the number of the corresponding UTM zone in the northern hemisphere. For example, use for UTM zone 12N. ### UTM Southern Hemisphere * * * ... * The last two digits of EPSG codes above represent the number of corresponding UTM zone in southern hemisphere. For example, use for UTM zone 12S. ### Others * (RGF93 / Lambert-93) * (ETRS89 / Poland CS92) * (NZGD2000 / New Zealand Transverse Mercator 2000) * (Monte Mario / Italy zone 1) * (Monte Mario / Italy zone 2) * (NAD83 / BC Albers) * (SWEREF99 TM) * (WGS84 / Antarctic Polar Stereographic) * (ETRS89 / LAEA Europe) * (NAD83 / Ontario MNR Lambert) * (LKS94 / Lithuania TM) * (NSIDC Sea Ice Polar Stereographic North) * (ETRS89 / Austria Lambert) * (NAD83 / Yukon Albers) * (NAD83 / NWT Lambert) * (HTRS 96 / TM) * (D96 / TM) * (Pulkovo 1942(58) / Stereo70) * (D48 / GK) * (WGS 84 / Arctic Polar Stereographic) * (MOLDREF99 / Moldova TM) * (S-JTSK / Krovak East North) * (Amersfoort / RD New) * (NAD83 / MTM zone 4)