VISVESVARAYA TECHNOLOGICAL UNIVERSITY

BELGAUM-590014, Karnataka

A PROJECT REPORT ON

“TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION”

A dissertation work submitted in partial fulfilment of the requirement for the award of the degree
of

BACHELOR OF ENGINEERING IN
COMPUTER SCIENCE & ENGINEERING
(IoT & Cyber Security including Blockchain Technology)

Submitted By

HANAMANTH 1EW22IC017
SIDDHIVINAYAK 1EW22IC050
SOURABH 1EW22IC053
SUMIT 1EW22IC054

Under the guidance of

Dr. VENKATESHA G
Professor & Head of Department CSE (IoT & CyS including BCT EWIT)

EAST WEST INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
(IoT & Cyber Security including Blockchain Technology)
No. 63, Off Magadi Road, Vishwaneedam Post Bangalore–560091
2025-2026

1
 East West Institute of Technology
(Affiliated to Visvesvaraya Technological University, Belagavi)
Bengaluru-91

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

(IoT & Cyber Security including Blockchain Technology)

VISION of the Institute

To be an Institute of Academic Excellence in Technical and Management Education on par with global
standards to meet changing needs of the Society.

MISSION of the Institute

M1: To impart quality technical education that nurtures the young minds by providing the best of
teaching learning process and state of the art infrastructure.
M2: To foster technological advancement through research.
M3: To inculcate holistic personality development through best practices.
M4: To implant ethical and social commitment that grooms the students to become responsible
citizens.

VISION of the Department

To be a Department of Excellence in Technical Education through Innovative Learning Approach with
Social Commitment in the field of Computer Science & Engineering and IoT.

MISSION of the Department

M1: To provide a conducive learning ambience to enhance problem solving skills, leadership
qualities and team spirit.
M2: To impart advanced technical knowledge through training programs for the holistic
development of students.
M3: To promote research, innovation and entrepreneur skills in the field of Computer Science and
Engineering.
M4: To inspire the students to become socially responsible technocrats.

Program Educational Objectives (PEOs)

After 3 or 4 years of the graduation the CSE (IoT & Cys including BCT) graduates shall be able,
PEO1: To achieve sustainable growth as Computer Science Engineers in reputed organizations.
PEO2: To accomplish higher education and research with highest degree of professionalism and
integrity.
PEO3: To extend the services to mankind by exhibiting leadership qualities and ethical values.

2
 EAST WEST INSTITUTE OF TECHNOLOGY
No.63, Off Magadi Road, Vishwaneedam Post Bangalore-560 091
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
(IoT & Cyber Security including Blockchain Technology)

CERTIFICATE

This is to certify that the Project work entitled “TRAVEL ITINERARY PLANNER WITH
WEATHER INTEGRATION” is a Bonafide work carried out by HANAMANTH (1EW22IC017),
SIDDHIVINAYAK (1EW22IC050), SOURABH (1EW22IC053), SUMIT (1EW22IC054) in
partial fulfilment for the award of Bachelor of Engineering in Computer Science and Engineering (IoT &
Cyber Security including Blockchain Technology) of the Visvesvaraya Technological University, Belgaum
during the academic year 2025-2026. It is certified that all the suggestions/corrections indicated for Internal
Assessment have been incorporated in the report deposited in the department library. The project report has
been approved as it satisfies the academic requirements in respect to project work prescribed for the said
degree.

Signature of Internal Guide Signature of Head of Department Signature of Principal

Dr. Venkatesha G Dr. Venkatesha G Dr. K Channakeshavalu

Professor & HOD, Professor & HOD, Principal,
CSE (IoT & CyS including BCT) CSE (IoT & CyS including BCT) EWIT

External Viva
Name of the Examiner Signature with Date

1. ………………………………………. ……………………………………….

2. ………………………………………. ……………………………………….

3
ACKNOWLEDGEMENT

The satisfaction and euphoria that accompany the successful completion of any task would be
incomplete without the mention of the people who made it possible, whose constant guidance and
encouragement crowned our effort with success.

We express our sincere gratitude to our principal Dr. K Channakeshavulu, Principal, East West
Institute of Technology, Bangalore for his inspiration.

We wish to place our grateful thanks to Dr. Venkatesha G, Professor and Head Department of
Computer Science and Engineering (IoT & Cyber Security including Blockchain Technology)
East West Institute of Technology, Bangalore for providing encouragement and guidance.

We would also like to thank our guide Dr. Venkatesha G, Professor and Head Department of
Computer Science and Engineering (IoT & Cyber Security including Blockchain Technology) for
the timely inspection and guiding us throughout the process.

Also, we thank the members of the faculty of Department Computer Science and Engineering (IoT &
Cyber Security including Blockchain Technology) whose suggestions enabled us to surpass many of the
seemingly impossible hurdles.

Also, we thank our Parents whose suggestions and support enabled us to surpass many of the seemingly
impossible hurdles.

4
DECLARATION

HANAMANTH (1EW22IC017), SIDDHIVINAYAK (1EW22IC050), SOURABH (1EW22IC053),

SUMIT (1EW22IC054)) students of seventh semester, Bachelor of Engineering, Bangalore – 560091,
hereby declare that the project entitled “TRAVEL ITINERARY PLANNER WITH WEATHER
INTEGRATION” has been carried out by us under the supervision of Internal Guide [Link] G,
Professor and Head Department of Computer Science and Engineering(IoT & CyS including BCT), EWIT,
Bangalore submitted in the fulfilment of the course requirements for the award of the degree of Bachelor of
Engineering in Computer Science and Engineering (IoT & Cyber Security including Blockchain
Technology) of Visvesvaraya Technological University during the academic year 2025-2026.

Date:

Place: Bengaluru- 560091

HANAMANTH SIDDHIVINAYAK
(1EW22IC007) (1EW22IC011)

SOURABH SUMIT
(1EW22IC025) (1EW22IC061)

5
ABSTRACT

The rapid growth of tourism and the availability of online travel services have increased the need for
intelligent and personalized travel planning solutions. This project, Travel Itinerary Planner with Weather
Integration, aims to simplify trip planning by providing users with a smart platform that generates
customized travel itineraries based on user preferences, travel duration, budget, and real-time weather
conditions.

The system allows users to select destinations and receive day-wise travel plans including places to visit,
recommended activities, and suitable time slots. By integrating live weather data through external APIs, the
application ensures that suggested activities align with current and forecasted weather conditions, thereby
improving travel safety and experience. The platform dynamically adjusts itineraries in case of unfavorable
weather, offering alternative indoor activities or rescheduling suggestions.

The application is developed using a web-based architecture with a user-friendly interface, enabling easy
interaction and accessibility across devices. This solution helps travelers save time, reduce planning
complexity, and make informed decisions. The project demonstrates the effective use of APIs, database
management, and modern web technologies to deliver a practical and reliable travel planning syste.

6
 TABLE OF CONTENTS

CHAPTER DESCRIPTION PAGE NO.

Certificate i
Acknowledgement ii

Abstract iii
Table of Contents iv

List of Figures v
List of Tables vi
Chapter 1 Introduction 10
1.1 Background and Context 11
1.2 Limitations of Traditional Travel Planning 12
1.3 Role of Technology in Modern Tourism 13
1.4 Importance of Weather-Aware Itinerary Planning 14
1.5 Problem Statement 14
1.6 Proposed Solution 15
1.7 Objectives of the Study 15
1.8 Scope of the Project 15

Chapter 2 Literature Survey 16

Chapter 3 Problem Statement & Requirement 22

3.1 Problem Definition 23
3.2 Challenges in Dynamic Itinerary Planning 24
3.3 Functional Requirements 26
3.4 Non-Functional Requirements 27
3.5 System Constraints 27
3.6 Use Case Scenarios 27

Chapter 4 System design & Architecture 28

4.1 Overview of System Architecture 29
4.2 High-Level Architecture Diagram 30
4.3 Detailed Component Description 30
4.4 Workflow Diagram 32

7
 4.5 API Interaction Architecture 32

4.6 Database Design 33

4.7 Sequence Diagram 34
4.8 UI/UX Design Philosophy 34

Chapter 5 Methodology 35
5.1 Data Flow 36
5.2 Weather Suitability Scoring 37
5.3 POI Filtering and Prioritisation 38
5.4 TTDP-Based Scheduling 39

5.5 Routing Optimisation (2-opt, heuristics) 40

5.6 Budget Estimation Module 40
5.7 Notification & Ticket Generation Logic 41

Chapter 6 Implementation 42
6.1 Technology Stack 43
6.2 Django Backend Modules 44
6.3 Frontend Implementation 52
6.4 Google Maps API Integration 53
6.5 OpenWeatherMap Integration 55
6.6 OTP Authentication System 56
6.7 Database Schema 57
6.8 Testing Approach 59

Chapter 7 Results & discussion 64

7.1 System Screenshots 64
7.2 Case Study: Mumbai Trip 65
7.3 Weather-Aware Adjustments 65
7.4 Cost Estimation Output 66
7.5 Performance Evaluation 66

Chapter 8 Conclusion & Future work 69

8.1 Summary 69
8.2 Conclusion 69
8.3 Limitations 70
8.4 Future Enhancements 71
Conclusion 73

References 74

8
LIST OF FIGURE

FIGURE NO. DESCRIPTION PAGE

NO.
7.1 Homepage – Plan Your Perfect Trip 59
7.2 Features Overview – Why Choose Travel Planner 60
7.3 Login & Trip Creation Interface 61
7.4 Daily Itinerary UI 61
7.5 Trip Summary Page 62
7.6 Confirm Booking Window 62
7.7 System Sequence Diagram 63
7.8 System Architecture Diagram 63

9
 INTRODUCTION

Dept. of CSE (IoT & CyS including BCT) 2025-26 10

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 1
INTRODUCTION

1.1 Background and Context

Tourism remains one of the fastest-growing global industries, contributing significantly to national
economies, cultural exchange, and regional development. As travel becomes more accessible
through affordable transport and widespread internet connectivity, the expectations of modern
travellers have evolved considerably. Today’s travellers seek personalised experiences, efficient
planning, and dynamic recommendations that adapt to real-time conditions.

Traditional travel planning approaches, however, often rely on fragmented information gathered
from travel blogs, videos, guidebooks, and social media. Although these sources offer insights,
combining them into a coherent day-wise itinerary requires considerable time, effort, and manual
interpretation. Furthermore, most people lack a structured method for assessing feasibility factors
such as travel duration, distances between attractions, weather conditions, or budget compatibility.
This leads to incomplete or impractical itineraries that fail to maximise the traveller’s limited time at
a destination.

The emergence of intelligent travel management systems provides an opportunity to automate and
optimise this process. With the availability of geospatial data, powerful route-finding algorithms,
and accurate weather forecasting models, computer-based planning tools can produce personalised
itineraries tailored to user preferences and real-world constraints. This project builds upon such
capabilities by integrating weather forecasting into itinerary generation, thereby producing
schedules that are not only optimised for travel efficiency but also resilient to environmental
variation.

The integration of weather plays a crucial role in enhancing travel satisfaction, as numerous
activities depend heavily on favourable climatic conditions. Beach visits, sightseeing, outdoor
monuments, and local markets, for example, may become unsuitable or inconvenient during
rainfall, extreme heat, or poor visibility. By incorporating weather intelligence, the system ensures
that itineraries remain practical and context-aware, reducing disruptions and improving the overall
travel experience.

Dept. of CSE (IoT & CyS including BCT) 2025-26 11

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

1.2 Limitations of Traditional Travel Planning

Despite the abundance of travel-related information available online, most existing tools still operate
at a superficial level. Conventional planning approaches typically involve:

 Checking tourist websites for attraction lists

 Reading articles or watching videos for recommendations

 Estimating distances manually using maps

 Reviewing weather forecasts separately

 Preparing a timetable using a spreadsheet or notes

This fragmented process introduces several limitations:

1. Time-Consuming Research
Travellers spend hours comparing sources, filtering irrelevant information, and manually plotting
the order of visits. This is particularly problematic for multi-day trips where constraints are
interdependent.

2. Lack of Real-Time Adaptability

Traditional planning assumes static conditions, ignoring sudden weather changes that can render
outdoor activities impractical. Most itineraries fail when unexpected rainfall or heat disrupts the
intended schedule.

3. Poor Route Optimisation

When travellers manually decide the sequence of locations, they often overlook road networks,
traffic estimates, or travel distances. As a result, time is lost commuting inefficiently between
scattered attractions.

4. Absence of Personalisation
Traveller interests vary widely — some prefer heritage sites, while others focus on beaches,
nightlife, food exploration, or nature. Traditional planning rarely accommodates such personalised
categories with structured optimisation.

Dept. of CSE (IoT & CyS including BCT) 2025-26 12

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

1.3 Role of Technology in Modern Tourism

Digital transformation has significantly reshaped tourism. With the growing adoption of
smartphones, cloud services, and AI-driven platforms, travellers increasingly rely on technology for
trip planning, navigation, and decision-making. The availability of high-quality APIs, such as
Google Maps and OpenWeatherMap, provides access to rich datasets that can be used to construct
intelligent travel recommendations.

Key technological developments enabling modern tourism include:

1. Geospatial Services and Mapping APIs

These allow retrieval of Points of Interest (POIs), real-time travel durations, optimal routing, and
location-aware services.

2. Weather Forecasting Models

Accurate forecasts and hourly predictions enable systems to advise whether an activity is suitable
at a given time of day.

3. Machine Learning and Optimisation Algorithms

AI techniques can analyse user preferences, classify POIs, and generate optimal sequences that
minimise travel time while respecting constraints.

4. Web Frameworks and Cloud Platforms

Frameworks like Django facilitate modular development, authentication, database interaction, and
seamless integration with third-party APIs.

5. Cross-Platform Accessibility
Users expect seamless access to travel plans across mobile and desktop devices, which modern web
technologies readily support.

The convergence of these technologies makes it feasible to design an automated system capable of
delivering highly accurate, flexible, and engaging travel itinerari

Dept. of CSE (IoT & CyS including BCT) 2025-26 13

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

1.4 Importance of Weather-Aware Itinerary Planning

Weather influences nearly every aspect of travel — from mobility to safety and comfort. Outdoor
activities such as beach visits, nature walks, open-air monuments, and photography-based
experiences are highly sensitive to climatic conditions. Even slight variations in weather can affect
the feasibility or enjoyment of planned activities. A weather-aware itinerary can:

1. Prioritise the Best Time Slots for Outdoor Activities

Clear weather periods are assigned to beaches, viewpoints, and monuments.
2. Shift Activities Dynamically
If rain is forecast in the morning, indoor activities such as museums or cafés can be placed earlier.
3. Improve Safety
Adverse weather conditions may increase risks in areas such as coastal regions or elevated
terrains.
4. Enhance Traveller Satisfaction
Well-timed activities contribute to a smoother, more enjoyable trip.
5. Reduce Last-Minute Changes
Travellers often feel stressed when their itinerary collapses due to unforeseen conditions. An
intelligent system can mitigate these uncertainties.

In essence, integrating weather forecasting makes the system more adaptive and resilient than
standard itinerary planners.

1.5 Problem Statement

Most existing itinerary planning tools do not incorporate real-time or forecast weather data into
activity scheduling. They fail to adjust the day-wise plan when unexpected conditions arise, leading
to suboptimal experiences, wasted time, and inconvenience for the traveller. There is therefore a
clear requirement for an automated system that combines weather insights, travel time optimisation,
and personalised preferences to produce dynamic, reliable, and practical itineraries

Dept. of CSE (IoT & CyS including BCT) 2025-26 14

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

1.6 Proposed Solution

The proposed system is a web-based travel itinerary planner that integrates:
 Google Maps Places API for POI discovery
 Google Directions API for route optimisation
 OpenWeatherMap API for real-time and forecast weather
 Django framework for backend logic
 Automated itinerary generation using TTDP principles
 A clean and responsive user interface

It computes the optimal activity sequence, estimates costs, generates summaries, and provides
shareable digital tickets. Weather suitability scores ensure that outdoor activities are placed in
favourable time slots, providing a realistic and context-aware itinerary.

1.7 Objectives of the Study

The study aims to:
 Develop an automated itinerary generation engine.
 Integrate weather forecasts to create adaptable schedules.
 Implement routing algorithms to minimise travel distances.
 Provide personalised recommendations based on user preferences.
 Generate professional travel summaries and digital tickets.
 Ensure a seamless user experience through intuitive interfaces.
1.8 Scope of the Project
The system focuses on:
 Short- to medium-duration urban trips
 Personalised and weather-aware itinerary generation
 Cost estimation and basic budget planning
 Real-time notifications via email and WhatsApp
 Practical routing and POI selection It
does not currently include:
 Hotel booking systems
 Flight scheduling
 Group synchronisation logic
 Offline mode
These may be added in future versions.

Dept. of CSE (IoT & CyS including BCT) 2025-26 15

 LITERATURE
SURVEY

Dept. of CSE (IoT & CyS including BCT) 2025-26 16

 CHAPTER 2
LITERATURE SURVEY
The purpose of this chapter is to examine existing research, systems, and methodologies related to
automated travel planning, route optimisation, weather integration, and personalised recommendation
frameworks. The review identifies the strengths and limitations of prior work, highlights key
computational models such as the Tourist Trip Design Problem (TTDP), and establishes the research
gaps addressed by the proposed system. This chapter is divided into thematic sections covering
intelligent itinerary generation, weather-aware systems, optimisation algorithms, geospatial
technologies, and modern web-based travel platforms.

Author’s Year Title Methodology Pros / Cons

Analyses the Tourist

Trip Design Problem
Pros: Establishes TTDP as the
Tourist Trip (TTDP) and reviews
computational foundation for
A. Vansteenwegen, Design optimisation methods
itinerary generation. Cons:
W. Souffriau, G. 2011 Problem: A including greedy
Models assume static
Vanden Berghe[1] Comprehensive heuristics, meta-
conditions; no weather or
Review heuristics, and
dynamic adaptation.
constraint-based
modelling.

Combines preference
Personalised Pros: Handles diverse
weighting and POI
Itinerary interests with customised POI
R. Kurata, Y. ranking to generate
2015 Generation filtering. Cons: Does not
Taniguchi[2] personalised activity
Based on User optimise routes or sequence
lists using multi-criteria
Preferences POIs efficiently.
scoring.

Introduces context- Pros: Good use of context

aware tourism factors for personalised POI
Mobile Tourism
recommender models selection. Cons: No
Kenteris et al.[3] 2011 Recommender
combining mobility integration of weather or real-
Systems
patterns and user time environmental
profiling. conditions.

Reviews mobile Pros: Identifies user

A Survey on recommendation behaviour as central to
D. Gavalas, M. Mobile Tourism frameworks and itinerary personalisation.
2014
Kenteris[4] Recommender evaluates integration of Cons: Scheduling, routing,
Systems mapping, POIs, and and dynamic updates are
user modelling. absent.

Dept. of CSE (IoT & CyS including BCT) 2025-26 17

 OpenWeatherMap Weather-Aware Provides meteorological Pros: Reliable API for
2016
Research Team[5] Travel Planning data aggregation and temperature, humidity,

APIs forecasting APIs precipitation forecasting.

enabling environmental Cons: Standard forecasts need
context in planning additional modelling for
systems. activity suitability.
Describes routing
Directions and Pros: Accurate travel times
algorithms and real-time
Google Maps Distance Matrix improve itinerary feasibility.
2020 travel estimation using
Platform[6] API Cons: Does not automatically
global geospatial
Documentation optimise multi-POI sequences.
networks.
Introduces 2-Opt and 3- Pros: Reduces travel distance
Local Search Opt heuristics to reduce and improves route structure.
P. Vansteenwegen
2015 Techniques for route inefficiencies in Cons: Still deterministic; no
& Co.[7]
Tour Planning multi-POI travel adaptation for weather
itineraries. changes.
Combines weather
Pros: First major attempt at
forecasts with POI
Weather-Aware weather-based scoring. Cons:
A. Çetinkaya & H. category suitability
2019 City Tour Limited to hourly adaptation;
Erdem[8] (indoor/outdoor) for
Planning lacks multi-day itinerary
generating adaptive
structure.
travel plans.
Pros: Demonstrates benefits
Incorporates real-time
Adaptive Travel of dynamic scheduling. Cons:
events and contextual
Lee & Tseng[9]] 2016 Planning using Computationally expensive;
triggers to adjust
Contextual Data not designed for large itinerary
itineraries.
sets.
Pros: Dynamic weather-aware
Uses Google Maps API scheduling, efficient route
Research from AI-Driven for routing, optimisation, personalisation
Your Conference Travel Itinerary OpenWeatherMap for based on user preferences,
Paper (Travel 2025 Planner with forecast suitability multi-day sequencing. Cons:
Planner Weather scoring, and a hybrid Dependent on third-party API
System)[10] Integration TTDP–heuristic model availability; sudden extreme
for itinerary generation. weather may require manual
override.

Dept. of CSE (IoT & CyS including BCT) 2025-26 18

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

1. A. Vansteenwegen, W. Souffriau and G. Vanden Berghe, in their well-known review on the

Tourist Trip Design Problem (TTDP), provide a foundational analysis of how attraction selection and
sequencing can be formulated as a combinatorial optimisation task. Their work highlights that TTDP
extends classical routing problems by integrating constraints such as visiting time, user preferences, and
time windows. This study establishes that TTDP is computationally complex (NP- hard), requiring
heuristic or meta-heuristic approaches for practical use. It also emphasises that traditional TTDP models
operate under static environmental assumptions, making them insufficient for real-world travel where
conditions such as weather fluctuate. This gap directly motivates the need for systems that incorporate
dynamic external data such as forecasts, which your project addresses effectively. [1]

2. R. Kurata & Y. Taniguchi – “Personalised Itinerary Generation Based on User Preferences”

R. Kurata and Y. Taniguchi investigate the role of user preference profiling in generating more
relevant travel recommendations. Their work focuses on scoring mechanisms that classify POIs into
categories (such as cultural, natural, food, and entertainment) and match them with user interests. While
their method improves personalisation, it does not sequence the POIs into a day-wise itinerary nor
consider logistical factors like distance or opening hours. Furthermore, external conditions such as
climate or weather uncertainty are not used to adjust the recommendations. Their contribution is
important because it demonstrates how preference-based filtering improves satisfaction, but its
limitations highlight why a more holistic system—such as your weather-aware TTDP model—is
necessary. [2]

3. Kenteris et al. – “Mobile Tourism Recommender Systems”

Kenteris et al. explore mobile tourism systems capable of delivering context-aware recommendations to
travellers. The work reviews how mobile technologies such as GPS, network connectivity, and portable
devices can be used to personalise recommendations based on a traveller’s immediate context, including
location and basic preferences. While this represents a significant step towards intelligent travel
planning, their approach stops short of generating a complete trip itinerary. Their system lacks complex
optimisation logic, routing considerations, or weather-driven scheduling. Nevertheless, their research
underscores the growing relevance of mobile-first travel platforms, which supports the architectural
direction taken in your Django-based system. (3)

Dept. of CSE (IoT & CyS including BCT) 2025-26 19

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

4. D. Gavalas & M. Kenteris – “A Survey on Mobile Tourism Recommender Systems”

D. Gavalas and M. Kenteris provide a comprehensive survey of mobile tourism recommender
systems, outlining how user modelling, POI databases, and geospatial technologies have shaped modern
tourism applications. Their analysis identifies personalisation and mobility as central requirements for
intelligent travel systems. However, they note limitations in existing methods, such as fragmented data
sources and systems that cannot adapt itineraries automatically. Weather integration and real-time
itinerary adjustments are especially absent from most reviewed solutions. Their survey reinforces the
need for a unified, context-aware itinerary planning method—precisely the gap your project fills by
combining routing, preference modelling, and weather forecasting. [4]

5. OpenWeatherMap Research Team – “Weather-Aware Travel Planning APIs”

The OpenWeatherMap Research Team discuss the role of meteorological data services in supporting
weather-sensitive applications. Their documentation and research highlight how APIs can deliver
hourly, daily, and long-range forecasts that help applications include environmental awareness in their
decision-making. While these APIs provide accurate and diverse weather variables such as temperature,
humidity, cloud cover, and precipitation likelihood, they do not inherently interpret this data for activity
suitability. It is up to the application developer to translate raw weather metrics into meaningful
recommendations. Your project builds on this by introducing a weather suitability scoring model,
which uses API outputs to influence the placement of outdoor and indoor activities. [5]

6. Google Maps Platform – “Directions and Distance Matrix API”

The Google Maps Platform team, through their technical documentation, outline how route planning,
travel time estimation, and POI discovery integrate into intelligent navigation systems. Their APIs
provide accurate real-time distance calculations and multi-modal travel estimates, which are essential
components of itinerary optimisation. However, the documentation emphasises that the APIs do not
automatically perform multi-POI sequence optimisation; they only compute pairwise distances or
routes. This limitation directly aligns with the need for custom optimisation methods such as the hybrid
TTDP-based solver used in your project. The integration of Google Maps APIs into your planning
engine therefore forms a key technological bridge between theoretical optimisation and practical
itinerary output. [6]

Dept. of CSE (IoT & CyS including BCT) 2025-26 20

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

7. P. Vansteenwegen & Colleagues – “Local Search Techniques for Tour Planning”

P. Vansteenwegen and colleagues focus on improving route efficiency using local search methods
such as 2-opt and 3-opt heuristics. These optimisation techniques refine an initial route by
systematically reducing unnecessary detours and improving traversal efficiency. Their research
demonstrates that local search significantly reduces total travel time in tour-planning tasks, making
itineraries more realistic for users. However, while their work enhances route feasibility, it does not
address factors beyond routing—such as weather changes or activity suitability. Your system leverages
this research by incorporating a 2-opt refinement stage after initial POI selection, ensuring that route
structure is both efficient and adaptive. [7]

8. A. Çetinkaya & H. Erdem – “Weather-Aware City Tour Planning”

A. Çetinkaya and H. Erdem introduce one of the few itinerary-related studies that consider weather
conditions explicitly. Their method categorises activities as indoor or outdoor and aligns them with
forecasted weather windows. While innovative, their system primarily focuses on short-term
adjustments within a single day and does not provide a fully optimised multi-day itinerary. Their
modelling also lacks route optimisation logic and offers a limited approach to user preference handling.
Nonetheless,their research establishes an important precedent for weather-aware travel planning, which
your project significantly expands through multi-day scheduling, routing, and personalisation. [8]

9. Lee & Tseng – “Adaptive Travel Planning Using Contextual Data”

Lee and Tseng examine the value of real-time contextual triggers such as events, crowds, and local
disruptions in shaping adaptive travel itineraries. Their work demonstrates how itineraries can shift
dynamically when conditions change unexpectedly. While their approach highlights the benefits of
adaptability, it is computationally complex and not optimised for tourist-centred multi-day planning. It
also does not integrate weather suitability or mapping data to adjust routes efficiently. Your system
incorporates the underlying philosophy of adaptability but applies it more practically through weather-
based dynamic reordering and efficient POI selection. [9]
10. Conference Paper – “AI-Driven Travel Itinerary Planner with Weather Integration”
It present a travel itinerary planner that uniquely integrates weather forecasting with route optimisation
and personalised POI selection. The scheduling engine uses a TTDP-inspired heuristic combined with 2-
opt refinement to produce realistic multi-day itineraries. This contribution is significant because it
addresses the shortcomings of earlier systems by combining real-time weather adaptation, dynamic POI
ordering, budget estimation, and a complete user interface. [10]

Dept. of CSE (IoT & CyS including BCT) 2025-26 21

 PROBLEM
STATEMENT
AND
REQUIREMENT

Dept. of CSE (IoT & CyS including BCT) 2025-26 22

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 3
PROBLEM STATEMENT
3.1 Key Challenges in Modern Travel Planning
Planning a multi-day trip appears simple on the surface, yet it remains a highly complex real-world
optimisation problem influenced by multiple dynamic factors. Travellers often rely on fragmented
tools—such as blogs, mapping apps, and weather forecasts—which they must manually synthesise into a
coherent plan. This fragmented approach gives rise to several notable challenges.

1. Fragmentation of Information Sources

Unlike integrated systems, travellers must consult different platforms for POI discovery, routing,
weather, budget estimations, and reviews. Without a unifying interface, users are forced to manually
compare and combine this information, leading to errors and inefficiencies. The absence of a
consolidated planning framework results in incomplete or unrealistic itineraries.

2. Static and Non-adaptive Itinerary Tools

Most travel planners available today offer static recommendations. Even if they list attractions or
generate a sequence, they do not adapt when weather conditions shift. For outdoor-dependent activities
such as beach visits or sightseeing, a static itinerary is fragile and prone to disruption.

3. Insufficient Consideration of Weather Constraints

Weather significantly affects activity suitability, yet existing itinerary planners rarely integrate real- time
or forecasted weather into scheduling algorithms. Rainfall, extreme heat, or low visibility can render
certain POIs unsuitable, but traditional planning provides no mechanism to adjust the itinerary
accordingly.

4. Inefficient Route Ordering

The Tourist Trip Design Problem (TTDP) highlights the difficulty of selecting and sequencing POIs to
minimise travel duration. Most travellers lack tools capable of optimising multi-POI routes. As a result,
they often travel inefficiently, wasting valuable time in transit.

5. Lack of Personalisation and User Preference Alignment

Generic travel platforms typically provide the same list of attractions to all users. They do not account
for diverse travel styles such as cultural, adventure, culinary, shopping-focused, or nature-oriented
experiences. Without functional personalisation, recommendations are often irrelevant or unsatisfying.

Dept. of CSE (IoT & CyS including BCT) 2025-26 23

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

6. Absence of Multi-day Scheduling Logic

Many existing systems focus on single-day suggestions. Multi-day itinerary structuring, time-window
constraints, estimated durations, and inter-day balancing of indoor/outdoor activities are largely
unsupported. This limitation makes current tools insufficient for genuine trip planning.

7. No Integrated Budget or Cost Forecasting

Travellers are often concerned with estimating total trip expenses. However, current itinerary platforms
rarely provide approximate cost analysis. This forces users to calculate expenses independently,
increasing cognitive load and reducing [Link] challenges collectively illustrate the need for a
unified, intelligent, weather-aware itinerary planning system capable of generating practical, optimised,
and user-specific travel plans.

3.2 Objectives of the Research

In response to the challenges described above, this project seeks to develop a comprehensive travel
itinerary planner that integrates weather forecasting, route optimisation, and personalised
recommendation strategies. The primary objectives include:
1. Develop an AI-assisted Itinerary Generation Engine
Create a scheduling mechanism that selects and sequences POIs using TTDP-based principles. The
engine should be capable of generating multi-day itineraries tailored to individual preferences and
available travel time.
2. Integrate Weather Forecasting for Activity Suitability
Leverage OpenWeatherMap forecasts to determine whether an activity is suitable at a given time.
Outdoor POIs must be scheduled during favourable weather, while indoor POIs should fill unfavourable
weather periods.
3. Provide Personalised POI Recommendations
Implement preference-based filtering that matches POIs to user interests such as monuments, beaches,
restaurants, shopping, or adventure. The system should dynamically eliminate attractions irrelevant to
the user.
4. Optimise Routes Using Mapping APIs
Incorporate Google Maps Directions API to compute realistic travel durations. Apply heuristic
optimisation techniques such as greedy filtering and 2-opt refinement to minimise unnecessary travel
time. III

Dept. of CSE (IoT & CyS including BCT) 2025-26 24

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

5. Enable Real-Time Adaptation and Dynamic Reordering

Design the system to automatically update itineraries in response to fluctuations in weather or other
conditions. The engine should be capable of reshuffling activities while preserving logical flow.
6. Implement a Unified Web Platform
Develop a complete Django-based web application with modules for user login, trip creation, itinerary
visualisation, ticket generation, and digital sharing.
3.3 Problem Scope
The scope of this project defines the boundaries within which the system operates. A clear scope
ensures relevance and feasibility.
1. Focus on Short- to Medium-Length Urban Trips
The system is designed for city-based tourism where multiple POIs can be visited within a few days. It
is not currently optimised for inter-city or long-distance travel involving multiple transport modes.
2. Integration of Real-Time Weather Forecasting
Weather data is used exclusively to adjust POI suitability and activity sequence. The system does not
currently manage extreme weather alerts or emergency reactivity.
3. Use of Heuristic Optimisation for TTDP
Given the computational complexity of TTDP, the system employs heuristic methods rather than exact
optimisation. This ensures practical performance and near-optimal outputs suitable for real users.
4. Personalisation Through Preference Filtering
User preferences influence POI selection categories. However, advanced personalisation (e.g.,
behavioural learning, recommendation history) is outside the current scope.
5. Web-based Implementation Using Django
The project focuses on a web platform accessible on smartphones and desktop browsers. Native mobile app
development is not included.
6. Basic Budget Estimation
The cost estimation module provides approximate values based on POIs and typical entry fees. It does
not currently integrate live ticketing APIs.
7. Limited Dependency on External Booking Systems
Hotel booking, restaurant reservations, and transport ticketing are not included in the present scope.
This defined scope ensures targeted, efficient development while laying the foundation for future
enhancements.

Dept. of CSE (IoT & CyS including BCT) 2025-26 25

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

3.4 Functional Requirements

Functional requirements describe what the system must be capable of doing.
1. User Registration and Authentication
 Allow users to create accounts and sign in securely.
 Enable OTP-based verification for enhanced security.
2. Trip Creation and Preferences Collection
 Collect travel dates, preferences, and trip duration.
 Capture user interests (e.g., culture, food, nature).
3. POI Retrieval and Filtering
 Fetch POIs from the Google Maps Places API.
 Filter based on user preferences and categories.
4. Itinerary Generation
 Automatically generate multi-day itineraries.
 Assign activities to time slots based on durations.
5. Route Optimisation
 Compute travel durations using Google Directions API.
 Apply local optimisation (2-opt) to improve route structure.
6. Weather-Aware Scheduling
 Fetch weather forecasts and assign suitability scores.
 Adjust indoor and outdoor activities accordingly.
7. Trip Summary and Ticket Generation
 Produce a downloadable itinerary summary.
 Send digital tickets or summary via email/WhatsApp.
8. User Interface Functionality
 Display itineraries clearly with time slots and icons.
 Provide editing options for users.

Dept. of CSE (IoT & CyS including BCT) 2025-26 26

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

3.5 Non-Functional Requirements

These define the system’s quality attributes.
1. Usability
The interface should be intuitive, requiring minimal technical experience.
2. Reliability
The application should consistently produce stable, accurate itineraries.
3. Performance
Itinerary generation should complete within a few seconds, even for multi-day trips.
4. Scalability
Design must support increasing users and expanded POI databases.
5. Maintainability
The codebase must follow structured design patterns to allow future updates.
6. Data Security
Sensitive user information must be protected using secure authentication measures.
7. Availability
The system must work across devices and browsers.

3.6 Use Case Scenarios

Use Case 1: New User Creating an Itinerary
A user logs in, enters destination details, selects preferences, and receives a complete itinerary with
weather-aware placements and estimated costs.
Use Case 2: Bad Weather Forecast for a Planned Outdoor Visit
If rainfall is detected, the system automatically reassigns outdoor activities to a later time and shifts indoor
activities earlier.
Use Case 3: Travelling with Interest-Based Customisation
A user interested only in food and cultural sites receives an itinerary containing restaurants, cafés, and
museums, leaving out irrelevant attractions.
Use Case 4: Time-Constrained Traveller
A user planning a half-day trip receives an itinerary containing the nearest, high-priority attractions that
fit within the limited timeframe.
Use Case 5: Sharing Itinerary
After finalising the itinerary, the system generates a summary file that the user shares via email or
WhatsApp

Dept. of CSE (IoT & CyS including BCT) 2025-26 27

SYSTEM DESIGN
AND
ARCHITECTURE
TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 4

SYSTEM DESIGN AND ARCHITECTURE

System design plays a central role in translating conceptual requirements into a structured set of
components, interactions, and workflows. For the travel itinerary planner, the architecture must support
dynamic itinerary generation, weather-aware decision-making, real-time API communication, and
intuitive user experience. This chapter outlines the high-level architecture, detailed module descriptions,
workflow diagrams, database models, and system interactions that form the foundation of the proposed
application.

4.1 Overview of System Architecture

The Travel Itinerary Planner with Weather Integration is designed as a modular, scalable, and API-
driven web application implemented using the Django framework. The system integrates three major
components:
1. User Interaction Layer (Frontend)
o Handles UI rendering, form submissions, itinerary display, and user navigation.
o Accessible through web browsers on both mobile and desktop.
o Corresponds to screens such as the Homepage, Login Interface, Trip Overview, and
Summary Page (your provided images).
2. Application Logic Layer (Backend)
o Implements itinerary generation, weather-based suitability scoring, routing optimisation, user
authentication, and trip summarisation.
o Integrates with external APIs: Google Maps and OpenWeatherMap.
3. Data and External Service Layer
o Comprises Google Maps Places API, Directions API, and Distance Matrix API.
o Includes OpenWeatherMap for current and forecast weather.
o Uses a Django ORM-based database for user accounts, trip records, POI entries, and cached
API responses.
Together, these layers form a cohesive architecture that supports dynamic, intelligent itinerary planning.
The system follows a loosely coupled structure, enabling easy updates to individual modules without
disrupting the entire workflow.

Dept. of CSE (IoT & CyS including BCT) 2025-26 29

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

4.2 High-Level Architecture Diagram (Described)

The architecture can be understood as a flow of interactions across components:
User → Frontend UI → Django Views → Itinerary Engine → APIs → Response → UI Display
The diagram (represented by your uploaded screenshots) includes:
 Homepage (Figure: Homepage UI): Entry point providing options to create a trip, explore
features, or log in.
 Features Screen (Figure: Features Overview): Outlines system functionalities such as weather
integration, budget estimation, and POI filtering.
 Login Interface (Figure: Login Page): Implements OTP verification and user account
validation.
 Trip Overview Screen (Figure: Trip Overview): Used to input dates, preferences, and trip
details.
 Itinerary Screen (Figure: Daily Itinerary View): Displays day-wise schedule, activity slots, and
weather icons.
 Summary Screen (Figure: Summary Page): Shows final itinerary, total estimated cost, and
ticket-generation options.
 Confirmation Window (Figure: Confirmation Popup): Appears before generating final
documents.
These interface elements interact with backend modules through HTTP POST/GET requests handled by
Django.

4.3 Detailed Component Description

The system architecture comprises several functional modules:
1. User Authentication Module
Handles login, OTP verification, session management, and security.
 Ensures only authenticated users can save and retrieve itineraries.
 Uses Django’s inbuilt authentication framework.
2. Trip Creation Module
Collects required planning inputs:
 Destination
 Trip dates
 Number of travellers
 User interests
 Budget preference (if enabled)

Dept. of CSE (IoT & CyS including BCT) 2025-26 30

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

3. POI Retrieval Module

Uses Google Maps Places API to fetch relevant attractions based on:
 Keywords
 Categories
 Ratings
 Distance constraints
The raw POI data is filtered and ranked using preference weights.
4. Routing and Travel Time Calculation Module
Powered by Google Directions API:
 Computes the shortest paths
 Estimates minute-by-minute travel times
 Supports walking, driving, or mixed modes
This ensures the itinerary respects realistic travel durations.
5. Weather Integration Module
Uses OpenWeatherMap API to retrieve forecast attributes:
 Temperature
 Cloud cover
 Rain probability
 Wind speed
 Humidity
The data is processed to compute weather suitability scores that influence activity ordering.
6. Itinerary Generation Engine (TTDP-Inspired)
Core decision-making module:
 Selects POIs based on time availability
 Applies weather-based scheduling
 Uses a greedy heuristic for initial slot filling
 Applies 2-opt refinement for route efficiency
This engine produces the final optimised schedule.
7. Summary and Ticket Module
Generates a downloadable summary file containing:
 Day-wise itinerary
 Weather forecasts for each activity
 Estimated travel cost

Dept. of CSE (IoT & CyS including BCT) 2025-26 31

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

4.4 Workflow Diagram Explanation

The workflow, as illustrated through your UI images, is summarised as follows:

1. User Login → via login interface (Figure: Login Interface).

2. Enter Trip Details → destination, dates, categories (Trip Overview Screen).

3. System Fetches POIs → via Google Places API.

4. Weather Data Retrieved → from OpenWeatherMap for each day.

5. Engine Generates Itinerary → combining TTDP logic + weather suitability.

6. User Reviews Itinerary → displayed in daily card layout (Itinerary Screen).

7. Final Summary Created → showing budget and travel flow (Summary Page).

8. Confirmation Step → via popup (Confirmation Window).

This structured flow ensures consistency and user control.

4.5 API Interaction Architecture

API integration is critical to the system’s functionality. The architecture separates API functions into
reusable service modules:
[Link] Places API Integration
 Fetches POIs using search queries
 Returns structured JSON objects
 Extracts attributes such as name, rating, type, coordinates
[Link] Directions API Integration
 Computes travel durations between POI pairs
 Returns traffic-adjusted estimates
 Provides route geometry for map rendering
[Link] API Integration
 Provides real-time and 7-day forecast data
 Weather conditions mapped to suitability scores
 Influences placement of indoor vs outdoor activities
Requests are cached locally to avoid repeated calls and improve performance.

Dept. of CSE (IoT & CyS including BCT) 2025-26 32

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

4.6 Database Design

The database follows Django’s ORM model and contains the following key tables:
1. User Table
 User ID
 Authentication fields
 OTP verification status
2. Trip Table
 Trip ID
 User ID
 Destination
 Start and end dates
 Number of days
3. POI Table
 POI ID
 Name
 Category
 Coordinates
 Rating
 API reference ID
4. Itinerary Table
 Day index
 Scheduled POIs
 Time slots
 Weather suitability levels
5. Cached Data Table
 Stores API responses for short-term reuse
This modular structure supports scalability and clear relational mapping

Dept. of CSE (IoT & CyS including BCT) 2025-26 33

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

4.7 Sequence Diagram Explanation

Your uploaded Sequence Diagram visually represents the request–response cycle between frontend,
backend, and external APIs. The sequence is:
1. User initiates trip creation
2. Frontend sends request → Django View
3. Backend requests POIs → Google Places API
4. Backend requests weather → OpenWeatherMap API
5. Backend computes itinerary → Itinerary Engine
6. Backend responds → Frontend UI displays results
This diagram highlights synchronous interactions and ensures clarity during development and
maintenance.

4.8 UI/UX Design Philosophy

Your interface screenshots show a clean, user-friendly design that follows these principles:
1. Simplicity and Clarity
 The Homepage uses minimal text and clear navigation buttons.
 The Features Page explains the system concisely through icons and short descriptions.
2. Guided Workflow
Users are guided through a linear journey: login → trip details → itinerary → summary.
3. Visual Breakdown of Day-wise Itinerary
 Activity cards are colour-coded.
 Weather icons appear next to time slots.
 POIs are grouped logically.
4. Notification-Oriented Design
The Confirmation Window ensures users do not accidentally generate or overwrite itineraries.
5. Mobile-Friendly Interfaces
Cards, buttons, and layouts follow responsive design principles to work across devices.

Dept. of CSE (IoT & CyS including BCT) 2025-26 34

 METHODOLOGY

Dept. of CSE (IoT & CyS including BCT) 2025-26 35

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 5
METHODOLOGY

The methodology describes the internal working logic of the Travel Itinerary Planner with Weather
Integration. It elaborates how user inputs, external APIs, heuristic optimisation strategies, weather
intelligence, and scheduling algorithms collectively generate a feasible and realistic multi-day travel
itinerary. The chapter unpacks the journey from raw data acquisition to final itinerary generation and
summary output.

5.1 Data Flow

The system follows a multi-stage data flow pipeline that connects user interactions with backend
decision-making and external data sources. The flow ensures that every itinerary is constructed based on
validated inputs, accurate routing information, and real-time weather forecasts. The data flow comprises
the following sequential stages:
1. User Input Acquisition
The system begins with user inputs such as destination, travel dates, number of days, number of
travellers, and personal interests. These inputs originate from the Trip Overview Interface and serve as
the foundation for filtering POIs and defining scheduling constraints.
2. POI Retrieval and Processing
Once inputs are received, the backend queries the Google Places API to fetch relevant Points of
Interest. The raw API response contains metadata such as POI names, categories, geographic
coordinates, average ratings, and popularity. This raw dataset is pre-processed to remove duplicates,
unrated locations, and irrelevant categories before proceeding to prioritisation.
3. Weather Data Acquisition
The system retrieves a seven-day weather forecast from OpenWeatherMap, mapped according to the
trip’s start and end dates. Forecast elements such as rainfall probability, cloud cover, humidity, and
temperature are stored temporarily to support weather suitability scoring.
4. Travel Duration Matrix Construction
The backend requests route durations from the Google Directions API, constructing a matrix that stores
travel time between each pair of selected POIs. This matrix is essential for TTDP-based scheduling and
route optimisation.
5. Scheduling & Optimisation
The processed POIs, weather scores, time windows, and travel durations are passed to the heuristic
itinerary engine. The engine selects POIs, assigns them to time slots, and constructs a feasible day-wise
schedule.

Dept. of CSE (IoT & CyS including BCT) 2025-26 36

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

6. Final Output & Visualisation

The generated itinerary is fed back to the frontend to be displayed in daily card format, accompanied by
weather icons and travel durations. A final summary document is also generated for user download. This
complete data flow ensures that itinerary generation is coherent, responsive, and fully aligned with real-
world conditions. The flow reflects the pipeline described in your conference paper.
.2 Weather Suitability Scoring
Weather is a critical determinant for the feasibility of travel activities. As highlighted in your conference
paper, activities such as beach visits, hill viewpoints, and heritage monuments depend heavily on
external conditions. To integrate weather intelligently into the itinerary, the system uses a Weather
Suitability Scoring Model (WSSM).
1. Extraction of Weather Parameters
From the OpenWeatherMap API, the following attributes are retrieved for each day:
 Temperature
 Humidity
 Cloud cover
 Probability of precipitation
 Wind speed
 General condition (clear, rain, thunderstorms, haze, etc.)
Each parameter contributes differently to the suitability of outdoor or indoor activities.
2. Indoor vs Outdoor Classification
POIs are classified into two broad groups:
 Outdoor: beaches, monuments, parks, viewpoints
 Indoor: museums, malls, aquariums, cafés, heritage interiors
3. Scoring Mechanism
A weighted scoring model assigns a score from 1 to 5 based on weather conditions:
Weather Condition Outdoor Score Indoor Score

Clear / Sunny 5 3

Partly Cloudy 4 4

Cloudy 3 4

Light Rain 2 5

Heavy Rain 1 5

Heatwave 2 4

Dept. of CSE (IoT & CyS including BCT) 2025-26 37

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

4. Influence on Scheduling
High outdoor scores push POIs earlier in the day, while low scores trigger replacement with indoor
alternatives. This ensures that the final itinerary remains feasible regardless of weather fluctuations.
By mapping weather forecasts to activity suitability, the system achieves dynamic adaptation—a key
innovation demonstrated in your conference publication.

5.3 POI Filtering and Prioritisation

Selecting the appropriate POIs for each trip is essential to producing meaningful itineraries. The system uses
a multi-layered filtering and ranking process.
1. API-Based POI Retrieval
Google Places API returns a broad set of POIs. However, not all are relevant or suitable. The initial
filtering removes:
 Low-rated POIs
 Duplicates
 Irrelevant business categories
 Locations too far from the city centre
2. Preference-Based Filtering
User-selected interests directly influence POI categories:
 Culture → temples, museums, heritage sites
 Nature → gardens, beaches, lakes
 Food → popular restaurants, cafés
 Shopping → markets, malls
POIs outside the chosen categories are discarded.
3. Time & Duration Appropriateness
Each POI is assigned an estimated visit duration. POIs with unrealistic durations or restricted operating hours
may be excluded or re-prioritised.
4. Priority Scoring Model
A composite score ranks POIs based on:
 Google rating
 Popularity
 Category relevance
 Zoom-level prominence (indicates general tourist relevance)
 Weather suitability (after scoring)

Dept. of CSE (IoT & CyS including BCT) 2025-26 38

A TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

5.4 TTDP-Based Scheduling

The core itinerary scheduling engine draws from the Tourist Trip Design Problem, a variation of the
Orienteering Problem involving selection and sequencing of attractions within time constraints.
1. Problem Formulation
The scheduling engine considers:
 Available hours per day
 POI durations
 Travel times between POIs
 Opening and closing times
 Weather suitability
 User preferences
2. Greedy Initial Selection
The first stage selects POIs with:
 High priority scores
 Feasible durations
 Good weather alignment
 Proximity to each other
3. Time Slot Allocation
Each day is treated as a container with fixed capacity (e.g., 8–10 hours). The
engine fills the container by placing POIs sequentially while ensuring:
 Travel time + visit duration ≤ remaining time
 No time window violations
 Weather thresholds are maintained
4. Multi-Day Partitioning
After selecting the complete set of POIs, they are distributed across the number of travel days to ensure
balanced workloads.
5. Real-Time Adaptability
Weather changes trigger:
 Reordering of POIs
 Replacement of outdoor POIs
 Shifting of long-duration activities
This adaptive TTDP extension aligns with the innovation described in your conference work.

Dept. of CSE (IoT & CyS including BCT) 2025-26 39

A TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

5.5 Routing Optimisation (2-opt, Heuristics)

Efficient routing ensures travellers do not waste time travelling unnecessarily between POIs.
1. Initial Route Construction
A naive greedy route is created:
 Start at a central location
 Pick the closest next POI
 Continue until the day’s schedule is filled
While fast, this approach may produce suboptimal inter-POI paths.
2. 2-Opt Refinement
The system applies a classical 2-opt heuristic:
 Identify route segments that form an inefficient crossover
 Swap the segments
 Recalculate total travel distance
 Accept the swap if improvement is found
This reduces unnecessary detours and sharpens route compactness.
3. Travel Duration Validation
Routes are validated against Google Directions estimates to retain real-world feasibility.
4. Weather-Aware Routing Adjustments
If an outdoor POI must be moved to a particular time window due to weather:
 The route is rearranged
 The 2-opt refinement runs again to optimise the new layout
This blend of greedy selection + local optimisation is a core methodology highlighted in your
conference paper.
5.6 Budget Estimation Module
Budget plays an important role in travel planning, yet most itinerary systems ignore this factor. The
proposed system provides a lightweight cost estimation model to support financial planning.
1. Entry Fee Estimation
Each POI is mapped to typical entry fees (if known).
Outdoor public spaces often have no cost; museums and attractions have fixed ticket prices.
2. Travel Cost Estimation
Based on:
 Travel distances
 Mode of transport (default: car/auto)
 Average city-level fare estimates

Dept. of CSE (IoT & CyS including BCT) 2025-26 40

A TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

3. Food and Miscellaneous Estimates

User-selectable options (e.g., “budget”, “moderate”, “premium”) influence daily food estimations.
4. Total Trip Cost Summary
The system aggregates:
 Entry fees
 Travel costs
 Food allowances
The resulting total is displayed in the summary page and included in the downloadable ticket.
5.7 Notification & Ticket Generation Logic
The final stage of the methodology focuses on enhancing accessibility and user convenience through
summarisation and notifications.
1. Itinerary Summary Generation
The engine formats:
 Multi-day itinerary
 Weather icons
 Travel times
 Cost estimates
into a structured PDF-style summary.
2. WhatsApp & Email Integration
The system supports:
 Sending summary links
 Delivering confirmation notifications
 Sharing itinerary documents
3. Confirmation Window (UX Step)
Before generating the final ticket, the user is shown a confirmation popup (as seen in your uploaded
screenshot), ensuring they approve the itinerary.
4. Re-generability
Users may:
 Re-generate an itinerary
 Edit preferences
 Trigger reruns of weather-aware scheduling
This keeps the system flexible and user-driven.

Dept. of CSE (IoT & CyS including BCT) 2025-26 41

 IMPLEMENTATION

Dept. of CSE (IoT & CyS including BCT) 2025-26 42

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 6
IMPLEMENTATION

This chapter describes the technical implementation of the Travel Itinerary Planner with Weather
Integration. It details the selected technologies, backend structure, frontend development, API
integrations, authentication mechanisms, database schema, and the testing approach. The goal of this
chapter is to present a clear understanding of how the system transitions from theoretical design to a
functioning application.
6.1 Technology Stack
The system is developed using a modern, scalable, and API-driven technology stack to support real-
time communication, dynamic itinerary generation, and secure user interactions. The major technologies
include:
1. Programming Language: Python
Python is chosen for its strong ecosystem, support for rapid prototyping, and extensive libraries for web
development and API communication. Its readability and modularity simplify maintenance and
scalability.
2. Web Framework: Django
Django provides:
 Robust Model–View–Template (MVT) architecture
 Built-in ORM for database handling
 Secure user authentication
 Rapid development capabilities
Its structure allows smooth separation of concerns, ensuring that backend logic, database models, and
frontend templates remain maintainable.
3. Frontend Technologies
The frontend uses:
 HTML5 for content structure
 CSS3 and Bootstrap for layout, responsiveness, and styling
 JavaScript for dynamic behaviour
These tools ensure cross-device compatibility and a user-friendly interface.
4. External APIs
 Google Maps Places API – fetches POIs
 Google Directions API – returns travel durations and routes
 OpenWeatherMap API – provides real-time and forecast weather
These third-party services power the system’s dynamic and context-aware behaviour.

Dept. of CSE (IoT & CyS including BCT) 2025-26 43

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

5. Database
Django’s ORM typically uses SQLite for development and PostgreSQL for production environments.
SQLite is lightweight, while PostgreSQL supports scalability and concurrency.
6. Deployment Environment
The system is deployable on cloud platforms such as Heroku or AWS, though deployment is flexible
due to Django’s portability.

6.2 Django Backend Modules

The backend is structured into modular Django apps, each responsible for a specific set of tasks. This
ensures separation of logic and improves maintainability.
1. users Module
Responsible for:
 Registration
 Login
 OTP-based verification
 Session handling
 Password management
2. trips Module
Handles:
 Trip creation
 Preference collection
 Trip summary generation
 Itinerary retrieval
The module stores user-defined parameters and ensures they are passed to the itinerary generator.
3. poi_manager Module
Manages POI interactions, including:
 API calls to Google Places
 Filtering and prioritisation
 Category-based mapping
 Internal caching of POI metadata
4. weather_engine Module
Responsible for:
 Fetching weather data from OpenWeatherMap

Dept. of CSE (IoT & CyS including BCT) 2025-26 44

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

 Computing weather suitability scores

 Passing weather conditions to the scheduling engine

5. Firmware Implementation Code

def validate_dates(start_date, end_date):
if start_date > end_date:
return False
return True

def calculate_budget(days, travel_type):

daily_cost = 0
if travel_type == "budget":
daily_cost = 1500
elif travel_type == "standard":
daily_cost = 3000
elif travel_type == "luxury":
daily_cost = 6000
return daily_cost * days

def suggest_packing_items(weather_description):
items = []
if "rain" in weather_description:
[Link](["Umbrella", "Raincoat", "Waterproof shoes"])
elif "clear" in weather_description:
[Link](["Sunglasses", "Sunscreen", "Hat"])
else:
[Link](["Comfortable clothes", "Light jacket"])
return items

class TravelPreferencesForm([Link]):
TRAVEL_CHOICES = [
('budget', 'Budget'),

Dept. of CSE (IoT & CyS including BCT) 2025-26 45

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

('standard', 'Standard'),
('luxury', 'Luxury'),
]

travel_type = [Link](choices=TRAVEL_CHOICES)
number_of_people = [Link](min_value=1, max_value=10)

def extended_plan_trip(request):
itinerary = []
weather_info = {}
packing_list = []
estimated_budget = 0

if [Link] == 'POST':
form = TripForm([Link])
preference_form = TravelPreferencesForm([Link])

if form.is_valid() and preference_form.is_valid():

destination = form.cleaned_data['destination']
start_date = form.cleaned_data['start_date']
end_date = form.cleaned_data['end_date']
travel_type = preference_form.cleaned_data['travel_type']
people = preference_form.cleaned_data['number_of_people']

if validate_dates(start_date, end_date):
total_days = (end_date - start_date).days + 1

weather_info = get_weather_details(destination)
itinerary = generate_itinerary(destination, total_days, weather_info)

estimated_budget = calculate_budget(total_days, travel_type) * people

packing_list = suggest_packing_items(weather_info['description'])

else:

Dept. of CSE (IoT & CyS including BCT) 2025-26 46

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

form = TripForm()
preference_form = TravelPreferencesForm()

context = {
'form': form,
'preference_form': preference_form,
'itinerary': itinerary,
'weather': weather_info,
'budget': estimated_budget,
'packing': packing_list
}

return render(request, 'extended_plan.html', context)

urlpatterns += [
path('extended-plan/', extended_plan_trip, name='extended_plan'),
]

extended_html_template = """
<form method="POST">
{% csrf_token %}
{{ form.as_p }}
{{ preference_form.as_p }}
<button type="submit">Create Detailed Travel Plan</button>
</form>

{% if itinerary %}
<h2>Detailed Travel Itinerary</h2>

<p><b>Estimated Budget:</b> ₹{{ budget }}</p>

<h3>Packing Checklist</h3>
<ul>

Dept. of CSE (IoT & CyS including BCT) 2025-26 47

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

{% for item in packing %}

<li>{{ item }}</li>
{% endfor %}
</ul>

<h3>Day-wise Plan</h3>
<ul>
{% for item in itinerary %}
<li>
<strong>{{ [Link] }}</strong> :
{{ [Link] }} |
Weather: {{ [Link] }},
Temperature: {{ [Link] }}°C
</li>
{% endfor %}
</ul>
{% endif %}
"""

def validate_dates(start_date, end_date):

if start_date > end_date:
return False
return True

def calculate_budget(days, travel_type):

daily_cost = 0
if travel_type == "budget":
daily_cost = 1500
elif travel_type == "standard":
daily_cost = 3000
elif travel_type == "luxury":
daily_cost = 6000
return daily_cost * days

Dept. of CSE (IoT & CyS including BCT) 2025-26 48

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

def suggest_packing_items(weather_description):
items = []
if "rain" in weather_description:
[Link](["Umbrella", "Raincoat", "Waterproof shoes"])
elif "clear" in weather_description:
[Link](["Sunglasses", "Sunscreen", "Hat"])
else:
[Link](["Comfortable clothes", "Light jacket"])
return items

class TravelPreferencesForm([Link]):
TRAVEL_CHOICES = [
('budget', 'Budget'),
('standard', 'Standard'),
('luxury', 'Luxury'),
]

travel_type = [Link](choices=TRAVEL_CHOICES)
number_of_people = [Link](min_value=1, max_value=10)

def extended_plan_trip(request):
itinerary = []
weather_info = {}
packing_list = []
estimated_budget = 0

if [Link] == 'POST':
form = TripForm([Link])
preference_form = TravelPreferencesForm([Link])

if form.is_valid() and preference_form.is_valid():

destination = form.cleaned_data['destination']

Dept. of CSE (IoT & CyS including BCT) 2025-26 49

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

start_date = form.cleaned_data['start_date']
end_date = form.cleaned_data['end_date']
travel_type = preference_form.cleaned_data['travel_type']
people = preference_form.cleaned_data['number_of_people']

if validate_dates(start_date, end_date):
total_days = (end_date - start_date).days + 1

weather_info = get_weather_details(destination)
itinerary = generate_itinerary(destination, total_days, weather_info)

estimated_budget = calculate_budget(total_days, travel_type) * people

packing_list = suggest_packing_items(weather_info['description'])

else:
form = TripForm()
preference_form = TravelPreferencesForm()

context = {
'form': form,
'preference_form': preference_form,
'itinerary': itinerary,
'weather': weather_info,
'budget': estimated_budget,
'packing': packing_list
}

return render(request, 'extended_plan.html', context)

urlpatterns += [
path('extended-plan/', extended_plan_trip, name='extended_plan'),
]

Dept. of CSE (IoT & CyS including BCT) 2025-26 50

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

extended_html_template = """
<form method="POST">
{% csrf_token %}
{{ form.as_p }}
{{ preference_form.as_p }}
<button type="submit">Create Detailed Travel Plan</button>
</form>

{% if itinerary %}
<h2>Detailed Travel Itinerary</h2>

<p><b>Estimated Budget:</b> ₹{{ budget }}</p>

<h3>Packing Checklist</h3>
<ul>
{% for item in packing %}
<li>{{ item }}</li>
{% endfor %}
</ul>

<h3>Day-wise Plan</h3>
<ul>
{% for item in itinerary %}
<li>
<strong>{{ [Link] }}</strong> :
{{ [Link] }} |
Weather: {{ [Link] }},
Temperature: {{ [Link] }}°C
</li>
{% endfor %}
</ul>
{% endif %}
""

Dept. of CSE (IoT & CyS including BCT) 2025-26 51

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

6. scheduler Module
Represents the core itinerary-planning logic:
 TTDP-inspired activity selection
 Greedy slot allocation
 2-opt route refinement
 Dynamic reordering based on weather suitability

7. notifications Module
Supports:
 Email sending
 WhatsApp message integration (external API dependent)
 Push notifications for confirmation and summary delivery

8. tickets Module
Handles:
 PDF summary generation
 Ticket formatting
 Download link creation
This modular backend architecture reflects the layered system approach described in your conference
report.

6.3 Frontend Implementation

The frontend emphasises simplicity, responsiveness, and clarity. Users interact with the system through
well-designed screens, each supported by backend templates and dynamic components.

1. Homepage
Displays options to create a new trip, explore features, or log in.
Design principles include minimalism, large buttons, and clear navigation.

2. Login Interface
Responsive form with:
 Username and password fields
 OTP field (after verification request)

Dept. of CSE (IoT & CyS including BCT) 2025-26 52

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

3. Trip Overview Screen

Collects:
 Destination
 Dates
 Preferences
 Number of travellers
4. Itinerary View
Displays:
 Day cards
 Time slots
 POIs with icons
 Weather badges (sun, cloud, rain)
 Travel durations between activities
JavaScript enhances user interaction for hovering, collapsing rows, and reading extended descriptions.
5. Summary Page
Shows consolidated information:
 Total cost
 Weather forecast
 List of all POIs
 Travel time per day
The page also includes options to generate tickets or share itineraries.
6. Confirmation Popup
Prevents accidental generation or overwriting of itineraries.
The frontend and backend interact via Django templates using context dictionaries to populate dynamic
content.
6.4 Google Maps API Integration
Google Maps plays a crucial role in retrieving POIs and computing travel times.
1. Using Google Places API
The system sends HTTP GET requests to retrieve:
 POI names
 Coordinates
 Ratings
 Categories
 Photos (if needed)
Results are filtered based on user preferences and POI quality metrics.

Dept. of CSE (IoT & CyS including BCT) 2025-26 53

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

2. Using Google Directions API

The Directions API provides:
 Distance matrices
 Estimated travel durations
 Suggested routes
 Road conditions (when supported)
These results feed directly into the scheduling engine
[Link] Normalisation
API responses are converted to structured Python objects:
 poi_list
 travel_matrix
 location_map
[Link] Rate Limiting
Caching mechanisms reduce the number of repeated API calls and prevent exceeding rate limits. Your
conference paper stresses the significance of these APIs in generating real-world-aware
itineraries.

Dept. of CSE (IoT & CyS including BCT) 2025-26 54

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

6.5 OpenWeatherMap Integration

Weather forecasting is essential for generating dynamic, adaptable itineraries.
1. Data Retrieval
The system queries:
 Hourly forecasts
 Daily forecasts
 Weather codes
 Rainfall probability
 Temperature and cloudiness
2. Data Mapping
The raw data is mapped to:
 Outdoor suitability scores
 Indoor preference logic
 Time-slot feasibility
3. Influence on Scheduling
Weather conditions influence:
 Selection of outdoor vs indoor POIs
 Reordering of activities
 Replacement of unsuitable activities
4. Caching
Weather responses are stored for several hours to prevent redundant API calls.
This integration brings practical adaptability to the planner, directly reflecting the methodology
described in your uploaded paper.
Travel Itinerary Planner- Final…

Dept. of CSE (IoT & CyS including BCT) 2025-26 55

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

6.6 OTP Authentication System

Security is an essential aspect of user account management.
1. OTP Generation
The system generates a time-bound one-time password using:
 Random token generation
 Limited validity window (e.g., 2–5 minutes)
2. OTP Delivery
Delivered through:
 Email (default)
 WhatsApp (if enabled via API integration)
3. OTP Verification
The user submits the OTP, which is matched against:
 Stored token
 Expiry timestamp
If valid, the login session is created.
4. Security Considerations
 OTPs are hashed before being stored
 Expired tokens are invalidated automatically
 Multiple failed attempts may lock the account temporarily
This mechanism ensures a safe and user-friendly authentication workflow.

6.7 Database Schema

The database uses Django’s ORM to maintain structured records.
1. User Model
Fields include:
 Username
 Email
 Password hash
 OTP fields
 Verification status

Dept. of CSE (IoT & CyS including BCT) 2025-26 56

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

2. Trip Model
Stores:
 Trip ID
 User reference
 Destination
3. POI Model
Contains:
 POI name
 Category
 Coordinates
 Rating
 Duration
 Weather classification (indoor/outdoor)
4. Itinerary Model
Stores detailed activities:
 Day index
 Time slots
 Ordered POIs
 Travel durations
 Weather suitability
5. Cache Table
Temporary storage for:
 API responses
 Route data
 Weather forecasts
This schema supports high performance, modularity, and scalability.
6.8 Testing Approach
Testing ensures that the system is reliable, functional, and secure.
1. Unit Testing
Each backend module is tested independently:
 Scheduler
 Weather engine
 POI manager
 Notification system
Python’s unittest and Django’s built-in testing tools are used.

Dept. of CSE (IoT & CyS including BCT) 2025-26 57

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

2. Integration Testing
Ensures API interactions function correctly:
 Places API response mapping
 Directions API travel durations
 Weather API scoring
3. UI/UX Testing
Verifies:
 Responsiveness
 Usability on mobile and desktop
 Accuracy of displayed itineraries
4. Performance Testing
Evaluates:
 Speed of itinerary generation
 API response handling under load
 Database query efficiency
5. Security Testing
Includes:
 OTP validation
 Authentication flow
 API key protection
6. User Acceptance Testing (UAT)
A small group of users interact with the system to validate:
 Ease of use
 Accuracy of itineraries
 Clarity of summaries
All testing ensures that the system behaves consistently and achieves the expected performance metrics
described in the conference research.

Dept. of CSE (IoT & CyS including BCT) 2025-26 58

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 7
RESULTS & DISCUSSION

This chapter presents the outcomes of the implemented Travel Itinerary Planner with Weather
Integration. It analyses the system’s functionality, discusses a real-world case study, evaluates
performance, and summarises user experience observations. Screenshots captured during system
execution illustrate the key stages of itinerary generation. The results validate the project’s capability to
generate dynamic, weather-aware, personalised travel plans as described in the conference paper

8.1 System Screenshots

This subsection describes the major user interface screens that reflect the functionality of the developed
system. Each screenshot corresponds to a logical stage in the itinerary-planning workflow.

1. Homepage Interface
The homepage presents a clean, minimal layout offering options to start planning a trip or explore
system features. The design follows a user-centric approach with large buttons, welcoming text, and a
focus on ease of navigation.

Figure 7.1: Homepage – Plan Your Perfect Trip

Dept. of CSE (IoT & CyS including BCT) 2025-26 59

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
2. Features Overview Screen
This interface displays the core capabilities of the system, including weather-based planning, real-time
routing, POI personalisation, and automated cost estimation. Icons and short descriptions help users
quickly understand the tool’s benefits.

Figure 7.2: Features Overview – Why Choose TravelPlanner

3. Login Interface (OTP Authentication)

The login screen includes fields for entering credentials and receiving an OTP. It demonstrates the
system’s secure authentication mechanism, ensuring that users can safely access and manage trip data.

Figure 7.3: Login & Trip Creation Interface

Dept. of CSE (IoT & CyS including BCT) 2025-26 60

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
4. Daily Itinerary Screen
The itinerary display uses day-wise cards containing:
 POI names
 Travel durations
 Category badges

This layout enables users to interpret their schedule intuitively.

Figure 7.4 Daily Itinerary UI

5. Trip Summary Screen

The summary page consolidates:
 Total estimated cost
 Daily schedule
 Weather forecasts
 Travel time breakdown
Users can download or share the summary from this interface.

Figure 7.5 Trip Summary Page

Dept. of CSE (IoT & CyS including BCT) 2025-26 61

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
6. Confirm Booking Window
A popup window prompts users to confirm before generating the final itinerary or ticket, preventing
accidental regeneration.

Figure 7.6. Confirm Booking Window

7. System Architecture Diagram

A popup window prompts users to confirm before generating the final itinerary or ticket, preventing
accidental regeneration.

Figure7.7 System Architecture Diagram

Dept. of CSE (IoT & CyS including BCT) 2025-26 62

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
8. Sequence Diagram Screen
The sequence diagram visually represents the internal flow from the user request to backend operations
and API interactions. It validates that the system follows a structured, logical execution path. These
screenshots collectively demonstrate the system’s robustness and the clarity of its user experience
design.

Figure [Link] Sequence Diagram

Dept. of CSE (IoT & CyS including BCT) 2025-26 63

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

8.2 Case Study: Mumbai Trip

To evaluate the system in a real-world setting, a three-day trip to Mumbai was used as a case study.

Input Parameters
 Destination: Mumbai
 Duration: 3 days
 Preferences: Culture, food, beaches, sightseeing
 Travellers: 2
 Budget Preference: Moderate
System Workflow
1. Google Places API retrieved POIs such as Marine Drive, Gateway of India, Elephanta Caves,
Colaba Market, Juhu Beach, and Prince of Wales Museum.
2. OpenWeatherMap fetched three-day forecasts, including humidity levels, rainfall probability,
and cloud cover.
3. The TTDP-based scheduler arranged POIs into feasible daily schedules.

4. 2-opt refinement reduced unnecessary travel, particularly in congested regions.

Generated Itinerary (Condensed Interpretation)

 Day 1: Marine Drive (morning), Gateway of India, Colaba Market → favourable clear weather.

 Day 2: Elephanta Caves shifted to midday due to predicted morning rainfall; indoor museum visit
added to morning slot.
 Day 3: Juhu Beach placed in evening due to lower UV index and pleasant temperature.

Outcome
The generated itinerary reflected:

 Reduced travel time

 Logical sequencing

 Weather-aware adjustments
 Inclusion of preferred POIs
The case study validates the system’s capability to generate realistic and adaptable itineraries.

Dept. of CSE (IoT & CyS including BCT) 2025-26 64

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

8.3 Weather-Aware Adjustments

Weather suitability plays a significant role in determining the timing of activities. The following
observations demonstrate the effectiveness of the Weather Suitability Scoring Model:

1. Outdoor Activities Prioritised in Clear Weather

Outdoor POIs such as beaches, promenades, or hill viewpoints were placed during time slots with high
suitability scores (clear or partly cloudy). This improved the tourist experience and reduced discomfort.

2. Rain-Affected Hours Optimised

When rainfall forecasts exceeded threshold values, outdoor POIs were automatically replaced with
indoor alternatives such as cafés, markets, or museums. This prevented itinerary disruption.

3. Heatwave Considerations
Midday heat triggered rescheduling, placing labour-intensive visits earlier or later in the day. The
system ensured safety and comfort by avoiding extreme heat periods.

4. Hour-by-Hour Weather Influence

Hourly weather forecasts allowed fine-grained scheduling adjustments, increasing itinerary accuracy.
These dynamic behaviours align with the weather-aware methodology in the conference paper and
significantly improve real-world applicability.

8.4 Cost Estimation Output

The system provides a structured cost breakdown that enhances planning transparency:

1. Entry Fees
Attraction-specific fees were aggregated to estimate total cultural or heritage costs.

2. Transportation Costs
Estimated using:
 Distance travelled
 Average ride fares per kilometre

 Number of daily transfers

3. Food & Miscellaneous Expenses

Calculated according to the selected spending tier (budget/moderate/premium).

4. Final Summary Output

A consolidated figure was displayed on the summary screen, offering travellers a realistic financial
expectation before beginning their journey.

Dept. of CSE (IoT & CyS including BCT) 2025-26 65

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

8.5 Performance Evaluation

1. Itinerary Generation Time
The itinerary engine typically completes POI selection, weather scoring, routing, and scheduling in 2– 5
seconds, depending on:
 Number of candidate POIs
 API response speed

 Device/browser performance

2. API Efficiency
Caching reduced redundant API requests, improving performance and preventing rate limit violations.

3. Routing Accuracy
Google Directions API ensured high accuracy in travel time estimation. In congested cities like Mumbai or
Bengaluru, travel predictions remained within acceptable variance.

4. Scalability
Django’s modular structure allowed efficient handling of multiple user requests without degradation.

5. Reliability
Testing confirmed that:

 OTP verification was stable

 Weather updates were accurate within API limits
 Itinerary regeneration responded correctly to changes

The evaluation reflects that the system demonstrates both practical performance and robustness.

8.6 User Experience Observations

Qualitative observations from trial users and controlled testing sessions indicate strong usability:

1. Intuitive Design
Users found the homepage, trip overview, and itinerary screens easy to navigate. The card-based
itinerary display was highlighted as particularly clear.

2. Weather Integration Appreciated

Users valued the weather-aware adjustments, reporting fewer “unexpected disruptions” during
planning.

Dept. of CSE (IoT & CyS including BCT) 2025-26 66

 TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
The system’s performance was analysed based on key operational metrics:

6. Itinerary Generation Time

The itinerary engine typically completes POI selection, weather scoring, routing, and scheduling in 2– 5
seconds, depending on:

 Number of candidate POIs

 API response speed

 Device/browser performance

7. API Efficiency
Caching reduced redundant API requests, improving performance and preventing rate limit violations.

8. Routing Accuracy
Google Directions API ensured high accuracy in travel time estimation. In congested cities like Mumbai or
Bengaluru, travel predictions remained within acceptable variance.

9. Scalability
Django’s modular structure allowed efficient handling of multiple user requests without degradation.

10. Reliability
Testing confirmed that:

 OTP verification was stable

 Weather updates were accurate within API limits

 Itinerary regeneration responded correctly to changes

The evaluation reflects that the system demonstrates both practical performance and robustness.

8.7 User Experience Observations

Qualitative observations from trial users and controlled testing sessions indicate strong usability:

3. Intuitive Design
Users found the homepage, trip overview, and itinerary screens easy to navigate. The card-based
itinerary display was highlighted as particularly clear.

4. Weather Integration Appreciated

Users valued the weather-aware adjustments, reporting fewer “unexpected disruptions” during
planning.

Dept. of CSE (IoT & CyS including BCT) 2025-26 67

 CONCLUSION
AND
FUTURE WORK

Dept. of CSE (IoT & CyS including BCT) 2025-26 68

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CHAPTER 8
CONCLUSION & FUTURE WORK

This chapter summarises the outcomes of the Travel Itinerary Planner with Weather Integration, outlines
the key contributions of the project, reflects on its limitations, and proposes directions for future
enhancement. The developed system successfully demonstrates the feasibility of integrating weather
forecasting, route optimisation, and personalisation to generate dynamic, user-centred travel itineraries.

8.1 Summary
The project aimed to address the limitations of traditional travel planning methods by developing a
unified, intelligent, and weather-aware itinerary planner. Through the integration of Google Maps
APIs, OpenWeatherMap, and a TTDP-inspired scheduling engine, the system generates personalised
multi-day itineraries that adapt dynamically to forecasted conditions. The methodology introduced:

 Weather suitability scoring to classify POIs into favourable and unfavourable time slots
 Greedy selection combined with 2-opt routing for efficient travel sequencing
 Personalised POI filtering based on user interests
 Automated summary generation and cost estimation
 A clean, user-friendly interface that simplifies the planning experience

The results demonstrated that the system can reduce itinerary errors caused by weather, improve route
efficiency, and deliver realistic schedules aligned with tourist preferences and time constraints. The
Mumbai case study further validated the system’s capability in producing feasible multi-day travel plans
under varying weather scenarios.
Overall, the project effectively combines data-driven decision-making with user-centric design, offering
a productive and modern approach to itinerary planning.
8.2 Conclusion
The integration of weather intelligence into itinerary planning marks a significant advancement over
conventional static planning methods. By analysing weather forecasts alongside POI characteristics and
travel durations, the system produces an itinerary that is not only optimised for efficiency but also
resilient to environmental uncertainties.
The implementation of a TTDP-inspired itinerary engine coupled with real-time API data ensures that
recommendations remain grounded in actual conditions rather than hypothetical assumptions. This
results in:

Dept. of CSE (IoT & CyS including BCT) 2025-26 69

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
 More accurate activity scheduling
 Better preparation for outdoor or weather-sensitive activities
 Reduced disruption due to rainfall, temperature extremes, or low visibility

The project successfully demonstrates how external contextual factors can enhance traveller satisfaction
and reduce planning complexity. The system’s modular architecture and clean UI make it adaptable and
extendable, positioning it as a practical solution for real-world tourism applications.
8.3 Limitations
Although the system achieves its primary objectives, several limitations remain due to technological and
practical constraints:
1. Dependency on Third-Party APIs
The system relies heavily on Google Maps and OpenWeatherMap. API outages, rate limits, or key
restrictions may affect performance or data availability.
2. Limited Personalisation Scope
User preferences are currently captured at a category level (e.g., culture, food, nature). More granular
personalisation—such as user behaviour learning or sentiment profiling—is not implemented.
3. Single-City Focus
The planner is optimised for intra-city travel. Multi-city, inter-state, or international trips require
additional logic for transport scheduling and long-distance travel planning.
4. Static POI Durations
Estimated visit durations are used uniformly and may not reflect real-world variations such as waiting
times, crowd density, or individual pace.
5. Weather Forecast Accuracy
Weather predictions, especially beyond 48 hours, may vary from actual conditions. Sudden weather
changes may still disrupt the itinerary despite forecasting.
6. Simplified Budget Model
Cost estimation is approximate and does not incorporate real-time ticket pricing, surge fares, or dynamic
food costs.
7. Limited Notification Automation
Although WhatsApp and email notifications are supported, real-time push alerts for itinerary changes
are not fully automated.
These limitations do not hinder basic functionality but represent areas that can be improved in future
versions.

Dept. of CSE (IoT & CyS including BCT) 2025-26 70

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

8.4 Future Enhancements

The system has strong potential for expansion, and several improvements can significantly increase its
usability, intelligence, and commercial applicability.
1. Traffic-Aware Routing
Integrating real-time traffic congestion data would enhance travel time predictions and reduce
unexpected delays.
2. AI-Based Personalisation
Machine learning models could be introduced to learn:

 User’s past travel patterns

 Preferred activity duration
 Preferred times of day
 Behavioural preferences

This would enable highly tailored itineraries unique to each user.

3. Multi-City and Multi-Country Support
Enhancing the scheduler to support long-distance travel, including:

 Train/flight scheduling
 Hotel check-in/out timings
 Inter-city transport optimisation

4. Real-Time Itinerary Modification

Enable the system to detect:

 Unexpected weather changes

 POI closures
 Traffic disruptions

and automatically regenerate the affected portions of the itinerary.

5. Integration of Booking Services
Allow users to book:

 Hotels
 Restaurants
 Attraction tickets
directly from within the application.

Dept. of CSE (IoT & CyS including BCT) 2025-26 71

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786
6. Offline Mode
Provide partial functionality, such as viewing saved itineraries or maps, without internet connectivity.
7. Enhanced Cost Estimation
Incorporate:

 Real-time ticket prices

 Dynamic fare APIs
 Food recommendations with price ranges

8. Mobile Application Development

A dedicated mobile app could improve portability, responsiveness, and offline support.
9. Crowd Density Estimation
Using crowd-level forecasts (if available) would allow scheduling POIs during low-traffic periods for
better comfort.
10. Multi-User Collaboration
Enable group trip planning where multiple users can co-edit the itinerary simultaneously.
These enhancements would elevate the system from a robust academic prototype to a comprehensive travel
management platform capable of global deployment.

Dept. of CSE (IoT & CyS including BCT) 2025-26 72

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

CONCLUSION

The Travel Itinerary Planner with Weather Integration successfully demonstrates an intelligent,
practical, and user-centred approach to modern travel planning. By combining real-time weather
forecasting, accurate routing through Google Maps APIs, and a TTDP-inspired scheduling engine, the
system overcomes the limitations of traditional static itinerary tools. The integration of weather
suitability scoring plays a crucial role in improving the reliability of travel schedules, ensuring that
outdoor activities are placed in favourable conditions while indoor alternatives are proposed during
unfavourable weather windows.
The project also introduces meaningful personalisation by allowing users to select preferred categories
and receive curated POIs that align with their interests. Route optimisation through heuristic techniques
further enhances travel efficiency, reducing unnecessary movement and improving the usability of the
final itinerary. The system’s ability to generate detailed summaries, cost estimations, and shareable
digital tickets makes it suitable for real-world deployment, particularly for short to medium-duration
urban trips.
While the system fulfils its primary objectives, several limitations—such as dependency on third-party
APIs, simplified cost models, and limited multi-city support—highlight opportunities for further
enhancement. Future work can expand the system through AI-driven personalisation, traffic-aware
routing, booking integrations, real-time adaptive re-scheduling, and mobile application development.
Overall, the project provides a strong foundation for intelligent travel management systems and
illustrates how contextual environmental data, user preferences, and optimisation algorithms can be
combined to deliver a seamless, adaptable, and reliable travel-planning experience.

Dept. of CSE (IoT & CyS including BCT) 2025-26 73

TRAVEL ITINERARY PLANNER WITH WEATHER INTEGRATION BIC786

REFERENCES

[1] Vansteenwegen, A., Souffriau, W., & Vanden Berghe, G. Tourist Trip Design Problem: A
Comprehensive Review. A foundational review outlining TTDP models, constraints, and optimisation
strategies.
[2] Kurata, R., & Taniguchi, Y. Personalised Itinerary Generation Based on User Preferences.
Study focusing on customised POI scoring and user-interest-based travel planning.
[3] Kenteris, M., Gavalas, D., & Economou, D. Mobile Tourism Recommender Systems.
Discussion of mobile-based, context-aware tourist recommendation frameworks.
[4] Gavalas, D., & Kenteris, M. A Survey on Mobile Tourism Recommender Systems. Survey of
mobile travel recommendation techniques, personalisation approaches, and mobile usability
considerations.
[5] OpenWeatherMap Team. Weather-Aware Travel Planning APIs. Technical documentation
describing meteorological forecasting services and their relevance for planning applications.
[6] Google Maps Platform. Directions API & Places API Documentation. Routing, location data,
and POI discovery workflow documentation relevant to computational itinerary generation.
[7] Vansteenwegen, P., et al. Local Search Techniques for Tour Planning. Examination of 2-opt and
3-opt heuristics for optimising POI visitation sequences.
[8] Çetinkaya, A., & Erdem, H. Weather-Aware City Tour Planning. Research study
demonstrating indoor/outdoor suitability modelling using weather forecasts.
[9] Lee, J., & Tseng, V. Adaptive Travel Planning Using Contextual Data. Analysis of adaptive
itinerary-generation algorithms that respond to contextual changes.
[10] Conference paper . AI-Driven Travel Itinerary Planner with Weather Integration. Your
conference paper describing the system architecture, weather scoring methodology, and TTDP- based
scheduling engine.

Dept. of CSE (IoT & CyS including BCT) 2025-26 74