> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/files/raster-and-imagery.md).
# Raster and imagery
Upload GeoTIFFs, drone orthomosaics, DEMs, and other raster files. Learn how Felt handles projections, colors, and No Data values.
Raster data is a grid of pixels, such as aerial and satellite imagery, drone orthomosaics, and elevation models. Upload a GeoTIFF or another [raster format](/upload-anything/files/supported-file-types.md#raster-data) with [Upload Anything](/upload-anything/files.md), and Felt adds it as a raster layer. Export drone orthomosaics and elevation models as GeoTIFFs; a Cloud Optimized GeoTIFF isn't required for uploads.
## Projections
Felt reads a raster's coordinate reference system (CRS) from the file, its ground control points, or a `.prj` file uploaded with it. If none of these provides a CRS, Felt guesses. If a raster lands in the wrong place, assign its CRS in a desktop GIS such as QGIS, export it as a GeoTIFF, and upload it again.
## Colors and No Data values
Felt keeps a raster's color table and No Data values. Colors can look slightly different from the source software, because Felt scales values to 0–255 for display. To change a raster's color ramp or opacity, see [Style raster layers](/styling/style-raster-layers.md).
## Stream large rasters
Stream imagery that's too large to upload or changes often. Add tiles from a URL with [XYZ raster tiles](/upload-anything/urls/xyz-raster-tiles.md), or stream Cloud Optimized GeoTIFFs from your own bucket with [Stream large rasters](/upload-anything/stream-large-rasters.md).
---
# 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://help.felt.com/upload-anything/files/raster-and-imagery.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.
