October 2010 - mkgmap-dev - The mkgmap lists

Overview map
by Steve Ratcliffe 19 Jun '12

19 Jun '12

Hi I have started to implement adding features into the overview map. You can find ready built jar files on the download page and in the 'overview' branch in subversion. It creates the overview map from the .img (as before) and so it is very quick to try out even on a set of tiles covering a whole country. There is no configuration yet, it just takes everything (lines and polygons) that is in the least detailed layer of the detailed maps and adds it into the overview. You will immediately notice a big problem in that the overview map shows up even when the detailed maps are being displayed, so you get ugly jagged lines across the top of the map. I remember this happening the last time we has an overview map and I wonder if anyone can remember if there was a solution then? I'm going to start by trying the (so-called) POI flags, as one of those has been noted to be set differently on detail and base maps before. ..Steve

5 15

Re: [mkgmap-dev] Bad routing error here in Rome...
by Marco Certelli 21 May '11

21 May '11

Hello. I'll re-test the situation every week. Compiled italy.osm.bz2 from download.geofabrik.de 1) latest mkgmap + latest splitter: Routing Error in Mapsource and Nuvi 255 2) mkgmap 1188 + oldest splitter (51kB): No Error in Mapsource and No error in Nuvi 255 Ciao, Marco. --- Dom 31/1/10, Marco Certelli <marco_certelli(a)yahoo.it> ha scritto: > Da: Marco Certelli <marco_certelli(a)yahoo.it> > Oggetto: Re: [mkgmap-dev] Bad routing error here in Rome... > A: "Development list for mkgmap" <mkgmap-dev(a)lists.mkgmap.org.uk> > Data: Domenica 31 gennaio 2010, 16:43 > Hi Mark. > > No way. I reduced maxnode to 500000 (Italy is splitted in > 42 tiles) > > I tested latest splitter and latest mkgmap: exactly same > error as before in mapsource routing. > > Ciao, Marco. > > > --- Sab 30/1/10, Mark Burton <markb(a)ordern.com> > ha scritto: > > > Da: Mark Burton <markb(a)ordern.com> > > Oggetto: Re: [mkgmap-dev] Bad routing error here in > Rome... > > A: mkgmap-dev(a)lists.mkgmap.org.uk > > Data: Sabato 30 gennaio 2010, 17:00 > > > > Hi Marco, > > > > > Here is the part of the cmd script doing the > actual > > job: > > > > > > java -enableassertions -Xmx1000m -jar > > ..\bin\splitter.jar --mapid=66%FID%001 > --max-nodes=1000000 > > ..\OSM-Data\%osmfile% > > > > > > java -enableassertions -Xmx1000m -jar > > ..\bin\mkgmap.jar --code-page=1252 > > --country-name="%country%" --latin1 --family-id=%FID% > > --mapname=66%FID%001 --overview-mapname=66%FID%000 > --tdbfile > > --series-name="OSM-%country%" > --family-name="OpenStreetMap: > > %country%" --road-name-pois --add-pois-to-areas > > --no-poi-address --ignore-maxspeeds > --remove-short-arcs > > --preserve-element-order > > --style-file=..\bin\resources\styles\ --style=%style% > > --description="%country%" --route --net --gmapsupp -c > > template.args > > > > OK - thanks. > > > > Have you tried using smaller tile sizes? i.e. does the > same > > problem > > exist if you use, say, 500000 for max nodes? > > > > Also, does the map show any other problems in that > area > > apart from > > routing not working? > > > > Mark > > _______________________________________________ > > mkgmap-dev mailing list > > mkgmap-dev(a)lists.mkgmap.org.uk > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > > > >

6 15

actual splitter branch
by h.scholland＠googlemail.com 22 Nov '10

22 Nov '10

Hi, I would like to use new binary-format with mkgmap splitter, but I've no idea how to build a jar-file from branch. In makgmap-dev I read that you have build it successfully. Would it be possible, that you send me a working splitter.jar with binary support? You can email it to h.scholland(a)googlemail.com Greets aighes

6 11

RFE --merge-lines only from resolution X
by Felix Hartmann 07 Nov '10

07 Nov '10

Currently the --merge-lines works in all resolutions. However in resolution 24 and 22 there is not much speed improvement on the GPS, but it's quite annoying that the information pop up on hoover shows in the wrong place. It would be great if one could specify the first resolution from which the --merge-lines is actually used. I think 21 or 20 down, would be best, but setting it via the commandline or "options" file would be better than hardcoding it.

3 16

Re: [mkgmap-dev] Missing ways part 1
by Adrian 02 Nov '10

02 Nov '10

Marko wrote: > If I remember previous discussions correctly, splitter does not split > lines exactly at the tile border, but instead it includes all nodes > that are not too much outside the tile. That is also what I understood. Splitter includes in each tile, the nodes that fall within the tile, and also the nodes in an overlap region around the tile. The width of the overlap can be set with --overlap. > An almost-straight long way can be drawn with few nodes. You could > help the situation by adding a point to the line close to the > splitting border. I would expect it to cause a problem, if a particular way does not have a node in the overlap region. The difficulty with your fix is that it would only work for me (and only if I use the same areas.list each time); it will not work for other users. Also, it will not work for me in the long term, because data is continuously added to OSM, so the tiles need to be made smaller as time goes on. As I understand it, splitter is intended to clip ways at the last included node. [This is done to avoid an additional pass through the input file.] If there is no node in the overlap region, I would expect the way to stop short of the bounding box. In the finished map, I would expect to see a gap in the way at the tile boundary. The maximum length of the gap would be one segment, between adjacent nodes. What I am actually seeing is that the way is entirely lost from both tiles. When inspecting the tiles in JOSM, I can see that all the nodes are present, including those from the missing way. But few of the nodes in the overlap region have ways attached. So it appears that splitter is not working as intended.

4 8

Turn restrictions apparently broken in osm.pbf
by Marko Mäkelä 02 Nov '10

02 Nov '10

Hi Steve, I am seeing bogus warnings like this when processing a file in the OSM Protobuf format: 2010/10/31 21:17:25 WARNING (RestrictionRelation): finland.osm.pbf: Turn restriction http://www.openstreetmap.org/browse/relation/168868 (at http://www.openstreetmap.org/?mlat=61.89944&mlon=27.80067&zoom=17) lacks 'via' node (guessing it should be at http://www.openstreetmap.org/?mlat=61.89854&mlon=27.80311&zoom=17, why don't you add it to the OSM data?) If I process the same data in the OSM XML format, I do not see these messages. Could it be that the RestrictionRelation handler is picky about the order of the relation members when processing osm.pbf input? Best regards, Marko

2 3

Sea polygon on top
by Carlos Dávila 31 Oct '10

31 Oct '10

One user of my maps, with an iQue 3600 device, has reported that the maps are displayed with the sea polygon on top of the map. Map is generated with --generate-sea=polygons. In the TYP file sea polygon is defined with drawing order 2 and land polygon with drawing order 3. Other devices don't show this problem. I seem to recall having read that different devices may behave different about map layers priority. Could you confirm this? Is there a way to avoid this problem, other than using --generate-sea=multipolygon

1 0

[PATCH v1] Improved tagging of multipolygons
by WanMil 31 Oct '10

31 Oct '10

The patch fixes the following tagging: polygon A: leisure=nature_reserve (the complete area) polygon B: natural=water (only the inner area) multipolygon relation: natural=wood and outer=polygon A and inner=polygon B (only the surrounding area) => See also thread http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2010q3/009112.html The patch fixes also problems with cascaded multipolygons. MP1: outer P1 [natural=wood] inner P2 [natural=water] MP2: outer P2 [natural=water] inner P3 [natural=sand] Without this patch P2 was added twice to the map. Once with the complete polygon area and once with the cut out P3. I think this patch will also make it possible to remove the unlovely tag-removal-map used by the multipolygons. But first I have to check that in deep. Please test this patch carefully with some of your well known multipolygons! I would not be surprised by the patch containing some unwanted stuff... WanMil

1 1

motorway_link not always oneway
by maning sambale 28 Oct '10

28 Oct '10

The default style treats motorway_link as oneway by default. I've seen some cases (in the Philippines) where this isn't so. Is it the same case for other countries? If so, I propose we modify the default style. Or, any suggestions to modify the style? http://www.mkgmap.org.uk/svn/wsvn/mkgmap/resources/styles/default/lines -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

10 23

Speed Limit Icon
by Reinhard Randoll 27 Oct '10

27 Oct '10

Hi, i use mkgmap for some weeks now and I really like it! I have one Question: My Garmin device shows a speed limit icon in the screen with the standard map and some downloaded OSM-based-mkgmap-generated maps. But the maps I generate show never this speed limit icon??? I searched a lot but did not find out what option I have to activate? Can you halp me? Thanks, Reinhard

3 2