Need Assessment Report
KSSDI – Geo Portal, System Requirement Specification
Project Investigators
H Hemanth Kumar, S N Sondur and U T Vijay
2009
Turn Key Solution Provider: Navayuga Spatial Technologies (P) limited.
Karnataka State Council for Science and Technology
Indian Institute of Science campus, Bengaluru
Table of Contents Definition, Acronyms, Abbreviations........................................................................................................ 4
References .............................................................................................................................................. 6
Section 1: Introduction ............................................................................................................................ 7
Section 2.0: Core Components of the KSSDI Geo Portal and Clearinghouse .............................................. 8
Section 2.1: Logical Overview of the KSSDI System: .......................................................................... 8
Section 2.2: Description of KSSDI Data Store: ................................................................................. 10
Section 2.3: Approach towards Establishing the KSSDI system ....................................................... 11
Section 2.3.1: Establishment of Servers and Installation of Software for setting up a Geo-Portal
Clearing house. .............................................................................................................................. 12
Section 2.3.2: Development of Geo Portal...................................................................................... 15
Section 2.3.3: Operationalisation of Geo Portal and Training to Identified KSCST staff and Line
Department Executives .................................................................................................................. 19
Section 2.3.4: Maintenance for 3 Years on KSSDI Geo Portal Software and Hardware .................... 20
Section 3: Needs of the KSSDI Geo-Portal .............................................................................................. 21
Section 4: Potential Applications of KSSDI Geo-Portal ............................................................................ 25
Section 5: Intended Functional Components of KSSDI Geo-Portal .......................................................... 27
Section 6: Intended Users of KSSDI Geo-Portal ...................................................................................... 33
Section 6.1: General User .................................................................................................................. 33
Section 6.2: Data Provider ................................................................................................................. 34
Section 6.2.1: Data Provider ........................................................................................................... 34
Section 6.2.2: Data Manager (with respect to department) ............................................................ 35
Section 6.3: Administrator ................................................................................................................. 35
Section 6.3.1: System Administrator .............................................................................................. 35
Section 6.3.2: Super Administrator................................................................................................. 36
Section 6.3.3: Data Manager .......................................................................................................... 36
Section 7: Non Functional Requirements of KSSDI Geo-Portal ................................................................ 38
Section 8: Necessary Data & Resources of KSSDI Geo-Portal .................................................................. 39
Data Requirements for Geo-Portal (Master Data List) ........................................................................ 39
Data Requirements for applications ................................................................................................... 42
ANNEXURES .......................................................................................................................................... 43
Annexure 1: Data Migration / Upload Steps........................................................................................ 44
1. Centralized Hosting: ............................................................................................................... 44
2. Decentralised Hosting: ........................................................................................................... 48
Annexure 2: Steps to Publish Datasets as Map service: ....................................................................... 49
Annexure 3: KSSDI Participating Agencies: .......................................................................................... 51
Annexure 4: Reference High Level KSSDI Use Cases ............................................................................ 55
Annexure 5: Reference Lower KSSDI Use Cases .................................................................................. 59
Annexure 6: Detailed Department Wise Requirements ....................................................................... 70
Annexure 7: Roles of KSCST: ............................................................................................................... 73
Annexure 8: Data Management: ......................................................................................................... 75
Annexure 9: Version Control, Back Up and Storage: ........................................................................ 78
Version Control: ................................................................................................................................ 78
Backup and Storage: .......................................................................................................................... 81
Annexure 10: Performance & Benchmarks: ...................................................................................... 83
Benchmarks ....................................................................................................................................... 83
Performance ...................................................................................................................................... 84
Definition, Acronyms, Abbreviations Any definitions, acronyms and abbreviations specific to this document are outlined in this section:
KSSDI Karnataka State Spatial Data Infrastructure
KSCST Karnataka State Council for Science & Technology
NRDMS Natural Resources Data Management System
SOI Survey of India
NST Navayuga Spatial Technologies Pvt. Ltd.
RFP Request for Proposal
NSDI National Spatial Data Infrastructure
SDI Spatial Data Infrastructure
UML Unified Modelling Language
GIS Geographical Information System
SDO Spatial Data Object
ISO International Standard Organization
OGC Open Geospatial Consortium
WMS Web Mapping Service
WFS Web Feature Service
WCS Web Coverage Service
WRS Web Registry Service
CSW Catalogue Service on Web
QA/QC Quality Analysis/ Quality Checking
COTS Commercial Off The Self
ESRI Environmental Systems Research Institute, Inc.
GML Geographic Mark-up Language
JSR Java Specification Requests
FTP File Transfer Protocol
PDA Personal Digital Assistant
HDD Hard Disc Drive
PDF Portable Document Format
LU/LC Land Use / Land Cover
ZPC Zilla Panchayath Constituency
TPC Taluk Panchayath Constituency
GPJ Gram Panchayath Jurisdiction
ULB Urban Local Bodies
LAC Legislative Assembly Constituency
PC Parliamentary Constituency
PHC Primary Health Centre
CHC Community Health Centre
SHC Sub Health Centre
HQ Head Quarter
M.I. Minor Irrigation
SC Schedule Cast
ST Schedule Tribe
RDBMS Relational Database Management System
PK Primary Key
FK Foreign Key
ER Entity Relation
ORM Object Relational Model
References
“Revised Request for Proposal (RFP) for Setting up Geo Portal and Clearing House” PDF document released on November 2008.
NST Technical Proposal document submitted for the revised RFP in December 2008.
NRDMS-queries-user needs-applications.doc
DoE, User Need Assessment and Master Data List
Health Services, User Need Assessment and Master Data List
PDS, User Need Assessment and Master Data List
National Map Policy 2005 from Survey of India
NSDI Metadata Standards 2.0
Samaj Vignan Shod Patrika Uttarakhand-1 (2007), Half yearly research journal of social sciences
Section 1: Introduction
Under Department of Science and Technology’s Natural Resource Data Management System (NRDMS) program, Karnataka State Council of Science and Technology (KSCST) envision establishing a Karnataka State level Spatial Data Infrastructure called KSSDI. KSSDI will be a centralized single window access of all the geospatial data available across the Karnataka state as a decision support system to support various local level planning within the Karnataka State government departments and affiliated agencies. KSCST has developed district level GIS databases to support the process of local level planning at the level of district, taluk and village. The geospatial datasets generated, maintained and provided by various concerned state level governments, academics, private or civil society organization of Karnataka will also be made part of the project data clearing house. The Initial use of the geo-portal and the clearinghouse will primarily be on an experimental basis giving access to spatial data and its metadata sets held under KSCST at different District database centers setup under NRDMS. The data will be initially be accessed by the concerned staff based at the districts from the NRDMS centers or the Line Departments. The services will eventually be extended to beneficiaries of various developmental programmes or schemes and general public under the regulations of the Government of India. Other organizations and agencies in due course will be invited to share their information by publishing the details in the geo-portal & clearinghouse. The purpose of this document is to describe the software requirements for the KSSDI system that
include setting up a Data Clearinghouse and an OGC/ISO Compliance Geo Portal.
The below sections will describe in detail about the components of the KSSDI Geo Portal and the
Clearinghouse.
Section 2.0: Core Components of the KSSDI Geo Portal and Clearinghouse
Section 2.1: Logical Overview of the KSSDI System:
KSSDI system information is separated into Front End and Back Office:
The Front End users and components are:
General Users: Members of general public that access the KSSDI Geo Portal using the web pages
through the internet:
Data Maintainer/ Manager: They are the representatives from government departments, and have
the privilege to update data, metadata and service catalogue specific to their department only.
Registration & Login System: Request registration details from new users and login interface for
existing users.
Geo Portal: This is the OGC Compliance GIS system that provide the ability to browse the map layers
and legends, Search and Query, Catalogue services, Application Queries, Metadata view, Download
and Upload, Provision for product catalogue and payment my cart.
The Back End users and components are:
KSSDI Administrator: KSCST authorised Individuals for managing the operations of the KSSDI system
that includes – users, groups, roles, privileges, maintaining and managing the data or metadata, and
managing application resources.
Security Management System: The module that keep tracks of the user information, their roles and
access privileges. Only the administrator of the system has access to manage this module.
Application Resource Management: An administrative component to restrict data access and
application functions like disabling request type or output formats, hiding layers or columns, and
restrict view by scale or spatial area credentials.
Data Upload: Includes tools for migration of existing spatial data into Oracle spatial SDO format or
Geo Raster format, and attributes dataset into tables. Also helps in providing spatial indexing for
optimised access.
Styling: This is an OGC complaint style editor to set or change spatial layer style, colour, label and
legend representation on the map. Also provide ability to set or change north arrow, scale, grid,
units, border, and title.
Figure 1: KSSDI System Overview – Data Flow Diagram
Section 2.2: Description of KSSDI Data Store:
Following data stores are required to support the functions of the KSSDI Geo Portal System:
Data Dictionary: Includes Real world object description, definition, source, typology, etc.
information as a catalogue.
Geospatial datasets
o Geographic Base map Information (Administrative Boundaries )
4 Divisions boundary
29 Districts boundary
49 Subdivisions boundary
176 Taluks Boundary
747 Hoblies/revenue circles boundary
Zilla Panchayath Constituency boundaries
Taluk Panchayath Constituency boundaries
5653 Gram Panchayath Jurisdiction boundaries
29406 Villages boundary
(Source: KSCST, Revenue boundaries statistics http://karanatakforest.gov.in, RDPR Govt. of
Karnataka web site & state profile-Karnataka document in http://www.panchayat.nic.in)
o Thematic Maps spatial datasets
Point themes (e.g. settlements, HQ, etc)
Linear themes (Roads, Drainage, etc)
Polygon themes (LULC, Soil, Slope, watershed, etc)
Attribute datasets
o Census details
o Settlements details
o Infrastructure facilities details
o Health Centre details
o Education details
Raster maps repository
Authentication & Authorization Information
Service Registry Information
Product catalogue information
Topographic sheet information
Section 2.3: Approach towards Establishing the KSSDI system
The approach towards establishing the KSSDI system (Geo Portal and Clearinghouse) involves four main
steps or phases:
1. Establishment of Servers and Installation of Software, and setting up a clearinghouse.
2. Development of the Geo Portal
3. Operationalisation of Geo Portal and Training to identified KSCST staff and Line Department
Executives.
4. Maintenance for 3 Years on KSSDI Geo Portal Software.
Figure 2: KSSDI Geo Portal and Clearinghouse.
Section 2.3.1: Establishment of Servers and Installation of Software for setting up a Geo-Portal
Clearing house.
The establishment of the servers, installation of the software and setting up of a Clearing House will be
based on the discussions and the Infrastructure Readiness at KSCST/KSSDI. The hardware & software
that is to be established at the clearing house are as below:
The Hardware Components:
S No. Component Make Quantity
1 Blade Servers Chassis IBM Blade Server HS21 1
2 Application & Database servers IBM Blade server HS21 2
3 Web, Security and Backup Servers IBM Blade server HS21 3
4 SAS Storage DS3200 storage solution 1
5 Backup Device -Tape Library TS3100 tape library 1
6 Rack and its accessories IBM Netbay S2 42U 1
7 Internet Firewall CISCO ASA 5520 1
8 Application and Database Zone Firewall
CISCO ASA 5550 1
9 Internet Router CISCO 3845 1
10 Application and Database Zone Gigabit switch
CISCO 4948 – 10 GE 2
11 DMZ switch Catalyst 2960 G 1
12 UPS 30 KVA APC Smart UPS – VT with 2 hours backup
1
The Software Components:
S No. Component Make Quantity
1 Backup Software IBM Tivoli Storage manager 1
2 SNMP CISCO Works LAN Management solution Software 1
3 RDBMS ORACLE 11 g – Enterprise Edition with Spatial Option
2
4 OGC Software REDSPIDER / Apollo Suite Software including Apollo server, Image manager – catalog and Application solution kit – deployment license
1
5 Operating System Microsoft Windows 2003 / 2008 server standard edition
5
Figure 3: KSSDI System Infrastructure
The above said Hardware and Software Components comprise the KSSDI Geo-Portal Clearinghouse.
Approach for setting up the geo-portal clearinghouse:
KSSDI readiness of the Infrastructure.
Getting the clearance from KSSDI/KSCST for procurement of the Hardware.
Procurement of the Hardware from the desired vendors.
Warranty period initiation for the Hardware.
Setting up of network.
Installation of the respective software on the desired servers.
Data Migration from Other datasets to Oracle database on the identified Database Server
Figure 4: Approach for setting up the geo-portal clearinghouse.
Note: The Navayuga Team in co-ordination with the KSCST Team will place the order for the Hardware
after the KSSDI Readiness of the infrastructure. The commencement of the Warranty for the Hardware
will start from the day the Order is delivered for the customer (KSCST).
Section 2.3.2: Development of Geo Portal
It’s an enterprise level geo spatial web based system that provides access to spatial data directory
through a series of geographic service interfaces. Based on Service Oriented Architecture Geo Portal
provides the ability to link, communicate or collaborate with other portals through similar interfaces. It
has the ability to publish data on internet and provide catalogue of existing geo services.
Software Development & Deployment Environment for the Geo Portal is Java open platform based:
JDK 1.6 as the Java Open platform system environment
JPortal for implementation of Portlet as per JSR 168 specification
JAAS, LDAP-OpenDS 1.2.0 for establishing Security /Identity System
JBoss Application Server 4.2.3 as Application Server environment
Spring Framework 2.5 as persistent layer
Hibernate 3.0 as Data connectivity layer
JSF 1.2 as presentation layer
Rich Faces 3.2.2 as dynamic content for presentation
Section 2.3.2.1: Objectives for KSSDI Geo Portal
Karnataka State Spatial Data Infrastructure (KSSDI) project is intended to develop the KSSDI system
providing following benefits:
The proposed system will be a Web Based GIS - Solution to serve the need of the Users spread over
Internet.
The system will publish the geospatial datasets that exists with KSCST and other data providers in a
viewable format over the web browser to its authorized users.
The system will allow the end users to view and query the spatial data on the Map.
Geo-spatial data sets acquired, and maintained by various state-government departments/ NRDMS
centres/ Private/ Academic/ or Civil Society Organisations of Karnataka will be made part of the data
clearinghouse.
The initial use of the Geo-portal and the data clearinghouse will primarily be on an experimental
basis for providing access to spatial data and metadata sets held by KSCST at different District
Database Centres set up under NRDMS.
The data/metadata/ services will initially be accessed by the concerned staff based at the districts
from the NRDMS Centres or the Line Departments.
These services will eventually be extended to beneficiaries of various developmental
schemes/programmes and the general public with certain restrictions under provisions of the
prevailing rules and regulations of the Government of India
Other organisations/ agencies will share their data/ metadata sets held or provided by them by
publishing their details in the Geo-portal /Clearinghouse.
The local level planning is in following areas of development process:
o Natural resources o Demography o Agro economy o Socio Economy and o Infrastructure Facilities
Section 2.3.2.2: Scope of KSSDI Project
In Project Scope:
Following items is considered part of the project scope for the NST team:
Developing and SDI framework with OGC / ISO Compliance Services
Preparing the Project Need Assessment Report with the assistance from KSCST team
A real world object catalogue, conceptual and physical data model demonstrating semantic
interoperability between various spatial data hierarchy, scale, and nodes of data providing agencies.
UML based Data model and Architecture design diagram with documentation
Establishing of centralised Geospatial data Clearing house containing data (spatial, attributes) and
metadata sets for NRDMS district centres and line departments as provided by KSCST, with the
ability to remotely update.
Metadata to be as per the ISO19115 standards.
Developing and deploying Geo-Portal on the accepted (ERDAS IONIC/APOLLO Server) SDI framework
to view the clearing house data in OGC complaint service architecture with key services for
registration, publication, upload and update of metadata.
Customised software code for the Geo-Portal with necessary documentation and operation
provision for services – WMS, WFS, WCS, WRS, CSW conforming to OGC standards
Provide multilingual support to view in English and Kannada Language as well.
Secure system to handle data, user identity and network
System testing and User Acceptance testing of the integrated framework
Operationalisation of the complete system
Provisioning for payment gateway
Training KSCST identified staff on the data Clearinghouse and Geo-Portal deployment , execution
and maintenance
Three years comprehensive maintenance of an approved system
Out of Project Scope:
Following are considered out of purview of the NST team during the project life time:
Base data generation and survey
Data correction and/or validation
Identification of spatial data stakeholders
Identification of users, user groups
Collecting spatial and attributes information from each individual participating line departments
Access spatial data sets through Geo portal from a PDA or mobile phones using standard plug-ins
Establishing a payment gateway
Identification of participants for training
Training on basic concepts of GIS and its usage.
On completion of the project, running and maintaining of the KSSDI setup will be done by KSCST/State
Government.
Section 2.3.2.3: Approach to the Geo Portal Development
The Approach to the Geo Portal development involves the following:
Identifying the functional requirements (Includes the Geo Portal + Application requirements).
Identifying the existing datasets at KSCST of various Line Departments.
Identification of the Intended users and finalize the user roles and access modules.
Preparation of Need Assessment Report (Which Includes the Functional + Data + User
Requirements).
Review of Need Assessment Report and Approval.
Preparation of the Real World Object Catalogue (Which includes the Datasets based on the
Hierarchy and Classification).
Review the Real World Object Catalogue and Approval.
Preparation of the Conceptual Data Model (Which includes the ER Diagrams & ISO 19109
representation of the Datasets of in the Real World Object Catalogue)
Review of the Conceptual Data Model and Approval.
Development of the Geo Portal.
Figure 5: Approach for KSSDI Geo Portal development
Section 2.3.3: Operationalisation of Geo Portal and Training to Identified KSCST staff and Line
Department Executives
Operationalisation involves the deployment of the developed Geo Portal Application Software, which
includes the Security Module on the Web Server and KSSDI Geo Portal and Application Suite on the
Application Server. After the operationalisation a User Acceptance Test will be done to ensure the
functionalities of the Portal. The deployed applications will be hosted on the Internet and generic users
will be created. Training will also be conducted to Identified executives from the various line
departments on Portal usage and respective data management of their Department using the Portal.
Approach to the Operationalisation and Training is as follows:
Deployment of the Geo Portal on respective Servers.
User Acceptance test will be conducted to ensure the ease of functionality of the portal.
Hosting Geo Portal Application over Internet.
Training to the KSCST Staff in portal Administration.
Training to the Line Department Executives on usage of Portal.
Figure 6: Approach for KSSDI Geo Portal Operationalisation
Section 2.3.4: Maintenance for 3 Years on KSSDI Geo Portal Software and Hardware
With the sign off on operationalisation and successful completion of training the KSSDI setup is
handover to the KSCST for running and maintaining.
From the date of handover, NST team would be engaged for duration of three years for the following
support activities:
Software troubleshooting
Application issues resolution and patch update
Software upgrade
Providing monthly maintenance Report
Geo Portal & Clearinghouse operational checklist
Section 3: Needs of the KSSDI Geo-Portal
Based on the type of users and the operations perceived under each type, the needs of the KSSDI
system can be classified into following list:
No. Needs of the KSSDI Geo Portal Intended Functional Components User
01 Data Preparation Data Clearinghouse Module Data Manager/ Data Provider
Datasets Identification, Classification & Hierarchy
Real World Object Catalogue
Data Dictionary – definition and content description of tables and fields
Real World Object Catalogue
Database Schema ER Model & UML Model
02 Data Storage Data Clearinghouse Module (Oracle 11g Spatial Database)
Administrator
Loading all Administrative boundaries: Division, District, Subdivision, Taluk & Village data sets
Upload Tool
Loading all Thematic(Point, Linear & Polygon Features) datasets
Upload Tool
Live datasets that resides at respective line department’s remote locations made available as Registered Map Services
Registry Services
Data from remote locations made available to the central DB system thru FTP upload.
Manual QA/QC & Upload Tool
Upload onto the Centralized system, data sent thru physical storage devices like CD, DVD, Pen Drive, & HDD.
Manual QA/QC & Upload Tool
Tools to Upload Data (Migration) Easy Loader: loading spatial data in TAB, Shape, or E00 format using Oracle DB connection into SDO format and attribute data using JDBC connectivity. SQL Loader: Loading attributes data GeoRaster Loader: loading raster / images. SHPTOSDO: loading SHP to Oracle SDO format IONIC/APOLLO batch tool – for GML To Oracle SDO
Data Indexing RTree Indexes / Field Indexing
Associate Metadata (ISO 19115/NSD 2.0) Manage Metadata UI
Connection Pooling for concurrent access Oracle Connection Pooling
03 Data Publishing &Viewing Geo Portal Module
Publish Data Provider/
Data Manager
Make Data layers/tables as OGC complaint map services (WMS, WFS…)
Publishing
Registering the services and metadata Harvesting
Grouping/indexing Registered Services by AOI, keywords, place name, service type, scale, mapsheet
Catalogue Services
Selecting Service from Catalogue and Adding on Map
Map Viewer
Performing Map operations on Service layers Map Navigation tools
Performing attributes & spatial queries on Service layers
Search & Query
Editing Services metadata Manage Metadata
Deleting Services from Map View Layer Display
Local Data upload as GML / SHP Load
Map Viewing Geo Portal Module General User/ Data Provider
Viewing map as layer over a browser Layer Display
View vector map as WMS / WFS layer Publishing
View Raster map as WMS / WCS layer Publishing
View Map layers by Alias names Styling
View Map Legend by Alias names Styling
View map by Scale Styling
Hierarchical display of Administrative Boundaries layers
Layer Display
View Map by SOI Topographic sheet Search
View map by Line Departments/data providing agencies
Search
View X.Y Coordinates of cursor location Map Viewer
Map Navigation Toolbar options – Zoom in, Zoom out, Pan Grab, Pan Directions, Identify, Measure, Previous view, Full View, Zoom Rectangle
Map Navigation tools
Feature Identify Map Viewer
Switch On/Off Layers Layer Display
Select a layer Layer Display
View metadata of the layer Layer Display
Styling the layer for view Styling
Overlay Thematic layers on Administrative boundaries
Overlay Point/ Linear features on Administrative boundaries
04 Data Querying Geo Portal Module General User/ Data Provider
Query by Bounding Box Simple Query
Query by Constraint Attribute, Operator ((<,>,=,<=, >=, LIKE, AND,OR, etc) and Value
Simple Query
Query by Spatial Filter(INTERSECT, WITHIN, Complex Query
CONTAIN, etc)
Query by Multiple Join (Attributes Constraint + Spatial filter)
Complex Query
Query Single layer Simple Query
Query Multiple Layers Complex Query
Search Geo Portal Module General User/ Data Provider
Search by map service type Discover
Search by Keyword Discover
Search by Services Discover
Search by Administrative boundaries Search
Search by Scale Search
Search by Topo sheet Search
Search by Agency / Line Dept. Search
05 Dept. Specific Applications Predefined Queries Module General User/ Data provider/ Data Manager
06 Data Output /Results Geo Portal Module General User/ Data Provider
Online map viewing over a browser Map Viewer
Printing with customized layouts Print
As OGC complaint Map services Publishing
Downloading as GML or Shape files Save
Saving a map as an image- GIF, JPG, BMP, TIFF, etc.
Save
Filtered query on features and save as GML or shape
Simple Query
Export Data / metadata to GML, SHP, Excel, etc Save
Vector Output as SVG, KML Save
07 Data Editing Editing Data Manager/ Administrator
Feature Attribute Editing and update Attribute Edit UI Form
Point Feature geometry editing and update WFS-Transactional
Line Feature geometry editing and update WFS-Transactional
Polygon feature geometry editing and update WFS-Transactional
08 Security/Identity Management Administration Module Administrator
Manage Users: Create, Search User, Set User to Group
Manage Users
Manage Groups: Create, Update or Remove Group
Manage Groups
Add or Remove User(s) to/from a Group Manage Groups
Set Application Resources to the Group Manage Groups
Set/unset Roles and Privileges to the Groups Manage Groups
Manage Resources: Add/ Update or Remove Manage Resources
Resources
Add/Update/Remove methods form the Resources
Manage Resources
Manage Roles: Add/update/ Remove Roles Manage Roles
Set/unset Resources and operations for each Roles
Manage Roles
Manage Layers: New Data as WMS, WFS, WCS, update or Remove
Manage Layers
Manager Data: Agency/ Scale/ Area/ Data fields based data protection and control
Manager Data
Manage Metadata: Add/Update/Remove Metadata
Manage Metadata
09 Generic Needs: Web Portal All Users
KSSDI Web Site URL for access over internet Hosting
Default/Home Page for KSSDI Geo Portal Home page
Registration Page for the General User Security
Login Page for KSSDI Geo Portal Security
Change Password My Account
Request on forgot Password My Account
Update Profile My Account
View Data Dictionary Object Catalogue
Support Portal Services JBOSS - JPortal 1.0
Support Portrayal Services OGC -SLD
Support Catalogue Services OGC –CSW
Support Single Sign On J2EE - LDAP/JAAS
Support Portlet JBOSS – JPortal 1.0
Form based input /update of metadata ISO – 19115/19119
GML 2/3/SF/Shape File format OGC-WFS, GML SF
10 Others All Users
User Request to provide information on the map
Manage Requests
Respond to User request / Notify Manage Requests
Status of Requests Manage Requests
Intimate special user of registration – login/ password
Automated emailing
Data selection for purchase MyCart / Payment Gateway
Transaction Details Product Catalogue
User Profile View, update My Account
11 Deployment & Training NST/KSCST
Geo Portal & Data Services Testing
User Acceptance Testing
Deployment & Operationalising
Training Staffs
Maintenance Support
Section 4: Potential Applications of KSSDI Geo-Portal
An indicative list of typical user requirements for applications that can be made into predefined queries
as part of need assessment understanding are:
Department Application Requirement Application Query Data Required
Department of Education (Akshaya Yojana Programme)
Opening of new Primary School
Distance of a school from a village doesn’t exceed 1.5 kms
scale 1:50K: Village point, School point data
Scale <1:25K: Village Polygon, School polygon/point data
(District Primary Education Programme)
Opening of new Primary School
1. Population exceed 300 2. Village with Adult Education
Centre
Village level population/census data with:
Village Name, Village Panchayath Population,
Existing school, Existing Adult Education centre
(Akshaya Yojana Programme)
Construction of new school rooms
Select Schools for which additional rooms were constructed Population is in excess of 600
Number of students in excess
Village name Village population School Name
Number of students Number of Drop outs current year Number of School Rooms
Number of Rooms added last 3 year
(Akshaya Yojana Programme)
Repair to school rooms Select Schools for which rooms
were repaired Village census / settlement data Rooms Repaired attribute information Date of repair information
Location of School Select School in Private land Select School in Govt. Land Select School in Adult Education
Centre
Health Services
(Malaria Eradication Programme)
1. Identification of High Risk Areas
Select Districts prone to Malaria high risk areas
Data of Highly Affected Malaria Areas Name of the village,
Name of the Panchayath, Name of the PHC, Criteria,
Criteria Value
Health & Family Welfare Dept.
Villages with Primary health centre
Select Villages within a given Taluk that has PHC
Taluk boundary dataset with Village Census data with PHC
Watershed Development Dept.
Constituency wise watershed 1000 ha each
Select Constituency within a district that has watershed area 1000ha
LAC boundary dataset with District name with Watershed map with type delineation
Fishery Farmer Development Agency(FFDA)
Taluk wise location of M.I tanks having fishing activities
Select Taluk with MI Tank that has fishing activities
Taluk dataset with MI tank info at Taluk level Fishing activity attribute status
Minor Irrigation Dept.
Minor irrigation tank taluk wise
Select Taluk with Minor irrigation tank
Taluk dataset with Minor Irrigation tank details
Education Dept/RDPR
Schools with implementation of Rain water harvesting method
Select Village with schools that has Rain water harvesting
Village settlement dataset with School information Rain water harvesting status
Panchayath Raj Engineering Dept.
Schools with drinking water and toilet facilities
Select Village with schools that has drinking water and toilet facilities
Village settlement dataset with School information Drinking water & Toilet facilities availability status
Panchayath Raj Engineering Dept.
Village with fluoride distribution
Select fluoride distribution map at village level
Village or Taluk datasets with OBW Fluoride collection station location Fluoride measure details
District Adult Education Office
Village with adult education
Select Villages with Adult Education facility available
Village dataset with and without Adult Education details
District Adult Education Office
Village with continuing education centre
Select Villages with Continuing Education Centres (CEC) facility available
Village dataset with and without CEC attribute information
Dept. of Animal Husbandry & Veterinary Services
Village with veterinary facility
Select villages with Veterinary facility available
Village dataset with and without Veterinary Facility attribute information
Dept. of Animal Husbandry & Veterinary Services
Village with live stock distribution
Select Villages with liver stock distribution available
Village dataset with and without live stock attribute information
Zilla Panchayath Office
SC/ST percentage distribution taluk wise
Select Taluk wise SC/ST percentage Distribution
Village level census dataset with SC/ST population distribution attributes information
Talluk Panchayath
Village with population greater than 600
Select villages with population > 600
Village level census dataset with total population attributes
Panchayath Raj Engineering Dept.
Village with number of borewells
Select villages that has borewells and the count
Village dataset with and without borewell count attribute information
Health & Family Welfare Dept.
Village with Primary health centre
Select villages with PHC facility available
Village dataset with and without PHC attribute information
Health & Family Welfare Dept.
Village with Community Health
Select village with CH facility available
Village dataset with and without CH facility attribute information
Health & Family Welfare Dept.
8 kms Buffer around the village locations with PHCs
Select villages with PHCs with 8 Kms Buffer polygon
Village dataset with and without PHCs information
Health & Family Welfare Dept.
Villages without PHCs Select villages having PHCs facility Village dataset with and without PHCs information
Health & Family Welfare Dept.
12 kms buffer around village locations with CHCs
Select villages having CHCs with 12 kms buffer polygon
Village dataset with and without CHCs facility attribute information
Health & Family Welfare Dept.
Village location with population 3000 and with SHC
Select villages with population >= 3000 and SHC facility
Village dataset with and without SHC facility information beside population details
Health & Family Welfare Dept.
Villages without Sub centres
Select Villages that do not have (<>) Sub centres
Village dataset with and without Sub centres facility attribute information
A detailed department wise requirement is provided under the Annexure 6 for reference.
Section 5: Intended Functional Components of KSSDI Geo-Portal
KSSDI Geo Portal – Modules and Sub Modules
Description: The diagram shows the various modules and sub-modules envisaged based on the RFP for
the KSSDI Geo-Portal.
There are seven modules that serve all the requirements of the KSSDI Geo-Portal module and they are:
1. Security: This module will ensure secure and restrictive access to the portal, based on the login
credentials. Following are the functional sub modules:
a. Registration: Any Internet User/General Public wanting to access the portal must register (sign
up) using online registration. After sign-up user will get the confirmation email and email goes to
admin as well when new member joined the site
If any Government/NRDMS /Line Departments representatives want to access the portal as Data
provider, a separate request need to raised to the KSSDI Administrator for the User Id and
password creation for which he will be emailed his User Credentials to access the portal.
KSSDI Administrator would be the owner of the Geo portal and need to create the
administrative profile using the super administrator access.
Super Administrator profile would be created separately during the KSSDI system setup using
LDAP /Oracle Security Console Administrative privileges. The Super Administrator login id /user
name and the password can be decided and approved in consultation with the
KSSDI/KSCST/NRDMS committee and need to be documented and recorded. The password to
the super administrator access can be reset to default whenever desired.
The password will be dynamically encrypted and stored using SHAW and MD5 algorithm and can
never be visualised. The password however, can be reset to system default in case of loss or
forgetfulness.
b. Login: After the user registers and receives the login credentials, he/she can login to the portal.
The login provides secure access to use the services based on access permission of a specified
group i.e. General user, Data Provider & Administrator:
The general user when login, will have general user’s access permissions
The data providers will have data provider’s access permission, when logged in. Data
provider would be prompted to change his password on first login.
The administrator will be an authorised KSCST staff to have special access to manage the
entire system
Data Requirements:
Attribute table of user profiles with login credential
Attribute table for roles and access permissions linked to users and groups table.
Attribute table to track the user sessions details.
2. Administration: Provides the complete end–to–end administration of the portal with respective
privileges.
a. Manage User: This module will allow the KSSDI Administrator to create user, manage his profile
and Reset the password.
Add User: Add new user to the system.
View/Update User Details: View and Edit the user’s details.
Access Permissions: Access permissions to the users accessing the portal, which includes the
right of add/edit/delete the information, and services of the portal based on the modules
and sub modules.
Block/Un Block User: Block/unblock users from complete or partial access of the Portal
based on modules and sub modules.
Reports: Audit reports based on user transactions which would include login id, login start
time, session duration, logout end time, methods access, errors, exceptions, time outs, etc.
b. Manage Roles and Groups: This module will allow the KSSDI Administrator to create a new
Groups and Roles. Groups can be either creating a new Group/Agency/Data Provider. A Role can
be a either a Data Provide or Administrator providing Access Rules etc., for the Roles and
Groups.
c. Manage Data & Metadata: This module will allow the KSSDI Data Manager to manage the data
that has been hosted on the Portal.
d. Manage Application Resources: This module will allow the System Administrator to provide
controlled viewing of application by restricting functionality usage by methods and resources.
e. Manage Layers: Will enable administrator to show or hide layers and its attributes by roles and
privileges.
Data Requirements:
User profiles attribute Table(s)
Audit / Transaction attribute table(s)
Metadata attribute Table(s)
3. Map Viewer: This module will serve the user with a map based browser, allowing the user to see the
digital spatial data created and hosted by the data provider. It also provides many features to the
user based on the sib modules satisfying the geo portal requirements:
a. Viewer with Map Navigation: This module will act as a core module allowing the user to have
Map Browser with all the map utility tools such as Zoom in, Zoom out, Pan, Measure,
Longitude/Latitude display, Scale display, Identify tool, measure tool, Zoom Rectangle, etc for
performing major map operations.
b. Active layers and layer manipulations: Ability to switch on/off layers, select layers from
catalogue for viewing; layer styling, layer legend, alias display; etc.
c. Styling: Ability to change colour, style, symbol representation, labels for a layer and its features.
d. Search Metadata: This module will allow the user to search the metadata of a layer and view the
metadata going through a filter process to find the layers, which makes the search for metadata
easy.
e. Query: Simple query provide ability to search by bounding box, and conditional statements on a
single layer or table. Complex query provides ability to search and highlight features from
multiple tables / layers through multiple joins through spatial filters and attributes constraints.
f. Publish, Harvest & Catalogue Service: This module will allow the users to search for the
WMS/WFS/CS-W and other services and also authorized users can register their respective
datasets to the portal.
g. Discover: Ability to search services by service URL, service parameters and service type (using
OGC filters) that are published onto the catalogue.
h. Applications (Predefined): This module will allow the user to access the applications and also an
authorized user can customize an application based on the data availability.
i. Map Editing: This module will allow an authorized user to edit the map using WFS-T service. This
can only be accesses by authorized users.
j. Load, Print & Save: The map displayed on the viewer can be saved to a specified Image, GML
format for preserving for future use. These save details can be loaded back to temporary overlay
and view.
With data provider privileges the user would be able to save vector data as GML or
Shape files or Raster image files into a temporary location in the KSSDI server and send a
request to KSSDI Administrator to update into the centralised system.
Allowing for printing using a standard template the Map displayed in Viewer or the Metadata
Listing. Precautions will be taken to print the map with standard font, size, colour, and map
cartography.
Data Requirements:
ESRI Shape files of the Administrative boundaries loaded into Oracle database as SDO Geometry.
ESRI shape files of Thematic layers loaded into Oracle database as SDO Geometry.
ESRI Shape files of point and linear feature layers loaded into Oracle database as SDO Geometry.
Raster dataset as image files in TIFF, BMP, JPEG, GIF, etc
Registry table to store service details for the catalogue services
4. Metadata Extract: This module will allow the users to create and update the metadata to the layers.
It will also allow the user to update and remove the metadata of the layers.
a. Create/Upload Metadata: This module will allow the user to upload or create the metadata of a
layer that has been harvested to the Portal. The upload can be from XML file.
b. Update Metadata: This sub module will allow the user to edit the existing metadata details of
the layer.
c. Export Metadata: This sub module will allow the user to export the metadata of a layer to XML.
d. Remove Metadata: This sub module will allow the user to remove the metadata of layer
completely.
Data Requirements:
NSDI Metadata Standards v2.0 Database formats.
Metadata edit /update log table
5. Product Catalogue: this module will allow the users to search / add / remove the products available
with the various data providers, host them with the payment details of the products, and allow
them to download them by making the payment. This module will only provision them to host the
products and link to the payment gateway site.
a. View Products: This module will allow users to view the complete list of products i.e. the layers
hosted by various
b. Add Products: This module will allow users to add products other than the layers available over
the portal like maps data available as a .PDF etc.
c. Remove Products: This module will allow users to remove the products hosted on the portal.
d. Payment: This will be provision module that will add the list of products with its costs and it will
act as a provision module to link the payment to the Payment Gateway.
Data Requirements:
Attribute table to store the list of Products with its price details.
Attribute table to store the transaction details like user id, IP addresses, user bank name, user bank account number and the amount and the list of products the user has sent to his cart.
6. Service Request: This module will allow users create online / email request to interact with the data
providers or to the KSSDI Administrator to publish a data as a service that is not available or
accessible to view.
a. Create Request: This sub-module will facilitate the any user post the request directly to any data
provider or to an administrator.
b. View/Respond Request: This sub-module will allow the data-provider to respond to the requests
of the users and respond to the same.
c. Remove Requests: This sub-module will allow the administrator to remove the past requests or
the wrong requests posted by the users.
Data Requirements:
Attribute Table to store the user service requests.
Attribute table to track requests and the history of the requests events.
7. Help:
a. Help by user’s role: Help will be provided to all the respective users based on the roles assigned
to the user criteria.
Data Requirements:
HTML based Help document for the general user.
HTML based Help document for the Data Provider.
HTML based Help document for the System Administrator.
Section 6: Intended Users of KSSDI Geo-Portal As per the RFP, KSSDI system can be segregated into but not limited to three user groups based on roles
and privileges. As end users of the system they are also categorised as Geo Portal users and/or Data
Clearinghouse users.
1. General User (Geo Portal User)
2. Data Providers, and (Geo Portal & Data Clearinghouse User)
3. Administrator (Geo Portal & Data Clearinghouse User)
Other important points to be noted about the users of this system:
Only authorized users with valid login and password will have access to the Portal services.
Users of the system will be intranet or internet based to access the web application.
The users are expected to be computer and internet conversant.
The users of the KSSDI Geo Portal are expected to be GIS Savvy to view and query the spatial
information and the related maps.
Based on the security features of the system, each group will be allowed to access and perform
specific set of activities available within the Geo Portal.
Section 6.1: General User
General public not representing any government organisation is considered as general user of the Geo
Portal system.
General User must register with the portal to have access to the system.
General User has a specific access of viewing, search and querying the system.
General User would not be able to add, update, or download any information from the system
The General User can perform following actions:
Register profile, user name and password.
Login into the system using unique login id and password
Update profile
Change password
View Data Dictionary
View Map, navigate map, perform search and query operations
Access map features using key words/coordinates
Discover map services information using key words
Browse Data Catalogue Services and select layer to overlay and view.
Be able to view and modify existing queries and view results on map
Be able to define new queries, execute and view results on map
Load spatial data (GML or ESRI Shape files) available locally on his machine as a layer onto the map
Make online request to the data provider / administrator of the system to provide certain
information not available
Logout of the system
The General User will NOT BE ABLE to perform following actions:
Add, update or remove data while map viewing.
Can only remove data that is loaded locally as GML or shape files
Would not be able to save any modification into the system
Would not be able to save any new query into the system
Would not be able to register any services into the catalogue
Section 6.2: Data Provider This group of users are the representatives of the government departments or the affiliated agencies
providing spatial, attributes and metadata to be hosted on the KSSDI system. Based on their roles and
privileges they are classified into two sub groups:
1. Data Provider, and 2. Data Manager (with respect to his department)
Section 6.2.1: Data Provider
Data Provider has additional privileges over and above the General User privileges. They can perform following operations:
All of the General User Privileges
Add, update and remove data sets related to his department only.
Add, update and remove metadata related to data of the represented department only.
Add, update or remove catalogue services related to his departments data only
Upload or Download data as GML or ESRI Shape Files
Register and publish map into Catalogue Services
Restrict end users for specified Information related t o his departments data
View users requests and respond
Ensure data be OGC compatible
Generate reports related to represented department only.
Data Provider will NOT BE ABLE to perform following actions:
Add, update or remove data for different departments
Add, update or remove metadata for data from different departments
Add, update or remove any user registration profiles, roles and group related information
Section 6.2.2: Data Manager (with respect to department)
Members of KSCST and identified representatives of NRDMS and DST would be categorized
under this user group, who can perform:
All operations provided to General Users
Able to perform Data Provider operations across his department
Add, update or remove data sets that reside at KSCST -KSSDI Server with respect to his data
of his department/agency.
Manage data sets pertaining to his department, accessing rules to the data sets published.
Stakeholders will NOT BE ABLE to perform following actions:
Add, update or remove any user registration profiles
Add, update or remove roles and privileges
Add update and remove groups
Block any users or groups
Manage Application resources
Note: A Data Manager will be trained to perform the above activities.
Section 6.3: Administrator Considered as the super user of the system, the administrative users identified under this group has the
over all privileges to administer the complete system. They are grouped into:
1. System Administrator
2. Super Administrator
3. Data Manager
Section 6.3.1: System Administrator
System Administrator is an authorized KSCST Staff to perform administrative operations of the
KSSDI system. The administrative operation includes:
Managing Users
Managing Roles and Privileges
Managing Groups
Managing Application Resources
System Audit and Reporting
Section 6.3.2: Super Administrator
1. Super Administrator is the only authorized or registered KSCST staff to access the complete
KSSDI server application and the database as well.
2. Super administrator will have the sole and complete authority over the system setup and its
resources.
3. Super Administrator will have the sole authority to authorise creation, modification or
deletion of Administrative user profile, login and password.
4. Super Administrator will have the final authority to approve the data that need to be
uploaded into the Centralised Oracle 11g database. The Super Administrator will have the
authority to modify the data format as per the KSSDI data standard.
In addition to above operations Administrator must also be able to perform following
activities:
Sets up profiles for data providers and other government department representatives.
Control Data accessed by users
Add new data products to the existing Catalogue
Remove data products from the Catalogue
Restrict user accessing classified information
When creating/accepting profiles of users and data providers, the System should notify the corresponding user/data providers about his account information
Modify data format as per KSSDI data standard before uploading
Load spatial data into oracle database
Load attribute data into the oracle database
Make changes &/or update datasets as and when required or requested by State
Departments or NRDMS.
Section 6.3.3: Data Manager
Members of KSCST would be categorized under this user group, who can perform:
All operations provided to General Users
Able to perform Data Provider operations across all the departments
Add, update or remove data sets that reside at KSCST -KSSDI Server
Manage data sets pertaining to any department, accessing rules to the data sets published.
Stakeholders will NOT BE ABLE to perform following actions:
Add, update or remove any user registration profiles
Add, update or remove roles and privileges
Add update and remove groups
Block any users or groups
Fig: Shows the Modules, Sub Modules and Inter Modules of the Administration Module of the KSSDI
Geo Portal.
Section 7: Non Functional Requirements of KSSDI Geo-Portal
The Web server will host the portal application from the application Server.
Web based Geo-Portal will be based on OGC / ISO standards, which can be accessed over the
internet as well as the intranet.
The web response time at a maximum of 10 seconds for a Map Browser and a minimum of 1 second
with and Internet speed of 2 mbps and above. The response time may vary with the respect to the
following:
o Internet bandwidth
o Type of network connectivity
o Quantum of data getting processed to be rendered over the map viewer
o Size of the data being retrieved for display
o Virtual memory available for operation
Under the existing system architecture the geo portal will support 500 concurrent users.
The numbers of concurrent users expected to go up to 5000 in duration of three years period of
maintenance, can be supported within the current KSSDI architecture.
The spatial data stored in the database server shall be scalable from initial 6 GB data store to a
volume as large as 6 terabytes of raster and vector data in future. The storage device may
accordingly be updated when desired.
Automated system back up process to happen every day
Ability to configure the backup process either to happen by date or by daily/weekly/fortnight or
monthly basis.
All system generated errors, exceptions, and warnings must be logged in the audit logs
All Input errors must be handled with client side validation
Additional details on the backup storage and performance is included under annexure.
Section 8: Necessary Data & Resources of KSSDI Geo-Portal
Data Requirements for Geo-Portal (Master Data List)
The spatial and the attribute datasets upload into Oracle 11g spatial database must follow the object
catalogue model and the database conceptual schemas that are identified and agreed for the KSSDI
project.
The spatial datasets would be in MapInfo TAB file or ESRI SHP file format in WGS84 projection
system.
The shape files can be directly migrated into the centralised Oracle Database using SHP2SDO Utility.
The MapInfo TAB files either need to be converted into ESRI SHP files using Universal Translator tool
or can be directly uploaded onto Oracle database using EASY LOADER tool.
Attributes data can be easily migrated using Oracle 11g SQL Loader Tool.
A free utility from Oracle 11g called GeoRaster Loader can be used for migrating Raster images into
Oracle 11g storage.
Spatial datasets Attributes Datasets Administrative Boundaries
Four (4) Divisions Boundary Datasets Division names with: Census Details
Twenty Nine (29) Districts boundary datasets Districts Names with: Census Details
Subdivisions boundary Datasets Sub Division Names with: Census Details
Taluk Boundary Datasets Taluk names with: Census details
Planning Boundaries
Zilla Panchayath Constituencies Boundary datasets for every Taluk
ZPC Name with: Census details
Taluk Panchayath Constituencies Boundary datasets for every Taluk
TPC Name with: Census details
Gram Panchayath Jurisdiction Boundary datasets for every Taluk
GPJ Name with: Census details
Electoral Boundaries
Parliamentary constituencies Boundary dataset for every Districts
PC name
Legislative Assembly Constituencies Boundary dataset for every Districts
LAC name LAC type
Thematic Point themes: Village Settlement Head Quarters (State/Div./SubDiv./Taluk/Hobli/GP) Sample Collection Stations (RainGauge/Observation Wells/Air Monitoring/Weather) Tourist Places Airports
Names with: -Amenities details - -Measurement parameters with units -Place names -Airport names
Linear Themes: National highways
Road Names with: Road classification
State Highways Major District Roads Other District Roads Village Roads Railway Network Drainage
Road Width Road Thickness Other Road assets Traffic volume Traffic density Railway name with: Rail type, gauge type, etc Drainage name with: Drainage type, category, width, depth, etc
Polygon Themes: Agroclimatic Geology Hydrogeomorphology Reservoirs Waterbodies (Tank/Ponds/Lakes) Basin Boundaries Soil Slope Land use Land Cover Forest Wasteland Watersheds(Minor, Sub, Micro) Rivers
All with names, types, classification, properties and/or amenities details
Large Scale Maps Village boundaries Wards boundaries Locality boundaries Municipal/ Corporation boundaries Sub Colony boundaries Built-up areas Commercial areas Government Buildings Manufacturing areas Public /Semi Public areas Education areas Facility Centres Recreational Centres Residential areas Waterways Airports Railway lines Transportation Road Communication Drain Electricity Fuel Solid Waste Waterbodies
All with names, type, classification, category, amenities/provision details
Attributes - Census tables
Metadata tables
Raster - Raster format,
Raster data type Raster file size Raster geographic extent Raster resolution Toposheets numbers
Users/Groups - User name
User contact details Group name Group privileges Role types Resource details
Service Registry - Registry UUID
Registry name Registry type Registry category Scale related Agency related Price related URL
Product Catalogue
Product details Pricing details Temporal details Agency details Availability details Delivery details
Topographic Sheets
Sheet extents Topographic sheet id, Adjacent details
Agencies Details - Agency names
Agency contact person Agency address Agency website Agency Phone Agency Fax Agency email
Layers detail - Layer Id
Layer name Layer Alias Layer type Layer Geometry Layer columns Layer owner Layer agency
Data Requirements for applications
Following are the few identified applications and its data requirements:
Applications Data Requirements
Primary Education Geographic Location with teachers, students, rooms, location scheme details
Population Village boundaries, Taluk boundaries, District boundaries with Census data and population distribution
Health Geographic Location with type and scheme details
Irrigation Irrigation type, classification, etc
Infrastructure
Roads Road network, connectivity, type, classification, direction, lane, asset, etc
Agriculture Watershed, Spatial distribution, type, levels, crop, cultivation, soil, slope, irrigable conditions, Vegetation, Drainage, check dams, Eroded Lands Taluk map, Village map, Roads, Cadastre
Forest Spatial distribution with classification, type, flora, fauna, canopy, etc
Water Spatial distribution with classification, type, quality, usability, etc
Revenue Maps
Police Boundaries, jurisdiction, range, strength, activity, type, crime details, etc
Tourism Location, type, name, visitors distribution details
Energy Energy distribution, consumptions, assets, consumer details, etc
ANNEXURES
Annexure 1: Data Migration / Upload Steps
The geo-spatial datasets can be hosted into the KSSDI Geo Portal system in two approaches based on
the data location and sharing mode:
1. Centralised Hosting
2. Decentralised Hosting
1. Centralized Hosting:
Centralized hosting of the datasets into the KSSDI system would require physical availability of the data with the KSCST team for verification, validation and upload. The data can be made available to KSCST team by: a) Sending them through courier or carrying them personally using mobile storage devices, or b) Send them using KSSDI Load and save interfaces available under Administration “Manage
Data” & “Manage layer” sub modules or Load & Save option under Map viewer. c) The uploaded data get save under a predefined temporary folder in the server domain and a
email will be generated notifying the Administrator about the details of the upload. d) The KSSDI Administrator need to verify the data authenticity, format and classification as per
KSSDI data format identified under Real world Object catalogue and conceptual model before finalising to upload into centralised Database in Oracle 11g spatial SDO format.
The below steps provide details on loading datasets that are available with KSCST in SHAPE, TAB or GML format into Oracle 11g database:
Loading MapInfo TAB or ESRI Shape Files into Oracle 11g:
FIRST STEP
1. Convert Tab Files into Shape files Using MapInfo Professional
1.1) Open Tab File in MapInfo Professional
1.2) Open Tools Universal Translator Select Source Format as MapInfo TAB Specify
location of TAB File Select Destination Format as ESRI ShapeSpecify location of
Shape file in which place want to store Press OK
1.3) Translator converts into Shape Files and it displays successful message.
SECOND STEP
2. Loading ESRI Shape Files into Database Using shp2sdo Tool:
2.1) By Manual process:
2.1.1) place Shp2sdo.exe at Shape file folder
2.1.2) From Command prompt Specify Command as below:
shp2sdo.exe -o -d -p -n 1 -t 0.5 -s 8307 DIST_BND_84 DIST_BND -i DIST_BND_ID -g GEOMETRY
Meaning of above Command Options:
a) DIST_BND_84 the shape file name to convert (expects .dbf, .shp, and .shx files)
b) DIST_BND the name of the table to create and use in Oracle c) -o - convert to object-relational format
d) -d put the data in the control file generated by the tool
e) -p Store points in the SDO_ORDINATES array
f) -i id_column Name of the column used for numbering the geometries
g) -n start_id Start number for IDs
h) -t the tolerance
i) -s the SRID (spatial reference system ID)
j) -g GEOMETRY is the name of the column to load for the geometry object
2.1.3) Shp2Sdo creates .ctl as well as .sql files.
Execute .ctl (DIST_BND.ctl) file,.sql(DIST_BND.sql)files like as
below:
a) Execute .sql (DIST_BND.sql) file with following SQLPLUS
Command:
Connect kssdi_test/kssdi_test@nst (Connect to Oracle)
Give @DIST_BND.sql
Disconnect from Oracle
b) Execute .ctl (DIST_BND.ctl) files as below:
At Command Prompt:
Sqlldr kssdi_test/kssdi_test@nst DIST_BND.ctl
Next Connect to Oracle and execute the following commands
Connect kssdi_test/kssdi_test@nst
EXECUTE SDO_MIGRATE.TO_CURRENT ('DIST_BND');
2.1.4) Create Spatial Index for tables like as below
a) Connect to Oracle b) CREATE INDEX DIST_BND_SIDX ON DIST_BND (GEOMETRY) INDEXTYPE IS MDSYS.SPATIAL_INDEX;
2.2) By Using Custom Java Utility Tool:
2.2.1) Specify Shapefile folder Path as well as Schema name of Database in
ShpToSdoDSSDI.java and Execute loading.bat file
2.2.2) Just press any key, it will Creates loading_tables.bat file, which executes .ctl files
as well as .sql files and creates index also
3) Table in Oracle after migration
2. Decentralised Hosting:
In decentralised hosting the geospatial dataset can reside remotely from the KSSDI Geo Portal.
However the user of the system must be well versed in using maps in a web based environment.
Additionally the user must also be aware of the following usages:
a) Load locally available vector data in SHAPE files or GML format or raster data in Image
files formats for local uploading, viewing as a layer overlay and saving.
b) Secondly, the knowledge to publish a geospatial dataset as an OGC compliance map
services (WMS/WFS/WCS) in a public domain using internet. The following is essential
for publishing map as services:
I. Good bandwidth (minimum 2 mbps ) internet connectivity
II. Static / Public IP for hosting and public access.
III. Knowledge to spatial data publishing as map services
Annexure 2: Steps to Publish Datasets as Map service:
The following steps satisfy the interoperability, extensibility, and standardization of the map
service as a web service framework inline with the international standards such as WMS, WFS,
WCS, and WRS announced by OGC:
1. Identify spatial dataset that need to be published as a OGC service.
2. Either the spatial dataset can reside in file format like ESRI SHAPE files, GML files or in
RDBMS system like Oracle Spatial in SDO format, POSTGIS, MySQL and others that has
spatial extensions.
3. A single table or a group of tables can be published under a single service.
4. Apollo Server 9.3.2 or any OGC compliance GIS system that is capable of publishing WMS,
WFS & WCS services.
5. Apollo web based Administrative Console (similar feature for other OGC compliance GIS
software) for publishing data as a service.
6. Every service requires a universal unique Identification (UUID) called ‘service id’ that gets
automatically generated during the process of harvesting and gets registered in the WRS
system registry.
ADMIN-CONSOLE
In the bottom left pane of the admin console, choose the "Add Service" button. In the screen
that comes up on the right enter the Service ID (i.e. ATLCITY) and choose Oracle Provider.
1. In the Service Info tab, fill the Abstract and Title fields. Set ./wfs_md.xml in the Service
Metadata URL field. Click Accept
2. In the Connection Info tab the oracle connection details are updated and a connection test can
be performed.
3. Under Connection Info tab enter the schema and mapping file names i.e .xml and .xsd and click
on ‘ Generate types and mapping’. A popup window opens. Enter the schema and table name.
Click ‘Generate Mapping’. A schema and mapping file is generated for the corresponding table.
4. By following the above steps a service can published.
Note: Once publishing is done the service will be able to respond to WFS requests (GetCapabilities,
DescribeFeatureType, GetFeature) and to display maps through WMS requests (GetCapabilities,
GetMap, GetFeatureInfo)
Annexure 3: KSSDI Participating Agencies:
Tentative list of Agencies/ Line Departments/ Data providers involved with spatial data in the State Government are:
S.No. Data providers List Contact Details Data Provided
01
Survey Settlement and Land records
Central Office, K R Circle, Bangalore – 560001 +(91)-(80)-22212383, 22212408
Village boundary, Cadastral boundary, Land ownership information
02 Karnataka Public works Department
Public Works Department, Karnataka Government Secretariat, 3rd Floor, Vikasa Soudha, M.S.Building, Dr.Ambedkar Road, BANGALORE 560001
Road network
03 Dept. of Mines & Geology
No.49, Khanija Bhavan, Race Course Road, Bangalore-560001. Phone: 080- 22269632 ,22269633
Geological features, Rock types, Minerals Mineral resources Ground Water depth Ground Water Quality
04 Karnataka Forest Department
Aranya Bhavan, 18th
Cross, Malleswaram, Bangalore – 560003, Ph:- 91-80-23346846
Forest boundary, Forest types Species - Flora & Fauna
05 Bruhat Bangalore Mahanagar palike
Corporation Building, NR Square, N R Road, Bangalore – 560002 +(91)-(80)-22975500, 22221188, 22222753, 22276151
Urban Infrastructure facilities
06 Bangalore Metropolitan Regional Development Authority
No.1, Ali Askar Road, Bangalore – 560052 +(91)-(80)-22263479, 22255493, 41473086
Details on City Out Growth / Expansion
07 Town municipalities /City corporations
Bangalore Mahanagara Palike, NR Square, N R Road, Bangalore – 560002 +(91)-(80)-22221188
ULB infrastructures
08 Water Resources Department
# 304 Vikasa Soudha, Ambedkar Veedhi, Bangalore – 560001 91)-(80)-22255306, 22255524
Major & minor Irrigation
09 Revenue Department No.105,5th Floor, MS Building, Bangalore GPO, Bangalore – 560001 +(91)-(80)-22252731, 22032495, 22032904, 64518108
Bhoomi Project Land utilization Land use classifications
10 Zilla/ Taluka/ Gram Panchayath
Rural Development and Panchayath Raj Departments , 2nd and 3rd Floor MS Building, Bangalore -1
Rural Development programs/schemes
11 Karnataka Biodiversity Board
The Secretary to Government (Environment and Ecology)
Floral and faunal species, Location tag
Department of Forest Environment & Ecology Room No. 708, Gate 2, Multi Storied Building Dr. Ambedkar Veedhi Bangalore - 560 001 Tel: +91 80 22254377, 22092445
12 Bangalore Water Supply & Sewerage Board
Address: 1st Floor, CBAB Complex, Cauvery,Bhavan, K.G. Road, Bangalore, Karnataka, India Fax: 91-80-2215417
Bangalore water supply
13 Rural Development & Panchayati Raj Department
Rural Development and Panchayath Raj Departments , 2nd and 3rd Floor MS Building, Bangalore -560001
Samanya Mahiti Rural Water Supply Rural Infrastrucure Drought prone programme Village roads and bridges
14 Karnataka Urban Infrastructure & Finance Corporation
2nd Flr,Unity Bldg Annexe, 3rd Crs,Silver Jubilee Blk, Mission Road, Bangalore – 560027 +(91)-(80)-22232021, 22232134, 22232132, 22239321
Master plans
15 Karnataka Industrial Area Development Board
No.49,4th Floor, East Wing, Khanija Bhavan, Race Course Road, Bangalore – 560001 +(91)-(80)-22259361, 22265883, 22258609
Industrial land use
16 Department of Industries & Commerce
MS Building, Bangalore 560001 Location of industries, related data
17 Karnataka Urban Water Supply & Drainage Board
No.6, Jal bhavana, Bannerghatta Rd,1st Ph, BTM Layout 1st Stage, Bangalore – 560029 +(91)-(80)-26539003, 26539002, 26539004, 41106504 1st Floor, Cauvery Bhavan, Kempegowda Road, Bangalore – 560009 +(91)-(80)-22945100, 22945101
Water supply and Sewerage pipelines
18 Department of Economics & Statistics
7th Floor, MS Building, Bangalore – 560001 +(91)-(80)-22253758, 22353832, 22353829
Rainfall and statistical data
19 Karnataka State Remote Sensing & Environment Centre
6th Floor, Multi Storage Building, 4th Stage, Dr. Ambedkar Vedhi, Palace Road, Bangalore – 560001 +(91)-(80)-22371325
Thematic maps
No.17, SOI Building Campus, Sarjapur Road, Koramangala, Bangalore – 560034 +(91)-(80)-25634893
20 Karnataka State Council for Science & Technology
Indian Institute of Science(IISc), Malleshwaram, Bangalore - 560012 +(91)-(80)-23311394, 23348849, 23348849, 23341652, 23461688 [email protected]
NRDMS maps/ data: Secondary data
21 Excise Department To be provided -
22 Directorate of Agriculture
To be provided Crop details Seeds Fertilizers Land suitability Land Capability
23 Survey of India To be provided Topgraphic sheet Slope Contours Drainages Water Bodies
24 Geological Survey of India
To be provided Geological and Geo-morphological features
25 Central Ground Water Board
To be provided Ground Water Depth Water Quality
26 Forest Survey of India To be provided Forest types
27 Indian Meteorological Department
To be provided Weather data
28 Karnataka Polution Control Board
To be provided Air Monitoring station Water effluent station Solid Waste Management
29 Directorate of Tourism To be provided Tourism details
30 National Bureau of Soil Survey and Land use planning
To be provided Soil categories, types, irritability
31 Directorate Fishery Culture
To be provided Fishy Culture details
32 Directorate Seri Culture
To be provided Silk realing centres
33 Directorate Horticulture
To be provided Farms Nurseries Drip irrigation
34 Animal Husbandry and Veterinary Services
To be provided Cattle Census Poultry / Dairy Farms Veterinary facilities
35 Directorate of Food and Civil Supplies
To be provided Fair price shops Petrol stations Kerosene depots
36 Women and Child Welfare Development
To be provided Anganwadis, bal bhavans, Remand homes
37 Police Department To be provided Jurisdiction, crime, etc
39 Directorate of Education
To be provided School / education institutions details
40 Directorate of Health and Family Planning
To be provided PHC CSC
41 Department of Energy (BESCOM, KPTCL, KPCL)
To be provided Power distributions IP sets Power Stations
KSCST team will supply all the relevant documents to form the basis for conducting the requirement analysis,
preparing the feature catalogue, and design of the envisaged spatial database. Both spatial and attribute data sets
to be incorporated into the database will also be provided by the KSCST.
Annexure 4: Reference High Level KSSDI Use Cases
Figure: KSSDI Geo Portal Module Use Case Representation
Figure: KSSDI Geo Portal Administrative Module Use Case Representation
Figure: KSSDI Geo Portal Map Viewer Module Use Case Representation
Figure: KSSDI Geo Portal Metadata Extract Module Use Case Representation
Figure: KSSDI Geo Portal Product Catalogue Module Use Case Representation
Figure: KSSDI Geo Portal Service Request Module Use Case Representation
Figure: KSSDI Geo Portal Help Module Use Case Representation
Annexure 5: Reference Lower KSSDI Use Cases
Figure: Centralized Database Use Case
Figure: Geo Portal Use Case
Figure: ERDAS APOLLO SDI Framework Use Case
Figure: Need Assessment Use Case
KSSDI Registration & Login Use Case: Use-case Id: KSSDI Geo Portal–Registration Use Case Name: Registration & Login Description: Registering a user with his name, address, contact details and user name and password choice for
the KSSDI site access Actor/Role Player:
Administrator, Data Provider, General User
Preconditions User should have internet to access KSSDI portal URL Data Dependencies:
Registration details must be true in all respect User Information Table
Frequency of Use:
As and when a new user wants to access the site
Basic Flow: System prompts the user for their username and password. Or provide an option to register as a new user. New user select ‘Register’ to go to registration screen to enter details and submit. Submitting registration details generated Email notification to the Administrator Administrator validate the user details and sent Authentication notification and details through email. User enters username/password and submits the information. System verifies the user. User is given access to the system to perform their job.
Post conditions:
Identity confirmed and user level set.
Alternate flow: On the fly authentication on registration without a wait for Administrator intervention. Associate Use Case Diagram: KSSDI Geo Portal – Registeration & Login
General User
1..*
-SignupUser Profile
«uses»
Administration
«uses»
Roles & Privileges
«extends»
Login
1..*
-LoginId1 «uses»
Data Provider
* 1
Administrator
*
Registration
Exceptions The user details entered in the registration is incomplete or incorrect.
The username and password doesn’t meet the criteria. The details are not acceptable due to security reasons
Includes; Notification to the Administrator on registration submission Notification to the user on the status of registration
Special Requirement:
None
Assumptions: The user to be computer literate The user is assumed to provide all valid and complete details
Note & Issues: Users wanting immediate access to the site. Requirement(s) satisfied by this use case:
Secure Access, Registration and Login
KSSDI Data Migration Use Case:
Use-case Id: KSSDI Geo Portal–Data Migration Use Case Name: Data migration into Oracle
Description: Upload spatial and attribute data in MapInfo tab file format or in ESRI shape file format onto Oracle 11g Spatial database storage
Actor/Role Player: Administrator
Preconditions 1. Spatial data must be topologically correct 2. Data must be arrange in correct hierarchical level as per the real world object relation 3. Datasets must be classified and group as per scale, real world objects, feature types
and mapsheet representation. 4. Datasets schema must be consistently represented across all layers 5. Data indexing must exist 6. Relationship with other datasets must exist
Data Dependencies: Feature Catalogue Real world object catalogue Database Conceptual model
Frequency of Use: While establishing the centralized database system. Also when data is updated to reflect changes
Basic Flow: 1. Identify the location of the data that need to be uploaded. 2. Verify the data hierarchy, classification and semantics are well established 3. Maintain a checklist for data and indexes for upload 4. Establish a unique workspace for KSSDI within the Oracle database 4. Use SHPTOSDO utility to upload data from ESRI shape file format 5. Use Easy Loader utility to upload from MapInfo Tab files 6. Oracle GeoRaster tool for uploading Image datasets
Post conditions: Centralized database system is established for the geo portal access
Alternate flow: None
Associate Use Case Diagram: KSSDI Geo Portal-Data Migration
Centralised DB
Centralised DB
Schema
«extends»
Upload Tools
SHP2SDO
EasyLoader
GeoRaster Loader
«uses»
GeoDatasets
«uses»
Administrator
1..*
Exceptions The username and password cannot be verified.
Includes: GIS tools like MapInfo and ESRI to verify data content and format Utilities to upload spatial datasets into oracle database
Special Requirement: None
Assumptions: Datasets are geometrically correct
Note & Issues: Upload duration depends on the size and quantity of the datasets
Requirement(s) satisfied by this use case:
Centralized Hosting of datasets into Oracle 11g Spatial
KSSDI Manage Metadata Use Case:
Use-case Id: KSSDI Geo Portal– Manage Metadata Use Case Name: Managing Metadata
Description: Ability to add, edit and delete meta data information
Actor/Role Player: Administrator, Data Provider
Preconditions Data for which meta data is required, must exist in the database and geo portal as well. Metadata information about the data must exist to add or update.
Data Dependencies: Metadata (CID- AtTMd01 to CID- AtTMd0109) for the Spatial datasets
Frequency of Use: As and when data is updated As and when meta data requires an update
Basic Flow: 1. Interface to identify the data for which the metadata to be updated. 2. Standard user interface form to add or update the metadata 3. Submit to save the information into the centralized repository 4. Option to delete and existing metadata.
Post conditions: Metadata is added or updated or delete from the system as per the action performed
Alternate flow: None
Associate Use Case Diagram:
Publish Metadata
ISO19115 NSDI 2.0
«extends»
«extends»
«uses»
Upload
Update«uses»
«uses»
KSSDI Geo Portal – Managing Metadata
1..*
Data ProviderAuthorize User
Exceptions
Includes: ISO109115 / NSDI 2.0 metadata format
Special Requirement: Relation should be maintained between the layers and its corresponding data provider, so that the provider can modify or update only those layer details that belong to his/her agencies
Assumptions: NSDI 2.0 metadata format in XSD format
Note & Issues: Differences between ISO 109115 & NSDI 2.0
Requirement(s) satisfied by this use case:
Manage Metadata: Add, update, upload
KSSDI Query Use Case:
Use-case Id: KSSDI Geo Portal - Querying Use Case Name: Querying of layers / tables
Description: Authorizes user to query single or multiple map layers and able to save the result in GML/Shape format and publish as map service into the catalog
Actor/Role Player: Administrator, Data Provider, General User
Preconditions User should have a valid username and password. User must be authorized to perform query operation on the map layers
Data Dependencies:
All map layers
Frequency of Use: When in map view and any of query operation is selected
Basic Flow: 1. System prompts the user for their username and password. 2. User enters username/password and submits the information. 3. System verifies the user. 4. User access map to view and perform query operation. 5. View results of query 6. Select to view 7. Save into GML or shape. 8. If authorized ability to publish into catalog
Post conditions: View query results, with the ability to save and publish
Alternate flow: Simple Query – on single layer
Complex Multiple Spatial Query – on multiple layers and attributes
Dynamic query – select line dept., select layers, set description, define SQL and save to retrieve by keyword search and execute repeatedly
Associate Use Case Diagram: KSSDI Geo Portal – Simple Query
Simple Query
Authorize User
«uses»
Map Viewer
«uses»
Catalogue Service
return results
«uses»
«extends»
KSSDI Geo Portal – Complex Query
Complex Query
«uses»
Map Viewer
«uses»
Catalogue Service
return results
«uses»
«extends»
Single Table
«uses»
Multiple Tables
«uses»
KSSDI Geo Portal – Dynamic Qyery
Dynamic Query
Authorize User
Authorize User
Line Dept.
SQl Query
Multiple Tables
Centralised DB
«uses»
«uses»
«uses»«uses»
«uses»
Keyword Search
«extends»
General User
Data Provider
Data Provider
Data Provider
Administrator
Administrator
Administrator
1..*
1..*
1..*
1..*
*
Map Viewer
«uses»
Catalogue Service
«extends»
Exceptions For authorized users only
Includes: Line department details, layer and field details, spatial and attribute filters
Special Requirement:
Dynamic query definition for Line department applications
Assumptions: Authority or privilege to perform all the querying operations SQL queries must be tested to work before using in dynamic query options
Note & Issues: NA
Requirement(s) satisfied by this use case:
Querying, Application, Multi spatial and attribute joins
KSSDI Download/Upload GML/SHP Use Case:
Use-case Id: KSSDI Geo Portal – Download or Upload Use Case Name: Downloading and Uploading
Description: Authorizes user to download or upload and view or query map data information as GML 3.x or as Shape file format
Actor/Role Player: Administrator, Data Provider, General User
Preconditions User should have a valid username and password. User must be authorized to perform download operation of the map data
Data Dependencies: All map layers
Frequency of Use: When provided with download option while viewing or querying map layers
Basic Flow: 1. System prompts the user for their username and password. 2. User enters username/password and submits the information. 3. System verifies the user. 4. User access map to view and perform query operations. 5. User uses the download options to download data into local system 6. Option to download in any of the two formats – GML or Shape 7. Save dialog to save the gml / shape file into local machine
Post conditions: User is able to save the information as gml or shape in the local machine
Alternate flow: Using ‘Discover - local data’ option
Associate Use Case Diagram: KSSDI Geo Portal – Download/Upload
Download & Upload
SHP
Authorize User
«uses»
«extends»
«extends»
Local Disk
«uses»
Map Viewer
«uses»
Data Provider
Administrator
GML
General User
Exceptions Must be authorized to perform download operation.
Includes: GML format 2.x and 3.x along with shape file format
Special Requirement:
Ability to publish GML into catalogue services
Assumptions: Must have the authority to download / upload data in GML & Shape file format
Note & Issues: Dependent on Geo API
Requirement(s) satisfied by this use case:
Map Download and Upload in GML and Shape file format
KSSDI Catalogue Service Use Case:
Use-case Id: KSSDI Geo Portal-Catalogue Service Use Case Name: Catalogue Service
Description: Authorizes user to view catalogue service to view and add to map Actor/Role Player: Administrator, Data Provider, General User
Preconditions All map layers must be part of the Registry service published as WMS, WFS or WCS to appear in the catalogue services
Data Dependencies: All map layers published as WMS, WFS All image layers published as WCS
Frequency of Use: When viewing map
Basic Flow: 1. System prompts the user for their username and password. 2. User enters username/password and submits the information. 3. System verifies the user. 4. User access to view catalogue of services published 5. Perform search on catalogue for map layer by keyword, service type Area of Interest
or by coordinates. 6. Results list display for selection and map viewing.
Post conditions: Identity confirmed and user level set.
Alternate flow: -
Associate Use Case Diagram:
KSSDI Geo Portal – Catalogue Service
CSW
«extends»
PublishingWRS
«extends»
WMS WFS WCS
«uses»«uses»«uses»
«uses»«uses» «uses»
Map Viewer
Configuring
«uses»
Data Provider
Administrator
-_1
-_1
1..*
Catalogue Service
«extends»
Exceptions Must be authorized to view catalogue
Includes: WRS for publishing into the Catalogue service
Special Requirement:
Every map layer in the SDI framework must be published using WRS into Catalogue service (CSW) for selection and map viewing
Assumptions: -
Note & Issues: -
Requirement(s) satisfied by this use case:
Harvesting, Data Publishing as Map Services, Catalogue Services and listing
KSSDI Data Editing Use Case:
Use-case Id: UC_DataEditing Use Case Name: DataEditing
Description: Authorizes user to edit vector data from a web browser
Actor/Role Player: Administrator, Data Provider
Preconditions User should have a valid username and password. User must be authorized to edit map vector data The WFS server msut be transactional to perform vector edit
Data Dependencies: All vector data - point, line or polygon geometry types and associate attribute layers under: CID-SpD01 CID- AtTMd01 to 09 CID- AtTCnT01 to 17 CID- SpDLsD1 to 34
Frequency of Use: when select WFS-Transaction
Basic Flow: System prompts the user for their username and password. User enters username/password and submits the information. System verifies the user. User access vector map to perform WFS-T operation. Uses the tool bar option to add, edit or delete spatial or attribute features on a dataset layer:
Drawing geometry options:
Point I. Add Vertex
II. Delete Vertex III. Move Vertex
Line I. Add Vertex
II. Delete Vertex III. Move Vertex IV. Add Line
Polygon I. Add Vertex
II. Delete Vertex III. Move Vertex IV. Add Inner Ring V. Add Polygon
Post conditions: Change in geometrical shape of the object
Alternate flow: NA
Associate Use Case Diagram: KSSDI Geo Portal Data Editing
WFS-T Map Editing
«extends»
Authorized User
«uses»«uses»
Administrator
Data Provider
Viewer
Exceptions WFS-T must be available to perform editing operations
Includes; WFS-T
Special Requirement: NA
Assumptions: WFS-T feature option and API available to support editing of features
Note & Issues: NA
Requirement(s) satisfied by this use case:
Geometry Features and Attribute editing
Annexure 6: Detailed Department Wise Requirements
Department/Scheme Application Requirement Application Query Data Required
Agriculture
(Drought Prone Area Program DPAP)
Water shed area 2500 Ha Water shed area 500 Ha
Select watershed with area = 2500 Ha Select watershed with area = 500 ha
Water shed boundary map with type delineation and area information available in Hectares
Million Well Scheme (MWS)
Water shed area = 500 Ha with SC 33% population
Select watershed with area = 500 ha and census SC total population 33%
Census population data for SC Watershed delineation boundary map with types
Soil fertility map with nutrient availability.
Soil fertility map with nutrient availability.
Soil fertility maps.
Soil
Village level Population Village Level SC, ST Census
Micro Irrigation Scheme Soil type & under ground water level of a specific area & design cropping pattern and to know organic matter depletion
Soil type & under ground water level of a specific area & design cropping pattern and to know organic matter depletion
Soil, HGM
Dept. of PRED
Regarding Topography & soil surface with engineering point of view details.
Soil Categories of Taluks under a district. Locating a particular type of taluk, where Type of soil is greater than there usual level.
Soil, Slope,
Ground water levels to drill bore or dig open were to know underground water levels are very important, whether this information is available.
Locate Ground water wells where Water Level is below the expected level
OBW
Need for existing road details information.
Location of Village roads and deriving the details of the Road.
Roads
Village wise water supply & Bore wells location
Location of the Bore Wells and Villages. Tank Details of a Taluk/Village.
Location Data of the Bore Wells, MWS, Tanks and Water Bodies.
All MDR, SH & NH, village road information of status of road.
Locating Roads and Providing its Details.
Roads – NH, SH, MDR, Village boundary
Dept. of Social Forestry
The extent of wasteland available in a gram panchayath of villages and also the extent of roads.
Locate Waste Land Area > 100 Sq. Kms, Under a Taluk.
VR, Wasteland, ODR
Topography, soil type, slope and the land pattern in selecting the species to be planted in a village.
Soil, Slope, LULC, Village boundary map
Village settlements inside R.F. & S.F. Boundaries
Village settlements inside R.F. & S.F. Boundaries
Forest, Village
Dept. of Health
Infrastructure of Health Systems in District /Medical college/Dist. Hospital/Taluk Hospital/CHC/IPHS/PHC/PHU/SGB Centre.
Locate the PHC’s Under a Taluk of the District. Locate taluk where Health facilities are not available under a district.
Census part 2 + Health facilities with village settlement
Department of Fisheries
Present water spread area of the tanks and the achucut area of the tank.
Locate Tanks where Water Spread Area is more than 100 Sq. Kms
Tanks, Water Bodies with Location Details
Exact location of the tank, (longitude/latitude), Survey No. and route.
Locating the Tanks under a Taluk with locations
Tanks, Water Bodies with Location Details
Fish Farmers Development Agency
Extent of water spread area of tanks (latest) to know the fish seed requirement.
Tank map, Taluk & Village map
Extent of water logged area, which has become suitable for agriculture in achucut area.
Locate Tanks where water quality is greater and suitable for agriculture under a Taluk.
Tank map, Taluk and Village Map
Horticulture
Integrated soil & climate based data, village wise to facilitate Horticulture development.
<< Parameters to be Given>> Soil, Agro climatic, LULC
Dept. of Sericulture
Water Resources (Open well & Bore wells) taluk wise & village wise.
Water Resources (Open well & Bore wells) taluk wise & village wise.
Waterbodies, tanks/ponds/reservoir
Taluk Panchayath
All Infrastructure available GP wise to be provided including internal resources.
Query on the Village Settlements and Infrastructure Facilities
GPJ map, Settlement, amenities details,
Location of Drinking Water Facilities
To locate the M.W.S. and PS. in taluks.
Drinking water facilities, MWS and Pump Stations
Dept. of Watershed
Soil Erosion Soil and Water Shed Layer Soil, Watershed
Drainage and Watershed Drainage and Watershed Drainage,Watershed
Minor Irrigation
R.S. map indicating the MI Tanks, Anicuts
R.S. map indicating the MI Tanks
Minor Irrigation Tanks, Water Bodies
Dept. of Education
Location of Schools, Computer Centres.
Locate Examination Centre where School Id = 5
Census
Dept. of Economics & Statistics
Identify Natural Resources in Villages
Locate Villages with out Lake Locate Villages with out River Passage
Water bodies, Rivers, SOIL, LULC
Annexure 7: Roles of KSCST:
Karnataka State Council of Science and Technology (KSCST) established under the patronage of
Department of Science and Technology and Karnataka Government, and its members will play a vital
role in establishing the Karnataka State Spatial Data Infrastructure (KSSDI), operationalising and
maintenance of the system. The elaboration of the roles and responsibilities is detailed as hereunder:
System Stages KSCST Roles and Responsibilities
Establishment: Assist in identifying the users and the expected levels of usage of the KSSDI system
Assistance in preparation of the Need Assessment Report
Provide documents to form the basis of conducting requirement analysis, identifying feature catalogue and designing spatial database schema
Sharing district level user needs information specific to each individual line departments and NRDMS centers as an assistance to the preparation of KSSDI need assessment
The desired functional requirements of the KSSDI System
Gathering district, taluk and village level spatial and attribute datasets to be incorporated into the KSSDI system
Organise the gathered district taluk and village level datasets for the local level planning
Provide data for the real world object catalogue identification and preparation
Review and approval of the Need Assessment prepared by the NST consultants
Ensure systematic deployment procedures be established for setting up the KSSDI software
Ensure standard database model be established in the centralised repository
Ensure all the datasets are organized into identified centralized database as per the approved KSSDI data standards
Setup a systematic and periodic review process and ensure strict adherence establishing the KSSDI system
Record of all operations into standard template as checklist and procedures
Operationalisation Ensure the customization of the spatial and attribute datasets into centralized database follow the established database model standards and procedures
Ensure the customization of the SDI framework follow the OGC compliance
Ensure deployment of KSSDI software system is follows the system architecture with proper connectivity and validation:
Hosting and entry point at web server,
Security management is hosted at security server
KSSDI Geo Portal application is hosted at application server, and
KSSDI data resides at database server
Ensure the relationship between users, functions, and data requirements identified in the Need assessment is established in the Geo Portal to the complete satisfaction
Identify KSCST member and entrust authority to perform a system level verification of the data deployment, portal operations and results.
Identify KSCST member and entrust authority to perform a system level Testing and reporting of test results / issues/ bugs of the data deployment, portal operations and
results.
Authorize KSCST individuals to manage the KSSDI system
Identification of the staff for training
Identify date of training and notify all the participants of the venue, date and time of the training
Intimate Line departments for a user level acceptance testing and reporting
Ensure rectifications of issues observed during user level acceptance testing
Project Sign off for role out and operationalisation of the Geo Portal
Setup Data manager roles and privileges
Entrust the role of system administrator within KSCST
Entrust the role of super administrator within KSCST
Intimate line departments and district centres of the roles and responsibilities at the KSCST for operationalising the KSSDI system and the point of contact for further interaction
Formally notify all stakeholders about the Geo Portal system role out and the web site URL for access
Formalize the support guidelines to be followed during system maintenance phase
Maintenance: Assess readiness at KSCST to take up maintenance
Identify the datasets that need to be published into Geo Portal
Entrust responsibilities to Add/update/remove datasets from the server
Verify data that need centralized hosting
Entrust role to perform QA/QC of data for hosting
Period review of the Geo Portal system
Ensure technical support for software troubleshooting
Resolution of application issues and patch update
Periodic Upgrade of software and hardware
Monitor number of hits, transaction logs
Ensure monthly maintenance reports generated and shared for committee review
Review and regularize the maintenance checklist based on previous experiences
Responsible for periodic data update
Responsible for periodic data backup
Annexure 8: Data Management:
With the increase in quantum of data that need to be stored into the central repository and be used by
the geo Portal, maintaining the Data Consistency becomes a major issue, while adding, or periodic
updating or removing. With respect to the KSSDI Geo Portal will have a procedural approach for
adding/updating a dataset:
Data Operations Data Consistency check list
Data Loading To add new a dataset into Oracle review the schema of the dataset
Establish Unique Identifiers
Establish the Standard Data Format and naming conventions as identified in the Real World Object Catalogue
Import the dataset to oracle database using SHP2SDO tool
Shape files can be loaded into Database using Oracle Shp2Sdo tool, that generates .ctl and .sql files
The Data tables are inserted into Oracle with the help of .ctl and .sql file
Shp2Sdo automatically creates metadata for tables in .ctl and .sql files
Need to create spatial index for the tables on geometry column whose datatype like SDO_GEOMETRY
when creating spatial index on geometry column for a table e it is a must to give index name that does not exceed 30 character
Ensure keywords like ZONE,LEVEL are oracle keywords and need to be avoided as column name
Ensure Column name cannot start with numbers
The geometry column must contain correct data without null values, array elements must be consistent with the count with same reference system
While loading dump files through Import option must check for tablenames that already exist in database. If already exist then those tables need to be dropped with cascade constraints and delete metadata layer for those tables
Enter the details of the layer/dataset in the data dictionary using data dictionary module in order to give the layer unique code
Data dictionary module allows you to classify the dataset
The Layer Code assigned here will act as the unique code for the other operations on the layer such as for Metadata Information, Data Manager, etc
Oracle Database To view the data loaded correctly or not into Oracle need to use a free tool called GEORAPTER SPATIAL VIEWER (provided by sourceforge.net)
GEORAPTER SPATIAL VIEWER can be found at http://georaptor.sourceforge.net/install.xml
GEORAPTER SPATIAL VIEWER support for SQL Developer 1.1 and Later Versions
The metadata for each table is stored in MDSYS.USSR_SDO_GEOM_METADATA view. GeoRapter tool reads the metadata for that table from user_sdo_geom_metadata view.
If metadata and spatial index for a table is create for a table properly then GEORAPTER displays table data otherwise it displays common error message like:
“no metadata layer exist for a table” ,or
“OCI index routine engine does not fine index for a table”,or
“index failure” ,or
“SRID does not match with geometry data(i.e if geometry data is in EPSG:32643 but metadata created for that table with srid EPSG:8307)”or
“unable to read metadata from USER_SDO_GEOM_METADAT view”, etc.
To validate geometry column for table then we have the option in SQLDEVELOPER VALIDATE GEOMETRY columns it displays 0 errors if geometry column contains correct data otherwise it shows errors.
To view attribute data and geometry data separately for a specific record GEORAPTER provides option to view them separately
It is possibility to view spatial data for 2 or more tables at a time using GEORAPTER.
If the geometry column contains negative data i.e coordinates values is in negative like -1234.8888888888 then we loaded the data incorrectly by giving SRID wrong i.e. SRID does not match with data. Sometimes it displays data in spatial view but when we are accessing application side data does not come or selection for that data is not coming. For this we have to transform layers into correct EPSG format
If we are trying to create spatial index for a table that index name already exists then it displays index names already exists. These types of constraints also available for column names as well as table names.
If we are creating primary key on specific column already data is in table it displays error message not null constraint is violated if that specific column contains null values.
If we are trying to create spatial index other than GEOMETRY column then it displays errors so we must create spatial index on GEOMETRY column only.
Geometry type (GTYPE) in SDO_GEOMETRY datatype are:
GTYPE specifies whether it is 2D or 3D data.
If GTYPE= 2001 It specifies 2D point Data
GTYPE like 2002 It specifies 2D line Data
GTYPE like 2003It specifies 2D polygon Data
If table data has multi line strings data but if we stored data with GTYPE 2002 into database
then we are unable to see that type of data in GEORAPTER or it displays incorrectly.
Therefore, we have to check GTYPE for records including SRID and SDO_ORDINATES_ARRAY
elements .These type of problems, which we are commonly faced with MULTIPOINT as well
as MULTIPOLYGON data also.
For multi line strings we need to specify GTYPE as 2006.
If we need to create relationships like FOREIGN KEY ,PRIMARY KEY on existing tables for
example FOREIGN KEY relationship
We need to check parent table has primary key or not and any one of the column data in
child table must match with parent table or not.
Data Updating Centralised Updation:
Updated data is sent to the KSSDI Data Center Data is reviewed by the Data Manager/Administrator and Updated
Decentralized Updation: A request for updation of the data is given to the KSCST Administrator. The administrator converts the WFS service to WFS-T and provides the access
permissions for editing online. The user updates the geometry features and attributes from remote and intimates the
administrator. The changes made by the user will be stored to the database but will not be
committed. Once the administrator reviews the changes, the data updated can be committed or
else roll backed.
Data Maintenance All the major datasets once uploaded into the Oracle database are locked and are not allowed to update. If it has to be updated it has to go through the channel of KSCST approval.
If it’s required to update any particular dataset by a department directly, the department has to specify the reason and details of update to KSCST. On approval a WFS (T) service will be created by ADMIN and an authorized user can update the data which will reflect into the database
If the data is updated through any of the above process the records are not to be committed into the master tables without the verification Super Administrator. The super admin will approve it gets committed or disapproves for a roll back
In the above scenario data will be updated but the schema will not change
The data will be maintained in two forms during edit process: as master table and as transaction table. The edit will happen only into transaction table. This gives the ability to verify the changes by the KSSDI super administrator and the authority to commit or role back.
Annexure 9: Version Control, Back Up and Storage:
Version Control: Workspace Manager, a feature of Oracle 11g Database, allows the Data Administrators to manage
multiple version of data in the same database. It uses workspaces as virtual environment to isolate a
collection of changes to production data, keep a history of changes to data and create multiple data
scenarios for “what if” analysis.
Versioning for concurrency means data can be inserted and changed in a workspace while users
continue to use the production / deployed version of the data. Isolating changes in this fashion, also
known as long transaction, is useful for data validation and long duration projects. Versioning of history
allows earlier versions of the data to be kept indefinitely. This is useful to go back and view how the
database looked with the changes at a particular point of time.
It is a PL / SQL package that “Version enables” user tables. When a table is version enabled it is
renamed. A view is created on it and given the original table name, which makes the renaming of the
table transparent to the applications. Instead of triggers created on the view ensure all DML statements
executed on the view are applied to the underlying table. Workspace Manager metadata columns added
to the user table allow multiple versions of a row with the same user defined primary key to exist in the
table.
A workspace logically groups a collection of changes and provides session context to ensure a user
accesses the appropriate version of a row. Workspaces can be arranged in hierarchies. The top most
workspace is called LIVE. It is the default workspace for the user activity and the production version of
the data.
Workspace manager only makes a copy of a row if it is changed. This can significantly reduce the
hardware, software, and time needed to manage multiple versions of the data as compared to the
scenarios where data is copied in bulk (tables and schemas) and synchronised. It increases productivity
by allowing concurrent to different versions of the data and changing context to a different workspace.
It also reduces labour by allowing a single point of update and management for all versions of the data
while freeing the application developer from writing custom code and creating application specific
metadata to keep track of multiple data versions. It does not require changes to the application SQL
statements to access version enabled tables.
Workspace manage can enable the KSSDI users to store the current, proposed and historical values for
data in the same centralised database. Data Administrator creates workspaces to isolate a collection of
changes for an indefinite period of time. These changes are merged with current data when they are
completed and approved. This allows the end users to access current data while data is being updated.
It also creates an audit trail for the data administrator and keeps historical and proposed states of the
data for other authorised users.
The workspace manager “GotoDate” API enables user to see database as it existed at any point of time.
The workspace manager “CompressWorkspace” API is used to remove obsolete versions.
Oracle Enterprise Manager Interface provides a comprehensive feature options to version-enable tables,
work in workspaces, use workspace save points, history, privileges, access modes, locks and to detect
and resolve conflicts:
Version – enabling Tables:
The unit of versioning is a row. When a table is version enabled, all rows in the table will support
multiple versions of the data. All insert, updates, and deletes (DML) to row versions are done in
conventional oracle short transactions, ensuring data integrity. Workspace manager implements by
renaming the table to tablename_LT adding few columns to store versioning metadata and creating a
view. A table can be disabled from versioning.
Workspaces:
A workspace is a virtual environment to maximize concurrency and logically group and isolate a set of
changes to data in a long transaction of indefinite duration. Users in a workspace automatically see the
correct version of the rows in which they are interested along with a transactional consistent view of
rest of the data. The default workspace for a session context is called LIVE where the user sees the
current production data. When a workspace is created it is created as a child of LIVE. A child workspace
can be made to have two or more parent workspaces.
A new version of a row is created when a change is made to a row in a child workspace for the first time.
Subsequent changes to the row are applied to the same version until a save point is created.
Changes in a workspace cannot be seen outside the workspace until they are explicitly merged with
production data or discarded.
Workspace operations includes create, goto, refresh, merge, rollback, compress, remove, multi-parent,
and alter description.
Save points:
These are changes in the workspace to which changes can be rolled back, and to which users can go to
see the state of the database.
Save points can be created implicitly or explicitly. An implicit save point is created in the parent
workspace when a child is created. An explicit save point is created by a user on completion of a design
and commit.
History of Changes:
This option provides transaction time timestamp every time a row is changed. It provides a history of
changes made to each new version created by a save point.
Valid Time Support:
If Valid Time option is enabled for a table each row contains and added column to hold the valid from
and valid till period associated with the row as an object type. The gives and option to indicate the data
is valid within an associated time range.
Merging, Refreshing, and Rolling Back Workspace Changes:
Merging a workspace involves applying changes made in a child workspace to its parent workspace.
Rolling back a workspace deletes the changes made to the workspace in one or more version enabled
tables. Rollback can happen between save points or with the original copy.
Refreshing the workspace involves applying changes made in the parent workspace to a child
workspace. The refresh can happen manually or automatically as changes are committed or merged in
the parent.
Spatial Topology Support:
A workspace can isolate a collection of changes to one or more topologies keep history of changes and
create multiple topological scenarios for “what If” analysis in the database.
Backup and Storage: Ailing to the set up of the Clearing House for the KSSDI Geo Portal one of the components suggested and
procured software for the storage and back up is the IBM Tivoli Storage Manager. It’s a client licensed
product that provides storage management services in a multiplatform computer environment. The
backup-archive client program permits users to back up and archive files from their workstations or file
servers to storage, and restore and retrieve backup versions and archived copies of files to their local
workstations. Tivoli Storage Manager provides these functions:
Reduces network complexity
Tivoli Storage Manager reduces network complexity with interfaces and functions that span network
environments. This provides consistency across different operating systems and hardware.
Increases administrator productivity
Tivoli Storage Manager can reduce the cost of network administration by allowing administrators to
perform these actions:
Automate repetitive processes
Schedule unattended processes
Administer Tivoli Storage Manager from anywhere in the network
Reduces the risk of data loss
Many users do not back up their data. Other users apply stand-alone backup techniques with diskettes
and tapes as the only protection for business data. These backup systems often produce disappointing
results during recovery operations. Tivoli Storage Manager schedules routine backups that enable users
to recover from accidental data deletion without administrator involvement.
Optimizes existing storage resources
Tivoli Storage Manager allows users to move files from client file systems to Tivoli Storage Manager
Storage. This saves space on client file systems and can eliminate the expense of upgrading client
storage hardware.
Tivoli Storage Manager monitors client storage space and moves files from client file systems to Tivoli
Storage Manager Storage if an out-of-space condition threatens. This function can also eliminate the
expense of client hardware upgrades.
Tivoli Storage Manager provides these services:
Backup and restore services
These services generate backup copies of data at specified intervals and restore the data from these
copies when required. These services protect against workstation or file server media failure, accidental
file deletion, data corruption, data vandalism, or site disasters.
Archive and retrieve services
These services provide backup-archive clients with point-in-time copies of data for long-term storage.
Server hierarchical storage management services
These services migrate client files from expensive storage media to less expensive storage media (from
disk to tape, for example). Administrator-defined thresholds determine file migration for each storage
pool. Migration applies to all backup and archive client files.
Automation services
Tivoli Storage Manager Administrators can increase productivity by automating common storage
administration tasks.
Administration services
Tivoli Storage Manager Administration services provide support for routine monitoring, administration,
and accounting. Administrators can manage the server from another system or the same system. The
Tivoli Storage Manager utilities allow the administrator to perform these functions:
Set client and server options
Define devices
Format storage volumes
Add additional clients
Label tape volumes
Tivoli Storage Manager monitors scheduled operations and maintains status information in the
database. An administrator can export data to removable media. This data can be imported by another
server, making the export and import features a convenient utility for moving server data. The
administrator can specify the accounting option generated at the end of each client session.
Security services
Security services control user access to Tivoli Storage Manager Data, storage, policy definitions, and
administrative commands.
Disaster recovery management
Disaster recovery management helps the administrator implement a comprehensive backup and
recovery procedure for important business applications, data, and records.
Annexure 10: Performance & Benchmarks:
Benchmarks
The benchmarks of “KSSDI Geo Portal Application” for the support of comprehensive application in
order to discover, describe, catalogue and securely deliver geospatial data to end-users. Some of the
benchmarks of the KSSDI Geo Portal Application would be:
OGC & ISO: Will be built based on International Standards for describing and delivering the data. It
follows open standards and is totally non-proprietary. To access these geo-spatial data, the end-user can
use any application that can consume OGC Web Services.
Interoperability: Application allows administrator to deliver different types of geospatial data from
varied sources to huge list of end-users. The data can be in any format and any end-user who can read
and access OGC web services can see and view this data. Therefore, the end-user sees unified set of data.
Catalogue: A department can catalogue geospatial information by harvesting metadata and persist it in a
central, searchable catalogue. Simple harvesting from SAN with thousands of imagery takes
approximately less than 3 minutes per GB and about 180,000 per day. In addition, if footprints,
thumbnails and pyramids have to be created then these numbers end up to approximately less than six
minutes per GB and 80,000 per day.
GML: It has support for GML2, GML3, and GML-SF, the only open geospatial data model language to
define and exchange your objects.
Feature Update from Remote: An administrator can offer updating feature and vector data through the
Transactional WFS (WFS-T) interface.
Coverage Data: Support for multiple Coverage data and output formats like NITF, compresses GeoTIFF,
JPEG2000, DTED, ECW, etc.
Scalable: It is completely „Scalable. Practically the system can support thousands of concurrent users.
Depending on the performance and load on the server, by adding a single server the application can
support thousands of additional users.
Support: Supported operating system for the server are Microsoft Windows Server 2003 32-bit+ and
SOLARIS 10 UNIX. The client can also support Microsoft XP Professional.
Concurrent Users: The system allows 50 concurrent users to login in less than 0.1 sec each.
Performance The performance of the system is expected to match the response criteria as identified under ERDAS
Apollo capabilities overview. Following is the performance snapshot taken from the Apollo Technical
overview document from ERDAS.
Assumptions
500,000 Images of different format (IMG, TIFF, ECW, NITFF)
At least half of the images have most of their catalogue metadata populated
At least 1/3 have a custom queryable attributes populated Response
TEST Description Time Frame
Login 50 concurrent users - login <0.1 sec each
Catalogue Search Multiple users (> 5) querying different geographic areas
0.7 sec
Multiple users (> 5) querying same geographic area
0.7 sec
Single user querying over a large geographic area 0.2 sec
Data Harvesting Simple Harvesting data from a large enterprise production SAN with thousands of imagery
< 3 min/GB and 180,000 per day
Harvesting data from a large enterprise production SAN with thousands of imagery and with provisioning (Generate Footprints, Thumbnails and Pyramids)
< 6 min/GB and 80, 000 per day
Data Delivery 50 simultaneous users per WMS request average
< 2 sec
2000 x 2000 pixel WMS mosaic 10 sec
