<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks Gerd, it is what it is. Then I'll stick with brouter or rwgps to make more accurate elevation profiles.<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Van:</b> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <gpetermann_muenchen@hotmail.com><br>
<b>Verzonden:</b> donderdag 20 januari 2022 00:44<br>
<b>Aan:</b> Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk><br>
<b>Onderwerp:</b> Re: [mkgmap-dev] elevation in bridges and tunnels</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Minko,<br>
<br>
there is no special flag for tunnel/bridge in the IMG format, at least we don't know any. So, Garmin software cannot detect the special case.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com><br>
Gesendet: Donnerstag, 20. Januar 2022 09:41<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] elevation in bridges and tunnels<br>
<br>
Thanks Gerd,<br>
It's a pity that this cannot be corrected. I thought the route could look where a tunnel/bridge section is (based on OSM tags) and just ignore all elevation data and starts reading it where there is no tunnel or bridge tag?<br>
<br>
________________________________<br>
Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <gpetermann_muenchen@hotmail.com><br>
Verzonden: donderdag 20 januari 2022 00:34<br>
Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk><br>
Onderwerp: Re: [mkgmap-dev] elevation in bridges and tunnels<br>
<br>
Hi all,<br>
<br>
I also don't like the wrong profile for bridges and tunnels, but there is nothing we can do about this so far.<br>
The other routers know that the have to treat bridges and tunnel special, but Garmin software doesn't have this information.<br>
We also cannot manipulate the elevation data because there may be another highway under the bridge or above the tunnel.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von lig fietser <ligfietser@hotmail.com><br>
Gesendet: Donnerstag, 20. Januar 2022 09:20<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] elevation in bridges and tunnels<br>
<br>
I've put an example on this forum (in Dutch). The brouter route (<a href="https://tinyurl.com/3nt27szy">https://tinyurl.com/3nt27szy</a>) shows a profile that is more accurate than the route in Basecamp.<br>
<br>
<a href="https://forum.wereldfietser.nl/viewtopic.php?f=3&t=30684&p=412494#p412494">https://forum.wereldfietser.nl/viewtopic.php?f=3&t=30684&p=412494#p412494</a><br>
________________________________<br>
Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens lig fietser <ligfietser@hotmail.com><br>
Verzonden: woensdag 19 januari 2022 23:55<br>
Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk><br>
Onderwerp: [mkgmap-dev] elevation in bridges and tunnels<br>
<br>
<br>
Hi guys,<br>
I came across this video on youtube, where ridewithgps.com improved their elevation profiles by ignoring the underlying altititude data of tunnel and bridges:<br>
<a href="https://youtu.be/wd-wT3EeayI">https://youtu.be/wd-wT3EeayI</a><br>
I found out that other route planners like brouter, cycle.travel and Osmand also ignores the surface altitude that lies above tunnels and underneath bridges, but mkgmap/Garmin does not. This leads to a much higher elevation gain or loss in the route profile
than the actual ride. Is it possible for mkgmap to correct this issue, or is it hard coded in the Garmin Basecamp software?<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</div>
</span></font></div>
</body>
</html>