[mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.

Mon May 12 06:04:31 BST 2014

Hi Colin,

I am not sure what you mean. Let me try an example:
I am aware that my Oregon 450t needs e.g.
tourism=camp_site [0x2b05 resolution 24]
instead of
tourism=camp_site [0x2b03 resolution 24]
which is used in the default style.

If I got you right, you want to create some kind of database to keep track of these 
differences and a style that uses a symbol to reference the database.
So, for my example, we would have a database with a symbol
"camp_site_poi_type" and a default value 0x2b03 and a special value 
for the Oregon 450t containing 0x2b05.
The style would then use something like

tourism=camp_site [db:camp_site_poi_type resolution 24]

When reading the style, mkgmap could look up the database to find 
the right value.

If the database would use SQL, we probably need a few tables 
for device types, groups of device types, firmware versions, etc.
Without SQL, it might be another XML file. 

Any ideas how many differences we have  and how they could be stored?

Gerd

Date: Sun, 11 May 2014 12:22:50 +0200
From: colin.smale at xs4all.nl
To: mkgmap-dev at lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.

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.

Colin

On 2014-05-11 11:52, Gerd Petermann wrote:

Hi Minko,

thanks for your help. This is now implemented with r3269.

Gerd

> Date: Sun, 11 May 2014 11:45:47 +0200
> From: ligfietser at online.nl
> To: mkgmap-dev at lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Commit: r3259: remove most checks regarding routable/non-routable types.
> 
> > what about 0xa ? Or was that meant to be 0x1a ?
> 
> Hi Gerd
> 
> 0x0a gives also a routing error, so everything in the range 
> 0x01-0x13, 0x16 and 0x1b
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140512/e0fce562/attachment.html>