![]() |
In the first week of March, as the conflict between the United States and Iran erupted, delivery drivers like Saeed Ahmed continued to work in Dubai.
"We found it very frustrating. We usually knew the way, but in unfamiliar areas we had to constantly call customers, delay deliveries and annoy them", Ahmed told Rest of the World.
This is not an isolated incident. military These systems can block GPS signals completely or falsify the signal, causing the device to report a false location.
According to data from Windward, a maritime intelligence company, more than 1,650 ships in the Middle East on 7 March were affected by faulty GPS signals, an increase of 55% over the previous week.
"Any interfering signal will affect all GNSS receivers within range, including smartphones", said Thomas Withington, an independent electronic warfare expert.
Older drivers are adapting by memory. Muhammad Asif, a driver in Dubai for more than 20 years, says that maps sometimes show distant locations. "The map tells me 40 minutes when I have five minutes to get there", said Muhammad Asif. In this case, he navigates himself based on experience.
On logistics platforms, incorrect location data causes a host of problems. Drivers are assigned erroneous orders, resulting in delivery times that are difficult to predict accurately.
"Core logistics systems rely heavily on real-time location data. In GPS jamming incidents, we have seen a consequential impact on operational seamlessness. Automatic allocation logic is disrupted", said Raman Pathak, CEO of Jeebly.
"The GPS signal comes from a satellite 20,000 kilometers away. When it arrives, the signal is already very weak and susceptible to interference; an even stronger signal from the ground can make the device believe that it's somewhere else entirely", explains Jim Stroup of AQNav.
After more than a month of war, drivers are still trying to adapt. "Before, we followed the map; now we have to use our memory", Ahmed says.
See also: https://znews.vn/mu-duong-vi-chien-su-iran-post1640624.html










Comment (0)