Introduction
This is the next step after collating all the boundary hierarchies which are being used in the state. In a hierarchy there are certain types of boundary classification and in all the levels there will be a mapping which we could define as a parent child mapping in order to link certain levels of the classification.
For example a hierarchy could be:
Administration Hierarchy: City/ULB → Zone → Ward → Locality
In the above mentioned hierarchy, a City/ULB is being divided into different into zones followed by zones into wards and at the end wards into locality.
Data Table
Data has to be collected for every boundary hierarchy type and boundary type with a mapping between the boundary code and its parent boundary code. Following is the table which is to be used across all the hierarchy types.
Sr. No. | Boundary Code* | Boundary Name* (In English) | Boundary Name* ( In Local Language) | Parent Boundary Code* | Boundary Type* | Hierarchy Type Code* |
1 | W1 | Ward no.1 | वार्ड नंबर 1 | Z1 | Ward | ADM |
2 | W2 | Ward no.2 | वार्ड नंबर 2 | Z1 | Ward | ADM |
3 | W3 | Ward no.3 | वार्ड नंबर 3 | Z2 | Ward | ADM |
4 | W4 | Ward no.4 | वार्ड नंबर 4 | Z3 | Ward | ADM |
Note: Data given in the table is a sample data.
Procedure
Data Definition
Following is the definition of the data columns which are being used in the template:
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
|---|---|---|---|---|---|
1 | Boundary Code | Alphanumeric | 64 | Yes | This is a code for the sub classification for a particular boundary |
2 | Boundary Name (In English) | Text | 256 | Yes | The name of the boundary that is being defined in English language |
3 | Boundary Name (In Local Language) | Text | 256 | Yes | The name of the boundary that is being defined in the local language of the state e.g. Telugu, Hindi etc. |
4 | Parent Boundary Code | Alphanumeric | 64 | Yes | This is the boundary code of the parent which identifies to which parent the child belongs to. |
5 | Boundary Type | Text | 256 | Yes | The name of the boundary type i.e. Ward, Zone etc. |
6 | Hierarchy Type Code | Alphanumeric | 64 | Yes | The code of the boundary hierarchy type for which this particular boundary is defined. |
Steps to fill data
Following are the steps which should be used to fill the template:
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.
After Identifying all the boundary hierarchy, get the sub classification of all the hierarchies.
Figure out the codes for all the sub classification for a particular city/ULB.
Start filling the template from the top of the hierarchy in a drill down approach.
A parent child mapping code has to be created for every boundary level except for the top level.
Follow the steps till you reach the last sub classification.
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. | There could be infinity hierarchies, but every hierarchy must have a proper sub classification in a similar fashion. | One Hierarchy has Zone → Area → Locality Second Hierarchy has State → City → Ward → Mohalla → Location |
2. | Every boundary level classification should have one separate data template each. | - |
3. | Do not leave any boundary code without a parent boundary code. | - |
Attachments
Configurable Data Template - Boundary Data
2. Configurable Sample Data - Boundary Data