...
Following is the definition of the data columns which are being used in the template:
...
Sr. No. | Column Name | Data Type | Data Size | Mandatory | Description |
|---|---|---|---|---|---|
1 | Boundary Code | Alphanueric | Yes | This is a code for the sub classification for a particular boundary |
...
2 | Boundary Name(English) |
...
Alphanueric | Yes | The name of the boundary that is being defined in English language |
...
3 | Boundary Name(Local Language) |
...
Alphanueric | No | The name of the boundary that is being defined in the local language of the state |
...
4 | Parent Boundary Code |
...
Alphanueric | Yes | This is the boundary code of the parent which identifies to which parent the child belongs |
...
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.
For example:
There is a state S divided into cities/ULB’s with the city codes as C1, C2, C3,… . And a city is divided into Zones with zone code as Z1, Z2, Z3, the following could be a mapping between these 2 entities:
...
And further the classification could be drilled down to Localities/Mohalla’s etc depending upon the state’s/clients requirement.
...
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 | All the boundary codes have to be alphanumeric i.e start with the first letter of the sub classification and rest could be followed by numbers. | U1 |
2 | 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 |
3 | Every boundary level classification should have one template each. | - |
4 | All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed. | *Code |
5 | All the boundary codes weather parent or child have to be unique across the data for a single ULB |
...
No code can repeat | ||
6 | Do not leave any hierarchy. | - |
7 | Do not leave any boundary code without a parent boundary code. | - |
Attachments
Following is the attached template for the collection of boundary data. The state is free to increase/decrease the boundary sub classification levels according to there requirements. :
| View file | ||
|---|---|---|
|
Below is the attached sample data file for admin level hierarchy boundary data:
| View file | ||
|---|---|---|
|