- mkgmap-dev - The mkgmap lists

Commit: r3664: add check to make sure that roads have more than one point , else later processing may fail with assertion
by svn commit 04 Feb '16

04 Feb '16

Version mkgmap-r3664 was committed by gerd on Thu, 04 Feb 2016 add check to make sure that roads have more than one point , else later processing may fail with assertion

1 0

Commit: r3663: remove debug code which produces lots of error messages
by svn commit 04 Feb '16

04 Feb '16

Version mkgmap-r3663 was committed by gerd on Thu, 04 Feb 2016 remove debug code which produces lots of error messages

1 0

Commit: r3662: exit-hints-v1.patch : improve exit/destinatio hints
by svn commit 01 Feb '16

01 Feb '16

Version mkgmap-r3662 was committed by gerd on Mon, 01 Feb 2016 exit-hints-v1.patch : improve exit/destinatio hints the patch - adds secondary_link and tertiary_link ways to the list of candidates for splitting - adds destination:street and and destination:lanes:forward/ backward to the tags which might be used as a replacement for destination - tries to explain a bit more how the option process-destination works in the help and doc

1 0

address search
by demon.box 29 Jan '16

29 Jan '16

hi, excuse me, how can I have in MapSource an address search result like this (open mtb map)? <http://gis.19327.n5.nabble.com/file/n5866219/omm.jpg> with my compiled map I have only this result: <http://gis.19327.n5.nabble.com/file/n5866219/mio.jpg> there's only the addr:street tag without addr:city and addr:country how can I make this in my style rules? thanks! --enrico -- View this message in context: http://gis.19327.n5.nabble.com/address-search-tp5866219.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

4 6

Order of objects rendered
by Dave Swarthout 28 Jan '16

28 Jan '16

I saw a note on the tagging list just now that reflects on something I've been curious about for some time. If mkgmap comes upon an object that has two tags, both of which are valid, which one will mkgmap use? Here is the post: One of the rules we use is the "one feature, one OSM element” [1] This makes sense for a lot of elements, e.g. if something has the tag: higway=residential it would be silly to also have amenity=restaurant on the same element. But it is not very uncommon to have a memorial that was created as a piece of art by an artist. One could tag such an object with: tourism=artwork historic=memorial and of course add other relevant stuff like artist_name etc. But what should be rendered in such a case? The memorial or the artwork? >From my understanding, once a node or way with a valid code has been encountered during style processing, mkgmap considers it finished and moves to the next item. But let's say I prefer to see the historic=memoriaI tag rendered and don't care about artwork, is there a way to prioritize the assignment of icons to one of those tags? Cheers, Dave -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

How do I get a GPS "pin drop" to show addresses along a road?
by greg crago 27 Jan '16

27 Jan '16

In City Navigator, when I move my GPS cursor (a pin symbol) over a road, it displays the address as well as the street name. My current maps just shows the street name. I am using the \bounds.zip and --index, --housenumbers -- -x-split-name-index --poi-address Is there anything I am missing? Is the SEQUENCE of these options important in the command line? Greg

1 0

Basecamp v 4.5.2 will NOT display linetype 0x17
by greg crago 27 Jan '16

27 Jan '16

I just discovered that linetype 0x17 does not show up in Basecamp v4.5.2 for some reason? This is not routable, I used 0x00 and it does show up. Go figure.

1 0

[Patch v1] improve exit hints
by Gerd Petermann 26 Jan '16

26 Jan '16

Hi all, I've combined the patches link-hook-v1.patch destination_tags_v1.patch hints_v1.patch into the attached one, I've also improved the docu in options.txt. The patch - adds the evaluation of destination:street and destination:lanes:forward (*:backward) - adds secondary_link and tertiary_link to the processed road types - fixes an issue with the style rules so that the exit number is used when both mkgmap:exit_hint=true AND mkgmap:dest_hint=true match. Please check esp . the changes in the rules for lines, I am not sure if the usage of new tags like exit_hint=* and dest_hint=* are a good idea, maybe they should be prefixed with work: or so to make clear that they are only used to build a part of the name. I've tested this with a few files and found no problems, so if I here no complains I'll commit it on friday. A binary can be found here: http://files.mkgmap.org.uk/download/289/mkgmap.jar Gerd

1 0

dasch map
by Steve Sgalowski 26 Jan '16

26 Jan '16

with keep complete false i get this warning msg up any ideas what i should look for my compile string is this start /low /b /wait java -enableassertions -Xmx2400m -jar ..\bin\mkgmap.jar>mkgmap.log --link-pois-to-ways --polygon-size-limits="23:15, 22:14, 21:13,20:12,19:11 18:10, 17:9, 16:8, 15:7, 14:6, 13:5, 12:4 ,11:3 10:2, 9:1, 8:0 " --process-exits --keep-going --process-destination --merge-lines --style=default --pois-to-areas-placement=tagelist --tdbfile --transparent --make-poi-index --reduce-point-density=2.6 --reduce-point-density-polygon=4 --index --levels=0:24,1:23,2:22,3:21,4:20,5:19,6:18,7:16 --verbose --route --country-name="%country%" --family-id=%FID% --mapname=66%FID%001 --overview-mapname=66%FID%000 --series-name="OSM-%country%" --family-name="OpenStreetMap: %country%" --style-file=..\bin\styles\ --style=%style% --description="%country%" -c ..\bin\template_basic.args -c template.args %TypFileToAdd% Stephen

2 4

[Patch v1] reduce line distortion
by Gerd Petermann 26 Jan '16

26 Jan '16

Hi all, in a private mail Minko pointed out that the changes in the housenumber code introduced a "cosmetic problem": If the housenumber code adds a so called number node to a road and the style also added one or more overlays for that road the road and the overlay line(s) may no longer be the same. In some cases the added number node was > 1 m from the overlay line(s), so the map looks as if there are two roads. The attached patch changes the calculation of the position of the number node so that smaller distortion is preferred. It also simplifies the code, which should be continued ... I think a distance of less than 0.4 m is not visible, and nearly all calculated points are now closer than that. A binary based on r3658 is here: http://files.mkgmap.org.uk/download/287/mkgmap.jar If I here no complains I'll commit this patch next Monday. Gerd

4 7