> 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/complaints-management/deploy/setup/production-setup/deploy-complaints-management/unified-approach-not-for-publish/4.-upload-boundary-information.md).
# 4. Upload Boundary Information
{% hint style="info" %}
**Note:** This boundary data is seeded at the city level. Please authenticate again using city-level credentials before attempting to seed the data.
{% endhint %}
#### 4.1 What are Boundaries?
Boundaries are the geographic divisions of your city:
* City → Zone → Ward → Block → Locality
#### 4.2 Select Your Tenant
Step 1: Find the boundary section in the notebook
Step 2: Enter your tenant code (e.g., pg.citya)
#### 4.3 Create Boundary Hierarchy
If this is a new setup, you need to define the hierarchy levels.
Option A: Create New Hierarchy
Step 1: Select "Create New Hierarchy"
Step 2: Enter hierarchy levels:
| Level | Boundary Type |
|---|
| Level 1 | City |
| Level 2 | Zone |
| Level 3 | Ward |
| Level 4 | Block |
Step 3: Run the cell
#### Option B: Use Existing Hierarchy (Recommended if already configured)
Use this option if a boundary hierarchy is already available for the tenant.
Steps:
1. Select “Use Existing Hierarchy”.
2. Click “Search Hierarchies”.
3. Choose the required hierarchy from the dropdown.
4. Click “Generate Template”.
Note: Ensure the correct tenant code is entered before searching for existing hierarchies.
#### 4.4 Generate Boundary Template
Step 1: Click "Generate Template"
Step 2: Wait for generation (30-60 seconds)
Step 3: Download the template when ready
#### 4.5 Fill the Boundary Template
Open the downloaded Excel file.
Fill in boundary data:
| Code | Name | Parent Code |
|---|
| PG_CITYA | City A | (leave empty) |
| PG_CITYA_Z1 | Zone 1 | PG_CITYA |
| PG_CITYA_Z1_W1 | Ward 1 | PG_CITYA_Z1 |
| PG_CITYA_Z1_W1_B1 | Block 1 | PG_CITYA_Z1_W1 |
Important Rules:
* First level (City) has no parent
* All other levels must have a valid parent code
* Codes must be unique
#### 4.6 Upload and Process
Step 1: Upload the filled template
Step 2: Click "Process Boundaries"
Step 3: Wait for processing (1-5 minutes)
#### 4.7 Check Results
✅ PHASE 2 COMPLETE
Boundaries Created: 45
Processing Time: 2m 15s
Click on check processing status after a while to check the generated boundary Excel
---
# 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/complaints-management/deploy/setup/production-setup/deploy-complaints-management/unified-approach-not-for-publish/4.-upload-boundary-information.md?ask=&goal=
```
`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.