INDUSTRIAL PROJECT REPORT

Internship project report on

Geofencing for EC Sockets in Indian Railways

submitted in partial fulfilment of the

Requirements for the award of

Bachelor of Engineering
in
School of Electronics and Communication
Engineering

Carried out at
South Western Railways, Hubballi
Submitted By : Basavaraj Sajjan
01FE18BEC040

Under the guidance of

Prof. Vishal Pattanshetti Mr. B.V.Ganji
Prof. Vijay H.M SSE/Tele/Control
College Guide Industry Guide
KLE Technological University South Western Railways

SUBMITTED TO:
School of Electronics and Communication Engineering
KLE TECHNOLOGICAL UNIVERSITY
Hubballi

1
 DECLARATION

I hereby declare that the Industrial Internship Project Report entitled ”GEOFENCING
FOR EC SOCKETS IN INDIAN RAILWAYS” is an authentic record of our work
as per the requirements of the Industrial Internship Project during the period from Jan
10 2022 to May 31 2022 for the award of the degree of Bachelor of Engineering at KLE
Technological University, Hubballi under the guidance of Prof. Vishal Pattanshetti
and Prof. Vijay H.M.

Basavaraj sajjan
01FE18BEC040

Date :

2
3
 K.L.E SOCIETY’S
KLE Technological University,
Hubballi-580031
2021-2022

SCHOOL OF ELECTRONICS AND COMMUNICATION

ENGINEERING

CERTIFICATE

This is to certify that the internship project entitled “Geofencing for EC Sockets in
Indian Railways” is a bonafide work carried out by “Basavaraj Sajjan”, bearing
University Seat No. 01FE18BEC118 in South Western Railway company, in partial
fulfillment for the award for Bachelor of Engineering in Electronics and Communication
in the School of Electronics and Communication Engineering of KLE Technological
University, Hubballi for the academic year 2021-2022.

Prof. Vishal Pattanshetti Dr. Nalini C. Iyer Dr. N.H.Ayachit

Prof. Vijay H.M
Guide Head of School Registrar

External Viva:

Name of Examiners Signature with date

1.

2.

4
 ACKNOWLEDGMENT
The feeling of fulfillment that lies within the effective completion of “Geofencing for
EC Sockets in Indian Railways” would be unfinished without citing the names of the
individuals who made a difference in completing this project as their consistent direction,
support, and encouragement brought about in its realization. We are thankful to our
esteemed institute KLE Technological University, Hubballi which has provided us an
opportunity to fulfill the most cherished desire to reach our goal. We express a deep sense
of appreciation to our Head of School of Electronics and Communication, Dr. Nalini Iyer
for giving the motivation and direction required for taking this Internship Project to its
completion. We sincerely thank our Guide Prof. Vishal Pattanshetti for his consistent
support and suggestions. We also thank Prof. Vijay H.M for his guidance and support.
We also thank Mr. B.V.Ganji our Industry guide for his guidance and support. Finally,
we would like to thank all those who either specifically or in an indirect way made a
difference in this project. We offer profound appreciation to our guardians who have
acknowledged, encouraged, and helped in our endeavor.

-Basavaraj Sajjan

5
 COMPANY PROFILE
Indian Railways (IR) is the state-claimed railway organization of India. Indian Railways
had, until of late, a restraining infrastructure on the nation’s rail transport. It is one of
the biggest and busiest rails arranged on the planet, moving a little more than six billion
travelers and just about 750 million tonnes of cargo every year. IR is the world’s biggest
business or utility manager, with more than 1.6 million workers.

The railroads cross the length and width of the nation; the courses spread a complete
length of 63,940 km (39,230 miles). Starting in 2005 IR possesses a sum of 216,717 carts,
39,936 mentors, and 7,339 trains and runs an aggregate of 14,244 trains day by day,
including around 8,002 traveler trains.

Railroads were first acquainted with India in 1853. By 1947, the time of India’s Indepen-
dence, there were forty-two rail frameworks. In 1951 the frameworks were nationalized as
one unit, getting probably the biggest system on the planet. Indian Railways works both
significant distance and rural rail frameworks.

As of walk 2017, Indian Railways’ moving stock comprised 277,987 cargo carts, 70937
traveler mentors, and 11,452 trains and mentor creation offices in a few areas in India.
Being the world’s eighth-biggest boss, it had 1.30 million workers as of March 2016. Indian
Railways is divided into several zones, which are further subdivided into divisions.

The number of zones in Indian Railways increased from 6 to 8 in 1951,9 in 1952 and 16
in 2003. Each Zonal railway is made up of a certain number of divisions, each having a
divisional headquarters. There is a total of 68 divisions. Each of the 16 zones is headed
by its respective General Manager who reports directly to Railway Board. The zones are
further divided into divisions under the control of the Divisional Railway Manager (DRM).
South Western Railway is one of the 16 zones of the Indian Railway and is subdivided
into 3 divisions, namely:

1. Hubballi

2. Mysore

3. Bangalore

South-Western Railway was created by amalgamating the reorganized Hubballi division

from South Central Railway with the Bangalore and Mysore divisions of the Southern
railway. This railway has become operational on 1st April 2003 with its headquarters at
Hubballi in the state of Karnataka.

6
 ABSTRACT
A geo-fence is a virtual perimeter of interest that can be set up to fire notifications when
it is entered or exited or both. For example, a geo fencing app can alert us that an
employee has left a previously specified area. The project presents geofencing for EC
Sockets in Indian Railways using GPS. This system comprises a webpage that can track
the location of the user, user can upload a picture of the EC Sockets for authentication
and a description of its condition. Admin can check the uploaded data and verify it. The
system detects the location of the user through geolocation and Google Maps APIs. The
detected location consists of the longitude and latitude of the user, after detecting the
latitude and longitude, we use reverse geocoding to convert those latitudes and longitude
into the exact name of the location. Further, the detected location will get stored on
the firebase database. The admin or the supervisor can check that data on the website.
The technique of Vue.js is selected which is an open-source javascript framework. Vue.js
is used because it has an easier learning curve, which makes it faster to master and vue
uses templates which makes the process simpler and faster. Vue.js combines the top-level
features of React and Angular. Javascript which is an interpreted programming language
is used for designing network-centric applications. For storing the data, the cloud-based
database Firebase is used in which data is stored in JSON. Vuetify is used for webpage
designing, which is a Vue UI library with handcrafted components with material design
specifications for building any website or application.

7
Contents

1 Introduction 11
1.1 Motivation...................................................................................................................... 11
1.2 Literature survey...........................................................................................................11
1.3 Problem statement....................................................................................................... 14
1.4 Objectives....................................................................................................................... 14
1.5 Organization of the report.......................................................................................... 14

2 System design 15
2.1 Dataflow Diagram.........................................................................................................15
2.2 Functional block diagram....................................................................................16
2.3 Design alternatives....................................................................................................... 16
2.4 Final design......................................................................................................... 16

3 Implementation details 17
3.1 Algorithm.............................................................................................................17
3.2 Flowchart........................................................................................................................ 18
3.3 Software Requirements................................................................................................ 18

4 Results and discussions 19

4.1 Result Analysis.................................................................................................... 19

5 Conclusions and future scope 28

5.1 Conclusion...................................................................................................................... 28
5.2 Future scope.................................................................................................................. 28

References 28

Appendix 30

8
List of Figures

2.1 Dataflow Diagram......................................................................................................... 15

2.2 Functional Block Diagram.................................................................................. 16

3.1 Flowchart........................................................................................................................18

4.1 Default Login Page............................................................................................. 20

4.2 Login Page With Credentials..............................................................................21
4.3 Chat Window................................................................................................................. 22
4.4 Google Maps Window.................................................................................................. 23
4.5 Sign-up Page....................................................................................................... 24
4.6 Sign in Page........................................................................................................ 24
4.7 Home Page.....................................................................................................................25
4.8 Data Upload Page......................................................................................................... 25
4.9 Choose date.................................................................................................................... 26
4.10 Choose time................................................................................................................... 26
4.11 View uploaded data......................................................................................................26
4.12 Details of the uploaded data.......................................................................................27

5.1 Details of the uploaded data.......................................................................................30

5.2 Details of the uploaded data.......................................................................................31

9
Chapter 1

Introduction

A geo-fence is a virtual boundary of interest that may be configured to send alerts when
it is entered, exited, or both. A geo-fence program, for example, can notify us when an
employee leaves a previously defined region.

Some geofences are set up to monitor activities in secure regions, alerting management
when someone enters or exits a certain area. Geofencing can also be used by businesses
to monitor employees in the field, automate time cards, and maintain track of company
property.

1.1 Motivation
The issue of security is very paramount in any organization, especially in an organization
such as Railways. Geo-fencing software is recently been applied to user applications such
as media, various publications, advertisements, wildlife monitoring, and many other recre-
ational activities. Current geo-fencing systems work with virtual geographical boundaries.
We try to present a generic approach for the present geofencing system and demonstrate
how it can be presented in practice. The concept of security and concern for people has
made us take up this project.

In Railways, at every 1km, there is an EC post which is used for emergency communi-
cation, those need to be properly maintained so that during emergencies they are in a
working condition. These EC sockets have to be checked every week by a trackman. We
were asked to develop a website where we can track the position of the trackman so that
we can monitor his activity.

1.2 Literature survey

In this paper, the system designed on the Plot Researches Geofences with a radius of
between 50 to 50,000 meters can be created. This specification covers the requirements
and provision of tests and inspection of the Auto Dialing System for Emergency Socket.
The system includes one Way side Telephone and one Base Station Unit. The Wayside
Tele- phone shall work from existing Emergency Sockets provided alongside the Railway
Track for talking to the control office on Underground RE/Quad Cable Communication
Network and Base Station Unit shall be fitted in the Test Room and shall work as part
of the overall system. The system is also capable of connecting Railway Exchange or

10
DOT Exchange by pressing the designated button from the Wayside telephone through
Test Room Equipment. The Wayside Telephone will work similar to Auto Telephone and
shall become a subscriber of Railway Telephone Exchange by pressing (*) Star and shall
be-come to a subscriber of DOT telephone exchange by pressing hash. The Connectivity
can be achieved automatically through the Base Station Unit provided in the Test Room.
A 4-Wire DTMF Telephone shall be connected to the Tx and Rx terminal of the base unit
and a 2-Wire Control Telephone at the 2-Wire terminal. Railway Exchange terminal to
Railway Exchange line and DOT terminal to DOT Exchange line. The following operation
of the base unit can be checked:
1. Clarity of speech between the telephone

2. Loudness of Voice and action of volume control in loudspeaker circuit

3. Operation of Relay 1 and Relay 2

4. Dial tone and Ring back of both exchanges

5. Conversation between 4-Wire DTMF telephone to both subscriber telephone (Rly

and DOT) one by one

6. Indication and numeric display

[2] The present level of location-based services delivers spatial information to mobile users
based on GPS sensor position data. However, the geographical information distribution
service occasionally includes undesirable information. A new spatial information delivery
system is proposed in the proposed system to improve the integrity of geographical infor-
mation delivery. An experiment is carried out with an Indoor Messaging System and an
accelerometer, and it is found that the approach may identify user activity without gaining
access to personal information and limit the amount of spam information. The technique
is projected to provide the following three benefits. First, based on dynamic information
selection matching the user’s status, the user can automatically get only information of
interest. Second, it may identify a user’s status without requiring any personal infor-
mation. Third, utilizing sensors put on mobile interfaces can estimate user states. The
method needs users to collect position and acceleration data at the same time. The exper-
iment confirmed that position determination utilizing momentary IMES signal strength
was unreliable in interior situations due to interference and multipath. The emphasis is
primarily on improving spatial information distribution for mobile interfaces in indoor
environments, and an approach to estimating user status using location and acceleration
data from mobile interfaces, without personal data, is proposed to achieve precise spatial
information reporting. Furthermore, in an indoor experiment, the technique may provide
dynamic information selected based on a combination of the IMES and acceleration sen-
sors.

In this study[3], on the hardware side, real-time tracking and geofencing were accom-
plished by detecting the distance between coordinates. After the data is transmitted to
the server, the geofence operation is done on the map application screen. Geofences may
be created using not only circles but also polygons related to the user’s design. The
program may be used to track down youngsters. If the child is playing in the yard of
the home and the geofence area is determined to encompass the perimeter of the house,
the geofence will alert when the child travels away from the house. The geofence region

11
is adjusted in two ways in this scenario: static and dynamic. Predefined static polygon.
The child’s home is always characterized as static since the school he or she attends is
always immutable. The fact that a polygon formed in real-time in a freshly traversed
region may be utilized as a geofence without storing is referred to as dynamic geofence,
and it has supplied the study with a highly flexible application. As a web system, NodeJS
is chosen. The JavaScript programming language is used on both the server and client
sides. Because it just delivers HTML output to the user portion, it is more secure than
other systems. The Leaflet library is also a piece of open-source mapping software. It was
used to create a user-friendly web application with many libraries. GPS data has been
mistaken for a variety of reasons. Its goal is to minimize data error rates to make the
system function quicker and more stable. The problem is narrowly focused, and several
techniques have been devised. The Kalman filter was the most popular of them. The
outcomes of the three approaches are compared. Moving average, logistic regression, and
the Kalman filter were used to reduce errors. The parameter value in the moving average
that reduces the error the greatest is computed as 10 and applied in this manner. The
fact that no estimation value is obtained for the first ten data points is a bad scenario in
this technique. The Kalman filter’s input parameters are also significant when working
with GPS data. The parameter value that was utilized in logistic regression analysis is 9.
Three sample points were identified and measurements were taken at these locations to
get reliable GPS data values to test whether the algorithm findings were valid. The real
position value is based on more sophisticated GPS equipment with a margin of error of
1-2 cm. In comparison to this value, the Kalman filter lowers the greatest errors for all
locations. The experiment was carried out both outside and in a low-density structure.
As a result, the data’s average inaccuracy value was roughly 2 meters.
This paper[1]investigates a GPS-based position tracking system with geofencing features.
This system offers a high-security technique for preventing vehicle theft. It also leveraged
the Internet of Things to deliver a notification to the user based on the location’s limits
(IoT). In this study, the system was able to simply monitor and track the location of the
automobile, as well as generate an alarm when the vehicle exited the geofence region. This
system’s hardware and software components were separated. The ESP8266 NodeMCU
and GPS module were among the hardware components, while Google Maps and the IoT
platform were among the software components. The administrator was able to monitor
the vehicle via computer, and the notification alarm was set off. When the automobile
left or entered the geofence region, a notification alert was sent to the admin’s registered
email account. Driving around the geofence zone put the prototype system to the test.
The results showed the correct position of the vehicle as well as an email notification alert
when it left or entered the borders. When compared to the real map on the mobile phone,
the location accuracy is roughly 95 percent. The system design was comprised of hardware
and software components. The hardware components included an ESP8266 NodeMCU, a
GPS module, and a WiFi receiver. The IoT cloud-based software components were used.
The IoT cloud also serves as a platform for administrators to access information and
preserve data. The GPS data was transmitted to this platform through the NodeMCU
signal from the GPS. The NodeMCU then used the Ubidots Token that was included in
the source code to send a signal to the Ubidots cloud with the latitude and longitude
format. The data was continuously taken from the NEO 6M GPS Module, which was
connected to the ESP8266 NodeMCU. Ubidots contained a map widget that connected
with Google Maps to show the location. The latitude and longitude of the gadget were
shown on the Ubidots platform. The geofencing was then built using Google Maps by

12
drawing the geographical bounds of the specific location to monitor the car. Typically,
the admin or developer will define the bounds of the geo-fence region. So, if an automobile
was within this geofence, it was determined to be in a certain location.

1.3 Problem statement

To build a web application for geofencing the EC Sockets using javascript an interpreted
programming language and vue.js open-source framework to track the static position of
the trackman for maintenance of the EC socket.

1.4 Objectives
1. To build a website where a user can upload his current location, photo of the EC
Socket, and add a description about the condition of the EC Socket.

2. Admin should be able to view the uploaded data by the user and can approve or
deny it.

3. To track the static position of the trackman at a particular EC post and verify
whether he has checked the EC post or not.

1.5 Organization of the report

1. Chapter 1 which is the current chapter gives brief description about the introduc-
tion, motivation, objectives, literature survey and problem statement.

2. Chapter 2 System design describes the block diagram of the system and the final
solution.

3. Chapter 3 Implementation details describes the algorithm and flow of the system
designed along with the specifications and detail explanation of all the stages.

4. Chapter 4 is the discussion on the results obtained from the system.

5. Chapter 5 is the conclusion of the project with the discussion on the future scope.

13
Chapter 2

System design

System design elaborates the functions, that the system should perform and the various
means of achieving these functions.This section details the proposed design.

2.1 Dataflow Diagram

Figure 2.1: Dataflow Diagram

In fig 2.1, the dataflow diagram can be seen, when the user opens the webpage by entering
the credentials and sends his/her location, the request is sent to the server to access the
location of the user. The admin gives the permission and sends it to the server. The server
sends the location of the user to the commuter through the webpage, and the location of
the user is displayed on the map layout.

14
2.2 Functional block diagram
The following fig 2.2, is the proposed Functional block diagram of the system which helps
us in understanding the system and it’s functions better and be expressed in brief.

Figure 2.2: Functional Block Diagram

2.3 Design alternatives

1. Receiving location : GLONASS
Sending location to database: Real-time database
Displaying location to the commuters: App

2. Receiving location :NavIC

Sending location to database: Cloud database
Displaying location to the commuters: Google Earth

3. Receiving location : GPS module

Sending location to database: Server
Displaying location to the commuters: Webpage

2.4 Final design

We select one of the optimal solutions based on its working and ease of the implementation.

The system detects the location of the user through geolocation and Google Maps APIs.
The detected location consists of the longitude and latitude of the user. After detecting the
latitude and longitude, we use reverse geocoding to convert those latitudes and longitude
into the exact name of the location. The user can upload the image of the EC socket after
checking it and add a description of its condition and select the date and time and submit
the details. Further, the detected location will get stored on the firebase database. The
admin or the supervisor can check that data on the website.

15
Chapter 3

Implementation details

In this Chapter, the system specifications with the architecture are explained. The used
algorithms are defined and described with examples. The implementation details of the
proposed system along with its algorithms are discussed.

3.1 Algorithm
1. The Railway Tester will go to check working of EC-Socket .
• Takes the snapshot from his mobile phone.
• Go to the website and Upload the Details of the EC Socket (title, description,
date and time).

2. Click on the ’Detect Location’ icon which detects his exact location.
• It will fetch latitudes and longitudes of his location using Geolocation API and
Google Maps API.
• The fetched Latitudes and Longitudes will be converted into the name of that
location using ’Reverse Geocodoing’.
• His location then gets stored on the database of the website.
3. Upload the Snapshot of EC Socket.
• On clicking ’Upload Image’ feature of the website, it will open his mobile gallery
from which he can upload the taken snapshot of ec socket.
• Image and other Uploaded details of the EC Socket gets stored on the database
of the website.

4. Admin will View and Verify the uploaded data

• The uploaded data from database will be reflected on the website.
• The Admin will check the uploaded details of the EC Socket.
• Click on Verify button if he found the details satisfactory.
• Click on Test-Again button if he want the EC Socket to be checked again.

16
3.2 Flowchart

Figure 3.1: Flowchart

The above flowchart in fig 3.1, explains the step by step process of the proposed algorithm.

3.3 Software Requirements

The following have been used to build the website,

JavaScript: Interpreted Programming language designed for network-centric application.

Vue.js: Open-Source JavaScript Framework

Vuetify: Vue UI Library with hand crafted components with material design specifications
for building any website or application.

Firebase Database: Cloud hosted database in which data is stored JSON.

17
Chapter 4

Results and discussions

This section involves the final project results. It concludes the strategies and plans into
the final set of results. Initially, the webpage was built that showed only the static location
of the railman to the admin. Also, there is the same webpage interface for both users and
admin. Railman can send his/her static location to the webpage with a message regarding
the working of the EC Sockets whether it is working properly or not.

4.1 Result Analysis

Initially, the final result was a system used to track the railman through Mobile GPS
by interfacing the Google Map. The technique of node.js and express.js is selected, both
node.js and express.js are backend and frontend JavaScript run time environments respec-
tively. This system sends the location to the navigator through coordinates. It builds a
Google map link and pastes it into the webpage. The coding is done in JavaScript and
deployed on a hosting platform HEROKU. Heroku is a cloud platform as a service support-
ing several programming languages.Node.js is an open-source, cross-platform, back-end
JavaScript runtime environment that runs on the V8 engine and executes JavaScript code
outside a web browser.Express.js or simply Express is a back end web application frame-
work for Node.js, released as free and open-source software under the MIT License. It is
designed for building web applications and APIs. It has been called the de facto standard
server framework for Node.js. Once code is deployed on HEROKU, the webpage interface
appeared. Figure 4.1 below depicts the home screen for the user. Users can log in with
names and a particular room number in which the admin is present.

This system’s main objective is to track vehicles to get the location of Mobile GPS and
send it to the commuters through the server. The proposed system allows commuters to
check the location of railman through a link sent on the webpage which directs the user
to Google maps. This objective has been met successfully. The general evaluation result
is that the system proved to be reliable as to view the location of the vehicles. Here in
figure 4.2, the user enters his credentials such as his Name and enters a particular room
number (for example 101) in which the admin is present to check the location of the user.

18
 Figure 4.1: Default Login Page

As the user enters the credentials, he/she will be directed to the page (room) where the
admin can see other online users and their messages in the chat window. User can send the
location of his own which can be accessed by the admin and explain about the working of
the EC sockets. Admin then track user static location in the google map interface.These
features are shown in the fig 4.3 and fig 4.4.

The proposed system can be further modified by installing the GPS/GSM modules in
any device for tracking purposes and accessing the device location through them. The
webpage can be converted to an android application like IRCTC rail connect which can
reach maximum commuters and help them with the location of the user. In the future,
the system can also be used for tracking goods vehicles, Fleet vehicles, Taxi networks,
and many more.

Drawback of this project was that Admin cannot able to see the pictures of the EC sockets
whether the Railman repairs it correctly or not. Also, Railman needs to update the date
and time manually which he/she can enter false data as well. To avoid this, a webpage is
required which have not only a location tracking option but also uploading data features
including pictures, description of picture, date and time of data submission, etc.

19
 Figure 4.2: Login Page With Credentials

Later we designed an alternate webpage with several features for user and admin both.
Users can upload photos, send present and static locations for tracking purposes, data
submission date and time, write a description about the EC Sockets whether the socket
is working fine or not, and many more. Admin can recheck and verify whether the data
uploaded by the user is fine or not. Admin can track the user’s present and static location.

In figure 4.5, the sign-up page interface is shown in which the user can register him-
self/herself on the webpage by using email-ID and a password. In this system, Vue.js
is used which is an Open Source JavaScript Framework. It is used to build single-page,
client-side applications. Real-time data streaming is not handled by VueJS. It’s more
efficient as compared to node.js which we used initially as It allows you to run JavaScript
code on the server-side and Handles requests from the browser. Real-time data streaming
is handled easily in node js.

20
 Figure 4.3: Chat Window

In figure 4.6, the sign-in page is shown which appears for the already registered users.

In figure 4.7, the home page is shown which has the features like uploading new data and
viewing uploaded data. The Railway Tester will go to check the working of EC-Socket.
Takes the snapshot from his mobile phone. Go to the website and Upload the Details of
the EC Socket (title, description, date, and time)

21
 Figure 4.4: Google Maps Window

In figure 4.8, the user can upload the following data including Title, Location, Image of the
tested EC Socket, and write a description about it. By clicking on the ’Detect Location’
icon which detects his exact location. It will fetch latitudes and longitudes of his location
using Geolocation API and Google Map API. The fetched Latitudes and Longitudes will
be converted into the name of that location using ’Reverse Geocodoing’.His location then
gets stored on the database of the website.

In figures 4.9 and 4.10, the user can choose the date and time or it will be taken auto-
matically. Also, he can upload the Snapshot of the EC Socket. On clicking the ’Upload
Image’ feature of the website, it will open his mobile gallery from which he can upload
the taken snapshot of the EC socket. Image and other Uploaded details of the EC Socket
get stored on the database of the website.

In the figure 4.11, the user can view the uploaded data.

In the figure 4.12, the admin can view the image uploaded along with the date, time
and description and verify it.The uploaded data from database will be reflected on the
website.The Admin will check the uploaded details of the EC Socket.Click on Verify
button if he found the details satisfactory.Click on Test-Again button if he want the EC
Socket to be checked again

22
Figure 4.5: Sign-up Page

Figure 4.6: Sign in Page

23
 Figure 4.7: Home Page

Figure 4.8: Data Upload Page

24
 Figure 4.9: Choose date

Figure 4.10: Choose time

Figure 4.11: View uploaded data

25
Figure 4.12: Details of the uploaded data

26
Chapter 5

Conclusions and future scope

5.1 Conclusion
The project’s main goal is to develop a website where the user can upload data, photos
and his location when he is checking the EC posts, and the admin can view this uploaded
data and verify the authenticity. The objectives of the project have been met succesfully.
This system helps the railways to monitor the functioning of the EC Sockets in a better
way.

5.2 Future scope

The project can be further improved by adding features like, creating a sepearte list for a
particular EC post, where all the previous data uploaded related to that post is stacked.
We can also add a feature where we can see all the EC posts in a list and it displays
whether that EC post has been checked or not.

27
Bibliography

[1] AH Abbas, Mohammed I Habelalmateen, Syukran Jurdi, Lukman Audah, and NAM
Alduais. Gps based location monitoring system with geo-fencing capabilities. In AIP
Conference Proceedings, volume 2173, page 020014. AIP Publishing LLC, 2019.

[2] Masafumi Nakagawa. Improvement in the geofencing service interface using indoor
positioning systems and mobile sensors. International Archives of the Photogramme-
try, Remote Sensing and Spatial Information Sciences, 4:W4, 2013.

[3] Zeynep ÖZDEMİR and Bülent TUĞRUL. Geofencing on the real-time gps tracking
system and improving gps accuracy with moving average, kalman filter and logistic
regression analysis. In 2019 3rd International Symposium on Multidisciplinary Studies
and Innovative Technologies (ISMSIT), pages 1–6. IEEE, 2019.

28
Figure 5.1: Details of the uploaded data

29
Figure 5.2: Details of the uploaded data

30