Hi WanMil,
what is the benefit of the new handling?
There are many benefits:
1. Thight integration of process-exits and process-destination. You can
decide via style file what happens if a link is part of an exit and
contains a destination tag.
2. Each destination tag is taken into account.
Folks, I'm sometime getting routing issues to some POIs - most seems ok but
some are always showing the problem. I'm wondering if what I'm hitting is
the problem described at:
http://wiki.openstreetmap.org/wiki/Mkgmap/known_issues#add-pois-to-areas_sometimes_places_the_POI_outside_the_polygon
Version 2541 was committed by wanmil on Sat, 30 Mar 2013
Documentation: Add description how to preprocess bounds
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Him
On Sat, Mar 30, Enrico Liboni wrote:
Folks, I'm sometime getting routing issues to some POIs - most seems ok but
some are always showing the problem. I'm wondering if what I'm hitting is
the problem described at:
If I go to Tools-Settings-Map-Map Info only the OSM map is enabled.
However I believe the basemap - if I understood correctly what the
basemap is - is always enabled
by default since when zooming out I can see mountains and (high)ways
outside the tiles I used for my osm map.
I tried by renaming
On Sat, Mar 30, Enrico Liboni wrote:
If I go to Tools-Settings-Map-Map Info only the OSM map is enabled.
However I believe the basemap - if I understood correctly what the
basemap is - is always enabled
by default since when zooming out I can see mountains and (high)ways
outside the tiles
Hi,
I've observed a similar behaviour in BaseCamp. I don't know why the
parameter '--transparent' does not what it is expected to do, but the
background with type '0x4b' is always shown in BaseCamp regardless if the
parameter is set or not.
Is this caused due to BaseCamp behaviour or due to a
Steve Ratcliffe wrote
1. Is the expression key=* also matching with tags created in action
blocks
of previous rules?
Example (nonsense, but representative):
highway=residential { add test=yes; }
test=* [0x06 resolution 22]-- not working
But if test=* is the
Please ensure that you use at least mkgmap version r2479. In older
versions it happened that --transparent did not work for some countries.
WanMil
Hi,
I've observed a similar behaviour in BaseCamp. I don't know why the
parameter '--transparent' does not what it is expected to do, but the
Hi WanMil,
WanMil wrote
Please ensure that you use at least mkgmap version r2479. In older
versions it happened that --transparent did not work for some countries.
Sorry, I've forgotten to mention that I'm using mkgmap version 2540.
Greetings
--
View this message in context:
Another option is to replace 0x4b with another polygon without special
behaviour. That gives consistent results and no drawbacks that I could
notice so far...
On 30.03.2013 18:20, WanMil wrote:
Please ensure that you use at least mkgmap version r2479. In older
versions it happened that
Am 30.03.2013 10:59, schrieb WanMil:
what is the benefit of the new handling?
There are many benefits:
Okay, thanks, I will test it.
Here is the patched mkgmap:
http://rapidshare.com/files/3509423819/dist.zip
Chris
___
mkgmap-dev mailing list
Thorsten many thanks for your help!!!
My osm generated map is routable and I was wrong in my previous post: I did
some further tests with renaming the base map to gmapbmap.iii - so the
device can't use the basemap - and I can properly navigate to address/pois,
just in some pretty long routes
13 matches
Mail list logo
