Map corrections- speed

[madkiwi]

Has anyone else noticed that if you do a road speed correction, when travelling on the corrected road it displays 1mph less than what you entered?

I changed my street to 25 mph, and the main road through town (Highway 93 through Missoula, MT) to 45 mph. Now whenever I am driving on them my TT 920 shows the maximum speeds as 24 and 44 mph respectively.

Is it just me or is that the same experience for everyone else?

App version 8.010, NA map v720.1803

Thanks

 

[just4fn]

Mine does this also. look like a bug

 

[dhn]

Mine does this also. look like a bug

It's a flaw in the software's algorithm that coverts speeds from mph to kph and back again.

 

[Michael Quinlan]

It's a flaw in the software's algorithm that coverts speeds from mph to kph and back again.

I think the bottom-line rhetorical question here is "where in the process is the error?" If the error is early enough in the process it's possible that the Map Share data being submitted to TT, and the map data being stored in your own maps is different than what you intended. If later in the process, it could be as harmless as an error converting the value for display, in which case a firmware update could correct the issue for data that had been previously entered.

 

[ar1979]

I have noticed this too.
I also noticed, when I corrected speeds of 55 or more, it was showing me the correct value. When I corrected speeds of 45 and below it always used to come up with one less. This was weird to me.

 

[cputrdoc]

I've noticed this too but I've also noticed a different peculiarity -- my complex consists of publicly-owned streets, which means it appears on the map and the city takes care of it. ...but within the complex the speed limit is 13. So I told my TomTom about it... it displays the speed limit as 14 during navigation. Edit that back to 13? No, it's already set to 13. ...but displays 14 during navigation. This looks more complicated than a "less than vs. less than or equal to" bug.

 

[madkiwi]

Something else- I was attempting to enter speeds along a route where the limit is 35 along most of the street, but drops to 25 for about 1/2 a mile. The procedure for selecting sections of road are retarded, so it takes a while.

Then after changing the section I wanted to 25, I wanted to assign 35 to the rest of the street. Well, instead of pre-selecting the street portions that I have not already edited, it selects the entire street again! So I have to use the select function (retarded) to deselect the parts of the street I edited 2 minutes before.

And how come some street sections are only a few feet long? I found as many as 5 sections in one block.

Good idea, poorly executed.

 

[Michael Quinlan]

I've noticed this too but I've also noticed a different peculiarity -- my complex consists of publicly-owned streets, which means it appears on the map and the city takes care of it. ...but within the complex the speed limit is 13. So I told my TomTom about it... it displays the speed limit as 14 during navigation. Edit that back to 13? No, it's already set to 13. ...but displays 14 during navigation. This looks more complicated than a "less than vs. less than or equal to" bug.

This would indicate to me that the value is being stored correctly, and that the error is only in the display of the number. Good news I guess, since data stored incorrectly could later be propagated through Map Share.

 

[cputrdoc]

And how come some street sections are only a few feet long? I found as many as 5 sections in one block.

Good idea, poorly executed.

Please file a Support ticket about this on TomTom's web site. I've already done so, but until and unless there are sufficient users requesting a fix, nothing will be done.