> 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/ro/documentatie-api/puncte-finale-geo-pentru-acces-la-date-spatiale/wms-obtine-imagini-raster-ale-straturilor-de-date-spatiale/6.-hartazone-schema-de-culori-personalizata.md).

# 6. HartaZone: schemă de culori personalizată

Straturile de date legate de parcela sunt localizate în `câmp` -> `vectorAnalysisMaps` -> `geoMaps` atribut. Acesta are reprezentările origin și miniatură "VectorAnalysisMap". Fiecare `geoHartă` conține detalii complete despre acces `url`, codurile de culoare, clasele și denumirile de vizualizare.

{% hint style="info" %}
Ca prima opțiune, noul schema de culori poate fi aplicată direct prin următorul exemplu `env=c1:%23762a83%3Bc2:%23af8dc3%3Bc3:%23e7d4e8%3Bc4:%23d9f0d3%3Bc5:%237fbf7b` ar trebui bifat, unde `%23` este `#` simbol și `%3b` este `;` simbolul.
{% endhint %}

Ca a doua opțiune, noua culoare poate fi salvată în prealabil prin[ Mutație: Setează scheme de culori personalizate pentru mutația selectată "GeoMaps"](/geopard-tutorials/ro/documentatie-api/prezentare-generala-a-cererilor-api-geopard/39.-mutatie-seteaza-scheme-de-culori-personalizate-pentru-geohartile-selectate.md).

### URL

[https://api.geopard.tech/geo/map?SERVICE=WMS\&VERSION=1.1.1\&REQUEST=GetMap\&FORMAT=image/png\&TRANSPARENT=true\&VIEWPARAMS=uuid:\<vector\_analysis\_map\_uuid>\&LAYERS=zone\_map\_view\&exceptions=application/vnd.ogc.se\_inimage\&SRS=EPSG:3857\&STYLES=zonesmap\_5\&HEIGHT=512\&WIDTH=512\&BBOX=\<field\_bounding\_box\_in\_epsg3857><mark style="color:verde;">\&env=c1:%23762a83%3Bc2:%23af8dc3%3Bc3:%23e7d4e8%3Bc4:%23d9f0d3%3Bc5:%237fbf7b</mark>\&geopardApiKey=\<cheia\_ta\_geopard>](https://api.geopard.tech/geo/map?SERVICE=WMS\&VERSION=1.1.1\&REQUEST=GetMap\&FORMAT=image/png\&TRANSPARENT=true\&VIEWPARAMS=uuid:)

### Vizualizare

<figure><img src="https://lh4.googleusercontent.com/iEa6wne-xyboxYiPKLIAcWzs8bw6MGg9WT5dS6LauWDY1aCtF-DcF0aU_5zDrH7Itx2ZMqHvd_BZPDdv8j0vnSVmrc2SqTXOqA-Hy-jbbfomEqxIR-kV_vZGl5wXL53dEb9k0Zb6ynWO8ntfmofZAA" alt=""><figcaption><p>HartaZonelor cu Schema de Culori Personalizată</p></figcaption></figure>


---

# 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/ro/documentatie-api/puncte-finale-geo-pentru-acces-la-date-spatiale/wms-obtine-imagini-raster-ale-straturilor-de-date-spatiale/6.-hartazone-schema-de-culori-personalizata.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.