NRSC Bhuvan - Mobile - Applications PDF
NRSC Bhuvan - Mobile - Applications PDF
NRSC Bhuvan - Mobile - Applications PDF
ASDCIG-Aug-2015-TR-731
nrsc
BHUVAN
MOBILE APPLICATIONS
August 2015
Security
Classification
Public
Distribution
Document (a)
Issue:
Issue-01, August,
2015
Report Type
Technical
Report No
NRSC-RSAA-ASDCIG-Aug-2015-TR-731
Title
Collation
Pages
21
Project
BHUVAN
Author(s)
10
11
(b) Revision:
Figures
11
References
2
12
Originating unit
NRSC
13
Date of Initiation
July, 2015
14
Date of Publication
August, 2015
Approved by
Director, NRSC
Contents
1.
Introduction .................................................................................................................... 1
2.
3.
4.
5.
6.
7.
8.
9.
Metadata ...................................................................................................................... 13
10.
11.
Annexure-1 ........................................................................................................................ 20
ii
List of Tables
Table 1: Development tools and technologies used for Bhuvan Mobile Applications .............. 6
Table 2: Catalog of Bhuvan Mobile Applications developed ......................................................... 7
Table 3: Metadata elements maintained for Bhuvan Mobile Applications ................................ 13
List of Figures
Figure 1: Bhuvan Mobile Applications solution architecture ......................................................... 3
Figure 2: Screen shot of Field Data Collection page ................................................................... 16
Figure 3: Screen shot of GPS option ............................................................................................. 16
Figure 4: Screen shot of Camera option........................................................................................ 16
Figure 5: Screen shot of Preview of photograph option .............................................................. 17
Figure 6: Screen shot of Attribution option .................................................................................... 17
Figure 7: Screen shot of send option ............................................................................................. 17
Figure 8: Screen shot of Save option for sending later ............................................................... 17
Figure 9: Screen shot of sending saved observation (Manage and Send Later) .................... 18
Figure 10: Screen shot of User Profile option ............................................................................... 18
Figure 11: Screen shot of Exit option ............................................................................................. 18
iii
1. Introduction
Field data collection is a mandatory process for the classification of remote sensing data
many application projects. Traditionally, the collection of data is a manual process with the
project scientists visiting the planned sites, noting down the parameters of interest, taking
photographs as required and incorporating the collected information in the final application
after returning to office. However this manual entry is not only error prone but also consumes
significant time and efforts.
Disaster management activities also rely a great deal on field information for making geospatial database of infrastructure facilities like hospitals, relief shelters and godowns. Even
during disaster-time there is need for communicating emergency messages and field
situation from disaster affected areas in near real time to operation centres for making
appropriate decisions and providing quick response.
The recent advances in the field of mobile devices, communications and global positioning
systems have made it possible to design and build innovative and effective methods of field
data collection and management. Now-a-days mobile devices are equipped with the features
like integrated GPS receiver, photo camera, GPRS/3G/4G/Wi-Fi connectivity, feature-rich
OS, etc., which can be leveraged to implement highly productive applications.
In most cases, data collection is not just limited to non-spatial data but also collecting spatial
data features e.g. line, point and polygon features using the inbuilt GPS device. The utility of
data collection process is further enhanced with the incorporation of geo-tagged field
photographs and other audio/ video/ multimedia content. Mobile technology can be used
extensively to collect field information by means of crowd sourcing.
Data collection alone is not adequate to fulfil the requirements of most applications, which
also demand near real time transmission to an operations/ management centre with
subsequent organization and management of the collected data in a central repository. With
this approach, organizations like NRSC can effectively contribute and provide support to
various operational, scientific, and societal-benefit programs via the in-house developed
smart phone-based mobile tools and the Bhuvan platform's infrastructure & services.
By implementing a mobile device based solution to streamline the data collection and
utilization process, some of the achieved benefits are given below:
The collected data is authenticated since the user invariably has to visit the site to
capture location (latitude-longitude), photographs and mandatory field attributes
Attribute values can be edited prior sending to Bhuvan Server.
Near real time visualization of the location based field data on web browser. Since the
entire process of receiving, organization of datasets and visualization datasets on the
satellite image map are automated.
Very useful for disaster mitigation, damage assessment, infrastructure periodic
monitoring projects, scientific geo-information science projects (natural resources), etc.
Bhuvan Mobile Applications
Mobile device - smart phone or tablet with 4" or better display, camera, GPS, GPRS/
3G/ 4G/ Wi-Fi, Bluetooth, mini-USB OTG, internal/ external SD card, Android O.S.
Cell phone provider network with data connectivity gateway for near real time data
transfer from field.
Mobile application on the device to enable user to collect field information.
Bhuvan server infrastructure and services to handle field data reception and
repository organization.
Bhuvan portal applications for field data geo-visualization, query and reporting.
Various users/ organizations/ stakeholders: Field data collectors, data managers,
software developers, moderators, data/ application end users, project managers,
general public.
connectivity is present. Deferred sending is also essential, when multiple attempts to send
data in near real time fail due to communication errors. The user is also provided with a
choice to edit the attribute/ parameter values (but not the geo-location or the photos) prior to
the sending the observation.
A handler programs on Bhuvan servers receive the field data from the various mobile
applications on smart phones distributed across the country under various projects. Bhuvan
is deployed in a load-balanced configuration to enable smooth data transfer and processing.
The received data is immediately organized in the respective folders and also in a spatially
enabled RDBMS.
A set of Bhuvan servers, which are responsible for geo-visualization portal services, cater to
the needs of the users and managers of each project. Each project having a mobile
application component is assigned with the necessary user profiles and roles. Appropriate
role-based access control is implemented for providing the various portal services like data
visualization on Bhuvan WMS layers, query, data download, etc. Bhuvan also enables
authorized users to access the field data from client applications in the form callable Web
Services.
6. Development Environment
The mobile applications architecture was guided by the design goal of ensuring the use
state-of-the art as well as proven technologies in the development process. At the same
time, it was envisaged to enable cross platform deployment in view of the popularity of
diverse environments like Android, iOS, Windows, etc. In view of this, the selected
development environment is based platform-independent technologies derived from Web
standards like HTML, JavaScript and CSS. The leading and proven platform conforming to
this is the free/ open source Apache Cordova, which consists of native device plug-in for all
the mobile OSs. This approach facilitates the application development to be common up to
90%, but there is still a small amount of dependence and need for platform-specific devices
and development tools/ operating systems. In view of this, the development is carried out
Bhuvan Mobile Applications
with higher priority for Android platforms, which support easier development and deployment
options.
On the server side, the primary technologies used are Apache web server, PHP application
server and Postgres/ PostGIS DBMS. Both the device-side and server-side development
follows the W3C guidelines.
The following table summarizes the various development tools and technologies used:
Table 1: Development tools and technologies used for Bhuvan Mobile Applications
Sno
Activity
Mobile Apps
1
Map visualization
Database
Mobile SDK
Android 19
Server Apps
1
Database Tier
Release
Date
Name of App
Features
User
Distribution
Mechanism
Prime
Minister's
Office
Bhuvan Protal
and proposed
on Google play
store
MNCFC
Task Team
MNCFC
Classified
Bhuvan Users
MNCFC
Task Team
MNCFC
Task Team
Version
PMO
15-Apr-15
Bhuvan Pragati
1.1
Ministry of Agriculture
5-Aug-13
1.1
18-Feb-15
1.2
29-Sep-14
Crop Cutting
Experiment
1.1
8-Oct-14
Crop Cutting
Experiment
1.1a
12-Nov-14
Crop Cutting
Experiment
1.1b
MNCFC
Classified
Bhuvan Users
1.2
MNCFC
Classified
Bhuvan Users
19-Feb-15
Crop Cutting
Experiment
30-Mar-15
Crop Damage
1.1
9/20/2013
EOAM-Horti
1.1
RRSC-S
Classified
Bhuvan Users
10
22-Dec-14
ChamanApp
1.1
MNCFC
Classified
Bhuvan Users
1.2
MNCFC
Classified
Bhuvan Users
Department
of Science &
Technology
(Technology
and Capacity
building from
NRSC, SOI
and IIRS)
Task Team
CWC
Bhuvan
CWC
Bhuvan
CWC
Bhuvan
NMCG
Bhuvan
NMCG
Bhuvan
NMCG
Bhuvan
NMCG
Bhuvan and
Google Play
store
11
19-Jul-15
BhuvanChamanapp
State RS
Punjab
Classified
Bhuvan Users
12
26-Sep-13
MANU app
1.1
19-Dec-13
AIBP
1.1
14
28-May-14
AIBP
1.1a
15
11-Jul-15
BhuvanAIBPapp
1.2
16
26-Feb-15
Bhuvan Ganga
1.1
17
12-Mar-15
Bhuvan Ganga
1.2a
18
19-Mar-15
Bhuvan Ganga
1.2b
19
1-Jul-15
1.2c
Multiple profile,
location, photos and
send or Send later
Multiple profile,
location, photos and
send or Send later
Collection page
location, photos and
send or send later,
Android-L supported
and schema V-2
location, photos and
send or send later,
Schema v-1
location, photos and
send or send later,
Android-L
supported, edit
feature and schema
V-1
location, photos and
send or send later,
Android-L supported
and schema V-2
Improved Help
27-Jan-14
IWMP app
1.1
DoLR
Bhuvan
21
16-Sep-14
IWMP app
1.1a
DoLR
Bhuvan
DoLR
Bhuvan
DoLR
Bhuvan
Panchayat
Raj Dept
Bhuvan
Panchayatsprot
al& Proposed
Google Play
Store
GAIL
Bhuvan
22
28-Jan-15
1.1b
23
8-Apr-15
1.2
Supporting Android L
24
8-Nov-14
Bhuvan Panchayats
1.1
25
9-Dec-14
GAILapp
1.1
26
20-Feb-15
Bhuvan IndiaPost
1.1
Department
of Post
Bhuvan
27
10-Mar-15
Bhuvan IndiaPost
1.2
Department
of Post
Bhuvan
28
30-Jan-15
MoLEapp
1.1
Ministry of
Labour and
Employment
Bhuvan
29
12-Feb-15
MoLEapp
1.2
Ministry of
Labour and
Employment
Bhuvan
30
5/1/2013
CAMPA
1.1
FEG
Task Team
13-Dec-14
NDRFapp
1.1
NDRF
Bhuvan
32
15-Oct-13
Phailin app
1.1
Same as earlier,
automatic folder
generation developed
General Public
Bhuvan
33
12-May-15
BhuvanEQ
1.1
NDRF
Bhuvan
34
14-Jul-15
NSSOapp
1.1
National
Sample
Survey Office
Bhuvan
Govt. of Sri
Lanka
Bhuvan
UNESCAP
35
13-Jun-14
ADA-Srilanka
1.1
36
29-Oct-14
HouseGeoTaggin
g
1.1
APSHCL
Bhuvan
37
12-Nov-14
HouseGeoTaggin
g
1.2
APSHCL
Bhuvan
38
7-Feb-15
HouseGeoTaggin
g
1.3
APSHCL
Bhuvan
39
2-Apr-15
HouseGeoTaggin
g
1.4
APSHCL
Bhuvan
40
12-Oct-14
HudHudApp
1.1
AP Govt
Bhuvan
Supporting Android
5.1, editing, view of
sent points
location, photos and
send or send later
10
Government of Karnataka
41
29-Jan-14
KFDapp
1.1
42
22-May-14
KFDapp
1.1a
43
27-Jun-14
KFDapp
1.1b
44
8-Aug-14
KFDapp
1.1a
Icon changed
Department of
Forest,
Karnataka
Bhuvan
Department of
Forest,
Karnataka
Bhuvan
Department of
Forest,
Karnataka
Bhuvan
Department of
Forest,
Karnataka
Bhuvan
ECI
Bhuvan
ECI
Bhuvan
ECI
Bhuvan
ECI
Bhuvan
ECI
Bhuvan
ECI
Bhuvan
ECI
Bhuvan
10-Feb-14
ECI_BMFapp
1.1a
46
22-Feb-14
ECI_BMFapp
1.1b
47
27-Mar-14
ECIIRapp
1.1
48
4-Apr-14
ECIIRapp
1.1.a
49
27-Apr-14
ECIIRapp
1.1b
50
29-Apr-14
ECIVechileTackin
g
1.1
51
1-May-14
ECIVechile
Tacking
1.1a
11
Department of Space
52
4-Oct-13
BhuvanPOI
1.1
53
24-Jul-14
BhuvanPOI
1.2
54
12-Mar-15
BhuvanPOI
1.2a
General Public
Bhuvan
General Public
Bhuvan
General Public
Bhuvan
General Public
Bhuvan and
Proposed
Google Play
store
ISRO
Task team
ISRO
Task team
55
6-Jul-15
BhuvanPOI
1.3
56
21-Nov-13
ISRO-DOS Sports
meet phase-1
1.1
57
28-Nov-13
ISRO-DOS Sports
meet phase-2
1.1
58
2-Jan-14
FDC Geosciences
1.1
59
9-May-14
FDC Geosciences
1.1
60
18-Jul-14
SubsidenceApp
1.1
61
28-Nov-14
EmissivityApp
1.1
62
19-May-14
NLSM
1.1
63
5-Apr-14
LiDARbetulApp
1.1
64
7-Jun-15
TraningApp
1.1
ASD&CIG
Task team
65
16-Jun-15
1.1
NRSC, Task
Team
Bhuvan
66
11-Jul-15
BhuvanIPU
1.1
NRSC, Task
Team
Bhuvan
NRSC,
Geosciences
Group
NRSC,
Geosciences
Group
NRSC,
Geosciences
Group
NRSC,
Geosciences
Group
NRSC,
Geosciences
Group
NRSC,
Forestry
Group
Task team
Task team
Task team
Task team
Task team
Task team
12
9. Metadata
With the increasing popularity of the mobile applications and a rising number of newer
requirements, it has become important to devise suitable mechanisms to keep track of the
numerous applications deployed, including new requirements and development. Accordingly,
a set of important metadata elements have been identified to manage the applications.
These metadata elements are presently maintained in basic database format and updated
regularly as required.
The metadata elements implemented so far are comprehensive enough to facilitate search,
query and preliminary configuration control. With suitable tools, the metadata can be easily
translated to the prevalent metadata standards like RDF for conformance to data exchange
standards.
Major metadata elements that are important for Mobile Apps are given in the Table 3 below:
Table 3: Metadata elements maintained for Bhuvan Mobile Applications
SNo
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Metadata
Mnemonic
Name
ProjectName
PackageName
InitiationDate
CompletionDate
Version
UserName
UserProject
UserDepartment
UserOrg
AuthorisedBy
AppSize
FeaturesDesc
ChangeLog
AttributeNames
AttributeTypes
AttributeValues
NoOfPhotos
The advantages are that they can be easily be adopted for any new development with little
effort.
13
Detailed Work Flow for Bhuvan Ganga - a mobile app for public participation in
Clean Ganga Mission
14
The user is advised to ensure GPS is switched-on with high accuracy before using the App
for data collection.
The procedure for using the App is given below. The main tasks in this App are, 1) Collecting
location information using GPS , 2) Taking photograph of the location (two photos), 3)
Adding additional information about the location and 4) Sending the collected information to
Bhuvan Ganga server on Bhuvan platform, either immediately or later.
Instructions
Step 1. The user is required to select any one option by tapping "Select from here" under
"Select the Activity". The options available are (i) Urban Sewage, (ii) Semi-Urban or Rural
Sewage, (iii) Natural drains or Nalas, (iv) Industrial Waste Water, (v) Solid Waste Disposal or
(vi) Others. The relevant icons will be enabled only after this selection.
15
16
The captured photographs may be viewed by tapping the "Preview" icon that appears below
the "Photo" icon
Open Preview
Close Preview
17
Step 7.. In order to upload the earlier saved data to Bhuvan Ganga server, "Manage" icon is
to be selected.. Then "Send Later" icon is to be selected.. This will list the data collected and
stored in the mobile. The
he data that needs to be uploaded is selected and then sent using the
"Send" icon. This will upload the data to Bhuvan Ganga server. A confirmation message
"Data sent successfully" appears once the upload is successful.
>>
Figure 9: Screen shot of sending saved observation (Manage and Send Later)
Managing data
The app provides facility for the user to manage the uploaded data. User can view the sent
data and also view any data that failed to upload. This will enable user to upload the data
again by tapping "Sent Failed" icon. There is a provision to edit attribute value in "Send
Later" and "Sent Failed" options.
The profile information can be viewed or edited using the "Profile" icon.
18
19
Annexure-1
SOFTWARE REQUIREMENTS SPECIFICATION
Mobile device application development
1)
The developed application must have very intuitive and ease-of-use features
2)
3)
The application must enable the field scientist/ user to collect the following:
Geographical location of the point in Lat, Lon (GPS)
Field photographs (0,1 or more) with direction
Multiple parameters (attribute/ value pairs)
Video, audio
4)
Must facilitate data collection for various types of end use and for different application
disciplines/ themes
5)
6)
One of the profiles must facilitate simple general purpose data collection, comprising of
GPS point, photo(s) and 2 parameter fields (say, Remarks1 and Remarks2) (to cater
to exigencies)
7)
Must also provide functionality to create new profiles on field and start collecting data
using the new profiles
8)
9)
Must support association of main project information, field data collection project
information, teams information, user information, etc in the field data collection activity
10)
The collected sample points for a particular data collection project with the device must
be numbered in sequence
11)
The software shall enable user to select the resolution/ quality of the photos, video and
audio
12)
The captured photos for each sample point must be immediately displayed on screen
before saving/ sending for checking quality and removing if necessary
13)
It must be possible to browse the details of already collected points existing on the
device with appropriate filters/queries
14)
There must be provision for deleting one or more of the collected points
15)
16)
The sequence numbers along with other information must allow for uniquely identifying
the sample point at the server-side central data repository
17)
Data and time stamping is required for each sample point and for each of the photos
18)
The captured photos must have the geotag information along with the direction
19)
The naming conventions for the XML files and photos must be clearly specified, which
preferably includes time stamping, to aid in data organization and retrieval
20
20)
The collected data must be saved on the device. Provision to be given to delete at a
later stage or based on conditions like time period, successful sent event, etc.
21)
The collected must also be organized on the device under respective folders (or any
other method) as: sent data, unsent data
22)
The unsent data must be resent based on configurable preferences: periodical retries,
manual retry, etc.
23)
It must allow transferring of collected data on the device (unsent, sent or both) to PCs
or laptops or servers. It must be possible to subsequently send such transferred data
to the central server via wired or wireless connectivity options
24)
Collected data can be sent using one or more of the following selectable transmission
technologies: GPRS, 3G, WiFi
25)
Data submission options (depending on server side implementations) are one or more
among the following selectable methods: web server/ service, email, ftp, sms
26)
The application shall enable the user to display satellite images and maps in
background with standard map navigation functionalities. While other map sources like
Google Maps can be considered, the priority is to source the data from Bhuvan
27)
The collected GPS points must be made visible on the image/ map with attribute
information and also marker symbols where appropriate
28)
There must be provision to filter/ query/ search on the points to limit the number of
points displayed at any instant
29)
Reverse geocoding functionality to be provided for the points collected with services
invoked from Bhuvan/ other sources
30)
31)
Configurability must be provided for setting many attributes and options: web server IP
address/ URL, email server address, ftp server address, SMS number, photo/ video
resolution, photos/ videos path, sent/ unsent folder paths, etc.
32)
User authentication must be provided. An admin user and a few user profiles may be
configured by default. Provision to be given for creation of new users by admin,
password reset by users, etc.
33)
Provision to be made for populating default information regarding projects, teams, etc.,
along with facility to create/ add new values on field in case of exigencies
---XXX---
21