> 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/nor/api-dokumentasjon/geo-endepunkter-for-tilgang-til-romlige-data/wms-hent-rasterbilder-av-romlige-datalag/11.-topografikart-hoyde-i-absolutte-tall.md).

# 11. Topografikart: høyde i absolutte tall

TopographyMap inkluderer følgende modeller: `digitale høyde, hillshade, helling, eksponering/aspekt, relieffposisjon, ruhet, rugositet`, og deres kombinasjon. Fremstillingen er tilgjengelig på åkernivå nøyaktig (ikke pixelerert) og beskjært etter grensen. Kvaliteten på topografien avhenger av åkerens beliggenhet og det beste tilgjengelige datasettet (USA, GB, EU og AU er dekket med LIDAR). TopographyMap kan bygges fra maskindata som høstetthet/jordsensorer/tilført-data hvis de inneholder høydeattributter. 

Åkerrelaterte topografilag ligger i `feltet` -> `topographyMaps` -> `geoMaps` attributtet. `geoKart` inneholder fullstendige detaljer om tilgang `url`, fargekoder, klasser og lagnavn.

<figure><img src="https://4236156289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FkBBhURFR90kOC9tlXero%2Fimage.png?alt=media&amp;token=caa9d402-aee7-47e8-b5eb-e36085259656" alt="" width="563"><figcaption><p>LIDAR-høyde</p></figcaption></figure>

<figure><img src="https://4236156289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2Fe01cIvD7QPwzIBpAkLM6%2Fimage.png?alt=media&amp;token=40be0b28-6fab-477d-ab2f-4d8d2491f637" alt="" width="563"><figcaption><p>LIDAR-helling</p></figcaption></figure>

<figure><img src="https://4236156289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2Fm2MjuJAUohqKPFXNl4YJ%2Fimage.png?alt=media&amp;token=50130bed-164a-4af3-a451-2b9766af0d6f" alt="" width="563"><figcaption><p>LIDAR-relieffposisjon</p></figcaption></figure>

Forespørselens format er [https://api.geopard.tech/geo/map/reflect?TRANSPARENT=true\&BBOX=\<minX,minY,maxX,maxY>\&LAYERS=elevation\_cropped,field\_view\&STYLES=dem\_elevation,crop\_boundary\&SRS=EPSG%3A900913\&WIDTH=512\&env=ve1:160.4%3Bve2:163.15%3Bve3:165.9%3Bve4:168.65%3Bve5:171.4\&VIEWPARAMS=uuid:\<field\_uuid>\&CQL\_FILTER=uuid=%27\<topography\_map\_uuid>%27%3Buuid=%27\<field\_uuid>%27\&geopardApiKey=\<geopard\_api\_key>](https://api.geopard.tech/geo/map/reflect?TRANSPARENT=true\&BBOX=). Hvor inndataattributtene er:

1. `BBOX=<minX,minY,maxX,maxY>` inneholder avgrensningsboksen (url-enkodet) for "Field" i EPSG:3857-projeksjon;
2. `STYLES=dem_elevation,crop_boundary` inneholder stilen til "TopographyMap"-entiteten som første attributt, de støttede verdiene er:

`dem_aspect`

`dem_elevation`&#x20;

`dem_hillshade`

`dem_roughness`

`dem_slope`&#x20;

`dem _tpi`

`dem_tri`

3. `WIDTH=512` reflekterer utdata-bildestørrelsen i piksler (det presise tallet er viktig bare hvis det brukes som miniatyrbilde);
4. `env=ve1:160.4%3Bve2:163.15%3Bve3:165.9%3Bve4:168.65%3Bve5:171.4` reflekterer området av høydeverdier for den aktuelle åkeren, detaljene ligger i "TopographyMap" -> "geoMaps" -> "classes" (MERK: %3B er url-enkodet ;-symbol);  &#x20;
5. `VIEWPARAMS=uuid:<field_uuid>` inneholder uuid for "Field";
6. `CQL_FILTER=uuid=%27<topography_map_uuid>%27%3Buuid=%27<field_uuid>%27` inneholder UUID-ene til "Field" og "TopographyMap" (MERK: %27 er url-enkodet ‘-symbol);
7. `geopardApiKey=<geopard_api_key>` er koblet til autorisasjonsalternativet via API-nøkkel.


---

# 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/nor/api-dokumentasjon/geo-endepunkter-for-tilgang-til-romlige-data/wms-hent-rasterbilder-av-romlige-datalag/11.-topografikart-hoyde-i-absolutte-tall.md?ask=<question>&goal=<user_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.