November 2018 - mkgmap-dev - The mkgmap lists

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

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

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

Re: [mkgmap-dev] Add a POI to the start of a relation (route:mtb)
by andreas.schmidt.hetschbach＠t-online.de 10 Dec '18

10 Dec '18

Hi Gerd, great idea and it works good for my puposes. In principle I try to do the following: Use Option –add-pois-to-lines • Add a tag route_mtb_info_point to the first member of a route • Add all the relevant relation Information • Add the „direction“ (role=backward/Forward) of the first member • Add an element in the Points-file which is shown at the start or the end (or in the middle if there is no direction) in relation of the direction of the way I can search for POI like „MTB-Info…“ and get all the MTB-Routes around my Position. The POI are at the start (or nearby) of the route (if the mebers are ordered) or somewhere on the route – as expected. Sometimes there are two POI for one route I have the following in my style: #add tag for direction to each member, could be both if way is twice or more with diff Direction in the route. route=mtb{apply role ='backward'{set mtb_role_backward="yes";} } route=mtb {apply role ='forward'{ set mtb_role_forward="yes";} } #save data of first member of the route, (could be more than one route but not relevant in this example) route=mtb{apply_first { set route_mtb_info_point="yes"; set route_mtb_info_point_forward="$(mtb_role_forward)"; set route_mtb_info_point_backward="$(mtb_role_backward)"; set route_mtb_name="$(route_mtb_name)-${name}"|"${name}"; set route_mtb_ref="$(route_mtb_ref)-${ref}"|"${ref}"; set route_mtb_info_actual ="HM:k.A.,KM:k.A."; set route_mtb_info_actual="HM:${ascent},KM:${distance}" | "HM:${fee},KM:${distance}" | "KM:${distance}" | "HM:${ascent}"; set route_mtb_info="$(route_mtb_info)-$(route_mtb_info_actual)"|"$(route_mtb_info_actual)"; echotags"rel apply_first" } I expected that for a way which is only member of one relation the values of route_mtb_info_point_forward and route_mtb_info_point_backward could never be „yes“ at the same time for both, because only the first member of the relation is under investigation. But it seems that if a way is more than once a member in a relation, the data of both positions are stored (the way is the first (backward) and the last (Forward) member of the relation). Way 337595135 [highway=track, motor_vehicle=forestry, mtb_role_backward=yes, mtb_role_forward=yes, route_bicycle=yes, route_hiking=yes, route_mtb_info=HM:754,KM:30, route_mtb_info_actual=HM:754,KM:30, route_mtb_info_point=yes, route_mtb_info_point_backward=yes, route_mtb_info_point_forward=yes, route_mtb_name=MTB-Strecke Breuberg 1, route_mtb_ref=Bb1, route_name=Odenwaldklub HW 27, Seligenstadt - Waldbrunn - Bad Rappenau-2-Burgen-Radweg-Rundwanderweg Breuberg Burg Breuberg 3: Scheuerberg-Weg-Rundwanderweg Breuberg Burg Breuberg 2: Schanzen-Weg-Rundwanderweg Breuberg Burg Breuberg 2: Schanzen-Weg-Südhessen-Route 22, route_ref=HW 27-2BR-3-2-2-22, route_symbol=rotes X auf weißem Grund, tracktype=grade2] rel apply_first The Points – file includes the following: route_mtb_info_point="yes" & route_mtb_info_point_forward="yes" & mkgmap:line2poitype=start {set mkgmap:label:1 = "MTB-Info: ${route_mtb_ref} ${route_mtb_name} ${route_mtb_info}"}[0x1010a resolution 20-24 ] route_mtb_info_point="yes" & route_mtb_info_point_backward="yes" & mkgmap:line2poitype=end {set mkgmap:label:1 = "MTB-Info: ${route_mtb_ref} ${route_mtb_name} ${route_mtb_info}"}[0x1010a resolution 20-24 ] route_mtb_info_point="yes" & mkgmap:line2poitype=mid & route_mtb_info_point_backward!=* & route_mtb_info_point_forward!=* {set mkgmap:label:1 = "MTB-Info: ${route_mtb_ref} ${route_mtb_name} ${route_mtb_info}"}[0x1010a resolution 20-24 ] This results in 2 POIs for this route. Andreas Gesendet von Mail für Windows 10

2 4

label rendering
by brad 05 Dec '18

05 Dec '18

How are street/highway/POI labels controlled, level and font size? How can I change them?

7 11

Missing addr:place addresses
by Lorenzo Mastrogiacomi 03 Dec '18

03 Dec '18

I have several addr:place addresses missing in the generated map, Garmin does not show them in the address search. Examples: ----- City: Potenza Picena Street (place): Contrada Spirito Santo all numbers are missing (street is not found at all): https://overpass-turbo.eu/s/DAt ----- City: Potenza Picena Street (place): Contrada Altavilla missing numbers 2, 15, 17, 18: https://overpass-turbo.eu/s/DAu Attached log file from mkgmap. Can you understad what appens from that? Thanks Lorenzo

3 18

semicolon in key value
by ValentinAK 29 Nov '18

29 Nov '18

Hi all How to use the key value with a semicolon? Example: *whitewater=put_in;egress* Best regards, Valentin -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

3 4

Openstreetmap URL
by nwillink 28 Nov '18

28 Nov '18

Hi Gert Just a minor observation SEVERE (StyledConverter):args\16620002.o5m: Found multiple points with equal coords as CoordPOI at http://www.openstreetmap.org/?mlat=50.764580&mlon=-3.427609&zoom=17 Perhaps all openstreetmap urls included in an error message should precede with https not http? Regards Nick -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

4 3

Commit r4257: defaultStyleTidy2.patch by Ticker Berkin. His comments:
by svn commit 26 Nov '18

26 Nov '18

Version mkgmap-r4257 was committed by gerd on Mon, 26 Nov 2018 defaultStyleTidy2.patch by Ticker Berkin. His comments: The changes are: A few minor white-space changes that I missed in the previous batch. Remove unnecessary () in conditions Add tmp: prefix to tags that are just used by the style logic, so it is clear they don't have special meaning to the mkgmap code and don't overwrite osm tags. There are still a few tags created in relation that I think should be renamed (mkgmap:boundary_name, mkgmap:relref, mkgmap:fast_road, mkgmap:us_interstate, mkgmap:us_usroute, mkgmap:us_state) but I won't do this yet. Ferries default to mkgmap:toll=yes add a few new points: amenity=charging_station amenity=grave_yard, crematorium amenity=post_box amenity=recycling amenity=restaurant, cuisine=curry, fish_and_chips, indian, seafood amenity=swimming_pool tourism=bed_and_breakfast add default name, either as [default_name ...] or {add name=...} to: amenity=fast_food amenity=prison amenity=restaurant amenity=playground amenity=recreation_ground shop=* tourism=* man_made=* Improve Embassy name http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4257

1 0

Commit r4256: Line pixmap width check, and unicode typ files
by svn commit 26 Nov '18

26 Nov '18

Version mkgmap-r4256 was committed by steve on Mon, 26 Nov 2018 Line pixmap width check, and unicode typ files http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4256

2 1