> 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/bg/dokumentaciya-na-api/pregled-na-zayavkite-km-geopard-api/14.-mutaciya-szdavane-na-field-ili-redaktirane-na-granicata-na-sshestvuvashoto-pole-s-nezadlzhitelni.md). # 14. Мутация: Създаване на „Field“ или редактиране на границата на съществуващото поле (с незадължителни етикети) Създайте "Поле" или редактирайте границата на съществуващото поле. {% hint style="danger" %} "Поле" `geojson` атрибутът трябва да е в проекция WGS84 (EPSG:4326), по-малко от 1040 ак / 420 ха, и да следва [спецификация](https://geojson.org/). Поддържани `geojson` видове са `MultiPolygon` и `Polygon`. {% endhint %} Подробности за употребата: * Атрибут `етикети` е карта с двойки ключ (име на етикет) и стойност (стойност на етикет). * Възможно е свързване на уникалната идентификация на собствена "Ферма" чрез \ атрибута. Атрибутът е по избор. * Атрибути `status` и `statusMessage` маркира резултата от регистрацията. " `"статус"=INVALID` отговор означава, че се изисква разследване на заявката за "Поле". Повече подробности за резултатите са в `statusMessage`. {% code overflow="wrap" lineNumbers="true" %} ```graphql мутация CreateFieldSample { registerField( input: { name: "Mutation Field" farmUuid: "" creationType: GEOJSON externalKey: "" geojson: "{\"type\":\"MultiPolygon\",\"coordinates\":[[[[-113.5393998,51.1831965],[-113.5391578,51.1832762],[-113.5335114,51.1832724],[-113.5328941,51.1832686],[-113.5324221,51.1831927],[-113.5320832,51.1830486],[-113.5317503,51.182821],[-113.5314901,51.1826047],[-113.5312904,51.1824264],[-113.5309696,51.1823013],[-113.5307034,51.1822637],[-113.5303706,51.1823168],[-113.5300317,51.1823889],[-113.5298017,51.1824344],[-113.5294991,51.1824231],[-113.5292026,51.1823586],[-113.5287789,51.1822675],[-113.5284824,51.1821537],[-113.5282827,51.1820285],[-113.5282343,51.1818502],[-113.5281979,51.1816036],[-113.5280998,51.1789079],[-113.5280331,51.1764057],[-113.5281207,51.1762546],[-113.5282577,51.1761516],[-113.5284275,51.1760863],[-113.528674,51.1760657],[-113.5289096,51.1760554],[-113.5373048,51.1760602],[-113.5375787,51.1760671],[-113.5377704,51.1761083],[-113.5379348,51.1762388],[-113.5379841,51.1764071],[-113.5379567,51.1769634],[-113.5379512,51.1770527],[-113.5393097,51.1770767],[-113.5394631,51.1771248],[-113.5395453,51.1772244],[-113.5395508,51.1773618],[-113.5395398,51.1797725],[-113.5395452,51.1826365],[-113.539539,51.1829293],[-113.5394999,51.1830779],[-113.5393998,51.1831965]]]]}" labels: "{\"label1\":\"value1\",\"label2\":\"value2\"}" } ) { uuid farmUuid name boundaryUrl status statusMessage creationType labels { name value } externalKey } } ``` {% endcode %} За да **Редактирате** съществуващото "Поле", добавете `uuid` атрибута към заявката. Разликата е в `uuid` атрибута, който определя "Полето" за промяна на границата. {% code overflow="wrap" lineNumbers="true" %} ```graphql мутация CreateFieldSample { registerField( input: { uuid: "" name: "Field_name" farmUuid: "" creationType: GEOJSON geojson: "{\"type\":\"MultiPolygon\",\"coordinates\":[[[[-113.5393998,51.1831965],[-113.5391578,51.1832762],[-113.5335114,51.1832724],[-113.5328941,51.1832686],[-113.5324221,51.1831927],[-113.5320832,51.1830486],[-113.5317503,51.182821],[-113.5314901,51.1826047],[-113.5312904,51.1824264],[-113.5309696,51.1823013],[-113.5307034,51.1822637],[-113.5303706,51.1823168],[-113.5300317,51.1823889],[-113.5298017,51.1824344],[-113.5294991,51.1824231],[-113.5292026,51.1823586],[-113.5287789,51.1822675],[-113.5284824,51.1821537],[-113.5282827,51.1820285],[-113.5282343,51.1818502],[-113.5281979,51.1816036],[-113.5280998,51.1789079],[-113.5280331,51.1764057],[-113.5281207,51.1762546],[-113.5282577,51.1761516],[-113.5284275,51.1760863],[-113.528674,51.1760657],[-113.5289096,51.1760554],[-113.5373048,51.1760602],[-113.5375787,51.1760671],[-113.5377704,51.1761083],[-113.5379348,51.1762388],[-113.5379841,51.1764071],[-113.5379567,51.1769634],[-113.5379512,51.1770527],[-113.5393097,51.1770767],[-113.5394631,51.1771248],[-113.5395453,51.1772244],[-113.5395508,51.1773618],[-113.5395398,51.1797725],[-113.5395452,51.1826365],[-113.539539,51.1829293],[-113.5394999,51.1830779],[-113.5393998,51.1831965]]]]}" } ) { uuid farmUuid name boundaryUrl status statusMessage creationType } } ``` {% endcode %} --- # 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/bg/dokumentaciya-na-api/pregled-na-zayavkite-km-geopard-api/14.-mutaciya-szdavane-na-field-ili-redaktirane-na-granicata-na-sshestvuvashoto-pole-s-nezadlzhitelni.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.