> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/api-docs/geo-endpoints-for-spatial-data-access/wms-get-raster-pictures-of-spatial-data-layers/16.-satellite-image-cropped-by-field-boundary.md). # 16. Satellite Image: cropped by Field boundary An accurate (not pixelated) cut of the Satellite Image based on the defined Field boundary is available for various views such as `RGB, NIR, EVI2, LAI, NDVI, GNDVI, IPVI, GCI, SAVI, OSAVI, NDWI, WDRVI, NDMI, MCARI`, etc. Each SatelliteImage contains an `geoMaps` object housing rendering details like `url`, color codes, classes, and name. These details are found within the `field` -> `satelliteImages` -> `geoMaps` attribute. The `url` specifically is used to display maps as a WMS layer. To illustrate, output samples for NIR and WDRVI views have been provided below. ### Near-Infrared (NIR), WDRVI, and WDRVI Contrast ![NIR](https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FBO5IUPWygVgPKpMAsela%2Fimage.png?alt=media\&token=23504b6c-df7c-460e-b1cd-b184fe86c575) ![WDRVI](https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FWWNyxHuZj4eEkSrUPEN1%2Fimage.png?alt=media\&token=8cccb814-3eb8-4b55-b1eb-ff0609091f68) ![WDRVI Contrast](https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2F7f0VDnbb4I5kiw7OdDg5%2Fimage.png?alt=media\&token=1ccffb9a-88b3-431b-9c8d-703cb784a5e6) The request format is [https://api.geopard.tech/geo/map/reflect?TRANSPARENT=true\&VIEWPARAMS=uuid:\\&TIME=2020-07-22T17%3A50%3A22Z\&BBOX=\\&LAYERS=sentinel2\_wdrvi\_and\_field\&SRS=EPSG%3A900913\&WIDTH=512\&geopardApiKey=\](https://api.geopard.tech/geo/map/reflect?TRANSPARENT=true\&VIEWPARAMS=uuid:). ### Explanation of the URL parameters Where the input attributes are: 1. `VIEWPARAMS=uuid:` contains the `uuid` of the "Field"; 2. `TIME=2020-07-22T17%3A50%3A22Z` has the data of the satellite image in the format YYYY-MM-DDThh:mm:ssZ (url encoded) and located in the "FieldSatelliteImagery" entity with `acquisitionDate` attribute; 3. `BBOX=` contains the bounding box (url encoded) of the "Field" in EPSG:3857 projection; 4. `WIDTH=512` reflects the output image size in pixels (the precise number is important only if it is used as a thumbnail); 5. `geopardApiKey=` is coupled to the authorization option via API Key; 6. `LAYERS=sentinel2_wdrvi_and_field` reflects the style, the provider attribute located in the "FieldSatelliteImagery" entity. The available options for Sentinel2 (`S2`) imagery `LAYERS` are: `sentinel2_ndvi_and_field` `sentinel2_evi2_and_field` `sentinel2_rgb_and_field` `sentinel2_gci_and_field` `sentinel2_lai_and_field` `sentinel2_nir_and_field` `sentinel2_osavi_and_field` `Sentinel2_wdrvi_and_field` the available options for Landsat8 (`L8, L9`) imagery `LAYERS` are: `landsat8_ndvi_and_field` `landsat8_evi2_and_field` `landsat8_rgb_and_field` `landsat8_gci_and_field` `landsat8_lai_and_field` `landsat8_nir_and_field` `landsat8_osavi_and_field` `landsat8_wdrvi_and_field` the available options for Landsat4-7 (`L4, L5, L6, L7`) imagery `LAYERS` are: `landsat4-7_ndvi_and_field` `landsat4-7_evi2_and_field` `landsat4-7_rgb_and_field` `Landsat4-7_gci_and_field` `landsat4-7_lai_and_field` `landsat4-7_nir_and_field` `landsat4-7_osavi_and_field` `landsat4-7_wdrvi_and_field`
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.geopard.tech/geopard-tutorials/api-docs/geo-endpoints-for-spatial-data-access/wms-get-raster-pictures-of-spatial-data-layers/16.-satellite-image-cropped-by-field-boundary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.