Data or Map Corruption
Posted: Fri Oct 04, 2019 2:35 pm
Hi,
Has anyone experienced a corrupt map or map database? This seems to me to be a Zumo issue and not a BaseCamp issue. Long post to follow.
I was on a trip last week-end in Connecticut and Massachusetts. A number of times my Zumo 550 seemed to loose its way while navigating. Actually, the first bit of weirdness came when telling it to follow a route crated in BaseCamp. It seemed unable to navigate. The route was displayed on the map and it was displaying the track. However, there were no prompts to follow turns or exits. The lower right-hand box that normally displays distance to next turn contained only a black arrow that seemed to point North.
Several attempts to reset the process by stopping navigation and reselecting the route did not fix this. Including turning the unit off and re-starting seemed to do nothing for this either. This lead me to believe that perhaps my exported route was corrupt.
Next I abandoned the pre-made route and told it to navigate to the favorite that was the end point of the route. This seemed to reset the navigation part of the unit’s processors. Prompts came to life.
However, the unit began to loose its way. I was following a Connecticut state highway with controlled access similar to the Interstates on our way to a proper interchange with an Interstate. The navigation prompts suddenly took me off the state highway and on to local streets. From the display, it seemed that the state road disappeared from the map display. I went back to foggy memory of the route and navigated by hand, watching the bizarre instructions and lack of roads on the map. It was dark and raining.
That evening I re-built the routes in BaseCamp and re-downloaded the gpx file to the unit. In the same session, I attempted to transfer the evening’s tracks to BaseCamp using the “Transfer” menu command. No tracks were found with this command. The tracks were found in the current.gpx file created when mounting the Zumo to the computer. I’ve not experienced this before.
A subsequent attempt to transfer tracks at the time I write this also failed to see or transfer tracks to BaseCamp. Something wrong in here.
Next day, my son drove on a trip to North Adams, MA, staring in suburban Hartford. He was navigating with Google maps on his iPhone. I had the Zumo following along trying to diagnose what was happening.
Numerous times, I watched the Zumo “run out of road” on the display and then it would recalculate, prompting to “proceed to the highlighted route” a point not near our current location shown on the Google map.
Operating environments as follows.
MacBook Pro, OS X 10.14.6, BaseCamp 4.8.4, City Navigator North America 2020.10
Zumo 550 Software Version 5.00 Audio Version 2.30, GPS SW Version 3.00
Map Info: CN North America NT 2020.10, Lower 49 States NW.
Configuration Notes: I do not keep a map in the Zumo memory. My map is a gmapsupp.img file on an SD card. I have the North America maps on one card and EU on another card.
One more note. This unit just came back from the Palm Doctor repair guy in Mankato, Minnesota. I had an outing in Minnesota since then with planned routes over city streets and County roads in rural Minnesota. No events of “getting lost”.
Has anyone experienced a corrupt map or map database? This seems to me to be a Zumo issue and not a BaseCamp issue. Long post to follow.
I was on a trip last week-end in Connecticut and Massachusetts. A number of times my Zumo 550 seemed to loose its way while navigating. Actually, the first bit of weirdness came when telling it to follow a route crated in BaseCamp. It seemed unable to navigate. The route was displayed on the map and it was displaying the track. However, there were no prompts to follow turns or exits. The lower right-hand box that normally displays distance to next turn contained only a black arrow that seemed to point North.
Several attempts to reset the process by stopping navigation and reselecting the route did not fix this. Including turning the unit off and re-starting seemed to do nothing for this either. This lead me to believe that perhaps my exported route was corrupt.
Next I abandoned the pre-made route and told it to navigate to the favorite that was the end point of the route. This seemed to reset the navigation part of the unit’s processors. Prompts came to life.
However, the unit began to loose its way. I was following a Connecticut state highway with controlled access similar to the Interstates on our way to a proper interchange with an Interstate. The navigation prompts suddenly took me off the state highway and on to local streets. From the display, it seemed that the state road disappeared from the map display. I went back to foggy memory of the route and navigated by hand, watching the bizarre instructions and lack of roads on the map. It was dark and raining.
That evening I re-built the routes in BaseCamp and re-downloaded the gpx file to the unit. In the same session, I attempted to transfer the evening’s tracks to BaseCamp using the “Transfer” menu command. No tracks were found with this command. The tracks were found in the current.gpx file created when mounting the Zumo to the computer. I’ve not experienced this before.
A subsequent attempt to transfer tracks at the time I write this also failed to see or transfer tracks to BaseCamp. Something wrong in here.
Next day, my son drove on a trip to North Adams, MA, staring in suburban Hartford. He was navigating with Google maps on his iPhone. I had the Zumo following along trying to diagnose what was happening.
Numerous times, I watched the Zumo “run out of road” on the display and then it would recalculate, prompting to “proceed to the highlighted route” a point not near our current location shown on the Google map.
Operating environments as follows.
MacBook Pro, OS X 10.14.6, BaseCamp 4.8.4, City Navigator North America 2020.10
Zumo 550 Software Version 5.00 Audio Version 2.30, GPS SW Version 3.00
Map Info: CN North America NT 2020.10, Lower 49 States NW.
Configuration Notes: I do not keep a map in the Zumo memory. My map is a gmapsupp.img file on an SD card. I have the North America maps on one card and EU on another card.
One more note. This unit just came back from the Palm Doctor repair guy in Mankato, Minnesota. I had an outing in Minnesota since then with planned routes over city streets and County roads in rural Minnesota. No events of “getting lost”.