November 2010 - mkgmap-dev - The mkgmap lists

Arabic+non arabic name
by Carlos Dávila 11 Nov '10

11 Nov '10

Is there any chance to get tags like name=Maknâs مكناس correctly displayed?

3 4

Multipolygon broken without warning
by Marko Mäkelä 11 Nov '10

11 Nov '10

Hi WanMil, The Vanajavesi multipolygon looks partially inverted on my map, as you can see in the attached crop of a QLandkarte screenshot. The bay to the south of the pointer is way http://www.openstreetmap.org/browse/way/43149608 and the lake is this multipolygon: http://www.openstreetmap.org/browse/relation/302922 The eastern tip of the inverted triangle could be near the east endpoint of the way, http://www.openstreetmap.org/?lat=61.1396522&lon=24.3896432&zoom=18 None of these have been edited recently. It seems to be this map tile: 63240002: 2822016,969728 to 2916352,1172416 # : 60.553894,20.808105 to 62.578125,25.157318 It would be easier to troubleshoot this if splitter produced something that can be cut by Osmosis. Any ideas what could be causing the issue? Marko

3 13

Missing icons when using TYP file
by Dermot McNally 10 Nov '10

10 Nov '10

Hi, For a while I've been using my own TYP file, customised from the one maintained by Computerteddy. In theory I have changed very little in the file - some road colours, and a few translations from German and American into English :) I've also changed the Family ID to 333 because that's what my maps use. My editing is done using the popular Czech online TYP editor and the resulting TYP file works fine for me when compiled into my maps using mkgmap. With the exception of Teddy's POI icons, such as the one for bus stops. Such icons appear on all of my Garmin devices only as tiny squares, even though the correct icons appear inside the editor. If I download one of Computerteddy's ready-made maps all icons appear as expected. My best guess is that Computerteddy may be overriding the default mappings for elements like bus stops, though I'm hoping to hear any other possible causes before I jump into a replumbing job. Thanks for any pointers, Dermot -- -------------------------------------- Igaühel on siin oma laul ja ma oma ei leiagi üles

3 4

Sea Detection
by Chris66 09 Nov '10

09 Nov '10

Hi, I created a map of a cutout of the europe geofabrik extract including generate sea option. All is OK, but one tile is white instead of blue because it's completely in the sea and contains no coastline. How to detect such tiles? I think this is easy: It contains no or very few data (only some ferry lines). An option for detecting such sea tiles and filling with a sea polygon would be nice. Christian

3 4

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

typ question
by Nick Willink 07 Nov '10

07 Nov '10

Each polygon has a separate generally 4 byte block referred to at 0x47 of a non NT type file header; the first two bytes plainly tells me where the polygon block is found,but what do the other 2 bytes refer to? They are obviously incremental for each polygon and may be related to a polygon’s xpm? Any ideas? Thanks Nick

2 1

Commit: r1728: Multipolygons: Do not issue a warning for non joinable ways outside the bounding box
by svn commit 05 Nov '10

05 Nov '10

Version 1728 was commited by wanmil on 2010-11-05 22:27:50 +0000 (Fri, 05 Nov 2010) Multipolygons: Do not issue a warning for non joinable ways outside the bounding box

1 0

Apply style to relation
by Carlos Dávila 04 Nov '10

04 Nov '10

I want to display all members of a given type of route relation with a custom style, in addition with the line style that corresponds to each member of the relation, which can be tracks or different kinds of roads. I've added the following line to the relations style file: type=route & route=my_type {add my_tag=yes} and the following line to the lines style file: my_tag=yes [0x10603 resolution 12 continue] (I also tried my_tag=yes & highway=* [0x10603 resolution 12 continue]) If I manually add my_tag=yes to a way it is displayed as I want (see attached screenshot), so I assume TYP and lines files are OK. What's the problem with the relations file?

2 2

Commit: r1727: Shortcomings of multipolygon tagging fixed.
by svn commit 04 Nov '10

04 Nov '10

Version 1727 was commited by wanmil on 2010-11-02 18:12:57 +0000 (Tue, 02 Nov 2010) Shortcomings of multipolygon tagging fixed. Problem 1: 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) Problem 2 (cascaded multipolygons): MP1: outer P1 [natural=wood] inner P2 [natural=water] MP2: outer P2 [natural=water] inner P3 [natural=sand]

3 2

Same city name in a different province search results (Fwd: is_in:state)
by maning sambale 04 Nov '10

04 Nov '10

We are testing several points style workaround in order get some basic address search working. In the points style we have these lines: # ------------------------------------------------------------------- # Convert 'is_in:city' or 'is_in:town' (if existing) to addr:city to become searchable in mkgmap1625 addr:city!=* & is_in:city=* {add addr:city='${is_in:city}'; delete is_in:city} addr:city!=* & is_in:town=* {add addr:city='${is_in:town}'; delete is_in:town} # Temporary HACK for none search-able 'state' tags is_in:state=* | addr:state=* | addr:province=* {add prov_name='${is_in:state}'; add prov_name='${addr:state}'; add prov_name='${addr:province}'; add is_in='${prov_name},,Philippines'; set is_in='${prov_name},,Philippines'; delete is_in:state; delete addr:state; delete addr:province;} Below are some observations in search results ---------- Forwarded message ---------- Date: Thu, Nov 4, 2010 at 5:09 PM Subject: is_in:state To: Maning Sambale <emmanuel.sambale(a)gmail.com> while most POI searches are working in garmin with our latest hack, im stuck with the following issue: same city names or town names, eg. San Fernando, La Union & San Fernando, Pampanga here is what i did on: assign two POI city & an amenity (fire station) name=San Fernando place=city is_in:state=La Union is_in:La Union,,Philippines name=San Fernando place=city is_in:state=Pampanga is_in:Pampanga,,Philippines name=A_Fire amenity=fire_station addr:city=San Fernando addr:state=La Union is_in:La Union,,Philippines Upon Searching:The said fire station will appear under "San Fernando, Pampanga, PH" on mapsource's Find command I don't know the order by which the is_in:state are processed, but once San Fernando is declared under Pampanga by any initial POI during compilation (it's not even in aphabetical order), it will stick to Pampanga only. Thus, any succeeding amenity with an addr:city=San Fernando, it will automatically assume that it's on Pampanga, even if I explicitly tagged it as La Union. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

1 0