Boundary Data Specs

Field name
Description
Mandatory
Input
Data type
Minimum length
Maximum length
Validation
Comments
Need data from program/state

Boundary code

This is a code for the sub-classification of a particular boundary. It should be unique across all boundaries defined.

Mandatory

MDMS

String

2

64

Yes

Boundary name* (In English)

The name of the boundary that is being defined in the English language.

Mandatory

MDMS

String

2

256

Yes

Boundary name* (In local language)

The name of the boundary that is being defined in the local language of the state. For example, Portuguese, Hindi, etc.

Mandatory

MDMS

String

2

256

Yes

Parent boundary code*

This is the boundary code of the parent which identifies to which parent the child belongs to.

Mandatory

MDMS

String

2

64

Yes

Boundary type*

The name of the boundary type, that is, ward, zone, etc.

Mandatory

MDMS

String

2

256

Yes

Hierarchy type code*

The code of the boundary hierarchies for which this particular boundary is defined.

Mandatory

MDMS

String

2

64

Yes

Campaign start date

The date when the campaign starts in the respective boundary.

Mandatory

MDMS

Date

Yes

Campaign end date

The date when the campaign is supposed to end in the respective boundary.

Mandatory

MDMS

Date

Yes

Total households

Total households present in the boundary (as per the micro-plan).

Mandatory

MDMS

Numeric

Yes

Targeted households

Total households targeted for the respective boundary (as per the micro-plan).

Mandatory

MDMS

Numeric

Yes

Total individuals

Total individuals present in the boundary (as per the micro-plan).

Mandatory

MDMS

Numeric

Yes

Targeted individuals

Total individuals targeted in the boundary (as per the micro-plan).

Mandatory

MDMS

Numeric

Yes

Bed nets estimated to be delivered

Total bed nets estimated to be delivered in the boundary (as per the micro-plan).

Mandatory

MDMS

Numeric

Yes

Last updated

https://creativecommons.org/licenses/by/4.0/