A Project by Sanat Kulkarni and Aditya Dutt

👉🏽 Objective :- The app will enable emergency operators to send a link to the victim/bystander, which, when clicked, fetches their location and relays it to the nearest ambulance. Additionally, it contains ERP portal for operators and administrators to manage and monitor emergency responses.

Table of Contents

1. Introduction

   1. Key Objectives

2. Getting Started

   1. System Requirements

   2. Installation

3. User Roles

   1. Admin

   2. Operator

4. Features

   1. Admin Dashboard

   2. Operator Dashboard

   3. Automatic Email Sending

   4. Automatic Location Fetching

   5. Ambulance Tracking

5. Detailed Instructions

   1. Sign In

   2. Managing Operators

   3. Managing Ambulances

   4. Managing Cases

   5. Profile Management

   6. Automatic Email Sending

   7. Automatic Location Fetching

   8. Ambulance Tracking

   9. Logging Out

6. Troubleshooting

7. Contact Support

---

Introduction

---

The Emergency Location Management System is a comprehensive solution designed to streamline the management of emergency operators, ambulances, and cases. This system is built to enhance the efficiency and effectiveness of emergency response teams by providing real-time data and automated processes.

Key Objectives

• Efficiency: Reduce response times by providing operators with real-time information and automated tools.

• Accuracy: Ensure precise location tracking of ambulances and operators to facilitate quick dispatch and coordination.

• Accountability: Maintain detailed records of all operations, including case management, operator activities, and ambulance usage.

---

About the Decisions

React.js (Frontend):
Chosen for its component-based architecture, which facilitates building complex, reusable UI elements like dashboards and tables. Its large community support, extensive libraries (e.g., react-leaflet), and efficient rendering (virtual DOM) make it suitable for interactive applications. State management libraries help manage application complexity.

Node.js/Express.js (Backend):
Selected due to its non-blocking I/O model, making it efficient for handling concurrent connections (important for location updates). JavaScript ecosystem alignment with the frontend simplifies development (full-stack JS). Large npm registry provides readily available packages for authentication (JWT), database interaction, email, etc. Well-suited for building REST APIs.

MongoDB/PostgreSQL (Choose One):

• MongoDB: Its flexible schema is advantageous for storing potentially varied case information and user profiles. Built-in geospatial capabilities are sufficient for storing and querying coordinates.

• PostgreSQL with PostGIS: Offers robust ACID compliance and relational integrity. PostGIS provides powerful geospatial functions beyond simple storage, potentially useful for future enhancements like proximity queries or route analysis.

JWT (JSON Web Tokens):
Used for authentication as it provides a stateless mechanism. Once the user logs in, the frontend stores the token and sends it with each request, eliminating the need for server-side session management and simplifying scalability.

---

Architectural Decisions

Multi-Tiered Architecture:
Adopted to enforce separation of concerns. The frontend handles presentation, the backend manages business logic and data access, and the database handles persistence. This makes the system easier to develop, test, maintain, and potentially scale different tiers independently.

RESTful APIs:
Chosen as the communication standard between frontend and backend due to its simplicity, statelessness, and wide adoption. It allows for clear definition of resources and actions.

---

Location Sharing Mechanism

Link-Based Approach:
Preferred over requiring a dedicated mobile app installation for callers/drivers because it maximizes accessibility. Anyone with a smartphone browser can use it instantly without prior setup, which is crucial in emergency situations.

Email Delivery (Demo):
Used as the initial delivery method as it's straightforward to implement. SMS is a critical alternative for future development, potentially offering faster delivery and higher open rates in emergencies.

Browser Geolocation API:
Leveraged as the standard, cross-platform way to access device location services directly from the web page, avoiding the need for native code.

---

Authentication and Authorization

Role-Based Access Control (RBAC):
Implemented to ensure users can only access functionalities relevant to their roles (Admin vs. Operator). The user's role is typically embedded within the JWT and checked by backend middleware on protected routes.

---

Mapping Technology Selection

OpenStreetMap (OSM) & Leaflet.js:
Chosen primarily because they are open-source and free to use, avoiding the potentially high costs associated with commercial mapping platforms like Google Maps Platform for extensive usage (especially tile serving and tracking). Leaflet is a lightweight, flexible, and widely used JavaScript library for interactive maps, well-suited for displaying markers and potentially routes.

Google Maps (Redirection):
Used for showing a specific case location, via URL redirection (maps.google.com?q=...). This leverages Google's familiar interface and powerful search/direction features for the operator without incurring API costs for simple point visualization.

---

Data Management Strategy

• Unique identifiers (UUIDs) are used for cases and location links to ensure security and prevent trivial guessing of links.

• Location data is timestamped to provide context.

• Case status (active, closed, etc.) helps operators manage workflow.

• Ambulance status (available, busy) aids in dispatch decisions.

---

Real-time Communication Approach

Ambulance Tracking:
Periodic polling (driver's device repeatedly sending location via HTTPS POST). This allows the driver's device to maintain a persistent connection to the backend and push location updates instantly, enabling smoother, near real-time tracking visualization on the operator's map with less overhead.

---

Getting Started

---

System Requirements

• Web browser (Chrome, Firefox, Safari, Edge)

• Internet connection

Installation

1. Clone the repository:

git clone <https://github.com/SanatKulkarni/Emergency-Location.git>

1. Navigate to the project directory:

cd emergency-location

1. Install dependencies:

npm install

1. Start the development server:

npm run dev

---

User Roles

---

Admin

Admins have access to the Admin Dashboard, where they can manage operators, ambulances, and cases.

Operator

Operators have access to the Operator Dashboard, where they can manage active cases and view available ambulances.

---

Features

---

Admin Dashboard

• Overview: View statistics on total operators, total cases, active cases, and total ambulances.

• Manage Operators: Add, edit, and delete operators.

• Manage Ambulances: Add, edit, and delete ambulances.

• Manage Cases: Add, edit, and delete cases.

Operator Dashboard

• Active Cases: View and manage active cases.

• Available Ambulances: View available ambulances.

Automatic Email Sending

• Email Notifications: Automatically send emails when a person calls for an Ambulance.

Automatic Location Fetching

• Location Tracking: Automatically fetch and push the location data of ambulances and operators to the server.

Ambulance Tracking

• Real-Time Tracking: Monitor the real-time location of ambulances on a map.

---

Detailed Instructions

---

Sign In

1. Navigate to the sign-in page.

2. Enter your email and password.

3. Click the "Sign In" button.

4. Based on your role, you will be redirected to the appropriate dashboard.

Managing Operators

1. Navigate to the "Operators" section in the Admin Dashboard.

2. Add Operator:

   1. Click the "Add Operator" button.

   2. Fill in the operator details in the modal form.

   3. Click "Save" to add the operator.

3. Edit Operator:

   1. Click the "Edit" button next to the operator you want to edit.

   2. Update the operator details in the modal form.

   3. Click "Save" to update the operator.

4. Delete Operator:

   1. Click the "Delete" button next to the operator you want to delete.

   2. Confirm the deletion in the prompt.

Managing Ambulances

1. Navigate to the "Ambulances" section in the Admin Dashboard.

2. Add Ambulance:

   1. Click the "Add Ambulance" button.

   2. Fill in the ambulance details in the modal form.

   3. Click "Save" to add the ambulance.

3. Edit Ambulance:

   1. Click the "Edit" button next to the ambulance you want to edit.

   2. Update the ambulance details in the modal form.

   3. Click "Save" to update the ambulance.

4. Delete Ambulance:

   1. Click the "Delete" button next to the ambulance you want to delete.

   2. Confirm the deletion in the prompt.

Managing Cases

1. Navigate to the "Cases" section in the Admin Dashboard.

2. Add Case:

   1. Click the "Add Case" button.

   2. Fill in the case details in the modal form.

   3. Click "Save" to add the case.

3. Edit Case:

   1. Click the "Edit" button next to the case you want to edit.

   2. Update the case details in the modal form.

   3. Click "Save" to update the case.

4. Delete Case:

   1. Click the "Delete" button next to the case you want to delete.

   2. Confirm the deletion in the prompt.

Profile Management

1. Navigate to the "Profile" section.

2. View and update your profile details.

3. Save any changes made to your profile.

Automatic Email Sending

1. The system will automatically send emails when a person calls for an Ambulance.

2. Ensure your email address is correctly provided to receive notifications.

Automatic Location Fetching

1. The system will automatically fetch and push the location data of ambulances and operators to the server.

2. Ensure location services are enabled on your device for accurate tracking.

Ambulance Tracking

1. Navigate to the "Ambulance Tracking" section in the Operator Dashboard.

2. View the real-time location of all available ambulances on the map.

3. Click on an ambulance marker to view its details, including current status and location coordinates.

Logging Out

1. Click the "Logout" button in the dashboard.

2. Confirm the logout action.

---

Troubleshooting

---

• Failed to load data: Ensure you have a stable internet connection. If the problem persists, contact support.

• Sign-in issues: Verify your email and password. If you forgot your password, use the password recovery option.

• Location fetching issues: Ensure location services are enabled on your device and you have granted the necessary permissions.

Contact Support

---

For further assistance, please contact our support team at aditya_dutt@srmap.edu.in or sanatshantanu_kulkarni@srmap.edu.in.