May 2011 - mkgmap-dev - The mkgmap lists

[locator] Country specific rules
by WanMil 06 Jun '11

06 Jun '11

I want to start to collect and commit your country specific rules. I know some of you have already posted them on the list but I have lost track of it. So please post your country specific rules as an answer in this thread. WanMil

8 52

problems with gmapi-builder
by maning sambale 03 Jun '11

03 Jun '11

I downloaded the latest gmapi-builder and tried the following: ===== python gmapi-builder -v -t for_mapsource/40000001.tdb -b for_mapsource/40000001.img for_mapsource/40000001.img for_mapsource/40000001_mdr.img for_mapsource/63240001.img -s for_mapsource/MINIMAL.TYP Unknown Block: 54, length: 20, '\x00\x00\x17\x00\x00\x00\x00\x00\x00\xe6\x00\x00\xce\x00\x00\x00\x00D\x00\x00' TDB Version: 4.07 Product ID: 1 Family ID: 639 Map Series: OSM_PHIL Map Family: OSM_PHIL Product Version: 1.00 Copyright: OSM Street map Copyright: http://www.openstreetmap.org/ Copyright: Map data licenced under Creative Commons Attribution ShareAlike 2.0 Copyright: http://creativecommons.org/licenses/by-sa/2.0/ Copyright: Map created with mkgmap-r1867 Copyright: Program released under the GPL Trademark: Test preview map Overview map: Map Number: 63240000 Parent Map: 0 Latitude North: 21.5771 Longitude East: 127.7930 Latitude South: 4.5264 Longitude West: 115.6201 Description: Overview Map Missing part: 0 of S?.ϻ in IMG-file. ======= The same data was used for a mapsource installer compiler and there are no problems with mapsource. My old gmapi syntax was python gmapi-builder -v -t for_mapsource/40000001.tdb -b for_mapsource/40000001.img for_mapsource/*.img -s for_mapsource/MINIMAL.TYP -i for_mapsource/40000001.mdx -m for_mapsource/40000001_mdr.img Same error results as above. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

3 12

UK Contours
by Stuart Poulton 02 Jun '11

02 Jun '11

Hi, Has anyone got a quick recipe for STRM contours to garmin for the UK, preferably on Linux ? Cheers Stuart

5 6

Index with Greek names (PATCH)
by Steve Ratcliffe 02 Jun '11

02 Jun '11

Hi In investigating another problem I discovered that an index created for tiles in Greece (and it would also apply to any other place where non-latin letters are used) does not work for finding streets. You can select them but clicking on Find usually does not find them. This is because the transliteration from Greek characters to Roman characters occurs after the labels are sorted for the NET section. This results in them being completely mis-sorted in NET. The attached patch does the transliteration first. It doesn't much affect maps of western European countries, but it would be good to get wider testing before committing it. Maps with ascii labels are sometimes a little smaller, because name that are different but transliterate to the same string used to be duplicated but with this patch they are not. ..Steve

2 4

Error on MapSource with r1919
by Carlos Dávila 30 May '11

30 May '11

MapSource crashes if I try to activate Spain map generated with r1919 throwing a message mentioning DSK_FIRSTIMAGESECTOR.CPP. The same input files compiled with r1916 work fine. Other maps like Morocco, Portugal, Canary Islands, all of them quite smaller, work fine with r1919.

5 36

Re: [mkgmap-dev] Mapsource Error MDR_TRIM_ADDR.CXX-440-6.16.3.0
by Peter Lerner 29 May '11

29 May '11

Steve, > I think we should investigate the lower case letter > problem first and see if that makes a difference. If you can send me the > osm files too I can try it out myself. The OSM src files are uploaded. > I'm not sure why the lower case letters get there, since they only occur > in the ascii transliterations, whereas you are using latin1 presumably. --latin1 --code-page=1252 Peter

1 0

Commit: r1955: Connect multipolygon ways including gap filling only if they have the same role
by svn commit 25 May '11

25 May '11

Version 1955 was commited by wanmil on 2011-05-25 22:23:10 +0100 (Wed, 25 May 2011) Connect multipolygon ways including gap filling only if they have the same role

1 0

Locator_Branch. All POI miss names if they are not present in resolution 24
by Felix Hartmann 25 May '11

25 May '11

Found another bug in the locator branch. If you create a POI like amenity=subway_entrance [0x45 resolution 24 continue] amenity=subway_entrance [0x11100 resolution 23-22] The name is missing from the POI in resolution 23-22.

2 2

[PATCH v1] Multipolygon: Autoconnect ways only if they have the same role
by WanMil 25 May '11

25 May '11

Ways become autoconnected only if they have the same role. WanMil

2 1

Idea: map layers (multiple output tiles per input tile)
by Marko Mäkelä 25 May '11

25 May '11

I got an idea today: Make the style language support layers, and allow the user to specify which layers to generate and in which output files. This would have the benefit that you could generate all output layers from a map in a single run, reducing the parsing and multipolygon processing overhead, and possibly allowing more parallel processing. The default layer (say, layer 0) would always be generated, to keep compatibility with the current behaviour. If we extended the default style so that it would generate overlay lines for bridges and tunnels on a non-default layer, these lines would be omitted by default. Someone with a fancy TYP file could invoke mkgmap with special options to generate these overlay lines, either in the same output tile, or in a separate output tile, so that the map user can enable or disable bridges and tunnels by selecting map sets on the device. Another application would be generating one map family per route relation type, so that you could choose which routes you want to see on the device: ski, bicycle, bus, road network, etc. My current --style=routes lumps all types of route relations together, not very useful. Let me illustrate this rough idea with an example. The syntax is not settled yet; I would appreciate some feedback on this. I think that I should be able to implement this, if there is no serious opposition to this idea. Consider the default style with the following addition to the beginning of the lines file: waterway=* [layer 1] boundary=* [layer 2] By default, all waterways and boundaries would be omitted from the map, because they are not in the default layer. Here is an example of such a default invocation, in the mkgmap.args format: family-id: 42 mapname: 63240001 description: City input-file: 63240001.osm.gz mapname: 63240002 description: Suburb input-file: 63240002.osm.gz Now, let us generate separate map sets for layer 1 and 2: family-id: 42 mapname: 63240001 description: City layer1-family-id: 1 layer1-mapname: 73240001 layer1-description: City Waters layer2-family-id: 2 layer2-mapname: 83240001 layer2-description: City Boundaries input-file: 63240001.osm.gz mapname: 63240002 description: Suburb layer1-family-id: 1 layer1-mapname: 73240002 layer1-description: Suburb Waters layer2-family-id: 2 layer2-mapname: 83240002 layer2-description: Suburb Boundaries input-file: 63240002.osm.gz We could also merge multiple layers to a single output tile by specifying layer3-merge: 2 or even ask mkgmap to merge everything to the default output tile: layer1-merge: default (or 0) layer2-merge: default What do you think? This scheme is only useable when it is acceptable to use the same map tiles for all map sets. If you need smaller or larger tiles for certain map layers, you would need to invoke mkgmap once for every set of input tiles. Best regards, Marko

8 20