Problems with CN 2014.3

[Jan Horn]

Having had time now to look at the problem more closely it is clear that the problem arises because the P24 from Virginia to Aldam is now shown as an track, not even unpaved. It would then navigate using better suited unpaved road to and from Aldam rather than the track it now became. I will repost that as a map error to Garmin. The speed issue I will use the unit around Welkom this morning to see if it still persists.

[Jan Horn]

After reinstalling 2014.30 the speed indicated is now back to normal. Something must have been corrupted during the first download and installation. I would not recommend that anyone update to 2014.30 it could cause someone unfamiliar with the roads to some destinations to be routed along unpaved roads while as in the case of the road to Aldam there are a paved road in fairly good nick available. I may also cause you to drive a longer route than necessary.

[dasilvarsa]

That = = = is actually unpaved road.

Have you managed to find any other errors ?
I played for about half an hour in Basecamp switching between 2014.2 and 2014.3 and cannot find any other errors near my favourite spots.

[fugglefeet]

Did a test run today with CN 2014.30 and only found one glitch in Ikageng, where it wanted to take me through an open field to get to a school. When I saw there was no way I could continue with the route (road was closed permanently and overgrown!), I continued to drive and the unit automatically recalculated a new route with a new arrival time and distance to match.

Darryl

[Jan Horn]

No other errors but does not mean it does not exists. It is virtually impossible to find them without spending hours swithing between the various versions of CN to comparing the rendering. I have decided not to use 2014.3 but to switch back to 2014.2 until the next upgrade. I cannot afford to use a map set with obvious errors, I may end up like the little old lady that went on a trip to family 50 miles away and drove 1500 miles to get there following the GPS instructions
Both Garmap and CN are not very consistent in the way they show unpaved roads and tracks. The calculation by 2014.3 uses unpaved roads from where it leaves the N5 up to Aldam Estates resort some 35 km. I for one would not be thrilled If the GPS took me along a 144 km trip of which 35 is unpaved just to find out that I could have made the trip in 64km on paved roads all the way.

[fugglefeet]

I will in the meantime continue to test CN 2014.30 to see what it does and if it does have any other errors that haven't crawled out of the woodwork yet. Will keep everyone posted with the caveats.

Darryl

[Jan Horn]

There are a lot more all over the country. It would mainly effect navigation on minor roads. One should be very careful when venturing in unfamiliar territories using 2014.3 it may just take you on a wide detour.

[fugglefeet]

Are these errors that have been reported to Garmin, or is this feedback from other end users? Could this result in a complete revision of the mapset? Please keep us posted on what you manage to find out. Thanks in advance.

Darryl

[dasilvarsa]

Obviously OFF TOPIC
Exept for You, I, and Jan nobody says anything anymore !
I wonder Why ?

[Jan Horn]

I have reported the problem I had with the route to Aldam with screen shots highlighting the problem to Garmin using the e mail as per MN's post in this forum. I have had no feed back or even an acknowledgement from them. That makes me unsure whether they received my mail. They changed a lot of the roads from a solid outline rendering to a dotted outline. When you hover the curser over those roads indicated in solid outlines it is indicated as "road" and dotted outline is shown as "unpaved road". I received some images comparing between 2014.3 and older versions showing where roads previously shown in solid outlines are now shown in dotted outlines. Around the Aldam area there are a lot of unpaved roads still shown with solid outlines and the PND will navigate you along these even though they are unpaved rather than along the paved road now shown in a dotted outline. The problem is that one can compare and find where the road categories has been changed looking at the differences in rendering but it is impossible to determine which paved roads has now been categorised wrongly as unpaved as in the case of the road from Virginia to Aldam and which unpaved roads are not categorised as such at all. One can change your avoidance settings to allow navigation on unpaved roads but that open another can of worms. I doubt if the errors that crept in will effect your city navigation but there is a real possibility that when you venture into the unknown your may end up traveling along unpaved and at a far grater distance than you could have. I will stick to 2014.2 until the next update.