NATIONAL GIS

BACK GROUND

A Vision for National GIS had been recently evolved under the aegis of the Planning

Commission through a Core Group of experts. The National GIS is envisaged as a fundamental

component of India's critical democratic and governance infrastructure, providing GIS support

to many aspects of the national economic and governance process that would benefit the nation.

The Vision is two-fold – one, to establish a “National GIS” as a technology platform through,

,an organisational structure of Indian National GIS Organisation (INGO) that is responsible

for, maintains and operates the GIS Platform.

The major elements of the National GIS platform include Infrastructure, Data assets,

Portal, Decision Support Applications and Capacity building component. The National GIS

Asset is proposed to be organized at two-levels - Seamless, nation-wide GIS content equivalent

to 1:10,000 scale and pockets of “geo-stitched” city-level larger-scale GIS Asset (wherever and

as and when available). National GIS Asset includes ~41+ GIS Features and a wide range of

~15+ sectoral geo-tagged attributes/tabular data from census, demographics, planning and

development, infrastructure and other sectoral datasets of ministries/states. It is also proposed

to allow crowd-sourced geo-tagged data content into the National GIS as an additional “citizen

layer” where citizens can populate their datasets/grievance-points etc. on the GIS frame. The

system will endeavour to integrate relevant policies and promote common standards that will

be founded on principles of “open standards” enabling inter-operability across platforms and

systems and technology neutrality.

Indian industry is envisaged to play a major role in terms of offering high-quality,

success-oriented, committed and cost-effective services and work with anchor agencies under

contractual obligations to Indian National GIS Organisation. In addition, it is proposed to utilise

the capacity of academic and other knowledge based institutions in activities related to training,

education, performance evaluation and policy analysis.

The National GIS will require high-quality documentation of standards and practices to

adopt and position, specifically on:

NATIONAL GIS STANDARDS

A National GIS Standard 2011 (TABLE- list tentatively some of the most critical

parameters in the standardization domain) that defines the mapping/surveying, GIS database

parameters and their limits for acceptance to National GIS. Existing GIS Standards like

NNRMS Standard of 2005, NSDI Metadata Standards of 2001/2009 and NSDI Exchange

Standards of 2001 have been studied, updated/enhanced and integrated into National GIS

Standards 2011 definition.

National Spatial Framework (NSF) definition with a core standard layer of India boundary

(with states, districts and other major features) as a core Geospatial dataset with appropriate

datum/projections defined – which can be made freely available and accessible for all GIS

activities in the country. The NSF, initially is to be defined equivalent to 1:50k SOI Open Series

Maps (with the available geodetic framework) and also later for 1:10k National GIS Asset (as

and when the next depth of geodetic framework is available) requirement.

Well-integrated into international standardisation efforts of OGC/ISO-TC211 and thus

bringing the 2-way integration of national standards within ISO framework.

No Parameter (All values at 3σ) National GIS Version 1 .0

(1:50,000 Version 2.0 National GIS

(1:10,000

M FRAMEWORK) FRAMEWORK)

Recommended source for National GIS Activities

Satellite images/Mapping Agencies

Satellite images/F resh Mapping

A NATIONAL GIS: SATELLITE IMAGE

STANDARDS

1 Generic/Standard Resolution 5.8m XS or better 5.8m XS or better

2

IRS Image Resolutions recommended for National GIS

5.8 m XS supported by 5 .8 m Pan / XS 2.5 m Pan fused XS

Activities

3 NSF 1:50K National GIS Foundation Dataset

1:10K National GIS Foundation Dataset

4 Projection for image outputs LCC or UTM (TBD) LCC or UTM (TBD)

5 Datum for image products WGS 84 WGS 84

6

Image Frames (geometrically corrected; important for Polygon Polygons

seamlessness)

7

Image Position (Planimetric) Accuracy (0.5 mm of scale) 25 5

in m

8 Band-to-Band Registration for XS data (0.25

pixel) in m ~6 ~1 .5

B NATIONAL GIS: MAP STANDARDS

1 NSF Nation/State Nation/State

2 Minimum Map Frame size for incorporation 15’ X 15’ 3’ 45” X 3’ 45”

3

Image Registration accuracy @ 0 .5 pixel (RMS) 12m 1.25m

No Parameter (All values at 3σ) National GIS Version 1 .0 (1:50,000

Version 2.0 National GIS (1:10,000

FRAMEWORK) FRAMEWORK) 4 Map Projection LCC or UTM (TBD) LCC or UTM (TBD) 5 Datum WGS 84 WGS 84

6 Position (Planimetric) Accuracy (1mm of scale) in m

50 10

7 Minimum Mappable Unit (MMU) (3 x 3 mm of scale) in 22500

900

sq mts

8 DEM Z-Spacing as 1mm of scale in m 50 10

M

9 DEM Z-Accuracy in m 10 5

10 Thematic Accuracy of Classification/Mapping 90/90 90/90

11 Map Formats Digital GIS compliant Digital GIS compliant Paper Paper

C NATIONAL GIS: GEODATABASE STANDARDS

1 Spatial Framework Seamless - National Seamless - National

2 Tie-Point Intervals for Spatial Framework 5’ X 5’ & 3’ 45” X 3’ 45” 45” X 45”

3 Coordinate units for Precision Decimal-Seconds Decimal-Seconds

4 Projection LCC LCC

5 Datum WGS 84 WGS 84

6 Coordinate Precision Single Single

7 Minimum Frame size for NRR 15’ X 15’ 3’ 45” X 3’ 45”

8 GIS DB Tic Registration Accuracy (0.25mm of scale) 12 .5

2.5

(RMS) in m

9 Position (Planimetric) Accuracy (1mm of scale) in m

50 10

10 Coordinate Movement Tolerance (CMT) (0 .125mm of 6.25 1.25

scale) in m*

11 Weed Tolerance (WT) (0.125mm of scale) in m* 6.25 1.25

12 Sliver Polygon Tolerance (SPT) (LESS-TH AN MMU) in <22500 <900

m*

No Parameter (All values at 3σ) National GIS Version 1 .0 (1:50,000

Version 2.0 National GIS (1:10,000

FRAMEWORK) FRAMEWORK)

13 Grid Size (for Image/Raster/DEM Layers) (0.5mm of

25 5

scale) in m

D NATIONAL GIS: OUTPUT STANDARDS

1 Output Formats Portal GIS compliant Portal GIS compliant

Digital publishing Digital publishing

Print Print

2 Output Framework Admin Units – State, District, Taluk,

Admin Units –District, Taluk, Villages

M Villages Natural Regions

Natural Regions

User defined region polygon

User defined region polygon Spatial Framework grids

Spatial Framework grids Cadastre Reference

Ownership Reference

4 Output Projection LCC / User defined UTM / User defined

5 Output Datum WGS 84 WGS 84

6 Output Formats GeoTIF, TIF, Shape file, Jpeg, NSDE,

GeoTIF, TIF, Shape file, Jpeg, NSDE, pdf,

pdf, png, GIS format png, GIS format

7 Output Symbology As per Layer Legend As per Layer Legend

8 National Spatial Framework Accuracy -

Tolerable limits <0 .1% of state or district or

taluk or tile <0 .1% of taluk or tile areas

for area of standard admin units areas

9 Framework Verification

CMT and Weed Tolerance <6 .25 <1 .25

Bound Box As per1:50 NSF As per 1:50 NSF

10 Position (Planimetric) Accuracy- Better than (Or Equal to)

75

15

1.5 mm of scale in m Output to be sampled and

certified for

Output to be sampled and certified

for

position accuracy quality position accuracy quality

11 Thematic Accuracy of Classification/Mapping 90/90 90/90

To be reported from Metadata To be reported from Metadata

12 Minimum Map Unit (MMU) – Not Less than (Or Equal 22500 900

to) (3 x 3 mm of scale) in sq mts

NATIONAL SPATIAL DATA INFRASTRUCTURE:

Background:

Government of India has notified the establishment of NSDI through a Cabinet

resolution in 2006. One of the objectives of NSDI is to provide metadata access to stake

holders. NSDI also to work on Standards development for Geospatial data covering its entirety.

It includes metadata, web services, content, proposals, exchange formats etc.

India has a vast amount of map information generated through systematic topographic,

geological, soil, cadastral surveys and various natural resources information generated with the

use of the remote sensing data. Encapsulating these maps and images into a National Spatial

Data Infrastructure (NSDI) provide information transparency and sharing, with the recognition

that spatial information is a national resource and citizens, society, private enterprise and

government have a right to access it, appropriately. One of the major elements of the NSDI is

defining common conventions and technical agreements, standards, metadata definitions,

network and access protocols – all of which will make it easily possible for the NSDI to come

into existence.

Metadata is first element of the NSDI – which enables a user to find spatial data that is

available in different NSDI Agency servers. Metadata serves two major purposes – both for

the spatial data generator and for the spatial data user. For the generator, the Metadata provides

a framework to document the spatial data and declare its content for users. For the user,

Metadata serves many important purposes, including finding the spatial data as per need;

browsing spatial data; deciding on whether the spatial data will meet the application need and

finding how the spatial data can be accessed. This Metadata Standard is an important document

that defines the schema and design for the NSDI Metadata.

The working group on Metadata Standard development along with the involvement of

Survey of India (SOI), National Informatics Centre (NIC), Geological Survey of India (GSI),

Forest Survey of India (FSI), National Bureau of Soil Survey and Land Use Planning

(NBSSLUP), National Atlas and Thematic Mapping Organisation (NATMO), Central Ground

Water Board (CGWB), Central Water Commission (CWC) and the private sector, has led the

effort of defining a ‘National Metadata Standards’.

Introduction:

NSDI is the national body to facilitate development of standards for metadata

as well as Spatial Data Infrastructure. Broad public participation, will help to ease

these problems and to develop the National user’s system. The NSDI Metadata

Standard, developed with the aim of encouraging applications, and the conditions for

accessing existing data, and to transfer data to a prospective users.

Spatial information generated either through conventional or latest

geoinformatics techniques has played a pivotal role in the sustainable development of

natural resources of the country, in recent times. Considering the importance of

providing information transparency and sharing the data among government and non-

government organisations, academia, industry and citizens at large, it is felt to have

common data standards and metadata definitions.

ISRO has taken the lead to be as chair for working group on ‘Metadata

Standards’. Various issues related to metadata standards were discussed and a decision

has been arrived to upgrade/modify the existing NNRMS-NSDI metadata standards

with respect to international standards recommended by Open Geospatial Consortium.

As per the recommendations of working group on metadata standards, the

existing NNRMS / NSDI metadata standards were reviewed against OGC metadata

standards. The necessity of all 343 elements of OGC metadata and their schema are

checked and finalized the metadata standards with 28 elements (with 9 mandatory

elements and 19 optional elements).

Scope

This NSDI metadata Standard provides a key to the information on the schema which

describes the information about the data and what services need to be given.

Proposed Metadata Standards for NSDI

As per the metadata described above the necessary standards for implementation at

National level by all NSDI agencies have been worked out using existing NNRMS and NRDB

metadata standards. Looking towards the data type available within various organizations

under NSDI the following “Metadata Standards (Table)” is proposed which need to be

implemented for future uses.

Table: Proposed Metadata Standards

Sr. No. Elements Scheme

1. Data

Identification Information

Name of the Dataset

Name of the Data

Theme

Keywords

Access Constraints

Use Constraints

Purpose of Creating Data

Data Type

2 Contact

Information

Contact Person

Organization

Mailing Address

City/Locality

Country

Contact Telephone

Contact Fax

Contact Email

3 Coverage

coverage.x.min

coverage.x.ma

coverage.y.min WGS84LL

coverage.t.late CE date

coverage.t.early

coverage.PlaceName

coverage.PeriodName

coverage.spatial.resolution

coverage.spatial.georeference

coverage.spatial.aggregation

coverage.temporal.precision

coverage.temporal.interval

coverage.temporal.aggregation

coverage.note

coverage.AlternativeMetadata

4

Geographic location of the

dataset (by four coordinates or by description)

Metadata.identificationInfo >

DataIdentification.extent > Extent >

GeographicBoundingBox or GeographicDescription

5. Citation

Data Prepared by

Original Source

Source Scale and Date Mapping

year digitizing year

survey year

Lineage

Associated Project preparing the data

Associated Publications

person.Affiliation person.Email

CorporateName.Address CorporateName

6 Metadata date

stamp Metadata.dateStamp M

ISO08601

7 Type

Data Format

Data File Size

Data Physical Location (Computer + path)

8 Subject subject.specific

subject.domain

9 Description description

description.history

10 Publisher Publisher

publisher.address

11 Dataset

responsible party

Metadata.identificationInfo >

DataIdentification.pointOfContact >

ResponsibleParty

12 Distribution

Format Metadata.distributionInfo > Distribution >

Format

13 On-line resource

Metadata.distributionInfo > Distribution >

DigitalTransferOption.onLine >

OnlineResource

14 Dataset topic

category Metadata.identificationInfo >

DataIdentification.topicCategory

15 Language language ISO0639-2Bsh

16 Abstract

describing the data Metadata.identificationInfo >

DataIdentification.abstract

17 Spatial

representation type Metadata.identificationInfo >

DataIdentification.spatialRepresentationType

18 Spatial resolution

of the dataset

Metadata.identificationInfo >

DataIdentification.spatialResolution >

Resolution.distance

or

Resolution.equivalentScale

19 Reference system

Metadata.referenceSystemInfo >

ReferenceSystem.referenceSystemIdentifier

>RS_Identifier

20 Temporal extent

information for the dataset

Metadata.identificationInfo >

DataIdentification.extent >

Extent.temporalElement

21 Vertical extent information for

the dataset

Metadata.identificationInfo >

DataIdentification.extent >

Extent.verticalElement > VerticalExtent

22 Quicklook Graphic file format / Map in encrypted mode

23 For Image Data

Name of the Satellite

Sensor

Path

Row

Image Acquired From

Date and Time of Image

File Format

Bits per Pixel

Spatial Resolution

Spatial Resolution Unit

Number of Bands

Number of Rows

Number of Cols

Purchased or Obtained on Exchange Basic

24 Rights Rights

25 Team

(organization name„xxxxx‟)

xxxxx.team

xxxxx.expert.commentary

xxxxx.expert.internal_notes

26 Attributes/Entity

and Attribute Entity_and_Attribute_Overview

and/or

Information Entity_and_Attribute_Detailed_Description

if the data includes a database that is not

documented, you are strongly encouraged to

develop the detailed description

27 Projection

Information

Name of Projection

Unit

Projection Parameters

28 Data Quality

Logical_Consistency_Report

Completeness_Report

Process_ Description

Process_Date

Source_Originator

Source_Publication_Date

Source_Title

Source_Online_Linkage

Source_Scale_Denominator

Type_of_Source_Media

Source_Time_Period_of_Content

Source_Currentness_Reference

Source_Citation_Abbreviation

Source_Contribution

• If data assessments performed:

Attribute_Accuracy_Report (if applicable)

Horizontal_Positional_Accuracy_Report (if

applicable)

Vertical_Positional_Accuracy_Report (if

applicable)

NSDI NODAL AGENCIES

Sr. Elements Scheme

1 Agency

Agency Code

Agency Name

Agency Acronym

Agency NSDIMgr

AgencyAddress1

AgencyAddress2

AgencyAddress3

Agency NSDIMgrPhone

Agency NSDIMgrFax

Agency NSDIMgrEmail

Agency Website

From the above mentioned table, 9 elements are made “Mandatory and the rest of the

elements are made optional in a meeting held on 19th February, 2009 at NSDI, New Delhi. The details of mandatory elements are as follows along with their schema.

Proposed Metadata Standards for NSDI with Nine essential elements and their schema (Mandatory)

Sr. No. Elements Scheme

1. Data

Identification Information

Name of the Dataset

Name of the Data

Theme

Keywords

Access Constraints

Use Constraints

Purpose of Creating Data

Data Type

2 Contact

Information

Contact Person

Organization

Mailing Address

City/Locality

Country

Contact Telephone

Contact Fax

Contact Email

3 Coverage

coverage.x.min

coverage.x.ma

coverage.y.min WGS84LL

coverage.t.late CE date

coverage.t.early

coverage.PlaceName

coverage.PeriodName

coverage.spatial.resolution

coverage.spatial.georeference

coverage.spatial.aggregation

coverage.temporal.precision

coverage.temporal.interval

coverage.temporal.aggregation

coverage.note

coverage.AlternativeMetadata

4. Citation

Data Prepared by

Original Source

Source Scale and Date Mapping

year digitizing year

survey year

Lineage

Associated Project preparing the data

Associated Publications

person.Affiliation person.Email

CorporateName.Address CorporateName

5. Metadata date

stamp Metadata.dateStamp M

ISO08601

6. Dataset topic

category Metadata.identificationInfo >

DataIdentification.topicCategory

7. Language language ISO0639-2Bsh

8. Abstract

describing the data Metadata.identificationInfo >

DataIdentification.abstract

9. For Image Data

Name of the Satellite

Sensor

Path

Row

Image Acquired From

Date and Time of Image

File Format

Bits per Pixel

Spatial Resolution

Spatial Resolution Unit

Number of Bands

Number of Rows

Number of Cols

Purchased or Obtained on Exchange Basic

OGC

Open Geospatial Consortium:

The Open Geospatial Consortium (OGC) was founded in 1994 to make

geographic information an integral part of the world’s information infrastructure. OGC

members – technology providers and technology users – collaboratively develop open interface

standards and associated encoding standards, and also best practices, that enable developers to

create information systems that can easily exchange “geospatial” information and instructions

with other information systems. Requirements range from complex scheduling and control of

Earth observation satellites to displaying simple map images on the Web and encoding location

in just a few bytes for geo-tagging and messaging. A look at the OGC Domain Working Groups

(http://www.opengeospatial.org/projects/groups/wg) shows the wide scope of current activity

in the OGC.

OGC(R) standards are technical documents that detail interfaces or encodings.

Software developers use these documents to build open interfaces and encodings into their

products and services. These standards are the main "products" of the Open Geospatial

Consortium and have been developed by the membership to address specific interoperability

challenges. Ideally, when OGC standards are implemented in products or online services by

two different software engineers working independently, the resulting components plug and

play, that is, they work together without further debugging.

OGC Web Services (OWS) are OGC standards created for use in World Wide Web

applications. Any Schemas (xsd, xslt, etc.) that support an approved (that is, approved by the

OGC membership) OGC standard can be found in the official OGC Schema Repository.

All adopted OGC Implementation Standards can be found in this list: OGC Implementation

Standards List. Many specifications are in the process of being advanced toward adoption by

the OGC membership as official OGC standards.

OpenGIS is the activity pursued by the OGC to form bases of the interoperability

between GIS services such as mapping services, data services, and portrayal services. OpenGIS

tries to achieve its interoperability aims by providing a rich suite of open interface and

implementation specifications. Some of these specifications are used in our GIS project and

explained in detail but the other approved specifications will be mentioned in the chapter

roughly. These interface specifications will enable GIS developers to create interoperable

components.

OGC OpenGIS Specifications enables you to get, mix and match your GIS services

from multiple sources over the web. These sources might be from different vendors and

different geographic areas but they must be implemented according to approved OGC

OpenGIS specifications. The approved OGC specifications are displayed in the Figure.

OGC Abstract Specification

The OGC Technical Committee (TC) has developed an architecture in support of its vision of

geospatial technology and data interoperability called the OGC Abstract Specification. The

Abstract Specification provides the conceptual foundation for most OGC standard

development activities. OGC standards are built and referenced against the Abstract

Specification, thus enabling interoperability between different brands and different kinds of

spatial processing systems. The Abstract Specification provides a reference model for the

development of OGC standards.

OGC Reference Model (ORM)

The OGC Reference Model (ORM) provides a framework for the ongoing work of the OGC.

The ORM describes the OGC Standards Baseline (SB) focusing on the relationships between

the OGC standards. The OGC SB consists of the approved OGC Abstract Specification and

OGC standards as well as OGC Best Practices documents.

Best Practices Documents

Documents containing discussion of best practices related to the use and/or implementation

of an adopted OGC document and for release to the public. Best Practices Documents are an

official position of the OGC and thus represent an endorsement of the content of the paper.

Schemas for some of these documents can be found at the Best Practices Schema Repository.

Engineering Reports

Engineering Reports (ERs) are a primary output of OGC Interoperability Program Initiatives

(testbeds, pilot projects and interoperability experiments).

ERs can address topics as needed by an initiative including:

Requirements

Specifications which may become the basis for development of an OGC Standard.

Testing Approach and Results (This includes experiment results)

Compliance Test Design

Next Steps and Lessons Learned

ERs represent consensus positions of the initiative participants and sponsors only. ERs

become a publicly available document by consensus motion of the Specification

Program. An ER does not represent the official position of the OGC nor of the OGC

Technical Committee.

Discussion Papers

Documents that present technology issues being considered in the Working Groups of the

Open Geospatial Consortium Technical Committee. Their purpose is to create discussion in

the geospatial information industry on a specific topic. Discussion papers are not intended to

be targets of acquisition descriptions. These papers do not represent the official position of

the Open Geospatial Consortium nor of the OGC Technical Committee. Schemas for some of

these documents can be found at the Discussion Paper Schema Repository.

White Papers

White papers present technology issues of interest to members of the Open Geospatial

Consortium. They are voted on by the membership to be approved for public release, but they

do not represent official positions of the Open Geospatial Consortium nor of the OGC

Technical Committee.

Change Requests

Change Requests are submitted by anyone for any existing or proposed OGC Standard.

Technical Committee Policy Directives

The standards and documents are governed by the Technical Committee Policy Directives.

Standards:

Implementation Standards are different from the Abstract Specification. They are

written for a more technical audience and detail the interface structure between software

components. An interface specification is considered to be at the implementation level of

detail if, when implemented by two different software engineers in ignorance of each other,

the resulting components plug and play with each other at that interface.

Most of the OGC standards depend on a generalized architecture captured in a set of

documents collectively called the Abstract Specification, which describes a basic data model

for representing geographic features. Atop the Abstract Specification members have

developed and continue to develop a growing number of specifications, or standards to serve

specific needs for interoperable location and geospatial technology, including GIS.

More information: http://www.opengeospatial.org/standards

The OGC Baseline and OGC Reference Model

The OGC Standards Baseline consists of the OGC standards

(http://www.opengeospatial.org/standards) for interfaces, encodings, profiles, application

schemas, and best practice documents. The OGC Reference Model (ORM)

(http://www.opengeospatial.org/standards/orm) describes these standards and the

relationships between them and related ISO standards. The ORM provides an overview of

OGC standards and serves as a useful resource for defining architectures for specific

applications.

In developing a Web services application using OGC standards (and in learning about the

relationships between OGC standards) it helps to think of publish, find and bind as the key

functions for applications in a Web services environment.

Publish: Resource providers advertise their resources.

Find: End users and their applications can discover resources that they need at run-

time.

Bind: End users and their applications can access and exercise resources at run-time.

Most of the OGC standards developed in recent years are standards for the Web services

environment, and these standards are collectively referred to as OGC Web Services (OWS).

The figure below provides a general architectural schema for OGC Web Services. This

schema identifies the generic classes of services that participate in various geoprocessing and

location activities.

Relationship between clients/servers and OGC protocols

The OGC standards baseline comprises more than 30 standards, including:

CSW - Catalog Service for the Web: access to catalog information

GML - Geography Mark-up Language:

XML- format for geographical information

GeoXACML - Geospatial eXtensible Access Control Mark-up Language (as of

2009 in the process of standardization)

KML - Keyhole Mark-up Language:

XML-based language schema for expressing geographic annotation and visualization

on existing (or future) Web-based, two-dimensional maps and three-dimensional

Earth browsers

Observations and Measurements

OGC Reference Model - a complete set of reference models

OWS - OGC Web Service Common

SOS - Sensor Observation Service

SPS - Sensor Planning Service

SensorML - Sensor Model Language

SFS - Simple Features - SQL

Styled Layer Descriptor (SLD)

WCS - Web Coverage Service: provides access, subsetting, and processing

on coverage objects

WCPS - Web Coverage Processing Service: provides a raster query language for ad-

hoc processing and filtering on raster coverages

WFS - Web Feature Service: for retrieving or altering feature descriptions

WMS - Web Map Service(WMS): provides map images

WMTS - Web Map Tile Service: provides map image tiles

WPS - Web Processing Service: remote processing service

GeoSPARQL - Geographic SPARQL Protocol and RDF Query Language:

representation and querying of geospatial data for the Semantic Web

The design of standards were originally built on the HTTP web services paradigm for

message-based interactions in web-based systems, but meanwhile has been extended with a

common approach for SOAP protocol and WSDL bindings. Considerable progress has been

made in defining Representational State Transfer (REST) web services.

Specification Profiles

The following documents are profiles of other OpenGIS† Specifications. Although they

appear on the respective pages of their "parent" specifications, this view is provided for

quickly accessing specific profiles. To access the parent specification simply use the link

provided below the profile description.

The GML standard declares a large number of XML elements and attributes meant to

support a wide variety of capabilities. For example, the GML standard can be used to

encode dynamic features, spatial and temporal topology, complex geometric property

types and coverages. With such a wide scope, interoperability can only be achieved

by defining profiles of GML that deal with a restricted subset of GML capabilities.

Such profiles limit the number of GML object types that can appear in compliant

schemas and consequently are easier to process.

Document specifies a GML profile for encoding definitions of commonly-used

Coordinate Reference Systems (CRSs) plus related coordinate Conversions. This

XML schema is a profile of the OGC Geography Mark-up Language (GML) version

3.1.1, using the separately specified “GML 3.1.1 CRS Support profile”. This profile

supports XML encoding of definitions of geographic, projected, vertical, and

composite CRSs, plus definitions of coordinate Conversions for projected CRSs.

Document specifies a GML profile for supporting multiple profiles for XML

encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate

Operations. This XML schema is a profile of the OGC Geography Mark-up Language

(GML) version 3.1.1. This profile supports almost all the XML elements, attributes,

and types used by CRS-related GML object elements.

Document specifies a GML profile for encoding definitions of grid coverage

(including image) Coordinate Reference Systems (CRSs) plus related coordinate

Transformations. This XML schema is a profile of the OGC Geography Markup

Language (GML) version 3.1.1, using the separately specified “GML 3.1.1 common

CRSs profile”. This profile supports XML encoding of definitions of Image and

Derived (grid) CRSs, and definitions of coordinate Transformations for

georeferencing images.

Document specifies a GML profile for XML encoding of simple dictionaries. This

XML schema is a profile of the OGC Geography Mark-up Language (GML) version

3.1.1. These “simple” dictionaries do not allow including remote resources within the

dictionary.

References:

[1] http://live.osgeo.org/en/standards/standards.html

[2] http://www.opengeospatial.org/standards

[3] Establishment of “NATIONAL GIS” under Indian National GIS Organisation (ingo) -

government of India planning commission national gis interim core group June, 2011

[4] National Spatial Data Infrastructure (NSDI) - Department of Science and Technology

(2009).