Road height restriction not taken into account

[morbidel]

I've tested multiple known height restrictions crossings (going under a bridge), for example, in Switzerland going under the rail bridge at 47.38274468554943, 9.566837856227705 there is a 3m height restriction.

I tested this on plan.tomtom.com with a camper vehicle and a height of 3.5m and it routes me directly under this bridge.

Tested also other variations, with same results.
Any hints if I'm doing something wrong?

Thanks

 

[canderson]

It is possible that there are map errors where the maximum height is not recorded correctly, or at all.
These should be reported to TomTom.

It would be interesting to know if one of the Camper models of TomTom causes the same routing issues.

 

[brianwatts99]

Morbidel, off topic on the height restriction issue, but do you realise that expressing GPS co-ordinates to 14 decimal places, you are getting down to a positional accuracy of one-millionth of a millimetre?

 

[canderson]

Morbidel, off topic on the height restriction issue, but do you realise that expressing GPS co-ordinates to 14 decimal places, you are getting down to a positional accuracy of one-millionth of a millimetre?

Indeed. No consumer GPS is fully accurate to 5 decimal places, so 47.38274, 9.56684 is always good enough.
The problem is Google. If you click on a point and save the coordinates, it comes up with those silly numbers.

 

[brianwatts99]

Yes Canderson, I am always rounding down the Google click saved co-ordinates.
Five decimal places gives you one metre accuracy, more than enough.

Dunno about PC computers, but with Mac OSX, Control click on Google Maps shows the co-ordinates to just 5 decimal places, but if you click on that, it saves the entire crazy 14 decimal places to the computer clipboard.

But, if you highlight the co-ordinates as they are shown (to 5 decimal places), then copy with Command-C, it copies just the 5 decimal places and so you are good to paste only those five places.