Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

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 but not limited to:

  1. Revenue collection

  2. Administration

  3. 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.

Boundary Hierarchy Type*

Code*

Description

1

Admin 

ADM

Administration level boundary classified on the basis of administrative functions such as scrutinize certain rules and regulations.

2

Revenue

REV

Revenue based classification of a ULB is done on the basis of revenue collection.

3

Locality

LOC

Location based classification could be done in order to identify a certain place.

*Mandatory columns

Please note: The above mentioned data for the boundary hierarchy is a sample data.

Procedure

Data Definition

  1. Boundary Hierarchy Type: The meaningful name to define one group of boundaries defined to perform one function.

  2. Code: Code is used to identify a certain classification of type of boundary hierarchy.

  3. Description : A brief description about the boundary hierarchy.

Steps to fill data

  1. Identify all the types of boundaries which are being used in the state in order to carry out various administrative/revenue functions.

  2. Fill up the hierarchy types and there codes in the respective columns in the template.

  3. A code should be created for the type of boundary being classified, and a brief description would always be helpful.

Validations

  1. Make sure that the hierarchies types should be uniform across all the ULB’s /cities in the state.

  2. All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.

  3. Make sure that the code should be unique for every boundary.

Do’s and Don'ts

  1. While consolidating the data for the boundary descriptions, do not leave any boundary hierarchy from the state.

Attachments

  1. 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:

  • No labels