<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Thorsten,<br><br>If I got that right we are talking about two different things.<br>The code that handles the exit:to and similar variables would stay,<br>means, the possibility to add infos to an exit node would still<br>work although nobody seems to use it.<br>I am talking about the code that adds the exit nodes to special<br>sections in the index and LBL file (e.g. LBL9 + LBL10).<br>I think that this info in the img and the corresponding code is obsolete.<br><br>My problem: The talks in year 2009 / 2010 suggest that it was possible to search <br>for exits at that time but that the search always used the basemap that came with<br>the device. One possible explanation for the - now missing - search is that the <br>Garmin software was faulty and that Garmin simply removed the option <br>instead of fixing it. Or maybe it comes only with specific devices or with special<br>maps ? <br><br>Gerd<br><br><br><div>> Date: Wed, 19 Aug 2015 12:04:41 +0200<br>> From: kukuk@suse.de<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] What's the meaning of the 'has no region' warnings?<br>> <br>> <br>> Hi,<br>> <br>> On Wed, Aug 19, Gerd Petermann wrote:<br>> <br>> > I still have no idea where the data is used. Maybe the device shows some additional<br>> > info when you drive on a motorway.<br>> > When Mark Burton committed the code with r984 he did not describe the wanted effect,<br>> > but he also seemed to be unsure about its positive effects, see here:<br>> > http://www.mkgmap.org.uk/websvn/listing.php?repname=mkgmap&rev=984<br>> > <br>> > and here:<br>> > http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q1/001293.html<br>> <br>> It looks like this is the code responsible for exit:to and similar variables.<br>> I played with this some time ago and the informations are shown in mapsource,<br>> don't remember anymore about my GPS device.<br>> The problem is, with the current way how things are mapped<br>> in OSM, it is nearly impossible to fill out this fields correct<br>> only with a style file. This would need help of mkgmap itself.<br>> That's why I stopped looking at it.<br>> <br>> But I haven't found a way to search for them, too.<br>> <br>> In the end, I would let the code stay and not remove it.<br>> <br>> Thorsten<br>> <br>> -- <br>> Thorsten Kukuk, Senior Architect SLES & Common Code Base<br>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany<br>> GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)<br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div> </div></body>
</html>