Professional Documents
Culture Documents
Appendix B - 1
To process location data in a server and to forward the generated response to the clients.
To find location data for a mobile device-based application that can use it directly.
The current cell ID is used to locate the Base Transceiver Station (BTS) that the mobile phone is
interacting with and the location of that BTS. It is the most basic and cheapest method for this
purpose as it uses the location of the radio base station that the cell phone is connected to. A
GSM cell may be anywhere from 2 to 20 kilometers in
diameter. Other approaches used along with cell ID can achieve location granularity within 150
meters. The granularity of location information is poor due to Wide Cell Range. The advantage
is that no additional cost is attached to the handset or to the network to enable this
service.
Appendix B - 2
Place Reports - It allows the users to add new locations to the Place service, and to delete
Places that the application has added to the database. The Google Places API [8] has the
following limitations on the query processing:
Users are allowed only 1000 requests per 24 hour period which are having the API Key.
Clients who have also validated their identity through the APIs console are allowed 100 000
requests for 24 hours period. A credit card is required for authentication, for enabling billing.
3.2.1 Place Searches
A Place Search request is an HTTP URL defined in the following way
either of the following values
json shows the response in JavaScript Object Notation (JSON)
xml shows output as XML. Table 1: Place Search API Arguments.
Arguments Description
Location (required)
The latitude/longitude about which place information is to be found out. This must
be defined as latitude, longitude.
Radius (required)
Distance (in meters) about which to show Place results. types (optional) Limit the results to
places matching at least one of the pre defined types. Types must be separated with a pipe
notation (type1|type2|etc).\
Language (optional)
The language code, showing in which language the results must be shown, if
possible. name (optional) A term to be mapped against the names of
Places. Results will be limited to those having the name.
Appendix B - 3
System requirements
Version 2.x
OS version
Windows
OS X/macOS
Linux
GNOME or KDE
desktop
RAM
Disk space
500 MB disk space for Android Studio, at least 1.5 GB for Android SDK, emulator
system images, and caches
Java version
Screen
resolution
Version 1.x
Windows
OS X
Linux
RAM
Disk space
Space for
Android
SDK
Appendix B - 4
JDK version
Screen
resolution
E. Academic research being carried out and other information, techniques being learnt.
F: Brief description of the development plan for the proposed project
Location based service (LBS) is emerging as a killer application in mobile data
services thanks to the
rapid development in wireless communication and location positioning technologies.
Users with
location-aware wireless devices can query about their surroundings (e.g., finding the
nearest
restaurant or all shopping malls within 10 miles) at any place, like AIRPOT,
ATM,BANK,BOOK STORE, BUS STARION, CAFE, CLOTHING, DENTIST, DOCTOR ,
FOOD, GYM HEALTH, HOSPITAL, PARK, PARKING, PIZZA, RESTAURANT, SCHOOL
SHOPPING MALL , ETC.anytime. While this ubiquitous
computing paradigm brings great convenience for information access, the
constraints of mobile
environments, the spatial property of location-dependent data, and the mobility of
mobile users pose
a great challenge for the provision of location-based services to mobile users.
Over-view of location based Services:
LBS have two major actions, that is:
1. Obtaining the location of user
2. Utilizing this information to provide a service.
LBS Application
This represents a specific application such as a find my friends application. This
consists of a
Smartphone component, which has a number of sensors, and potentially a server
component that ncludes application-specific data (such as location-tagged
information
LBS Middleware
This wraps access to Core LBS Features (Location Tracking, GIS Provider and
Location Collection
Services) to provide a consistent interface to LBS applications.
Location Tracking
This component stores the location trace of individual users. This represents a
fundamental
Appendix B - 5
component in next-generation LBS as it contains the data that allows a users route
to be determined
and potentially predicted. In particular, this component would typically support the
following
functionality:
1. Keep records on users current and past locations.
2. Notify other components when a specific user has moved, or when they move in
or out of an area.
This supports location-based notifications being sent to users.
3. Determine which users are within a defined location this supports geocasting
features.
4. Queries of location trace to generate user movement models
GIS Provider
This component provides geospatial functionality for many LBSs including map
information, map
visualization and directory services. Google Maps with its API can be considered a
GIS provider.
Location Collection Service
This component performs location collection to get a latitude and longitude for a
specific user.
Depending on the technology, this component may be accessed via the LBS
Middleware (e.g.,
mobile network triangulation via a service provider) or directly (e.g., via GPS
receiver in the
Smartphone).
Android provides access to the above components to facilitate the implementation
of LBS services
through the help of following classes;
1. Location Manager
2. Location Provider
3. Geocoding
4. Google-Map
Location Manager
Location Manager Class of android is present to manage all other components
needed to establish a
LBS system.
Location provider
Location provider represents the technology to determine the physical location i.e.
to handle GIS.
Location Provider component of Android application is a present to facilitate the
determination of
available provider and selection of suitable one.
Finding the List of Available Location Provider To get a list of names for all the
providers available on the device, call get Providers, using a Boolean to indicate if
you want all, or only the enabled, providers to be returned:
G. Brief description of the evaluation and test plan for the proposed project
a. Navigation users get route maps to a particular destination, real time traffic
routing that takes into account actual congestion patterns etc.
Appendix B - 6
Appendix B - 7