MP-SSDI TECHNICAL FRAMEWORK

MP-SSDI TECHNICAL FRAMEWORK –Draft version 1.0

Madhya Pradesh Agency for Promotion of Information Technology

2 | P a g e

Contents Executive Summary ................................................................................................................................. 4

Background Note .................................................................................................................................... 5

Architecture for MP-SSDI ........................................................................................................................ 8

Architecture Building Block ................................................................................................................. 8

Service Provider ...................................................................................................................... 8

Service Broker: ........................................................................................................................ 8

Service Consumer: .................................................................................................................. 9

Building Block Diagram: ................................................................................................................ 10

Typical Mash-up Architecture- ......................................................................................................... 11

Interoperability & Data Exchange Standards ........................................................................................ 12

Formats for Data Exchange: .............................................................................................................. 12

(i) Geo-spatial Vector Data ............................................................................................................ 12

(ii) Geo-spatial Raster Data ........................................................................................................ 13

(iii) Non-GIS Data ......................................................................................................................... 14

Protocols: .......................................................................................................................................... 15

(i) HTTP .......................................................................................................................................... 15

(ii) HTTPS .................................................................................................................................... 15

(iii) FTP ......................................................................................................................................... 15

(iv) SOAP ...................................................................................................................................... 15

Data Sharing .......................................................................................................................................... 16

Web Map Service: ............................................................................................................................. 16

Web Feature Service: ........................................................................................................................ 16

Web Coverage Service: ..................................................................................................................... 16

Web Map Tile Service: ...................................................................................................................... 16

Web Processing Service: ................................................................................................................... 16

SOAP Based XML Web Service: ......................................................................................................... 16

RESTful Web Service: ........................................................................................................................ 16

Data Processing ..................................................................................................................................... 17

Centralized Processing ...................................................................................................................... 17

1. WPS Service ........................................................................................................................... 17

2. Custom Build Web Service .................................................................................................... 17

Distributed Geospatial Analysis ........................................................................................................ 17

1. Plug-ins .................................................................................................................................. 17

3 | P a g e

2. Offline processing ................................................................................................................. 17

Application / Web Service Security ....................................................................................................... 18

Map Service Security ......................................................................................................................... 18

Denial of Service ............................................................................................................................... 18

Datum: .................................................................................................................................................. 20

Map Projections .................................................................................................................................... 21

Metadata Standards ............................................................................................................................. 22

Vector Data Model & Schema ............................................................................................................... 26

REFERENCES ................................................................................................................................ 30

Annexure I ....................................................................................................................................... 31

Annexure II ..................................................................................................................................... 51

4 | P a g e

Executive Summary

In the line of National Spatial Data Infrastructure (NSDI), at State level State Spatial Data

Infrastructure (SSDI) is formed. To setting up SSDI in Madhya Pradesh, regulate remotely

sensed data, encourage GIS & RS technology in governmental processes and to maintain &

allow easy access of spatial data among all the stake holders, State Government issued

Madhya Pradesh State Spatial Data Policy-2014 (MP-SSDP) on October 14th, 2014. In the

State, Department of Science & Technology as nodal department and MAP_IT as nodal

agency, declared to implement the MP-SSDI.

This technical framework document is prepared to give a high level understanding of

architecture, protocols, data schema, data exchange formats, projections & datum etc.

being proposed in the MP-SSDI. The low level architecture, clearing house mechanism,

exception handlings, UML based detailed schema/ data models are some of the few things

which are not touched in this version of the framework.

The 1st chapter Architecture of MP-SSDI gives information about the building blocks of

adopted service oriented architecture. It gives information about services, data encoding

and various physical layers.

Information related to supported data formats for vector, raster & non-spatial and

communication protocols related information is given in chapter 2 Interoperability & Data

Exchange Standards.

The 3rd chapter listed out proposed map and other services planned to use. Most common

OGC service WMS, WFS, WCS, WMTS & WPS are proposed. For share non-spatial data SOAP

based XML & RESTful web services are proposed.

Both centralized and distributed data processing model is proposed to fulfil the requirement

of any geo-processing related task. The chapter 4 Data Processing touched on this part.

Security is always a concern especially in geo-spatial data. The chapter Application / Web

Service Security listed out the proposed security mechanism.

5 | P a g e

The World Geodetic System 1984 (WGS 84) is seen as a commonly accepted datum even in

the Survey of India open series maps. Hence, the same is proposed to use for all the

datasets of MP-SSDI centralized repository.

The Transverse Mercator (TM) project system with modified parameters is selected for the

datasets. The information about modified parameters is detailed out on chapter 7-Map

Projection.

Metadata are critical in SDI implementation. NSDI Metadata Standard Version 2.0 are

adopted for MP-SSDI and listed out in Chapter 8-Metadata Standards. These metadata are

grouped in 28 categories and out of 127, 64 are marked as Mandatory and rest are Optional.

Chapter 9-Vector Data Model & Schema contains the list of GIS layers to be put for common

use. Data models for 12 administrative boundaries and 10 other layers is defined right now.

Data models for department specific GIS layers will be added once data sharing related

information received from the departments.

The technology is changing very fast in now days and geo-spatial is one of them. This is the

1st attempt to create the framework and not the last. It is proposed to enriching the

framework document based on the suggestions, technology trends and standards coming in

the use.

****

6 | P a g e

Background Note

Throughout the course of history geospatial data has played a significant role in

technological, economic, political and cultural dimensions of the society. Through

technological developments taking place, the mapping (collection, analysis and

representation) of geospatial data is continuously developing. In regards to this creation of

geospatial data appears to be a scientific matter.

Geospatial information is growing rapidly as like many areas of Information Technology.

Standards are crucial to share the geo-spatial data across the state and national users which

enable them to work together.

The unique integration capabilities of a GIS allow disparate data sets to be brought together

to create complete picture of a situation. GIS technology illustrates relationships,

connections, and patterns that are not necessarily obvious in any one data set, enabling

organizations to make better decisions based on all relevant factors.

There are a number of organizations proposing standards for the dissemination of

geographic information. One of the primary concerns in data exchange is proper transfer of

metadata. Metadata is data that describes features of other data, such as, the date of

production, processing techniques, analysis performed, original source, etc.

The exchange of geospatial information, especially among government organizations, and

from legacy systems, has led to the demand for a common data format. Standards provide a

common method to manage, access, and display information.

In the past, several government departments developed spatial datasets pertaining to their

domain/requirements but the datasets from different organisations followed different

standards in terms of scale, projection, accuracy, content and format and there was always

a lack of standardized data.

The Central Government announced the National Map Policy (NMP) on 19th May 2005. The

NMP document authorizes Survey of India (SOI) to issue detailed guidelines on the

implementation of the NMP. Following policies were taken in reference during drafting this

document-

• National Map Policy, 2005

• NSDI Resolution, 2006

• National Remote Sensing Policy, 2011

• National Mirror Committee for ISO TC 211 by BIS

• National Data Sharing & Accessibility Policy, 2012

• NSDI Metadata version 2.0

• State Data Sharing Policies (Delhi, MP, Odisha)

• Draft National Geo-spatial Information Policy 2016

7 | P a g e

Objective:

Following are the major objectives for technical framework -

To develop and maintain standards for collation and creation of digital geo-spatial

data.

To develop common solutions for discovery, access and use of spatial data in

response to the needs of diverse user groups

To listing out the technical protocols, formats and methodology for smooth

integration of different IT systems with MP-SSDI

To increase the awareness & understanding of the concepts and benefits of

geospatial technology

8 | P a g e

1. Architecture for MP-SSDI

In view of current technology trend and need of integration between heterogeneous

systems the Service Oriented Architecture is proposed for MP-SSDI. It will address the

requirement of users interested in the visualisation and analysis of the data organized and

maintained by different sources, without having to install the specific applications or data

on their system. They would to be able to connect to data services in real time and create

different data combinations, and ultimately consume, publish or share the contents and

services with third party applications.

Architecture Building Block

Details of each building block of SoA is as below-

Service Provider

The service provider building block contains the information about various services

available through the SSDI. Based on the nature and functionalities the services can be

grouped as below-

o Data Services - The services, those expose the processable data like Web

Feature Service (WFS), Web Feature Service with Transaction (WFS-T), Web

Coverage Service (WCS) and Custom Web Services are kept inside this group.

To make the provisions of near future demand of IoT (Internet of Things) &

Smart Cities related requirements Sensor Web Enablers (SWE) will be the part

of Data Services.

o Portrayals Services – The services used to provide the data for

representation & overlaying but cannot be used in processing are member of

Portrayal Services. The Web Map Services & Web Map Tile Services are part

of this building block.

o Processing Services – The data processing services like OGC Compliant Web

Processing Service, Sensor Alert/ Event Service, Customized Geo-processing

Service & Geo-coding services are part of Processing services. Detailed

information available in section Data Processing.

Service Broker: The service broker is meant to be a registry of services, and stores

information about what services are available on which format and who can use them.

9 | P a g e

Following OGC compliant Catalogue Service for Web (CSW) will be available for service

consumer to search the information about service & data –

o Meta Data Catalogue – To find Meta data information about available data.

The metadata standards version 2.0 approved by NSDI will be used as it is in

MP-SSDI also. Details can be seen in Technical Framework Part 1 - Meta Data

Standards.

o Service Catalogue - To find available services & allowed operations. Details of

type of services can be seen in Data Sharing section of this document.

o Style Catalogue – Representation of Standard WMS/WFS services can be

changed using published SLDs. The Style catalogue can be used to provide

information for available Style in the SSDI.

o Other – To get custom web services or any other information about services

& data if not covered in OGC compliant CSW.

Apart from the catalogue information, data encoding related information can also be

searched through the service broker. Total 12 different encoding formats will be

available through SSDI. List & details of these encoding formats are available in Data

Exchange & Protocols section.

Detailed specifications and manual to use the services will be published separately

before the service published on MP-SSDI.

Service Consumer:

The service requesters search for the entries of data, service & operation in the service

registry in order to invoke the service and use for the business needs. Services can be

invoked through the mobile, standalone PC connected through network, thin client or

web services through other web application or sensor feeds.Typical service consumers

would be as below –

o Data Discovery Client –Standard Desktop GIS Applications or web application

those can crawl or search through map service end points or Meta data and put the

information about available data can be put inside data discovery clients.

o Map Viewing Client –Standard Desktop GIS Applications, Mobile GIS Application or

WebGIS application used in map viewing purpose can be put inside this category.

o Geo-Processing Client –The GIS applications whether it is web, desktop or mobile

which can invoke Geo-Procesing (WPS or Proprietary) can be put into this category.

Such application can also display the data received after processing.

10 | P a g e

o Image Processing Client - Image processing clients are typical image processing

software used in image classification; feature extraction etc can be put inside this

category. It can be desktop based on web based.

o Styling Manager - To create, edit and manage the styles (SLDs) to use in

conjunction with WMS / WFS, specialized software can be used or plug-in with

standard GIS software can be used.

o Custom Web Service Client – The other web application or mobile application

those are consuming non-OGC / customized web services are falling under this

category. For example if

o Sensor / Event Feed Client –Various sensor feeds like Vehicle Tracking Devices or

air / water health sensor feeds are typical example of clients falling under this

category.

Building Block Diagram: The diagrammatic view of proposed architecture is as below–

Details of various services, encoding format is elaborated in Data Exchange Format &

Protocols & Data Sharing section.

11 | P a g e

Typical Mash-up Architecture-

Data layer will not be exposed directly to outer world and applications can access the data

through the services only. The communication between all the layers will happen as per the

protocols and data exchange formats mentioned in

12 | P a g e

Interoperability & Data Exchange Standards section. Typical mash-up architecture for general

use cases will be as below-

13 | P a g e

2. Interoperability & Data Exchange Standards

To ensure smooth integration of services and data among multiple sources & platforms,

interoperability & data exchange related standards and protocols have to be define. These

standards and protocols address the respective systems (software, hardware & firmware) to

allow their interaction with other systems.

This part of the document listed out adopted standards and data exchange protocols for

MP-SSDI. The data stored / shared through MP-SSDI may not available in all the formats

mentioned below. The selection of formats will be done on case to case basis.

Formats for Data Exchange:

The listing of the formats helps system integrators & solution architectures who would like

to integrate other systems with MP-SSDI. The list gives available options for integration and

data exchange purpose. It is not necessary that all the formats listed below will be

supported by default, the formats those expose the geometry information will be supported

on case to case basis and MP-SSDI will provide a mechanism to get support for such formats

through the portal.

The supported formats can be categorized in 3 categories (i) Geo-spatial Vector Data, (ii)

Geo-spatial Raster Data & (iii) Non-GIS Data. List of various formats under each category

along with short details is as below-

(i) Geo-spatial Vector Data

To fulfil user department’s needs it may be required to share or exchange spatial

data in standard vector data formats additional to standard Map Service. For

example providing data for offline /desktop based geo-processing, interactive

map rendering at client side, mobile mapping etc. To cater such requirements

support on following vector data formats will be available -

A. GML

To fulfil the requirement of client side rendering of maps to build interactive

maps, MPSSDI will support data exchange through OGC compliant GML ver

3.x as per ISO 19136. As per specification it contains geometry definition of

the objects hence the support will be provided on case to case basis.

B. CityGML

To build, store and share the virtual 3D view models & schema CityGML is

being used commonly which is the extended version of GML 3.1.1. The same

will be supported in MP-SSDI.

14 | P a g e

C. KML

Google Maps and Google Earth are used in various projects for simple map

based display purpose and KML files are commonly used in these systems. For

integration with such systems MP-SSDI will support OGC adapted the KML

version 2.2 format for data overlaying purpose.

D. GeoJSON

To build lightweight and interactive mapping application GeoJSON is being

commonly used in most of the JavaScript based libraries like OpenLayers,

Leaflet, ArcGIS JS API etc. MPSSDI will support the specifications of GeoJSON

published under rfc7946 for integrating applications.

E. GeoPackage

To develop and integrate with Mobile-GIS applications OGC compliant

GeoPackage will be supported in MP-SSDI. This format is commonly used to

build the mobile application having functionality for limited connectivity or

offline map rendering using vector and/or tile based raster data. The data

available with MPSSDI can be made available as GeoPackage on request and

on case to case basis.

F. Shapefile

To keep backward compatibility and offline data exchange purpose support

to Shapefile data format will be continued in MP-SSDI. Typical use cases for

shapefile will be in importing data from user departments to push into

centralized repository or to export data for offline usage.

(ii) Geo-spatial Raster Data

Some department requires raster datasets primarily satellite images for offline

image processing, image classification and data extraction purpose. Vice-versa

acquired raster datasets by the departments can also be used by MP-SSDI for

putting in centralized repository. To cater such requirement following raster

data formats will be supported-

A. GeoTIFF

The OGC supported GeoTIFF will be continued in MP-SSDI to serve the geo-

referenced imageries for offline usage.

B. JPEG2000

JPEG2000 image format will be supported in MP-SSDI to serve geo-referenced

imageries when the raster data is required for visualization purpose.

15 | P a g e

C. IMG

ERDAS imagine IMG data format will be supported on MP-SSDI as and when

required.

(iii) Non-GIS Data

In various use cases like creating on-the-fly thematic maps, linking additional

data, querying etc, it is required to use non-GIS data generally known as

attribute data for linking or sharing with external data source or web services.

For example to create a thematic map of District wise Allotted Scholarship,

School Education department may like to use administrative boundary maps

from MP-SSDI, district wise attribute data from scholarship portal, generate

thematic map using some mash-up APIs and show it on their portal. Another use

case may be populating crime locations data available in a CSV file to overlay on

map. To handle such type of scenarios MP-SSDI will support following formats

for integration purpose-

A. XML

Most of the systems developed in early 2000 even in current era also are

using Extensible Markup Language (XML) based web services for data

exchange. The MP-SSDI will continue to support XML based specification 1.0

for data exchange so that integration with such systems can be made

possible.

B. JSON

To keep data exchange light, language independent and promote AJAX based

data transmission; specifications of JavaScript Object Notation (JSON) ECMA-

404 are adopted. All the custom web services will consume or deliver data in

JSON object wherever required.

C. CSV

The comma separated value (CSV) is simple text file where each column value

is separated by the comma (,) and each row is separated by the line feed. This

format will be supported by the MPSSDI for thematic map preparation or

data overlaying in online applications. This format can also be used in data

creation or for data updation purpose in offline applications.

D. GPX

To import the data captured through GPS devices for data creation and

overlaying purpose GPS Exchange Format (GPX) will be supported by MP-

SSDI.

E. Base64 Encoding

The base64 encoding is adopted by MPSSDI to support media attachments

like image, audio or video or any other file associated with the features.

16 | P a g e

Protocols:

Following internet data communication protocols will be used in MPSSDI for all type of data

exchange.

(i) HTTP

The Hyper Text Transfer Protocol is most common protocol for information sharing over

the web. The same will be used in MP-SSDI for all the web applications developed but

limited to static information sharing and static pages only. The latest version HTTP v 2.0

is adopted for this purpose.

(ii) HTTPS

For all the geographic information, services and to run the web application HTTP over

secure socket layer (SSL) i.e. HTTPS will be used. All the map services, APIs, web services

are also exposed only through HTTPS.

(iii) FTP

For exchanging large size files like imageries, clipped data etc will be shared through File

Transfer Protocol. The FTP will not be accessible to Anonymous User.

(iv) SOAP

Simple Object Access Protocol (SOAP) will be supported for delivering data through OGC

services Or consuming data feed through XML web services.

17 | P a g e

3. Data Sharing

As Service Oriented Distributed Architecture is proposed for the SSDI so all the data (spatial & non-

spatial) data put on SSDI will be served through the web services only. Both types of data (spatial &

non-spatial) are exposed through the OGC compliant map services, RESTful Services, Remote

Procedure Call (RPC) or SOAP based XML services.

Details of adopted map & web services are as below-

Web Map Service: To serve the geo-spatial data for layer overlay purpose all the services will be published as

WMS service. The current specification of WMS 1.3.0 which is equivalent to ISO 19128 is

adopted. For compatibility purpose with old systems data will be available on specification

WMS ver 1.0.0, 1.1.0 & 1.1.1 also.

Web Feature Service: As and when required or on request certain vector data is published on WFS specification

1.1.0 and 2.0.

Web Coverage Service: To share the raster datasets for modelling and analysis purpose certain raster datasets will

be available as WCS service. WCS specifications WCS 1.0.0, 1.1.0, 1.1.1, 1.1.2, and 2.0.1 will

be used for publication.

Web Map Tile Service: To serve the cached maps for performance point of view base maps or any other least

updatable maps will be available as WMTS version 1.0.0.

Web Processing Service: To perform geospatial operation through the server GIS based processing services can be

published under WPS specification 1.0.0 as and when required or on request.

SOAP Based XML Web Service: Apart from the OGC compliant map services as per requirement other Simple Object Access

Protocol (SOAP) based XML web services can be published to serve non-spatial data as per

XML specification 1.0 of W3 standards.

RESTful Web Service: To make the interaction between requester and sender MPSSDI encourage use of

Representational State Transfer (REST) based web services. All the custom made web

services shall be built as RESTful web service for data interchange.

18 | P a g e

4. Data Processing

GIS & Image processing tasks are time and resource consuming. Traditionally desktop based

software’s are used to perform such task. But with the advancement in WebGIS technology

these task can be performed at server end remotely upto certain level. Different vendors

are proposing different solutions to run geo-processing / image processing on the fly. Open

Geo Consortium has also defined the standards of Web Processing Service (WPS) to cater

such requirement. Web based and server based geo-processing is preferred on MP-SSDI

platform but modules can be build on case to case basis for thick clients if centralized

processing not feasible or practical.

To perform geo-processing and image processing task following arrangements are planned

in MP-SSDI platform-

Centralized Processing

1. WPS Service

Generic geo-processing services those can be executed with-in a time span of 2 to 3

minutes can be publish as WPS. The targeted clients are other WebGIS applications.

For example to extract the data for given area of interest and mail to targeted users

can be put inside WPS service.

2. Custom Build Web Service

To address the lightweight GIS based queries and operations for consumption in non-

GIS applications custom build web services can be developed. These services fulfil

the requirement of such task those WPS services are fatty. For example identifying

the admin units for given list of latitude/longitude will be useful to initiate the

workflows in non-GIS or mobile based application.

Distributed Geospatial Analysis

1. Plug-ins

To perform routine task in distributed environment plug-in for standard GIS/Image

Processing desktop software like QGIS, ArcGIS or ERDASS Apollo can be developed.

Developed plug-in can communicate to centralized repository for data download or

use locally available data, process and produce the result for local usage.

2. Offline processing

Sometime it is needed to run specific model with standard GIS software which is of

non-generic nature and only data is required from MP-SSDI. To address such cases a

set of data can be provided in form of standard data formats like Shape File, GeoTIFF

etc for offline processing on request and case to case basis.

19 | P a g e

5. Application / Web Service Security

Security is important concern when delivering data over web or accessing any web

application and the same is applicable for any spatial data infrastructure. Security policies

have to be laid down for accessing data, application, executing remote process etc.

Following security mechanism are proposed for MP-SSDI security –

Map Service Security

All the map services will be published as secured map service whether data published

through map service declared as open access or not. There will be following methodologies

or mix of methodologies will be adopted to implement service level security –

1. Token Based Authentication

For short time (1 minute to 1 day) service accessibility, token or auth-key will be issued

to access map services. The provided auth-key/token can be used by client application in

3rd party web, desktop or mobile application. Token generation will be done by API

released by MPSSDI.

2. User & Web Referrer based Authentication

This type of authentication will be provided to access services in other web applications

in long term basis. Such type of access will be allowed to request coming from specific

web application only. Online system will be available to register the user and made the

request for desired services. The MPSSDI administrator will take decision on each

request coming for request.

3. User based Authentication

To access the map services in desktop or other thick clients for userid/password will be

provided on case to case basis. It is expected that such type of request will be received

from very less users so it is proposed to process these requests offline.

Denial of Service

To tackle the attacks related to Denial of Services (DOS) and Distributed Denial of Services

following provisions will be made –

1. TCP/IP Filtering

To reduce the chances for bandwidth choking TCP/IP based filtering can be used.

Specific type of services and operation can be allowed to white listed IPs. Also,

blacklisting of IP can be done for request coming from suspicious IP segments.

2. Limiting Request

Rules will be defined to process maximum request per second per user.

20 | P a g e

3. Captcha Provision

All the Web applications have to be implementing Captcha to handle DoS attacks.

21 | P a g e

6. Datum:

The World Geodetic System 1984 (WGS 84) is seen as a commonly accepted and

absolute global geodetic positioning system where coordinates are defined with

reference to the centre of Earth. WGS 84 datum is currently accepted as the best-

defined mathematical model to describe the earth’s surface. The SOI Open Series

Maps are also on WGS 84 datum and thus complete inter-compatibility would be

achieved. So, it is proposed to continue with WGS-84 datum in MP-SSDI.

22 | P a g e

7. Map Projections

Map Projections are equally important parameters in the standardisation process –

especially when different process elements are involved. When defining spatial data

standards, the problem of choosing the most suitable Map Projection becomes important –

though, today with the availability of automated tools, it is easy to re-project spatial

information from one Map Projection to another.

As per the NNRMS standards (ISRO: NNRMS: TR: 112: 2005; COMMITTEE REPORT) LCC and

TM projections should be considered for the different states of India.

As far as GIS database is concerned, archival of the spatial elements in Geographic

Coordinates would be the best choice as free from projections and allow flexibility for

seamlessness and also for providing outputs in any desired Map projection of choice of user.

The GIS database in Geographic coordinates gives a lot of flexibility in design and outputs.

Once the datum is fixed as WGS84 and the database is in geographic coordinates, then the

choice of map projection can be any projection be it LCC or TM. It is very easy to transform

coordinates from one projection system to another which have same datum. Almost all

commercially available GIS software can do such transformations. But it is preferable to use

UTM (Universal Transverse Mercator) Projection, which is a special case of TM as it is being

used worldwide besides Survey of India in its Open Series Maps. The main advantage of

UTM is that it is a standard projection whose parameters are defined and it is very easy to

convert the geographical coordinates to UTM grid coordinates and vice versa.

As MP is falling 3 different UTM Zones so to use only one projection for the whole State,

following parameters are proposed-

PARAMETERS OF TM PROJECTION SYSTEM

PROJECTION FALSE

EASTING

FALSE

NORTHING

CENTRAL

MERIDIAN

SCALE

FACTOR

LATITUDE OF

ORIGIN

LINEAR

UNITS

TM 500000.0000 500000.0000 78.41600000 0.99944400 24.00000000 Meter

All the databases should have a same co-ordinate and projection system and calling for a

Seamless system for MP state. These Standards are “generic” in nature and suggested to

enable systematic generation of the MPSSDI Repository.

23 | P a g e

8. Metadata Standards

Metadata are key component for data discovery whether it is spatial data or non-spatial

data. In Spatial Data Infrastructure (SDI) context it is very important as it provides a basis

to user to search geographic data availability, nature and holdings for data discovery/

access and processing.

National Spatial Data Infrastructure (NSDI) has released NSDI Metadata Standards ver

2.0 in year 2009. These standards are defined by a working group after reviewing OGC

and international standards and adopted as it is for MP-SSDI.

As per NSDI Metadata Standards total 127 metadata should be managed for GIS layers

being published in SDI. These metadata are grouped in 28 categories and out of 127, 64

are marked as Mandatory and rest are Optional. The list of Meta data is as below-

Sr Elements Scheme Category

1 Data Identification

Information Mandatory

Name of the Dataset Mandatory

Name of the Data Mandatory

Theme Mandatory

Keywords Mandatory

Access Constraints Mandatory

Use Constraints Mandatory

Purpose of Creating Data Mandatory

Data Type Mandatory

2 Contact Information

Contact Person Mandatory

Organization Mandatory

Mailing Address Mandatory

City/Locality Mandatory

Country Mandatory

Contact Telephone Mandatory

Contact Fax Mandatory

Contact Email Mandatory

3 Coverage

coverage.x.min Mandatory

coverage.x.ma Mandatory

coverage.y.min WGS84LL Mandatory

coverage.t.late CE date Mandatory

coverage.t.early Mandatory

coverage.PlaceName Mandatory

coverage.PeriodName Mandatory

coverage.spatial.resolution Mandatory

coverage.spatial.georeference Mandatory

coverage.spatial.aggregation Mandatory

coverage.temporal.precision Mandatory

24 | P a g e


coverage.temporal.interval Mandatory

coverage.temporal.aggregation Mandatory

coverage.note Mandatory

coverage.AlternativeMetadata Mandatory

4 Geographic location of the dataset

Metadata.identificationInfo > Optional

DataIdentification.extent > Extent > Optional

Geographic BoundingBox or GeographicDescription

Optional

5 Citation

Data Prepared by Mandatory

Original Source Mandatory

Source Scale and Date Mandatory

Mapping year Mandatory

digitizing year Mandatory

survey year Mandatory

Lineage Mandatory

Associated Project preparing the data Mandatory

Associated Publications person.Email Mandatory

person.Affiliation CorporateName Mandatory

CorporateName.Address Mandatory

6 Metadata date stamp

Metadata.dateStamp Mandatory

MISO08601 Mandatory

7 Type

Data Format Optional

Data File Size Optional

Data Physical Location (Computer + path) Optional

8 Subject subject.specific Optional

subject.domain Optional

9 Description description Optional

description.history Optional

10 Publisher Publisher.address Optional

publisher.address Optional

11 Dataset responsible party


DataIdentification.pointOfContact > Optional

ResponsibleParty Optional

12 Distribution Format

Metadata.distributionInfo > Distribution > Optional

Format Optional

13 On-line resource

Metadata.distributionInfo > Distribution > Optional

DigitalTransferOption.onLine > Optional

OnlineResource Optional

14 Dataset topic category

Metadata.identificationInfo > Mandatory

DataIdentification.topicCategory Mandatory

15 Language language ISO0639-2Bsh Mandatory

16 Abstract describing the data

Metadata.identificationInfo > Mandatory

DataIdentification.abstract Mandatory

17 Spatial Metadata.identificationInfo > Optional

25 | P a g e


representation type

DataIdentification.spatialRepresentationType

Optional

18 Spatial resolution of the dataset


DataIdentification.spatialResolution > Optional

Resolution.distance or Resolution.equivalentScale

Optional

19 Reference system

Metadata.referenceSystemInfo > Optional

ReferenceSystem.referenceSystemIdentifier

Optional

>RS_Identifier Optional

20 Temporal extent information for the dataset


DataIdentification.extent > Optional

Extent.temporalElement Optional

21 Vertical extent information for the dataset


DataIdentification.extent > Optional

Extent.verticalElement > VerticalExtent Optional

22 Quicklook Graphic file format / Map in encrypted mode

Optional

23 For Image Data

Name of the Satellite Mandatory

Sensor Mandatory

Path Mandatory

Row Mandatory

Image Acquired From Mandatory

Date and Time of Image Mandatory

File Format Mandatory

Bits per Pixel Mandatory

Spatial Resolution Mandatory

Spatial Resolution Unit Mandatory

Number of Bands Mandatory

Number of Rows Mandatory

Number of Cols Mandatory

Purchased or Obtained on Exchange Basic Mandatory

24 Rights Rights Optional

25 Team

xxxxx.team Optional

xxxxx.expert.commentary Optional

xxxxx.expert.internal_notes Optional

26 Attributes/Entity and Attribute Information

Entity_and_Attribute_Overview and/or Optional

Entity_and_Attribute_Detailed_Description

Optional

27 Projection Information

Name of Projection Optional

Unit Optional

Projection Parameters Optional

28 Data Quality

Logical_Consistency_Report Optional

Completeness_Report Optional

Process_ Description Optional

26 | P a g e


Process_Date Optional

Source_Originator Optional

Source_Publication_Date Optional

Source_Title Optional

Source_Online_Linkage Optional

Source_Scale_Denominator Optional

Type_of_Source_Media Optional

Source_Time_Period_of_Content Optional

Source_Currentness_Reference Optional

Source_Citation_Abbreviation Optional

Source_Contribution • If data assessments performed:

Optional

Attribute_Accuracy_Report (if applicable) Optional

Horizontal_Positional_Accuracy_Report (if applicable)

Optional

Vertical_Positional_Accuracy_Report (if applicable)

Optional

Source: NSDI Meta Data Standards ver 2.0

27 | P a g e

9. Vector Data Model & Schema

Spatial data formats are based on representations of the real world which can be placed in a

GIS to produce the maps, perform interactive queries and execute analyses. Spatial features

aggregated into collections of points, Lines & polygons. Topological relationships should

have been maintained.

The main aim of data models is to support the development of information systems by

providing the definition and format of data. The state specific general contents are

proposed here to keep homogeneity in the data that can be used by all departments.

REF: AMRUT CITIES, DESIGN & STANDARDS

Contents Spatial Layers Type Annexure

Base Map Layers 1. State Boundary 2. Division Boundary 3. Parliamentary

Constituency 4. District Boundary 5. Legislative

Constituency 6. Tehsil Boundary 7. Block boundary 8. GP Boundary 9. Municipal Boundary 10. Zone Boundary 11. Ward Boundary 12. Village Boundary

I

Khasra

Khasra

Forest Boundaries

Reserve Forest Protected Forest National Park Sanctuary

Rail Network

Broad Gauge Meter Gauge Other Gauge

Road/Road Centreline Network

National Highways State Highways Major District Roads Other District Roads City Roads Link Roads/Bypass Streets Path Track Village Roads

28 | P a g e


Bridges/Flyover

Bridges Flyover Culvert

Drainage/Streams Network

Drainage/Streams Network

Waterbodies

Major Rivers Lakes Reservoirs Pond/Tank

Canal Network

Major Canal Minor Canal Distributary Canal

Settlement Settlement

Landmarks Landmarks Railway station Bus stop Petrol pump Schools Hospitals Govt. Offices Banks Religious Places Tourist Places Malls Dams

LU/LC Layers

Class-I Class-II Class-III

II

Built-up

Residential

Planned Semi Dense Dense

Commercial

Retail and General Business Community Centre Wholesale and Warehousing Major Shopping Centres/ Malls Hotels/Resorts/Restaurants Cineplex/Cinema Hall Marriage Garden/Function Hall Market yards Petrol Pump/LPG filling station Others

29 | P a g e


Industrial

Manufacturing Service Chemical Pharmaceutical Textile IT Parks Industrial Estate / SEZ Agro based Food Processing Other Industries

Mixed Residential & Commercial Residential & Educational Residential & Health Services

Public & Semi Public

Educational Institutes Cantonment Health Services Aanganwadi Cremation/Burial Ground Social and Cultural Centre Religious Places Government Offices Police Station Fire Station Rest / Circuit House Electric sub-station Jail Auditorium/Museum Banks/ATM’s Public/Community Toilets Orphanage/ Old Age Homes Others

Transport & Communication

Bus Stop Bus Terminus Railway Stations Railway Property Railway Line / Sidings Airport / Air strips Helipad Roads Bridges / Flyovers Transport Nagar Taxi/Auto Stands Others

Recreational

Garden/ Park Play Ground Club Sports Centre Gymnasium

30 | P a g e


Swimming Pool Stadium Planetarium Aquarium Open Air Theatre Golf Course/Race Course Exhibition Ground Amusement /Theme Park Others

Water Bodies

River Stream/ Drain Canal Lakes/ Reservoir Back Water Ponds/Tanks Island (River/Lake)

Vacant Land

Government Land Private Land Reclaimed Land Layout / Plotted

Green Areas

Reserved Forest Protected/Notified Forest Green Belt

Agricultural Land

Cropland Fallow land Plantations Orchard Horticulture Plant Nursery

Wasteland

Scrubland Barren Rocky Sandy Area Salt Affected Gullied

Wetland

Waterlogged Low Lying Area Marshy Swampy

31 | P a g e


Others Aquaculture Brick Kiln Quarry Dam/Barrage Farm House Dairy Farm Poultry Farm Slaughter House Dairy Booth

REFERENCES

1. FORMULATION OF GIS BASED MASTER PLAN FOR AMRUT CITIES, DESIGN & STANDARDS, MARCH 2016,

TOWN AND COUNTRY PLANNING ORGANISATION, MOUD, GOI, NEW DELHI.

2. NSDI META DATA STANDARDS 2.0

32 | P a g e

Annexure I

S.No SPATIAL

LAYER TYPE GEOMETRY SYMBOL

1

Administrative

Boundaries

State Boundary Polygon

District Boundary Polygon

Tehsil / Block Boundary Polygon

GP Boundary Polygon Village Boundary Polygon

Municipal Boundary Polygon

Zone Boundary Polygon Ward Boundary Polygon

33 | P a g e

Spatial layer schema for State Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the State in Hindi

Name in

English Name_E Text 50 Name of the State in English

Area in

sq. km. Area_sqkm Double

Up to 4

decimals

Area of corresponding

State boundary

State Code State_Code Alphanumeric 10

34 | P a g e

Spatial layer schema for District Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the District in Hindi

Name in

English Name_E Text 50 Name of the District in English

Area in


Up to 4

decimals


District boundary

District

Code Dist_Code Alphanumeric 10


35 | P a g e

Spatial layer schema for Tehsil Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the Tehsil in Hindi

Name in

English Name_E Text 50 Name of the Tehsil in English

Area in


Up to 4

decimals


Tehsil boundary

Tehsil Code Teh_Code Alphanumeric 10

District



36 | P a g e

Spatial layer schema for Block Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the Block in Hindi

Name in

English Name_E Text 50 Name of the Block in

English

Area in


Up to 4

decimals

Area of

corresponding block

boundary Block Code Block_Code Alphanumeric 10

LGD Block

Code

LGD_B_Code Alphanumeric 10

District



37 | P a g e

Spatial layer schema for GP Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the GP in Hindi

Name in

English Name_E Text 50 Name of the GP in English

Area in


Up to 4

decimals

Area of

corresponding GP

boundary GP Code GP_Code

Alphanumeric 10

LGD GP

Code

LGD_G_Code Alphanumeric 10

Block Code Blk_Code Alphanumeric 10

LGD Block

Code



District



38 | P a g e

Spatial layer schema for Village Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the Village in

Hindi

Name in

English Name_E Text 50 Name of the Village in

English

Area in


Up to 4

decimals

Area of

corresponding

Village boundary Village

Code Vill_Code

Alphanumeric 10

GP Code GP_Code Alphanumeric 10

LGD GP

Code



LGD Block

Code



District



Census

Code

ccode_11 Alphanumeric 18

39 | P a g e

Spatial layer schema for Municipal Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the Municipal in Hindi

Name in

English Name_E Text 50 Name of the Municipal in

English

Area in


Up to 4

decimals


Municipal boundary

Town Code T_Code Alphanumeric 10


District



Census

Code


40 | P a g e

Spatial layer schema for Zone Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the Zone in Hindi

Name in

English Name_E Text 50 Name of the Zone in English

Area in


Up to 4

decimals


Zone boundary

Zone

Number Zone_No Alphanumeric 10



District



41 | P a g e

Spatial layer schema for Ward Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50

Name in

Hindi Name_H Text 50 Name of the Ward in Hindi

Name in

English Name_E Text 50 Name of the Ward in English

Area in


Up to 4

decimals


Ward boundary

Ward

Number Ward_No Alphanumeric 10



District



S.No SPATIAL

LAYER

TYPE GEOMETRY SYMBOL

2 Khasra Khasra Polygon

42 | P a g e

Spatial layer schema for Khasra:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50 Government Land or Private

Land

Owner

Name Own_Name Text 50 Name of the Khsara Owner

Area in

hectre

Area_hect Double Up to 4

decimals

Area of

corresponding

Khasra as per record.

Khasra

Number

KID Alphanumeric 10

BHU Code BHU_code Alphanumeric 18

Village

Code

Vill_Code Alphanumeric 10

GP Code GP_Code Alphanumeric 10

LGD GP

Code



LGD Block

Code



District



Census

Code


S.No SPATIAL


3 Forest

Boundary Reserve Forest Polygon RF

Protected Forest Polygon PF

National Park / Sanctuary Polygon

43 | P a g e

Spatial layer schema for Forest Boundary:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50 Type As Forest

Name Name Text 50 Name of the Forest

Area in


Up to 4

decimals


Forest boundary

District



S.No SPATIAL


4

Rail Network Broad Gauge Line

Narrow Gauge Line

Other Gauge Line

44 | P a g e

Spatial layer schema for Railline:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field Width

Description/Value

Type Type Text 50 Type of Rail Line

Name Name Text 50 Name of the Rail

Line District Code Dist_Code Alphanumeric 10

State Code

State_Code Alphanumeric 10

S.No SPATIAL


5

Road/Road

Centerline

Network

National Highway Polygon / Line

State Highway Polygon / Line

Major District Road Polygon / Line

Other District Road Polygon / Line

Bypass Polygon / Line

Link Road Polygon / Line

City Road Polygon / Line

Streets Polygon / Line

Village Roads Polygon / Line

Path Track Line

45 | P a g e

Spatial layer schema for Road/Road Centerline Network:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Road

Name Name Text 50 Name of the Road

Road

Number Road_No Alphanumeric 10

Ward

Number Ward_No Alphanumeric 10

Town

Code T_Code Alphanumeric 10

Tehsil

Code Teh_Code Alphanumeric 10

District


State

Code State_Code Alphanumeric 10

S.No SPATIAL


6

Bridges/ Flyovers

Bridge Line

Culvert Line

Flyover Line

46 | P a g e

Spatial layer schema for Bridges/Flyovers:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Bridge/Flyover

Name Name Text 50 Name of the Bridge/Flyover

Town


District


State


S.No SPATIAL

LAYER


7 Drainage/Stream

Network Stream Polygon / Line

Drainage Polygon / Line

47 | P a g e

Spatial layer schema for Drainage/Stream Network:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Drainage/Streams networks

Name Name Text 50 Name of the Drainage/Streams

networks

District


State


S.No SPATIAL

LAYER


8

Water Bodies

River Polygon

Ponds Polygon

Lake Polygon

Tank Polygon Island (River/Lake) Polygon

Reservoir Polygon

48 | P a g e

Spatial layer schema for Water Bodies:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Water Body

Name Name Text 50 Name of the Water Body

Tehsil


District


State


S.No SPATIAL

LAYER


9

Canal Major Canal Line

Minor Canal

Line Distributary Canal Line

49 | P a g e

Spatial layer schema for Canal:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Canal

Name Name Text 50 Name of the Canal

District


State


S.No SPATIAL

LAYER


10 Settlement Settlement Polygon

50 | P a g e

Spatial layer schema for Settlement:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Settlement

Name Name Text 50 Name of the Settlement

Village

Code Vill_Code Alphanumeric 10

Town


Tehsil


District


State


S.No SPATIAL

LAYER


11

Landmarks

Railway Station Point Standard Symbols

will be used Bus Stop

Point

Petrol Pumps

Point

Schools

Point

Hospitals

Point

Govt. Offices

Point

Banks

Point

Religious Places

Point

Tourist Places

Point

Malls

Point

Dams Point

51 | P a g e

Spatial layer schema for Landmarks:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Type Type Text 50 Type of Landmark

Name Name Text 50 Name of the Landmark

Town


Tehsil


District


State


52 | P a g e

Annexure II

S.No CLASS SUB-CLASS GEOMETRY SYMBOL

1

Residential

Planned Polygon

Semi Dense Polygon

Dense Polygon

2

Commercial

Retail/ General Business Polygon Wholesale/ Warehouse Polygon

Community Centre Polygon

Hotel / Resort / Restaurant Polygon

Shopping Centre / Mall Polygon

Multiplex / Cinema Polygon

Function Hall / Marriage Garden Polygon

Petrol Pump / LPG filling station Polygon

Market yards

Polygon Others Polygon

3

Industrial

Manufacturing

Polygon

Service

Polygon

Chemical

Polygon

Pharmaceutical

Polygon

Textile

Polygon

IT Parks

Polygon

Industrial Estate / SEZ

Polygon

Agro based & Food Processing

Polygon

Other Industries Polygon

4

Mixed

Residential & Commercial

Polygon

Residential & Educational

Polygon

Residential & Health Services Polygon

5

Public & Semi

Public

Educational Institutes

Polygon

Cantonment

Polygon

Health Services

Polygon

Aanganwadi

Polygon

Cremation/Burial Ground

Polygon

Social and Cultural Centre

Polygon

Religious Places

Polygon

53 | P a g e

.No CLASS SUB-CLASS GEOMETRY SYMBOL

Government Offices

Polygon

Police Station

Polygon

Fire Station

Polygon

Rest / Circuit House

Polygon Electric sub-station

Polygon Jail

Polygon Auditorium/Museum

Polygon

Banks/ATM’s

Polygon

Public/Community Toilets

Polygon

Orphanage/ Old Age Homes

Polygon

Others Polygon

6

Transport &

Communication

Bus Stop

Polygon

Bus Terminus Polygon

Railway Stations

Polygon

Railway Property

Polygon

Railway Line / Sidings

Polygon

Airport / Air strips

Polygon

Helipad Polygon

Roads

Polygon

Bridges / Flyovers

Polygon

Transport Nagar

Polygon

Taxi/Auto Stands

Polygon

Others Polygon

7

Recreational

Garden/ Park

Polygon

Play Ground

Polygon

Club

Polygon

Sports Centre

Polygon

Gymnasium

Polygon

Swimming Pool

Polygon

Stadium

Polygon

Planetarium

Polygon

Aquarium

Polygon

54 | P a g e


Open Air Theatre

Polygon

Golf Course/Race Course

Polygon

Exhibition Ground

Polygon

Amusement /Theme Park

Polygon

Others Polygon

8

Water Bodies

River

Polygon

Stream/ Drain

Polygon/Line

Canal

Polygon/Line

Lakes/ Reservoir

Polygon

Back Water

Polygon

Ponds/Tanks

Polygon

Island (River/Lake) Polygon

9

Vacant Land Government Land

Polygon

Private Land Polygon

Reclaimed Land

Polygon

Layout / Plotted Polygon

10

Green Areas Reserved Forest

Polygon

Protected/Notified Forest

Polygon

Green Belt

Polygon

11

Agricultural land

Cropland

Polygon

Fallow land

Polygon

Plantations

Polygon

Orchard

Polygon

Horticulture Polygon

Plant Nursery Polygon

12

Waste Land

Scrubland

Polygon

Barren Polygon

Rocky

Polygon

Sandy Area

Polygon

Salt Affected

Polygon

Gullied Polygon

55 | P a g e


13

Wetland Waterlogged

Polygon

Low Lying Area

Polygon

Marshy

Polygon

Swampy

Polygon

14

Others

Aquaculture

Polygon

Brick Kiln

Polygon Quarry

Polygon

Dam/Barrage

Polygon

Farm House

Polygon

Dairy Farm

Polygon

Poultry Farm

Polygon

Slaughter House

Polygon

Dairy Booth Polygon

56 | P a g e

Spatial layer schema for LU/LC Layer:-

Attribute

Name

Attribute

Field Name

Attribute

Field Type

Attribute

Field

Width

Description/Value

Class Class Text 25 Class as given

Sub-Class Sub_Class Text 50 Sub Class as given

Area in sq.

mt. Area_sqmt Double

10 Up to 4

decimals

Area of corresponding feature in

sq. mt.

Name Name Text 50 Name of the Landmark

MP-SSDI TECHNICAL FRAMEWORK

Documents

Transcript of MP-SSDI TECHNICAL FRAMEWORK