- mkgmap-dev - The mkgmap lists

mkgmap Version r4278
by Manfred Haiduk 04 Mar '19

04 Mar '19

Hi all just thinking about as if i missed something. The option "remove-ovm-work-files" seems to do not work anymore, is it a bug or a new feature ? -- Best regards ##################################################### Manfred Haiduk, Zum Fischbach 9, D-52393 Hürtgenwald Germany e-mail mhaiduk(a)t-online.de #####################################################

2 1

Commit r4281: improve default style points, patch by Ticker Berkin:
by svn commit 02 Mar '19

02 Mar '19

Version mkgmap-r4281 was committed by gerd on Sat, 02 Mar 2019 improve default style points, patch by Ticker Berkin: Changes are: Always use 0x2f0c instead of 0x4e00 for amenity=toilet. 0x4e00 isn't findable. 0x2f0c is "Other:Rest Area/Tourist Info". add: tourism=resort [0x2b04 resolution 24] This is searchable under the "Lodgings" > "Resort" category on some devices Use 0x3200 instead of 0x660f for barrier=bollard barrier=...etc. 0x660f is "Land Features:Pillar" and so they all show in FIND, making searching for nearby features less useful. 0x3200 is a small point, that can be labeled with the type of barrier http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4281

1 0

Commit r4280: improve default style polygons, patch by Ticker Berkin:
by svn commit 02 Mar '19

02 Mar '19

Version mkgmap-r4280 was committed by gerd on Sat, 02 Mar 2019 improve default style polygons, patch by Ticker Berkin: Changes are: 0x17, which shows as "Park" in green, is currently used for these OSM objects: park, playground, common, garden, greenfield, meadow, grass, village_green, square/plaza Keep this mapping for leisure=park, playground Use 0x15 for landuse=village_green Use 0x1c for landuse=meadow, grass, greenfield, farmland Use 0x1d for leisure=common Use 0x20 for leisure=garden Use 0x25 for square/plaza Use 0x26 instead of 0x10 for landuse=farmyard 0x26 was unused. 0x10 is used landuse=residential Use 0x26 instead of 0x4e for landuse=farm Use 0x12 instead of 0x08 for landuse=retail 0x12 was unused. 0x08 is "Shopping Center" Use 0x12 instead of 0x05 for highway=services ie consider it a retail area - it normally includes shops, parking, fuel, eating places etc and isn't just a "Parking Lot". Someone suggested this change a few months ago but I can't remember who. Use 0x22 instead of 0x1e for historic=... 0x22 was unused. 0x1e is "Park" add natural=tundra [0x52 resolution 18] This is a standard Garmin type add natural=beach | natural=sand [0x53 resolution 20] This is Garmin type, sometimes labeled "Flat" or Sandbank,tidal/mud flat and the change was suggested by Nick / Minko on 27-Sep-2018 Use 0x0f instead of 0x0c for landuse=commercial 0x0f was unused. 0x0c is "Industrial Complex" Use 0x11 instead of 0x04 for military=danger_area This often covers a large area of other mixed use, and rendering it with partially transparent is much more informative Use 0x23 instead of 0x13 for amenity=... Use 0x24 instead of 0x13 for man_made=... 0x23 & 0x24 were unused. 0x13 is now just used for building Use 0x21 instead of 0x1f for tourism=... 0x21 was unused. 0x1f is "Park" http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4280

1 0

Commit r4279: improve default style lines, patch by Ticker Berkin:
by svn commit 02 Mar '19

02 Mar '19

Version mkgmap-r4279 was committed by gerd on Sat, 02 Mar 2019 improve default style lines, patch by Ticker Berkin: Changes are: Use 0x30 for leisure=track instead of treating it like a footpath. 0x30 was introduced in the last set of changes as the code for various sports tracks (gallop, raceway) Use 0x0b (Road) instead of 0x06 as the "hint" portion of a *_link. 0x0b was unused. 0x06 is used for highway=minor & highway=unclassified Use 0x11 instead of 0x07 for highway=cycleway 0x11 was unused. 0x07 is Alley and is used for bridleway, service... Use 0x17 for various linear barriers and also man_made=breakwater Use 0x1a for car ferries, 0x1b for other ferries. At the moment 0x1b is used for all ferries Use 0x26 instead of 0x10a02 for intermittent steam & drain http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4279

1 0

default style improvements
by Ticker Berkin 01 Mar '19

01 Mar '19

Hi I'd like to make quite a few changes and improvements to the default style. Some of these should be non-contentious: The first change I propose is to make the layout consistent and clearer and I've attached a patch to do this for the points/lines/polygons files. The only change here is white-space (blanks, tabs, new-lines), no other characters have been changed. I've used: $ java ... uk.me.parabola.mkgmap.osmstyle.StyleImpl pathTo/default to check there are no semantic changes, but this program fails to dump the <finalize> section, so I've checked these very carefully via other methods. Next changes I am thinking of are: Simple layout where character changes are involved Provide more information on unnamed objects where a good garmin mapping hasn't been found, eg, after all the shop=known ... lines there is a mop-up: shop=* & shop!=no & shop!=none [0x2e0c resolution 24] changing this to: shop=* & shop!=no & shop!=none {add name='${shop|subst:"_=> "}'} [0x2e0c resolution 24] will name unnamed shops with the value of the shop tag. There are about 15 sections that benefit from this. Add more commonly used tag-values, eg: tourism=bed_and_breakfast [0x2b02 resolution 24] and other mop-ups I think these sort of changes should be applied to the trunk After this, the changes I'm thinking of will require more discussion. Regards Ticker

10 76

Update of typ with correct codepage and special chars
by Joris Bo 28 Feb '19

28 Feb '19

Hello, Thx for all the help and tips. When using utf-8 and codepage 65001 together it works from txt tot typ and back to .txt But it's easy to mess up if you (accidently) re-save from a typ-editor in the wrong txt format, so be careful. Tested from .txt to .typ with mkgmap.jar * In the previous version I made a mistake when restoring a backup column of the German translations after messing up, This should now be the work of Ralf * The Portuguese translations are updated thx to Alexandre * Thx to Steph for the French translations ! * Hopefully fixed the codepage issues Feel free to feedback New languages can be added using the xls Kind regards Joris

4 6

mkgmap experimental options --x..
by dave pitney 23 Feb '19

23 Feb '19

Hello - Is there a listing of mkgmap experimental options? I know these are not listed in the docs (nor should they be) but I may find one that is helpful. Also it should be stated that support for these may not be available. Thanks, -- pitney ----------------- end of message ------------------------

2 1

splitter option? (or new request)
by dave pitney 23 Feb '19

23 Feb '19

Hello - Is there is an option to not compress pbf output files when using splitter? I use the split files as input to mkgmap. Osmium has an option "pbf_compression=none" which is placed in the json file as an option. This increases file size (appx double) but allows faster file reading/writing. Given the low cost of storage and the (relatively) high cost of processing/time this may be a useful splitter option. I am current using r591. Thank you, -- pitney ----------------- end of message ------------------------

2 1

A minor, documentation only change request
by Randolph J. Herber 22 Feb '19

22 Feb '19

This request may cause changes in many places; but, no changes to mkgmap behavior. It took me close to five years to learn what really was meant by: " but the lowest usable resolution with MapSource seems to be 11." in --overview-levels. I suggest a change to " but the lowest usable resolution (coarsest scale, smallest scale number) with MapSource seems to be 11." I had interpreted that the numbers to the right of the colon had to be 11 or smaller numerically. Randolph J. Herber

2 1

posting test
by dave pitney 22 Feb '19

22 Feb '19

testing if pitney can post -- pitney ----------------- end of message ------------------------

2 1