> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/deployment/configuration/master-data-templates/ward-boundary.md).

# Ward Boundary

## Introduction

Wards are the smallest administrative boundaries with the ULBs. A ULB is divided into multiple wards.

## Data Table

| Sr. No. | Ward Code | Ward Name | Ward Name (Odia) |
| ------- | --------- | --------- | ---------------- |
| 1       | W001      | Ward 1    | ୱାର୍ଡ ୧          |
| 2       | W002      | Ward 2    | ୱାର୍ଡ ୨          |
| 3       | W003      | Ward 3    | ୱାର୍ଡ ୩          |
| 4       | W004      | Ward 4    | ୱାର୍ଡ ୪          |
| 5       | W005      | Ward 5    | ୱାର୍ଡ ୫          |
| 6       | W006      | Ward 6    | ୱାର୍ଡ ୬          |
| 7       | W007      | Ward 7    | ୱାର୍ଡ ୭          |
| 8       | W008      | Ward 8    | ୱାର୍ଡ ୮          |
| 9       | W009      | Ward 9    | ୱାର୍ଡ ୯          |
| 10      | W010      | Ward 10   | ୱାର୍ଡ ୧୦         |
| 11      | W011      | Ward 11   | ୱାର୍ଡ ୧୧         |
| 12      | W012      | Ward 12   | ୱାର୍ଡ ୧୨         |
| 13      | W013      | Ward 13   | ୱାର୍ଡ ୧୩         |
| 14      | W014      | Ward 14   | ୱାର୍ଡ ୧୪         |
| 15      | W015      | Ward 15   | ୱାର୍ଡ ୧୫         |
| 16      | W016      | Ward 16   | ୱାର୍ଡ ୧୬         |
| 17      | W017      | Ward 17   | ୱାର୍ଡ ୧୭         |
| 18      | W018      | Ward 18   | ୱାର୍ଡ ୧୮         |
| 19      | W019      | Ward 19   | ୱାର୍ଡ ୧୯         |
| 20      | W020      | Ward 20   | ୱାର୍ଡ ୨୦         |
| 21      | W021      | Ward 21   | ୱାର୍ଡ ୨୧         |
| 22      | W022      | Ward 22   | ୱାର୍ଡ ୨୨         |
| 23      | W023      | Ward 23   | ୱାର୍ଡ ୨୩         |

{% hint style="info" %}
The data given in the table is sample data for reference.
{% endhint %}

## Data Definition

<table><thead><tr><th width="97">Sr. No.</th><th>Column Name</th><th>Data Type</th><th>Data Size</th><th>Is Mandatory?</th><th>Definition/ Description</th></tr></thead><tbody><tr><td>1</td><td>Code</td><td>Alphanumeric</td><td>64</td><td>Yes</td><td>A unique code that identifies the project type.</td></tr><tr><td>2</td><td>Project Type</td><td>Text</td><td>256</td><td>Yes</td><td>Provides the name of the project type </td></tr><tr><td>3</td><td>Project Type (Odiya)</td><td>Text</td><td>256</td><td>No</td><td>Project type name in local language</td></tr><tr><td>4</td><td>Effective From</td><td></td><td></td><td></td><td>Date from which the project is effective</td></tr><tr><td>5</td><td>Effective To</td><td></td><td></td><td></td><td>Date till which the project is effective</td></tr><tr><td>6</td><td>Is Active</td><td></td><td></td><td></td><td>Whether the project is active or not</td></tr></tbody></table>

## Attachments

{% file src="/files/LBKm3kUzIXFBnInzCs7G" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/deployment/configuration/master-data-templates/ward-boundary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.