June 2011 - mkgmap-dev - The mkgmap lists

Footways/cycleways and motorcars
by Francisco Moraes 17 Jun '11

17 Jun '11

Hi, The other day, while routing to a geocache, my Oregon wanted me to "turn" into a greenway which was close to where the geocache would be. Is there a way to avoid this by default? Seems to me that the default style should imply motorcar=no on footway and probably also on a cycleway. If not, should I change the greenways to add the explicit motorcar=no or doing that via style is better? I have not used styles, so I assume it would be simple to override the default just for that. Francisco

5 9

Commit: r1968: Do transliteration before creating the labels so that
by svn commit 17 Jun '11

17 Jun '11

Version 1968 was commited by steve on 2011-06-17 12:23:38 +0100 (Fri, 17 Jun 2011) Do transliteration before creating the labels so that all sorting is done on the transliterated values and not the raw unicode.

1 0

Syntax Question
by Bill Lancashire 17 Jun '11

17 Jun '11

Could someone explain to me the correct way and position to use the (!) in the style files. For example, in the current 'default style' the following two lines exist: railway=rail & !(tunnel=yes) [0x14 resolution 21] leisure=track & area!=yes What is the significance of putting the (!) before the open brackets or before the (=) sign. I mean, would there be any difference between the following two statements and would they both work?: railway=rail & !(tunnel=yes) railway=rail & tunnel!=yes Many thanks.

2 1

search for hexcodes of 64xx, 65xx & 66xx
by maning sambale 17 Jun '11

17 Jun '11

Is there anybody out there, who compiled their map using mkgmap, and where they able to search for Geographic Features (man_made,land & water) using "Mapsource's Find Places" (not nuvi)? these are the POI's with hexcodes of 64xx, 65xx & 66xx? -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 3

Commit: r1966: Do not uppercase names that go into the index.
by svn commit 16 Jun '11

16 Jun '11

Version 1966 was commited by steve on 2011-06-16 20:10:42 +0100 (Thu, 16 Jun 2011) Do not uppercase names that go into the index. Leave them as they were in the input files (which will usually be already in uppercase of course).

1 0

cannot search for street/address when sending to device via Mac Garmin MapInstall
by maning sambale 15 Jun '11

15 Jun '11

My map was a splitted into four tiles compiled with mkgmap r1867 and gmapibuilder.py. I installed the map to mac RoadTrip. I can search for streets using roadtrip. But when I send the maps to my nuvi 1310 using Garmin's MapInstall, I can't search for streets anymore. In nuvi, "Where to" > "Address" then a message will appear "No Map Data Available". The map is available here for anyone to test: http://dl.dropbox.com/u/607635/osm-ph_gps_maps/dev/osmph_macroadtrip_latest… -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 2

River flooding with r1955
by Francisco Moraes 09 Jun '11

09 Jun '11

Hi, While geocaching on Saturday, I noticed an area of the map that was flooded. It seems the following relation is the culprit: http://www.openstreetmap.org/browse/relation/169902 It renders correctly in the openstreetmap, but the mkgmap generated map floods a large area with water: http://www.openstreetmap.org/?lat=36.13856&lon=-78.9059&zoom=15 Any thoughts? Francisco

3 13

[locator] What's next?
by WanMil 09 Jun '11

09 Jun '11

Hi all, it's been a long time since the locator branch was merged and I want to start thinking about what has to be done to merge it back to trunk. So please post your bugs or features that need to be fixed before merging it back to trunk. By the way: do you think the branch should be merged or should we abandon the branch because it has too many flaws? WanMil

8 25

Commit: r1962: Zap warning about unreferenced nodes that only occur for pbf files.
by svn commit 08 Jun '11

08 Jun '11

Version 1962 was commited by steve on 2011-06-08 22:24:07 +0100 (Wed, 08 Jun 2011) Zap warning about unreferenced nodes that only occur for pbf files. - Marko Makela

1 0

Land polygon from sea generator
by Adrian 08 Jun '11

08 Jun '11

I have recently updated my setup to use a new version of mkgmap with improvements to sea generation and indexing. I would like to congratulate all involved for the great progress that has been made. I made a map of Great Britain and France. It occupies 1.1GB and comprises 184 tiles. I extracted the area I wanted from the Geofabrik Europe extract. The mkgmap run took 52 min (Core 2 Duo 2.66GHz, --max-jobs). I gave it 7GB of RAM and it used 4GB. [I am using Apple Java 1.6. Previous releases simply stopped with an error if they ran out of memory. The latest release appears to do something similar to virtual memory, so it does not stop when it runs out of memory, but it becomes extremely slow when it starts to swap to disk.] I used generate-sea:multipolygon,extend-sea-sectors with mkgmap-r1955 (trunk) and the sea all seems to have been generated correctly. There was just one place where a land polygon was missing, and so I got a yellow background instead of white. Tile details from areas.list: 63240143: 2381824,49152 to 2439168,131072 # : 51.108398,1.054688 to 52.338867,2.812500 This tile contained some white land and some yellow land. The yellow area was around 51.9N 1.1E. It is the area south of the Stour estuary including Clacton-on-Sea and Walton-on-the-Naze. I inspected the coastline data of this tile in JOSM and I could not see any problem with it. This is, however, a very complex coastline. The coastline ways and nodes account for about one fifth of the data of the tile. I think this coastline contains an excessive amount of detail. There appears to have been a large-scale import from the Ordnance Survey Vector Map and I suspect the data was not simplified before it was added to OSM. I have uploaded Ipswich.zip to files.mkgmap.org.uk/download. I would be grateful if someone could look at why the land polygon was not generated. The .zip contains: 143coast.osm.gz, which has just the coastline elements from the aforementioned tile, my commands, style and .TYP files, the details from areas.list, and the actual mkgmap command. I tried to use osmosis to extract the coastline elements from the tile, but osmosis could not touch the file produced by splitter, not even an old version of osmosis which supports API 0.5. Osmosis complained that the time stamps were missing. This is what I did instead: 1. Load the file produced by splitter, into JOSM. JOSM produces tens of thousands of warnings but it opens the file. (I believe JOSM was modified specifically to allow it to open splitter tiles.) 2. Use the search feature to select all elements tagged natural=coastline. 3. Create a new data layer. 4. Merge the selection into the new layer. 5. Save the new layer as 143coast.osm. This file lacks the bounds data, so... 6. Expand the file produced by splitter, to 63240143.osm. 7. Use a text editor to copy and paste the bounds element from 63240143.osm to 143coast.osm. (I was surprised that my text editor could open a 100MB file, but it did. It took 0.5GB of RAM.) During the run of mkgmap, three tiles produced errors like this: SEVERE (MapSplitter): 63240175.osm.gz: Area too small to split at http://www.openstreetmap.org/?mlat=52.03131&mlon=0.87899&zoom=17 (reduce the density of points, length of lines, etc.) With two of the tiles, I could not see any resulting defects in the map. For the third tile - 63240175: 2381824,32768 to 2439168,49152 # : 51.108398,0.703125 to 52.338867,1.054688 the only defect I could see was that at resolution 24, the land polygon was missing in the part of the tile to the north of 52.03131N, the latitude given in the error message. This run of mkgmap also prompted other questions which I might raise as separate threads.

3 10