September 2017 - mkgmap-dev - The mkgmap lists

default style and highway=services
by Gerd Petermann 13 Sep '17

13 Sep '17

Hi all, I've just noticed that there is no special rule for this tag https://wiki.openstreetmap.org/wiki/Tag:highway=services in the default style. In fact, it is often handled by the "mop up" rule highway=* & area!=yes [0x07 road_class=0 road_speed=0 resolution 23] because many mappers forget to add area=yes as suggested in the wiki. I think we should add a rule like highway=services & area!=* & is_closed() = true {add area=yes} somewhere before the mop up rule. Comments? Gerd -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

2 1

Commit r3996: add test to avoid rare NPE in HousenumberGenerator.useAddrPlaceTag()
by svn commit 11 Sep '17

11 Sep '17

Version mkgmap-r3996 was committed by gerd on Mon, 11 Sep 2017 add test to avoid rare NPE in HousenumberGenerator.useAddrPlaceTag() A rare combination of addr:place, addr:street and a way with addr:interpolation in combination with missing road name seems to cause this. Did not find the right place to fix it, so the data is now simply ignored. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3996

1 0

default style:pier
by nwillink 08 Sep '17

08 Sep '17

Hi Just an observation : The default style adds a footway to all piers. (man_made=pier | man_made=piste:halfpipe) & area!=yes {add highway=footway; name '${ref} ${name}' | '${ref}' | '${name}' } I can see why ,particularly with large wide piers like Brighton Pier. Such piers are relatively rare. Unfortunately , the pier tag is too general and can also include a place for mooring (mooring=yes). These 'mooring piers' are most commonly not open to the general public , their entrance being barred by a gate. In an ideal world such piers should have an access restriction. When I visited Falmouth this summer I thought I was able to walk along all the piers mapped ; unfortunately, I couldn't. When I create my 'walking maps' I only add a footway when area=yes or the pier includes route=hiking etc relation. Take Torquay harbour : it looks as if you can do a nice stroll along all these 'piers'; in reality access is private. I'm not sure what to do about this other than adding access tags to each pier. -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

1 0

License issue in mkgmap & splitter source: GPL-2 (v2 only) incompatible with GPL-3 (v3 only)
by Sebastiaan Couwenberg 02 Sep '17

02 Sep '17

Several source files are licensed under the GPL-2 which is incompatible with GPL-3 source in splitter. To combine GPL-2 code with GPL-3 code, the GPL-2 code needs to be license under the GPL-2+ (v2 or later), or dual-licensed under the GPL-2 (v2 only) or GPL-3 (v3 only).[0] The mkgmap source files in question: src/uk/me/parabola/mkgmap/filters/MustSplitException.java src/uk/me/parabola/mkgmap/reader/MapReader.java The splitter source files in question: src/uk/me/parabola/splitter/tools/BitReader.java src/uk/me/parabola/splitter/tools/BitWriter.java test/func/ArgsTest.java test/func/Base.java test/func/SolverAndProblemGeneratorTest.java test/func/lib/Args.java test/func/lib/Outputs.java test/func/lib/TestUtils.java test/uk/me/parabola/splitter/tools/TestBitReader.java Steve & Gerd, can you relicense the code to GPL-2+ (v2 or later) or dual license those files as GPL-2 (v2 only) or GPL-3 (v3 only)? This issue prevents the update of the mkgmap packages in Debian. Kind Regards, Bas [0] https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

3 8