November 2011 - mkgmap-dev - The mkgmap lists

Commit: r2097: 60: Allow more than one base-style
by svn commit 16 Nov '11

16 Nov '11

Version 2097 was commited by steve on 2011-11-16 21:01:38 +0000 (Wed, 16 Nov 2011) 60: Allow more than one base-style

1 0

Cutting down the default style
by Minko 16 Nov '11

16 Nov '11

I work with typviewer which is capable of importing en exporting text files: http://opheliat.free.fr/michel40/TYPViewer3.5/ It is free to use but there is no info about under what license it can be used. You can ask the developer about the source code. You can have a look at http://code.google.com/p/mkgmap-style-s … efault.txt to see if this is workable or not. Also there is Nick Willinks Typwiz editor, http://www.pinns.co.uk/osm/ He is on this list so he might comment on this.

6 14

Commit: r2092: Translate motor_vehicle and vehicle access rules.
by svn commit 16 Nov '11

16 Nov '11

Version 2092 was commited by marko on 2011-11-16 07:48:45 +0000 (Wed, 16 Nov 2011) Translate motor_vehicle and vehicle access rules.

4 4

Option to delete unconnected ways?
by Francisco Moraes 15 Nov '11

15 Nov '11

Hi, Is there an option to pass to mkgmap that would delete unconnected ways? Those unconnected ways lead to routing errors and are useless in a generated map. Francisco

4 4

warn against head-to-head or back-to-back coastline ways
by Marko Mäkelä 15 Nov '11

15 Nov '11

An OSM newcomer edited the coastline last weekend. He had deleted existing natural=coastline ways and replaced them with his own edits, and he forgot to connect the nodes. I fixed that by extracting the natural=coastline ways from the finland.osm.pbf with Osmosis, loading it into JOSM and addressing the validator complaints. All well and good, but the flooding did not cease today. I was puzzled. JOSM did not complain anything. mkgmap only complained the usual stuff about broken coastlines, e.g., when it sees an island polygon on firm ground, or stuff like that. Finally, it occurred to me that the new coastline sections were the wrong way around (land to the right, instead of land to the left). Could mkgmap please issue a warning when it notices that a natural=coastline way is connected to a natural=coastline way that runs in the opposite direction? I will file a similar bug against JOSM. Best regards, Marko

1 1

[PATCH]splitter memory usage
by GerdP 14 Nov '11

14 Nov '11

http://gis.638310.n2.nabble.com/file/n6958659/splitter_memory.patch splitter_memory.patch This patch reduces memory requirement in splitter by ~50% by replacing class SparseInt2ShortMultiMap with class Node2AreaMap. It also includes small performance tweaks. Still not solved by this patch: - Memory usage depends on the highest node id in the data. - Node id > Integer.MAX_VALUE do not work (not a problem at this moment) If this small patch is okay for you, I can provide a bigger one that also fixes these issues, but touches many more files Ciao, Gerd -- View this message in context: http://gis.638310.n2.nabble.com/PATCH-splitter-memory-usage-tp6958659p69586… Sent from the Mkgmap Development mailing list archive at Nabble.com.

5 15

TYP file compiler branch
by Steve Ratcliffe 13 Nov '11

13 Nov '11

Hi There is a new branch for the TYP compiler and its integration into mkgmap, all further development will now happen there. The new name for the compiler to run it standalone is: uk.me.parabola.mkgmap.main.TypCompiler but once it is integrated, then you won't need that, as mkgmap will just compile a .txt to a .typ if it sees one on the command line. The compiler now completely compiles the file I am testing with[1] resulting in the exact same typ file, apart from time stamp, that is also in that directory. I've not tried it on anything else yet, so let me know your results! Only Colormode=0x10 is supported, colour mode 0x20 should be finished soon. ..Steve [1] default.txt in http://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/typ/world-…

1 0

Typ file compiler
by Steve Ratcliffe 13 Nov '11

13 Nov '11

Hi Attached is the first version of the TYP file compiler, using code written by Thomas Lußnig in 2008 to write the TYP file, which has been lying unused in mkgmap since then. It only writes the polygon draw order, so not much use yet, but I expect to be adding the other sections quickly. It reads any valid typ text file, or at least it will read: http://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/typ/world-… So to use it, first compile a jar as normal. Then run the following command (you can not use the -jar option in this case) java -cp dist/mkgmap.jar uk.me.parabola.mkgmap.typ.TypTextReader <in> <out> <in> defaults to "default.txt" <out> defaults to "OUT.TYP" This method of running it is temporary and may even go away at some point. I will check the code in to trunk, since it is completely separate from anything else in mkgmap. ..Steve

3 6

Commit: r2077: The permament name of the typ compiler will
by svn commit 13 Nov '11

13 Nov '11

Version 2077 was commited by steve on 2011-11-13 14:11:11 +0000 (Sun, 13 Nov 2011) The permament name of the typ compiler will be uk.me.parabola.mkgmap.main.TypCompiler

1 0

Commit: r2076: Implement points (POI's) for the TYP compiler.
by svn commit 13 Nov '11

13 Nov '11

Version 2076 was commited by steve on 2011-11-13 12:45:10 +0000 (Sun, 13 Nov 2011) Implement points (POI's) for the TYP compiler. Now compiles the default.txt file completely. Features not in that file may or may not work. In particular at the moment only ColourMode=0x10 for POIs is supported and any specified colour mode is ignored. The input file must be in the native character encoding for your system.

1 0