March 2011 - mkgmap-dev - The mkgmap lists

Sea (or lakes) issue
by Nakor 03 Apr '11

03 Apr '11

Hello, I have a tile out of splitter which covers the area http://www.openstreetmap.org/?minlon=-81.342773&minlat=41.220703&maxlon=-79… . I did not find yet any option to have the lakes (delimited by natural=coastline) rendered properly. I tried various generate-sea options but did not get the expected result. With no --generate sea I get only parts of Lake Erie and Lake Ontario with water (I guess because there are some water=* polygons in those particular places) With extends-sea-sector, MapSource crashes With multipolygons or no-sea-sectors, both lakes are OK but Ontario is flooded With polygons the whole tile is flooded What options should I use to get it right? Thanks, N.

3 14

LOCATOR: doubt about "contains no name tag" messages
by Carlos Dávila 03 Apr '11

03 Apr '11

Processing spain.osm.pbf from Geofabrik I get several "contains no name tag" messages that point to ways tagged in the form: admin_level=8 boundary=administrative It's true they don't have a tag name, but they belong to relations with the same tags + a name and the relation is fully within the tile, so it's supposed they should get the name from the relation. Additionally, there are thousands of ways in Spain tagged in the same way (all administrative boundaries were imported that way) that don't trigger the same warning. As an example you can have a look at way 45338454. It's about 2 km away from the tile border.

2 5

Options overhaul
by Steve Ratcliffe 01 Apr '11

01 Apr '11

Hi There is a new branch for an overhaul of the options. There are a number of recent (and not so recent!) posts about options that are badly documented, have the wrong defaults or just plain shouldn't exist. The first couple of things I plan to do in preparation are: 1. Make it possible to negate any option by pre-pending it with 'no' (eg --no-route). This has the effect of turning off the option for the following files. This is not currently possible. It will also give a consistent way to turn off options that are by default active. 2. Add a way to document old options and and give a warning that the option is no longer in use and what should replace it if anything. This will allow for options to be removed from the help list, without actually removing them from the program, so as not to break existing scripts. If anyone has any thoughts on how the options could be improved now would be a good time to discuss it. Things already on the list include: --charset, --remove-short-arcs, --ignore-osm-bounds, setting options inside the style (which can already be done, its just not really used properly). ..Steve

10 13

polygon overlays
by n Willink 31 Mar '11

31 Mar '11

I've seen many TOPO TYP files with polygons 0x100+ ; they don't always show transparency; are they used as overlays? If so, is it possible to create overlay polygons? The current overlays style file seems to be reserved for polylines only... -- View this message in context: http://gis.638310.n2.nabble.com/polygon-overlays-tp6226235p6226235.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 4

Splitter and .pbf
by Bob Hawkins 31 Mar '11

31 Mar '11

I was advised recently that I could use the much smaller .pbf file rather than .bz2 from Geofabrik, but that I had to use a particular splitter, in this case r161-3. This, I did. I wonder, though, how it is known what particular splitter version to use with, say, the next .pbf file I choose to use. I note, too, that the current splitter page displays r-170 only. I am sure it displayed more when I used it recenty, such as r161-3, for example, which I now find at http://89.16.174.14/detail/8.

6 8

compile issues with mkgmap-r1905
by maning sambale 31 Mar '11

31 Mar '11

I upgraded my mkgmap and had issues with mapsource crashing: App: MapSource At: 3/28/2011 3:55:30 AM (UTC) OS: Windows XP Service Pack 3 Processor: Pentium Pro or Pentium II, RAM: 2047472 GEO_POSITION.HPP-62-6.11.6.0 Language ID: 1033 Part Number: 006-A0041-00 Build Type: Release Upon looking at the installed files, I noticed that the 40000001_mdr.img is on 816 KB whaich used to be 2.1 MB. I also have problems with creating the gmapi for mac: python gmapi-builder -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 -i for_mapsource/40000001.mdx -m for_mapsource/40000001_mdr.img TDB Version: 4.07 Product ID: 1 Family ID: 639 Map Series: OSM_PHIL Map Family: OSM_PHIL Product Version: 1.00 Trademark: Test preview map TDB file contains no detail blocks. Missing part: 0 of . in IMG-file. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

1 2

0x10 for residential in default style
by Jeroen Muris 30 Mar '11

30 Mar '11

Hello all, At the moment, I’m merging my own custom style with the default, and I’m wondering about the use of code 0x10 for landuse=residential in the polygons file. Is 0x10 a standard Garmin code for residential areas? If not, isn’t 0x01/0x02/0x03 a better choice (0x03 is already in use for place=village)? BTW: I hope to be able to switch completely to the default style and then fit my TYP file to that. When I’m done with that, is there any interest for that TYP file? Regards, J-----.

3 20

Overview of OSM tagging vs effects on Garmin maps
by Colin Smale 30 Mar '11

30 Mar '11

Hi, I have been experimenting with mkgmap for a couple of months now. I am not really a Java programmer, but I can read and understand the code easily. Having been surprised by how certain map attributes come through on the Garmin using the standard stylesheets, I have been looking into how the chain currently works from OSM data to mkgmap to the style sheets to the Garmin device so I could consider adjusting the way things are tagged in order to improve the end result. I am of course not advocating "tagging incorrectly for the renderer". My intention is to optimise routing instructions, including both actual turns and the spoken instructions. Browsing through the code, I have discovered quite a few pieces of logic which refer to specific OSM tags which are not, or poorly, documented. For example, the "through_route" relation is extremely useful, and I have seen that the "display_name" tag can override "ref" and "name". Neither of these are documented on the OSM wiki. There are also quite a few "internal" tags in the mkgmap namespace which could concievably be set in the OSM data to override default algorithms in the code. Now there's a discussion taking place about revising the documentation for the command line options, would it be an idea to start some documentation of the way tags are used within the Java code? This would assist anyone wanting to tweak the style sheets without diving into the code. Colin

2 1

Not enough room
by Nakor 28 Mar '11

28 Mar '11

Hello, I have a map where I get this exception: uk.me.parabola.imgfmt.MapFailedException: There is not enough room in a single garmin map for all the input data The .osm file should be split into smaller pieces first. How can I now which input file is too big? Thanks, N.

4 4

[patch] splitter template file issue
by Nakor 27 Mar '11

27 Mar '11

Hi, If mapid starts with a zero, splitter writes an incorrect template.args file. The attached patch fixes it. Thanks, N.

1 0