logo separator

[mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

From Gerd Petermann GPetermann_muenchen at hotmail.com on Thu Feb 11 06:54:34 GMT 2016

Hi Greg,


the problem is similar to the one here:

http://gis.19327.n5.nabble.com/mkgmap-r3665-complie-error-removing-road-class-and-road-speed-made-a-non-routable-line-tp5867289p5867294.html


Your change made the line with 0x02 visible in res 24, and that triggers the warning.


Gerd


________________________________
Von: mkgmap-dev-bounces at lists.mkgmap.org.uk <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von greg crago <gregcrago at gmail.com>
Gesendet: Mittwoch, 10. Februar 2016 23:28
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Changing from RESOLUTION RANGE to single RESOLUTION causes compile error in r3665

Gerd, I still do not understand.

Let's say I WANT resolution 17-24


The rule

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

means res 17 - 24.



but when I use this ([0x02 resolution 17 continue]) , I get an error compiling. All of the other instances of a single resolution (which means x-24) do not give compile errors, it seems only lines with


 ( network=e-road | int_ref=* )


Greg

On Wed, Feb 10, 2016 at 5:15 PM, Steve Sgalowski <steve.sgalowski at gmail.com<mailto:steve.sgalowski at gmail.com>> wrote:
i run my resolution from 24-18  on all my poi files , due to the type of work i do in australia

Stephen


On Thu, Feb 11, 2016 at 8:11 AM, greg crago <gregcrago at gmail.com<mailto:gregcrago at gmail.com>> wrote:
Default line style has this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17 continue]

I wanted to only show this on RESOLUTION 17, so I changed it to this:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 17 continue]

Now when I compile using mkgmap -r3665 I get this error:

Warning: routable type 0x02 is used for non-routable line with level 0. This may break routing. Style file lines, line 165.

How does changing the Resolution Range to a single Resolution cause this error?

Greg

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto: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<mailto: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/20160211/ac267399/attachment.html>


More information about the mkgmap-dev mailing list