<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 Colin,<br><br>I am not sure what you mean. Let me try an example:<br>I am aware that my Oregon 450t needs e.g.<br>tourism=camp_site [0x2b05 resolution 24]<br>instead of<br>tourism=camp_site [0x2b03 resolution 24]<br>which is used in the default style.<br><br>If I got you right, you want to create some kind of database to keep track of these <br>differences and a style that uses a symbol to reference the database.<br>So, for my example, we would have a database with a symbol<br>"camp_site_poi_type" and a default value 0x2b03 and a special value <br>for the Oregon 450t containing 0x2b05.<br>The style would then use something like<br><br>tourism=camp_site [db:camp_site_poi_type resolution 24]<br><br>When reading the style, mkgmap could look up the database to find <br>the right value.<br><br>If the database would use SQL, we probably need a few tables <br>for device types, groups of device types, firmware versions, etc.<br>Without SQL, it might be another XML file. <br><br>Any ideas how many differences we have and how they could be stored?<br><br>Gerd<br><br><div><hr id="stopSpelling">Date: Sun, 11 May 2014 12:22:50 +0200<br>From: colin.smale@xs4all.nl<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Subject: Re: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.<br><br>
As there are clearly differences in features supported by various models, would it maybe be an idea to externalise the differences in some way? How about a file to contain the capabilities of device types, an option to target a particular entry in that file, and a way to expose the selected device in the style files? That could also help address the differences in supported POI categories and icons.<BR>
Colin<BR>
<BR>
<div> </div>
On 2014-05-11 11:52, Gerd Petermann wrote:<BR>
<blockquote style="padding-left:5px;border-left:#1010ff 2px solid;">
<div dir="ltr">Hi Minko,<br><br>thanks for your help. This is now implemented with r3269.<br><br>Gerd<br><br>
<div>> Date: Sun, 11 May 2014 11:45:47 +0200<br>> From: ligfietser@online.nl<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.<br>> <br>> > what about 0xa ? Or was that meant to be 0x1a ?<br>> <br>> Hi Gerd<br>> <br>> 0x0a gives also a routing error, so everything in the range <br>> 0x01-0x13, 0x16 and 0x1b<br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div>
</div>
<br>
<pre>_______________________________________________
mkgmap-dev mailing list
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
</pre>
</blockquote>
<br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>