[mkgmap-dev] [PATCH v4] - Code around highway shield crap when sorting labels

Sun Mar 21 09:47:15 GMT 2010

On 21.03.2010 10:32, Mark Burton wrote:
> Felix,
>
>    
>> okay searching for roads works very well now.
>>      
> Good.
>
>    
>> However the ENQ problem is
>> not solved for me. Using: /set ref = '${ref}'/ inside relations file for
>> relations that have a ref (like EV6) and then
>> /{ set name='${ref|highway-symbol:box:6:4} ${name}' |
>> '${ref|highway-symbol:box:6:4}'; add display_name='${name}'}/
>> inside lines file, causes mkgmap to create these havoc names.
>>      
> Sorry, once again, I am nonplussed by the style syntax, what does the
> 6:4 mean in the above?
>
>    
This means 6 characters maximum, or 4 non numeric characters maximum if 
I remember it correctly. Default is 7:5 if I remember correctly.
>> If read with mapedit name looks like this:
>> ~[0x2f]EV6 ~[0x2e]EV6 DONAURADWEG
>> inside Mapsource it looks like this:
>> EV6 | EV6 DONAURADWEG
>>
>> Clearly mkgmap has some problem here. There is nowhere at all where I
>> ask [0x2f] or [0x2e] to be included into the name. Furthermore is
>> neither 0x2f nor 0x2e the type of the road.
>>      
> Well, the 0x2f and 0x2e are the 6-bit encodings of the Oval and Box
> shields so at least one of those matches what your doing above but I
> can't see how the Oval code is getting in there. Do you have some other
> rule that adds an Oval shield?
>    
No, the full rules for the highway shields are as follows (I don't think 
there is a bug inside on my part):

( extremecarver=mr | route=mtb ) & ref=*                             { 
set name='${ref|highway-symbol:hbox:6:4} ${name}' | 
'${ref|highway-symbol:hbox:6:4}'; add display_name='${name}'}

extremecarver5=bike & ref=* & extremecarver!=mr & route!=mtb            
{ set name='${ref|highway-symbol:box:6:4} ${name}' | 
'${ref|highway-symbol:box:6:4}'; add display_name='${name}'}

highway=* & ref=* & extremcaver5!=bike & extremecarver!=mr & route!=mtb 
{ set name='${ref|highway-symbol:oval:6:4} ${name}' | 
'${ref|highway-symbol:oval:6:4}'; add display_name='${name}'}
> So I wonder if the problem is that your ending up with a highway shield
> code embedded in the name rather than being a prefix. Perhaps, it
> can only cope with prefix shields.
>    
I don't understand what you mean with /being a prefix/.
> Mark
> _______________________________________________
> 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://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20100321/9e84debc/attachment.html