July 2019 - mkgmap-dev - The mkgmap lists

documentation improvement patch
by Mike Baggaley 30 Jan '20

30 Jan '20

Hi Gerd, I have attached a patch to improve the documentation of the command line. I did it some time ago and had forgotten about it, but the discussion on whether to change default options prompted me to come back to it. The change is purely to the documentation, no code changes. Please review and if it meets with your approval, commit. Thanks, Mike

6 28

New branch for default typ file
by Gerd Petermann 21 Dec '19

21 Dec '19

Hi all, I've created a new branch now with changes proposed by Joris. I hope this helps bringing this forward. Attached is a document from Joris. Gerd

11 52

Building map with Hebrew characters
by Carlos Dávila 18 Nov '19

18 Nov '19

I'm trying to build a map of Israel with Hebrew characters, but using --code-page=1255 a get the following assertion: at uk.me.parabola.imgfmt.app.srt.SRTFile.writeWeights(SRTFile.java:117) at uk.me.parabola.imgfmt.app.srt.SRTFile.writeSrt4Chars(SRTFile.java:99) at uk.me.parabola.imgfmt.app.srt.SRTFile.write(SRTFile.java:63) at uk.me.parabola.mkgmap.combiners.MdrBuilder.init(MdrBuilder.java:117) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:605) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:128) at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:143) at uk.me.parabola.mkgmap.main.Main.main(Main.java:114) With --unicode I also get an assertion: Exception in thread "main" java.lang.AssertionError: -125 at uk.me.parabola.imgfmt.app.BufferedImgFileWriter.put1u(BufferedImgFileWriter.java:154) at uk.me.parabola.imgfmt.app.SectionWriter.put1u(SectionWriter.java:78) at uk.me.parabola.imgfmt.app.srt.SRTFile.writeWeights(SRTFile.java:113) at uk.me.parabola.imgfmt.app.srt.SRTFile.writeSrt8(SRTFile.java:166) at uk.me.parabola.imgfmt.app.srt.SRTFile.write(SRTFile.java:68) at uk.me.parabola.mkgmap.combiners.MdrBuilder.init(MdrBuilder.java:117) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:605) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:128) at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:143) at uk.me.parabola.mkgmap.main.Main.main(Main.java:114) Probably I'm missing something obvious, but I always used --code-page=1251 and have no idea what it may be

5 12

mkgmap:set_unconnected_type differentiate between connected on both sides or on one side only
by Felix Hartmann 14 Nov '19

14 Nov '19

Would it be possible to have the mkgmap:set_unconnected_type=... differentiate between conncected on both sides for lines and only connected on one side? For example I would like to delete all service=driveway shorther than 100m length if they are connected only on one side to another routable line - if they are in between I would like to keep them. (in some countries - e.g. Switzerland and France) often highway=service&service=driveway leads not only to a house but also connects e.g. to a highway=track or highway=path. -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich

5 44

Sample basic mkgmap config file
by Gerd Petermann 13 Nov '19

13 Nov '19

Hi all, here is my proposal for a file which should be good for every new user. I plan to add it to the examples directory in the distributed zip. Please suggest improvements if you miss something really important. I started to write a HOWTO but got stuck because it is so difficult to handle the differences between Windows/Linux/Mac and the usage of relative or absolute paths. I've recently learned that new users might not even know how to copy a file into a hidden directory like C:\ProgramData. I know that some of you distribute packages containing styles and scripts but I think they all work either only on Windows or on Linux or they require further packages like pearl. Correct me if I'm wrong. No idea how to continue here :( Gerd

4 16

type/subtype of points and cities
by Ticker Berkin 05 Nov '19

05 Nov '19

Hi I think the mkgmap internal handling of types/subtypes of points is obscure. In the points style file, the type code is always full, ie type << 8 | subtype, but when the points are read back from the RGN file for the MDR processing, the representation is the same provided the subtype is not zero, otherwise it is just type! Logic then decides that if the value is <= 0xff it is because the subtype is zero. It is simpler and much clearer to preserve the original representation. This also allows unambiguous use of type 0 with subtypes, and, possibly, city with subtypes. It also allows the same function to be used to test a type for being in the 'city' range, regardless of the context. mkgmap wasn't consistent the ranges for the isCity test. City POI are written in a different manner to the RGN file. The old range for this was: type >= 0x0100 && type <= 0x1100 which I've kept, except changing to: ...& type < 0x1200. A similar range was used for MDR5. However, city POI are held in group 1 of MDR 9/10. This is used in Find > City 'By Name'. The old range was: type <= 0xf, where, if the subtype was zero, type is right shifted by 8 (see above), non-zero subtypes messed up the testing. Now it uses the same range as above. Actually neither of these ranges are correct for my Garmin devices. Find > City show nearby POI with types in the range 0x0100..0x0d1f, regardless of the img RGN or MDR. The eTrex Legend labels POIs in this range as {Large/Medium/Small} City/Town and points in the range 0x0e00..0x111f as "*". Find > City 'by-name' returns POI if in group 1 of MDR 9/10. I find it a useful feature to have a POI that can be searched for but doesn't flood the list of nearby points. Generally, non-zero subtypes for cities cause problems in the RGN structure and I've added a test for this to the style validation. There is also a fix to --make-poi-index, but I can't detect any effect of this option. This patch won't make any difference to the img output unless the there are points 0x1000, 0x1100. If this patch is accepted, I'll do the equivalent to the img display system. Regards Ticker

3 13

how to deal with "Attention: Tile contains both drive-on-left (303) and drive-on-right roads" ?
by Alexis Huxley 02 Aug '19

02 Aug '19

Hi, I'm using mkgmap r4287 and trying to process continent files from geofabrik, e.g. http://download.geofabrik.de/asia-latest.osm.pbf. For about the last six months (today included) I have "drive-on-left-and-drive-on-right" errors for either Africa or Asia: I call splitter like this: java -Xmx380000M -jar splitter.jar --max-threads=40 --mapid=38610001 --search-limit=1000000 /u/ahux/tmp-dir/as/asia-latest.osm.pbf The splitter output looks okay, though I note it ends: Number of MapFailedExceptions: 1 Number of ExitExceptions: 0 and then I call mkgmap like this: java -Xmx380000M -jar mkgmap.jar --code-page=1252 --latin1 --route --remove-short-arcs --road-name-pois --add-pois-to-areas --index --location-autofill=bounds --tdbfile --max-jobs=40 --mapname=38610001 --country-abbr=AS --country-name="Asia" --family-id=598 --family-name="OSM_AS" --overview-mapname=as --series-name="OSM Asia (2019 07)" --description="OSM_AS" --generate-sea=multipolygon --bounds=/u/ahux/tmp-dir/as/bounds-latest.zip --precomp-sea=/u/ahux/tmp-dir/as/sea-latest.zip --style-file=/u/ahux/tmp-dir/as/mkgmap/distrib/mkgmap-r4287/examples/styles/default /u/ahux/tmp-dir/as/3861*.osm.pbf and get a *lot* of these: SEVERE (StyledConverter): /u/ahux/tmp-dir/as/38610086.osm.pbf: Attention: Tile contains both drive-on-left (71473) and drive-on-right roads (51) and a few other assorted messages like: SEVERE (MapFailedException): /u/ahux/tmp-dir/as/38610555.osm.pbf: (thrown in RoadDef.writeRgnOffsets()) Overflow of the NET1. The tile (/u/ahux/tmp-dir/as/38610555.osm.pbf) must be split so that there are fewer roads in it SEVERE (RestrictionRelation): /u/ahux/tmp-dir/as/38610173.osm.pbf: Turn restriction (no_straight_on) http://www.openstreetmap.org/relation/9335098 (at http://www.openstreetmap.org/?mlat=-6.405884&mlon=106.829270&zoom=17) via node is not a routing node How should I respond to these messages? I mean: can I use mkgmap's output anyway? Or should I try to get upstream data fixed in OSM? (if yes: how can I turn these error messages into a location?) Or should I modify my calls to mkgmap or splitter? Oh, also another small question: is there any convention/rule/list for '--mapname=NNNNNNNN' or '--family-id=NNN' numbers, or should just make them up? (which what I'm currently doing). Can anybody offer any advice? Many thanks! Alexis

3 12