Introduction
A ULB is divided into certain levels of boundaries by various government administrative authorities in order to carry out there piece of function better. A ULB/City could be divided by different set of delimitation of boundary based on majorly :
Revenue collection
Administration
Locality
All these authorities have designated certain levels of boundary classification for a certain ULB.
Data Table
The below mention table is used to collect data for the types of hierarchy being followed:
Sr. No. | Code* | Boundary Hierarchy Type* | Description |
1 | ADM | Administration | Administration level boundary classified on the basis of administrative functions such as scrutinize certain rules and regulations. |
2 | REV | Revenue | Revenue based classification of a ULB is done on the basis of revenue collection. |
3 | LOC | Locality | Location based classification could be done in order to identify a certain place.
|
Please note: The above mentioned data for the boundary hierarchy is a sample data.
Procedure
Data Definition
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
|---|---|---|---|---|---|
1 | Code | Alphabet | Yes | Code is used to identify a certain classification of type of boundary hierarchy. | |
2 | Boundary Hierarchy Type | Alphanumeric | yes | The meaningful name to define one group of boundaries defined to perform one function. | |
3 | Description | Alphanumeric | - | yes | A brief description about the boundary hierarchy. |
Steps to fill data
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the types of boundaries which are being used in the state in order to carry out various administrative/revenue functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise till the entire data is filled into a template.
Then fill up the hierarchy types and there codes in the respective columns in the template.
A code should be created for the type of boundary being classified.
A brief description of the boundary hierarchy type would be helpful.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
Checklist
The checklist is a set of activities to be performed one the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
Common Checklist
This checklist covers all the activities which are common across the entities.
Sr. No. | Checklist Parameter | Example |
|---|---|---|
1 | Make sure that each and every point in this reference list has been taken care of. |
Entity Specific Checklist
This checklist covers the activities which are specific to the entity.
Sr. No. | Checklist Parameter | Example |
|---|---|---|
1 | Make sure that the hierarchies types should be uniform across all the ULB’s /cities in the state. | - |
2 | Make sure that the code should be unique for every boundary. | One code assigned to the first hierarchy type cannot be used by the other hierarchy type in case if any. |
3 | While consolidating the data for the boundary descriptions, do not leave any boundary hierarchy from the state. | - |
Attachments
The template in order to collect the data for boundary hierarchy is attached below:
2. Below is the attachment for sample data that was collected: