# Managing Crop Season Information with Tags (Labels)
By default, GeoPard supports two levels of hierarchy: farm and field. That is often not enough when you manage several farms with dozens of fields or work with multiple clients.
For that purpose, GeoPard includes a flexible label system. You can create as many labels as you need, assign a name to each label, and add as many values as required. A label is a key-value pair, where the key is a hierarchical entity, such as “Client”, “Region”, or “Crop2021”, and the value is one of the available options for that key, such as “John Smith” or “Betty Johnson”.
Labels are created at the account level and are not shared automatically. Once created, you can use labels and their values to search and filter fields. This helps narrow the field list to the ones that need your attention. If you work with colleagues, agree on label names and values in advance to keep the structure clean and consistent.
### **Overview**
1. A label is a key-value pair, where the key is a hierarchical entity, such as “Client”, “Grower”, “Crop2021”, or “Region”, and the value is one of the available options for that key.
2. Every label can be linked to one or many fields directly.
3. A field can contain multiple labels.
4. Labels are linked to the account.
5. You can search and filter fields using labels.
### **Case: Managing fields for several clients**
If you use GeoPard to manage farms or fields for several clients, you can create labels to distinguish fields by client name, as shown in the table below: 
You can configure the mentioned hierarchy in two ways:
1. Manual way: create all labels manually in the interface and assign them using a bulk action. Click **Edit Fields**, select the fields you want to label, click **Add Labels**, then click **Finish Editing** to leave edit mode.
2. Automatic way: upload field boundaries with `.shp` and `.dbf` together. The `.dbf` file contains the attributes with the hierarchy details.
Click **Upload** in the left menu, select the farm where the boundaries will be uploaded, select the .dbf file, and click the **Upload** button.
Wait for the confirmation dialog to see that the boundaries were uploaded successfully:
If the .dbf file contained the labels, you will see them on the Fields view:
To filter the field list, use the labels you created. For example, click the filter and select `Client Name` → `John Smith` to display only the fields for that client:
Keep in mind that you can apply multiple filter criteria based on the labels you created:
### **Case: Season details including crop and year**
You can also use labels for fast access to the fields with the defined crop/variety or with the defined year.
1. Collect the list of used crops: corn, wheat, canola, etc.
2. Create labels manually or automatically (described above, ex. label key: “Crop”, label values: “Wheat”, “Corn”, “Soybean”).
3. Assign labels using bulk operation:
Click the **Edit Fields** button and select the fields, for which you want to assign a label, and then click **Add Labels** button:
You can use the same approach for adding year information:
Then you can apply both labels to search for fields by crop name and year:
### **Case: Field operation details**
You can also use labels for fast access to fields to check planned/executed operations.
1. Define the list of operations.
2. Create labels manually or automatically via upload (ex. label key: “Field Operations”; label values: “TissueSampling”, “SoilSampling”, “Spraying”, “Seeding”, etc.).
3. Add labels for status (ex. label key: “Status”; label values: “Planned”, “In Progress”, “Done”, etc.).
Then you can apply several labels to search for fields based on operation type and status:
A
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/managing-crop-season-information-with-tags-labels.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
