DESC:CROSS REFERENCE TO RELATED APPLICATION
This application is based on and derives the benefit of Indian Provisional Application IN202241059204, the contents of which are incorporated herein by reference.
TECHNICAL FIELD
Embodiments disclosed herein relate to vehicle safety systems and more particularly to determining vehicles driving in a wrong direction on the road; i.e., against the legally permitted traffic direction.
BACKGROUND
Currently, in locations (such as India), vehicles (such as two wheelers, four wheelers, passenger vehicles, commercial vehicles, and so on) tend to drive in a wrong direction on the roads. Examples of this can be, but not limited to, driving in a wrong direction on a one-way street, driving on the right side of the road, and so on. This can be dangerous and can result in accidents; hereby causing death and/or injuries.
Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.
OBJECTS
The principal object of embodiments herein is to disclose methods and systems to determining vehicles driving in the wrong direction of the traffic by recording latitude and longitude of the vehicle in time-order by comparing an azimuth angle of road measurement and the azimuth angle of latitude/longitude information with a threshold value.
These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF FIGURES
Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:
FIG. 1 depicts a system for determining vehicles driving in the wrong direction of the traffic, according to embodiments as disclosed herein;
FIG. 2 depicts one or more components of the vehicle, according to embodiments as disclosed herein;
FIG. 3 depicts the wrong way determination module, according to embodiments as disclosed herein;
FIG. 4 depicts a flowchart for determining vehicles driving in the wrong direction of the traffic, according to embodiments as disclosed herein; and
FIG. 5 depicts a flowchart for determining vehicles driving in the wrong direction of the traffic, according to embodiments as disclosed herein.

DETAILED DESCRIPTION
The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.
The words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.
Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts/sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components/modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components/elements/steps is for the purposes of this description and should not be construed as sequential ordering/placement/occurrence unless specified otherwise.
The embodiments herein achieve methods and systems to determining vehicles driving in the wrong direction of the traffic by recording latitude and longitude of the vehicle in time-order by comparing an azimuth angle of road measurement and the azimuth angle of latitude/longitude information with a threshold value. Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
FIG. 1 depicts a system for determining vehicles driving in the wrong direction of the traffic. The system as depicted, comprises at least one vehicle 101, and a wrong way determination module 102. Examples of the vehicle 101 can be, but not limited to, a moped, a scooter, a motorbike, a car, a truck, a van, a bus, a bicycle, or any other vehicle that can operate on a road. The vehicle 101, as depicted in FIG. 2, comprises a location sensing module 101A, at least one communication module 101B, and a memory 101C.
The location sensing module 101A can determine the current location of the vehicle 101, using at least one suitable means, such as, but not limited to, Global Positioning System (GPS), GPS Aided GEO Augmented Navigation (GAGAN), Galileo, cell triangulation, or any other means capable of determining the current location of the vehicle 101. The location sensing module 101A can communicate the determined location to the wrong way determination module 102 using the communication module 101B, along with the respective timestamps. In an embodiment herein, the location sensing module 101A can communicate the determined location to the wrong way determination module 102 using the communication module 101B in real-time. In an embodiment herein, the location sensing module 101A can communicate the determined location to the wrong way determination module 102 using the communication module 101B at pre-defined time intervals. In an embodiment herein, the location sensing module 101A can communicate the determined location to the wrong way determination module 102 using the communication module 101B on at least one pre-defined event occurring (for example, the vehicle making a turn, joining a road, the vehicle starting to move, and so on).
The communication module 101B can use at least one of a wired and/or wireless means for enabling communication with at least one external entity, such as, but not limited to, the wrong way determination module 102.
The memory 101C can comprise data related to a user of the vehicle 101, data related to the vehicle 101, trips taken by the user, previous trips, determined location(s) of the vehicle 101, data sent to the vehicle from other sources (such as, but not limited to, the wrong way determination module 102), and so on. Examples of the memory 101C can be, but not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The memory 101C may also include one or more computer-readable storage media. The memory 101C may also include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 101C may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory 101C is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
The wrong way determination module 102, as depicted in FIG. 3, can comprise a controller 102A, at least one communication module 102B, and a memory 102C. In an embodiment herein, the wrong way determination module 102 can be a dedicated device. In an embodiment herein, the wrong way determination module 102 can be implemented on at least one of a server, the Cloud, and so on. In an embodiment herein, the controller 102A can be in the form of a processor. The examples of the processor can be, but not limited to, at least one of a single processer, a plurality of processors, multiple homogeneous or heterogeneous cores, multiple Central Processing Units (CPUs) of different kinds, microcontrollers, special media, and other accelerators. The processor may be a general purpose processor, such as an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an Artificial Intelligence (AI)-dedicated processor such as a neural processing unit (NPU).
The memory 102C can comprise information received from the vehicle 101, geospatial index data (such as, but not limited to, the H3 index, the Google S2 index, and so on), latitude/longitude (lat/long) coordinates of various locations (such as roads, or any other locations on which the vehicle may travel through), data received from the vehicle, generated alerts, user data, current travel route of the user, and so on. The memory 102C can be configured as a separate device independent of the processor, or may be integrated in the processor. The examples of the memory 102C can be, but not limited to, NAND, embedded Multimedia Card (eMMC), Secure Digital (SD) cards, Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), solid-state drive (SSD), and so on. The memory 102C may also include one or more computer-readable storage media. The memory 102C may also include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 102C may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
The communication module 102B can use at least one of a wired and/or wireless means for enabling communication with at least one external entity, such as, but not limited to, at least one vehicle 101.
On determining that a vehicle 101 is performing a journey (based on information received from the vehicle 101) or has completed a journey, the controller 102A can determine an intersection between the geospatial index of the route that a user of the vehicle is intending to travel and the journey data. In an embodiment herein, the journey data can be real-time data. In an embodiment herein, the journey data can be data tracing the travel, once the travel has been completed. The determined intersection can be a portion of the journey that is to be analyzed for checking if the user has travelled in the wrong direction and is the commonality between them. The controller 102A can sort the journey data in order. The controller 102A can determine the lat/long of the start and end of specific roads (wherein road herein can refer to any path, over which the vehicle can travel), based on data stored in the memory 102C. The controller 102A can sort the lat/long in terms of time, based on their respective timestamps. The controller 102A can then determine the azimuth angle of the road and the azimuth angle of consecutive lat/longs. In an embodiment herein, the azimuth angle of the road can be determined using a Geodesic Inverse Formula (also known as Vincenty’s inverse formula) for ellipsoid. The azimuth angle of consecutive lat/longs is the angle between two consecutive lat/longs.
The azimuth angles can be determined using an inverse geodesic approach. Given the coordinates of the two points (F_1, L_1) and (F_2, L_2), the inverse problem finds the azimuths a_1, a_2 and the ellipsoidal distance s.
sin?s= v(?(cosU_2 sin?)?^2+?(cosU_1 sinU_2-sinU_1 cosU_2 cos?)?^2 ) (1)
cos?s=sin??U_1 sinU_2+cosU_1 cosU_2 cos?? (2)?
s=arctan2 (sins,coss) (3)
sin?a= (cosU_1 cosU_2 sin??)/sin?s (4)
cos?(2s_m )=cos?s- 2sin??U_1 sinU_2 ?/(?cos?^2 a)=cos?s- 2sin??U_1 sinU_2 ?/(1-?sin?^2 a) (5)
C=f/16 ?cos?^2 a[4+f(4-3?cos?^2 a)] (6)
?=L+(1-C)f sin?a {s+C sin?s [cos?(2s_m )+C cos?s (-1+2?cos?^2 (2s_m ))]} (7)
When ? has converged to the desired degree of accuracy (10-12 corresponds to an error of approximately 0.06mm), the controller 102A evaluates the following:
U^2=?cos?^2 a ((a^2-b^2)/b^2 ) (8)
A=1-u^2/16384(4096+u^2 [-768+u^2 (320-175u^2 ] (9)
B=u^2/1024(256+u^2 [-128+u^2 (74-47u^2 ] (10)
?s=B sin??s {? cos?(2s_m )+1/4 B(cos?s [-1+2?cos?^2 (2s_m )]-B/6 cos?(2s_m ) [-3+4?sin?^2 s][-3+4?cos?^2 (2s_m )] (11)
s=bA(s-?s) (12)
a_1=arctan2(cosU_2 sin??,cosU_1 sinU_2-sinU_1 cosU_2 cos?? ) (13)
a_2=arctan2(cosU_1 sin??,-sinU_1 cosU_2+cosU_1 sinU_2 cos?? ) (14)
Wherein
a: length of semi-major axis of the ellipsoid (radius at equator).
f: flattening of the ellipsoid.
b=(1-f)a : length of semi-minor axis of the ellipsoid (radius at the poles).
U_i=arctan?((1-f) tan???_i ?) : reduced latitude.
L_1,L_2: Longitude of the points.
L=L_2-L_1: difference in longitude of two points..
?: Difference in longitude of the points on the auxiliary sphere.
a_1,a_2: forward azimuth at the points.
a: forward azimuth of the geodesic at the equator, if it were extended that far.
s : ellipsoidal distance between two points.
s : angular separation between two points.
s_1: angular separation between the point and the equator.
s_m: angular separation between the midpoint of the line and the equator.
The controller 102A can compare the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs with a pre-defined threshold for all lat/long values. If the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to the pre-defined threshold for a specific lat/long value, the controller 102A can determine that the vehicle 101 is travelling in the wrong direction at that specific lat/long value. If the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is less than the pre-defined threshold for a specific lat/long value, the controller 102A can determine that the vehicle 101 is travelling in the correct direction at that specific lat/long value. The threshold can be defined in terms of degrees. For example, the threshold can be 15 degrees, or 20 degrees.
The controller 102A can sum up all the values of lat/longs for which the user has been determined to be travelling in the wrong direction to determine the total distance that the user travelled in the wrong distance. The controller 102A can determine a score for the user, wherein the score is a ratio of the total distance that the user has travelled in the wrong distance to the total distance of the journey performed by the user.
In an embodiment herein, the controller 102A can provide an alert to the user (either on a user device (such as an app on a mobile device being used by the user for accessing the vehicle), an email, a text message, an instant message, and so on. The controller 102A can add this information to the user account, along with the determined score.
In an embodiment herein, the controller 102A can provide an alert to the user (either on a user device (such as an app on a mobile device being used by the user for accessing the vehicle), an email, a text message, an instant message, a pop-up indication, and so on, if the determined score is greater than a threshold score. The controller 102A can add this information to the user account, along with the determined score, if the determined score is greater than a threshold score. The threshold score can be defined in terms of a percentage. For example, the threshold score can be configured as 30%.
In an embodiment herein, the controller 102A can provide an alert to the user in real-time, on determining that the vehicle is travelling in the wrong direction. In an embodiment herein, the alert can be provided using an indicator on the vehicle; examples of the indicator can be, but not limited to, a dashboard of the vehicle, a central console of the vehicle, and so on. In an embodiment herein, the alert can be provided on a user device (such as an app on a mobile device being used by the user for accessing the vehicle), an email, a text message, an instant message, a pop-up indication, and so on.
FIG. 4 depicts a flowchart for determining vehicles driving in the wrong direction of the traffic. The vehicle 101 communicates the determined location (wherein the location is determined by the location sensing module 101A) to the wrong way determination module 102, along with the respective timestamps. In an embodiment herein, the vehicle 101 communicates the determined location in real-time. In an embodiment herein, the vehicle 101 communicates the determined location at pre-defined time intervals. In an embodiment herein, the vehicle 101 communicates the determined location to the wrong way determination module 102 on at least one pre-defined event occurring.
On determining that a vehicle 101 is performing a journey (based on information received from the vehicle 101) or has completed a journey, in step 401, the wrong way determination module 102 determines the intersection between the geospatial index of the route that a user of the vehicle is intending to travel and the journey data, wherein the determined intersection can be a portion of the journey that is to be analyzed for checking if the user has travelled in the wrong direction.
In step 402, the wrong way determination module 102 sorts the journey data in order. The wrong way determination module 102 determines the lat/long of the start and end of specific roads (wherein road herein can refer to any path, over which the vehicle can travel). The wrong way determination module 102 sorts the lat/long in terms of time, based on their respective timestamps. In step 403, the wrong way determination module 102 determines the azimuth angle of the road and the azimuth angle of consecutive lat/longs.
In step 404, the wrong way determination module 102 checks if the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to a pre-defined threshold for all lat/long values. If the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to the pre-defined threshold for a specific lat/long value, in step 405, the wrong way determination module 102 determines that the vehicle 101 is travelling in the wrong direction at that specific lat/long value. If the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is less than the pre-defined threshold for a specific lat/long value, the wrong way determination module 102 determines that the vehicle 101 is travelling in the correct direction at that specific lat/long value. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
FIG. 5 depicts a flowchart for determining vehicles driving in the wrong direction of the traffic. The vehicle 101 communicates the determined location (wherein the location is determined by the location sensing module 101A) to the wrong way determination module 102, along with the respective timestamps. In an embodiment herein, the vehicle 101 communicates the determined location in real-time. In an embodiment herein, the vehicle 101 communicates the determined location at pre-defined time intervals. In an embodiment herein, the vehicle 101 communicates the determined location to the wrong way determination module 102 on at least one pre-defined event occurring.
On determining that a vehicle 101 is performing a journey (based on information received from the vehicle 101) or has completed a journey, in step 501, the wrong way determination module 102 determines the intersection between the geospatial index of the route that a user of the vehicle is intending to travel and the journey data, wherein the determined intersection can be a portion of the journey that is to be analyzed for checking if the user has travelled in the wrong direction.
In step 502, the wrong way determination module 102 sorts the journey data in order. The wrong way determination module 102 determines the lat/long of the start and end of specific roads (wherein road herein can refer to any path, over which the vehicle can travel). The wrong way determination module 102 sorts the lat/long in terms of time, based on their respective timestamps. In step 503, the wrong way determination module 102 determines the azimuth angle of the road and the azimuth angle of consecutive lat/longs.
In step 504, the wrong way determination module 102 checks if the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to a pre-defined threshold for all lat/long values. If the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to the pre-defined threshold for a specific lat/long value, the wrong way determination module 102 determines that the vehicle 101 is travelling in the wrong direction at that specific lat/long value. If the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is less than the pre-defined threshold for a specific lat/long value, the wrong way determination module 102 determines that the vehicle 101 is travelling in the correct direction at that specific lat/long value.
In step 505, the wrong way determination module 102 determines the total distance that the user travelled in the wrong distance by summing all the values of lat/longs for which the user has been determined to be travelling in the wrong direction.
In step 506, the wrong way determination module 102 determines the score for the user, wherein the score is a ratio of the total distance that the user has travelled in the wrong distance to the total distance of the journey performed by the user. In step 507, the wrong way determination module 102 provides an alert to the user, based on the determined score. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.
The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in FIGs. 1, 2, and 3 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
The embodiment disclosed herein describes methods and systems to determine vehicles driving in the wrong direction of the traffic by recording latitude and longitude of the vehicle in time-order by comparing an azimuth angle of road measurement and the azimuth angle of latitude/longitude information with a threshold value. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.
The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.
,CLAIMS:STATEMENT OF CLAIMS
We claim:
1. A method (400) for determining a vehicle driving in a wrong direction, the method comprising:
determining (401), by a wrong way determination module (102), an intersection between a geospatial index of a route that a user of the vehicle is intending to travel and journey data;
sorting (402), by the wrong way determination module (102), the journey data;
determining (403), by the wrong way determination module (102), an azimuth angle of a road and an azimuth angle of consecutive latitudes/longitudes (lat/longs);
checking (404), by the wrong way determination module (102), if a difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to a pre-defined threshold for all lat/long values;
and
determining (405), by the wrong way determination module (102), that the vehicle has driven in the wrong direction, if the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to a pre-defined threshold for all lat/long values.
2. The method, as claimed in claim 1, wherein the vehicle (101) is at least one of performing a journey; and has completed a journey.
3. The method, as claimed in claim 1, wherein the determined intersection is a portion of the journey that is to be analyzed for checking if the user has travelled in the wrong direction.
4. The method, as claimed in claim 1, wherein sorting the journey data comprises:
determining, by the wrong way determination module (102), the lat/long of the start and end of specific roads along the journey; and
sorting, by the wrong way determination module (102), the lat/long in terms of time, based on respective timestamps.
5. The method, as claimed in claim 1, wherein the azimuth angle of the road is determined using a Geodesic Inverse Formula for ellipsoid.
6. The method, as claimed in claim 1, wherein the azimuth angle of consecutive lat/longs is an angle between two consecutive lat/longs.
7. The method, as claimed in claim 1, wherein the method further comprises:
determining, by the wrong way determination module (102), a total distance that the user travelled in the wrong distance by summing values of lat/longs for which the user has been determined to be travelling in the wrong direction;
determining, by the wrong way determination module (102), a score for the user, wherein the score is a ratio of the total distance that the user has travelled in the wrong distance to the total distance of the journey performed by the user; and
providing, by the wrong way determination module (102), an alert to the user, based on the determined score.
8. A module (102) configured to:
determine an intersection between a geospatial index of a route that a user of a vehicle is intending to travel and journey data;
sort the journey data;
determine an azimuth angle of a road and an azimuth angle of consecutive latitudes/longitudes (lat/longs);
check if a difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to a pre-defined threshold for all lat/long values; and
determine that the vehicle has driven in the wrong direction, if the difference between the azimuth angle of the road and the azimuth angle of consecutive lat/longs is greater than or equal to a pre-defined threshold for all lat/long values.
9. The module, as claimed in claim 8, wherein the vehicle (101) is at least one of performing a journey; and has completed a journey.
10. The module, as claimed in claim 8, wherein the determined intersection is a portion of the journey that is to be analyzed for checking if the user has travelled in the wrong direction.
11. The module, as claimed in claim 8, wherein the module (102) is configured to sort the journey data by:
determining the lat/long of the start and end of specific roads along the journey; and
sorting the lat/long in terms of time, based on respective timestamps.
12. The module, as claimed in claim 8, wherein the module (102) is configured to determine the azimuth angle of the road using a Geodesic Inverse Formula for ellipsoid.
13. The module, as claimed in claim 8, wherein the azimuth angle of consecutive lat/longs is an angle between two consecutive lat/longs.
14. The module, as claimed in claim 8, wherein the module (102) is configured to:
determine a total distance that the user travelled in the wrong distance by summing values of lat/longs for which the user has been determined to be travelling in the wrong direction;
determine a score for the user, wherein the score is a ratio of the total distance that the user has travelled in the wrong distance to the total distance of the journey performed by the user; and
provide an alert to the user, based on the determined score.