- mkgmap-dev - The mkgmap lists

[PATCH v1] - misc fixes to subdivision area splitting
by Mark Burton 05 Sep '09

05 Sep '09

In trying to determine the cause of the problem that Felix has reported when tiles use a lot of polygon styles, I have been looking at the code that divides areas into "subdivisions". The attached patch (applies to 1170) makes a few changes in that department. It is not expected to fix the polygon problem but it should be otherwise beneficial in that it will reduce the number of subdivisions created. Please do test this patch, especially if you are processing complex maps as I don't want to commit it until it's had a good bashing. I have processed all of GB and NL without problems.

1 0

Commit: r1169: Make exception messages more realistic.
by svn commit 04 Sep '09

04 Sep '09

Version 1169 was commited by markb on 2009-09-04 23:16:29 +0100 (Fri, 04 Sep 2009) Make exception messages more realistic.

1 0

Commit: r1168: Fixed the fixed* error reporting.
by svn commit 04 Sep '09

04 Sep '09

Version 1168 was commited by markb on 2009-09-04 23:16:26 +0100 (Fri, 04 Sep 2009) Fixed the fixed* error reporting. Now unwraps Errors thrown within worker thread.

1 0

Commit: r1167: Fix isInfoEnabled() so that it tests the correct log level.
by svn commit 04 Sep '09

04 Sep '09

Version 1167 was commited by markb on 2009-09-04 23:16:23 +0100 (Fri, 04 Sep 2009) Fix isInfoEnabled() so that it tests the correct log level.

1 0

RNP type for Nuvi?
by Mark Burton 04 Sep '09

04 Sep '09

Hi, I got my Nuvi (a 255) and the OSM map looks good and appears to route OK. I thought I would use the road name pois but the default type code that gets used (0x640a) doesn't appear in the POI search on the Nuvi - so are there any Nuvi users using RNPs? If so, what type code are you using? Cheers, Mark

1 0

mkgmap creates polygons that break Mapsource panning and also routing in some zoomlevels as well as crashing the GPS
by Felix Hartmann 04 Sep '09

04 Sep '09

*a) *First of all Mapsource >=6.14.1 is not affected. Problem exists on <=6.13.7. And my Vista HCx crashes on trying to zoom into this map and restarts. (this is after a master reset, so it's the map not the GPS). I do assume that Nuvi and other modern units will take the maps without crashing. I have not found out which polygon is responsible for this, and I don't really understand it. The problem may be partly related to the extended types, but the extended types themselves are not the reason for Mapsource crashing on certain zoomlevels. You can download the broken tile here and look at it to find out if you find the problem. What I found out so far: I am using the following "problematic" lines in my style-file: leisure=* & fixme!=yes & import!=* [0x2a resolution 24] tourism=* & fixme!=yes & import!=* [0x2b resolution 24] sport=* & fixme!=yes & import!=* &sport!=skiing &sport!=ski [0x2c resolution 24] landuse=* & landuse!=commercial & fixme!=yes & import!=* [0x2d resolution 24] natural=* & fixme!=yes & import!=* [0x2e resolution 24] amenity=* & fixme!=yes & import!=* [0x2f resolution 24] 1. If I drop these lines (which not include extended polygons everything runs fine) 2. Using them AND using a typfile with extended polygon types mapsource will not pan over this tile from 1-3km resolution (medium detail) --> notice that the problematic lines in question are not even supposed to be included in level 20 (=mapsource 1-3km). 3. Without Typfile or with typfile without definitions of extended polygon types everything is allright and I can pan over this tile. You can download the tile including typfile from here for analysis, and if you feel brave tryout also on GPS (mine crashes but no damage, your mileage may vary): *_http://openmtbmap.org/downloads/gmapsupp.zip_* It is crashing if I put map-detail on GPS to medium, zoom in to 2km or 1.2km, and then try to pan through the tile from northern tileborder (middle between east/west) to the south. In the south of the map 2km zoom level is perfectly fine, also on the side boarders (the area broken in Mapsource is the same where the gps crashes). Maybe the problem is completely unrelated to the extended types, but I think it has something to do with the extended types. *b)* Everyone intending to use extended types for Polygons please keep care. Mapsource will not zoom and pan the map upon putting some extended polygon types into the map. *Breaking Mapsource panning completely, also breaks routing:* 0x1102? Will also break Mapsource panning without typfile if present. Don't ever use theese types. (and probabely many others). * * *Working without problem (as far as I can tell).* 0x1100? 0x1101? 0x10f1? 0x10f0?

2 21

Some feature requests
by Willem Sonke 04 Sep '09

04 Sep '09

Dear mkgmap developers, When using mkgmap, I noticed three things that could be improved a bit to increase the ease of use; because I'm not an experienced Java programmer, I unfortunately can't program them myself and I even don't know if they are possible to implement: * A message when a map has been created successfully: mapname.img created successfully or something. Especially for beginners it seems that the job has failed because no message was given. * A message when a style file couldn't be found; now mkgmap seems to use the default style without warning. * A message when on the command line some options are given after the input file, I have had a big problem with this because I didn't know that you have to specify the options before the input file. For example: You have specified options after the last input file. They will not be processed by mkgmap. Willem1

1 0

Custom POI Icons & resolution
by Mark Burton 04 Sep '09

04 Sep '09

Hi, I thought I would make myself a traffic light icon using the TYP file. The icons appear where you expect but they are visible at higher zoom levels than the built in icons for pois that have the same resolution. I tried a few different type codes without noticing any obvious difference. So what's going on? Are custom pois treated differently with regard to zoom levels? Cheers, Mark

3 5

Commit: r1166: Re-encapsulate some fields in Tags and Element.
by svn commit 04 Sep '09

04 Sep '09

Version 1166 was commited by steve on 2009-09-04 10:06:15 +0100 (Fri, 04 Sep 2009) BRANCH: multipolygon Re-encapsulate some fields in Tags and Element.

1 0

Re: R: [mkgmap-dev] [PATCH v3] - beware of the bollards!
by Marco Certelli 03 Sep '09

03 Sep '09

--- Mer 8/7/09, Mark Burton <markb(a)ordern.com> ha scritto: > Da: Mark Burton <markb(a)ordern.com> > Oggetto: Re: R: [mkgmap-dev] [PATCH v3] - beware of the bollards! > A: mkgmap-dev(a)lists.mkgmap.org.uk > Data: Mercoledì 8 luglio 2009, 11:15 > > Hi Marco, > > > Why either side? shoudn't be enough one side only for > restrict the access to the whole way? > > Hey, thanks for that question, it reminded me that I needed > to make the > POI a routing node to stop routing across the POI when the > start point > is within the restricted region. > > The only case it doesn't work for now is when both the > start and end > points are within the restricted region (one each side of > the POI). > Mark, this is how I "solved" the issue so far: a short piece (say 10m) of footway on one side of the bollard http://www.openstreetmap.org/?lat=41.895031&lon=12.414956&zoom=18&layers=B0… I still do not see the reason to make 2 unaccessible arcs on both sides instead of one. Ciao.

4 5